@kungfu-tech/buildchain 4.0.2-alpha.9 → 4.0.3-alpha.0

package/architecture/{v4-architecture-constitution.md → architecture-constitution.md}

@@ -19,7 +19,7 @@ ai_provenance:
 # Buildchain v4 Architecture Constitution
 
 This constitution governs the `dev/v4/v4.0` release line. The executable
-authority is [`v4-capability-state-machine-manifest.json`](v4-capability-state-machine-manifest.json),
+authority is [`capability-state-machine-manifest.json`](capability-state-machine-manifest.json),
 validated by `buildchain architecture validate`. This document explains that
 contract; it cannot override it.
 
@@ -27,7 +27,7 @@ contract; it cannot override it.
 
 The first v4 line was created from the exact protected v3 merge that contains
 this constitution and
-[`v4-bootstrap-authority.json`](v4-bootstrap-authority.json). The exact source,
+[`bootstrap-authority.json`](bootstrap-authority.json). The exact source,
 bootstrap revision, N-1 qualification, protection, and merge-queue evidence are
 recorded there under the state `qualified-protected-v4-bootstrap`; a local
 branch or unrecorded candidate commit is not release-line authority.
@@ -43,8 +43,8 @@ ledger.
 Dependencies point inward only:
 
 ```text
-workflows -> TypeScript adapters -> libnode host -> Rust domain -> contracts
-legacy compatibility -> TypeScript adapters / contracts
+workflows -> Node provider/IO adapters -> tracked Rust/WASM domain -> contracts
+legacy compatibility -> Node facades / contracts
 ```
 
 Contracts contain serialization and compatibility facts, not provider SDK
@@ -55,12 +55,12 @@ or Rust domain are hard-zero violations. Cycles are forbidden.
 ## 3. Single-writer rule
 
 Every state machine has exactly one authoritative writer. The v4 cutover marks
-the TypeScript v4 control and provider plane authoritative and the legacy v3
-writer retired. Rust v4 owns the deterministic release-activation, journal,
-stable-fence, and recovery domain semantics while the TypeScript v4 adapter
-remains byte-equivalent at that boundary. A second writer, permanent dual
-write, cross-machine mutable file, or implicit compatibility authority has a
-hard-zero budget.
+the Rust/WASM domain authoritative and the legacy v3 and duplicate TypeScript
+semantic writers retired. Node owns provider and IO effects and exposes
+compatibility facades, but every deterministic release plan, fold, root, retry,
+and receipt decision crosses the checked WASM ABI. A second writer, permanent
+dual write, semantic fallback, cross-machine mutable file, or implicit
+compatibility authority has a hard-zero budget.
 
 ## 4. Explicit complexity budgets
 
@@ -85,15 +85,19 @@ second hand-maintained architecture list is authoritative.
 ## 6. Production cutover boundary
 
 The v4 line owns Delivery Warrant, Release Transaction, activation,
-publication, propagation, and release-tail state. This does not introduce a
-daemon, a service database, provider SDKs in contracts or Rust domain code, or
-a second writer. The retained `release/v3/v3.0` coordinate is rollback evidence
-only and cannot regain production authority without a new reviewed cutover.
+publication, propagation, and release-tail state. Its production domain is the
+tracked artifact governed by
+[`rust-wasm-production-authority.json`](rust-wasm-production-authority.json):
+Node verifies the artifact digest and ABI before use and fails closed without a
+JavaScript semantic fallback. This does not introduce a daemon, a service
+database, provider SDKs in contracts or Rust domain code, or a second writer.
+The retained `release/v3/v3.0` coordinate is rollback evidence only and cannot
+regain production authority without a new reviewed cutover.
 
 ## 7. Wave 0 host boundary
 
 The bounded Rust/libnode bridge spike is recorded in
