@skrr-ai/cli 0.1.123 → 0.1.125

package/dist/commands/agents/chat.d.ts

@@ -59,6 +59,31 @@ export declare function interruptedDetachMessage(input: {
     /** The second Ctrl-C: the CLI stopped waiting rather than running out the grace period. */
     forced?: boolean;
 }): string;
+/**
+ * `--jsonl` prints `text.delta` as a real delta unless `--cumulative` asks for the whole answer
+ * so far in every event. The cumulative form costs the square of the answer's length (a 57 KB
+ * answer printed 34.6 MB, OSK-20596), which is the wrong default for the mode scripts and other
+ * agents drive. `--incremental` is the old opt-in for what is now the default and changes nothing.
+ */
+export declare function jsonlTextForm(flags: {
+    cumulative?: boolean;
+}): {
+    incrementalText: boolean;
+};
+/**
+ * What to say when the user pressed Ctrl-C and the server then confirmed the run ended.
+ *
+ * The warning printed at the keypress ("a tool call already running on the runtime is not
+ * guaranteed to stop") is written before the outcome is known. When the run settles as `aborted`
+ * it is no longer the whole truth, and left as the last line it reads as a cancel that failed:
+ * the CLI exited without a word, the prompt came back, and a person could not tell whether to go
+ * and kill something (OSK-20603). A script has `run.result {status: "aborted"}`; a terminal gets
+ * this line. It claims what the server said, that the run ended, and nothing about processes.
+ */
+export declare function cancelledRunMessage(input: {
+    sessionId: string;
+    conversationId?: string | null;
+}): string;
 /**
  * What the durable record says about a turn, read from its messages.
  *
@@ -228,6 +253,7 @@ export default class AgentsChat extends BaseCommand {
         'thread-root': import("@oclif/core/interfaces").OptionFlag<string | undefined, import("@oclif/core/interfaces").CustomOptions>;
         'no-stream': import("@oclif/core/interfaces").BooleanFlag<boolean>;
         quick: import("@oclif/core/interfaces").BooleanFlag<boolean>;
+        cumulative: import("@oclif/core/interfaces").BooleanFlag<boolean>;
         incremental: import("@oclif/core/interfaces").BooleanFlag<boolean>;
         jsonl: import("@oclif/core/interfaces").BooleanFlag<boolean>;
         json: import("@oclif/core/interfaces").BooleanFlag<boolean>;

package/dist/commands/agents/chat.js

@@ -3,6 +3,8 @@ Object.defineProperty(exports, "__esModule", { value: true });
 exports.MAX_HANDOVER_WAIT_SECONDS = exports.DEFAULT_HANDOVER_WAIT_SECONDS = exports.STREAM_LOST_EXIT_CODE = exports.DETACH_EXIT_CODE = void 0;
 exports.streamedResultExitCode = streamedResultExitCode;
 exports.interruptedDetachMessage = interruptedDetachMessage;
+exports.jsonlTextForm = jsonlTextForm;
+exports.cancelledRunMessage = cancelledRunMessage;
 exports.reconcileTerminalFromMessages = reconcileTerminalFromMessages;
 exports.handoverStateFromMessages = handoverStateFromMessages;
 exports.handoverInterruptMessage = handoverInterruptMessage;
@@ -88,6 +90,29 @@ function interruptedDetachMessage(input) {
             ? ''
             : ', and look for a surviving process with `ps -ef | grep -i claude`'));
 }
+/**
+ * `--jsonl` prints `text.delta` as a real delta unless `--cumulative` asks for the whole answer
+ * so far in every event. The cumulative form costs the square of the answer's length (a 57 KB
+ * answer printed 34.6 MB, OSK-20596), which is the wrong default for the mode scripts and other
+ * agents drive. `--incremental` is the old opt-in for what is now the default and changes nothing.
+ */
+function jsonlTextForm(flags) {
+    return { incrementalText: flags.cumulative !== true };
+}
+/**
+ * What to say when the user pressed Ctrl-C and the server then confirmed the run ended.
+ *
+ * The warning printed at the keypress ("a tool call already running on the runtime is not
+ * guaranteed to stop") is written before the outcome is known. When the run settles as `aborted`
+ * it is no longer the whole truth, and left as the last line it reads as a cancel that failed:
+ * the CLI exited without a word, the prompt came back, and a person could not tell whether to go
+ * and kill something (OSK-20603). A script has `run.result {status: "aborted"}`; a terminal gets
+ * this line. It claims what the server said, that the run ended, and nothing about processes.
+ */
+function cancelledRunMessage(input) {
+    return (`Run ${input.sessionId} cancelled: the server confirmed it ended.` +
+        (input.conversationId ? ` Continue the conversation with --conversation ${input.conversationId}.` : ''));
+}
 /**
  * What the durable record says about a turn, read from its messages.
  *
@@ -379,20 +404,29 @@ class AgentsChat extends base_command_1.BaseCommand {
                 'agent’s runtime, tools, session, or working directory and cannot perform work — ' +
                 'it is for inline text assistance. Use --no-stream for a real turn.',
         }),
+        cumulative: core_1.Flags.boolean({
+            description: 'With --jsonl, make `text.delta` carry the whole answer so far in `text` (plus `delta`, ' +
+                'the characters it adds, when it only appends) and repeat the envelopes that ' +
+                '`session.output` already carries: the form --jsonl had before it was incremental by ' +
+                'default. A long answer written this way grows with the square of its length ' +
+                '(a 57 KB answer printed 34.6 MB), so use it only for a consumer that must read ' +
+                'the answer from any single event.',
+            dependsOn: ['jsonl'],
+            exclusive: ['incremental'],
+        }),
         incremental: core_1.Flags.boolean({
-            description: 'With --jsonl, make `text.delta` a real delta: it carries only `delta`, the characters ' +
-                'it adds, instead of the whole answer so far, and leaves out the envelopes that ' +
-                '`session.output` already carries. A rewrite that is not an append arrives as ' +
-                '`replace`, the new full text. `run.result` still holds the whole answer. Without it ' +
-                'a long answer written as JSON lines grows with the square of its length.',
+            hidden: true,
+            description: 'No longer needed: --jsonl is incremental by default. Accepted so scripts that already ' +
+                'pass it keep working.',
             dependsOn: ['jsonl'],
         }),
         jsonl: core_1.Flags.boolean({
             description: 'Emit one JSON event per line while streaming. Every line is a complete JSON value. ' +
-                'Assistant text arrives as `text.delta` whose `text` is the CUMULATIVE answer so far, ' +
-                'not a delta — take the last one, or `run.result` at the end. Each `text.delta` also ' +
-                'carries `delta`, the characters it adds, when it only appends to the one before; ' +
-                'with --incremental it carries nothing else of the text (see that flag). The same text is ' +
+                'Assistant text arrives as `text.delta`, a real delta: `delta` is the characters it ' +
+                'adds, and a rewrite that is not an append arrives as `replace`, the new full text. ' +
+                'Append the `delta`s, or take `run.result` at the end, which always holds the whole ' +
+                'answer. (--cumulative restores the older form, where `text` is the whole answer so ' +
+                'far; it grows with the square of the answer.) The same text is ' +
                 'mirrored inside `session.output` envelopes for consumers that want the raw stream, ' +
                 'so folding both doubles the answer: pick ONE lane. A widget the agent wrote ' +
                 '(a block of CSS, HTML and JavaScript the apps draw) is its text description in ' +
@@ -813,7 +847,7 @@ class AgentsChat extends base_command_1.BaseCommand {
             sessionId: started.sessionId,
             conversationId,
             jsonl: flags.jsonl,
-            incrementalText: flags.incremental,
+            ...jsonlTextForm(flags),
             quiet,
             approveTools: flags['approve-tools'],
             reconcileTerminal,
@@ -1005,6 +1039,10 @@ class AgentsChat extends base_command_1.BaseCommand {
                     this.error(noOutput, { exit: 1 });
                 this.log(result.text);
             }
+            else if (result.status === 'aborted') {
+                // Streaming human mode: say the cancel took, rather than leave the keypress warning last.
+                this.log(`\n${cancelledRunMessage({ sessionId: started.sessionId, conversationId: started.conversationId })}`);
+            }
         }
         finally {
             if (graceTimer)

package/dist/commands/agents/delete.d.ts

@@ -8,6 +8,14 @@ import { BaseCommand } from '../../base-command';
 export declare function agentRemovalQuestion(agentId: string, kind: AgentRemovalKind | null): string;
 /** What happened, read from the server's response rather than predicted. */
 export declare function agentRemovalReport(agentId: string, response: DeleteAgentResponse | undefined): string;
