kibi-cli 2.31.0 → 2.31.1

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
@@ -136,7 +136,7 @@ export async function signoffCommand(options, deps = {}) {
136
136
  else if (format === "chat") {
137
137
  write(`${renderSignoffChatMarkdown(view)}\n`);
138
138
  // The page path goes to stderr so stdout stays pasteable as the reply.
139
- (deps.writeNote ?? ((text) => process.stderr.write(text)))(`Kibi signoff page: ${path.join(cwd, SIGNOFF_LATEST_HTML)} (attach or publish it next to the reply when the host can show a page)\n`);
139
+ (deps.writeNote ?? ((text) => process.stderr.write(text)))(`Kibi signoff page: ${path.join(cwd, SIGNOFF_LATEST_HTML)} (publish it as a rendered page, such as a Claude Artifact, when the host has a page tool; an attached .html file shows as raw source in chat apps)\n`);
140
140
  }
141
141
  else {
142
142
  const target = options.output?.trim()
@@ -2,7 +2,7 @@
2
2
  id: kibi-commit-review
3
3
  name: kibi-commit-review
4
4
  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."
5
- version: 1.2.0
5
+ version: 1.2.1
6
6
  kibiCompatibility: ">=1.0.0"
7
7
  tags:
8
8
  - kibi
@@ -85,8 +85,9 @@ requirement with its statement (before and after for a rewrite), firmness,
85
85
  origin, scenarios and proof state. Put it in your reply unchanged (in the
86
86
  messaging tool's message when replies go through one), then add one or two
87
87
  sentences on why the requirements changed. Offer the full page with
88
- `kibi signoff --format html --open`, or attach or publish
89
- `.kb/briefs/signoff/latest.html` when your host can carry a file or a page;
88
+ `kibi signoff --format html --open`, or publish `.kb/briefs/signoff/latest.html`
89
+ as a rendered page when your host has a page tool (the Artifact tool in Claude
90
+ apps); never attach the `.html` as a file, which chat apps show as raw source;
90
91
  past 15 requirements the Markdown stops and only the page lists them all.
91
92
  Host details: `kibi-decisions`, `resources/signoff-views.md`. `--no-proof` skips the proof lookup, which reads coverage and is slow
92
93
  on a large knowledge base. The summary is not an approval: never set
@@ -2,7 +2,7 @@
2
2
  id: kibi-decisions
3
3
  name: kibi-decisions
4
4
  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."
5
- version: 1.2.0
5
+ version: 1.2.1
6
6
  kibiCompatibility: ">=1.0.0"
7
7
  tags:
8
8
  - kibi
@@ -13,7 +13,8 @@ statements and lists that render in any chat or messaging surface. Put it in
13
13
  your reply unchanged: never wrap it in a code block, summarize it or retell a
14
14
  requirement in your own words. Every run also writes
15
15
  `.kb/briefs/signoff/latest.json`, `latest.md` and `latest.html` (git-ignored);
16
- `latest.html` is a self-contained page with the full view.
16
+ `latest.html` is a self-contained page with the full view, meant to be opened
17
+ in a browser or published as a page, not attached as a file.
17
18
 
18
19
  ## Showing it on your host
19
20
 
@@ -21,7 +22,7 @@ requirement in your own words. Every run also writes
21
22
  | --- | --- |
22
23
  | 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 |
23
24
  | OpenCode terminal | `kibi signoff --format md` and paste the fenced block unchanged: kibi-opencode draws it as a card, and `/kibi-signoff` reopens it |
24
- | 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 |
25
+ | Replies sent through a messaging tool (cloud or project threads, chat bots) | Pass the default output as the message text. Share `latest.html` only as a rendered page: in Claude apps (claude.ai, the mobile and desktop apps, Claude Code on the web) publish it with the Artifact tool and give its link. Never attach the `.html` as a file: the Claude apps, Slack and most chat apps show it as raw source or a download. With no page tool, the message text is the whole view |
25
26
  | VS Code or Cursor with the kibi-vscode extension | The **Kibi: Show Requirements Signoff** panel follows every run |
26
27
  | Remote machine, no browser | Give the person the path of `latest.html` |
27
28
 
package/package.json CHANGED
@@ -1,6 +1,6 @@
1
1
  {
2
2
  "name": "kibi-cli",
3
- "version": "2.31.0",
3
+ "version": "2.31.1",
4
4
  "type": "module",
5
5
  "description": "Kibi CLI for knowledge base management",
6
6
  "engines": {
@@ -2,7 +2,7 @@
2
2
  id: kibi-commit-review
3
3
  name: kibi-commit-review
4
4
  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."
5
- version: 1.2.0
5
+ version: 1.2.1
6
6
  kibiCompatibility: ">=1.0.0"
7
7
  tags:
8
8
  - kibi
@@ -85,8 +85,9 @@ requirement with its statement (before and after for a rewrite), firmness,
85
85
  origin, scenarios and proof state. Put it in your reply unchanged (in the
86
86
  messaging tool's message when replies go through one), then add one or two
87
87
  sentences on why the requirements changed. Offer the full page with
88
- `kibi signoff --format html --open`, or attach or publish
89
- `.kb/briefs/signoff/latest.html` when your host can carry a file or a page;
88
+ `kibi signoff --format html --open`, or publish `.kb/briefs/signoff/latest.html`
89
+ as a rendered page when your host has a page tool (the Artifact tool in Claude
90
+ apps); never attach the `.html` as a file, which chat apps show as raw source;
90
91
  past 15 requirements the Markdown stops and only the page lists them all.
91
92
  Host details: `kibi-decisions`, `resources/signoff-views.md`. `--no-proof` skips the proof lookup, which reads coverage and is slow
92
93
  on a large knowledge base. The summary is not an approval: never set
@@ -2,7 +2,7 @@
2
2
  id: kibi-decisions
3
3
  name: kibi-decisions
4
4
  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."
5
- version: 1.2.0
5
+ version: 1.2.1
6
6
  kibiCompatibility: ">=1.0.0"
7
7
  tags:
8
8
  - kibi
@@ -13,7 +13,8 @@ statements and lists that render in any chat or messaging surface. Put it in
13
13
  your reply unchanged: never wrap it in a code block, summarize it or retell a
14
14
  requirement in your own words. Every run also writes
15
15
  `.kb/briefs/signoff/latest.json`, `latest.md` and `latest.html` (git-ignored);
16
- `latest.html` is a self-contained page with the full view.
16
+ `latest.html` is a self-contained page with the full view, meant to be opened
17
+ in a browser or published as a page, not attached as a file.
17
18
 
18
19
  ## Showing it on your host
19
20
 
@@ -21,7 +22,7 @@ requirement in your own words. Every run also writes
21
22
  | --- | --- |
22
23
  | 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 |
23
24
  | OpenCode terminal | `kibi signoff --format md` and paste the fenced block unchanged: kibi-opencode draws it as a card, and `/kibi-signoff` reopens it |
24
- | 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 |
25
+ | Replies sent through a messaging tool (cloud or project threads, chat bots) | Pass the default output as the message text. Share `latest.html` only as a rendered page: in Claude apps (claude.ai, the mobile and desktop apps, Claude Code on the web) publish it with the Artifact tool and give its link. Never attach the `.html` as a file: the Claude apps, Slack and most chat apps show it as raw source or a download. With no page tool, the message text is the whole view |
25
26
  | VS Code or Cursor with the kibi-vscode extension | The **Kibi: Show Requirements Signoff** panel follows every run |
26
27
  | Remote machine, no browser | Give the person the path of `latest.html` |
27
28