V44 Gate 10: Canonical Input Artifact Inventory#202
Conversation
Adds V43 and V44 to the canonical input artifact resolver so active-canon checks cover the generated proof inventories instead of reporting zero artifacts. Refreshes the V43 generated canonical input/proven artifacts and the V44 promotion-readiness artifact, and updates the demonstration test expectations to match the promoted artifact inventory. Validation: node scripts/check-bitcode-canonical-inputs.mjs --current-target V43; npm --prefix protocol-demonstration test; pnpm --filter @bitcode/protocol test; pnpm --filter @bitcode/protocol typecheck; node scripts/check-v44-gate10-promotion-readiness.mjs --promotion-mode --skip-branch-check --skip-package-tests; node scripts/generate-bitcode-proven.mjs --version V43 --commit "b29e088ba95c33a62247ff4e80b3ca09ff7a6b1c" --worktree-state clean --output BITCODE_SPEC_V43_PROVEN.md --check --allow-dirty; git diff --check.
|
The latest updates on your projects. Learn more about Vercel for GitHub.
|
There was a problem hiding this comment.
💡 Codex Review
https://github.com/engineeredsoftware/ENGI/blob/14d9477714be722db85c412927e393ec3496e001/packages/protocol/src/canonical/v21-specifying.js#L494-L498
Include posture drift artifacts in required inputs
When the V43/V44 canonical input checks run, these newly added version blocks are the generated-artifact inventory used after the two base reports, but they omit .bitcode/v43-canon-posture-drift-report.json and .bitcode/v44-canon-posture-drift-report.json. Both specs' exact generated-artifact inventory matrices mark those drift reports as draft-required, and the proven generator emits them, so a missing posture-drift report can now be silently accepted by check-bitcode-canonical-inputs during active V43 validation or V44 promotion.
ℹ️ 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".
Summary
Validation
node scripts/check-bitcode-canonical-inputs.mjs --current-target V43npm --prefix protocol-demonstration testpnpm --filter @bitcode/protocol testpnpm --filter @bitcode/protocol typechecknode scripts/check-v44-gate10-promotion-readiness.mjs --promotion-mode --skip-branch-check --skip-package-testsnode scripts/generate-bitcode-proven.mjs --version V43 --commit "$(git rev-parse HEAD)" --worktree-state clean --output BITCODE_SPEC_V43_PROVEN.md --check --allow-dirtygit diff --check