@research-engineering/agentic-proofkit 0.1.160 → 0.2.0

package/ADOPTION.md

@@ -30,18 +30,19 @@ Publisher and post-publish registry identity are admitted. GitHub Release
 assets are archive and provenance lookup, not package-manager dependency
 authority.
 
-Consumers may choose npm or Bun for installation. Both consume the same npm
-registry package identity:
+Consumers install the exact npm registry package identity:
 
 ```bash
-npm install -D @research-engineering/agentic-proofkit
-bun add -d @research-engineering/agentic-proofkit
+npm install --save-dev --save-exact @research-engineering/agentic-proofkit
+npm exec --offline -- agentic-proofkit help
 ```
 
 Release evidence still uses npm as the registry-authority CLI because Proofkit
 records npm-specific package identity, `dist.integrity`, `dist.shasum`, `npm
-pack`, and root-only registry install proof. Bun is not used as a substitute
-for those release-authority facts.
+pack`, and root-only registry install proof. A bare `agentic-proofkit` command
+is valid only when an installed package binary is already on `PATH`.
+Equivalent exact-tarball Bun execution has not been admitted, so Bun execution
+remains a non-claim.
 
 Stable authority channel ids:
 

package/README.md

@@ -24,25 +24,55 @@ packets without copying verifier logic between projects.
 The canonical registry identity is npm:
 
 ```bash
-npm install -D @research-engineering/agentic-proofkit
+npm install --save-dev --save-exact @research-engineering/agentic-proofkit
 ```
 
-Bun consumers may install the same npm registry package with Bun:
+Pre-1.0 releases may contain owner-declared breaking changes, so npm consumers
+must retain the exact saved version instead of replacing it with a version
+range.
+
+The canonical local invocation resolves only the already-installed dependency:
 
 ```bash
-bun add -d @research-engineering/agentic-proofkit
+npm exec --offline -- agentic-proofkit help
 ```
 
 npm remains the release-authority toolchain because release proof records npm
 registry identity, `dist.integrity`, `dist.shasum`, `npm pack`, and root-only
-registry install evidence. Bun is a supported consumer/developer package
-manager path, not a replacement for npm release evidence.
+registry install evidence. A bare `agentic-proofkit` command is valid when the
+package manager, script runner, or activated environment has already placed the
+installed binary on `PATH`; it is not the canonical copy-and-paste route.
+Equivalent exact-tarball Bun execution has not been admitted, so this README
+does not claim a Bun execution route.
 
 Python consumers use the Python package as a runner wrapper over the same Go
 CLI, not as a Python SDK. Python projects should still treat CLI/JSON records,
 exit codes, and package metadata as the public contract.
 
-Published Darwin binary distributions require macOS 12.0 or later.
+<!-- proofkit:platform-python:start -->
+Supported binary targets are macOS 12 or later on arm64 or x64.
+Linux manylinux 2.17 or later is supported on arm64 or x64. Windows is unsupported. The Python
+runner requires Python 3.9 or later and wraps the same Go CLI; it is not a
+Python SDK.
+
+After an exact Python package version is available from an admitted channel,
+use one complete package-manager chain:
+
+```bash
+python -m pip install agentic-proofkit==<version>
+python -m agentic_proofkit help
+```
+
+or:
+
+```bash
+uv add --dev agentic-proofkit==<version>
+uv run agentic-proofkit help
+```
+
+These conditional commands do not claim that any current version is available
+on PyPI.
+<!-- proofkit:platform-python:end -->
 
 ## Project Boundary
 
@@ -148,10 +178,10 @@ make generated invariants authoritative by itself.
 Use the CLI help route before reading source:
 
 ```bash
-agentic-proofkit help
-agentic-proofkit init
-agentic-proofkit help repo-profile-admission
-agentic-proofkit repo-profile-admission --help
+npm exec --offline -- agentic-proofkit help
+npm exec --offline -- agentic-proofkit init
+npm exec --offline -- agentic-proofkit help repo-profile-admission
+npm exec --offline -- agentic-proofkit repo-profile-admission --help
 ```
 
 Command-specific help is derived from the private command descriptor table and
@@ -175,8 +205,60 @@ value with lower transport overhead by placing the process option before the
 command:
 
 ```bash