+/**
+ * What became of the agent's Personal Context data, read from the same response
+ * (OSK-20112). The agent row is gone as soon as the delete returns, but data
+ * derived from its connected sources is erased separately: `Deleted agent` must
+ * never stand in for "erased". Nothing is printed when the server reported
+ * nothing (an older server, or an uninstall, which erases nothing).
+ */
+export declare function agentErasureReport(response: DeleteAgentResponse | undefined): string[];
 export default class AgentsDelete extends BaseCommand {
     static description: string;
     static examples: string[];

package/dist/commands/agents/delete.js

@@ -2,6 +2,7 @@
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.agentRemovalQuestion = agentRemovalQuestion;
 exports.agentRemovalReport = agentRemovalReport;
+exports.agentErasureReport = agentErasureReport;
 const core_1 = require("@oclif/core");
 const data_provider_1 = require("@skrr-ai/data-provider");
 const base_command_1 = require("../../base-command");
@@ -38,6 +39,19 @@ function agentRemovalReport(agentId, response) {
             return `Deleted agent ${agentId}`;
     }
 }
+/**
+ * What became of the agent's Personal Context data, read from the same response
+ * (OSK-20112). The agent row is gone as soon as the delete returns, but data
+ * derived from its connected sources is erased separately: `Deleted agent` must
+ * never stand in for "erased". Nothing is printed when the server reported
+ * nothing (an older server, or an uninstall, which erases nothing).
+ */
+function agentErasureReport(response) {
+    if ((0, data_provider_1.agentRemovalKind)(response) !== 'deleted')
+        return [];
+    const erasure = response && 'erasure' in response ? response.erasure : undefined;
+    return (0, data_provider_1.describePersonalContextErasure)(erasure)?.lines ?? [];
+}
 class AgentsDelete extends base_command_1.BaseCommand {
     static description = 'Delete an agent you created (irreversible), or uninstall one installed from the store (reinstalling restores it)';
     static examples = [
@@ -89,6 +103,8 @@ class AgentsDelete extends base_command_1.BaseCommand {
             this.handleApiError(err);
         }
         this.log(agentRemovalReport(args.id, response));
+        for (const line of agentErasureReport(response))
+            this.log(line);
     }
 }
 exports.default = AgentsDelete;

package/dist/commands/context.js

@@ -64,6 +64,13 @@ class Context extends base_command_1.BaseCommand {
                 path: (0, config_1.getConfigPath)(),
                 cliId: (0, cli_id_1.resolveCliId)(this.cliConfig) ?? null,
             },
+            // Silent about the DAEMON's device key on purpose (OSK-20507). This is the CLI's
+            // own sign-in, and the CLI never requires a device key (OSK-12063), so an
+            // unreadable one changes nothing an agent reading this can do. The daemon's
+            // account of its key is `skrr daemon status` (`problems`, from `/health`
+            // `deviceIdentity`), and the one line a `skrr` process prints about it is the
+            // notice in `lib/auth-core-init.ts`. Adding it here would put a machine fact
+            // beside a per-process one and read as this credential's state.
             auth: {
                 signedIn: Boolean(this.resolvedCredential?.token),
                 tokenSource: this.credentialSourceLabel(),

package/dist/commands/search/workspace.js

@@ -104,7 +104,7 @@ class SearchWorkspace extends base_command_1.BaseCommand {
             url: `${(0, web_url_1.webOrigin)(this.cliConfig.baseURL)}${item.href}`,
         }));
         if (flags.json) {
-            this.log(JSON.stringify({ ...response, results }, null, 2));
+            this.printJsonResult({ ...response, results });
             return;
         }
         for (const diagnostic of new Set(response.diagnostics || []))

