@kungfu-tech/buildchain 4.1.3-alpha.2 → 4.1.3-alpha.3

package/architecture/action-taxonomy.json

@@ -353,6 +353,14 @@
             "apply",
             "settle"
           ]
+        },
+        "version": {
+          "responsibility": "Regenerate declared version data in credentialless product jobs and materialize independently qualified publication or development sources.",
+          "operations": [
+            "build",
+            "materialize-publication",
+            "materialize-development"
+          ]
         }
       }
     },

package/architecture/agent-change-map.md

@@ -1052,6 +1052,7 @@ Owner: Buildchain consumer contract maintainers
 - `packages/core/consumer/contract/inspection.js`
 - `packages/core/consumer/contract/plan.js`
 - `packages/core/consumer/contract/products.js`
+- `packages/core/consumer/contract/reader.js`
 - `packages/core/consumer/contract/shape.js`
 - `scripts/generate-minimal-consumer-contract.mjs`
 
@@ -1062,6 +1063,7 @@ Owner: Buildchain consumer contract maintainers
 ### Tests
 
 - `tests/minimal-consumer-contract.test.mjs`
+- `tests/consumer-product-config.test.mjs`
 
 ### Generated outputs
 
@@ -1088,6 +1090,8 @@ Owner: Buildchain pipeline maintainers
 - `packages/core/providers/github/pipeline-run-entry.js`
 - `packages/core/providers/github/pipeline-runs.js`
 - `packages/core/providers/github/pipeline-source.js`
+- `packages/core/providers/github/pipeline-version-artifacts.js`
+- `packages/core/providers/github/pipeline-version-readback.js`
 - `packages/core/providers/github/pipeline-worker.js`
 - `packages/core/publication/pipeline/actions.js`
 - `packages/core/publication/pipeline/apply.js`
@@ -1129,7 +1133,15 @@ Owner: Buildchain pipeline maintainers
 - `packages/core/publication/pipeline/settle.js`
 - `packages/core/publication/pipeline/signing.js`
 - `packages/core/publication/pipeline/source-plan.js`
+- `packages/core/publication/pipeline/version-actions.js`
+- `packages/core/publication/pipeline/version-build.js`
+- `packages/core/publication/pipeline/version-context.js`
+- `packages/core/publication/pipeline/version-material.js`
+- `packages/core/publication/pipeline/version-preparation.js`
+- `packages/core/publication/pipeline/version-regeneration.js`
+- `packages/core/publication/pipeline/version-source-guard.js`
 - `packages/core/publication/pipeline/version.js`
+- `packages/core/publication/pipeline/worker.js`
 - `packages/core/workflow/attempt/journal.js`
 - `packages/core/workflow/commands/pipeline-build.mjs`
 - `packages/core/workflow/pipeline/action-output.js`
@@ -1183,6 +1195,7 @@ Owner: Buildchain pipeline maintainers
 ### Contracts
 
 - `architecture/decisions/0007-hosted-pipeline-controller.md`
+- `architecture/decisions/0009-pipeline-version-preparation.md`
 
 ### Tests
 
@@ -1229,6 +1242,10 @@ Owner: Buildchain pipeline maintainers
 - `tests/pipeline-runtime.test.mjs`
 - `tests/pipeline-settlement.test.mjs`
 - `tests/pipeline-source.test.mjs`
+- `tests/pipeline-version-artifacts.test.mjs`
+- `tests/pipeline-version-build.test.mjs`
+- `tests/pipeline-version-context.test.mjs`
+- `tests/pipeline-version-regeneration.test.mjs`
 - `tests/pipeline-web-status.test.mjs`
 - `tests/pipeline-worker.test.mjs`
 

package/architecture/ci-lane-change-budget.json

@@ -2852,6 +2852,91 @@
         "expectedContributionSeconds": 49500,
         "rationale": "Delegates to the same isolated product, native delivery and publication jobs. Recovery schedules only qualified missing work; this inherited conservative timeout sum is not measured latency or a new parallel lane family."
       }