-agentic-proofkit --json-layout compact requirement-context-slice --input slice-input.json
+npm exec --offline -- agentic-proofkit --json-layout compact requirement-context-slice --input slice-input.json
+```
+
+### First Valid Input
+
+The following marker-bounded record is a complete minimal requirement-source
+input. Its example IDs, paths, owner, invariant, and non-claims are
+caller-replaceable examples, not Proofkit-owned product meaning.
+
+<!-- proofkit:first-valid-input:start -->
+```bash
+npm exec --offline -- agentic-proofkit requirement-source-admission --input -
+```
+
+```json
+{
+  "schemaVersion": 1,
+  "sourceId": "example.requirements",
+  "specPackagePath": "docs/specs/example",
+  "overviewPath": "docs/specs/example/overview.md",
+  "requirementsPath": "docs/specs/example/requirements.v1.json",
+  "nonClaims": [
+    "This example does not approve merge or release."
+  ],
+  "requirements": [
+    {
+      "requirementId": "REQ-EXAMPLE-001",
+      "ownerId": "example.owner",
+      "invariant": "The example owner must replace this sentence with an admitted product invariant.",
+      "claimLevel": "blocking",
+      "riskClass": "medium",
+      "proofBindingRefs": [
+        "proofkit/requirement-bindings.json"
+      ],
+      "nonClaimRefs": [],
+      "nonClaims": [
+        "This example does not execute or authenticate a native witness."
+      ],
+      "lifecycle": {
+        "state": "active",
+        "replacementRequirementIds": [],
+        "evidenceRefs": []
+      },
+      "deferral": null,
+      "updatePolicy": {
+        "reviewOwnerId": "example.owner",
+        "requiresImpactDeclaration": true,
+        "requiresProofBindingReview": true
+      }
+    }
+  ]
+}
 ```
+<!-- proofkit:first-valid-input:end -->
 
 Use `secret-scan` only when the caller provides an explicit file inventory with
 content. It is a dedicated secret-like text detector for admitted inventory
@@ -187,7 +269,7 @@ For TypeScript consumers that want a small wrapper instead of hand-written
 child-process code:
 
 ```bash
