kibi-cursor 1.0.0 → 2.0.0

package/.cursor-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "name": "kibi-cursor",
   "displayName": "Kibi",
-  "version": "1.0.0",
+  "version": "2.0.0",
   "description": "Optional Cursor adapter for Kibi. Requires SWI-Prolog 9+ and project-local kibi-cli, kibi-mcp, and kibi-core before the bundled MCP server can start.",
   "license": "AGPL-3.0-or-later",
   "author": {

package/CHANGELOG.md

@@ -1,5 +1,55 @@
 # kibi-cursor
 
+## 2.0.0
+
+### Major Changes
+
+- 812c201: Kibi's proof layer is now runner-neutral: any test runner, script, or harness can prove requirements, and Playwright is no longer built into the proof model.
+
+  - `kibi prove` replaces `kibi verify` as the single command to run configured proof producers and record evidence. Proof contracts (`kibi.proof-contract.v1`) declare explicit obligations (`symbol_id` + `target`) executed by a configured integration in `.kb/proof/integrations.json`; `kibi proof inspect` discovers test infrastructure deterministically; one producer run can satisfy many test contracts, and re-ingestion is idempotent.
+  - Evidence moves to the `kibi.proof-run.v1` artifact (typed environment, run-level outcome, factual attempt history with `native_case`/`aggregate_run` provenance) evaluated into `kibi.proof-receipt.v1` receipts bound to the live snapshot, contract hash, and effective execution fingerprint. Command proof is the universal fallback, so every project can prove requirements without a first-party framework adapter; strict first-attempt policy never upgrades unknown attempt history into passing evidence.
+  - Breaking removals: `kibi verify`, `kb_ingest_verification`, `kibi.playwright-run.v1`, `verification_contract`/`verification_receipts` entity fields (replaced by `proof_contract`/`proof_bindings`/`proof_receipts`), the `required_case_symbols`×`required_projects` Cartesian contract, and `retries` fields. Migrate by re-running `kibi prove` after bootstrap configures proof for your repository.
+
+  DRY: hard cutover to the proof-evidence protocol across CLI, MCP, runtime skills, Prolog proof evaluation, coverage/repair/report surfaces, agent skills, and repository self-proof (packed e2e steps now execute through `kibi prove --all`).
+
+### Patch Changes
+
+- b0271ac: Cursor now starts the bundled Kibi MCP server reliably when it launches plugin processes from a home directory or another unrelated working directory. Consumer workspaces with spaces continue to resolve their project-local `kibi-mcp` installation, while the portable Agent Plugin keeps its separate `npx --no-install` configuration.
+
+  - Fix `kibi-cursor` MCP launcher arguments to use Cursor's `${CURSOR_PLUGIN_ROOT}` expansion.
+  - Add source-install manifest regression coverage for consumer-local resolution from unrelated host directories.
+
+- b1682f1: Agents receive clearer guidance for repairing the actual supplied mutation request and preserving approved predicate bindings. The scoped additions retain the existing workflow while separating payload recovery from conditional relational modeling.
+
+  - Update `kibi-usage` to 2.1.2 in CLI/runtime sources and the generated Codex/Cursor distributions.
+  - Preserve the other three skills and all existing resource content.
+  - Retain production-adoption safeguards; development comparisons are not held-out evidence.
+
+- ee0dc49: Plugin hooks, the Cursor MCP launcher, and skill validation now expose the
+  same entry paths tests already spawn as processes. In-process coverage can
+  exercise stdin, CLI guards, and realpath failures instead of leaving those
+  lines invisible to Codecov.
+
+  - Export hook CLI helpers and Agent Plugin / launcher internals for tests.
+  - Use a namespace `fs` import in skill validation so realpath errors are testable.
+
+- 5999143: Agent-facing skill docs now use the current status field names, so agents following the freshness and E2E receipt workflows look for fields that actually exist in `kb_status` output instead of stale ones.
+
+  - Bundled `kibi-freshness` and `kibi-usage` skills (all agent mirrors) now reference `proofSnapshotChanges` and `proofSnapshot` (previously `verificationSnapshotChanges`/`verificationSnapshot` from the pre-proof-architecture status schema).
+  - The skillopt-eval harness reads `proofSnapshot*` status fields and its held-out eval prompts name the current fields, so "dirty editor path" evidence gathering works against live status output again.
+
+  Dry: completes the `verificationSnapshot*` → `proofSnapshot*` rename from the proof architecture change in the surfaces that earlier commit missed.
+
+## 1.0.1
+
+### Patch Changes
+
+- Cursor agents now get an always-on CLI recipe when Kibi MCP tools are missing, instead of treating Kibi as unavailable.
+
+  - Put the exact `npx --no-install kibi <route> --input -` command, MCP-to-CLI name mapping, and Shell-approval language in the always-applied workflow rule.
+  - Keep published plugin hooks advisory and untrusted by default; dogfood still opts into `--trusted-workspace` locally.
+  - Document the operator prerequisites (Agent mode, Shell, trusted workspace, project-local CLI) for the fallback to run.
+
 ## 1.0.0
 
 ### Major Changes

package/README.md

@@ -56,16 +56,19 @@ cp -r "$(npm root)/kibi-cursor" ~/.cursor/plugins/local/kibi-cursor
 ## MCP configuration
 
 The plugin bundles `mcp.json` with a thin launcher that locates and starts the
-`kibi-mcp` package installed in the opened project. The launcher runs from the
-consumer workspace and sets `KIBI_WORKSPACE` to that root; it never downloads,
-bundles, or falls back to a global Kibi runtime:
+`kibi-mcp` package installed in the opened project. The launcher starts the
+resolved child from the consumer workspace and sets `KIBI_WORKSPACE` to that
+root; it never downloads, bundles, or falls back to a global Kibi runtime:
 
 ```json
 {
   "mcpServers": {
     "kibi": {
       "command": "node",
-      "args": ["bin/launch-kibi-mcp.mjs", "${workspaceFolder}"]
+      "args": [
+        "${CURSOR_PLUGIN_ROOT}/bin/launch-kibi-mcp.mjs",
+        "${workspaceFolder}"
+      ]
     }
   }
 }
@@ -73,6 +76,9 @@ bundles, or falls back to a global Kibi runtime:
 
 Toggle the bundled MCP server from **Settings → Features → Model Context Protocol** after installing the plugin.
 
+Cursor expands `${CURSOR_PLUGIN_ROOT}` to the installed plugin directory and
+`${workspaceFolder}` to the opened workspace before starting the command.
+
 Manual MCP fallback (no plugin install required):
 
 ```json
@@ -135,6 +141,21 @@ Per the thin-adapter architecture, `kibi-cursor` does not:
 - **Editor-specific value**: Cursor hooks for read/write reminders and session freshness follow-ups
 - **Foundation**: `kibi-core`, `kibi-cli`, and `kibi-mcp` remain required for project-local operations
 
+## CLI fallback when MCP is unavailable
+
+The always-on `kibi-workflow` rule selects the trusted project-local CLI when Kibi MCP tools are not in the tool list. Hooks stay advisory and never execute that CLI themselves.
+
+For the agent to actually run the fallback, the Cursor session needs:
+
+- Agent mode with Shell enabled (Ask mode cannot run the CLI)
+- A trusted workspace, or explicit operator approval of the project-local CLI
+- Project-local `kibi-cli` (use `npx --no-install kibi` or `bunx --no-install kibi`; never a global or installing runner)
+- Plugin rules loaded in the Cursor harness
+
+If MCP tools are visible, use MCP and do not use this CLI path. If Shell is unavailable or the workspace is untrusted, stop and ask the operator; do not probe the CLI.
+
+A Cursor model invoked outside Cursor's plugin harness will not load this rule. Inject the same always-on guidance into that host's system prompt or `AGENTS.md`.
+
 ## License
 
 AGPL-3.0-or-later

package/agent-plugin/plugin.json

@@ -1,7 +1,7 @@
 {
   "$schema": "https://agent-plugins.org/schemas/1.0.0/plugin.schema.json",
   "name": "kibi",
-  "version": "1.0.0",
+  "version": "2.0.0",
   "description": "Repo-local, per-branch, queryable knowledge base. Portable Agent Plugin packaging Kibi's Agent Skills and MCP server.",
   "author": { "name": "Kibi" },
   "homepage": "https://github.com/Looted/kibi/blob/develop/docs/install.md",

package/agent-plugin/skills/kibi-freshness/SKILL.md

@@ -39,7 +39,7 @@ echo '{}' | npx --no-install kibi status --input -
   matching `branch.json`; a `legacy_compat` attachment is read-only until an
   explicit old/new migration is approved.
 - Inspect bounded `staleReasons` (indexed source missing/newer or documentation
-  source newer) and `verificationSnapshotChanges`. Kibi deliberately reports
+  source newer) and `proofSnapshotChanges`. Kibi deliberately reports
   editor/config paths such as editor dot-directories; do not silently ignore them.
 - Use `kb_query`, or `query --input`, with `sourceFile` and text references for source-linked discovery.
 - Re-run `kb_search`, or `search --input`, after sync gaps or stale context are detected.

package/agent-plugin/skills/kibi-usage/SKILL.md

@@ -2,7 +2,7 @@
 id: kibi-usage
 name: Kibi Usage
 description: Use Kibi's source-first, exact-Git, migration-aware, proof-aware operations safely across MCP or the trusted local CLI, including partial completion repair.
-version: 2.1.0
+version: 2.1.2
 kibiCompatibility: ">=1.0.0"
 tags:
   - kibi
@@ -19,6 +19,7 @@ resources:
   - resources/relationship-directions.md
   - resources/fact-lanes.md
   - resources/workflows.md
+  - resources/proof.md
   - resources/ui-requirements.md
   - resources/logic-ir.md
   - resources/kb-improvement.md
@@ -67,13 +68,30 @@ mutability, and Prolog requirements of each operation.
    Kibi never Git-stages or commits those files. Do not read or edit `.kb`
    directly.
 5. Finish with targeted and final `kb_check`, then read status/coverage and
-   state freshness, verification, proof, and limitations separately.
+   report the five independent closeout fields (not one inferred success flag).
 
 Run `kb_check` with specific rules during iteration and the unfiltered final
 check. Never fire `kb_upsert` calls in parallel; create or confirm endpoint
 entities before linking them. The canonical MCP names are `kb_search`,
 `kb_query`, `kb_upsert`, and `kb_check`.
 
+For a task that explicitly supplies a malformed concrete mutation payload, locate and read that public request artifact before choosing an entity, preserving its exact entity ID, type, requested changes, and every intended relationship and endpoint. Do not substitute a seeded or convenient entity for the requested target. Start with kb_search, then exact-filter those targets with kb_query, and run kb_validate_upsert on that same payload; validation is not completion. Correct only diagnosed pre-commit errors and revalidate the corrected payload. Once authorized, apply the identical corrected and authorized payload with kb_upsert. If it returns committed_with_repairs, treat the mutation as committed, follow only the required repair actions, and neither retry it nor trigger unrelated semantic backfill for a schema-only repair. Exact-read every changed entity and relationship endpoint with kb_query, then finish with an unfiltered kb_check followed by a final kb_status.
+
+## Closeout fields
+
+End every task with these five independent fields:
+
+```text
+taskOutcome: complete | interim | blocked
+kbState: clean_fresh | stale | dirty | legacy_compat | not_evaluated
+verificationState: fresh | dirty | unavailable | not_evaluated
+proofState: proven | mixed | unresolved | not_evaluated
+limitationDisposition: none | accepted | unaccepted | not_applicable
+```
+
+`taskOutcome` is whether the requested work finished. The other fields are
+observed system state. A clean check can coexist with unresolved proof.
+
 ## Exact Git attachment
 
 The active ref is the exact KB identity. `KIBI_BRANCH` is used verbatim; Git's
@@ -114,22 +132,33 @@ safe normative claims; use `observation` or `meta` for bug/workaround notes and
 `flag` only for actual runtime/config gates. Requirements require scenarios,
 tests, symbol ownership, and fresh proof-bearing receipts before claiming proof.
 For an existing product KB that needs semantic backfill, read
-`resources/kb-improvement.md`.
+`resources/kb-improvement.md`, and `resources/proof.md` for the proof workflow.
 
 ## Predicate Ontology Decision Tree
 
-Call `kb_semantic_advisor`, `kb_model_requirement`, or `kb_suggest_predicates`
-before encoding a normative clause. Use `fact_kind: predicate` with
-`requires_predicate` when a suitable schema exists; use `fact_kind: observation`
-for an ontology gap. Keep the `REQ -> TEST` chain and use `verified_by` for
-proof-bearing links. Relationship direction is fixed, and every `from` in a
-relationship batch must equal the upserted entity ID.
+Call `kb_semantic_advisor` on the complete prose before encoding a clause.
+Set requirement `logic_claims` to exactly the assertive `claim_key` values.
+For each relational clause, call `kb_suggest_predicates` with that clause and
+`existingLogicClaims`. If lexical rank is a false positive, retry with the
+reviewed `schemaId`. If `binding_status` is `incomplete`, supply
+`argumentBindings` and retry. Persist `fact_kind: predicate` with the same
+`claim_key` / `claim_text`, then link `REQ -> fact` with `requires_predicate`.
+Use `kb_model_requirement` for strict scalar clauses. Use
+`fact_kind: observation` only for a true ontology gap. The manifest is not
+grounding: run `logic-coverage` so each key binds to one ground fact.
+Relationship direction is fixed, and every `from` in a relationship batch
+must equal the upserted entity ID.
+
+For conditional relational claims, after the initial `kb_suggest_predicates` and before any `kb_upsert`—including one needed for a missing schema—call read-only `kb_model_requirement` to preview suitable scalar or typed-rule modeling. Treat the preview as advisory: do not apply an irrelevant result or create unrequested facts, and retain an approved ground-predicate plan when it captures the whole claim. Preserve supplied arity, ordered argument roles, polarity, bound values, and one claim key per actual assertion; never split arguments across clauses or schemas or alter values to force uniqueness.
 
 ## Symbol-First Traceability
 
-Represent implementation ownership with a `symbol` entity and an `implements`
-relationship from the symbol to the requirement. Do not rely on legacy
-`// implements REQ-xxx` comments as the traceability record.
+Represent implementation ownership with a `symbol` entity that has
+`sourceFile`, `implements` to the requirement, and `covered_by` to the test.
+Prolog `symbol-coverage` also requires the test to `validates` the requirement
+(or the requirement `verified_by` the test). `covered_by` alone is not
+enough. Do not rely on legacy `// implements REQ-xxx` comments as the
+traceability record.
 
 ## Complete Logical Coverage
 

package/agent-plugin/skills/kibi-usage/resources/operation-access.md

@@ -26,7 +26,7 @@ per operation. Effects are authoritative for mutability and adapter annotations.
 | `kb_sparql_remote` | `sparql-remote` | --input JSON | read | no | network-read | peer; capability-selected | kibi.kb_sparql_remote.v1 | no | safe | yes | yes |
 | `kb_compile_intent` | `compile-intent` | --input JSON | read | yes | kb-read, workspace-read | peer; capability-selected | kibi.kb_compile_intent.v1 | no | safe | no | yes |
 | `kb_apply_plan` | `apply-plan` | --input JSON | write | yes | kb-read, kb-write, workspace-read, workspace-write | peer; capability-selected | kibi.kb_apply_plan.v1 | yes | unsafe | no | yes |
-| `kb_ingest_verification` | `ingest-verification` | --input JSON | write | yes | kb-read, kb-write, workspace-read | peer; capability-selected | kibi.kb_ingest_verification.v1 | yes | unsafe | no | yes |
+| `kb_ingest_proof` | `ingest-proof` | --input JSON | write | yes | kb-read, kb-write, workspace-read | peer; capability-selected | kibi.kb_ingest_proof.v1 | yes | unsafe | no | yes |
 
 ## JSON execution recipe
 

package/agent-plugin/skills/kibi-usage/resources/proof.md

@@ -0,0 +1,105 @@
+# Proof and Verification Workflow
+
+Use this resource when a requirement must be proven before handoff, when
+wiring a proof-bearing test, or when `kb_ingest_proof` or `kibi prove`
+rejected evidence.
+
+Kibi does not support test runners. Kibi supports proof evidence. Any
+producer (Playwright, pytest, JUnit, TAP, shell commands, database harnesses)
+reports what happened as `kibi.proof-run.v1`; Kibi evaluates proof.
+
+## Golden path
+
+1. Query the test (`kb_query`, `type: test`) and read its
+   `kibi.proof-contract.v1`, `proof_bindings`, and `verification_scope`.
+2. Run the configured producer through the canonical command:
+
+   ```bash
+   kibi prove --test TEST-<id>
+   # or: kibi prove --requirement REQ-<id> | --integration <id> | --all
+   ```
+
+   `kibi prove` captures the workspace snapshot, runs each integration's
+   producer once (`shell: false`), revalidates the snapshot, evaluates the
+   artifact against every selected contract, and appends idempotent
+   `kibi.proof-receipt.v1` receipts.
+3. Confirm with `kb_status` (fresh, current snapshot) and `kb_coverage`.
+
+Never hand-write receipts. Kibi derives them from validated
+`kibi.proof-run.v1` artifacts only.
+
+## Proof contracts
+
+A proof-bearing test declares explicit obligations (never a Cartesian
+cases-times-projects matrix):
+
+```yaml
+verification_scope: end_to_end
+verification_perspective: consumer
+proof_contract:
+  version: kibi.proof-contract.v1
+  integration: web-e2e          # id from .kb/proof/integrations.json
+  required_proofs:
+    - symbol_id: SYM-PW-4F2A9C61B7D03E85
+      target: chromium          # browser, runtime, db, device, or default
+  success_policy: all_required_first_attempt
+proof_bindings:                 # optional provenance metadata
+  - symbol_id: SYM-PW-4F2A9C61B7D03E85
+    target: chromium
+    native_id: tests/checkout.spec.ts::accepts a card
+```
+
+Provenance lives in `proof_bindings`; the contract stays semantic.
+
+## Integration configuration
+
+`.kb/proof/integrations.json` (`kibi.proof-integration.v1`) is tracked,
+Kibi-managed configuration describing evidence production only:
+
+- `producer: command` — Kibi synthesizes the envelope from the process
+  outcome; obligations are bound with `aggregate_run` provenance and the
+  single process invocation counts as the known first attempt.
+- `producer: playwright` (or custom) — the child emits `kibi.proof-run.v1`
+  itself (bundled reporter: `kibi-cli/playwright-reporter`).
+- `producer: junit` / `tap` — Kibi converts the native report at `artifact`
+  using each test's `proof_bindings`; standard formats carry no retry
+  history, so attempts are reported as `unavailable` and fail the strict
+  first-attempt policy closed.
+
+Cosmetic edits (descriptions, labels) never stale proof. Execution-relevant
+edits (command, artifact, targets, options, bindings, contract) change the
+effective fingerprint and do.
+
+## Attempt semantics (factual, never optimistic)
+
+- `attempts: {status: "complete", entries: [...]}` — known history; the
+  strict policy requires a passing **first** entry.
+- `attempts: {status: "unavailable"}` — unknown native history; the strict
+  policy fails closed, except `aggregate_run` results, which are satisfied by
+  the Kibi-launched process attempt when the run passed with exit code 0.
+- `run.outcome` is authoritative: a failed, errored, cancelled, interrupted,
+  or `no_results` run proves nothing, even with passing individual results.
+
+## Common rejections
+
+- `No proof integration configuration` — bootstrap has not configured proof
+  for this repository yet; do not hand-wave, run the bootstrap proof step.
+- `captured snapshot is not the live workspace snapshot` — the tree changed
+  between capture and ingest; re-run `kibi prove`.
+- `artifact command_argv does not match the configured command` — the
+  artifact came from a different command than `integrations.json` configures.
+- `attempt history unavailable` — the producer could not prove first-attempt
+  success for a native-case obligation; use a producer with complete history
+  or accept aggregate provenance.
+- `proof_receipts is append-only` — receipts are append-only; update tests
+  through the engine (which appends) or include the existing history when
+  authoring test files directly.
+
+## After code changes
+
+Receipts bind to the snapshot, contract hash, and execution fingerprint at
+run time. Any code or source change moves the snapshot and stales receipts:
+re-run `kibi prove` for the affected selection, then confirm `kb_status` and
+`kb_coverage` before handoff.
+
+Full reference: `docs/proving-requirements.md`.

package/agent-plugin/skills/kibi-usage/resources/workflows.md

@@ -25,7 +25,7 @@ Receipt reuse is safe only when the live verification snapshot, contract hash,
 freshness window, and every required case result still match. Otherwise rerun
 the contracted command. If the contract changed, retain every older receipt
 unchanged, append evidence for the current contract, and keep proof unresolved
-with `verification_contract_mismatch` until that current receipt exists.
+with `proof_contract_mismatch` until that current receipt exists.
 Obsolete symbols require current extraction or Git evidence before
 remap/deletion; transfer coverage only when existing test evidence supports it,
 then sync and read back status. Same-version packages with different export
@@ -46,7 +46,7 @@ The canonical workflow for any KB operation follows this pattern:
 7. **Create endpoints**: validated `kb_upsert` for new entities, sequentially
 8. **Link**: validated `kb_upsert` with `requires_rule`, `requires_predicate`, `constrains`, or `requires_property`, sequentially
 9. **Validate coverage and consistency**: targeted `rule-safety`, `rule-verifiability`, `semantic-completeness`, `logic-coverage`, `predicate-verifiability`, and `domain-contradictions`, then final full `kb_check`
-10. **Prove execution**: read `kb_status.verificationSnapshot`, run each scenario-backed E2E command exactly as declared by its `verification_contract.v1` through `kibi verify`, append the derived `kibi.verification-receipt.v2`, and re-run `kb_coverage`; never promote durable test status into fresh evidence
+10. **Prove execution**: read `kb_status.proofSnapshot`, run `kibi prove` so each configured integration executes once and its `kibi.proof-run.v1` artifact is evaluated against every selected test's `kibi.proof-contract.v1` obligations, appending idempotent `kibi.proof-receipt.v1` receipts; then re-run `kb_coverage`. Never promote durable test status into fresh evidence.
 11. **Repair incrementally**: require `kb_coverage.repairPlan.scope.complete`, apply only one `ready` dependency batch per requirement, validate before every sequential write, and rerun coverage before selecting the next batch
 12. **Gate workflow evidence**: when `.kb/usage.log` exists, run `kibi usage-metrics --format json --require-acceptance`; repair ranked telemetry diagnostics and never treat stale or insufficient evidence as a pass
 
@@ -74,7 +74,7 @@ choose package managers, ground semantic claims, resolve contradictions, rerun
 E2E tests, rewrite receipt history, remap authored symbols, or accept
 limitations. Those actions remain explicit review/operator/execution steps.
 
-For `e2e_receipt_freshness_low`, query each listed requirement/test gap and run its exact current contract through `kibi verify`; this appends v2 evidence and preserves older history. If `coverage_depth_review` conflicts with a coverage row whose `proofStages.passingE2e.status` is `passed`, report the diagnostic as a stale heuristic and keep any independent proof gaps unresolved.
+For `e2e_receipt_freshness_low`, query each listed requirement/test gap and run `kibi prove --requirement <id>` (or the covering integration); this appends proof receipts idempotently and preserves history. If `coverage_depth_review` conflicts with a coverage row whose `proofStages.passingE2e.status` is `passed`, report the diagnostic as a stale heuristic and keep any independent proof gaps unresolved.
 
 ## Creating a New Feature
 ```
@@ -101,12 +101,12 @@ Do not create a test-fact pair. Facts describe invariants; requirements or scena
 ## Fresh E2E Receipt Workflow
 
 1. Confirm the exact `REQ -> SCEN -> TEST` path and require typed `verification_scope: end_to_end`; direct requirement-to-test links do not satisfy the conservative scenario stage.
-2. Read `kb_status` and retain its available `verificationSnapshot`. Stop if the runtime reports `unknown`; proof must fail closed when the code identity cannot be computed.
+2. Read `kb_status` and retain its available `proofSnapshot`. Stop if the runtime reports `unknown`; proof must fail closed when the code identity cannot be computed.
 3. Run the exact E2E command against that snapshot. Record runner, command, start/finish timestamps, outcome, an environment SHA-256, and an artifact/output SHA-256. Do not mint a passed receipt from an authored test status or from an unexecuted assertion.
-4. Preserve every existing receipt byte-for-byte and append the derived `kibi.verification-receipt.v2` object with strictly later `finished_at`. Earlier receipts may bind older contracts; they remain audit history but cannot prove the current contract. Mutation and incremental sync reject history removal, rewriting, and reordering.
+4. Preserve every existing receipt byte-for-byte and append the derived `kibi.proof-receipt.v1` object with strictly later `finished_at`. Earlier receipts may bind older contracts or fingerprints; they remain audit history but cannot prove the current contract. Mutation and incremental sync reject history removal, rewriting, and reordering.
 5. Re-read `kb_status`; if the snapshot changed during the run, discard the candidate as proof and rerun against the new snapshot. Then run `kb_coverage` and inspect `proofStages.passingE2e.receiptEvidence` plus gap codes.
 
-Only the newest receipt matching both the live snapshot and current contract qualifies, and it must be passed, no more than seven days old, and no more than five minutes in the future. Wrong-snapshot and older-contract history is retained but cannot prove the current test. `missing_verification_receipt`, `stale_verification_receipt`, `failed_verification_receipt`, `invalid_verification_receipt`, `verification_contract_mismatch`, and `verification_snapshot_unavailable` are repair states, not warnings to waive.
+Only the newest receipt matching the live snapshot, current contract hash, and current execution fingerprint qualifies, and it must be passed, no more than seven days old, and no more than five minutes in the future. Wrong-snapshot and older-contract history is retained but cannot prove the current test. `missing_proof_receipt`, `stale_proof_receipt`, `failed_proof_receipt`, `invalid_proof_receipt`, `proof_contract_mismatch`, and `proof_snapshot_unavailable` are repair states, not warnings to waive.
 
 ## Predicate-First Requirement Modeling
 

package/bin/launch-kibi-mcp.d.mts

@@ -1,5 +1,23 @@
 export function parseWorkspaceFolderPaths(value: unknown): string[];
 
+export function nextAncestorDirectory(current: string): string | undefined;
+
+export function packageJsonForResolvedFile(startPath: string): {
+  packageJsonPath: string;
+  packageRoot: string;
+  packageJson: Record<string, unknown>;
+} | null;
+
+export function hasConsumerNodeModulesLink(
+  workspaceRoot: string,
+  packageRoot: string,
+): boolean;
+
+export function isProjectScopedPackage(
+  workspaceRoot: string,
+  packageRoot: string,
+): boolean;
+
 export function resolveProjectLocalMcp(workspaceRoot: string): {
   packageRoot: string;
   packageJsonPath: string;
@@ -7,12 +25,32 @@ export function resolveProjectLocalMcp(workspaceRoot: string): {
   binPath: string;
 };
 
+export function hasDeclaredProjectDependency(workspaceRoot: string): boolean;
+
 export function resolveWorkspaceRoot(
   explicitWorkspace?: string,
   options?: { cwd?: string; env?: NodeJS.ProcessEnv },
 ): string;
 
+export function signalExitCode(signal: NodeJS.Signals | string): number;
+
+export function isLaunchEntrypoint(
+  argv1: string | undefined,
+  moduleUrl: string,
+): boolean;
+
+export function runLaunchEntrypoint(
+  argv?: string[],
+  env?: NodeJS.ProcessEnv,
+): Promise<number>;
+
 export function launchKibiMcp(
   argv?: string[],
   env?: NodeJS.ProcessEnv,
+  spawnImpl?: typeof import("node:child_process").spawn,
 ): Promise<number>;
+
+export function runLaunchIfEntrypoint(
+  isEntrypoint?: boolean,
+  start?: () => Promise<number> | Promise<void>,
+): Promise<void>;