+    },
+    {
+      "laneId": ".github/workflows/.release-pipeline-products.yml#materialize",
+      "authorityClass": "governed-delegation",
+      "triggerClass": "reusable",
+      "concurrencyPolicy": {
+        "mode": "ref-scoped",
+        "cancelInProgress": false
+      },
+      "expectedRunnerMinutes": 5,
+      "cancellationBehavior": "finish-started",
+      "sloImpact": {
+        "mergeCritical": false,
+        "metric": "declared version regeneration before publication or next-development materialization",
+        "expectedContributionSeconds": 300,
+        "rationale": "One shared internal component executes each declared product platform for version-derived files, then independently verifies actual job completion and archive digests before Git writes. Up to five product runners each have a sixty-minute ceiling, and materialization has twenty minutes; the component can run once for publication and once for next development. Parent reusable jobs delegate without a separate product runner. Bounds are declared capacity, not measured latency; per-repository publication concurrency retains a single provider writer."
+      }
+    },
+    {
+      "laneId": ".github/workflows/.release-pipeline-products.yml#development",
+      "authorityClass": "governed-delegation",
+      "triggerClass": "reusable",
+      "concurrencyPolicy": {
+        "mode": "ref-scoped",
+        "cancelInProgress": false
+      },
+      "expectedRunnerMinutes": 5,
+      "cancellationBehavior": "finish-started",
+      "sloImpact": {
+        "mergeCritical": false,
+        "metric": "declared version regeneration before publication or next-development materialization",
+        "expectedContributionSeconds": 300,
+        "rationale": "One shared internal component executes each declared product platform for version-derived files, then independently verifies actual job completion and archive digests before Git writes. Up to five product runners each have a sixty-minute ceiling, and materialization has twenty minutes; the component can run once for publication and once for next development. Parent reusable jobs delegate without a separate product runner. Bounds are declared capacity, not measured latency; per-repository publication concurrency retains a single provider writer."
+      }
+    },
+    {
+      "laneId": ".github/workflows/.release-pipeline-version.yml#build",
+      "authorityClass": "evidence",
+      "triggerClass": "reusable",
+      "concurrencyPolicy": {
+        "mode": "ref-scoped",
+        "cancelInProgress": false
+      },
+      "expectedRunnerMinutes": 300,
+      "cancellationBehavior": "finish-started",
+      "sloImpact": {
+        "mergeCritical": false,
+        "metric": "declared version regeneration before publication or next-development materialization",
+        "expectedContributionSeconds": 18000,
+        "rationale": "One shared internal component executes each declared product platform for version-derived files, then independently verifies actual job completion and archive digests before Git writes. Up to five product runners each have a sixty-minute ceiling, and materialization has twenty minutes; the component can run once for publication and once for next development. Parent reusable jobs delegate without a separate product runner. Bounds are declared capacity, not measured latency; per-repository publication concurrency retains a single provider writer."
+      }
+    },
+    {
+      "laneId": ".github/workflows/.release-pipeline-version.yml#materialize",
+      "authorityClass": "governed-delegation",
+      "triggerClass": "reusable",
+      "concurrencyPolicy": {
+        "mode": "ref-scoped",
+        "cancelInProgress": false
+      },
+      "expectedRunnerMinutes": 20,
+      "cancellationBehavior": "finish-started",
+      "sloImpact": {
+        "mergeCritical": false,
+        "metric": "declared version regeneration before publication or next-development materialization",
+        "expectedContributionSeconds": 1200,
+        "rationale": "One shared internal component executes each declared product platform for version-derived files, then independently verifies actual job completion and archive digests before Git writes. Up to five product runners each have a sixty-minute ceiling, and materialization has twenty minutes; the component can run once for publication and once for next development. Parent reusable jobs delegate without a separate product runner. Bounds are declared capacity, not measured latency; per-repository publication concurrency retains a single provider writer."
+      }
+    },
+    {
+      "laneId": ".github/workflows/.ops-pipeline-execute.yml#stable-recheck",
+      "authorityClass": "evidence",
+      "triggerClass": "reusable",
+      "concurrencyPolicy": {
+        "mode": "ref-scoped",
+        "cancelInProgress": false
+      },
+      "expectedRunnerMinutes": 20,
+      "cancellationBehavior": "finish-started",
+      "sloImpact": {
+        "mergeCritical": false,
+        "metric": "bounded stable qualification recheck",
+        "expectedContributionSeconds": 1200,
+        "rationale": "Wait at most fifteen minutes outside the publication lock, then wake the same native Attempt through the normal entry to collect fresh qualification. Twenty minutes includes runtime preparation; this is a conservative timeout budget, not measured latency."
+      }
     }
   ],
   "declarationFamilies": [

package/architecture/decisions/0009-pipeline-version-preparation.md

@@ -0,0 +1,186 @@
+---
+status: draft
+period: 2026-09-13
+theme: minimal-consumer-version-preparation
+doc_type: architecture-decision-record
+source_level: local-files
+confidence: medium
+sensitivity: public
+evidence_grade: B
+review_state: unreviewed
+last_reviewed: 2026-09-13
+ai_provenance:
+  model_family: GPT-6
+  product: Codex
+  generated_at: 2026-09-13
+  visible_context: Consumer compiler, prepared self product contract, product execution, version materialization, provider adapters and local adversarial tests.
+  invisible_context_boundary: Local tests do not establish published entry qualification, hosted provider authorization or completed self migration.
+---
+
+# ADR 0009: Regenerate version data before qualifying the final product source
+
+Changing a package version can invalidate generated documents that embed that
+version or hashes of other documents. Both publication and next-development
+preparation must regenerate those declared documents before creating the final
+Git source. Leaving the old documents in place would fail the ordinary clean
+source build, or publish facts that disagree with the product version.
+
+The runtime retains an exact preparation in the current attempt. It binds the
+source and TOML, selected runtime, target version, parent plan, purpose and
+declared platforms. An internal component checks out that source on separate
+product runners, patches only declared primary version fields, and executes the
+existing product install/build/verify commands without publication credentials.
+No new consumer command or workflow input is needed.
+
+The product result contains every declared version document and derived file.
+The source guard compares all original tracked bytes, types, executable modes,
+HEAD and tree directly; index flags cannot hide modifications. Only declared
+material bytes may change. Primary documents must exactly equal the pure version
+field patch. Changed derived documents from different platforms must agree.
+The source TOML, managed runtime locks and workflow authority cannot be generated
+as version material. Paths are literal, regular UTF-8 files with bounded size;
+symlink and submodule sources are not qualified by this preparation implementation.
+
+The ordinary product build also compares every tracked file directly with its
+admitted Git blob before and after executing commands. Index flags, local clean
+filters and ignored executable-mode changes cannot make altered bytes qualify.
+Tracked symbolic links retain their exact target bytes; parent directories
+cannot become links. Source checkout transformations must preserve the admitted
+bytes (Buildchain declares LF checkout in `.gitattributes`); unresolved submodules
+are rejected. This strengthens both the initial version-preparation source check
+and ordinary build qualification without granting product commands credentials.
+
+Project Cut replay transfers generated source patches through private temporary
+files instead of buffering them as command metadata. Git still applies the exact
+binary patch to an isolated index and compares stable patch identity and changed
+paths against the source. This permits large committed action bundles without
+changing the source composition, family receipt, conflict rejection or metadata
+output bound. Temporary descriptors and files are closed on success and failure.
+
+A separate job checks the original published caller, exact reusable definitions,
+provider run and retry, every successful platform job, and immutable artifact
+digests before reading results. The retained preparation and actual source
+contract are checked again before the qualified material enters the journal.
+Git materialization verifies the resulting tree, exact document bytes and ref.
+The final product build then runs against that exact materialized source and is
+qualified and signed through the existing publication boundary.
+
+For next-development, the same preparation starts from the retained current
+protected development source. It creates an ordinary PR and preserves the
+completed publication while waiting for protected review and integration.
+Recovery can reuse retained material only for the same parent and runtime;
+conflicting qualified results fail closed. Published payloads and provider
+receipts remain immutable under the existing recovery contract.
+
+This adds actual product execution when derived version files are declared.
+The publication component calls one shared internal version component for its
+two purposes. Each component stays within the existing job, step and module
+budgets. Local tests cover real child processes and Git byte guards, artifact
+transport rejection, retained request admission, materialization and existing
+recovery regressions. Hosted platform and provider qualification remain separate
+delivery requirements.
+
+An npm artifact may declare `path = "."` to pack the product directory through
+the standard runtime packer with lifecycle hooks disabled. Optional artifact
+`filename` data preserves established download names. Names are single bounded
+filenames with the declared format, unique across the full publication plan,
+and independently verified against the packed file. These fields do not expose
+publication commands or provider control to the consumer.
+
+The prepared `.buildchain/minimal-consumer.toml` declares Buildchain's npm
+package and the three existing binary downloads using those ordinary product
+fields. It retains all seven primary version documents and three derived
+documents. The contract is inactive: the current callers still select
+`.buildchain/buildchain.toml`. Publishing this preparation does not activate a
+second publisher or prove the self migration. The protected transition must
+qualify the published entry and selected runtime, preserve the existing stable
+qualification gates, retire the old consumer callers with a single writer,
+and finally use the shared normal/recovery pair and canonical TOML path.
+
+Each declared native checkpoint platform retains a full candidate action build,
+site generation and repository check through ordinary product commands. Linux
+runs this with the npm product; macOS and Windows run it with their standalone
+product. The full check includes the product's checkpoint clean-process and
+recovery tests; a binary version/help smoke test alone cannot replace source
+qualification. Rust formatting, lint and WASM toolchain components are explicit
+install commands on each platform. Local configuration checks establish this
+wiring only; the protected hosted executions and any remaining container-specific
+qualification must still pass before retiring the existing verification caller.
+
+Site generation reads its KFD upstream declarations from the product-owned
+`architecture/product-upstreams.json`. The existing collector receives this
+data explicitly, so changing the consumer TOML to the minimal schema preserves
+the product's seven upstream evidence assets and their digests. The legacy
+configuration retains its declarations until the protected caller cutover;
+the new data contains no build, publication or recovery orchestration.
+
+The prepared contract also declares stable eligibility as a closed `stable`
+table: minimum publication interval and canary soak in seconds, literal product
+paths, a product impact document, and whether published-entry qualification is
+required. It carries no workflow names, provider commands or evidence selectors.
+The publication plan retains an independent copy under its immutable root.
+The self preparation preserves the existing 86,400-second interval and
+3,600-second soak. The shared stable evaluator now rejects impact from another
+candidate version and duplicate canary observations instead of selecting the
+last observation. These declarations and local checks do not activate the new
+publisher: independent provider collection and enforcement in the pipeline
+remain required before the protected self cutover.
+Stable preparation and application now collect source facts after verifying
+the authoritative attempt. The collector resolves the exact public Alpha tag,
+requires the same channel PR source and compiled contract, and verifies every
+declared version document. It reads product impact from a bounded regular Git
+blob in that exact tree, independently checking its bytes and version. Product
+differences include added, removed and mode-changed files from complete Git
+trees; a short comparison listing cannot silently hide product changes.
+
+Complete bounded release pagination identifies the previous published product
+and the most recent earlier stable publication, including backports for the
+cooldown. The comparison must match the plan's retained previous channel.
+Fresh tag, release and predecessor observations reject concurrent changes.
+Same-version recovery does not count its own completed publication as an older
+release. These facts carry their own root and the exact publication plan root.
+
+New publication plans declare evidence version 1 and publish their full plan
+alongside qualification, capsules, invocation, attestation and Passport. The
+plan root is already bound by the signed product predicate. Recovery of an older
+retained transaction preserves its original evidence inventory and provider
+receipts; it does not retroactively add a plan or replace public bytes.
+
+Stable product qualification reads those fixed evidence assets from the exact
+Alpha release, with complete bounded pagination, unique identities, byte digests
+and a second asset readback. It checks the original signature through the
+central publisher workflow and exact provider source, reconstructs the Passport
+and invocation, and requires every declared product/platform output. Original
+build jobs and the signing job must still match provider readback, including
+their attempt, source, publisher definition and completion times. Historical
+qualification is checked at its issue time; it does not renew that receipt or
+authorize the current Stable publisher. Successful product evidence also causes
+another source observation before the eligibility decision.
+
+Published-entry qualification independently inventories completed normal PR
+runs after the exact Alpha release. It verifies the generated thin caller,
+published entry definition, managed source lock and selected candidate runtime,
+then reads the original native Attempt and retained product-build receipt.
+The normal consumer commit can differ from the released runtime commit; its
+compiled product contract must be identical. Every declared platform and the
+exact recorder job must agree with fresh provider readback. A newer failed or
+unrecorded matching build blocks fallback to older successful evidence. Recovery
+runs, foreign entries and an old runtime behind a new entry do not qualify.
+
+When only the publication interval or canary soak remains unsatisfied, preparation
+retains the eligibility and a source-bound waiting receipt in the same Attempt.
+An internal job outside the repository publication lock waits at most fifteen
+minutes, checks native ownership every thirty seconds, and wakes the same normal
+entry. The next execution recollects qualification; the waiting receipt grants
+no publication authority. Publication checks again before provider effects and
+can return to this waiting path if new evidence moves the soak deadline.
+
+The timer stops if its retained receipt is superseded, the Attempt changes or
+the phase advances. A successor can claim the exact waiting native head while
+the old outer run finishes its wake job; the existing worker fence then rejects
+the old publisher. Missing qualification and non-time failures remain errors.
+Local tests exercise real native records with deterministic provider facts and
+an injected clock, including bounded waits and stale-worker races. They do not
+establish live published qualification or activate the prepared self contract.
+Alpha preparation remains available for the protected transition; the legacy
+stable publisher retains its existing policy until the protected self cutover.

package/architecture/internal-capabilities.json

@@ -231,6 +231,7 @@
     "packages/core/consumer/contract/inspection.js",
     "packages/core/consumer/contract/plan.js",
     "packages/core/consumer/contract/products.js",
+    "packages/core/consumer/contract/reader.js",
     "packages/core/consumer/contract/shape.js",
     "packages/core/consumer/policy-admission.js",
     "packages/core/consumer/policy-scan.js",
@@ -478,6 +479,8 @@
     "packages/core/providers/github/pipeline-run-entry.js",
     "packages/core/providers/github/pipeline-runs.js",
     "packages/core/providers/github/pipeline-source.js",
+    "packages/core/providers/github/pipeline-version-artifacts.js",
+    "packages/core/providers/github/pipeline-version-readback.js",
     "packages/core/providers/github/pipeline-worker.js",
     "packages/core/providers/github/product-publication.js",
     "packages/core/providers/github/publication-control-plane.js",
@@ -599,7 +602,15 @@
     "packages/core/publication/pipeline/settle.js",
     "packages/core/publication/pipeline/signing.js",
     "packages/core/publication/pipeline/source-plan.js",
+    "packages/core/publication/pipeline/version-actions.js",
+    "packages/core/publication/pipeline/version-build.js",
+    "packages/core/publication/pipeline/version-context.js",
+    "packages/core/publication/pipeline/version-material.js",
+    "packages/core/publication/pipeline/version-preparation.js",
+    "packages/core/publication/pipeline/version-regeneration.js",
+    "packages/core/publication/pipeline/version-source-guard.js",
     "packages/core/publication/pipeline/version.js",
+    "packages/core/publication/pipeline/worker.js",
     "packages/core/publication/publication-rehearsal-capsule.js",
     "packages/core/publication/publication-rehearsal-provider-bindings.js",
     "packages/core/publication/publication-rehearsal.js",
@@ -3070,10 +3081,14 @@
         "packages/core/consumer/contract/inspection.js",
         "packages/core/consumer/contract/plan.js",
         "packages/core/consumer/contract/products.js",
+        "packages/core/consumer/contract/reader.js",
         "packages/core/consumer/contract/shape.js",
         "scripts/generate-minimal-consumer-contract.mjs"
       ],