-agentic-proofkit json-report-cli-adapter-source --language typescript --format json
+npm exec --offline -- agentic-proofkit json-report-cli-adapter-source --language typescript --format json
 ```
 
 The generated adapter remains caller-owned after materialization. It must be
@@ -197,10 +279,7 @@ contract; it does not become a separate public SDK or proof authority.
 | Need | Owner |
 |---|---|
 | Human orientation | This README |
-| Coding-agent startup | `AGENTS.md` |
 | Adoption and release-channel model | `ADOPTION.md` |
-| Active work ledger | `BACKLOG.md` |
-| Contribution rules | `CONTRIBUTING.md` |
 | Vulnerability reporting boundary | `SECURITY.md` |
 | Explicit boundary denials | `NON_CLAIMS.md` |
 | `LICENSE` | MIT license |

package/dist/agentic-proofkit

@@ -33,4 +33,9 @@ if [ ! -x "$binary" ]; then
   exit 1
 fi
 
+AGENTIC_PROOFKIT_LAUNCHER_PROFILE=npm_offline
+AGENTIC_PROOFKIT_PYTHON_EXECUTABLE=
+export AGENTIC_PROOFKIT_LAUNCHER_PROFILE
+export AGENTIC_PROOFKIT_PYTHON_EXECUTABLE
+
 exec "$binary" "$@"

package/docs/proofkit-contract-map.md

@@ -93,7 +93,8 @@ opt-in derived projection over the same report. This map explains the route
 families without becoming an execution, freshness, or merge decision.
 The exact route input vocabulary is machine-readable in
 `proofkit/cli-contract.v2.json` under `agent-route.inputContract`; the Go
-admission implementation and shipped CLI contract are parity-tested.
+admission implementation owns nested and semantic behavior, while the shipped
+CLI contract owns the bounded root-shape variants and their ABI digest.
 
 Formal rule:
 
@@ -113,7 +114,7 @@ Semantic context routes are `requirement-context-compose`,
 
 | State or goal | Next Proofkit route | Stop or escalation condition |
 |---|---|---|
-| The agent does not know where to start. | `init` or `init --preset fresh|code-baseline|code-audit|legacy|change-set` | Treat output as dry-run route guidance only. Stop before scanning, writing files, or making requirements authoritative. |
+| The agent does not know where to start. | `init`, or `init --preset` with `fresh`, `code-baseline`, `code-audit`, `legacy`, or `change-set` | Treat output as dry-run route guidance only. Stop before scanning, writing files, or making requirements authoritative. |
 | No admitted spec/profile exists and the caller has explicit capability observations. | `capability-map-admission`; use `trustMode: "code_baseline"` only when maintainers intentionally freeze current code, otherwise use `trustMode: "audit_from_code"`. | Stop before treating seeds as stable requirements. The consumer owns observation extraction, materialization, requirement meaning, and proof adequacy. |
 | No admitted spec/profile exists and no capability observations exist. | `scaffold-project-structure`, `adoption-workflow-plan`, or `stack-preset` | Stop before writing files; the consumer owns materialization, overwrite policy, and final requirement text. |
 | Candidate boundary is uncertain. | `adoption-doctor` or `gradual-adoption-guidance --agent-envelope` | Escalate to owner review when the boundary is advisory, ambiguous, or missing native witnesses. |

package/docs/release-process.md

@@ -42,10 +42,11 @@ Go source
   -> GitHub Release assets with checksums and SBOM for provenance lookup
 ```
 
-The committed `release/change-record.v1.json` owns the reviewed, version-bound
-declaration of the public-contract delta, migration decision, platform
-requirements, known limitations, and rollback strategy. It does not infer
-change completeness from the source diff. The repository-owned
+In a source checkout, the committed `release/change-record.v2.json` owns the
+reviewed, version-bound declaration of the public-contract delta, migration
+decision, platform requirements, known limitations, and rollback strategy. It
+is not part of the installed npm or PyPI projection and does not infer change
+completeness from the source diff. The repository-owned
 `release:manifest` tool admits that record and creates `release-manifest.json`,
 `checksums.sha256`, `metadata-checksums.sha256`, `sbom-subjects.sha256`,
 release notes, and deterministic SBOM candidate evidence from explicit package,
@@ -81,9 +82,10 @@ Before publishing a version:
 
 1. The source tree is clean.
 2. `package.json` contains the exact new version.
-3. `release/change-record.v1.json` contains the same version and explicitly
-   classifies breaking changes, additions, migration, platform requirements,
-   known limitations, and rollback.
+3. In the source checkout, `release/change-record.v2.json` contains the same
+   version, names the exact previous version and compatible or breaking change
+   class, and explicitly classifies breaking changes, additions, migration,
+   platform requirements, known limitations, and rollback.
 4. `package.json` repository, license, bin, exports, files, and publishConfig
    match the intended public package contract.
 5. The npm account has verified email and write-protective 2FA, or the package
@@ -211,9 +213,9 @@ The evidence must distinguish:
 These evidence classes are not interchangeable.
 
 Historical GitHub Releases are immutable provider state. If an older release
-metadata record names an asset that is absent from the provider release and the
-provider rejects exact backfill, the repository records that as a historical
-archive-evidence exception instead of mutating the release model around it.
+metadata record names an asset that is absent from the provider release, the
+repository records that as a historical archive-evidence exception. It does
+not attempt backfill regardless of whether the provider would permit mutation.
 Future releases must prevent recurrence by verifying the expected public asset
 set, byte-for-byte Release asset content, `release-notes.md` presence, release
 manifest and metadata checksum closure, and retained workflow evidence checksum

package/docs/specs/proofkit-consumer-infra-retirement/overview.md

