@kungfu-tech/buildchain 4.0.1-alpha.4 → 4.0.1-alpha.6

package/actions/release-tail/README.md

@@ -11,3 +11,11 @@ not the adapter, compares the observed subject and target roots, owns retry and
 terminal classification, checkpoints state and emits the standardized receipt.
 Tokens remain Action inputs and are never written to the transaction or
 receipt.
+
+When `rehearsal-capsule` is supplied, the same Action switches to the v4
+Publication Rehearsal Capsule boundary. `simulate` and `replay` remain
+effect-disabled. `provider` additionally requires exact capsule-bound
+rehearsal authority, consumes only the capsule-rooted data bindings, and
+records every request/readback while still emitting
+`productionAuthority: false` and no Release Passport. See
+[`docs/v4-publication-rehearsal.md`](../../docs/v4-publication-rehearsal.md).

package/architecture/decisions/0002-next-development-transition.md

@@ -0,0 +1,101 @@
+---
+status: accepted
+period: 2026-08-11
+theme: next-development-transition
+doc_type: architecture-decision-record
+source_level: local-files
+confidence: high
+sensitivity: public
+evidence_grade: A
+review_state: self-reviewed
+last_reviewed: 2026-08-11
+---
+
+# ADR 0002: Alpha Publication and Next-development Are Separate Transactions
+
+## Status
+
+Accepted. This decision is normative for Buildchain promotion controllers and
+for generated consumer guidance.
+
+## Context
+
+An Alpha publication and preparation of the following development version have
+different trust boundaries. Alpha publication establishes public, immutable
+facts about version N. Preparing N+1 changes repository version material and
+may require a protected pull request or an upstream anchor that does not exist
+when Alpha N completes. Treating both operations as one success condition makes
+a post-publication conflict appear to invalidate a publication that already
+succeeded, and encourages retries to move Alpha refs while repairing Dev.
+
+Buildchain supports two legal version models:
+
+- `semver` with `next = "auto"`, where N+1 increments the Alpha sequence on
+  the same semantic patch; and
+- `anchored` with `next = "manual"`, where no version may be inferred before a
+  declared anchor manifest is materialized and rooted.
+
+The crossed combinations `semver/manual` and `anchored/auto` have no defined
+meaning and are rejected.
+
+## Decision
+
+Alpha publication reaches its own terminal success before a next-development
+transition is created. The transition records the completed Alpha exact tag,
+release commit, tree, publication evidence root, and completion time. A
+deterministic idempotency key covers that completed-Alpha root together with
+the repository, legal version model, and the role-separated adapter path set.
+
+The independent next-development state machine is:
+
+```text
+planned ----------------------> materialized -> pr-pending -> merged -> verified
+   \                              \---------------------------> merged
+    -> waiting-anchor ----------> materialized
+```
+
+`semver/auto` derives its target while planned. `anchored/manual` remains in
+`waiting-anchor` until an exact semantic version and the digest of the declared
+anchor manifest are supplied. `pr-pending` is durable incomplete state, not a
+publication failure. Direct materialization may proceed to `merged` or
+`verified` when repository governance does not require a pull request.
+
+Every non-initial state transition is compare-and-swap guarded and rooted in
+explicit evidence. Replaying an identical request is a no-op. Alpha outcome is
+always `preserved-success`; no transition may write an Alpha branch, exact tag,
+or floating tag. A controller that needs to repair next-development state may
+write only paths declared by `version.files` and `version.derived_files`; the
+configured anchor manifest is declared read-only authority.
+
+## Local adapter boundary
+
+The reference adapter is provider-neutral. It reads the checked-in
+`buildchain.toml`, derives the sorted path allowlist, validates the completed
+Alpha and optional anchor, and plans version-file content. It never invokes Git,
+network clients, lifecycle commands, package registries, or provider APIs.
+Mutation requires explicit `--write`, rejects symlinks and path escapes, and is
+limited to configured `version.files`. The standard repository transaction
+adapter passes the exact target in `BUILDCHAIN_VERSION`, permits changes only
+to `version.files` plus `version.derived_files`, runs
+`lifecycle.version-state` when derived files are declared, and then runs
+`lifecycle.verify`. The reference writer fails closed rather than invoking
+those consumer commands because transaction execution is a separate slice.
+For anchored/manual, the consumer must
+materialize the declared manifest first; the adapter verifies its exact digest
+and does not invent or edit upstream anchor data.
+
+Preparing development state alone creates no Git tag, GitHub Release, public
+package, or release candidate.
+
+## Consequences
+
+- A completed Alpha N remains successful when N+1 waits for an anchor, a
+  protected PR, merge, or verification.
+- Retrying development preparation cannot republish Alpha N or change any
+  Alpha ref.
+- Semver and anchored consumers share one lifecycle while retaining their
+  distinct version authority.
+- Provider adapters may project pull-request identifiers and merge evidence,
+  but those observations do not become part of the local mutation authority.
+- Generated config, Agent instructions, and public documentation are checked
+  against the same constants; projection drift fails repository checks.