-      "tests": ["tests/minimal-consumer-contract.test.mjs"],
+      "tests": [
+        "tests/minimal-consumer-contract.test.mjs",
+        "tests/consumer-product-config.test.mjs"
+      ],
       "contracts": ["architecture/decisions/0005-minimal-consumer-contract.md"],
       "generatedOutputs": [
         "architecture/minimal-consumer-migration.json",
@@ -3120,6 +3135,8 @@
         "packages/core/providers/github/pipeline-run-entry.js",
         "packages/core/providers/github/pipeline-runs.js",
         "packages/core/providers/github/pipeline-source.js",
+        "packages/core/providers/github/pipeline-version-artifacts.js",
+        "packages/core/providers/github/pipeline-version-readback.js",
         "packages/core/providers/github/pipeline-worker.js",
         "packages/core/publication/pipeline/actions.js",
         "packages/core/publication/pipeline/apply.js",
@@ -3161,7 +3178,15 @@
         "packages/core/publication/pipeline/settle.js",
         "packages/core/publication/pipeline/signing.js",
         "packages/core/publication/pipeline/source-plan.js",
+        "packages/core/publication/pipeline/version-actions.js",
+        "packages/core/publication/pipeline/version-build.js",
+        "packages/core/publication/pipeline/version-context.js",
+        "packages/core/publication/pipeline/version-material.js",
+        "packages/core/publication/pipeline/version-preparation.js",
+        "packages/core/publication/pipeline/version-regeneration.js",
+        "packages/core/publication/pipeline/version-source-guard.js",
         "packages/core/publication/pipeline/version.js",
+        "packages/core/publication/pipeline/worker.js",
         "packages/core/workflow/attempt/journal.js",
         "packages/core/workflow/commands/pipeline-build.mjs",
         "packages/core/workflow/pipeline/action-output.js",
@@ -3256,11 +3281,16 @@
         "tests/pipeline-runtime.test.mjs",
         "tests/pipeline-settlement.test.mjs",
         "tests/pipeline-source.test.mjs",
+        "tests/pipeline-version-artifacts.test.mjs",
+        "tests/pipeline-version-build.test.mjs",
+        "tests/pipeline-version-context.test.mjs",
+        "tests/pipeline-version-regeneration.test.mjs",
         "tests/pipeline-web-status.test.mjs",
         "tests/pipeline-worker.test.mjs"
       ],
       "contracts": [
-        "architecture/decisions/0007-hosted-pipeline-controller.md"
+        "architecture/decisions/0007-hosted-pipeline-controller.md",
+        "architecture/decisions/0009-pipeline-version-preparation.md"
       ],
       "generatedOutputs": [],
       "validationCommands": [

package/architecture/maintainability-debt.json

@@ -7,8 +7,8 @@
   },
   "totalExcessLedger": {
     "metric": "calibrated-full-dimensional-excess-v1",
-    "measuredExcess": 38852,
-    "current": 30791
+    "measuredExcess": 38833,
+    "current": 30772
   },
   "defaults": {
     "owner": "Buildchain architecture maintainers",
@@ -321,7 +321,7 @@
           "lines": 1887
         },
         "current": {
-          "lines": 1825
+          "lines": 1806
         },
         "target": {
           "lines": 600

package/architecture/maintainability-policy.json

@@ -26,17 +26,17 @@
   },
   "repositoryBudgets": {
     "baselineRevision": "9569f69c2cb609372b8a3d65ce5dec8fb7b34a84",
-    "maxHandMaintainedSourceFiles": 1449,
-    "maxHandMaintainedSourceLines": 214973,
-    "maxWorkflowFiles": 72,
-    "maxWorkflowLines": 10289,
-    "latestTransition": "Exact-attempt source, native ownership and product publication recovery through a shared public execution component.",
-    "latestTransitionRationale": "Charge the measured recovery implementation and two hosted workflow additions: immutable predecessor admission, original per-platform source/artifact requalification, retained native cleanup before CAS, repaired runtime continuation, atomic publication material import, fresh signed-transaction recovery authority and preserved completed effects. Shared normal/recovery execution retains separate credentialless product, signing, publisher and follow-up jobs. No per-file, function, complexity, debt or exception ceiling changes; independent governance review covers the exact aggregate and CI lane declarations.",
+    "maxHandMaintainedSourceFiles": 1471,
+    "maxHandMaintainedSourceLines": 217779,
+    "maxWorkflowFiles": 73,
+    "maxWorkflowLines": 10457,
+    "latestTransition": "File-backed Project Cut replay for large generated patches.",
+    "latestTransitionRationale": "Charge the measured 27 implementation lines for private patch files and descriptor cleanup. Exact stable patch identity, changed paths, isolated-index replay, family receipts and conflict rejection remain enforced; the metadata output bound stays at 64 MiB. No new module, workflow, action or authority is introduced; per-file, function, complexity, debt and exception ceilings remain unchanged. This aggregate budget change remains proposed until independent protected review.",
     "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. CI lane change-budget enforcement adds a bounded parser, evaluator, guard, and tests without creating another merge authority. Minimal consumer contract adds exactly seven bounded contract modules, one generated-contract gate and six product build/test example sources; the source-file ceiling increases by fourteen for this reviewed feature slice. Existing per-file, function, complexity and debt limits are unchanged. The final readable template sources require exact source-line and total-automation ceilings of 203394 and 224451 respectively; this charges all generated example sources rather than hiding them from measurement.",
     "governance": "legacy-debt-sunset-2026q4",
     "maxActionDefinitions": 283,
     "maxActionDefinitionLines": 12399,
-    "maxAutomationImplementationLines": 236737
+    "maxAutomationImplementationLines": 239777
   },
   "sourceBudgets": {
     "newFileLines": 600,

package/architecture/minimal-consumer-migration.json

@@ -7036,6 +7036,15 @@
       "destination": "retain-product-source; move-orchestration-into-runtime",
       "commandReferences": []
     },
