@research-engineering/agentic-proofkit 0.1.157 → 0.1.159

package/CONTRIBUTING.md

@@ -25,10 +25,16 @@ admission, and rollout approval belong in consuming repositories.
 Run before proposing a non-trivial change:
 
 ```bash
+npm ci --ignore-scripts
+npx playwright install chromium firefox webkit
 npm run check
 git diff --check
 ```
 
+The browser engine installation is a one-time prerequisite for the pinned
+rendered-runtime gate. CI installs the same engines with their Linux system
+dependencies before running that gate.
+
 If your local project uses Bun, `bun run check` is acceptable as a convenience
 runner only when it invokes the same scripts and leaves `npm run check`
 equivalent. Release and package-authority proof remains npm-owned.

package/README.md

@@ -154,7 +154,7 @@ agentic-proofkit repo-profile-admission --help
 
 Command-specific help is derived from the private command descriptor table and
 does not read stdin. The full machine-readable command inventory remains
-`proofkit/cli-contract.v1.json`; the human route map is
+`proofkit/cli-contract.v2.json`; the human route map is
 `docs/proofkit-contract-map.md`.
 
 | Repository state | Minimal first route | Stop condition |
@@ -165,6 +165,16 @@ does not read stdin. The full machine-readable command inventory remains
 | Current code must be audited before it becomes a contract | `capability-map-admission` with `trustMode: "audit_from_code"` | Stop at owner questions and candidate-only records |
 | Legacy repository has local proof infrastructure | `migration-parity-admission`, then `migration-plan` | Stop before deleting local proof owners without parity evidence |
 | A change set needs bounded checks | `changed-path-set`, optional `impact`, then `selective-gate-plan` and `selective-gate-evidence` | Stop on unknown scope, missing routes, or stale receipts |
+| An agent needs only one specification subtree | `requirement-context-compose --repo-root . --input context-catalog.json`, then `requirement-context-slice` | Stop before treating a bounded slice as complete repository truth |
+| A human needs semantic navigation, comparison, or traceability | `requirement-browser-server --view workspace --serve` over an admitted workspace input | Browser output, annotations, diff, and graph remain derived and non-authoritative |
+
+JSON commands default to readable output. Agents can request the same JSON
+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
+```
 
 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

package/docs/proofkit-contract-map.md

@@ -9,7 +9,7 @@ Owner: `proofkit`.
 This map helps consuming repositories choose the smallest Proofkit CLI command
 or JSON contract without loading the full README or source tree. It is not an
 exhaustive schema reference. The canonical command inventory is
-`proofkit/cli-contract.v1.json`.
+`proofkit/cli-contract.v2.json`.
 
 Formal rule:
 
@@ -47,7 +47,7 @@ owner boundaries. It is not a second command-family inventory.
 | Receipts and producers | `proof-receipt-admission`, `receipt-producer-admission`, `receipt-currentness-scope`, `receipt-trust-class`, `producer-policy-self-proof` | receipt sets, producer policy, scope/currentness facts, trust classes | receipt shape, producer/receipt compatibility, self-proof diagnostics | producer authentication, freshness policy, CI trust roots | receipt/provenance report |
 | Release and deployment | `release-authority`, `external-consumer`, `registry-consumer-proof-input-compose`, `registry-consumer`, `deployment-evidence-admission`, `completion-criteria`, `branch-authority`, `readiness-closeout` | package facts, tarball/registry facts, explicit primitive registry/install/smoke facts, deployment evidence, criteria, branch facts | artifact/channel boundary checks, registry-consumer input composition, release diagnostics, falsifiable criteria shape | package publication, registry fetch, package-manager execution, deployment, rollback, approval | composed input, release/deployment/readiness report |
 | Supply-chain and quality | `self-check`, release workflow, `npm run release:sbom`, `npm run self:coverage`, `npm run go:actionlint`, `npm run go:bench` | release artifacts, source workflows, specs, bindings, witness plans, explicit benchmark invocation | deterministic self-check report shape, SBOM candidate evidence, coverage metrics, workflow lint routing, benchmark entrypoints | public-source provenance, vulnerability triage, license approval, CI run admission, release approval | self-check report, SBOM, metrics report, CI signal, or benchmark output |
-| Repository structure | `repo-profile-admission`, `workspace-manifest-facts`, `workspace-registry`, `workspace-changed-package-plan`, `workspace-shard-partition`, `typescript-public-api-surfaces`, `text-policy`, `secret-scan`, `package-runtime-dependency-admission` | explicit repo/profile facts, caller-owned manifest records, caller-owned roots, caller-owned text file inventories, optional `environmentClassPolicies` tuples | structural admission, manifest-to-workspace fact projection, workspace graph projections, TypeScript package public API checks, text policy admission, explicit-inventory secret-like text detection, shard plans | repository freshness, git/file discovery, command policy, package manager truth, provider secret scanning | structural, fact, policy, or planning report |
+| Repository structure | `repo-profile-admission`, `workspace-manifest-facts`, `workspace-registry`, `workspace-changed-package-plan`, `workspace-shard-partition`, `typescript-public-api-surfaces`, `text-policy`, `secret-scan`, `package-runtime-dependency-admission` | explicit repo/profile facts, caller-owned manifest records, caller-owned roots, caller-owned text file inventories, explicit TypeScript package-manifest and per-condition source paths, optional `environmentClassPolicies` tuples | structural admission, manifest-to-workspace fact projection, workspace graph projections, bounded TypeScript package public API checks over referenced files, text policy admission, explicit-inventory secret-like text detection, shard plans | repository freshness, git/file discovery, compiler output provenance, command policy, package manager truth, provider secret scanning | structural, fact, policy, or planning report |
 | Custom and generated artifacts | `custom-rule-boundary`, `document-lifecycle-boundary`, `rendered-artifact-freshness`, `conformance-profile`, `json-report-cli-adapter-source`, `witness-plan`, `witness-scheduler-plan` | custom rule metadata, document lifecycle records, artifact digests, profile manifests, command metadata, adapter language | boundary checks, generated-view freshness shape, deterministic adapter source generation, scheduler metadata checks | rule execution, document meaning, cache contents, CI scheduling, committed generated-source freshness | boundary report, generated source artifact, or scheduler report |
 | CLI metadata | `help` | optional command name or help flag | built-in command catalog and help text routing | command selection, semantic proof, freshness, merge policy | text help only |
 
@@ -92,7 +92,7 @@ returns deterministic JSON from explicit caller-owned facts; the envelope is an
 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.v1.json` under `agent-route.inputContract`; the Go
