fix: bump aidotnet.tensors to 0.103.1 — fix ModelFamily-NeuralNetworks streaming crash

[ooples]

What

Bumps AiDotNet.Tensors 0.102.17 -> 0.103.1.

Why

0.103.1 ships AiDotNet.Tensors #692, the root-cause fix for the
ModelFamily – NeuralNetworks CI shard failures.

Those shards are not failing on the models — the models are correct (they pass
with weight-streaming off). They fail because of a weight-streaming bug:
WeightRegistry.ReleaseToPool used the strict storage drop, which throws
"sole storage ownership; refcount 2" when a forward-time peer (COW clone /
compiled-plan rebind / int-quant alias) shares a materialized streaming weight's
storage. MaterializeScope.Dispose aggregates that into the AggregateException
that breaks every paper-scale VLM forward on the 16 GB runner. The near-master O-R
shard fails on Phi3Vision x10, every one with that exact exception.

#692 mirrors the established #430 soft-defer fix (defer the drop instead of
throwing). Validated upstream: 56/56 streaming tests + the exact consumer repro.

Note

A separate streaming perf timeout (paper-scale single-forward churn on the
16 GB runner) is tracked independently; this PR lands the correctness fix that
removes the crash/AggregateException class.

🤖 Generated with Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
aidotnet_website	Ready	Preview, Comment	Jun 25, 2026 11:12pm
aidotnet-playground-api	Ready	Preview, Comment	Jun 25, 2026 11:12pm

[coderabbitai]

Warning

Review limit reached

@ooples, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 2 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based credits.

🚦 How do rate limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: ASSERTIVE

Plan: Pro

Run ID: 34d9246f-1c7d-4a1a-affc-b8f29e1f462c

📥 Commits

Reviewing files that changed from the base of the PR and between d377a3c and 4dc5e10.

📒 Files selected for processing (1)

• Directory.Packages.props

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch fix/neuralnetworks-modelfamily-shards

---

_{Comment @coderabbitai help to get the list of available commands.}