V46 Gate 8: Promotion Readiness And Canon Workflow

[geraldarthurdavis]

Summary

• adds package-backed V46 promotion readiness report generation and checking
• wires V46 PROVEN generation support, promotion scripts, and v46-canon-promotion workflow
• updates V46 spec family, roadmap, README surfaces, and shared gate/canon workflows for V45 active / V46 draft and V46 active / V47 draft postures

Validation

• pnpm run check:v46-promotion-readiness
• pnpm run check:v46-gate8
• pnpm run check:v46-local-interface-comprehension-rehearsal
• pnpm --dir packages/protocol exec node --test --test-force-exit test/v46-local-interface-comprehension-rehearsal.test.js
• pnpm --dir packages/protocol exec node --test --test-force-exit test/v46-promotion-readiness.test.js
• pnpm --filter @bitcode/protocol typecheck
• pnpm --filter @bitcode/protocol test
• node scripts/generate-bitcode-proven.mjs --version V46 --commit HEAD --generated-at 2026-06-02T00:00:00.000Z --worktree-state dirty-preview --output BITCODE_SPEC_V46_PROVEN.md --allow-dirty --check
• node scripts/promote-bitcode-canon.mjs --version V46 --commit HEAD --dry-run
• git diff --check

[vercel]

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

Project	Deployment	Actions	Updated (UTC)
engi-uapi	Ready	Preview, Comment	Jun 2, 2026 12:52pm

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: bf749c12c7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Rewrite V46 draft prose during promotion

When the V46 promotion path runs, this branch only updates status-table fields before returning. I checked the promotion preparation in a detached worktree, and the resulting promoted files still contain body text such as V46 does not replace V45 as active canon until promotion workflow validation in BITCODE_SPEC_V46.md and draft-only/current-authority-V45 language in the parity matrix, so the promotion workflow would commit a self-contradictory canon. Add V46 body/parity rewrites here, similar to the custom V45 promotion rewrite, so promoted V46 no longer describes itself as a draft over V45.

Useful? React with 👍 / 👎.