+`proofkit/cli-contract.v2.json` under `agent-route.inputContract`; the Go
 admission implementation and shipped CLI contract are parity-tested.
 
 Formal rule:
@@ -107,6 +107,10 @@ goal plus caller-owned state
 
 Decision tree:
 
+Semantic context routes are `requirement-context-compose`,
+`requirement-context-slice`, `requirement-semantic-diff`, and
+`requirement-traceability-graph`.
+
 | 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. |
@@ -116,14 +120,15 @@ Decision tree:
 | Temporary external design, implementation-plan, PR, code, or test observations may contain durable requirements. | `requirement-authoring-plan` | Treat output as candidate-only; stop before writing `requirements.v1.json`, retaining temporary documents, or claiming requirement meaning. |
 | Requirement records exist. | `requirement-source-admission`; use `requirement-source-transition` for lifecycle changes. | Escalate when blocking requirements lack proof routes or lifecycle replacement ids are incomplete. |
 | Humans or agents need meta/module/submodule navigation. | `requirement-spec-tree`, then `requirement-spec-tree-view` or `requirement-browser-server --view spec-tree` from the same caller-owned tree input. | Stop before inferring hierarchy from paths. The consumer owns source hierarchy; CLI/browser outputs remain presentation only and are not committed by default. |
+| An agent needs a bounded semantic subset instead of whole specification files. | `requirement-context-compose --repo-root <caller-selected-root>` over an explicit catalog, then `requirement-context-slice` over the materialized snapshot. | The snapshot and slice are content-bound derived projections. Stop before inferring hierarchy, scanning ambient paths, treating omissions as absence, or promoting the slice to requirement, proof, freshness, or merge authority. |
 | Overview prose may contain durable claims. | `spec-overview-claims` | Escalate when normative claims are not tied to `REQ-*` records. |
 | Requirements have no verified proof route. | `requirement-bindings`, `witness-plan` from either an explicit `witness_command_catalog` or a complete `binding_witness_plan_input`, `proof-slice`, or `requirement-proof-resolver` | Stop before claiming proof adequacy; native witness semantics stay with the consumer. A binding-derived witness plan still needs caller-owned vocabulary and conservative command policy. |
 | Tests or proof evidence need inventory. | `test-evidence-inventory`; use `--projection discovery-draft` only for explicit discovered-test facts, then `requirement-coverage-input-compose` when an aggregate `coverage_compose_input` exists, then `requirement-coverage-view` when a `coverage_view_input` exists | Compose only from explicit caller-owned facts. Discovery drafts are candidate-only and cannot close coverage. Use `failureClassifications[]`, `warningClassifications[]`, and `agentActionPlan[]` for machine routing. Escalate when tests are route-only, weak-oracle, unbound, or outside the caller-owned coverage universe. |
 | A change set is known. | `changed-path-set`, optionally `requirement-impact-input-compose`, `impact`, then `selective-gate-plan --agent-envelope` | Raw `knownChangedPaths` in `agent-route` are diagnostic only. Materialize a caller-owned `changed_path_set`, compose a caller-owned `impact_input` before `impact`, and compose a caller-owned `selective_gate_plan_input` before `selective-gate-plan`. Use `scanObligation` to name whether a `text-policy`, `secret-scan`, or caller-owned external scanner is required. Fail closed on unknown scope, dynamic edges, missing owner routes, unbound proof-like paths, or full-gate escalation. |
 | Caller-owned file contents need secret-like text detection. | `secret-scan` | Provide explicit sorted file inventory with content. Stop before claiming repository-wide discovery, credential validity, provider ingestion, merge readiness, or replacement of GitHub secret scanning. |
