@kungfu-tech/buildchain 3.0.9-alpha.9 → 4.0.0-alpha.0

package/docs/cli-reference.md

@@ -269,127 +269,6 @@ buildchain create runner-provenance --input-json <file-or-json> [--output <file>
 buildchain dev
 ```
 
-### `buildchain dev authority admit-merge-group`
-
-- Help: `buildchain dev authority admit-merge-group --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority complete-qualification`
-
-- Help: `buildchain dev authority complete-qualification --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority heartbeat-landing`
-
-- Help: `buildchain dev authority heartbeat-landing --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority heartbeat-qualification`
-
-- Help: `buildchain dev authority heartbeat-qualification --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority lease-landing`
-
-- Help: `buildchain dev authority lease-landing --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority lease-qualification`
-
-- Help: `buildchain dev authority lease-qualification --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority migrate`
-
-- Help: `buildchain dev authority migrate --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority observe`
-
-- Help: `buildchain dev authority observe --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority recover`
-
-- Help: `buildchain dev authority recover --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority settle`
-
-- Help: `buildchain dev authority settle --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev authority submit`
-
-- Help: `buildchain dev authority submit --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev authority <migrate|submit|lease-qualification|heartbeat-qualification|complete-qualification|lease-landing|heartbeat-landing|recover|admit-merge-group|settle|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
 ### `buildchain dev merge-queue`
 
 - Help: `buildchain dev merge-queue --help`
@@ -420,18 +299,7 @@ buildchain dev pr-admit --repository <owner/repo> --branch <dev/vN/vN.M> --pull-
 - Syntax:
 
 ```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
-```
-
-### `buildchain dev proof classify-native`
-
-- Help: `buildchain dev proof classify-native --help`
-- Canonical id: `dev`
-- Options: `--json`, `--output`
-- Syntax:
-
-```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
+buildchain dev proof <source|verify-source|classify|replay|integration|verify-integration> [--output <file>] [--json]
 ```
 
 ### `buildchain dev proof integration`
@@ -442,18 +310,7 @@ buildchain dev proof <source|verify-source|classify|native|verify-native|classif
 - Syntax:
 
 ```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
-```
-
-### `buildchain dev proof native`
-
-- Help: `buildchain dev proof native --help`
-- Canonical id: `dev`
-- Options: `--json`, `--output`
-- Syntax:
-
-```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
+buildchain dev proof <source|verify-source|classify|replay|integration|verify-integration> [--output <file>] [--json]
 ```
 
 ### `buildchain dev proof replay`
@@ -464,7 +321,7 @@ buildchain dev proof <source|verify-source|classify|native|verify-native|classif
 - Syntax:
 
 ```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
+buildchain dev proof <source|verify-source|classify|replay|integration|verify-integration> [--output <file>] [--json]
 ```
 
 ### `buildchain dev proof source`
@@ -475,7 +332,7 @@ buildchain dev proof <source|verify-source|classify|native|verify-native|classif
 - Syntax:
 
 ```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
+buildchain dev proof <source|verify-source|classify|replay|integration|verify-integration> [--output <file>] [--json]
 ```
 
 ### `buildchain dev proof verify-integration`
@@ -486,29 +343,7 @@ buildchain dev proof <source|verify-source|classify|native|verify-native|classif
 - Syntax:
 
 ```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
-```
-
-### `buildchain dev proof verify-native`
-
-- Help: `buildchain dev proof verify-native --help`
-- Canonical id: `dev`
-- Options: `--json`, `--output`
-- Syntax:
-
-```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
-```
-
-### `buildchain dev proof verify-native-reuse`
-
-- Help: `buildchain dev proof verify-native-reuse --help`
-- Canonical id: `dev`
-- Options: `--json`, `--output`
-- Syntax:
-
-```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
+buildchain dev proof <source|verify-source|classify|replay|integration|verify-integration> [--output <file>] [--json]
 ```
 
 ### `buildchain dev proof verify-source`
@@ -519,18 +354,7 @@ buildchain dev proof <source|verify-source|classify|native|verify-native|classif
 - Syntax:
 
 ```text
-buildchain dev proof <source|verify-source|classify|native|verify-native|classify-native|verify-native-reuse|replay|integration|verify-integration> [--output <file>] [--json]
-```
-
-### `buildchain dev two-phase`
-
-- Help: `buildchain dev two-phase --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--expected-head`, `--native-command`, `--native-proof`, `--pull-request`, `--repository`, `--warrant-result`
-- Syntax:
-
-```text
-buildchain dev two-phase --repository <owner/repo> --branch <dev/vN/vN.M> --pull-request <n> --expected-head <sha> --warrant-result <file> [--native-proof <file>] [--native-command <command>]
+buildchain dev proof <source|verify-source|classify|replay|integration|verify-integration> [--output <file>] [--json]
 ```
 
 ### `buildchain dev warrant cancel-queued`
@@ -541,7 +365,7 @@ buildchain dev two-phase --repository <owner/repo> --branch <dev/vN/vN.M> --pull
 - Syntax:
 
 ```text
-buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
+buildchain dev warrant <submit|select|heartbeat|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
 ```
 
 ### `buildchain dev warrant close`
@@ -552,7 +376,7 @@ buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-que
 - Syntax:
 
 ```text
-buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
+buildchain dev warrant <submit|select|heartbeat|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
 ```
 
 ### `buildchain dev warrant heartbeat`
@@ -563,7 +387,7 @@ buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-que
 - Syntax:
 
 ```text
-buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
+buildchain dev warrant <submit|select|heartbeat|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
 ```
 
 ### `buildchain dev warrant observe`
@@ -574,18 +398,7 @@ buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-que
 - Syntax:
 
 ```text
-buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
-```
-
-### `buildchain dev warrant qualify`
-
-- Help: `buildchain dev warrant qualify --help`
-- Canonical id: `dev`
-- Options: `--branch`, `--execute`, `--json`, `--output`, `--repository`
-- Syntax:
-
-```text
-buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
+buildchain dev warrant <submit|select|heartbeat|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
 ```
 
 ### `buildchain dev warrant recover`
@@ -596,7 +409,7 @@ buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-que
 - Syntax:
 
 ```text
-buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
+buildchain dev warrant <submit|select|heartbeat|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
 ```
 
 ### `buildchain dev warrant select`
@@ -607,7 +420,7 @@ buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-que
 - Syntax:
 
 ```text
-buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
+buildchain dev warrant <submit|select|heartbeat|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
 ```
 
 ### `buildchain dev warrant submit`
@@ -618,7 +431,7 @@ buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-que
 - Syntax:
 
 ```text
-buildchain dev warrant <submit|select|heartbeat|qualify|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
+buildchain dev warrant <submit|select|heartbeat|recover|close|cancel-queued|observe> --repository <owner/repo> --branch <dev/vN/vN.M> [--execute] [--output <file>] [--json]
 ```
 
 ## `diagnostics`
@@ -1498,11 +1311,11 @@ buildchain lifecycle
 
 - Help: `buildchain lifecycle run --help`
 - Canonical id: `lifecycle`
-- Options: `--artifact-name`, `--artifact-path`, `--cwd`, `--manifest-path`, `--process-summary`, `--required`, `--summary-path`
+- Options: `--artifact-name`, `--artifact-path`, `--cwd`, `--manifest-path`, `--platform-id`, `--platform-name`, `--process-summary`, `--required`, `--summary-path`
 - Syntax:
 
 ```text
-buildchain lifecycle run <stage> [--cwd <dir>] [--required] [--artifact-name <name>] [--artifact-path <path>]... [--manifest-path <path>] [--summary-path <path>] [--process-summary <json>]
+buildchain lifecycle run <stage> [--cwd <dir>] [--required] [--artifact-name <name>] [--artifact-path <path>]... [--platform-id <id>] [--platform-name <name>] [--manifest-path <path>] [--summary-path <path>] [--process-summary <json>]
 ```
 
 ## `log`
@@ -2167,17 +1980,6 @@ buildchain release-tail init --declaration <json-or-path> [--state <path>]
 buildchain release-tail plan --declaration <json-or-path> [--output <path>]
 ```
 
-### `buildchain release-tail rehearse`
-
-- Help: `buildchain release-tail rehearse --help`
-- Canonical id: `release-tail`
-- Options: `--capsule`, `--capsule-root`, `--environment-json`, `--evidence`, `--mode`, `--state`
-- Syntax:
-
-```text
-buildchain release-tail rehearse --capsule <path> --capsule-root <absolute-path> --mode <simulate|replay> --state <path> --evidence <path> [--environment-json <json-or-path>]
-```
-
 ### `buildchain release-tail status`
 
 - Help: `buildchain release-tail status --help`

package/docs/cli.md

@@ -49,7 +49,7 @@ Consumers should pin the exact Buildchain version that was validated in their
 repository. When dogfooding a fresh Buildchain release immediately after it is
 published, pnpm may block the install through a minimum release-age policy. In
 that case, add a temporary package/version-specific `minimumReleaseAgeExclude`
-entry, such as `@kungfu-tech/buildchain@3.0.0`, and remove it once the package
+entry, such as `@kungfu-tech/buildchain@4.0.0`, and remove it once the package
 has aged past the normal policy window. Do not replace that with a broad
 registry or scope-wide exclude. Paper scaffold and migration maintain the
 exact current entry in `pnpm-workspace.yaml` before refreshing the lockfile.
@@ -110,7 +110,7 @@ import publicSurfaceAudit from "@kungfu-tech/buildchain/site/public-surface-audi
 
 Use `dist/site/manual-registry.json` to find the packaged operating manuals and
 their SHA-256 digests. Use `dist/site/buildchain-contract.json` to verify the
-floating-ref contract world for a runtime such as `@v3`.
+floating-ref contract world for a runtime such as `@v4`.
 
 For exhaustive lookup, use the generated references rather than scanning this
 conceptual guide:
@@ -386,9 +386,9 @@ branch action, and initial version before any GitHub mutation happens:
 
 ```bash
 buildchain release line open \
-  --major 3 \
+  --major 4 \
   --minor 1 \
-  --source-ref release/v3/v3.0 \
+  --source-ref release/v4/v4.0 \
   --json
 ```
 
@@ -401,9 +401,9 @@ reconciliation succeeds, and opens the first dev-to-alpha channel PR:
 
 ```bash
 buildchain release line open \
-  --major 3 \
+  --major 4 \
   --minor 1 \
-  --source-ref release/v3/v3.0 \
+  --source-ref release/v4/v4.0 \
   --write \
   --json
 ```
@@ -994,10 +994,10 @@ even when the bundle hash has been refreshed.
 maintainer opens or merges a channel PR:
 
 ```bash
-buildchain release --dry-run --target-ref alpha/v3/v3.0
-buildchain release --dry-run --target-ref release/v3/v3.0 --sha <verified-sha>
-buildchain release dry-run --target-ref publish-gate/major --source-ref release/v3/v3.0
-buildchain release explain --target-ref alpha/v3/v3.0 --json
+buildchain release --dry-run --target-ref alpha/v4/v4.0
+buildchain release --dry-run --target-ref release/v4/v4.0 --sha <verified-sha>
+buildchain release dry-run --target-ref publish-gate/major --source-ref release/v4/v4.0
+buildchain release explain --target-ref alpha/v4/v4.0 --json
 ```
 
 This is a Buildchain-level dry-run, not an npm dry-run. It explains the legal
@@ -1012,7 +1012,7 @@ Pass `--json` for a machine-readable plan.
 for the publish transaction state:
 
 ```bash
-buildchain transaction inspect --version v3.0.1-alpha.2
+buildchain transaction inspect --version v4.0.1-alpha.2
 ```
 
 It reads or locally initializes the durable transaction record and validates
@@ -1039,9 +1039,9 @@ Buildchain's own npm package is published from
 `.github/workflows/buildchain-ref-promotion.yml`, inside the same publish
 transaction that promotes release refs:
 
-- `v3.0.3-alpha.0` publishes to npm with dist-tag `alpha`.
-- `v3.0.2` publishes to npm with dist-tag `latest`.
-- moving refs such as `v3`, `v3.0`, and `v3.0-alpha` do not match the publish
+- `v4.0.3-alpha.0` publishes to npm with dist-tag `alpha`.
+- `v4.0.2` publishes to npm with dist-tag `latest`.
+- moving refs such as `v4`, `v4.0`, and `v4.0-alpha` do not match the publish
   workflow and do not publish.
 
 The promotion workflow uses npm Trusted Publishing through GitHub Actions OIDC.

package/docs/dev-alpha-candidate-patrol.md

@@ -13,7 +13,7 @@ ai_provenance:
   model_family: GPT-5
   product: Codex
   generated_at: 2026-08-11
-  visible_context: Buildchain v3 Release Train and Release Cut contracts, existing source locks, exact-source Alpha preflight, Dev Patrol, cancelled duplicate runs, protected auto-merge policy, repository release governance, and the consumer-owned settlement renderer threat model.
+  visible_context: Buildchain v4 parity of the proven v3 Release Train and Release Cut contracts, existing source locks, exact-source Alpha preflight, Dev Patrol, cancelled duplicate runs, protected auto-merge policy, repository release governance, and the consumer-owned settlement renderer threat model.
   invisible_context_boundary: No credentials, private logs, or private configuration were used.
 ---
 
@@ -39,7 +39,7 @@ head, selected SHA, and count of skipped newer commits. This makes a slow native
 verification lane live under continuous development without silently treating
 an unqualified head as releasable.
 
-Before any new selection, the v3 controller now resolves the open managed PR and
+Before any new selection, the v4 controller now resolves the open managed PR and
 validates its embedded authoritative Release Train. If one exists, the frozen
 Release Cut wins: Candidate Patrol does not scan for or retain a newer qualified
 candidate. It returns the cut's exact candidate commit, candidate tree,
@@ -59,14 +59,6 @@ controller then compares the selected SHA to the exact Alpha head before it can
 be eligible, so a bounded scan cannot turn a commit outside the promotion
 ancestry into a candidate.
 
-Generated next-development version preparation is not a product candidate. The
-observer skips both the signed `chore(release): prepare ...` commit and its
-two-parent integration commit. When later product work becomes qualified, the
-nearest preparation becomes a reservation: Patrol reads every path changed by
-that preparation at both exact SHAs and requires identical Git blob identities.
-A missing or stale reserved path blocks selection before the Release Cut and
-therefore before any heavy candidate build.
-
 The decision is `kungfu-buildchain-channel-candidate-decision/v1`. It records the
 source and target branches and SHAs, comparison distance, workflow paths, run
 identities and attempts, completion times, URLs, policy, and a canonical decision
@@ -88,7 +80,7 @@ The companion state is
 - `stale`: the available exact-SHA evidence pair is outside policy age; or
 - `blocked`: qualification or reconciliation failed closed.
 
-New v3 states embed the complete `kungfu-buildchain-release-train/v1` record.
+New v4 states embed the complete `kungfu-buildchain-release-train/v1` record.
 `held` states include a rooted `kungfu-buildchain-release-train-hold/v1`
 receipt with the expected cut and observed coordinates. Dev movement alone is
 not an allowed supersession cause. Legacy markers remain readable by the core