package/dist/commands/store/gallery-admissions/approve.js

@@ -24,7 +24,7 @@ class StoreGalleryAdmissionsApprove extends base_command_1.BaseCommand {
                 revision: flags.revision, digest: flags.digest, imagesReviewed: true, ...(flags.note ? { note: flags.note } : {}),
             });
             if (flags.json)
-                this.log(JSON.stringify(result, null, 2));
+                this.printJsonResult(result);
             else
                 this.log(`Approved gallery revision ${flags.revision}.`);
         }

package/dist/commands/store/gallery-admissions/preview.js

@@ -36,7 +36,7 @@ class StoreGalleryAdmissionsPreview extends base_command_1.BaseCommand {
             await (0, promises_1.writeFile)(flags.output, bytes, { flag: 'wx', mode: 0o600 });
             const receipt = { requestId: args.id, kind, revision: review.revision, digest: review.digest, imageId: args.imageId, sha256: digest, path: flags.output, bytes: bytes.length };
             if (flags.json)
-                this.log(JSON.stringify(receipt));
+                this.printJsonResult(receipt);
             else
                 this.log(`Wrote ${bytes.length} bytes to ${flags.output} (sha256:${digest}). Review revision ${review.revision}, digest ${review.digest}.`);
         }

package/dist/commands/store/gallery-admissions/refuse.js

@@ -23,7 +23,7 @@ class StoreGalleryAdmissionsRefuse extends base_command_1.BaseCommand {
                 revision: flags.revision, digest: flags.digest, note: flags.note.trim(),
             });
             if (flags.json)
-                this.log(JSON.stringify(result, null, 2));
+                this.printJsonResult(result);
             else
                 this.log(`Refused gallery revision ${flags.revision}.`);
         }

package/dist/commands/store/gallery-admissions/show.js