-| Does a TypeScript package public API match a caller-owned manifest? | `agent-route` with `goal: "verify_typescript_public_api"` and explicit `typescript_public_api_manifest` plus `typescript_public_api_repo_root`, then `typescript-public-api-surfaces --repo-root <caller-selected-root>` | This is an explicit filesystem scanner. Stop before guessing `repo-root`, claiming checkout freshness, package-manager truth, or merge readiness. |
+| Does a TypeScript package public API match a caller-owned manifest? | `agent-route` with `goal: "verify_typescript_public_api"` and explicit `typescript_public_api_manifest` plus `typescript_public_api_repo_root`, then `typescript-public-api-surfaces --repo-root <caller-selected-root>` | The manifest must name each referenced `package.json`, sorted-unique export conditions, and a non-JSX `.ts`, `.mts`, or `.cts` `sourcePath` whose canonical target has the same admitted extension class. The bounded scanner accepts only the fail-closed export grammar in `proofkit/cli-contract.v2.json`; it does not parse unrestricted TypeScript or TSX, infer conventional layouts, or prove compiler output provenance, checkout freshness, package-manager truth, or merge readiness. |
 | Receipts are available for planned checks. | `selective-gate-evidence --agent-envelope`; then materialize a caller-owned `obligation_decision_input` from the evidence output plus command routes, currentness, and trust facts; then run `selective-gate-obligation-decision-input`; then materialize the resulting `obligation_decision` input and run `obligation-decision --agent-envelope` | Escalate on missing, stale, invalid, untrusted, blocked, unavailable, or unknown-scope evidence. |
-| Human inspection is needed. | `requirement-source-view`, `requirement-proof-view`, `requirement-coverage-view`, `requirement-spec-tree-view`, or `requirement-browser-server` | `agent-route` emits browser commands as plan-only by default. Use `browserMode: "serve_local_view"` for `--serve` and `openBrowser: true` for `--open`. Rendered HTML and Markdown are presentation only unless the consumer admits a tracked artifact freshness gate. |
+| Human inspection, semantic comparison, or traceability navigation is needed. | `requirement-source-view`, `requirement-proof-view`, `requirement-coverage-view`, `requirement-spec-tree-view`, `requirement-semantic-diff`, `requirement-traceability-graph`, or `requirement-browser-server` | Semantic diff compares admitted owner fields rather than lines. Traceability keeps specification, proof, code, and native execution evidence planes separate. Browser and rendered outputs remain presentation only unless the consumer admits a tracked artifact freshness gate. |
 | Temporary external document lifecycle facts, generated views, or rendered views need authority classification. | `document-lifecycle-boundary` | Treat lifecycle records as caller-owned metadata. Temporary design docs and implementation plans are not retained repository authority unless rewritten into deterministic specs, proof bindings, tests, package-public docs, or backlog rows. |
 | A JavaScript/TypeScript consumer needs less wrapper code. | `json-report-cli-adapter-source --language typescript --format json` | Generated adapter source is caller-owned after materialization. The consumer still owns package pin, binary path, repo paths, local policy, and freshness proof. It is a CLI runner adapter, not a separate SDK authority. |
 | A Python consumer needs Proofkit from Python tooling. | Install the Python package when available and invoke the same CLI/JSON contract. | The Python package is a runner wrapper over the Go CLI, not a Python SDK or alternate schema owner. |
@@ -133,7 +138,7 @@ Decision tree:
 
 ## Routing Rules
 
-1. Start from `proofkit/cli-contract.v1.json` when a machine needs the exact
+1. Start from `proofkit/cli-contract.v2.json` when a machine needs the exact
    command, flags, input mode, output mode, scope class, or `agent-route` input
    contract.
 2. Start from this map when a human or agent only needs the correct command

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