-[`v4-rust-libnode-bridge-spike.md`](v4-rust-libnode-bridge-spike.md). Wave 0
+[`rust-libnode-bridge-spike.md`](rust-libnode-bridge-spike.md). Wave 0
 uses a replaceable subprocess host behind a closed byte-oriented contract; the
 Rust trunk owns process lifecycle and transport, while existing TypeScript
 remains the only production writer. This selection is evidence for later
@@ -102,7 +106,7 @@ qualification, not a final ABI or consumer migration.
 ## 8. Wave 2 Stage Capsule contract
 
 The executable Stage Capsule architecture contract is
-[`v4-stage-capsule-contract.json`](v4-stage-capsule-contract.json). It fixes one
+[`stage-capsule-contract.json`](stage-capsule-contract.json). It fixes one
 schema authority, one TypeScript v3 writer, validation-only Rust, and zero
 provider imports or production write-authority changes. Identity, retention
 promise, current availability, qualification, content roots, and rooted
@@ -111,7 +115,7 @@ reconciliation work must consume this contract rather than create competing
 identity or writer authority.
 
 The successor storage slice is governed by
-[`v4-stage-capsule-store-contract.json`](v4-stage-capsule-store-contract.json).
+[`stage-capsule-store-contract.json`](stage-capsule-store-contract.json).
 It adds provider-neutral output-manifest, retention-state, transport, and store
 receipt roots plus a deterministic no-network local filesystem reference
 store. GitHub Artifact and S3-compatible adapters remain effect-disabled or
@@ -120,7 +124,7 @@ and qualification evidence stay separate facts; none becomes Capsule identity,
 qualification authority, or a production writer.
 
 Final Wave 2 qualification is governed by
-[`v4-stage-capsule-qualification.json`](v4-stage-capsule-qualification.json).
+[`stage-capsule-qualification.json`](stage-capsule-qualification.json).
 It consumes the existing Capsule, store, checkpoint, and resume authorities for
 six real-runner shadow campaigns and one exact terminal reconciliation. A
 qualification root is evidence only: TypeScript v3 remains production
@@ -130,12 +134,11 @@ effects, release effects, and public cutover remain outside this transition.
 ## 9. Wave 3 provider operation journal
 
 The executable provider operation journal contract is
-[`v4-provider-operation-journal-contract.json`](v4-provider-operation-journal-contract.json).
+[`provider-operation-journal-contract.json`](provider-operation-journal-contract.json).
 It freezes one closed schema authority and one Rust v4 state-fold authority
 for append-only intent, attempt, rooted observation, confirmation, and
-reconciliation records. The TypeScript v4 plane performs provider adaptation
-and conformance projection against the same fixtures; v4 is the sole
-production writer.
+reconciliation records. The Node v4 plane performs provider adaptation and
+calls the tracked Rust/WASM authority; it contains no second state fold.
 
 Logical operation identity excludes attempt ordinals and mutable provider or
 runner facts. Every retry preserves `operationRoot`, while every attempt and
@@ -158,12 +161,12 @@ closed with typed faults.
 ## 10. Release activation production domain
 
 The executable release activation boundary is
-[`v4-release-activation-shadow-domain.json`](v4-release-activation-shadow-domain.json).
+[`release-activation-shadow-domain.json`](release-activation-shadow-domain.json).
 It consumes an explicit qualification root, dependency graph, compensation
 boundaries, provider-operation identities, and append-only journal facts to
-derive one deterministic activation plan and resume state. Rust is the sole v4
-plan-and-fold authority; TypeScript must remain byte-equivalent against
-the same closed schema and fixture.
+derive one deterministic activation plan and resume state. Rust/WASM is the
+sole v4 plan-and-fold authority; the Node facade delegates through the checked
+ABI and retains only provider adaptation.
 
 Confirmed operations are never eligible for replay. Attempting, observed, and
 confirmable operations require provider-neutral readback before any retry,
@@ -177,7 +180,7 @@ rooted readback before confirmation or retry.
 ## 11. Stable publication production fence
 
 The stable-candidate production publication boundary is governed by