@@ -16,7 +16,7 @@ class StoreGalleryAdmissionsShow extends base_command_1.BaseCommand {
         try {
             const result = await data_provider_1.dataService.getStoreGalleryAdmission(flags.kind, args.id);
             if (flags.json) {
-                this.log(JSON.stringify(result, null, 2));
+                this.printJsonResult(result);
                 return;
             }
             const r = result.review;

package/dist/generated/agent-guides.json

@@ -350,7 +350,7 @@
                         "id": "memory",
                         "title": "Where an Agent's knowledge lives",
                         "readWhen": "you need to read or change what an Agent knows, or tell its Memory from its configuration",
-                        "tokens": 858,
+                        "tokens": 891,
                         "aliases": [],
                         "explains": [
                             "MEMORY_NOT_MOUNTED",
@@ -489,7 +489,7 @@
                 "version": 4,
                 "routed": true,
                 "aliases": [],
-                "tokens": 861,
+                "tokens": 865,
                 "sections": [
                     {
                         "id": "model",
@@ -709,7 +709,7 @@
                 ]
             }
         ],
-        "hash": "da48eab97c0c8b0102894a1256266cd67df3611313caec27ffff1ef2c2ec87ae",
+        "hash": "3581ad4744d3aae5df82a9358ddb6f87e823b4928104006581e16b3a4d821b2e",
         "tokens": 544
     },
     "routedIndex": {
@@ -1063,7 +1063,7 @@
                         "id": "memory",
                         "title": "Where an Agent's knowledge lives",
                         "readWhen": "you need to read or change what an Agent knows, or tell its Memory from its configuration",
-                        "tokens": 858,
+                        "tokens": 891,
                         "aliases": [],
                         "explains": [
                             "MEMORY_NOT_MOUNTED",
@@ -1202,7 +1202,7 @@
                 "version": 4,
                 "routed": true,
                 "aliases": [],
-                "tokens": 861,
+                "tokens": 865,
                 "sections": [
                     {
                         "id": "model",
@@ -1353,7 +1353,7 @@
                 ]
             }
         ],
-        "hash": "ac18c43c11f5a755bd8f80f49323edc91d9ee75d3448a18e5ffc7ba30a484bbc",
+        "hash": "2f65b076744f03768c49bce61d58f4ee26354c007316777602a3567f3d71f35d",
         "tokens": 493
     },
     "cards": {
@@ -1676,7 +1676,7 @@
             "routed": true,
             "aliases": [],
             "body": "## Concept model\n\n| Noun | Question it answers |\n| --- | --- |\n| **Agent** | Who acts, and with which identity, instructions, model, tools and tone? |\n| **Harness** | Which provider runs its turns, on which machine? One machine × one provider: Claude Code and Codex on one laptop are two Harnesses. |\n| **Machine** | Which computer: a personal machine running the daemon, a Dedicated Runtime, or a Hosted Machine? |\n| **Release** | Which exact, installable snapshot of the Agent's portable specification? |\n| **Role** | Which portable responsibility (purpose, scope, parameters) can be installed on an Agent? |\n| **Memory Store** | What does the Agent know, kept for the Agent or for a Space? |\n| **Notepad** | What does one person privately want this Agent to keep in mind? |\n\n## Decide\n\n- **Who am I?** The managed identity block in your instruction file names the Agent this machine\n  speaks as. `--agent <agent-id>` chooses which Agent a message speaks as. Neither sets authorship:\n  the server records the author of every write from the authenticated runtime, and `skrr context`\n  reports only whether this runtime carries an Agent binding.\n- How it writes (shorter, plainer, warmer) is **tone**. What it does or must never do is an\n  **instruction block**. Neither belongs in a Memory Store or the Notepad.\n- A preference the person tells you to remember is a Memory proposal they review, not an edit to\n  your own instructions. Work to do later, or to keep checking, belongs to a commitment.\n- Where it runs is its execution targets. A Machine is not a Harness: pin the Harness.\n\n## Workflow\n\n### Change an Agent's configuration\n\n1. Read the current value of exactly what you will change, on the Agent the owner named.\n2. Make the narrowest change asked for: add or edit one instruction block rather than replacing\n   all of them.\n3. Read the resolved state back and report that. A workspace policy can override a tone you set.\n\nThe commands for each step are in the `configure` section; `--help` gives their flags.\n\n## Authority\n\n| Actor | May do | Only a person may do |\n| --- | --- | --- |\n| Agent | Read any Agent it can view; when the owner asks, change an Agent's instructions, tone, model or tools, create an Agent, or delete one the owner's own message names; propose a Memory change | Widen an Agent's permissions: permission mode, network egress, tool sign-in; publish, list, price or share an Agent; connect a channel; choose paid compute; approve a Memory promotion; set Memory governance |\n| Person | Everything in both columns | — |\n\nAn Agent never widens its own permissions or membership, even where a command would accept it.\n\n## Live state\n\n- `skrr agents show <agent-id> --expanded` — the full configuration, execution targets included.\n- `skrr agents instructions show <agent-id>` — the instruction blocks in order, with instance ids.\n- `skrr agents tone show <agent-id>` — the tone it actually writes in, and where that came from.\n- `skrr harnesses list` and `skrr machines list` — Harness ids and the Machines they run on.\n- `skrr memory mounts resolve --agent <agent-id>` — the Memory Stores it can read or write.\n\n## Related guides\n\n- `commitments` — what an Agent is responsible for over time, and making something happen later.\n- `learning` — teaching an Agent a preference or procedure that lasts.\n- `spaces` — admitting an Agent to a Space.\n- `store` — publishing an Agent release.",
-            "hash": "f5c941dd33a0972a57433e00234c9d6a86e5897c32e950e91b0d40d26142119f",
+            "hash": "accb2eed6a5f6f0fe16c9bec8bd2233ecda3111976e36215e81ea61491ebe93b",
             "tokens": 944,
             "sections": [
                 {
@@ -1716,7 +1716,7 @@
                     "id": "memory",
                     "title": "Where an Agent's knowledge lives",
                     "readWhen": "you need to read or change what an Agent knows, or tell its Memory from its configuration",
-                    "tokens": 858,
+                    "tokens": 891,
                     "aliases": [],
                     "explains": [
                         "MEMORY_NOT_MOUNTED",
@@ -1861,9 +1861,9 @@
             "version": 4,
             "routed": true,
             "aliases": [],
-            "body": "## Concept model\n\n| Noun | Question it answers |\n| --- | --- |\n| Memory | What does the agent durably know — a fact in a versioned Agent or Space Store? |\n| Lesson | What reviewed instruction applies — a Memory node typed `knowledge`, `preference`, `procedure`, `exemplar`, `rubric` or `capability`? |\n| Lesson state | May it reach runtime context — `candidate` (proposed), `active`, `needs_attention` (stopped because its evidence changed) or `archived` (history only)? |\n| Use receipt | What happened when one exact lesson version was used — `presented`, `applied`, `verified` or `failed`, at the strength the server assigned? |\n| Notepad | What did the agent note for itself — private scratch, never reviewed knowledge? |\n| Skill | What is installed and invoked — the executable artifact a reviewed lesson can compile into? |\n\n## Decide\n\n- A durable **fact** belongs in Memory. A **rule, preference or procedure** that should govern future work belongs in a lesson, and every lesson enters as a `candidate` a person must review.\n- The agent's own working notes belong in its **Notepad** — never something the person asked to stick.\n- A reviewed procedure that should become invocable or publishable becomes a **Skill**.\n- Never use a lesson to grant access: it cannot open a file, install a credential, widen a membership or authorize a tool action.\n\n## Workflow\n\n### Make a rule stick\n\n1. Restate it exactly — the trigger, the action and the exception — and choose its kind.\n2. File it for review. Never write it straight into canonical Memory or your own instructions.\n\nWhere the current Task is filed does not choose a Memory Store. The default below is deliberately\nAgent-owned; use a Space scope only after `skrr memory mounts resolve` confirms that Space Store is\nmounted for this session.\n\n```bash\nskrr memory proposals create --agent <agent-id> --scope agent:<agent-id> \\\n  --kind <kind> --path <path> --content \"<the rule as stated>\"\n```\n\n3. Report it as awaiting the person's review — a candidate, not something learned.\n\n### Act on a lesson\n\n1. Only `active` lessons reach runtime context; check `applicability` and `exclusions` before relying on one.\n2. Act under ordinary tool and permission authority — the lesson itself grants nothing.\n3. The runtime records a use receipt against the exact version; a self-report counts as a claim, not an observation.\n\n## Authority\n\n| Actor | May do | Only a person may do |\n| --- | --- | --- |\n| Agent | Propose candidates; reinforce an active lesson whose content did not change; stop using one | Activate, change or restore active instructions |\n| Person | Review, activate and change instructions; dismiss candidates; grant evidence use; install and publish a Skill; own adaptive-learning consent | — |\n\n## Live state\n\n- `skrr memory proposals list --agent <agent-id> --scope <scope>` — proposals awaiting review (`proposed` is the default status).\n- `skrr learning status` — the person's adaptive-learning consent, learned state and serving fallback.\n- `skrr agents notepad show <agent-id>` — the agent's private notes.\n\n## Related guides\n\n- `store` — publishing a lesson as a Skill release, and installing Skills.\n- `agents` — the agent's Memory, Notepad and instructions.",
-            "hash": "b228b2fa45eec60cfbf3fb451bcc68061931197d947ed2d7da0cf97251ad6533",
-            "tokens": 861,
+            "body": "## Concept model\n\n| Noun | Question it answers |\n| --- | --- |\n| Memory | What does the agent durably know — a fact in a versioned Agent or Space Store? |\n| Lesson | What reviewed instruction applies — a Memory node typed `knowledge`, `preference`, `procedure`, `exemplar`, `rubric` or `capability`? |\n| Lesson state | May it reach runtime context — `candidate` (proposed), `active`, `needs_attention` (stopped because its evidence changed) or `archived` (history only)? |\n| Use receipt | What happened when one exact lesson version was used — `presented`, `applied`, `verified` or `failed`, at the strength the server assigned? |\n| Notepad | What did the agent note for itself — private scratch, never reviewed knowledge? |\n| Skill | What is installed and invoked — the executable artifact a reviewed lesson can compile into? |\n\n## Decide\n\n- A durable **fact** belongs in Memory. A **rule, preference or procedure** that should govern future work belongs in a lesson, and every lesson enters as a `candidate` a person must review.\n- The agent's own working notes belong in its **Notepad** — never something the person asked to stick.\n- A reviewed procedure that should become invocable or publishable becomes a **Skill**.\n- Never use a lesson to grant access: it cannot open a file, install a credential, widen a membership or authorize a tool action.\n\n## Workflow\n\n### Make a rule stick\n\n1. Restate it exactly — the trigger, the action and the exception — and choose its kind.\n2. File it for review. Never write it straight into canonical Memory or your own instructions.\n\nWhere the current Task is filed does not choose a Memory Store. The default below is deliberately\nAgent-owned; use a Space scope only after this session's mounts confirm that Space Store is mounted.\n\n`skrr memory mounts resolve` shows the mounts.\n\n```bash\nskrr memory proposals create --agent <agent-id> --scope agent:<agent-id> \\\n  --kind <kind> --path <path> --content \"<the rule as stated>\"\n```\n\n3. Report it as awaiting the person's review — a candidate, not something learned.\n\n### Act on a lesson\n\n1. Only `active` lessons reach runtime context; check `applicability` and `exclusions` before relying on one.\n2. Act under ordinary tool and permission authority — the lesson itself grants nothing.\n3. The runtime records a use receipt against the exact version; a self-report counts as a claim, not an observation.\n\n## Authority\n\n| Actor | May do | Only a person may do |\n| --- | --- | --- |\n| Agent | Propose candidates; reinforce an active lesson whose content did not change; stop using one | Activate, change or restore active instructions |\n| Person | Review, activate and change instructions; dismiss candidates; grant evidence use; install and publish a Skill; own adaptive-learning consent | — |\n\n## Live state\n\n- `skrr memory proposals list --agent <agent-id> --scope <scope>` — proposals awaiting review (`proposed` is the default status).\n- `skrr learning status` — the person's adaptive-learning consent, learned state and serving fallback.\n- `skrr agents notepad show <agent-id>` — the agent's private notes.\n\n## Related guides\n\n- `store` — publishing a lesson as a Skill release, and installing Skills.\n- `agents` — the agent's Memory, Notepad and instructions.",
+            "hash": "6c69c94f8070907742b4513feea16b30aa0f99cf632eb7ef74b85ea8991ed305",
+            "tokens": 865,
             "sections": [
                 {
                     "id": "model",
@@ -5437,7 +5437,7 @@
                     "id": "memory",
                     "title": "Where an Agent's knowledge lives",
                     "readWhen": "you need to read or change what an Agent knows, or tell its Memory from its configuration",
-                    "tokens": 858,
+                    "tokens": 891,
                     "aliases": [],
                     "explains": [
                         "MEMORY_NOT_MOUNTED",
@@ -5513,7 +5513,7 @@
                     "id": "memory",
                     "title": "Where an Agent's knowledge lives",
                     "readWhen": "you need to read or change what an Agent knows, or tell its Memory from its configuration",
-                    "tokens": 858,
+                    "tokens": 891,
                     "aliases": [],
                     "explains": [
                         "MEMORY_NOT_MOUNTED",
@@ -5590,7 +5590,7 @@
                     "id": "memory",
                     "title": "Where an Agent's knowledge lives",
                     "readWhen": "you need to read or change what an Agent knows, or tell its Memory from its configuration",
-                    "tokens": 858,
+                    "tokens": 891,
                     "aliases": [],
                     "explains": [
                         "MEMORY_NOT_MOUNTED",
@@ -5625,9 +5625,9 @@
                 "MEMORY_VERSION_CONFLICT",
                 "NODE_REFERENCE_REQUIRED"
             ],
-            "body": "Read this when you need to read or change what an Agent knows, or tell its Memory from its configuration.\n\n| Where              | What it holds                                                              | Who changes it                           |\n| ------------------ | -------------------------------------------------------------------------- | ---------------------------------------- |\n| Agent Memory Store | What this Agent knows, as versioned topics                                 | The Agent, through its own mounted store |\n| Space Memory Store | What a Space knows; mounted only for a member of that Space                | An Agent proposes; a person approves     |\n| Notepad            | One person's private notes to this Agent, read on that person's chat turns | That person                              |\n| Persona files      | Who the Agent is and who it works for (SOUL, IDENTITY, USER and others)    | The owner, or the Agent about itself     |\n\nInstructions and tone are configuration, not Memory: what the Agent must always do goes in an\ninstruction block, and how it writes goes in its tone.\n\nRules:\n\n- Resolve the mounts before you read or write. A store mounted read-only takes neither writes nor\n  proposals from you: keep the topic in the Agent's own store, where a person can promote it.\n- A Task or command's `--space` chooses where that work is filed and supplies request context; it\n  does **not** select or mount a Space Memory Store. Run `skrr memory mounts resolve` first, then\n  name one of the mounted scopes. When the requested Space Store is absent, use the Agent Store\n  only for Agent-owned knowledge; never treat that fallback as shared Space Memory.\n- An Agent's change to a Space Memory Store is always a proposal. It changes nothing until a\n  person approves it, and only a person may approve promoting an Agent topic into a Space or\n  admitting personal data to one.\n- A change to an existing topic names the version it read. When the topic has moved on, read the\n  latest version and retry against it; never overwrite it.\n- Everyone with edit access to the Agent can read its Agent Memory Store.\n- What the Agent may remember (read and write scopes, retention, evidence) is governance, and\n  governance is the owner's.\n\nUse the canonical commands: `skrr memory mounts`, `skrr memory topics`, `skrr memory proposals`,\n`skrr memory versions`. The ungrouped commands such as `skrr memory list` and `skrr memory tree`\naddress older pools: what one surface holds does not exist in the other. `--agent` selects whose\nMemory you act on; it does not change who is signed in.\n\n## Example\n\nFind what the Agent already knows before adding to it, then propose the addition.\n\n```bash\nskrr memory mounts resolve --agent <agent-id> --space <space-id> --json\nskrr memory topics list --agent <agent-id> --space <space-id> --scope \"space:<space-id>\"\nskrr memory proposals create --agent <agent-id> --space <space-id> --scope \"space:<space-id>\" \\\n  --path /team/release-process --content \"Releases need a green smoke test.\" --evidence task:<task-id>\n```\n\n## Refusals\n\n| Code                             | Cause                                            | Fix                                                     |\n| -------------------------------- | ------------------------------------------------ | ------------------------------------------------------- |\n| `MEMORY_NOT_MOUNTED`             | The target store is not mounted for this session; `--space` alone does not mount it | Run `memory mounts resolve`; choose a writable mounted scope, or use Agent-owned Memory without claiming it is shared |\n| `MEMORY_STORE_READ_ONLY`         | The target store is mounted read-only            | Write to the Agent's own store; a person can promote it |\n| `MEMORY_SPACE_PROPOSAL_REQUIRED` | An Agent wrote straight to a Space Memory Store  | Submit it as a proposal                                 |\n| `MEMORY_VERSION_CONFLICT`        | The topic changed since you read it              | Read the latest version and retry against it            |\n| `NODE_REFERENCE_REQUIRED`        | The request named no topic                       | Pass one of `memoryId`, `nodeId` or `path`              |",
-            "hash": "4ff05f37d8557901fb27c3cdfc3251c006554f7c74476952dac37cbea5a5610b",
-            "tokens": 858,
+            "body": "Read this when you need to read or change what an Agent knows, or tell its Memory from its configuration.\n\n| Where              | What it holds                                                              | Who changes it                           |\n| ------------------ | -------------------------------------------------------------------------- | ---------------------------------------- |\n| Agent Memory Store | What this Agent knows, as versioned topics                                 | The Agent, through its own mounted store |\n| Space Memory Store | What a Space knows; mounted only for a member of that Space                | An Agent proposes; a person approves     |\n| Notepad            | One person's private notes to this Agent, read on that person's chat turns | That person                              |\n| Persona files      | Who the Agent is and who it works for (SOUL, IDENTITY, USER and others)    | The owner, or the Agent about itself     |\n\nInstructions and tone are configuration, not Memory: what the Agent must always do goes in an\ninstruction block, and how it writes goes in its tone.\n\nRules:\n\n- Resolve the mounts before you read or write. A store mounted read-only takes neither writes nor\n  proposals from you: keep the topic in the Agent's own store, where a person can promote it.\n- The Space a Task or call names chooses where that work is filed and supplies request context; it\n  does **not** select or mount a Space Memory Store. Resolve the mounts first, then name one of the\n  mounted scopes. When the requested Space Store is absent, use the Agent Store only for\n  Agent-owned knowledge; never treat that fallback as shared Space Memory.\n- An Agent's change to a Space Memory Store is always a proposal. It changes nothing until a\n  person approves it, and only a person may approve promoting an Agent topic into a Space or\n  admitting personal data to one.\n- A change to an existing topic names the version it read. When the topic has moved on, read the\n  latest version and retry against it; never overwrite it.\n- Everyone with edit access to the Agent can read its Agent Memory Store.\n- What the Agent may remember (read and write scopes, retention, evidence) is governance, and\n  governance is the owner's.\n\nUse the canonical commands: `skrr memory mounts`, `skrr memory topics`, `skrr memory proposals`,\n`skrr memory versions`. The ungrouped commands such as `skrr memory list` and `skrr memory tree`\naddress older pools: what one surface holds does not exist in the other. `--agent` selects whose\nMemory you act on; it does not change who is signed in. `--space` chooses where a command's work is\nfiled and never mounts a store: run `skrr memory mounts resolve` first, then pass one of the\nmounted scopes with `--scope`.\n\n## Example\n\nFind what the Agent already knows before adding to it, then propose the addition.\n\n```bash\nskrr memory mounts resolve --agent <agent-id> --space <space-id> --json\nskrr memory topics list --agent <agent-id> --space <space-id> --scope \"space:<space-id>\"\nskrr memory proposals create --agent <agent-id> --space <space-id> --scope \"space:<space-id>\" \\\n  --path /team/release-process --content \"Releases need a green smoke test.\" --evidence task:<task-id>\n```\n\n## Refusals\n\n| Code                             | Cause                                            | Fix                                                     |\n| -------------------------------- | ------------------------------------------------ | ------------------------------------------------------- |\n| `MEMORY_NOT_MOUNTED`             | The target store is not mounted for this session; naming a Space alone does not mount it | Resolve the mounts; choose a writable mounted scope, or use Agent-owned Memory without claiming it is shared |\n| `MEMORY_STORE_READ_ONLY`         | The target store is mounted read-only            | Write to the Agent's own store; a person can promote it |\n| `MEMORY_SPACE_PROPOSAL_REQUIRED` | An Agent wrote straight to a Space Memory Store  | Submit it as a proposal                                 |\n| `MEMORY_VERSION_CONFLICT`        | The topic changed since you read it              | Read the latest version and retry against it            |\n| `NODE_REFERENCE_REQUIRED`        | The request named no topic                       | Pass one of `memoryId`, `nodeId` or `path`              |",
+            "hash": "8a5bafc440947aa93782c6d0b196c08f83a0656c4eafd1439990ba99f35c30ce",
+            "tokens": 891,
             "sections": [
                 {
                     "id": "model",
@@ -5666,7 +5666,7 @@
                     "id": "memory",
                     "title": "Where an Agent's knowledge lives",
                     "readWhen": "you need to read or change what an Agent knows, or tell its Memory from its configuration",
-                    "tokens": 858,
+                    "tokens": 891,
                     "aliases": [],
                     "explains": [
                         "MEMORY_NOT_MOUNTED",
@@ -5741,7 +5741,7 @@
                     "id": "memory",
                     "title": "Where an Agent's knowledge lives",
                     "readWhen": "you need to read or change what an Agent knows, or tell its Memory from its configuration",
-                    "tokens": 858,
+                    "tokens": 891,
                     "aliases": [],
                     "explains": [
                         "MEMORY_NOT_MOUNTED",

package/dist/lib/agentic-stream.js

@@ -775,6 +775,12 @@ function endsWithIgnoringWhitespace(whole, tail) {
     const wanted = solid(tail);
     return wanted.length > 0 && solid(whole).endsWith(wanted);
 }
+/** `head` is the start of `whole`, whitespace aside. */
+function startsWithIgnoringWhitespace(whole, head) {
+    const solid = (value) => value.replace(/\s+/g, '');
+    const wanted = solid(head);
+    return wanted.length > 0 && solid(whole).startsWith(wanted);
+}
 class AgenticStreamClient {
     options;
     socket = null;
@@ -2456,10 +2462,18 @@ class AgenticStreamClient {
         // `' \n\n::::skrr-ui{'`), so the harness's last block is not a byte-for-byte suffix of the
         // accumulation even though it is its tail, and taking it as the answer would drop
         // everything the agent said before the tool call (OSK-16934).
+        //
+        // The other way round is the same defect from the other end: a result that is a strict
+        // PREFIX of the accumulation was cut to a length cap, not written as the answer. The daemon
+        // keeps the first 4000 characters of a turn's text for the result it reports, so every local
+        // answer longer than that came back as its first 4000 characters, cut mid-word, with
+        // `status: completed` (OSK-20616). What streamed is the longer record of the same words.
         const accumulationIsSuperset = finalText.length > 0 &&
             this.accumulated.length > finalText.length &&
             (this.accumulated.endsWith(finalText) ||
-                endsWithIgnoringWhitespace(this.accumulated, finalText));
+                endsWithIgnoringWhitespace(this.accumulated, finalText) ||
+                this.accumulated.startsWith(finalText) ||
+                startsWithIgnoringWhitespace(this.accumulated, finalText));
         if (event.publicProjection === 'lookback_answer_v1' && typeof event.result === 'string') {
             this.accumulated = event.result;
         }

package/dist/lib/auth-core-init.d.ts

@@ -38,9 +38,22 @@ export declare function plainCredentialEnvelopeWarning(args: readonly unknown[])
 export declare const CREDENTIAL_KEY_CHANGED_NOTICE: string;
 /**
  * The one line an unreadable device key prints when no credential-key change
- * explains it. The CLI never enrolls or requires a device key (OSK-12063), so
- * this degrades a proof, not access — say exactly that.
+ * explains it (OSK-20506).
+ *
+ * The CLI never enrolls or requires a device key (OSK-12063), so this degrades a
+ * proof, not a sign-in: say exactly that. What it must not do is point at
+ * `skrr login`. That signs this CLI in on its own and never creates or replaces a
+ * device key, so a person who followed it would be told the same thing on the next
+ * command. Only an interactive daemon sign-in mints a key and re-pins it, and which
+ * one depends on who runs the daemon, so this uses the sentence the hand-off
+ * refusals use for the same repair (`daemonSignInRemedy`) rather than a second
+ * spelling.
+ *
+ * `profile` names the command for a non-default profile: a bare `skrr daemon login`
+ * signs the default daemon in and leaves this one as it was (OSK-16435).
  */
+export declare function deviceKeyRecoveryRequiredNotice(profile?: string): string;
+/** The notice for the default profile. */
 export declare const DEVICE_KEY_RECOVERY_REQUIRED_NOTICE: string;
 export declare function createCredentialEnvelopeWarningPresenter(): (args: readonly unknown[]) => string | null;
 type DedicatedGenerationPreparationOptions = {

package/dist/lib/auth-core-init.js

@@ -5,6 +5,7 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
 Object.defineProperty(exports, "__esModule", { value: true });
 exports.CliCredentialInitializationError = exports.DEVICE_KEY_RECOVERY_REQUIRED_NOTICE = exports.CREDENTIAL_KEY_CHANGED_NOTICE = void 0;
 exports.plainCredentialEnvelopeWarning = plainCredentialEnvelopeWarning;
+exports.deviceKeyRecoveryRequiredNotice = deviceKeyRecoveryRequiredNotice;
 exports.createCredentialEnvelopeWarningPresenter = createCredentialEnvelopeWarningPresenter;
 exports.prepareDedicatedRuntimeAuthGeneration = prepareDedicatedRuntimeAuthGeneration;
 exports.ensureAuthCoreConfigured = ensureAuthCoreConfigured;
@@ -38,10 +39,12 @@ const node_fs_1 = __importDefault(require("node:fs"));
 const node_path_1 = __importDefault(require("node:path"));
 const proper_lockfile_1 = __importDefault(require("proper-lockfile"));
 const auth_core_1 = require("@skrr-ai/auth-core");
+const cli_handoff_wire_1 = require("@skrr-ai/auth-core/cli-handoff-wire");
 const cred_envelope_1 = require("./cred-envelope");
 const device_identity_1 = require("./device-identity");
 const auth_storage_1 = require("./auth-storage");
 const keychain_1 = require("./keychain");
+const daemon_command_hint_1 = require("./daemon-command-hint");
 function envFlag(name) {
     const v = process.env[name];
     return v === '1' || v === 'true' || v === 'TRUE';
@@ -117,13 +120,33 @@ const DEVICE_KEY_DECRYPT_FAILED = '[deviceIdentity] private_key_decrypt_failed';
 const DEVICE_KEY_RECOVERY_REQUIRED = '[deviceIdentity] recovery_required';
 /**
  * The one line an unreadable device key prints when no credential-key change
- * explains it. The CLI never enrolls or requires a device key (OSK-12063), so
- * this degrades a proof, not access — say exactly that.
+ * explains it (OSK-20506).
+ *
+ * The CLI never enrolls or requires a device key (OSK-12063), so this degrades a
+ * proof, not a sign-in: say exactly that. What it must not do is point at
+ * `skrr login`. That signs this CLI in on its own and never creates or replaces a
+ * device key, so a person who followed it would be told the same thing on the next
+ * command. Only an interactive daemon sign-in mints a key and re-pins it, and which
+ * one depends on who runs the daemon, so this uses the sentence the hand-off
+ * refusals use for the same repair (`daemonSignInRemedy`) rather than a second
+ * spelling.
+ *
+ * `profile` names the command for a non-default profile: a bare `skrr daemon login`
+ * signs the default daemon in and leaves this one as it was (OSK-16435).
  */
-exports.DEVICE_KEY_RECOVERY_REQUIRED_NOTICE = "warning: this machine's stored device key could not be read, so skrr sends requests " +
-    'without a device proof until the local daemon signs in again. (DEBUG=1 shows the underlying error.)';
+function deviceKeyRecoveryRequiredNotice(profile = keychain_1.DEFAULT_PROFILE) {
+    const loginCommand = (0, daemon_command_hint_1.daemonCommandHint)('login', { profile });
+    return ("warning: this machine's stored device key could not be read, so skrr sends requests " +
+        `without a device proof. To replace it, ${(0, cli_handoff_wire_1.daemonSignInRemedy)({ repinsDeviceKey: true, loginCommand })}. ` +
+        '(DEBUG=1 shows the underlying error.)');
+}
+/** The notice for the default profile. */
+exports.DEVICE_KEY_RECOVERY_REQUIRED_NOTICE = deviceKeyRecoveryRequiredNotice(keychain_1.DEFAULT_PROFILE);
 function createCredentialEnvelopeWarningPresenter() {
     let keyChanged = false;
+    // auth-core named a failure as the DEVICE key's (see below): the person has one
+    // line to read for it, and it is not the credential line.
+    let deviceKeyUnreadable = false;
     return (args) => {
         const [message, metadata] = args;
         const event = typeof message === 'string' && message.startsWith('[credEnvelope] ')
@@ -157,10 +180,28 @@ function createCredentialEnvelopeWarningPresenter() {
             (message === DEVICE_KEY_DECRYPT_FAILED || message === DEVICE_KEY_RECOVERY_REQUIRED)) {
             return '';
         }
+        // No key change in THIS process, yet the device key will not open (the
+        // credential key changed in an earlier one, or the file is damaged).
+        // auth-core's device identity labels that read with its own hint, so the
+        // producer says WHAT failed and this decides what a person reads. The
+        // generic line would say "signing in again rebuilds it", and `skrr login`
+        // does not rebuild a device key. Print nothing for it, and nothing for the
+        // device identity's own echo of the same failure: `recovery_required`
+        // follows and carries the one line (OSK-20506). The flag is set by that
+        // hint alone, so another credential that will not open still gets its own
+        // line below.
+        if (event === 'cred_envelope.read.decrypt_failed' &&
+            meta.hint === auth_core_1.DEVICE_KEY_UNREADABLE_CREDENTIAL_HINT) {
+            deviceKeyUnreadable = true;
+            return '';
+        }
+        if (deviceKeyUnreadable && message === DEVICE_KEY_DECRYPT_FAILED)
+            return '';
         // Without a key change an unreadable device key is a real fault: one
         // plain line instead of an object dump.
-        if (message === DEVICE_KEY_RECOVERY_REQUIRED)
-            return exports.DEVICE_KEY_RECOVERY_REQUIRED_NOTICE;
+        if (message === DEVICE_KEY_RECOVERY_REQUIRED) {
+            return deviceKeyRecoveryRequiredNotice((0, keychain_1.getActiveProfile)());
+        }
         return plainCredentialEnvelopeWarning(args);
     };
 }

package/dist/lib/command-hygiene.js

@@ -453,6 +453,35 @@ const AGENT_CRITICAL_COMMANDS = [
     'agent:message:send',
     'tasks:complete',
 ];
+/**
+ * The text of a command file, with a pure re-export alias read as its target.
+ *
+ * `export { default } from '../search/tasks';` is a second spelling of another
+ * command: oclif loads the same class, so the alias has the target's flags,
+ * description and args. Reading the alias's own few lines reports a missing
+ * `--json` and a missing description that the command in fact has, and the only
+ * way to silence that would be to copy the description into the alias, where
+ * the two spellings could drift apart.
+ *
+ * One hop, and only when the re-export is the whole module (comments aside), so
+ * a file that adds its own code is still audited as itself.
+ */
+function readCommandSource(file) {
+    const source = fs.readFileSync(file, 'utf8');
+    const code = source
+        .replace(/\/\*[\s\S]*?\*\//g, '')
+        .replace(/\/\/.*$/gm, '')
+        .trim();
+    const alias = code.match(/^export\s*\{\s*default\s*\}\s*from\s*['"](\.{1,2}\/[^'"]+)['"]\s*;?$/);
+    if (!alias)
+        return source;
+    const target = path.resolve(path.dirname(file), alias[1]);
+    for (const candidate of [`${target}.ts`, path.join(target, 'index.ts')]) {
+        if (fs.existsSync(candidate))
+            return fs.readFileSync(candidate, 'utf8');
+    }
+    return source;
+}
 function auditCommands({ rootDir, manifest, }) {
     const issues = [];
     const commands = manifest?.commands ?? {};
@@ -512,7 +541,7 @@ function auditCommands({ rootDir, manifest, }) {
         sourceCommandFiles = files.length;
         for (const file of files) {
             const rel = path.relative(sourceRoot, file);
-            const source = fs.readFileSync(file, 'utf8');
+            const source = readCommandSource(file);
             const command = commandIdFromRelativePath(rel);
             sourceCommandIds.add(command);
             const hasFromJson = /['"]from-json['"]/.test(source);