@@ -13,22 +13,27 @@ denial, and package artifact behavior only.
 - `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 without executing native witnesses, scanning implicit
-  repository state, deciding proof freshness, or accepting broad caller-supplied
-  phrase suppressors that can hide readiness overclaims.
+  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.
 - `REQ-PROOFKIT-PACKAGE-003`: the root package remains installable and
   executable by an outside consumer on the current native platform 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.
-- `REQ-PROOFKIT-PACKAGE-005`: the Go source, static analysis, package gate,
-  and vulnerability gates remain the native merge-critical quality floor for
-  the current Proofkit source tree.
+- `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.
 - `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, and explicit non-claims
-  until PyPI publication.
+  embedded binary identity, local install smoke proof, POSIX exec
+  process-identity and signal preservation, and 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.

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

@@ -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 without executing native witnesses, scanning implicit repository state, deciding proof freshness, or accepting 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; 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.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": [
@@ -116,7 +116,7 @@
     {
       "requirementId": "REQ-PROOFKIT-PACKAGE-005",
       "ownerId": "proofkit.package-boundary",
-      "invariant": "The Go source, formatting, static analysis, vet, test, package artifact, and vulnerability gates remain the native merge-critical quality floor for the current Proofkit source tree.",
+      "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.",
       "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, 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, local install smoke proof, POSIX exec process-identity and signal preservation, and explicit non-claims until PyPI publication.",
       "claimLevel": "blocking",
       "riskClass": "medium",
       "proofBindingRefs": [

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

@@ -25,16 +25,18 @@ execution receipts, and merge policy.
 - `REQ-PROOFKIT-SPEC-003`: witness planning accepts caller-owned structured
   command metadata, scheduler constraints, environment classes, and
   binding-derived command projections only through admitted witness vocabulary
-  and conservative safe argv policy, without executing commands or selecting
-  repository policy.
+  and conservative safe argv policy. Self-hosting bindings and witness plans
+  preserve command ids, argv, and environment classes without executing
+  commands or selecting repository policy.
 - `REQ-PROOFKIT-SPEC-004`: selective planning and selective evidence reports
-  keep changed-path facts, planned commands, receipts, evidence class,
-  producer-admission state, and obligation candidates explicit, keep merge
-  approval consumer-owned, and fail closed for unknown or unmatched proof
-  inputs.
+  keep canonical changed-path facts, resolvable agent references, planned
+  commands, receipts, evidence class, producer-admission state, and obligation
+  candidates explicit, keep merge approval consumer-owned, and fail closed for
+  unknown or unmatched proof inputs.
 - `REQ-PROOFKIT-SPEC-005`: rendered proof views and agent envelopes remain
-  bounded, derived presentations over structured source and never become
-  canonical proof or requirement authority.
+  bounded, reference-closed derived presentations over structured source,
+  count each semantic omission once, and never become canonical proof or
+  requirement authority.
 - `REQ-PROOFKIT-SPEC-006`: test evidence inventory, explicit test-discovery
   draft projections, proof-binding-derived inventory projections, normalized
   inventory projections, coverage-view input composition, and requirement
@@ -95,6 +97,21 @@ execution receipts, and merge policy.
   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`.
+- `REQ-PROOFKIT-SPEC-019`: explicit catalogs compose content-bound semantic
+  context snapshots through existing source, tree, proof, and coverage owners
+  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.
+- `REQ-PROOFKIT-SPEC-022`: semantic diff compares admitted requirement fields
+  by owner-declared scalar, set, and map semantics rather than textual order.
+- `REQ-PROOFKIT-SPEC-023`: traceability graphs preserve specification, proof,
+  code traceability, and native execution as distinct evidence planes and
+  accept code topology only as explicit caller-owned input.
 
 ## Non-Claims
 

package/docs/specs/proofkit-spec-proof-core/requirements.v1.json