+    {
+      "path": ".buildchain/minimal-consumer.toml",
+      "kind": "config",
+      "destination": "closed-toml-plan",
+      "commandReferences": [
+        "scripts/build-standalone-binary.mjs",
+        "scripts/verify-standalone-product.mjs"
+      ]
+    },
     {
       "path": ".buildchain/release-impact.json",
       "kind": "consumer-source",

package/architecture/product-upstreams.json

@@ -0,0 +1,20 @@
+[
+  {
+    "id": "kfd",
+    "package": "@kungfu-tech/kfd",
+    "repository": "kungfu-systems/kfd",
+    "kfd_1": "exported-witness",
+    "kfd_2": "exported-claim",
+    "kfd_3": "exported-collaboration-interface",
+    "kfd_4": "schema-metadata",
+    "evidence": [
+      "package:kfd.release.json",
+      "package:.buildchain/kfd-1/contract-world.witness.json",
+      "package:.buildchain/kfd-2/public-release-trust.claim.json",
+      "package:.buildchain/kfd-2/kfd-foundation.trust-claims.json",
+      "package:.buildchain/kfd-2/kfd-foundation.trust-assessment.json",
+      "package:.buildchain/kfd-3/collaboration-interface.json",
+      "package:standards.json"
+    ]
+  }
+]