package/architecture/internal-capabilities.json

@@ -6,6 +6,10 @@
     "bin/internal",
     "packages/core/release-passport.js",
     "packages/core/buildchain-contract.js",
+    "packages/core/kungfu-temporal-fact.js",
+    "packages/core/buildchain-compatibility-fact.js",
+    "packages/core/buildchain-compatibility-authority.js",
+    "packages/core/buildchain-compatibility-proof.js",
     "packages/core/workflow-call-contract.js",
     "packages/core/workflow-yaml-contract.js",
     "packages/core/paper-fleet.js",
@@ -26,6 +30,9 @@
     "packages/core/release-tail-provider-plane.js",
     "packages/core/release-tail-provider-adapters.js",
     "packages/core/release-tail-compatibility.js",
+    "packages/core/v4-publication-rehearsal-capsule.js",
+    "packages/core/v4-publication-rehearsal-provider-bindings.js",
+    "packages/core/v4-publication-rehearsal.js",
     "actions/release-tail/index.js",
     "scripts/authorize-promotion-runtime-override.cjs",
     "scripts/build-contract-core.mjs",
@@ -50,6 +57,12 @@
     "crates/buildchain-v4-bridge/src/main.rs",
     "packages/core/v4-runtime-ref-resume-authority.js",
     "packages/core/v4-runtime-selector-persistence.js",
+    "packages/core/v4-tail-reseal-contract.js",
+    "packages/core/v4-tail-reseal.js",
+    "packages/core/v4-tail-reseal-github.js",
+    "packages/core/v4-tail-reseal-receipt.js",
+    "scripts/v4-tail-reseal.mjs",
+    "scripts/v4-tail-reseal-macos-rehearsal.mjs",
     "packages/core/v4-provider-operation-journal.js",
     "packages/core/v4-stage-capsule.js",
     "packages/core/v4-stage-capsule-store.js",
@@ -105,8 +118,20 @@
     "crates/buildchain-v4-contracts/src/stable_publication_fence.rs",
     "packages/core/v4-partial-mutation-recovery-qualification.js",
     "crates/buildchain-v4-contracts/src/partial_mutation_recovery.rs",
+    "packages/core/adopter-delivery-gate.js",
+    "packages/core/adopter-delivery-passport.js",
+    "packages/core/adopter-delivery-vectors.js",
+    "packages/core/buildchain-delivery-bootstrap.js",
+    "packages/core/buildchain-delivery-infrastructure.js",
+    "packages/core/buildchain-delivery-self-dogfood.js",
+    "packages/core/kfd-adopter-category-driver.js",
+    "packages/core/legacy-kfd-adopter-driver.js",
+    "packages/core/published-delivery-authority.js",
+    "packages/core/v4-adopter-delivery.js",
     "packages/core/v4-adopter-delivery-parity.js",
-    "crates/buildchain-v4-contracts/src/adopter_delivery.rs"
+    "crates/buildchain-v4-contracts/src/adopter_delivery.rs",
+    "crates/buildchain-v4-contracts/src/compatibility_facts.rs",
+    "crates/buildchain-v4-contracts/src/compatibility_facts"
   ],
   "ownershipRules": [
     {
@@ -450,6 +475,22 @@
         "docs/release-tail-provider-plane.md"
       ]
     },
+    {
+      "id": "v4-publication-rehearsal",
+      "owner": "Buildchain publication rehearsal maintainers",
+      "implementation": [
+        "packages/core/v4-publication-rehearsal-capsule.js",
+        "packages/core/v4-publication-rehearsal-provider-bindings.js",
+        "packages/core/v4-publication-rehearsal.js"
+      ],
+      "tests": ["tests/v4-publication-rehearsal.test.mjs"],
+      "contracts": [
+        "architecture/v4-publication-rehearsal-parity.json",
+        "contracts/v4-publication-rehearsal-capsule-v1.schema.json",
+        ".github/workflows/v4-publication-rehearsal-dogfood.yml",
+        "docs/v4-publication-rehearsal.md"
+      ]
+    },
     {
       "id": "v4-delivery-authority",
       "owner": "Buildchain protected delivery maintainers",
@@ -512,6 +553,65 @@
         "docs/dev-delivery-qualification-landing-adr.md"
       ]
     },
