kibi-cli 2.29.0 → 2.31.0

package/src/public/operations/specs/discovery.ts

@@ -259,7 +259,7 @@ export const statusSpec = {
   name: "kb_status",
   cliName: "status",
   description:
-    "Report current branch, KB snapshot, freshness metadata, schema status, and a typed kibi.migration-plan.v2 action graph. Read-only status inspection with no mutation side effects; damaged stores are diagnosed without starting the engine.",
+    "Report current branch, KB snapshot, freshness metadata, schema status, and a typed kibi.migration-plan.v2 action graph. Call it first to orient on a branch or after a failed call; use kb_check for validation findings and kb_coverage for proof status. Read-only status inspection with no mutation side effects; damaged stores are diagnosed without starting the engine.",
   businessInputSchema: { type: "object", properties: {} },
   // Status must remain available when the branch store cannot be attached.
   requiresProlog: false,

package/src/public/operations/specs/impact-review-preparation.ts

@@ -5,13 +5,15 @@ export const prepareImpactReviewSpec = {
   name: "kb_prepare_impact_review",
   cliName: "prepare-impact-review",
   description:
-    "Prepare complete content-bound impact-review authoring inputs from the current staged snapshot or explicitly selected immutable Git commits. Returns strict reviewer schemas and an unauthored template; it does not decide, approve, sign, stage, or prove the review.",
+    "Prepare complete content-bound impact-review authoring inputs from the current staged snapshot or explicitly selected immutable Git commits. Use it when kb_check reports that changed files need an impact review; it does not plan KB changes. Returns strict reviewer schemas and an unauthored template; it does not decide, approve, sign, stage, or prove the review.",
   businessInputSchema: {
     type: "object",
     additionalProperties: false,
     required: ["scope"],
     properties: {
       scope: {
+        description:
+          'What to review: {"kind":"staged"} for the staged snapshot, or {"kind":"diff","baseCommit":"<sha>","headCommit":"<sha>"} with full commit hashes.',
         oneOf: [
           {
             type: "object",

package/src/public/operations/specs/planning.ts

@@ -35,7 +35,7 @@ export const compileIntentSpec = {
   name: "kb_compile_intent",
   cliName: "compile-intent",
   description:
-    "Compile complete change intent into a deterministic, snapshot-bound read-only plan. Reuses intent-aware discovery and semantic modeling, accounts for every proposition, reports contradiction witnesses, proposes traceability links, and emits dependency-ordered kb_upsert-style steps only for resolved typed claims. contradictionAnalysis.outcome is no_conflict only when the check could decide: an unmodeled proposition or a related current requirement without logic leaves it unresolved with reasons and reviewCandidates to compare and judge through conflictReviews. No mutation side effects.",
+    "Compile complete change intent into a deterministic, snapshot-bound read-only plan. Use it before editing code for a change request that may touch several requirements; use kb_model for one requirement's prose and kb_plan_bootstrap for first-time onboarding. Reuses intent-aware discovery and semantic modeling, accounts for every proposition, reports contradiction witnesses, proposes traceability links, and emits dependency-ordered kb_upsert-style steps only for resolved typed claims. contradictionAnalysis.outcome is no_conflict only when the check could decide: an unmodeled proposition or a related current requirement without logic leaves it unresolved with reasons and reviewCandidates to compare and judge through conflictReviews. No mutation side effects.",
   businessInputSchema: {
     type: "object",
     required: ["intent", "mode"],

package/src/public/operations/specs/reporting.ts

@@ -118,7 +118,7 @@ function validateEntityType(type?: string): void {
 }
 
 const COVERAGE_PROOF_STATUSES: ReadonlySet<string> = new Set([
-  "proven",
+  "tested",
   "missing",
   "unresolved",
   "not_applicable",
@@ -173,20 +173,47 @@ export const findGapsSpec = {
   name: "kb_find_gaps",
   cliName: "find-gaps",
   description:
-    "Run bulk missing/present relationship analysis over KB entities. Use for questions like which requirements lack scenarios or tests. No mutation side effects.",
+    "List KB entities by the relationships they lack or have. Use for questions like which requirements lack scenarios or tests; all filters must match, and a relationship counts in either direction. Use kb_coverage instead for proof status and repair plans, and kb_check for rule violations. No mutation side effects.",
   businessInputSchema: {
     type: "object",
     properties: {
       type: {
         type: "string",
         enum: ENTITY_TYPES,
+        description: "Only report entities of this type. Omit for all types.",
+      },
+      missingRelationships: {
+        type: "array",
+        items: { type: "string" },
+        description:
+          "Relationship types the entity must have none of, in either direction, for example specified_by or verified_by. verified_by and validates satisfy each other.",
+      },
+      presentRelationships: {
+        type: "array",
+        items: { type: "string" },
+        description:
+          "Relationship types the entity must have at least one of each, in either direction.",
+      },
+      tags: {
+        type: "array",
+        items: { type: "string" },
+        description:
+          "Keep entities carrying any of these metadata tags. Bootstrap provenance stubs appear in rows only when this names bootstrap:provenance-stub.",
+      },
+      sourceFile: {
+        type: "string",
+        description: "Keep entities whose source path contains this substring.",
+      },
+      limit: {
+        type: "integer",
+        default: 100,
+        description: "Maximum rows to return; count reports the full total.",
+      },
+      offset: {
+        type: "integer",
+        default: 0,
+        description: "Zero-based row offset for pagination.",
       },
-      missingRelationships: { type: "array", items: { type: "string" } },
-      presentRelationships: { type: "array", items: { type: "string" } },
-      tags: { type: "array", items: { type: "string" } },
-      sourceFile: { type: "string" },
-      limit: { type: "integer", default: 100 },
-      offset: { type: "integer", default: 0 },
     },
   },
   requiresProlog: true,
@@ -200,7 +227,7 @@ export const findGapsSpec = {
  * + bound-symbol code scope) and hand the Prolog coverage stage a
  * TestId -> BindingHash dict. This is the default binding mode since slice 3;
  * KIBI_PROOF_BINDING_MODE=strict-snapshot opts out (receipts then match only
- * against the whole-workspace snapshot they were proven on).
+ * against the whole-workspace snapshot they were produced on).
  */
 // implements REQ-kibi-verification-evidence-contract
 export function currentProofBindingMode(): "per_contract" | "strict_snapshot" {
@@ -404,13 +431,13 @@ export async function executeCoverage(
       },
     };
     const fullyCovered = Number(enrichedPayload.summary?.fullyCovered ?? 0);
-    const proofProven = Number(enrichedPayload.summary?.proofProven ?? 0);
+    const proofTested = Number(enrichedPayload.summary?.proofTested ?? 0);
     const total = Number(enrichedPayload.summary?.total ?? 0);
     return {
       content: [
         {
           type: "text",
-          text: `Coverage summary: ${fullyCovered} structurally covered and ${proofProven} proven out of ${total}.`,
+          text: `Coverage summary: ${fullyCovered} structurally covered and ${proofTested} tested end to end out of ${total}.`,
         },
       ],
       structuredContent: enrichedPayload,
@@ -425,25 +452,55 @@ export const coverageSpec = {
   name: "kb_coverage",
   cliName: "coverage",
   description:
-    "Generate curated structural coverage and conservative end-to-end requirement proof reports for requirements, symbols, or grouped types. Reports include the compatible repair plan plus typed kibi.migration-plan.v2 actions; semantic and E2E actions remain review/execution work. Paginated plans identify incomplete scope and no mutation occurs.",
+    "Generate curated structural coverage and conservative end-to-end requirement proof reports for requirements, symbols, or grouped types. Use it to ask which requirements are tested end to end, how strong each requirement's evidence is (evidenceLevel: proved, tested, asserted or unverified), and what blocks the rest; use kb_find_gaps for a plain list of missing links and kb_check for rule violations. Reports include the compatible repair plan plus typed kibi.migration-plan.v2 actions; semantic and E2E actions remain review/execution work. Paginated plans identify incomplete scope and no mutation occurs.",
   businessInputSchema: {
     type: "object",
     properties: {
-      by: { type: "string", enum: ["req", "symbol", "type"], default: "req" },
-      tags: { type: "array", items: { type: "string" } },
-      includePassing: { type: "boolean", default: false },
+      by: {
+        type: "string",
+        enum: ["req", "symbol", "type"],
+        default: "req",
+        description:
+          "Report shape: req gives per-requirement proof status and a repair plan, symbol gives per-symbol ownership coverage, type gives counts per entity type.",
+      },
+      tags: {
+        type: "array",
+        items: { type: "string" },
+        description:
+          "Keep rows for entities carrying any of these metadata tags.",
+      },
+      includePassing: {
+        type: "boolean",
+        default: false,
+        description:
+          "Also return rows that are already tested or not applicable. By default only rows that still need repair are returned.",
+      },
       statuses: {
         type: "array",
         items: {
           type: "string",
-          enum: ["proven", "missing", "unresolved", "not_applicable"],
+          enum: ["tested", "missing", "unresolved", "not_applicable"],
         },
         description:
           "Requirement proof-status filter (req mode): include only rows whose proofStatus is listed. Selecting statuses implies include-passing; not_applicable rows carry their typed applicability reason in proofStages.applicability.reason. The summary always reflects the whole KB.",
       },
-      includeTransitive: { type: "boolean", default: true },
-      limit: { type: "integer", default: 100 },
-      offset: { type: "integer", default: 0 },
+      includeTransitive: {
+        type: "boolean",
+        default: true,
+        description:
+          "Count symbol coverage reached transitively through linked entities, not only direct links.",
+      },
+      limit: {
+        type: "integer",
+        default: 100,
+        description:
+          "Maximum rows to return. When the repair plan reports scope.complete false, rerun with offset 0 and a larger limit.",
+      },
+      offset: {
+        type: "integer",
+        default: 0,
+        description: "Zero-based row offset for pagination.",
+      },
       includeMigrationPreview: {
         type: "boolean",
         default: false,
@@ -526,22 +583,53 @@ export const graphSpec = {
   name: "kb_graph",
   cliName: "graph",
   description:
-    "Run bounded graph traversal from one or more seed IDs across curated relationship types. No mutation side effects.",
+    "Run bounded graph traversal from one or more seed IDs across curated relationship types and return the nodes and edges reached. Use it to follow links from IDs you already have, such as a requirement to its scenarios and tests or a symbol to the requirements it implements; use kb_query to find entities by filter and kb_search to ask a question. Traversal stops at depth, maxNodes or maxEdges and then sets truncated. No mutation side effects.",
   businessInputSchema: {
     type: "object",
     required: ["seedIds"],
     properties: {
-      seedIds: { type: "array", items: { type: "string" } },
-      relationships: { type: "array", items: { type: "string" } },
+      seedIds: {
+        type: "array",
+        items: { type: "string" },
+        description:
+          "Entity IDs to start from, for example REQ-... or SCEN-.... Seeds are always returned as nodes.",
+      },
+      relationships: {
+        type: "array",
+        items: { type: "string" },
+        description:
+          "Relationship types to follow, for example specified_by, verified_by or implements. Omit to follow every relationship type.",
+      },
       direction: {
         type: "string",
         enum: ["outgoing", "incoming", "both"],
         default: "outgoing",
+        description:
+          "outgoing follows links from each node, incoming follows links pointing at it, both does either.",
+      },
+      depth: {
+        type: "integer",
+        default: 1,
+        minimum: 1,
+        maximum: 5,
+        description: "Number of hops from the seeds.",
+      },
+      entityTypes: {
+        type: "array",
+        items: { type: "string" },
+        description:
+          "Keep only nodes of these types (req, scenario, test, adr, flag, event, symbol, fact) in the result, and the edges between them. Traversal still passes through other types.",
+      },
+      maxNodes: {
+        type: "integer",
+        default: 200,
+        description: "Stop and set truncated once this many nodes are reached.",
+      },
+      maxEdges: {
+        type: "integer",
+        default: 500,
+        description: "Stop and set truncated once this many edges are reached.",
       },
-      depth: { type: "integer", default: 1, minimum: 1, maximum: 5 },
-      entityTypes: { type: "array", items: { type: "string" } },
-      maxNodes: { type: "integer", default: 200 },
-      maxEdges: { type: "integer", default: 500 },
     },
   },
   requiresProlog: true,

package/src/public/skills/kibi-commit-review/SKILL.md

@@ -0,0 +1,125 @@
+---
+id: kibi-commit-review
+name: kibi-commit-review
+description: "Use when kibi check --staged or the Kibi pre-commit hook blocks a commit (kibi_impact_evidence_missing, symbols_manifest_stale, symbol_granularity_violation, symbol-coverage, kibi check-generated drift, Staged impact review failed), or when preparing a commit or pull-request impact review. Covers reading the per-file Detail lines, authoring .kb/symbols.yaml symbol entries through kb_upsert, kibi sync --refresh-symbol-coordinates, staging the tracked Kibi evidence with git add, kb_prepare_impact_review for a staged or diff scope, the kibi signoff requirements summary to show before a commit, and how merge commits and migration renames are judged."
+version: 1.2.0
+kibiCompatibility: ">=1.0.0"
+tags:
+  - kibi
+  - commit
+  - staged-check
+  - traceability
+  - agent-guidance
+resources:
+  - resources/staged-gate.md
+---
+## Goal
+
+Get a commit through Kibi's staged gate by fixing the cause: the commit
+carries the knowledge its behavior change needs, with current symbol
+coordinates, so the gate passes for the same reason a reviewer would accept it.
+
+## Interface Selection
+
+Use the visible approved MCP tools or the trusted project-local CLI as equal
+peer interfaces (CLI JSON: `printf '%s\n' '{}' | npx --no-install kibi status
+--input -`). The gate itself is CLI: `npx --no-install kibi check --staged`
+(add `--format json` for the full evidence). If neither surface is available,
+stop and name the missing capability. Never read or edit `.kb/` files directly.
+
+## When this applies
+
+- `kibi check --staged` fails, or the pre-commit hook (`kibi check-generated
+  --staged --changed-only`, then `kibi check --staged`) blocks a commit.
+- You are about to commit or open a pull request and want the impact review
+  ready first.
+
+Never read or open any file under `.kb`, not even read-only with a file tool to look at symbols or coordinates; doing so fails the session even when nothing is written. What you need is already shown elsewhere: the gate's `Detail:` lines, `kb_query` by `sourceFile` or `id`, and `kb_check` with `staged: true` show which symbols and coordinates are covered and which are missing. Before deciding what the change is, always run `kb_search` with `sourceLocations` for each named file and `kb_query` the requirement that governs it, even when the edit looks coordinate-only or seems to contradict a firm rule. When a write is authorized, keep the supplied target and its intended edges, query those targets first, validate the exact payload with `kb_upsert` and `dryRun: true`, then send that same payload with `kb_upsert` and exact-read the result back with `kb_query` before the final checks. Distinct authorized payloads may need several sequential writes, but never resend a write that is already committed, and let typed `nextActions` drive recovery. A passing dry run is validation only, not completion.
+
+## Steps
+
+1. **Read the whole failure.** Each finding names an id, the files, `Detail:`
+   lines and a `Suggestion:`. Detail lines are complete per file: how many
+   symbols extraction finds in the staged content, how many the staged
+   evidence covers, and every symbol missing from `.kb/symbols.yaml` with its
+   line. The common ids and their fixes are in `resources/staged-gate.md`.
+2. **Find the owning knowledge.** `kb_search` with `sourceLocations` for each
+   named file (or `kb_query({sourceFile})`), then `kb_query` the requirements,
+   scenarios and tests it returns. Run `kb_check` with `sourceFiles`,
+   `includeImpactDiagnostics: true` and `staged: true` to see the impact
+   findings, including `requirement_statement_unverified` quotes.
+3. **Decide what the change is.**
+   - Behavior changed: update or record the knowledge (a requirement with a
+     scenario, or a new clause) through `kb_upsert`. If the change contradicts
+     a recorded rule, stop and ask; load `kibi-decisions`.
+   - New or uncovered symbols: author a `symbol` entity per listed symbol
+     through `kb_upsert` (`title` = the member the extractor names,
+     `sourceFile`, `status: active`, `symbol_role: behavioral`, `implements`
+     to the requirement, `covered_by` to the test). Then run
+     `kibi sync --refresh-symbol-coordinates`.
+   - Only coordinates moved: `kibi sync --refresh-symbol-coordinates`.
+   - No behavior change (a genuine false positive): see the audited
+     no-impact note in `resources/staged-gate.md`; it never covers a real
+     behavior change.
+4. **Stage the evidence.** Kibi authors tracked files but never Git-stages or
+   commits them. `git status --short .kb` lists what it wrote; `git add` the
+   entity Markdown, `.kb/relationships/` shards, `.kb/symbols.yaml` and
+   `.kb/symbol-coordinates.yaml` that belong to this change (use `git add -p`
+   when the files hold unrelated edits).
+5. **Re-run** `kibi check --staged` (and `kibi check-generated --staged` when it
+   failed) until it passes. Never bypass the hook (`--no-verify`) unless the
+   person says so.
+
+## Requirements signoff
+
+Before you ask the person to approve a commit that adds, rewrites or retires
+requirements, or changes code that implements them, show them what they are
+signing off:
+
+```
+npx --no-install kibi signoff            # working tree; --staged for the index
+```
+
+It prints Markdown listing each new, changed, affected and retired
+requirement with its statement (before and after for a rewrite), firmness,
+origin, scenarios and proof state. Put it in your reply unchanged (in the
+messaging tool's message when replies go through one), then add one or two
+sentences on why the requirements changed. Offer the full page with
+`kibi signoff --format html --open`, or attach or publish
+`.kb/briefs/signoff/latest.html` when your host can carry a file or a page;
+past 15 requirements the Markdown stops and only the page lists them all.
+Host details: `kibi-decisions`, `resources/signoff-views.md`. `--no-proof` skips the proof lookup, which reads coverage and is slow
+on a large knowledge base. The summary is not an approval: never set
+`approved_by` or `origin.ref` from it.
+
+## Impact reviews
+
+When the repository's base commit carries `.kibi/impact-policy.json`, the gate
+also demands a content-bound review record at `.kibi/impact-review.json`
+(`Staged impact review failed: impact_review_invalid ...`). Prepare it with
+`kb_prepare_impact_review` (`scope: {"kind":"staged"}`, or `{"kind":"diff",
+"baseCommit":"<40-hex sha>","headCommit":"<40-hex sha>"}` for a pull
+request). It is read-only: it returns per-file evidence, requirement scopes,
+residual review obligations and an unauthored record template. Draft each
+file's `decision` from what you verified, leave `reviewer.id` for the person
+who reviews, and never present the record as their approval. Field details are
+in `resources/staged-gate.md`.
+
+## Merge commits and migrations
+
+During a merge (`MERGE_HEAD` exists), files staged unchanged from a merged
+parent are skipped (`Merge commit: N staged file(s) are taken unchanged ...`);
+only what the merge resolved or edited is judged. A commit that moves
+knowledge into `.kb/` after `kibi migrate` is compared with the old paths
+(`Baseline: HEAD with N staged knowledge rename(s) ...`), and symbol records
+changed only by the migration are not judged as changed. Debt reported there
+came from the branch or the old layout; the full `kibi check` still shows it.
+
+## Typed results and report
+
+Parse `kibiProtocol`, `status`, diagnostics and typed `nextActions` on every
+Kibi write. On `committed_with_repairs`, run the repair actions and never
+resend the original write. Report the findings you fixed (id, file, what
+changed), the knowledge you recorded or confirmed still current, the files
+you staged, the final `kibi check --staged` result, and anything left for the
+person (an open rule conflict, an unauthored review decision).

package/src/public/skills/kibi-commit-review/resources/staged-gate.md

@@ -0,0 +1,98 @@
+# The staged gate
+
+Reference for `kibi-commit-review`: what `kibi check --staged` and
+`kibi check-generated --staged` report, how to fix each finding, and the
+impact-review record. The staged check reads blob content from the Git index,
+not the working tree, so a fix counts only once it is staged.
+
+## Reading a finding
+
+```text
+symbols_manifest_stale: .kb/symbol-coordinates.yaml is stale or missing for staged source files: src/billing/refund.ts
+  Detail: src/billing/refund.ts — extraction finds 4 symbol(s), evidence covers 3.
+      Not in .kb/symbols.yaml: approveRefund (line 42)
+  Suggestion: Author .kb/symbols.yaml entries for the uncovered symbols (kibi upsert, with implements/covered_by links), then run kibi sync --refresh-symbol-coordinates && git add .kb/symbol-coordinates.yaml .kb/symbols.yaml, then re-run kibi check --staged.
+```
+
+- Detail lines name every symbol, never a shortened list. `Evidence without a
+  matching symbol:` lists manifest entries whose declaration is gone or
+  renamed: rename the symbol's `title`, or retire the entry.
+- `--format json` carries the same lists in the diagnostic `evidence`
+  (`symbolsManifest[].missing` / `extra`, `uncoveredSymbols[].titles`).
+
+## Blocking findings
+
+| Id or message | Cause | Fix |
+| --- | --- | --- |
+| `kibi_impact_evidence_missing` | A staged behavior edit (changed lines in exported or behavior-bearing code, not comments or formatting) has no staged Kibi evidence. Test-only edits do not need it unless they add executable test symbols. | Query the owning knowledge; update it when behavior changed; stage entity Markdown under `.kb/`, authored `.kb/symbols.yaml` entries for the listed symbols, or refreshed `.kb/symbol-coordinates.yaml`. |
+| `symbols_manifest_stale` | Extraction output changed and the staged coordinates (or manifest) do not match it. | Author entries for the listed symbols first, then `kibi sync --refresh-symbol-coordinates`, then stage both manifests. |
+| `symbol_granularity_violation` | A changed behavioral member is owned only by a coarse class or module symbol while a narrower declaration exists. | Add a symbol for the member itself (`title` = `Class.method` or the exported function) with its own links; use `granularity_reason` (`config-artifact`, `module-level-behavior`, `extractor-miss`, `legacy-link`, `test-suite`) only when it is true. |
+| `symbol-coverage` | A changed symbol, or a symbol whose staged manifest entry changed, fails the full-check rule on the staged knowledge. | The symbol `implements` the requirement and is `covered_by` a test that verifies it: through the requirement's scenario (`verified_by` scenario -> test) when it has one, else `verified_by` requirement -> test. A direct requirement -> test link does not count while a scenario exists. The finding's suggestion names the missing link (see `kibi-traceability`). |
+| `kibi_impact_override_missing_rationale` | A `Kibi-Impact: none` declaration has no `Rationale:` line. | Add the rationale, or drop the declaration and stage real evidence. |
+| `entity-context-missing` (staged entity) | A staged requirement, scenario, test, ADR or observation fact has fewer than 12 words of context. | Upsert a sectioned `document.body` (see `kibi-usage`, Entity body contract). |
+| `domain-contradictions`, `scenario-feasibility`, `exception-claim-keys` (staged `.kb/` change) | The staged knowledge introduces a violation the last commit did not have. | Fix the knowledge; a contradiction with a recorded rule goes to the person (`kibi-decisions`). |
+| Proposition-complete ingestion | A staged requirement's semantic inventory is missing or no longer matches its prose. | Re-derive it (`kb_model` analyze with the complete prose) or run `kibi migrate` for drift. |
+| `kibi check-generated --staged` drift | The staged `.kb/symbols.yaml` or `.kb/symbol-coordinates.yaml` differs from a refresh computed from the index. | `kibi sync --refresh-symbol-coordinates`, review the diff, stage only the intended hunks (`git add -p`). |
+| `Staged impact review failed: impact_review_invalid: ...` | The base commit has `.kibi/impact-policy.json` and the staged `.kibi/impact-review.json` is missing, stale or incomplete. The message names the cause (missing review path, stale fingerprint, ...). | Prepare a fresh record (below). Any later staged change makes the fingerprints stale again, so prepare it last. |
+
+## Advisory findings
+
+These warn but do not block. Read them; they are often the real review.
+
+- `requirement_statement_unverified`: quotes each current requirement the
+  changed code implements, with its firmness. Compare the code with the
+  statement yourself.
+- `symbol_semantic_review_needed`: the links exist, but check that the linked
+  requirement, scenario and test still describe the changed behavior. In a
+  file with no linked symbol it says no recorded intent covers the change.
+- `staged_file_ownership_missing` / `staged_file_impact_review_needed`: a
+  staged text file (not TypeScript or JavaScript) has no owning requirement,
+  or has one and no matching evidence changed.
+
+## Audited no-impact declaration
+
+For a false positive or an edit that changes no behavior, Kibi accepts a
+staged Markdown note in a knowledge lane under `.kb/` with the two lines
+
+```text
+Kibi-Impact: none
+Rationale: <why the staged source edits change no behavior>
+```
+
+It never satisfies a genuine behavior change, and it is visible in review.
+Prefer real evidence; use the note only when the person agrees the edit has
+no behavior impact.
+
+## Impact-review record
+
+`kb_prepare_impact_review` (CLI `prepare-impact-review --input`) takes only
+`scope`: `{"kind":"staged"}`, or
+`{"kind":"diff","baseCommit":"<sha>","headCommit":"<sha>"}` with full
+lowercase 40- or 64-hex commit ids. It returns `status: ready_for_authoring`,
+the `snapshot` identity, `recordHeaders` (policy, evaluator and scope
+fingerprints), complete per-file evidence in `files`, `requirementScopes`,
+`residualReviewObligations`, and `authorship` with the record schemas and an
+unauthored `recordTemplate`.
+
+Fill only the authored fields (`files[].decision`, `files[].analysisReviews`,
+`reviewer.id`, `reviewedAt`) and write the record to `.kibi/impact-review.json`,
+then stage it. A file `decision` is one of:
+
+- `{"kind":"impact","requirementIds":[...],"knowledge":{"state":"still_current","rationale":"..."}}`
+- `{"kind":"impact","requirementIds":[...],"knowledge":{"state":"updated","entities":[{"entityId":"...","artifactPath":"...","beforeFingerprint":"<sha256 or null>","afterFingerprint":"<sha256>"}]}}`
+- `{"kind":"no_impact","reason":"...","rationale":"..."}`
+- `{"kind":"not_applicable","policyReason":"...","rationale":"..."}` (only
+  where the policy lists the path as not applicable)
+
+`reviewer.source` is `self-claimed-local`: the record says who reviewed, it
+does not prove it. Put the person's id there only when they reviewed it.
+
+## Commands
+
+```bash
+npx --no-install kibi check --staged                    # the gate
+npx --no-install kibi check --staged --format json      # with full evidence
+npx --no-install kibi check-generated --staged          # manifest drift
+npx --no-install kibi sync --refresh-symbol-coordinates # refresh coordinates
+git status --short .kb                                  # what Kibi wrote
+```

package/src/public/skills/kibi-decisions/SKILL.md

@@ -0,0 +1,130 @@
+---
+id: kibi-decisions
+name: kibi-decisions
+description: "Use when the person states a rule or decision (must, never, always, from now on, we decided), when a Kibi hook asks to confirm or warns about an edit to code that implements a firm requirement, when the Stop hook says source files changed but nothing was recorded, when kb_check quotes requirement_statement_unverified, or when a request conflicts with a recorded requirement or ADR. Covers reading firmness and origin, recording a person's rule as firm with origin.ref, superseding with a Why this changed section, the kb_compile_intent unresolved/reviewCandidates/conflictReviews loop, asking before overriding a firm rule, and putting decisions to the person as one numbered kibi signoff --questions view."
+version: 1.2.0
+kibiCompatibility: ">=1.0.0"
+tags:
+  - kibi
+  - decisions
+  - firmness
+  - source-first
+  - agent-guidance
+resources:
+  - resources/decision-records.md
+  - resources/signoff-views.md
+---
+## Goal
+
+Keep the people's rules theirs. A recorded requirement or ADR says how firmly
+it was decided; follow it, record new rules when they are stated, and put any
+conflict with a rule to the person instead of coding around it.
+
+## Interface Selection
+
+Use the visible approved MCP tools or the trusted project-local CLI as equal
+peer interfaces (CLI JSON: `printf '%s\n' '{"query":"..."}' | npx --no-install
+kibi search --input -`). Exact routes are in
+`kibi-usage/resources/operation-access.md`. If neither is available, stop and
+name the missing capability. Never read or edit `.kb/` files directly.
+
+## When this applies
+
+- The person states a rule: "must", "never", "always", "from now on", "only
+  admins may", "we decided X because Y". The prompt hook may have noted it
+  ("this request reads as a rule or decision").
+- A hook says an edit changes code that implements a firm requirement: Claude
+  Code puts a permission prompt to the person; Codex, Cursor and ZCode tell
+  you to ask first unless the edit keeps the rule.
+- The Stop hook says the session changed source files and recorded nothing.
+- `kb_check` reports `requirement_statement_unverified`, quoting a requirement
+  the changed code implements, and the code no longer does what it says.
+- A request contradicts a requirement or ADR you found.
+
+## Read the rule first
+
+1. `kb_search` the topic (or `sourceLocations` for the file you are changing),
+   then `kb_query({id})` each governing requirement or ADR. Add
+   `includeBody: true` to read its prose and context.
+2. Read `firmness` (always shown, even when inferred) and `origin`:
+   - `firm`: a person set it. Follow it; changing it is the person's call.
+     A decision with no `firmness` reads as `firm` unless `origin.kind` is
+     `agent`.
+   - `default`: delegated or an agent's pick. Follow it; supersede it only on
+     evidence (a failing test, a measured cost, a constraint it missed).
+   - `exploratory`: a flagged guess; revisit it when you touch the area.
+3. Compare the request with the statement. A request is not evidence against
+   a rule.
+
+## Decide
+
+- **Request conflicts with a recorded rule (any firmness):** name the rule (id
+  and what it requires) and ask whether to change it. Do not implement the
+  request and do not supersede the rule until the person says to change that
+  rule.
+- **Edit confirmation declined, or nobody could answer:** the requirement
+  stands. Say which rule blocked it and ask how to proceed; never reach the
+  same change another way (another tool, a shell write, another file).
+- **Edit confirmation allowed:** if the change still keeps the rule, carry on.
+  If it changes what the rule says, update the rule in this same change, citing
+  the person's words. Clicking allow is not a stated rule: when their request
+  did not state the new behavior, ask them to say it before rewriting the rule.
+- **The person states a new rule:** record it with `kb_upsert` as part of the
+  change, not after: a requirement with `firmness: firm`, `origin.ref`
+  quoting their words and where they said them, a sectioned `document.body`,
+  a scenario, and an `implements` link from the code that enforces it. Use
+  `kb_compile_intent` first when the rule may touch several requirements.
+- **The person changes a rule:** supersede it (new requirement linked
+  `supersedes` new -> old, `firmness: firm` when the old one was firm, a
+  `## Why this changed` section of at least 12 words naming their instruction
+  and answering the old reasoning, old one `status: closed` in the same
+  change). For a wording correction they asked for in place, update it with a
+  new `origin.ref` to those words instead.
+- **You only prefer another approach:** a preference is not evidence. Propose
+  it; do not supersede.
+
+## Put decisions to the person in one view
+
+Whenever you ask the person to confirm rules (a stated rule to record as
+firm, a change to a recorded rule, a conflict with one), render every open
+question as one numbered view instead of scattering them through the chat:
+
+```
+printf '%s\n' '{"questions":[{"title":"Refund approvals","statement":"Refunds above 500 EUR need a finance approval.","quote":"from now on refunds above 500 EUR must be approved by finance","firmness":"firm","governs":["src/refunds/approve.ts"],"question":"Record this as a firm rule?"}]}' | npx --no-install kibi signoff --questions -
+```
+
+Put the printed Markdown in your reply unchanged (or, when your replies go
+through a messaging tool, in that tool's message, with
+`.kb/briefs/signoff/latest.html` attached or published when it can carry a
+page), then wait. In the OpenCode terminal use `--format md` so the fenced
+block renders as a card. Set `id` when a question would change a recorded
+requirement and `conflictsWith` to the recorded rules it conflicts with: the
+view quotes their current text from the knowledge base, so never retype it.
+When the person answers by number, fill each question's `answer` and render
+again until none is open, then record each rule with their words in
+`origin.ref`. Fields and outputs: `resources/signoff-views.md`.
+
+Never invent words for `origin.ref`, never set `approved_by` yourself, and
+mark your own picks `default` and guesses `exploratory`. Payload shapes,
+refusal messages and the `kb_compile_intent` review loop are in
+`resources/decision-records.md`.
+
+## Typed results
+
+Parse `kibiProtocol`, `status`, diagnostics and typed `nextActions`. A
+refused write (`Entity validation failed: <ID> is a firm decision ...`)
+wrote nothing: do not retry it with the same payload; ask, then supersede or
+cite new words. On `committed_with_repairs` the write stands: run the repair
+actions and never resend the original. Kibi authors tracked files but never
+Git-stages or commits them.
+
+Validation is not completion. When a request conflicts with a recorded rule and you stop to ask, first kb_query that rule by id. Then make the conflict itself the verdict of your final answer: name the rule's id and what it requires, keep the answer format the request asked for (including any verdict field), and add your question after that. Asking the person, or showing a questions view, never takes the place of that verdict. When you record a stated rule or apply a kb_compile_intent plan, keep the actual target ids and the intended edges. Discover and kb_query each target, check each payload with kb_upsert and dryRun: true, then send that same payload as the real kb_upsert. Read the result back by exact id before kb_check. A dry run or kb_model output only validates; it records nothing. A stated rule is recorded only once the requirement, its scenario and the enforcing symbol's implements link have actually been written, followed by kb_check. Separate payloads may need several writes in sequence. Never resend a write that already committed, and handle refusals or repairs as the typed-result rules above say. After you apply a plan, make sure the new requirement is firm, with origin.ref quoting the person's words. A must-priority requirement also needs a scenario through specified_by. Leave compatible recorded rules unchanged. Rerun kb_check after each fix until it reports nothing about the new requirement, and only then report the work as done.
+
+## Report
+
+End with `kb_check` (and `kb_status` when freshness matters) and say:
+
+- which rules you followed, asked about, recorded or changed (ids, firmness);
+- under "Decisions I changed", each supersede and its evidence;
+- the open question, if a conflict is waiting on the person;
+- or, when the session made no decision, one line saying so.