@@ -41,7 +41,8 @@ approval, rollout approval, and production decisions.
 - `REQ-PROOFKIT-RETIRE-008`: adoption doctor reports classify caller-provided
   imperfect-repository migration gaps and non-passing child reports into
   advisory, failed, or blocked states and emit bounded owner-specific guidance
-  without scanning repositories or owning semantic boundary decisions.
+  without scanning repositories or owning semantic boundary decisions;
+  unresolved external prerequisites remain blocked in every adoption mode.
 - `REQ-PROOFKIT-RETIRE-009`: workspace manifest fact projection turns explicit
   caller-owned manifest records into registry-compatible workspace facts and
   planning inputs without reading manifests from disk or owning package-manager

package/docs/specs/proofkit-consumer-infra-retirement/requirements.v1.json

@@ -197,7 +197,7 @@
     {
       "requirementId": "REQ-PROOFKIT-RETIRE-008",
       "ownerId": "proofkit.consumer-infra-retirement",
-      "invariant": "Adoption doctor reports classify caller-provided imperfect-repository migration gaps, non-passing child reports, and stale current authority vocabulary facts into advisory, failed, or blocked states, and emit bounded owner-specific agent guidance without scanning repositories or owning semantic boundary decisions.",
+      "invariant": "Adoption doctor reports classify caller-provided imperfect-repository migration gaps, non-passing child reports, and stale current authority vocabulary facts into advisory, failed, or blocked states, and emit bounded owner-specific agent guidance without scanning repositories or owning semantic boundary decisions; every unresolved external prerequisite remains blocked in every adoption mode, while mode policy can relax only admitted advisory gaps.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": [

package/docs/specs/proofkit-package-boundary/overview.md

@@ -9,34 +9,63 @@ denial, and package artifact behavior only.
 - `REQ-PROOFKIT-PACKAGE-001`: the package artifact set exposes the supported
   CLI through one root package with embedded platform binaries while denying
   root imports, source imports, generated JavaScript imports, and deep internal
-  package paths as public contract.
+  package paths as public contract. Its closed machine-field inventory, bounded
+  Markdown destination grammar, README owner table, and exact README
+  command-navigation statement keep admitted routes closed over shipped entries
+  or explicit source-checkout evidence classes without claiming a complete
+  Markdown parser.
 - `REQ-PROOFKIT-PACKAGE-002`: the CLI builds deterministic reports, plans,
   generated source artifacts, and policy-admission results from explicit
   caller-owned JSON, declared no-input command parameters, or declared explicit
-  scanner scope classes. Explicit scanners consume only caller-named bounded
-  canonical files under documented fail-closed grammars rather than guessing
-  layouts or silently accepting unsupported syntax; no command executes native
-  witnesses, scans implicit repository state, decides proof freshness, or accepts
-  broad caller-supplied phrase suppressors that can hide readiness overclaims.
+  scanner scope classes. One immutable explicit launcher profile renders the
+  closed display-command and structured-argv inventory across help, preset,
+  bootstrap, project, route, workflow, and coverage surfaces without rewriting
+  caller commands or autodetecting a runner. Python executable admission
+  rejects secret-like, Unicode control, and Unicode format content without
+  disclosing it; the authored
+  CLI contract closes required input and JSON output root-shape variants,
+  exact successful-output selectors, native source sets, and requirement
+  scenarios, rejects repeated or mixed pilot selectors rather than applying
+  last-write-wins routing, then generates private help and preset projections
+  without claiming nested shape or type parity.
+  Explicit scanners consume only caller-named bounded canonical files under
+  documented fail-closed grammars, pin each referenced package sub-root before
+  reading its manifest and sources, bind every alias of one canonical source
+  to its first immutable identity, digest, and parsed result, and reject later
+  alias drift rather than guessing layouts or silently accepting unsupported
+  syntax. Explicit loopback browser opening accepts only the exact root URL and
+  one fixed platform launcher argv; no command executes native witnesses,
+  scans implicit repository state, decides proof freshness, or accepts literal or
+  strict-character-reference-encoded broad caller-supplied phrase suppressors
+  that can hide readiness overclaims.
 - `REQ-PROOFKIT-PACKAGE-003`: the root package remains installable and
-  executable by an outside consumer on the current native platform without
-  claiming registry publication.
+  executable by an outside consumer through the exact offline onboarding trace
+  on the current native platform; every generated preset command retains the
+  offline npm resolver and one exact emitted continuation is re-executed
+  without claiming registry publication.
 - `REQ-PROOFKIT-PACKAGE-004`: CI package-gate receipts used as merge evidence
   are admitted through a declared producer policy and proof-receipt shape
-  validator instead of current-build output alone.
+  validator instead of current-build output alone, and each fixed subprocess
+  verdict rejects process, JSON, or non-passed-state failure independently.
 - `REQ-PROOFKIT-PACKAGE-005`: tracked source hygiene covers each admitted text
-  language in staged blobs and the current worktree; Go formatting, static
-  analysis, test, package, and vulnerability gates remain the native
-  merge-critical quality floor and explicitly provision every runtime required
-  by a merge-critical oracle.
+  language in staged blobs and the current worktree, including every extension
+  currently present in the tracked authored browser assets, matches prohibited
+  organization identifiers only at identifier boundaries so content digests
+  cannot create false positives, and retains Go formatting, static analysis,
+  test, package, and vulnerability gates as the native merge-critical quality
+  floor with every required oracle runtime explicitly provisioned.
 - `REQ-PROOFKIT-PACKAGE-006`: Python/uv distribution is a platform wheel
   wrapper over the same Go CLI, with wheel-safe package metadata, wheel tags,
   embedded binary identity, local install smoke proof, POSIX exec
-  process-identity and signal preservation, and explicit non-claims until PyPI
-  publication.
+  process-identity and signal preservation, exact generated display and argv
+  routes through the active absolute interpreter, direct execution of the
+  root/family/leaf help chain and emitted agent-route argv with npm absent from
+  `PATH`, and an owner-checked README platform projection with explicit
+  non-claims until PyPI publication.
 - `REQ-PROOFKIT-PACKAGE-007`: package-public Markdown records release-channel
-  state only and must not embed exact per-version provider facts that are owned
-  by immutable registry, release, and manifest artifacts.
+  state only, excludes source-checkout contributor routes, closes admitted
+  package references, and must not embed exact per-version provider facts that
+  are owned by immutable registry, release, and manifest artifacts.
 
 ## Non-Claims
 

package/docs/specs/proofkit-package-boundary/requirements.v1.json

@@ -8,7 +8,7 @@
     {
       "requirementId": "REQ-PROOFKIT-PACKAGE-001",
       "ownerId": "proofkit.package-boundary",
-      "invariant": "The package artifact set exposes the supported CLI through one root package with embedded platform binaries while denying root imports, source imports, generated JavaScript imports, and deep internal package paths as public contract.",
+      "invariant": "The package artifact set exposes the supported CLI through one root package with embedded platform binaries while denying root imports, source imports, generated JavaScript imports, and deep internal package paths as public contract; every exact forbidden root name and suffix is exercised through complete root-package verification, the contract-map decision table retains exactly three cells per row, and each reference admitted through the closed machine-field inventory, bounded Markdown destination grammar, README owner table, or exact README command-navigation statement resolves to a shipped entry unless its exact field is explicitly classified as source-checkout evidence.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": [
@@ -18,7 +18,7 @@
         "NC-PROOFKIT-PACKAGE-001"
       ],
       "nonClaims": [
-        "This requirement does not claim consumer adoption, registry publication, rollout approval, or production readiness."
+        "This requirement does not claim a complete Markdown parser, discovery of unclassified code-span paths, consumer adoption, registry publication, rollout approval, or production readiness."
       ],
       "lifecycle": {
         "state": "active",
@@ -35,7 +35,7 @@
     {
       "requirementId": "REQ-PROOFKIT-PACKAGE-002",
       "ownerId": "proofkit.package-boundary",
-      "invariant": "The CLI builds deterministic reports, plans, generated source artifacts, and policy-admission results from explicit caller-owned JSON, declared no-input command parameters, or declared explicit scanner scope classes; explicit scanners consume only caller-named bounded canonical files under documented fail-closed grammars rather than guessing layouts or silently accepting unsupported syntax, and no command executes native witnesses, scans implicit repository state, decides proof freshness, or accepts broad caller-supplied phrase suppressors that can hide readiness overclaims.",
+      "invariant": "The CLI builds deterministic reports, plans, generated source artifacts, and policy-admission results from explicit caller-owned JSON, declared no-input command parameters, or declared explicit scanner scope classes; one immutable launcher-profile value renders every Proofkit-owned display command and structured argv field in the closed generated-command inventory across root, family, and leaf help, stack preset, bootstrap, project structure, agent route, adoption workflow, and requirement coverage surfaces while preserving caller-owned command bytes; launcher admission accepts only path, offline npm, or absolute-interpreter Python-module routes, rejects Python executable values containing report-visible secret-like, Unicode control, or Unicode format content without disclosing rejected values, and performs no ambient runner autodetection; the authored CLI contract closes every required-input and JSON-output root-shape variant declaration, rejects repeated or mixed pilot selectors instead of applying last-write-wins routing, binds each root-distinct output selector to its exact successful-output test, native source-path set, and requirement scenario, and generates private help and stack-preset projections without replacing native admission; explicit scanners consume only caller-named bounded canonical files under documented fail-closed grammars, pin each referenced package sub-root before reading its manifest and sources, bind every lexical alias of one canonical source route to the immutable identity, digest, and parsed result of its first admission, and reject later alias drift rather than guessing layouts or silently accepting unsupported syntax; explicit loopback browser opening accepts only the exact root URL and dispatches one fixed platform launcher argv; no command executes native witnesses, scans implicit repository state, decides proof freshness, or accepts literal or strict-character-reference-encoded broad caller-supplied phrase suppressors that can hide readiness overclaims.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": [
@@ -45,7 +45,7 @@
         "NC-PROOFKIT-PACKAGE-002"
       ],
       "nonClaims": [
-        "This requirement does not claim native witness execution, producer authentication, proof freshness, or merge approval."
+        "This requirement does not claim nested CLI field shape, scalar type, collection cardinality, nullability, a complete Markdown parser, native witness execution, installation of source-checkout witness files, runtime JSON Schema validation, producer authentication, proof freshness, or merge approval."
       ],
       "lifecycle": {
         "state": "active",
@@ -62,7 +62,7 @@
     {
       "requirementId": "REQ-PROOFKIT-PACKAGE-003",
       "ownerId": "proofkit.package-boundary",
-      "invariant": "The root package remains installable and executable by an outside consumer on the current native platform without claiming registry publication.",
+      "invariant": "The exact local root-package tarball remains installable and executable by an outside consumer on the current native platform through npm exec --offline, with a continuous root-help to family to stack-preset to every exact generated preset continuation and first-valid-input onboarding trace, including successful re-execution of one emitted self-continuation without network fallback, without claiming registry publication.",
       "claimLevel": "blocking",
       "riskClass": "medium",
       "proofBindingRefs": [
@@ -89,7 +89,7 @@
     {
       "requirementId": "REQ-PROOFKIT-PACKAGE-004",
       "ownerId": "proofkit.package-boundary",
-      "invariant": "CI package-gate receipts used as merge evidence are admitted through a declared producer policy and proof-receipt shape validator instead of current-build output alone.",
+      "invariant": "CI package-gate receipts used as merge evidence are admitted through a declared producer policy and proof-receipt shape validator instead of current-build output alone, and every fixed Proofkit subprocess verdict independently rejects process failure, invalid JSON, and any non-passed state.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": [
@@ -116,7 +116,7 @@
     {
       "requirementId": "REQ-PROOFKIT-PACKAGE-005",
       "ownerId": "proofkit.package-boundary",
-      "invariant": "Tracked source hygiene covers every admitted project text language in both staged blobs and the current worktree, while Go formatting, static analysis, vet, test, package artifact, and vulnerability gates remain the native merge-critical quality floor and explicitly provision every runtime required by a merge-critical oracle.",
+      "invariant": "Tracked source hygiene covers every admitted project text language in both staged blobs and the current worktree, matches prohibited organization identifiers only at identifier boundaries so content digests cannot create false positives, while Go formatting, static analysis, vet, test, package artifact, and vulnerability gates remain the native merge-critical quality floor and explicitly provision every runtime required by a merge-critical oracle.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": [
@@ -143,7 +143,7 @@
     {
       "requirementId": "REQ-PROOFKIT-PACKAGE-006",
       "ownerId": "proofkit.package-boundary",
-      "invariant": "Python/uv distribution is a platform wheel wrapper over the same Go CLI, with wheel-safe package metadata, wheel tags, embedded binary identity, local install smoke proof, POSIX exec process-identity and signal preservation, and explicit non-claims until PyPI publication.",
+      "invariant": "Python/uv distribution is a platform wheel wrapper over the same Go CLI, with wheel-safe package metadata, wheel tags, embedded binary identity, exact wheel-set version, uniqueness, presence, and SHA closure, local install smoke proof, POSIX exec process-identity and signal preservation, generated display and argv routes bound to the absolute active interpreter plus -m agentic_proofkit, successful direct-argv re-execution of an exact emitted self-continuation, the complete root-help to family-help to leaf-help chain, and an exact emitted agent-route argv with npm absent from PATH, and a marker-bounded README projection of the owned Python and platform matrix with explicit non-claims until PyPI publication.",
       "claimLevel": "blocking",
       "riskClass": "medium",
       "proofBindingRefs": [
@@ -170,7 +170,7 @@
     {
       "requirementId": "REQ-PROOFKIT-PACKAGE-007",
       "ownerId": "proofkit.package-boundary",
-      "invariant": "Package-public Markdown records release-channel completion state only and must not embed exact package versions, source refs, provider run URLs, registry tarball URLs, integrity strings, shasums, or other per-version release facts that are owned by immutable registry records, GitHub Release artifacts, and generated release manifests.",
+      "invariant": "Package-public Markdown records release-channel completion state only, excludes contributor-only governance and backlog routes from the npm artifact, closes Markdown and admitted machine references over shipped entries with explicit source-checkout evidence exceptions, and must not embed exact package versions, source refs, provider run URLs, registry tarball URLs, integrity strings, shasums, or other per-version release facts that are owned by immutable registry records, GitHub Release artifacts, and generated release manifests.",
       "claimLevel": "blocking",
       "riskClass": "medium",
       "proofBindingRefs": [

package/docs/specs/proofkit-spec-proof-core/overview.md

@@ -13,7 +13,9 @@ execution receipts, and merge policy.
 
 - `REQ-PROOFKIT-SPEC-001`: requirement source admission validates structured
   `REQ-*` records and source-package shape without owning requirement meaning
-  or scanning overview prose as authority.
+  or scanning overview prose as authority; one shipped, marker-bounded example
+  is parsed as bounded expansion-free literal shell words and executed through
+  the installed current product as a first valid input.
 - `REQ-PROOFKIT-SPEC-002`: requirement proof binding reports validate
   caller-owned requirement-to-witness mappings, require compact scenarios to be
   admitted `surface_id::stable_anchor` identities, require compact witness
@@ -58,9 +60,11 @@ execution receipts, and merge policy.
   reading sources, rendering views, or owning requirement/proof semantics.
 - `REQ-PROOFKIT-SPEC-009`: requirement spec tree views render admitted
   caller-owned hierarchy through shared safe browser document fragments,
-  deterministic CLI JSON, Markdown, HTML, explicit output paths, and loopback
-  browser serving without accepting caller-owned raw HTML or making rendered
-  output authoritative.
+  deterministic CLI JSON, Markdown, HTML, repository-confined same-parent
+  atomic output replacement after final destination-parent plus
+  temporary-object identity, mode, and content admission, and loopback browser
+  serving with one exact supported-view vocabulary without accepting
+  caller-owned raw HTML or making rendered output authoritative.
 - `REQ-PROOFKIT-SPEC-010`: requirement impact input composition converts
   caller-owned base/current requirement sources, single-current-binding compact
   proof contracts, changed-path facts, generated-artifact policy, local
@@ -69,8 +73,11 @@ execution receipts, and merge policy.
   impact evaluator.
 - `REQ-PROOFKIT-SPEC-011`: adoption contract envelope admission validates a
   complete caller-owned aggregate adoption envelope, selects one child route
-  through orthogonal CLI flags, and delegates to existing child command
-  contracts without becoming a second adoption readiness policy.
+  through orthogonal CLI flags, rejects repeated single-value mode or pilot
+  selectors and an explicitly empty pilot value, binds its union output to the
+  exact successful public-CLI root witness and native owner, and delegates to
+  existing child command contracts without becoming a second adoption readiness
+  policy.
 - `REQ-PROOFKIT-SPEC-012`: requirement authoring plans package caller-provided
   design, implementation, PR, code, test, and clarification facts into
   candidate-only requirement updates, delegate structural checks to requirement
@@ -94,27 +101,32 @@ execution receipts, and merge policy.
   and emits only bounded candidate requirements, bindings, or owner guidance.
 - `REQ-PROOFKIT-SPEC-018`: an authored command-family catalog covers every
   public CLI command exactly once, deterministically generates the private
-  runtime navigation projection, and adds opt-in family help while preserving
-  existing help invocation forms, process channels, no-input behavior, and leaf
-  dispatch; descriptor and help truth remains owned by `REQ-PROOFKIT-QUALITY-004`.
+  runtime navigation projection, adds token-bounded root discovery, and projects
+  exact stack-preset IDs into help and diagnostics while preserving existing
+  help invocation forms, process channels, no-input behavior, and leaf dispatch;
+  descriptor and help truth remains owned by `REQ-PROOFKIT-QUALITY-004`.
 - `REQ-PROOFKIT-SPEC-019`: explicit catalogs compose content-bound semantic
-  context snapshots through existing source, tree, proof, and coverage owners
-  without ambient repository discovery.
+  schema-v2 context snapshots with exact expected-digest coverage through
+  existing source, tree, proof, and coverage owners, with strict v1 adaptation
+  and without ambient repository discovery.
 - `REQ-PROOFKIT-SPEC-020`: bounded context queries select parent-before-child,
   role-aware, reference-closed semantic subsets by stable identity and report
   each active bound without treating bounded absence as source absence.
 - `REQ-PROOFKIT-SPEC-021`: the loopback workspace progressively presents
   immutable context, semantic diff, traceability trust states, authority
-  boundaries, and non-claims, then emits a bounded source-bound question packet
-  only after explicit user submission.
+  boundaries, one exact loopback root URL through one fixed platform launcher
+  argv, visible loading and sanitized terminal failure states through native
+  document semantics, and non-claims, then emits a bounded source-bound question
+  packet from a visibly labelled region only after explicit user submission.
 - `REQ-PROOFKIT-SPEC-022`: semantic diff compares admitted requirement fields
-  by owner-declared scalar, set, map, and lifecycle semantics, covers entity
-  additions and removals, and remains closed under output re-admission.
+  by owner-declared scalar, set, map, and lifecycle semantics through schema-v2
+  records and strict v1 adapters, covers entity additions and removals, and
+  remains closed under output re-admission.
 - `REQ-PROOFKIT-SPEC-023`: traceability graph input schema v2 preserves
   specification, proof, code traceability, and native execution as distinct
-  evidence planes and accepts code topology only as explicit caller-owned input
-  with source-digest, parent-edge, abstraction-order, and pre-materialization
-  budget closure.
+  evidence planes, consumes the normalized v1/v2 context boundary, and accepts
+  code topology only as explicit caller-owned input with source-digest,
+  parent-edge, abstraction-order, and pre-materialization budget closure.
 
 ## Non-Claims