chore(release): 10.0.3

[branarakic]

Release 10.0.3

Version bump for the 10.0.3 release cut from main (b0bbb511a). Patch release — node/UI/devnet stability fixes; no smart-contract changes, no deployment required (no Solidity source or ABI changes since 10.0.2).

What's in it (13 PRs since v10.0.2)

• Node UI — PCA owner-access model hardening (refactor(node-ui): decompose ConvictionDetailView into sections + shared hooks (#1348, #1375) #1446, refactor(node-ui): extract ApproveWalletsModal batch orchestration into a reducer + runner (#1350) #1453, refactor(node-ui): centralize the PCA owner-access model + resolve signer once (#1375) #1468, refactor(node-ui): consolidate approve signer planning into the owner-access model + close the snapshot-load lock (#1470, #1469) #1472; PCA node-UI: decompose ConvictionDetailView DetailBody into section components #1348/PCA node-UI: extract ApproveWalletsModal batch orchestration into a reducer/runner #1350/PCA HW: consolidate owner access, progress, and detail-view orchestration #1375 series)
• Folded-private ACK anchoring on storage-ack v2 (v10: Folded public+private KAs never anchor on-chain — shouldCollectV10ACKs gates on !hasPrivateData #1369, Fix folded private publish anchoring #1371)
• Reduced node RPC load + usage metrics (Reduce DKG node RPC load across startup and steady-state polling #1440, feat(telemetry): RPC usage metrics — raw JSON-RPC request counts per node/method #1409)
• WM→SWM promote migration fix (Intermittent WM→SWM promote migration fails to land the root in shared memory (blocks node-ui e2e on main) #1464, fix(#1464): WM→SWM promote e2e flake — dedicated-CG isolation + un-masking #1483)
• Base mainnet ACK candidate filtering by active relays (Codex/base mainnet ack candidate filter #1482)
• Devnet UI solc/config (test(evm/devnet): pin E2E devnet to solc 0.8.24+cancun (fix V10-UI-Tests) #1403), testnet store preflight (fix(testnet): store-outage resilience — worker respawn, write-preflight rescue, ACK dead-air decline #1408)
• Devnet regression lane repaired against the Add lifecycle-native Knowledge Asset CLI #1410 KA-publish CLI unification (fix(devnet): repair suites broken by #1410 + daemon.log double-write; harden stress/lifecycle blind spots #1496)

This PR

• Lockstep version bump of all 20 workspace package.json files 10.0.2 → 10.0.3 (matches the 10.0.1→10.0.2 convention; internal deps are workspace:*).
• CHANGELOG.md [10.0.3] section.
• Lockfile untouched (the only 10.0.2 strings in pnpm-lock.yaml are third-party deps), so pnpm install --frozen-lockfile stays valid.

After merge

Tag v10.0.3 on main → release.yml builds the GitHub Release + markitdown binaries → manual pnpm -r publish (OTP) → move mainnet/testnet dist-tags. See DKG-RELEASE-10.0.3-RUNBOOK.md.

[otReviewAgent]

🟡 Issue: The new release heading accidentally captures existing Unreleased notes

What's wrong
The changelog now has an empty Unreleased section followed immediately by the 10.0.3 heading, while the pre-existing #960 Fixed block remains below that heading. That makes the release-history structure ambiguous and easy to mismaintain because a future release editor cannot tell whether the older block was intentionally included in 10.0.3 or was stranded by the insertion point.

Example
A reader scanning the changelog will now see the #960 dkg init fixes under the 10.0.3 release, not under Unreleased. If those notes are still unreleased, the file now gives the wrong release-history structure; if they are included in 10.0.3, they should be deliberately folded into the new Fixed section instead of left as a second, standalone ### Fixed block.

Suggested direction
Make the section boundary explicit: keep unreleased work above the 10.0.3 heading, or merge the #960 entry into the 10.0.3 release notes intentionally so future readers do not have to infer whether it shipped.

Confidence note
This assumes the existing #960 changelog entry was meant to remain under Unreleased; the diff places the new release heading before it without moving that entry, so the section ownership changes even though the lines themselves are unchanged.

For Agents
Inspect CHANGELOG.md around the top release sections. Preserve the intended 10.0.3 notes, but either move the #960 block above the 10.0.3 heading under Unreleased, or explicitly merge it into the 10.0.3 Fixed content if it shipped in this release. Verify the top of the changelog has clear section ownership: Unreleased only contains unreleased entries, and 10.0.3 contains only intentional release notes.