V29 Gate 10: Accept promoted protocol posture

Make the Gate 10 promotion-readiness checker validate the protocol package posture according to the active pointer, accepting V28/V29 before promotion and V29/V30 after the generated canon commit. Document the promoted posture requirement in the V29 spec family.

Author: geraldarthurdavis

BITCODE_SPEC_V29.md

@@ -277,6 +277,9 @@ The promotion-readiness contract has five parts:
 `packages/protocol/data/state.json` are commercial runtime posture carriers.
 They must align to V28 active / V29 draft during Gate 10 work and be rewritten
 to V29 active / V30 draft by promotion automation.
+The Gate 10 checker is promotion-mode aware: it must accept the V28/V29 package
+posture before the generated canon commit and the V29/V30 package posture after
+the generated canon commit.
 
 Gate 10 does not itself promote `BITCODE_SPEC.txt`.
 It closes when `version/v29` can be pull-requested to `main` and the V29

BITCODE_SPEC_V29_DELTA.md

@@ -202,7 +202,8 @@ Closure acceptance:
 
 - `check:v29-gate10` validates the V29 promotion-readiness surface from a clean
   Gate 10 branch and can run in `--promotion-mode` after `BITCODE_SPEC.txt`
-  advances to `V29`.
+  advances to `V29`, including the promoted V29 active / V30 draft protocol
+  package posture.
 - Gate-quality CI invokes all V29 gate scripts while V29 is still a draft and
   switches to promoted V29 validation after the promotion workflow writes the
   canonical pointer commit.

BITCODE_SPEC_V29_PARITY_MATRIX.md

@@ -313,7 +313,8 @@ Accepted surfaces:
 
 - `scripts/check-v29-gate10-local-staging-promotion-readiness.mjs` validates
   the Gate 10 specification, QA ledger, scripts, workflow wiring, runtime
-  posture, and promotion-mode behavior.
+  posture, and promotion-mode behavior before and after the generated V29/V30
+  protocol package posture rewrite.
 - `.github/workflows/bitcode-gate-quality.yml` runs all V29 gate checks in
   draft posture and switches to promoted V29 checks after the promotion commit.
 - `.github/workflows/bitcode-canon-quality.yml` accepts both V28 active / V29

scripts/check-v29-gate10-local-staging-promotion-readiness.mjs

@@ -193,20 +193,25 @@ function main() {
     'Runtime promotion preparation must update commercial package posture, package data, and package README.',
   );
 
+  const expectedActiveCanon = pointer === 'V29' ? 'V29' : 'V28';
+  const expectedDraftTarget = pointer === 'V29' ? 'V30' : 'V29';
+  const expectedProtocolReadmePosture =
+    pointer === 'V29' ? 'V29` active, `V30` draft after V29 promotion' : 'V28` active, `V29` draft';
+
   assertCheck(
     failures,
-    packageCanonPosture.includes("ACTIVE_CANON_VERSION = 'V28'") &&
-      packageCanonPosture.includes("DRAFT_TARGET_VERSION = 'V29'") &&
-      packageState.includes('"activeCanonVersion": "V28"') &&
-      packageState.includes('"draftTargetVersion": "V29"') &&
-      packageState.includes('"activeProvenAppendixPath": "BITCODE_SPEC_V28_PROVEN.md"') &&
-      packageState.includes('"draftSpecPath": "BITCODE_SPEC_V29.md"'),
-    'Protocol package posture and seed state must be aligned to V28 active / V29 draft before promotion.',
+    packageCanonPosture.includes(`ACTIVE_CANON_VERSION = '${expectedActiveCanon}'`) &&
+      packageCanonPosture.includes(`DRAFT_TARGET_VERSION = '${expectedDraftTarget}'`) &&
+      packageState.includes(`"activeCanonVersion": "${expectedActiveCanon}"`) &&
+      packageState.includes(`"draftTargetVersion": "${expectedDraftTarget}"`) &&
+      packageState.includes(`"activeProvenAppendixPath": "BITCODE_SPEC_${expectedActiveCanon}_PROVEN.md"`) &&
+      packageState.includes(`"draftSpecPath": "BITCODE_SPEC_${expectedDraftTarget}.md"`),
+    `Protocol package posture and seed state must be aligned to ${expectedActiveCanon} active / ${expectedDraftTarget} draft.`,
   );
   assertCheck(
     failures,
-    protocolReadme.includes('V28` active, `V29` draft') && protocolReadme.includes('Gate 10'),
-    'Protocol package README must name the draft posture and Gate 10 promotion boundary.',
+    protocolReadme.includes(expectedProtocolReadmePosture) && protocolReadme.includes('Gate 10'),
+    `Protocol package README must name the ${expectedActiveCanon}/${expectedDraftTarget} posture and Gate 10 promotion boundary.`,
   );
   assertCheck(
     failures,