-[`v4-stable-publication-fence.json`](v4-stable-publication-fence.json). It
+[`stable-publication-fence.json`](stable-publication-fence.json). It
 binds one exact candidate root to source, metadata, provider-operation journal,
 protected ancestry, provider confirmations, and an independently sealed
 qualification before a production publication plan can exist.
@@ -193,7 +196,7 @@ targets, and it must read them back before completion.
 ## 12. Wave 3 partial-mutation recovery qualification
 
 The executable recovery qualification boundary is
-[`v4-partial-mutation-recovery-qualification.json`](v4-partial-mutation-recovery-qualification.json).
+[`partial-mutation-recovery-qualification.json`](partial-mutation-recovery-qualification.json).
 It consumes retained Stage Capsule resume evidence and release-activation journal
 state only after exact source, policy, platform, qualification, plan, state,
 operation, journal, and compensation-boundary roots agree.
@@ -203,8 +206,8 @@ Every nonterminal operation maps deterministically to `retry`, `wait`,
 `terminal-noop` facts and never re-enter the next-operation set. Missing,
 expired, corrupt, conflicting, cross-boundary, or attempt-budget-exhausted
 evidence fails closed at an exact Stage Capsule or provider-operation
-checkpoint. The Rust domain is the sole v4 planner and TypeScript is a
-byte-equivalent projection. Both are pure: they perform zero provider,
+checkpoint. The Rust/WASM domain is the sole v4 planner and the Node facade
+delegates to it. The planner is pure: it performs zero provider,
 filesystem, network, credential, ref, package, image, or release mutation.
 Their exact plan is the only recovery authority consumed by the TypeScript v4
 provider adapter.

package/architecture/{v3-core-mechanism-inventory.md → baseline-core-mechanism-inventory.md}

@@ -19,7 +19,7 @@ ai_provenance:
 # v3 Core Mechanism Inventory
 
 This is the human projection of
-[`v3-core-mechanism-inventory.json`](v3-core-mechanism-inventory.json).
+[`baseline-core-mechanism-inventory.json`](baseline-core-mechanism-inventory.json).
 The JSON inventory is authoritative and validated by
 `scripts/check-core-mechanism-inventory.mjs`.
 

package/architecture/{v4-bootstrap-authority.json → bootstrap-authority.json}