@@ -62,7 +62,7 @@
     {
       "requirementId": "REQ-PROOFKIT-SPEC-003",
       "ownerId": "proofkit.spec-proof-core",
-      "invariant": "Witness planning accepts caller-owned structured command metadata, scheduler constraints, environment classes, and binding-derived command projections only through admitted witness vocabulary and conservative safe argv policy, without executing commands or selecting repository policy.",
+      "invariant": "Witness planning accepts caller-owned structured command metadata, scheduler constraints, environment classes, and binding-derived command projections only through admitted witness vocabulary and conservative safe argv policy; self-hosting requirement bindings and witness plans preserve the same command ids, argv, and environment classes without executing commands or selecting repository policy.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": [
@@ -89,7 +89,7 @@
     {
       "requirementId": "REQ-PROOFKIT-SPEC-004",
       "ownerId": "proofkit.spec-proof-core",
-      "invariant": "Selective planning and selective evidence reports keep changed-path facts, planned commands, receipts, evidence class, producer-admission state, and obligation candidates explicit, keep merge approval consumer-owned, and fail closed for unknown or unmatched proof inputs.",
+      "invariant": "Selective planning and selective evidence reports keep canonical changed-path facts, resolvable agent references, planned commands, receipts, evidence class, producer-admission state, and obligation candidates explicit, keep merge approval consumer-owned, and fail closed for unknown or unmatched proof inputs.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": [
@@ -116,7 +116,7 @@
     {
       "requirementId": "REQ-PROOFKIT-SPEC-005",
       "ownerId": "proofkit.spec-proof-core",
-      "invariant": "Rendered proof views and agent envelopes remain bounded, derived presentations over structured source and never become canonical proof or requirement authority.",
+      "invariant": "Rendered proof views and agent envelopes remain bounded, reference-closed derived presentations over structured source, count each semantic omission once, and never become canonical proof or requirement authority.",
       "claimLevel": "blocking",
       "riskClass": "medium",
       "proofBindingRefs": [
@@ -490,6 +490,71 @@
         "requiresImpactDeclaration": true,
         "requiresProofBindingReview": true
       }
+    },
+    {
+      "requirementId": "REQ-PROOFKIT-SPEC-019",
+      "ownerId": "proofkit.spec-proof-core",
+      "invariant": "Requirement context composition reads only caller-selected repository-relative catalog paths through a confined filesystem root, admits each source through its semantic owner, records current and optional expected digests, and emits one bounded content-bound derived snapshot without ambient scanning or new requirement, proof, coverage, freshness, or merge authority.",
+      "claimLevel": "blocking",
+      "riskClass": "high",
+      "proofBindingRefs": ["proofkit/requirement-bindings.json"],
+      "nonClaimRefs": ["NC-PROOFKIT-SPEC-019"],
+      "nonClaims": ["This requirement does not claim ambient repository discovery, later-checkout freshness, requirement meaning, proof adequacy, native witness execution, merge approval, release approval, rollout approval, or production readiness."],
+      "lifecycle": {"state": "active", "replacementRequirementIds": [], "evidenceRefs": []},
+      "deferral": null,
+      "updatePolicy": {"reviewOwnerId": "proofkit.spec-proof-core", "requiresImpactDeclaration": true, "requiresProofBindingReview": true}
+    },
+    {
+      "requirementId": "REQ-PROOFKIT-SPEC-020",
+      "ownerId": "proofkit.spec-proof-core",
+      "invariant": "Requirement context slicing strictly re-admits snapshot identity, applies closed profiles and intersecting stable-id selectors under deterministic bounds, rejects unknown explicit targets, retains selected ancestors before descendants, preserves source-role and lifecycle reference closure, and distinctly reports depth, node-count, and requirement-count omissions without treating bounded absence as source absence.",
+      "claimLevel": "blocking",
+      "riskClass": "high",
+      "proofBindingRefs": ["proofkit/requirement-bindings.json"],
+      "nonClaimRefs": ["NC-PROOFKIT-SPEC-020"],
+      "nonClaims": ["This requirement does not claim source completeness outside the admitted snapshot, product meaning, proof freshness, native execution, merge approval, release approval, rollout approval, or production readiness."],
+      "lifecycle": {"state": "active", "replacementRequirementIds": [], "evidenceRefs": []},
+      "deferral": null,
+      "updatePolicy": {"reviewOwnerId": "proofkit.spec-proof-core", "requiresImpactDeclaration": true, "requiresProofBindingReview": true}
+    },
+    {
+      "requirementId": "REQ-PROOFKIT-SPEC-021",
+      "ownerId": "proofkit.spec-proof-core",
+      "invariant": "The loopback requirement workspace visibly preserves presentation-only authority boundaries, non-claims, snapshot and baseline identity, and trust-significant graph states while rendering immutable admitted context, optional semantic diff, and optional traceability graph through exact allowlisted routes, a per-process capability, same-origin handoff admission, source-digest and JSON-pointer anchors, Unicode code-point quote coordinates, bounded browser-session question packets after explicit UI submission across the admitted tree domain subject to explicit packet byte bounds, and terminal one-shot concurrent session semantics without persistence, command execution, provider access, or authority promotion.",
+      "claimLevel": "blocking",
+      "riskClass": "critical",
+      "proofBindingRefs": ["proofkit/requirement-bindings.json"],
+      "nonClaimRefs": ["NC-PROOFKIT-SPEC-021"],
+      "nonClaims": ["This requirement does not authenticate the surrounding browser profile or operating-system user and does not claim remote access, annotation persistence, agent execution, provider delivery, proof freshness, merge approval, release approval, rollout approval, branded Safari behavior, or production readiness."],
+      "lifecycle": {"state": "active", "replacementRequirementIds": [], "evidenceRefs": []},
+      "deferral": null,
+      "updatePolicy": {"reviewOwnerId": "proofkit.spec-proof-core", "requiresImpactDeclaration": true, "requiresProofBindingReview": true}
+    },
+    {
+      "requirementId": "REQ-PROOFKIT-SPEC-022",
+      "ownerId": "proofkit.spec-proof-core",
+      "invariant": "Requirement semantic diff compares two admitted context snapshots by stable requirement identity and owner-declared scalar, set, and map field classes, producing deterministic added, removed, and modified facts without textual diff, inferred move semantics, or authority over requirement meaning.",
+      "claimLevel": "blocking",
+      "riskClass": "medium",
+      "proofBindingRefs": ["proofkit/requirement-bindings.json"],
+      "nonClaimRefs": ["NC-PROOFKIT-SPEC-022"],
+      "nonClaims": ["This requirement does not claim textual equivalence, inferred moves, product meaning, proof freshness, merge approval, release approval, rollout approval, or production readiness."],
+      "lifecycle": {"state": "active", "replacementRequirementIds": [], "evidenceRefs": []},
+      "deferral": null,
+      "updatePolicy": {"reviewOwnerId": "proofkit.spec-proof-core", "requiresImpactDeclaration": true, "requiresProofBindingReview": true}
+    },
+    {
+      "requirementId": "REQ-PROOFKIT-SPEC-023",
+      "ownerId": "proofkit.spec-proof-core",
+      "invariant": "Requirement traceability graph deterministically projects admitted specification and proof topology plus explicit caller-owned code topology while preserving specification, proof, code traceability, and native execution as distinct evidence planes and rejecting dangling topology references.",
+      "claimLevel": "blocking",
+      "riskClass": "high",
+      "proofBindingRefs": ["proofkit/requirement-bindings.json"],
+      "nonClaimRefs": ["NC-PROOFKIT-SPEC-023"],
+      "nonClaims": ["This requirement does not infer code topology, line or branch coverage, native execution, proof freshness, merge approval, release approval, rollout approval, or production readiness."],
+      "lifecycle": {"state": "active", "replacementRequirementIds": [], "evidenceRefs": []},
+      "deferral": null,
+      "updatePolicy": {"reviewOwnerId": "proofkit.spec-proof-core", "requiresImpactDeclaration": true, "requiresProofBindingReview": true}
     }
   ],
   "nonClaims": [

package/docs/specs/proofkit-supply-chain-quality/overview.md

@@ -22,7 +22,8 @@ vulnerability absence, or consumer rollout safety by itself.
   fuzzing side-effecting CLI or filesystem flows.
 - `REQ-PROOFKIT-QUALITY-004`: public CLI ABI has a small golden corpus and
   canonical ABI hash covering command topology, exit code, stdout/stderr
-  channel discipline, JSON parseability, stable public diagnostics, and
+  channel discipline, JSON parseability, stable public diagnostics, explicit
+  output schema evolution for breaking JSON field changes, and
   descriptor/contract/help parity without making private descriptors public API.
 - `REQ-PROOFKIT-QUALITY-005`: CodeQL workflow source is admitted as an
   independent semantic security analysis signal for Go source without replacing
@@ -45,9 +46,10 @@ vulnerability absence, or consumer rollout safety by itself.
   unknown command refs, contract-only commands, or route-only commands. Static
   route metadata and source syntax never become semantic falsifier evidence.
 - `REQ-PROOFKIT-QUALITY-011`: CI separates the OS-independent full
-  source/package gate from macOS platform smoke, uses explicit hosted runner
-  labels instead of floating latest labels, and exposes one fail-closed
-  aggregate gate that requires every required leaf check to finish with success.
+  source/package gate from macOS platform smoke, executes the complete Go
+  package set through its owner command, uses explicit hosted runner labels
+  instead of floating latest labels, and exposes one fail-closed aggregate gate
+  that requires every required leaf check to finish with success.
 - `REQ-PROOFKIT-QUALITY-012`: release and adoption channel identifiers use one
   canonical authority vocabulary that separates durable authority channels from
   display labels, publisher environments, statuses, and candidate evidence.
@@ -65,8 +67,9 @@ vulnerability absence, or consumer rollout safety by itself.
   release closeout.
 - `REQ-PROOFKIT-QUALITY-016`: release platform targets use one private owner
   that projects platform suffixes, Go build targets, npm OS/CPU metadata,
-  package tar entries, Python wheel tags, PyPI candidate completeness, and
-  SBOM binary subjects without becoming public API.
+  package tar entries, Python wheel tags, PyPI candidate completeness,
+  self-hosting native binary selection, and SBOM binary subjects without
+  becoming public API.
 - `REQ-PROOFKIT-QUALITY-017`: report-visible secret-shaped JSON traversal
   uses one private kernel owner for deterministic paths and finding kinds while
   command packages only map findings to their local report policy.
@@ -86,6 +89,15 @@ vulnerability absence, or consumer rollout safety by itself.
   state before mutation, stays confined to the repository across symlinks,
   binds non-empty generated content to stable source and execution-context
   snapshots, and emits a schema-versioned execution record.
+- `REQ-PROOFKIT-QUALITY-021`: CLI contract v2 owns one leading pretty or
+  compact JSON layout option through a descriptor-aware token-role
+  preclassification at process output boundaries while canonical identity
+  serialization remains unchanged.
+- `REQ-PROOFKIT-QUALITY-022`: the requirement workspace uses an explicit
+  embedded asset set, strict authored-JavaScript type checking, exact secured
+  routes, bounded server cleanup, repository-confined non-symlink proof
+  artifacts, and machine-admitted per-project rendered engine evidence without
+  runtime dependencies or a production bundler.
 
 ## Non-Claims
 

package/docs/specs/proofkit-supply-chain-quality/requirements.v1.json

@@ -51,7 +51,7 @@
     {
       "requirementId": "REQ-PROOFKIT-QUALITY-004",
       "ownerId": "proofkit.supply-chain-quality",
-      "invariant": "Public CLI ABI has a small golden corpus and canonical ABI hash covering command topology, exit code, stdout and stderr channel discipline, JSON parseability, stable public diagnostics, and descriptor/contract/help parity without making private descriptors a public API.",
+      "invariant": "Public CLI ABI has a small golden corpus and canonical ABI hash covering command topology, exit code, stdout and stderr channel discipline, JSON parseability, stable public diagnostics, explicit output schema evolution for breaking JSON field changes, and descriptor/contract/help parity without making private descriptors a public API.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": ["proofkit/requirement-bindings.json"],
@@ -142,7 +142,7 @@
     {
       "requirementId": "REQ-PROOFKIT-QUALITY-011",
       "ownerId": "proofkit.supply-chain-quality",
-      "invariant": "CI separates the OS-independent full source/package gate from the platform-specific macOS execution smoke, uses explicit hosted runner labels instead of floating latest labels, and exposes one fail-closed aggregate quality gate that requires every required leaf check to finish with success so skipped, failed, or cancelled leaf jobs cannot satisfy branch-protection evidence.",
+      "invariant": "CI separates the OS-independent full source/package gate from the platform-specific macOS execution smoke, executes the complete Go package set through the owner command rather than a partial package list, uses explicit hosted runner labels instead of floating latest labels, and exposes one fail-closed aggregate quality gate that requires every required leaf check to finish with success so skipped, failed, or cancelled leaf jobs cannot satisfy branch-protection evidence.",
       "claimLevel": "blocking",
       "riskClass": "medium",
       "proofBindingRefs": ["proofkit/requirement-bindings.json"],
@@ -207,7 +207,7 @@
     {
       "requirementId": "REQ-PROOFKIT-QUALITY-016",
       "ownerId": "proofkit.supply-chain-quality",
-      "invariant": "Release platform targets have one private owner that projects exact platform suffixes, Go build targets, npm OS/CPU metadata, package tar binary entries, Python wheel tags, PyPI candidate completeness, and SBOM binary subjects without turning the platform matrix into public API.",
+      "invariant": "Release platform targets have one private owner that projects exact platform suffixes, Go build targets, npm OS/CPU metadata, package tar binary entries, Python wheel tags, PyPI candidate completeness, self-hosting native binary selection, and SBOM binary subjects without turning the platform matrix into public API.",
       "claimLevel": "blocking",
       "riskClass": "high",
       "proofBindingRefs": ["proofkit/requirement-bindings.json"],
@@ -268,6 +268,32 @@
       "lifecycle": {"state": "active", "replacementRequirementIds": [], "evidenceRefs": []},
       "deferral": null,
       "updatePolicy": {"reviewOwnerId": "proofkit.supply-chain-quality", "requiresImpactDeclaration": true, "requiresProofBindingReview": true}
+    },
+    {
+      "requirementId": "REQ-PROOFKIT-QUALITY-021",
+      "ownerId": "proofkit.supply-chain-quality",
+      "invariant": "The public CLI v2 process contract admits one leading pretty or compact JSON layout option, preserves pretty as the default, classifies descriptor-admitted flag and value token roles before output policy so option-shaped values cannot alter output classification, emits sorted valid JSON with one trailing LF in both layouts, applies the selected layout only at JSON stdout or admitted JSON file sinks, and leaves canonical digest and identity serialization unchanged.",
+      "claimLevel": "blocking",
+      "riskClass": "high",
+      "proofBindingRefs": ["proofkit/requirement-bindings.json"],
+      "nonClaimRefs": ["NC-PROOFKIT-QUALITY-021"],
+      "nonClaims": ["This requirement does not change canonical source storage, semantic selection, stable identity, text output, help output, browser sessions, merge approval, release approval, or rollout readiness."],
+      "lifecycle": {"state": "active", "replacementRequirementIds": [], "evidenceRefs": []},
+      "deferral": null,
+      "updatePolicy": {"reviewOwnerId": "proofkit.supply-chain-quality", "requiresImpactDeclaration": true, "requiresProofBindingReview": true}
+    },
+    {
+      "requirementId": "REQ-PROOFKIT-QUALITY-022",
+      "ownerId": "proofkit.supply-chain-quality",
+      "invariant": "Authored requirement workspace JavaScript and CSS are embedded through an explicit compile-time asset set, served only by exact routes with restrictive response headers, strictly type-checked without a production bundler, and covered by Go lifecycle, concurrent terminal-state, HTTP security, and repository-confined non-symlink artifact falsifiers plus a machine-admitted per-project execution report proving the same non-empty passed test identities in pinned Chromium, Firefox, and Playwright WebKit, with bounded browser-server cleanup and no added runtime package dependencies.",
+      "claimLevel": "blocking",
+      "riskClass": "high",
+      "proofBindingRefs": ["proofkit/requirement-bindings.json"],
+      "nonClaimRefs": ["NC-PROOFKIT-QUALITY-022"],
+      "nonClaims": ["This requirement does not claim full WCAG conformance, every branded browser, provider CI ingestion, registry publication, release approval, rollout approval, or production readiness."],
+      "lifecycle": {"state": "active", "replacementRequirementIds": [], "evidenceRefs": []},
+      "deferral": null,
+      "updatePolicy": {"reviewOwnerId": "proofkit.supply-chain-quality", "requiresImpactDeclaration": true, "requiresProofBindingReview": true}
     }
   ]
 }

package/package.json

@@ -1,7 +1,7 @@
 {
   "name": "@research-engineering/agentic-proofkit",
   "description": "Reusable proof profile, report, graph, and witness-planning primitives.",
-  "version": "0.1.157",
+  "version": "0.1.159",
   "type": "module",
   "license": "MIT",
   "sideEffects": false,
@@ -36,7 +36,10 @@
   ],
   "scripts": {
     "build": "go run ./internal/tools/packagebuild",
-    "check": "npm run npm:version && npm run source-hygiene && npm run command-family:check && npm run text-policy && npm run mermaid:check && npm run go:check && npm run package:artifact && npm run self:receipt && npm run self:coverage && npm run release:closeout",
+    "check": "npm run npm:version && npm run source-hygiene && npm run command-family:check && npm run text-policy && npm run mermaid:check && npm run browser:check && npm run go:check && npm run package:artifact && npm run self:receipt && npm run self:coverage && npm run release:closeout",
+    "browser:check": "npm run browser:static-check && npm run browser:test",
+    "browser:static-check": "tsc -p tsconfig.browser.json && node --test scripts/browser-proof-execution.test.mjs scripts/browser-proof-inputs.test.mjs scripts/browser-selection-authority.test.mjs",
+    "browser:test": "go run ./internal/tools/browserproofverify --run",
     "command-family:check": "go run ./internal/tools/commandfamilygen --check",
     "go:actionlint": "go tool actionlint",
     "go:bench": "go test ./internal/kernel/admission ./internal/kernel/stablejson -run '^$' -bench . -benchmem -count=10",
@@ -69,5 +72,10 @@
   "cpu": [
     "arm64",
     "x64"
-  ]
+  ],
+  "devDependencies": {
+    "@axe-core/playwright": "4.12.1",
+    "@playwright/test": "1.61.1",
+    "typescript": "7.0.2"
+  }
 }