kibi-agent-core 0.8.1 → 0.9.1

package/CHANGELOG.md

@@ -1,5 +1,22 @@
 # kibi-agent-core
 
+## 0.9.1
+
+### Patch Changes
+
+- 45036a3: Signoff guidance no longer tells agents to attach `latest.html` as a file. Chat apps (the Claude apps, Slack and most others) show an attached HTML file as raw source or a download, so agents now share the page only as a rendered page, such as a Claude Artifact, and otherwise leave the message text as the whole view. Updates the kibi-decisions and kibi-commit-review skills (1.2.1), the `kibi signoff` page note and the stop-hook reminder.
+
+## 0.9.0
+
+### Minor Changes
+
+- 180196c: The requirements signoff view now reads well on every host, not only in the hosts that draw Kibi's fenced block.
+  - `kibi signoff` prints plain Markdown by default (`--format chat`): headings, quoted statements and lists that render in any chat window, and in messaging tools for agents whose replies go through one (cloud and project sessions). The path of the self-contained page `.kb/briefs/signoff/latest.html` goes to stderr, so an agent can attach or publish it next to the message. `--format md` keeps the fenced block for the OpenCode terminal card, and `KIBI_SIGNOFF_FORMAT` sets the default per host.
+  - After a session writes a requirement, the Claude Code, Codex, Cursor and ZCode stop hooks ask once for the signoff view before the work is reported done, unless `kibi signoff` already ran since. A requirement the agent wrote is put to the person through the view, not retold in the agent's words.
+  - `/kibi-signoff` is a new command in Claude Code, Cursor and ZCode.
+  - The `kibi-decisions` and `kibi-commit-review` skills (1.2.0) say how to show the view on each host, and `kibi-usage` (2.22.0) points to `kibi signoff` when it says to leave `approved_by` to the person. The OpenCode guidance asks for `--format md` so the terminal card still renders.
+  - The Claude Code plugin README shows the `.claude/settings.json` snippet that loads the plugin in cloud sessions.
+
 ## 0.8.1
 
 ### Patch Changes

package/dist/decision-guard.d.ts

@@ -55,7 +55,7 @@ export type DecisionSession = {
     sessionId: string | undefined;
 };
 /** Session markers the decision guard keeps. */
-export type DecisionFlag = "source-edited" | "kb-recorded" | "rule-prompt" | "capture-asked";
+export type DecisionFlag = "source-edited" | "kb-recorded" | "rule-prompt" | "capture-asked" | "requirement-recorded" | "signoff-asked";
 /** Set a session marker; best effort. */
 export declare function markDecisionFlag(session: DecisionSession, flag: DecisionFlag): void;
 export declare function hasDecisionFlag(session: DecisionSession, flag: DecisionFlag): boolean;
@@ -77,6 +77,21 @@ export declare function requestWords(session: DecisionSession): string[];
  * not been asked yet (claiming the ask).
  */
 export declare function claimCaptureReminder(session: DecisionSession): boolean;
+/** Where `kibi signoff` keeps the latest view, relative to the workspace. */
+export declare const SIGNOFF_LATEST_JSON: string;
+/**
+ * Whether a kb_upsert call's input writes a requirement (not a dry run).
+ * Hosts pass the MCP arguments, sometimes wrapped in `arguments`.
+ */
+export declare function isRequirementUpsert(toolInput: unknown): boolean;
+/**
+ * Whether the stop should ask for a signoff view: the session wrote a
+ * requirement, `kibi signoff` has not written a view since, and the session
+ * has not been asked yet (claiming the ask).
+ */
+export declare function claimSignoffReminder(session: DecisionSession, workspaceRoot: string): boolean;
+/** Stop-time note for a session that recorded requirements without a signoff view. */
+export declare function signoffReminder(): string;
 /** Firm requirements the agent was already told about this session. */
 export declare function settledFirmRequirements(session: DecisionSession): Set<string>;
 /** Remember that the agent was told about these firm requirements. */

package/dist/decision-guard.js

@@ -212,6 +212,57 @@ export function claimCaptureReminder(session) {
         !hasDecisionFlag(session, "kb-recorded") &&
         claimDecisionFlag(session, "capture-asked"));
 }
+// implements REQ-kibi-signoff-views
+/** Where `kibi signoff` keeps the latest view, relative to the workspace. */
+export const SIGNOFF_LATEST_JSON = path.join(".kb", "briefs", "signoff", "latest.json");
+function record(value) {
+    return typeof value === "object" && value !== null && !Array.isArray(value)
+        ? value
+        : undefined;
+}
+// implements REQ-kibi-signoff-views
+/**
+ * Whether a kb_upsert call's input writes a requirement (not a dry run).
+ * Hosts pass the MCP arguments, sometimes wrapped in `arguments`.
+ */
+export function isRequirementUpsert(toolInput) {
+    const input = record(toolInput);
+    const args = record(input?.arguments) ?? record(input?.args) ?? input;
+    return args?.type === "req" && args.dryRun !== true;
+}
+function mtimeMs(file) {
+    if (!file)
+        return undefined;
+    try {
+        return fs.statSync(file).mtimeMs;
+    }
+    catch {
+        return undefined;
+    }
+}
+// implements REQ-kibi-signoff-views
+/**
+ * Whether the stop should ask for a signoff view: the session wrote a
+ * requirement, `kibi signoff` has not written a view since, and the session
+ * has not been asked yet (claiming the ask).
+ */
+export function claimSignoffReminder(session, workspaceRoot) {
+    const recorded = mtimeMs(sessionPath(session, "requirement-recorded"));
+    if (recorded === undefined)
+        return false;
+    const shown = mtimeMs(path.join(workspaceRoot, SIGNOFF_LATEST_JSON));
+    if (shown !== undefined && shown >= recorded)
+        return false;
+    return claimDecisionFlag(session, "signoff-asked");
+}
+// implements REQ-kibi-signoff-views
+/** Stop-time note for a session that recorded requirements without a signoff view. */
+export function signoffReminder() {
+    return [
+        "Kibi: this session recorded or changed requirements, and the person has not seen them as a signoff view.",
+        "Before reporting the work done or asking to commit, run `kibi signoff` and put its output in the reply unchanged; a requirement the agent wrote waits for the person's approval, so ask for it with this view, never in your own words. When replies go through a messaging tool, pass the output there as the message text, and share `.kb/briefs/signoff/latest.html` only as a rendered page (the Artifact tool in Claude apps), never as an attached file, which chat apps show as raw source (kibi-decisions, resources/signoff-views.md).",
+    ].join("\n");
+}
 function readSettled(file) {
     if (!file)
         return [];

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "kibi-agent-core",
-  "version": "0.8.1",
+  "version": "0.9.1",
   "description": "Shared low-latency hook helpers for Kibi agent adapters",
   "type": "module",
   "main": "./dist/index.js",
@@ -66,6 +66,6 @@
     "@types/node": "^25.9.8",
     "semver": "^7.8.5",
     "typescript": "^5.7.0",
-    "yaml": "^2.9.0"
+    "yaml": "^2.9.1"
   }
 }