@@ -36,9 +36,9 @@
     "verifiedAt": "2026-08-07T02:20:03Z"
   },
   "authorityFiles": [
-    "architecture/v4-bootstrap-authority.json",
-    "architecture/v4-capability-state-machine-manifest.json",
-    "architecture/v4-exception-ledger.json"
+    "architecture/bootstrap-authority.json",
+    "architecture/capability-state-machine-manifest.json",
+    "architecture/exception-ledger.json"
   ],
   "bootstrapRule": {
     "authorityRevision": "the exact protected dev/v3/v3.0 merge containing this contract",

package/architecture/{v3-v4-capability-closure.md → capability-parity-closure.md}

@@ -19,7 +19,7 @@ ai_provenance:
 # Buildchain v3 to v4 live capability inventory
 
 The machine-readable inventory in
-[`v3-v4-live-capability-inventory.json`](v3-v4-live-capability-inventory.json)
+[`capability-parity-live-capability-inventory.json`](capability-parity-live-capability-inventory.json)
 binds the previous absorption-family v3 cut, the execution-time protected v3
 head, and the execution-time protected v4 head. It is an auditable cache of
 Git objects and generated registries, not an assertion that branch names remain
@@ -36,14 +36,14 @@ previous family capture. Each capability has exactly one disposition:
 Run the fail-closed check with:
 
 ```sh
-node scripts/check-v3-v4-capability-inventory.mjs
+node scripts/check-capability-parity-inventory.mjs
 ```
 
 Refresh the checked-in matrix only after intentionally updating all three exact
 cuts and reviewing every newly discovered gap:
 
 ```sh
-node scripts/check-v3-v4-capability-inventory.mjs --write
+node scripts/check-capability-parity-inventory.mjs --write
 ```
 
 The extractor rejects a new missing capability unless its exact stable identity

package/architecture/{v3-v4-live-capability-inventory.json → capability-parity-live-capability-inventory.json}

@@ -68690,7 +68690,7 @@
       "disposition": "v4-native",
       "id": "platform-branch:linux",
       "negativeProbe": "removing or substituting the declared v4 route fails validation",
-      "ownerAssignment": "2026-08-26-buildchain-v4-cross-platform-adopter-qualification",
+      "ownerAssignment": "2026-08-26-buildchain-cross-platform-adopter-qualification",
       "positiveProbe": "the exact v4 cut contains the declared route evidence",
       "residual": null,
       "sourceEvidence": {
@@ -68712,7 +68712,7 @@
       "disposition": "v4-native",
       "id": "platform-branch:macos",
       "negativeProbe": "removing or substituting the declared v4 route fails validation",
-      "ownerAssignment": "2026-08-26-buildchain-v4-cross-platform-adopter-qualification",
+      "ownerAssignment": "2026-08-26-buildchain-cross-platform-adopter-qualification",
       "positiveProbe": "the exact v4 cut contains the declared route evidence",
       "residual": null,
       "sourceEvidence": {
@@ -68734,7 +68734,7 @@
       "disposition": "v4-native",
       "id": "platform-branch:self-hosted",
       "negativeProbe": "removing or substituting the declared v4 route fails validation",
-      "ownerAssignment": "2026-08-26-buildchain-v4-cross-platform-adopter-qualification",
+      "ownerAssignment": "2026-08-26-buildchain-cross-platform-adopter-qualification",
       "positiveProbe": "the exact v4 cut contains the declared route evidence",
       "residual": null,
       "sourceEvidence": {
@@ -68756,7 +68756,7 @@
       "disposition": "v4-native",
       "id": "platform-branch:windows",
       "negativeProbe": "removing or substituting the declared v4 route fails validation",
-      "ownerAssignment": "2026-08-26-buildchain-v4-cross-platform-adopter-qualification",
+      "ownerAssignment": "2026-08-26-buildchain-cross-platform-adopter-qualification",
       "positiveProbe": "the exact v4 cut contains the declared route evidence",
       "residual": null,
       "sourceEvidence": {

package/architecture/{v4-capability-state-machine-manifest.json → capability-state-machine-manifest.json}

@@ -3,7 +3,7 @@
   "contract": "kungfu-buildchain-v4-capability-state-machine-manifest",
   "releaseLine": {
     "branch": "dev/v4/v4.0",
-    "bootstrapAuthority": "architecture/v4-bootstrap-authority.json",
+    "bootstrapAuthority": "architecture/bootstrap-authority.json",
     "productionAuthority": "v4-native",
     "productionFallback": null,
     "rollbackRef": "release/v3/v3.0",
@@ -549,5 +549,5 @@
       }
     }
   ],
-  "exceptionLedger": "architecture/v4-exception-ledger.json"
+  "exceptionLedger": "architecture/exception-ledger.json"
 }

package/architecture/{v4-capability-state-machine-manifest.schema.json → capability-state-machine-manifest.schema.json}

@@ -36,7 +36,7 @@
       "minItems": 1,
       "items": { "$ref": "#/$defs/stateMachine" }
     },
-    "exceptionLedger": { "const": "architecture/v4-exception-ledger.json" }
+    "exceptionLedger": { "const": "architecture/exception-ledger.json" }
   },
   "$defs": {
     "stringArray": {
@@ -58,7 +58,7 @@
       "properties": {
         "branch": { "const": "dev/v4/v4.0" },
         "bootstrapAuthority": {
-          "const": "architecture/v4-bootstrap-authority.json"
+          "const": "architecture/bootstrap-authority.json"
         },
         "productionAuthority": { "const": "v4-native" },
         "productionFallback": { "type": "null" },