[Pepps233]

Summary

Verify the migrated updater through actual staging R2 and Worker responses before distributing the client.

All 21 live source CLI canaries passed, with package execution intercepted and every staging fixture cleaned up.

Reasoning

Controlled response tests alone do not establish that deployed storage and HTTP responses produce the intended CLI behavior.

The canaries reuse the existing isolated source CLI harness, remap only the exact production version URL to the fixed staging endpoint, and allow no other socket destination.

Production authority and public contracts remain unchanged.

Changes

• Add an opt-in --client-canaries mode to the staging publisher verifier and a manual workflow input.
• Exercise real terminal startup, missing/newer/equal/older releases, force, offline mode, automatic opt-out, retries, and seven invalid stored-record cases.
• Assert exact canonical npm install arguments without executing install or uninstall.
• Record requests, responses, blocked unrelated install telemetry, cleanup, regression results, and the approved local artifact rebuild and scan.

Testing

• node scripts/verify-release-publication.mjs --staging --client-canaries: all 21 live canaries passed; owned records and shared lock confirmed absent afterward.
• Focused client baseline: 155 tests passed; changed source CLI test file: 32 tests passed.
• npm run check and full isolated ./test.sh: passed.
• Owner-approved npm run build in packages/coding-agent: passed; source and compiled version-check paths contain no old Pi endpoint.
• actionlint 1.7.12 and cross-repository contract/fixture comparisons: passed.
• Cloud and isolated Worker quality gates: passed, including 335 Worker tests.

The workflow becomes dispatchable after reaching the default branch.
This validates source clients with simulated installation; it does not claim published-package installation or authorize production activation.