kibi-cli 2.29.0 → 2.31.0

package/dist/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/dist/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/dist/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.

package/dist/public/skills/kibi-decisions/resources/decision-records.md

@@ -0,0 +1,142 @@
+# Decision records
+
+Reference for `kibi-decisions`: what the hooks say, the payloads that record
+or change a rule, what Kibi refuses, and the `kb_compile_intent` review loop.
+
+## What the hooks say
+
+| Hook | Text you see | What it means |
+| --- | --- | --- |
+| Prompt submit | `Kibi: this request reads as a rule or decision (it says "<phrase>").` | The phrase matched words such as "must", "never", "always", "from now on", "has to". It only asks whether there is something to record; check with `kb_search`. |
+| Before an edit (Claude Code) | A permission prompt: `Kibi: this edit changes <symbol>, which implements a firm requirement recorded in the knowledge base: <ID>: <title>. Allow it if ...` | The person decides. You are also told: if the edit was declined or could not be confirmed, the requirement stands; if allowed and the change alters what the requirement says, update the requirement with `kb_upsert` in this change. |
+| Before an edit (Codex, Cursor, ZCode) | `Kibi: this edit changes <where>, which implements a firm requirement, a rule the person set: ...` | The host cannot prompt the person, so you must: unless the edit keeps the rule, ask before making it and name the rule. |
+| Stop | `Kibi: this session changed source files and recorded nothing in the knowledge base.` (or the variant naming a rule-like request) | Record the decision the person stated or the change made (a rule, a limit, a default, who may do what) as a requirement linked to its code, or say in one line that there was none. Asked once per session. |
+
+The firm-edit prompt covers current requirements whose effective firmness is
+`firm` and that the edited symbol (or, for a whole-file write, any symbol of
+the file) implements. Superseded and retired requirements never ask. An
+operator can turn the prompt off with `KIBI_CONFIRM_FIRM_EDITS=0`; that does
+not make a firm rule negotiable.
+
+`kb_check` with `sourceFiles` and `includeImpactDiagnostics: true` reports
+`requirement_statement_unverified` (warning) for each current requirement a
+changed behavioral symbol implements, quoting its statement and firmness.
+Kibi never compares code with prose: you do. A change that no longer does what
+the quote says is a conflict with a recorded rule.
+
+## Effective firmness
+
+| `firmness` | `origin.kind` | Effective |
+| --- | --- | --- |
+| `firm`, `default` or `exploratory` | any | as written |
+| absent | `agent` | `default` |
+| absent | `human`, `import`, `migration`, or no origin | `firm` |
+
+`kb_search` answers and `kb_query` rows show the effective value. Hook
+snippets label firm decisions `[firm: ask before changing]` and exploratory
+ones `[exploratory]`; an unlabeled decision is `default`.
+
+## Record a rule the person stated
+
+Discover first (`kb_search`, `kb_query`). If a current requirement already
+says it, link to it instead of restating it. Otherwise write the scenario
+first, then the requirement (the requirement's write sends `specified_by`):
+
+```json
+{"type":"req","id":"REQ-billing-refund-approval","properties":{"title":"Refunds above 500 EUR need a finance approval","status":"open","priority":"must","firmness":"firm","origin":{"kind":"agent","ref":"session request: \"from now on refunds above 500 EUR must be approved by finance\""}},"relationships":[{"type":"specified_by","from":"REQ-billing-refund-approval","to":"SCEN-billing-refund-approval"}],"document":{"body":"Refunds above 500 EUR need a finance approval.\n\n## Context\n\nThe person asked for this rule while changing the refund flow; reason not stated.\n\n## Source\n\n> from now on refunds above 500 EUR must be approved by finance\n\nSession request."}}
+```
+
+Then link the enforcing symbol with `implements` (and its test with
+`covered_by`). Preview with `dryRun: true` when unsure; a passing dry run is
+validation, not the write.
+
+- `origin.ref` is where the words are and the words themselves: a ticket URL,
+  a document path with line, or the session request quoted. Kibi checks that a
+  reference exists, not that it is genuine, so never write words nobody said.
+- `kb_upsert` records `origin.kind: agent` when you omit `origin`; the explicit
+  `firmness: firm` is what makes the rule the person's. Leave
+  `origin.approved_by` to the person.
+- A rule from a document, test or ticket a person wrote is `firm` too, with
+  `origin.ref` to that source.
+- Your own choice is `default`; a guess is `exploratory`. Write the value
+  explicitly whenever you record a decision.
+- For strict modeling (claim keys, predicate facts) follow `kibi-usage`,
+  "Second-agent edits", recipe 1.
+
+## Supersede a rule
+
+Only when the person said to change that rule (firm), or on evidence (default):
+
+1. Write the new scenario, then the new requirement with `supersedes` to the
+   old one (direction new -> old), `firmness: firm` when the old one was firm,
+   `origin.ref` to the person's instruction, and a body section:
+
+   ```markdown
+   ## Why this changed
+
+   The person asked on 2026-10-21 to raise the approval threshold to 1000 EUR
+   because finance now reviews refunds weekly; the old 500 EUR limit predates
+   that review.
+   ```
+
+   At least 12 words, naming the evidence and answering the old decision's
+   reasoning.
+2. Upsert the old requirement with `status: closed` in the same change (its
+   stored `title`, the new status; status and links stay editable on a firm
+   decision).
+3. Re-point or close the old scenario, and move `implements` links to the new
+   requirement when the code now enforces it.
+4. Run `kb_check`.
+
+A preference ("this would be cleaner") is not evidence: propose it in the
+report instead of superseding. An authored requirement is never deleted:
+`kb_delete` returns `outcome: supersession_required`.
+
+## Correct a firm rule in place
+
+When the person asks for a correction that keeps the rule's meaning (a typo, a
+clearer title), update the existing requirement with a new `origin.ref` citing
+their words. Without new human words, Kibi refuses to change a firm decision's
+title, statement (or an ADR's body) or to lower its firmness.
+
+## What Kibi refuses or blocks
+
+| Where | Code or message | Fix |
+| --- | --- | --- |
+| `kb_upsert`, `dryRun`, `kb_apply_plan` step | `Entity validation failed: <ID> is a firm decision, so kb_upsert does not change its <fields> in place.` | Ask the person; then cite their words in `origin.ref`, or supersede with a firm decision. |
+| `kb_upsert` | `firmness: firm` without `origin.ref` (or `approval_ref` on a requirement) | Add the reference to the person's words. |
+| `kb_upsert` | `firmness is only valid on req and adr entities` | Remove `firmness` from facts, scenarios, tests and symbols. |
+| `kb_check` | `decision-firm-unreferenced` | As above. |
+| `kb_check` | `decision-firm-superseded` | The superseding decision must be `firm` too. |
+| `kb_check` | `decision-firm-edited` | A firm decision's claim changed in the working tree since `HEAD` without new words; revert, or cite their words. |
+| `kb_check` | `supersedes-reason-missing` | Add `## Why this changed` (12+ words). |
+| `kb_check` | `superseded-requirement-open` | Close the superseded requirement. |
+
+## The kb_compile_intent review loop
+
+`kb_compile_intent` (`mode: "create"` or `"update"`, the complete intent,
+`context` when creating) is read-only and returns a plan.
+
+- `contradictionAnalysis.outcome`:
+  - `no_conflict`: the check could decide and found none.
+  - `conflict`: a witness or your own verdict says the intent contradicts a
+    current requirement. The plan `status` is `blocked`.
+  - `unresolved`: Kibi could not decide. `reasons` say why
+    (`unmodeled_target`, `unmodeled_related`, `analysis_unavailable`). Never
+    read it as consistent.
+- `reviewCandidates[]`: up to five current requirements Kibi could not compare
+  logically, each with `requirementId`, `title`, `sentence` (the closest
+  sentence), `statement`, `score`, `modeled` and `review` (`pending`,
+  `conflict` or `no_conflict`).
+- Compare the intent with each candidate's `statement`, then compile again
+  with the same input plus
+  `conflictReviews: [{"requirementId": "...", "verdict": "conflict" | "no_conflict", "note": "..."}]`.
+  A verdict may also name a requirement discovery did not rank.
+- On `conflict`: ask the person which rule holds. Then supersede or change
+  the requirement (as above), or change the intent, and compile again.
+- Plan `status` is `ready`, `needs_resolution` (ambiguous or unmodeled
+  propositions, missing targets) or `blocked`. Apply only a `ready` plan the
+  person approved, with `kb_apply_plan` and its full `planHash`.
+- A compiled plan records the new requirement as an agent's. When the intent
+  is the person's stated rule, follow the apply with a `kb_upsert` that sets
+  `firmness: firm` and `origin.ref` on that requirement.

package/dist/public/skills/kibi-decisions/resources/signoff-views.md

@@ -0,0 +1,66 @@
+# Signoff views
+
+`kibi signoff` renders what a person signs off, so the agent never retypes
+requirement text from memory. It is a CLI command, not an MCP tool.
+
+| View | Command | When |
+| --- | --- | --- |
+| Decisions to confirm | `kibi signoff --questions <file or ->` | Mid-work: rules to record as firm, a change to a recorded rule, a conflict |
+| Requirements signoff | `kibi signoff` (`--staged` for the index) | End of work: before asking to commit |
+
+Both print plain Markdown by default (`--format chat`): headings, quoted
+statements and lists that render in any chat or messaging surface. Put it in
+your reply unchanged: never wrap it in a code block, summarize it or retell a
+requirement in your own words. Every run also writes
+`.kb/briefs/signoff/latest.json`, `latest.md` and `latest.html` (git-ignored);
+`latest.html` is a self-contained page with the full view.
+
+## Showing it on your host
+
+| Host | Best view |
+| --- | --- |
+| Claude Code, Codex, Cursor, ZCode, VS Code chat | Paste the default output; `/kibi-signoff` (Claude Code, Cursor, ZCode) runs it. Offer `kibi signoff --format html --open` for the page |
+| OpenCode terminal | `kibi signoff --format md` and paste the fenced block unchanged: kibi-opencode draws it as a card, and `/kibi-signoff` reopens it |
+| Replies sent through a messaging tool (cloud or project threads, chat bots) | Pass the default output as the message text, and attach or publish `.kb/briefs/signoff/latest.html` next to it when the tool can carry a file or a page |
+| VS Code or Cursor with the kibi-vscode extension | The **Kibi: Show Requirements Signoff** panel follows every run |
+| Remote machine, no browser | Give the person the path of `latest.html` |
+
+`--format md` wraps the same Markdown in a ```` ```kibi-signoff ```` or
+```` ```kibi-questions ```` fence for host renderers; use it only where one
+draws it, because everywhere else a fence shows as raw code.
+`KIBI_SIGNOFF_FORMAT` sets the default for a host. `--format html --open`
+writes and opens the page; `--format json` prints the view.
+
+## Questions input
+
+`{"questions":[...]}` or a bare array. Each question:
+
+| Field | Required | Meaning |
+| --- | --- | --- |
+| `statement` | yes | The rule as it would be recorded |
+| `title` | no | A short name for the card |
+| `id` | no | The recorded requirement the question would change; the view quotes its current statement and firmness |
+| `quote` | no | The person's words that would go in `origin.ref` |
+| `firmness` | no | `firm`, `default` or `exploratory`, as it would be recorded |
+| `governs` | no | Files or symbols the rule governs |
+| `conflictsWith` | no | Recorded requirement ids it conflicts with; the view quotes them |
+| `question` | no | What you ask, when it is more than "record this?" |
+| `answer` | no | The person's answer; answered questions are struck out |
+
+The person answers by number ("1 yes, 2 exploratory, 3 reword: ..."). Copy
+each answer into `answer`, render again, and record the rules only once every
+question is answered. An answer is the person's words: quote it in
+`origin.ref`; a view itself is never an approval.
+
+## Summary contents
+
+| Section | Meaning |
+| --- | --- |
+| New | Requirement documents the change adds |
+| Changed | Rewritten requirements; a changed statement shows before and after |
+| Affected by the code change | Unchanged requirements whose implementing code changed (the `requirement_statement_unverified` set) |
+| Superseded or retired | Requirements the change retires, supersedes or deletes |
+
+Each requirement shows its firmness, origin, superseded rules, changed code
+symbols, scenarios and proof state (the earliest unmet proof gate). Parts
+Kibi could not compute are named in a `Note:` line instead of failing.

package/dist/public/skills/kibi-freshness/SKILL.md

@@ -2,7 +2,7 @@
 id: kibi-freshness
 name: kibi-freshness
 description: Check exact Git attachment, branch migration/quarantine, compiled-store freshness, source linkage, and repair state before decisions or writes.
-version: 2.0.0
+version: 2.1.0
 kibiCompatibility: ">=1.0.0"
 tags:
   - kibi
@@ -53,6 +53,8 @@ echo '{}' | npx --no-install kibi status --input -
   `committed_with_repairs`, follow required typed `nextActions`; never retry the
   original operation.
 
+For every freshness, branch, or completion question, call `kb_status` first, then `kb_query` the entities and source files that status names, then `kb_check` as the last Kibi call before answering. Never skip the query step, even when status alone seems to answer the question. If another query or write follows a check, run `kb_check` again before answering. When asked whether requirements are consistent or proven, run `kb_query`, then `kb_check` with the rules `domain-contradictions`, `kb-consistency` and `kb-consistency-unresolved`, then `kb_coverage`, and read whether the analysis was complete. `domain-contradictions` compares facts two at a time; `kb-consistency` checks every fact of a property together, so a clean pairwise result is not proof. Report a `kb-consistency` violation as a conflict, name every requirement it lists, and give superseding or changing one of them as the next step; never edit or delete facts to make the check pass. Report a context `kb-consistency-unresolved` names as unresolved, never as consistent, with the step that would make it comparable. Report any unmodeled or unknown clause as incomplete analysis, not as consistent. Only when every clause is fully modeled and compatible, state plainly that no conflict was found. For authorized knowledge changes, keep the exact supplied target and intended relationship edges, and discover and query those targets first. Validate the payload with `kb_upsert` and `dryRun: true`, then perform the authorized `kb_upsert` with that same payload and read the result back exactly before the final checks. A passing dry run is validation, not completion. Distinct authorized payloads may need several sequential writes, each validated and read back, but never retry a mutation that already committed. If a mutation returns `committed_with_repairs`, follow its typed `nextActions` instead of repeating the original operation.
+
 ## Guidance
 
 - Treat MCP and the trusted project-local CLI as equal peer surfaces.

package/dist/public/skills/kibi-traceability/SKILL.md

@@ -29,6 +29,8 @@ interfaces. Select the surface by capability; neither is semantically preferred.
 For CLI JSON, use a dedicated route such as
 `printf '%s\n' '{}' | kibi status --input -`.
 
+For every traceability answer, begin with `kb_search` even when an identifier is already named, then exact-filter with `kb_query`, inspect relationships with `kb_graph`, and make `kb_status` the final Kibi call, including after `kb_graph` or `kb_coverage`; report no conclusions until that closing `kb_status` returns. When judging scenario feasibility, ground each step in the queried requirements, scenarios, tests, and symbols, and state missing links, ambiguity, or stale evidence explicitly rather than inferring them. For authorized coverage or link work, keep the exact supplied target and intended edges, discover and query those targets, then validate the payload with `kb_upsert` and `dryRun: true`. A passing dry run is only validation, not completion: next perform the real `kb_upsert` with the same payload, exact-read the result back with `kb_query`, run `kb_check` and `kb_coverage`, report the resulting proof state, and finish with `kb_status`. Distinct authorized payloads may each need their own sequential dry run and write, so there is no single-write limit, but never retry a mutation that already committed; on `committed_with_repairs`, execute the typed repair action instead.
+
 ## Workflow
 
 Use the visible approved MCP tools or trusted project-local CLI as equal peer
@@ -50,6 +52,8 @@ plan_returned` with a hash-bound plan whose `nextActions[0].input` is the exact
 through a new requirement linked with `supersedes`. Relationship deletes patch
 shards while preserving unrelated records.
 
+For executable coverage work, keep the production symbol's implements link to its requirement and link that same production symbol to its qualifying test with covered_by; reserve executable_for for a symbol that stands for the executable test itself, and never put executable_for on a symbol that also carries production ownership or coverage. Preserve the exact supplied target and intended edges, discover and query those targets, validate the payload with `kb_upsert` and `dryRun: true`, then perform the authorized real `kb_upsert` with the same payload and exact-read the result with `kb_query` before final checks, because validation alone is not completion. A passing dry run does not guarantee the commit: if the real `kb_upsert` returns an error, read its message and correct only the conflicting relationship on the same target rather than working around it with a new entity, then validate again with `dryRun: true`, write again, and exact-read it back. Distinct authorized payloads may each need their own sequential validation and write, so there is no single write limit, but never retry a mutation that already committed; on `committed_with_repairs`, execute the typed repair action instead. Then run `kb_check` and `kb_coverage`, report the proof and verification state they return, treating a dirty verification snapshot after a write as expected rather than as a failure, and finish with `kb_status`.
+
 ## Typed recovery and proof
 
 Parse `kibiProtocol`, `resultVersion`, `status`, `effects`, diagnostics, and