+    {
+      "id": "v4-compatibility-facts",
+      "owner": "Buildchain compatibility authority maintainers",
+      "implementation": [
+        "bin/internal/compatibility-facts-cli.mjs",
+        "packages/core/kungfu-temporal-fact.js",
+        "packages/core/buildchain-compatibility-fact.js",
+        "packages/core/buildchain-compatibility-authority.js",
+        "packages/core/buildchain-compatibility-proof.js",
+        "crates/buildchain-v4-contracts/src/compatibility_facts.rs",
+        "crates/buildchain-v4-contracts/src/compatibility_facts/encoding.rs",
+        "crates/buildchain-v4-contracts/src/compatibility_facts/fixture.rs",
+        "crates/buildchain-v4-contracts/src/compatibility_facts/lifecycle.rs",
+        "crates/buildchain-v4-contracts/src/compatibility_facts/verifier.rs"
+      ],
+      "tests": ["tests/v4-compatibility-facts.test.mjs"],
+      "contracts": [
+        "architecture/v4-compatibility-facts-parity.json",
+        "contracts/v4-compatibility-facts-v1.schema.json",
+        "contracts/fixtures/v4-compatibility-facts-v1/shared.json",
+        "dist/site/schemas/v4-compatibility-facts-v1.schema.json",
+        "docs/v4-compatibility-facts.md"
+      ]
+    },
+    {
+      "id": "v4-adopter-delivery",
+      "owner": "Buildchain adopter delivery maintainers",
+      "implementation": [
+        "bin/internal/adopter-delivery-cli.mjs",
+        "packages/core/adopter-delivery-gate.js",
+        "packages/core/adopter-delivery-passport.js",
+        "packages/core/adopter-delivery-vectors.js",
+        "packages/core/buildchain-delivery-bootstrap.js",
+        "packages/core/buildchain-delivery-infrastructure.js",
+        "packages/core/buildchain-delivery-self-dogfood.js",
+        "packages/core/kfd-adopter-category-driver.js",
+        "packages/core/legacy-kfd-adopter-driver.js",
+        "packages/core/published-delivery-authority.js",
+        "packages/core/v4-adopter-delivery.js",
+        "packages/core/v4-adopter-delivery-parity.js",
+        "crates/buildchain-v4-contracts/src/adopter_delivery.rs"
+      ],
+      "tests": [
+        "tests/v4-adopter-delivery.test.mjs",
+        "tests/v4-adopter-delivery-parity.test.mjs"
+      ],
+      "contracts": [
+        "architecture/v4-adopter-delivery-parity.json",
+        "contracts/v4-adopter-delivery-v1.schema.json",
+        "contracts/fixtures/v4-adopter-delivery-v1/archive-template.json",
+        "contracts/fixtures/v4-adopter-delivery-v1/bootstrap-positive.json",
+        "contracts/fixtures/v4-adopter-delivery-v1/gate-positive.json",
+        "contracts/fixtures/v4-adopter-delivery-v1/gate-unknown-selector.json",
+        "contracts/fixtures/v4-adopter-delivery-v1/offline-vectors.json",
+        ".github/workflows/v4-adopter-delivery.yml",
+        ".github/workflows/v4-adopter-delivery-dogfood.yml",
+        "docs/v4-adopter-delivery.md"
+      ]
+    },
     {
       "id": "v4-architecture-governance",
       "owner": "Buildchain architecture maintainers",
@@ -526,9 +626,14 @@
         "packages/core/v4-release-activation-shadow.js",
         "packages/core/v4-stable-publication-fence.js",
         "packages/core/v4-partial-mutation-recovery-qualification.js",
-        "packages/core/v4-adopter-delivery-parity.js",
         "packages/core/v4-runtime-ref-resume-authority.js",
         "packages/core/v4-runtime-selector-persistence.js",
+        "packages/core/v4-tail-reseal-contract.js",
+        "packages/core/v4-tail-reseal.js",
+        "packages/core/v4-tail-reseal-github.js",
+        "packages/core/v4-tail-reseal-receipt.js",
+        "scripts/v4-tail-reseal.mjs",
+        "scripts/v4-tail-reseal-macos-rehearsal.mjs",
         "packages/core/v4-stage-capsule.js",
         "packages/core/v4-stage-capsule-store.js",
         "packages/core/v4-stage-capsule-local-store.js",
@@ -546,8 +651,7 @@
         "crates/buildchain-v4-contracts/src/release_activation_shadow/model.rs",
         "crates/buildchain-v4-contracts/src/release_activation_shadow/journal.rs",
         "crates/buildchain-v4-contracts/src/stable_publication_fence.rs",
-        "crates/buildchain-v4-contracts/src/partial_mutation_recovery.rs",
-        "crates/buildchain-v4-contracts/src/adopter_delivery.rs"
+        "crates/buildchain-v4-contracts/src/partial_mutation_recovery.rs"
       ],
       "tests": [
         "tests/v4-architecture.test.mjs",
@@ -561,8 +665,9 @@
         "tests/v4-stage-capsule-store.test.mjs",
         "tests/v4-platform-stage-checkpoints.test.mjs",
         "tests/v4-stage-capsule-qualification.test.mjs",
-        "tests/v4-adopter-delivery-parity.test.mjs",
-        "tests/v4-runtime-ref-resume-authority.test.mjs"
+        "tests/v4-runtime-ref-resume-authority.test.mjs",
+        "tests/v4-tail-reseal.test.mjs",
+        "tests/v4-tail-reseal-parity.test.mjs"
       ],
       "contracts": [
         "architecture/v4-architecture-constitution.md",
@@ -579,7 +684,6 @@
         "architecture/v4-stage-capsule-store-contract.json",
         "architecture/v4-platform-stage-checkpoints.json",
         "architecture/v4-stage-capsule-qualification.json",
-        "architecture/v4-adopter-delivery-parity.json",
         "architecture/v4-runtime-ref-resume-authority.json",
         "contracts/v4-host-contract-v1.schema.json",
         "contracts/v4-provider-operation-journal-v1.schema.json",
@@ -597,8 +701,13 @@
         "contracts/fixtures/v4-partial-mutation-recovery-v1/shared.json",
         "contracts/v4-runtime-ref-resume-authority-v1.schema.json",
         "contracts/fixtures/v4-runtime-ref-resume-authority-v1/scenario.json",
+        "architecture/v4-tail-reseal-parity.json",
+        "contracts/v4-tail-reseal-v1.schema.json",
+        "contracts/fixtures/v4-tail-reseal-v1/valid.json",
+        ".github/workflows/v4-tail-reseal.yml",
         "docs/v4-stage-capsule.md",
-        "docs/v4-runtime-ref-resume-authority.md"
+        "docs/v4-runtime-ref-resume-authority.md",
+        "docs/v4-tail-reseal.md"
       ]
     }
   ]

package/architecture/maintainability-policy.json

@@ -5,12 +5,13 @@
   "enforcementRevision": "5308189b09bcb5a1314195412f2807a40d678838",
   "repositoryBudgets": {
     "baselineRevision": "c70e6ac28431888b24fefc218246cc69f8dde85a",
-    "maxHandMaintainedSourceFiles": 384,
-    "maxHandMaintainedSourceLines": 146550,
-    "maxWorkflowFiles": 71,
-    "maxWorkflowLines": 25259,
-    "latestTransition": "Delivery authority now migrates a rechecked live v1 ref with the configured v2 policy, rejects GitHub artifact runtime credentials in candidate ancestry, binds containment comparison to the exact protected-base head, and keeps v2 migration promises out of the v1 workflow contract.",
-    "rationale": "Bounded modules separate candidate, evidence, native proof and execution, canonical failure verification, closed-set execution transfer, process-boundary verification, Warrant state and qualification, authority state, qualification, Landing acquisition, verified-attempt admission, Landing settlement and fence validation, provider attempt and heartbeat readback, sealed terminal evidence, hosted heartbeat, resume, store, options, command-specific adapters, and CLI orchestration responsibilities. The protected delivery workflow gives candidate and seal jobs no provider write credential, recursively rejects transfer drift, scopes every transfer artifact to the exact provider run attempt, chains every durable heartbeat state and receipt root on a distinct hosted runner domain, and permits qualification or exact failure settlement only after the finalizer verifies live jobs and the latest durable authority state. Public Landing admission and heartbeat always perform non-injectable fresh exact-attempt provider readback, and heartbeat-loss coordination never invokes GitHub's run-scoped cancellation API where a successor rerun could race. V2 mutation cannot initialize a second empty authority beside a legacy ref: migration reads and roots the canonical live v1 ref, rechecks it, applies the explicit configured v2 policy, and atomically replaces its bytes through one expected-old non-force update, so old v1 controllers fail closed while the prior commit remains immutable history. Candidate ancestry classifies the GitHub artifact runtime token as credential authority. Every Landing settlement, including an unexpired fence, requires product-owned terminal readback. Terminal cleanup reads the immutable historical attempt, derives workflow and hosted Landing job identity from live run data, reads the exact protected ref head and compares containment against that immutable SHA, and seals merged only when the admitted merge-group head is contained by that protected base; a later different-head merge settles the old attempt as dequeued. Terminal normalization preserves transfer, finalizer boundary, native and seal job, admitted provider attempt, protected-base head, containment result, and terminal readback coordinates. The public reusable workflow truthfully retains its single-flight v1 authority without advertising v2 migration, while bounded v2 remains a separate opt-in CLI, Node API, and schema contract; the tracked self-caller stays on public v4-alpha with matching stable and alpha locks, and transient train selection is dispatch-only. These exact 384-file, 146550-source-line and 25259-workflow-line ceilings cannot grow implicitly."
+    "maxHandMaintainedSourceFiles": 422,
+    "maxHandMaintainedSourceLines": 158836,
+    "maxWorkflowFiles": 75,
+    "maxWorkflowLines": 25983,
+    "latestTransition": "Floating Alpha bootstrap routes only automatic Alpha self-promotion through the protected Alpha private shell while the old floating shell cannot carry its own repair; stable promotion remains on the public v4 wrapper.",
+    "latestTransitionRationale": "One credentialless resolver reuses the published promotion identity authority to bind the floating router and runtime, protected Alpha shell, and exact Alpha lock digest before that shell independently reproduces the external consumer-policy certification. The bounded route adds no manual publication, tag, ref, npm, stable, or public-consumer authority and is removed after the protected workflow promotion advances v4-alpha. These exact 422-file, 158836-source-line, 75-workflow-file and 25983-workflow-line ceilings add no unreviewed headroom or function-budget widening.",
+    "rationale": "Bounded modules separate candidate, evidence, native proof and execution, canonical failure verification, closed-set execution transfer, process-boundary verification, Warrant state and qualification, authority state, qualification, Landing acquisition, verified-attempt admission, Landing settlement and fence validation, provider attempt and heartbeat readback, sealed terminal evidence, hosted heartbeat, resume, store, options, command-specific adapters, and CLI orchestration responsibilities. The protected delivery workflow gives candidate and seal jobs no provider write credential, recursively rejects transfer drift, scopes every transfer artifact to the exact provider run attempt, chains every durable heartbeat state and receipt root on a distinct hosted runner domain, and permits qualification or exact failure settlement only after the finalizer verifies live jobs and the latest durable authority state. Public Landing admission and heartbeat always perform non-injectable fresh exact-attempt provider readback, tolerate only a not-yet-materialized seal job while retaining exact native and duplicate-job rejection, and heartbeat-loss coordination never invokes GitHub's run-scoped cancellation API where a successor rerun could race. The hosted process boundary anchors trust in the kernel-resolved versioned Runner.Worker path while accepting an equivalent argv-zero spelling with the same basename; its public boundary marker is allowed only at the one exact non-secret value, so a forged value under the same credential-like name still fails closed. The credentialless transfer seal validates the rooted native reuse decision against the Warrant-bound source, closure, dependency, toolchain, environment and command inputs; qualifiedBase stays in the proof and decision where it is rooted and later independently rechecked, rather than being assumed on the Warrant schema. V2 mutation cannot initialize a second empty authority beside a legacy ref: migration reads and roots the canonical live v1 ref, rechecks it, applies the explicit configured v2 policy, and atomically replaces its bytes through one expected-old non-force update, so old v1 controllers fail closed while the prior commit remains immutable history. Candidate ancestry classifies the GitHub artifact runtime token as credential authority. Every Landing settlement, including an unexpired fence, requires product-owned terminal readback. Terminal cleanup reads the immutable historical attempt, derives workflow and hosted Landing job identity from live run data, reads the exact protected ref head and compares containment against that immutable SHA, and seals merged only when the admitted merge-group head is contained by that protected base; a later different-head merge settles the old attempt as dequeued. Terminal normalization preserves transfer, finalizer boundary, native and seal job, admitted provider attempt, protected-base head, containment result, and terminal readback coordinates. The public reusable workflow truthfully retains its single-flight v1 authority without advertising v2 migration, while bounded v2 remains a separate opt-in CLI, Node API, and schema contract; the tracked self-caller stays on public v4-alpha with matching stable and alpha locks, and transient train selection is dispatch-only. Next-development parity adds one versioned transition authority, one durable controller, one bounded reservation adapter, and pure public-contract recovery evidence while retaining the existing thin floating-channel callers byte-for-byte. The floating-consumer gate reuses the existing contract-world evaluator so SHA drift passes only under the selected lock's compatibility policy, breaking surface drift still fails closed, and external certification reconstructs the receipt from the observed workflow SHA rather than the lock's historical evidence SHA. Tail reseal adds no Stage Capsule effect or general rebuild authority: it verifies the exact retained four-platform bytes, admits one known macOS tail failure through live provider readback, fences signing and finalization to explicit credentials and Warrant identity, and requires standard candidate Passport plus provider and protected readback. Compatibility Facts parity isolates canonical encoding, temporal verification, lifecycle validation, fixture projection, public authority projection, and CLI adaptation into bounded modules; legacy digest and proof arrays are derived only from exact current Fact lineage. Publication Rehearsal adds no production release authority: the content-addressed capsule contract binds source, candidate, manifest, config, canonical data-only provider bindings, provider policy, observations and core version separately from filesystem, runtime and rehearsal-only provider authority; simulate, replay and explicitly authorized provider rehearsal all reuse the release-tail planner, while same-commit local dogfood resolves the new reusable contract and exact current runtime before external callers remain on floating v4-alpha. Cross-runtime candidate recovery preserves original runtime and provider roots and creates resume lineage only after exact public ref, tag, ancestry, npm version and integrity readback. Adopter Delivery restores the reviewed public v3 gate, drivers, Passport binding, N-1 bootstrap and exact archive loader through one public v4 surface while keeping provider and release authority explicit non-claims. Floating Alpha bootstrap uses only the existing exact resolver and protected Alpha private shell to move an otherwise stale floating shell, retains public v4 stable promotion, and removes itself after protected readback. These exact 422-file, 158836-source-line, 75-workflow-file and 25983-workflow-line ceilings cannot grow implicitly."
   },
   "sourceBudgets": {
     "newFileLines": 600,
@@ -19,9 +20,21 @@
     "existingDebtPolicy": "no-widening"
   },
   "approvedNewFileTransitions": {
+    "packages/core/next-development-transition.js": {
+      "maxLines": 738,
+      "rationale": "The single versioned authority keeps completed-Alpha identity, legal successor models, role-separated adapter bounds, materialization roots, compare-and-swap transitions and deterministic replay validation together. Anchored and manual initial state persists as waiting-anchor after reviewed input and exposes rooted anchor binding plus controller materialization recording; this exact reviewed ceiling cannot grow implicitly."
+    },
+    "packages/core/next-development-controller.js": {
+      "maxLines": 728,
+      "rationale": "The durable controller keeps atomic child identity, rooted checkpoints, idempotent materialization operations, latest protected Dev revalidation, PR settlement and exact source and derived root readback in one provider-neutral authority. It exposes no Alpha publication effect and resumes only through injected atomic store and executor boundaries; this exact reviewed ceiling cannot grow implicitly."
+    },
+    "actions/promote-buildchain-ref/internal/promote-alpha-channel.js": {
+      "maxLines": 599,
+      "rationale": "The extracted Alpha promotion stage replaces the former non-fast-forward skip with the existing exact-current-Dev regeneration contract, protected PR fallback, and fail-closed workspace binding; this exact reviewed ceiling cannot grow implicitly."
+    },
     "scripts/dev-delivery-source-proof-reuse.mjs": {
       "maxLines": 631,
-      "rationale": "The bounded source-proof driver seals one exact PR qualification and verifies either the reviewed two-parent merge or GitHub's exact linear replay by base ancestry, commit count and every intermediate tree. Unknown, nonlinear, extra-commit or tree-drift compositions still fail closed to the full lifecycle, and this exact file ceiling cannot grow implicitly."
+      "rationale": "The bounded source-proof driver seals one exact PR qualification and delegates merge-group graph verification to the isolated exact-patch replay module. Unknown, nonlinear, extra-commit, patch-drift or base-divergent compositions still fail closed to the full lifecycle, and this exact file ceiling cannot grow implicitly."
     },
     "scripts/dev-pr-prequeue-guard.mjs": {
       "maxLines": 399,
@@ -84,6 +97,10 @@
     "packages/core/v4-runtime-selector-persistence.js": {
       "maxLines": 228,
       "rationale": "The isolated source scanner rejects persisted exact, train, authority, variable, secret, and environment selector authority while inventorying OIDC, IAM, and external authority metadata without reading credentials; this exact ceiling cannot grow implicitly."
+    },
+    "scripts/resume-from-candidate-run.mjs": {
+      "maxLines": 1125,
+      "rationale": "The candidate recovery adapter retains the existing artifact normalization and immutable recovery receipt boundary while adding fresh authorized cross-runtime Stage Capsule resume material, post-publication ref, tag, ancestry, and npm readback, and rooted Release Passport lineage. Its main orchestration remains below the default function length and complexity limits, and this exact file ceiling cannot grow implicitly."
     }
   },
   "approvedExistingDebtTransitions": {
@@ -92,8 +109,8 @@
       "rationale": "The public facade forwards the reviewed runtime-resume authority beside the existing declarative release-tail and v4 governance APIs without adding a second implementation or execution path; this exact post-integration ceiling cannot grow implicitly."
     },
     "actions/promote-buildchain-ref/index.js": {
-      "maxFunctionLines": 276,
-      "rationale": "The existing action entrypoint forwards one optional rooted v4 runtime-resume evidence document into the already audited durable Passport operation; this one-line terminal widening is exact and cannot grow implicitly."
+      "maxFunctionLines": 280,
+      "rationale": "The existing action entrypoint forwards the optional rooted v4 runtime-resume material and its trusted post-publication finalizer into the audited durable Passport operation. The exact readable four-line input widening cannot grow implicitly."
     },
     "actions/promote-buildchain-ref/lib.js": {
       "maxLines": 6952,
@@ -104,9 +121,9 @@
       "rationale": "The runtime entrypoint now binds every compatibility command and alias, including the upstream paper command, through the tested command registry; this exact post-integration wiring ceiling cannot grow implicitly."
     },
     "packages/core/release-passport.js": {
-      "maxLines": 2958,
+      "maxLines": 2976,
       "maxFunctionLines": 304,
-      "rationale": "Responsibility-owned validators preserve issue ordering, byte-stable reports, upstream release evidence, consumer-policy certification, and the new rooted runtime A+B resume lineage. The optional attachment is normalized and independently reverified before inclusion; these exact post-integration ceilings cannot grow implicitly."
+      "rationale": "Responsibility-owned validators preserve issue ordering, byte-stable reports, upstream release evidence, consumer-policy certification, and rooted runtime A+B resume lineage. Tree-equivalent promotion keeps the original built source identity while the optional attachment is normalized and independently reverified before inclusion; these exact post-integration ceilings cannot grow implicitly."
     },
     "packages/core/buildchain-contract.js": {
       "maxLines": 1096,
@@ -119,8 +136,8 @@
       "rationale": "The publication authority now declares the alpha/v4/v4.0 and release/v4/v4.0 protected channels required for the v4 public train. This exact two-line channel transition cannot grow implicitly."
     },
     "packages/core/buildchain-config.js": {
-      "maxLines": 1806,
-      "rationale": "Artifact signing configuration admits only the Buildchain-owned JIT profile with exact safe archive-relative target paths while rejecting credentials, entitlement files, wildcard paths, incompatible artifact kinds, and incomplete declarations; this exact wiring ceiling cannot grow implicitly."
+      "maxLines": 1885,
+      "rationale": "Artifact signing configuration admits only the Buildchain-owned JIT profile with exact safe archive-relative target paths while rejecting credentials, entitlement files, wildcard paths, incompatible artifact kinds, and incomplete declarations. Publication rehearsal remains effect-disabled. Adopter delivery adds only a closed public contract, exact selectors and repository-relative input, readback, bootstrap, archive and result paths; this exact wiring ceiling cannot grow implicitly."
     },
     "scripts/check-internal-architecture.mjs": {
       "maxFunctionComplexity": 37,
@@ -131,8 +148,8 @@
       "rationale": "The new-file budget evaluator recognizes only explicit path-scoped transitions with exact ceilings and mandatory rationales; the default budget and every existing no-widening check remain unchanged."
     },
     "scripts/check-inventory.mjs": {
-      "maxLines": 1486,
-      "rationale": "Inventory retains the recovery, sealed-bundle, no-product-install, and durable-finalization checks, requires the self-dogfood lock to match the current major, and binds every channel-router lane to the exact caller shell without unresolved static channel refs. This exact post-integration ceiling cannot grow implicitly."
+      "maxLines": 1497,
+      "rationale": "Inventory retains the complete recovery and publication authority set and additionally requires both bounded next-development self-dogfood command and harness files beside the contract, controller, schemas, fixtures, adapter, generated guidance and public documentation; this exact post-integration ceiling cannot grow implicitly."
     },
     "scripts/generate-channel-promotion-workflow.mjs": {
       "maxFunctionLines": 290,
@@ -149,8 +166,8 @@
       "rationale": "The existing Gate validator admits an explicit bounded long-form duration class while preserving the standard 60-second default and exact capture-to-scene binding; this exact post-integration ceiling cannot grow implicitly."
     },
     "scripts/dev-alpha-candidate-patrol.mjs": {
-      "maxLines": 1184,
-      "rationale": "The existing single-flight exact-source Alpha controller now idempotently registers repository-selected GitHub auto-merge intent only after settlement revalidation, with explicit merge-method validation and no direct merge or approval path; this exact ceiling cannot grow implicitly."
+      "maxLines": 1197,
+      "rationale": "The existing single-flight exact-source Alpha controller delegates next-development reservation validation to the bounded core reader, carries the rooted result into selection, and retains the no-publication boundary; this exact ceiling cannot grow implicitly."
     },
     "scripts/build-contract-core.mjs": {
       "maxLines": 1229,
@@ -287,6 +304,7 @@
           "release-passport-promotion-routing-json",
           "release-passport-v4-consumer-policy-certification-json",
           "release-passport-v4-consumer-policy-certification-root",
+          "release-passport-v4-runtime-resume-evidence-command",
           "release-passport-v4-runtime-resume-evidence-json",
           "release-tail-state-path",
           "require-governance",
@@ -304,7 +322,7 @@
         "secrets": [],
         "outputs": []
       },
-      "rationale": "The promote action preserves the independently rooted v4 consumer-policy certification and now accepts one optional verified runtime-resume evidence document for final Release Passport construction; v3 behavior remains unchanged."
+      "rationale": "The promote action preserves the independently rooted v4 consumer-policy certification and accepts one optional verified runtime-resume evidence document plus one trusted post-publication finalizer command. The command runs only inside the existing durable Passport finalization boundary after provider effects and public readback; v3 behavior remains unchanged."
     },
     "cli:architecture": {
       "fromRevision": "5308189b09bcb5a1314195412f2807a40d678838",
@@ -1494,9 +1512,9 @@
       "rationale": "The existing version-state commit transaction remains nested under its extracted operation factory and is independently regression-tested; this exact inherited ceiling cannot grow."
     },
     "actions/promote-buildchain-ref/internal/durable-transaction-operations.js#createDurableTransactionOperations": {
-      "maxLines": 376,
+      "maxLines": 378,
       "maxComplexity": 1,
-      "rationale": "Transplanted legacy durable transaction and Passport operations now live in an independently owned module; one semantic durable-material seam lets already-proven contained finalization restore immutable publication facts without accepting a transient rebuilt candidate or inconsistent per-field overrides, and this exact inherited ceiling cannot grow."
+      "rationale": "Transplanted legacy durable transaction and Passport operations remain in one independently owned module. The exact two-line readable widening forwards rooted runtime-resume material and its post-publication finalizer without accepting a transient rebuilt candidate or inconsistent per-field overrides; this ceiling cannot grow implicitly."
     },
     "packages/core/paper-npm-bootstrap.js#executePaperNpmBootstrap": {
       "maxLines": 490,

package/architecture/release-tail-contract-inventory.json

@@ -41,6 +41,7 @@
       "release-passport-evidence-command",
       "release-passport-invariant-passport-command",
       "release-passport-kfd-3-artifact-verify-command",
+      "release-passport-v4-runtime-resume-evidence-command",
       "verification-command"
     ],
     "configAndCliAliases": [
@@ -286,7 +287,8 @@
       "publicNames": [
         "release-passport-kfd-3-artifact-verify-command",
         "release-passport-invariant-passport-command",
-        "release-passport-attachment-command"
+        "release-passport-attachment-command",
+        "release-passport-v4-runtime-resume-evidence-command"
       ],
       "aliases": [
         {
@@ -306,7 +308,8 @@
         "action:actions/promote-buildchain-ref/action.yml#release-passport-kfd-3-artifact-verify-command",
         "action:actions/promote-buildchain-ref/action.yml#release-passport-invariant-passport-command",
         "action:actions/promote-buildchain-ref/action.yml#release-passport-attachment-command",
-        "action:actions/promote-buildchain-ref/action.yml#release-passport-evidence-command"
+        "action:actions/promote-buildchain-ref/action.yml#release-passport-evidence-command",
+        "action:actions/promote-buildchain-ref/action.yml#release-passport-v4-runtime-resume-evidence-command"
       ],
       "executionSites": [
         {

package/architecture/v3-core-mechanism-inventory.json

@@ -69,6 +69,11 @@
         "root": "packages/core",
         "pattern": "^release-activation-transaction\\.js$"
       },
+      {
+        "mechanismId": "next-development-controller",
+        "root": "packages/core",
+        "pattern": "^next-development-(?:transition|controller|candidate-reservation)\\.js$"
+      },
       {
         "mechanismId": "publication-authority",
         "root": "packages/core",
@@ -130,6 +135,90 @@
     "orphanPolicy": "Every state-bearing mechanism must own source, tests, public surfaces, durable-store disposition, recovery, and v4 migration disposition; missing or ambiguous ownership fails validation."
   },
   "mechanisms": [
+    {
+      "id": "next-development-controller",
+      "owner": "Buildchain protected development version plane",
+      "writers": [
+        "completed Alpha terminal-success schedulers",
+        "packages/core/next-development-controller.js"
+      ],
+      "schemas": [
+        "kungfu-buildchain-next-development-transition/v1",
+        "kungfu-buildchain-next-development-controller/v1"
+      ],
+      "stores": [
+        "atomic child store keyed by repository and completed-Alpha root",
+        "compare-and-swap rooted controller checkpoints"
+      ],
+      "states": [
+        "planned",
+        "waiting-anchor",
+        "materialized",
+        "pr-pending",
+        "merged",
+        "verified"
+      ],
+      "events": [
+        "schedule",
+        "bind-reviewed-anchor",
+        "materialize-current-dev",
+        "open-protected-version-pr",
+        "record-merge",
+        "verify-protected-dev-readback"
+      ],
+      "transitions": [
+        "one completed Alpha creates or reuses one deterministic durable child",
+        "stale Dev material is superseded before protected delivery",
+        "merged reaches verified only after exact source and derived root readback"
+      ],
+      "recovery": [
+        "fresh runners load the durable child and resume the last rooted checkpoint",
+        "idempotent materialization operation keys reuse effects after lost responses"
+      ],
+      "effects": [
+        "declared source and derived version material",
+        "protected Dev version pull request"
+      ],
+      "retry": [
+        "Dev movement supersedes only the stale materialization attempt",
+        "readback mismatch remains merged and retries observation without rebuilding"
+      ],
+      "invalidation": [
+        "completed Alpha identity drift",
+        "undeclared changed path",
+        "durable compare-and-swap conflict",
+        "protected Dev version or root disagreement"
+      ],
+      "providerReadback": [
+        "latest protected Dev SHA",
+        "protected version PR status",
+        "protected Dev ancestry, target version, source roots, and derived roots"
+      ],
+      "publicSurfaces": [
+        "cli:next-development",
+        "export:./next-development-transition",
+        "export:./next-development-controller",
+        "export:./next-development-projection"
+      ],
+      "compatibilityCallers": [
+        "v4 completed-Alpha schedulers through the atomic store and executor interfaces"
+      ],
+      "sourcePaths": [
+        "packages/core/next-development-transition.js",
+        "packages/core/next-development-controller.js",
+        "packages/core/next-development-candidate-reservation.js"
+      ],
+      "testPaths": [
+        "tests/next-development-transition.test.mjs",
+        "tests/next-development-controller.test.mjs",
+        "tests/dev-alpha-candidate-patrol.test.mjs",
+        "tests/next-development-self-dogfood.test.mjs"
+      ],
+      "migrationDisposition": "v4-authoritative-with-public-consumer-lifecycle-proof",
+      "unresolved": [
+        "provider-specific durable-store retention and workflow wake policy remain caller-owned integration choices"
+      ]
+    },
     {
       "id": "dev-delivery-warrant",
       "owner": "Buildchain Dev delivery control plane",