balladeer 1.0.5 → 1.0.7

package/README.md

@@ -41,10 +41,11 @@ To upgrade the executable and refresh in one command, run `npx -y balladeer@late
 
 Run `balladeer setup --refresh` to refresh repository instructions without replacing other tools'
 settings. For Codex, keep `--client codex`: `balladeer setup --client codex --refresh`. Existing
-instructions are not refreshed just because a package was installed. Refresh can contact npm and
-write the local toolchain when ensuring the executable is installed; it does not perform a Balladeer
-authority action. The repository MCP entry continues to use `npx -y balladeer@latest mcp` so native
-tools can pick up published updates.
+policy updates arrive through the project guidance loader after its initial activation. Installing a
+package alone does not prove the host loaded that guidance. Refresh can contact npm and write the
+local toolchain when ensuring the executable is installed; it does not perform a Balladeer authority
+action. The repository MCP entry continues to use `npx -y balladeer@latest mcp` so native tools can
+pick up published updates.
 
 Automatic installation supports macOS/Linux with zsh, bash or sh. It uses the active npm global
 prefix or a writable personal prefix; when needed, it adds a bounded PATH block to your shell
@@ -79,6 +80,22 @@ is refused, authorized MCP reads, coding and explicitly requested capture may co
 session ID. Do not invent an ID or trailer. This does not fix missing credentials, installation or
 authorization failures, and does not guarantee every CLI command works in every sandbox.
 
+## Current project guidance
+
+Version 1.0.7 introduces a stable instruction block and project-local guidance hooks. Setup writes
+Codex hooks in the connected project's `.codex/config.toml`, or Claude Code hooks in its
+`.claude/settings.json`. It never installs global hooks. The loader checks that the current
+project's MCP entry matches the requested repository and deployment before reading credentials or
+fetching guidance. An unrelated repository remains untouched.
+
+The next MCP launch can migrate recognized older Balladeer blocks; customized or conflicting blocks
+are left for an explicit repair. Review your coding host's normal hook trust prompt once. Project
+trust alone does not prove the hook is trusted or running. After activation, guidance is fetched at
+supported work boundaries, so policy revisions and rollbacks do not require another package
+installation or repository edit. A fetch failure keeps ordinary work moving and suppresses
+unsolicited capture until the current workspace mode is available. A delivery receipt proves context
+was emitted, not that an agent followed it.
+
 ## If npm cannot start the bootstrap
 
 An EPERM or EACCES error naming npm's cache happens before Balladeer starts. Use an allowed writable

package/dist/cli.d.ts

@@ -30,6 +30,8 @@ type Parsed = Readonly<{
      * rather than quietly resolved to the last one.
      */
     repositories: readonly string[];
+    hook: "codex" | "claude" | undefined;
+    event: "SessionStart" | "UserPromptSubmit" | "SubagentStart" | undefined;
     owner: string | undefined;
     /** `check-seals --install-hook`: write the optional pre-push hook. */
     installHook: boolean;

package/dist/cli.js

@@ -7,6 +7,7 @@ import { runCheckSeals } from "./commands/check-seals.js";
 import { runDiscover } from "./commands/discover.js";
 import { runExplain } from "./commands/explain.js";
 import { parseRole, runInvite } from "./commands/invite.js";
+import { runGuidance } from "./commands/guidance.js";
 import { runMcp } from "./commands/mcp.js";
 import { runPrepare } from "./commands/prepare.js";
 import { runPropose } from "./commands/propose.js";
@@ -170,6 +171,8 @@ export function parseArguments(argv) {
             throw new StoreError("usage", `${command} needs one of: ${SUBCOMMANDS[command].join(", ")}.`);
         }
     }
+    let hook;
+    let event;
     let json = false;
     let wait = false;
     let refresh = false;
@@ -216,7 +219,21 @@ export function parseArguments(argv) {
         }
         const [name, ...rest] = flag.split("=");
         const inline = rest.length > 0 ? rest.join("=") : undefined;
-        if (name === "--json")
+        if (name === "--hook") {
+            const requested = value("--hook", inline);
+            if (requested !== "codex" && requested !== "claude")
+                throw new StoreError("usage", "--hook needs codex or claude.");
+            hook = requested;
+        }
+        else if (name === "--event") {
+            const requested = value("--event", inline);
+            if (requested !== "SessionStart" &&
+                requested !== "UserPromptSubmit" &&
+                requested !== "SubagentStart")
+                throw new StoreError("usage", "--event needs SessionStart, UserPromptSubmit or SubagentStart.");
+            event = requested;
+        }
+        else if (name === "--json")
             json = true;
         else if (name === "--again")
             again = true;
@@ -334,6 +351,10 @@ export function parseArguments(argv) {
     if (command !== "setup" && repositories.length > 1) {
         throw new StoreError("usage", `${command} acts on one repository. Name --repository once, or run it again for the other.`);
     }
+    if (hook !== undefined && command !== "guidance")
+        throw new StoreError("usage", "--hook belongs to guidance.");
+    if (event !== undefined && command !== "guidance")
+        throw new StoreError("usage", "--event belongs to guidance.");
     const chosen = controlPlane ?? process.env.BALLADEER_CONTROL_PLANE?.trim() ?? DEFAULT_CONTROL_PLANE;
     return {
         command,
@@ -350,6 +371,8 @@ export function parseArguments(argv) {
         file,
         repository: repositories[0],
         repositories,
+        hook,
+        event,
         owner,
         installHook,
         fresh,
@@ -552,6 +575,21 @@ async function dispatch(parsed, write) {
                 environment: process.env,
                 write,
             });
+        case "guidance":
+            if (parsed.hook === undefined) {
+                write("guidance needs --hook codex or claude.\n");
+                return 4;
+            }
+            return runGuidance({
+                controlPlane: parsed.controlPlane,
+                hook: parsed.hook,
+                ...(parsed.event === undefined ? {} : { event: parsed.event }),
+                ...(parsed.repository === undefined ? {} : { repositoryId: parsed.repository }),
+                environment: process.env,
+                cwd: process.cwd(),
+                stdin: process.stdin,
+                write,
+            });
         case "mcp":
             return runMcp({
                 controlPlane: parsed.controlPlane,

package/dist/commands/guidance.d.ts

@@ -0,0 +1,17 @@
+import { type GuidanceEvent } from "../guidance.js";
+export type GuidanceOptions = Readonly<{
+    controlPlane: string;
+    repositoryId?: string;
+    hook: "codex" | "claude";
+    event?: GuidanceEvent;
+    runtimeGeneration?: string;
+    environment: NodeJS.ProcessEnv;
+    cwd: string;
+    stdin: NodeJS.ReadableStream;
+    write: (text: string) => void;
+    error?: (text: string) => void;
+    fetchImpl?: typeof fetch;
+    now?: () => number;
+}>;
+/** Hook stdout is bounded context only. Host prompts and transcript paths never leave this process. */
+export declare function runGuidance(options: GuidanceOptions): Promise<number>;

package/dist/commands/guidance.js

@@ -0,0 +1,109 @@
+import { validateProjectGuidanceScope } from "../guidance-install.js";
+import { GUIDANCE_UNAVAILABLE, loadGuidance, recordGuidanceContext, } from "../guidance.js";
+import { readCredentials } from "../store.js";
+function readInput(stream) {
+    return new Promise((resolve, reject) => {
+        let bytes = 0;
+        const chunks = [];
+        const finish = (error) => {
+            clearTimeout(timer);
+            stream.removeListener("data", data);
+            stream.removeListener("end", end);
+            stream.removeListener("error", failed);
+            stream.pause();
+            if (error)
+                reject(error);
+            else {
+                try {
+                    resolve(JSON.parse(Buffer.concat(chunks).toString("utf8")));
+                }
+                catch {
+                    reject(new Error("invalid_hook_input"));
+                }
+            }
+        };
+        const data = (chunk) => {
+            const buffer = Buffer.isBuffer(chunk) ? chunk : Buffer.from(chunk);
+            bytes += buffer.length;
+            if (bytes > 65_536)
+                finish(new Error("hook_input_oversized"));
+            else
+                chunks.push(buffer);
+        };
+        const end = () => finish();
+        const failed = () => finish(new Error("hook_input_unavailable"));
+        const timer = setTimeout(() => finish(new Error("hook_input_deadline")), 250);
+        stream.on("data", data);
+        stream.once("end", end);
+        stream.once("error", failed);
+    });
+}
+function eventFrom(input) {
+    if (!input || typeof input !== "object" || Array.isArray(input))
+        return undefined;
+    const event = input.hook_event_name;
+    return event === "SessionStart" || event === "SubagentStart" || event === "UserPromptSubmit"
+        ? event
+        : undefined;
+}
+function identifier(input) {
+    return typeof input === "string" && input.length > 0 && input.length <= 256 ? input : undefined;
+}
+/** Hook stdout is bounded context only. Host prompts and transcript paths never leave this process. */
+export async function runGuidance(options) {
+    // A globally invoked hook cannot use --repository to reach another project's connection.
+    if (!options.repositoryId ||
+        !validateProjectGuidanceScope({
+            cwd: options.cwd,
+            hook: options.hook,
+            repositoryId: options.repositoryId,
+            controlPlane: options.controlPlane,
+        }))
+        return 0;
+    let event = options.event ?? "SessionStart";
+    const emit = (context) => options.write(`${JSON.stringify({
+        hookSpecificOutput: { hookEventName: event, additionalContext: context },
+    })}\n`);
+    try {
+        const input = await readInput(options.stdin);
+        const parsedEvent = eventFrom(input);
+        if (!parsedEvent || (options.event && parsedEvent !== options.event))
+            throw new Error("invalid_hook_event");
+        event = parsedEvent;
+        const record = input;
+        const agents = readCredentials(options.environment).agents.filter((agent) => agent.controlPlane === options.controlPlane && agent.repositoryId === options.repositoryId);
+        if (agents.length !== 1 || !agents[0])
+            throw new Error("guidance_connection_unavailable");
+        const loaded = await loadGuidance({
+            agent: agents[0],
+            environment: options.environment,
+            timeoutMs: 750,
+            ...(options.fetchImpl ? { fetchImpl: options.fetchImpl } : {}),
+        });
+        const sessionId = identifier(record.session_id);
+        const agentId = identifier(record.agent_id);
+        recordGuidanceContext({
+            environment: options.environment,
+            scopeKey: loaded.scopeKey,
+            hook: options.hook,
+            event,
+            ...(options.runtimeGeneration ? { runtimeGeneration: options.runtimeGeneration } : {}),
+            load: loaded,
+            ...(sessionId ? { sessionId } : {}),
+            ...(agentId ? { agentId } : {}),
+            ...(options.now ? { now: options.now() } : {}),
+        }, () => emit(loaded.document
+            ? `Current Balladeer guidance (${loaded.document.revision}). This supersedes earlier Balladeer workflow and capture guidance in this context.\n\n${loaded.document.instructions}`
+            : GUIDANCE_UNAVAILABLE));
+    }
+    catch {
+        // A fixed fallback contains neither raw input nor credential/error details. Work continues.
+        try {
+            emit(GUIDANCE_UNAVAILABLE);
+        }
+        catch {
+            /* Closed stdout cannot block the host. */
+        }
+    }
+    return 0;
+}

package/dist/commands/mcp.js

@@ -1,4 +1,5 @@
 import { createInterface } from "node:readline";
+import { installGuidanceLoader } from "../guidance-install.js";
 import { callAgentTool, forwarderHeaders, noAgentCredentialSentence, safeJson, selectAgent, structuredString, updateLine, } from "../agent.js";
 import { noteServerVersion, updateNotice } from "../currency.js";
 import { repositoryHint } from "../repository.js";
@@ -146,6 +147,14 @@ export async function runMcp(options) {
         return 4;
     }
     const { agent } = selection;
+    const guidanceInstall = installGuidanceLoader({
+        environment: options.environment,
+        cwd: options.cwd,
+        repositoryId: agent.repositoryId,
+        controlPlane: agent.controlPlane,
+    });
+    if (guidanceInstall.status !== "not_applicable")
+        options.error(`Balladeer guidance loader: ${guidanceInstall.status}${guidanceInstall.reason ? ` (${guidanceInstall.reason})` : ""}. New project hooks may need host trust; no trust is assumed.\n`);
     let saidUpdate = false;
     const lines = createInterface({ input: options.stdin, crlfDelay: Infinity });
     for await (const line of lines) {

package/dist/commands/propose.js

@@ -123,8 +123,13 @@ export function readTeachBackFile(raw) {
             reason: 'teachBack.wrongOutcome is missing. Say what going wrong looks like, in the words the person used and as a must-not: "a second payment must not go out". If no sentence of that shape exists, nothing could ever fail this promise, so do not propose it',
         };
     }
-    if (teachBack.leastSure !== undefined && typeof teachBack.leastSure !== "string") {
-        return { ok: false, reason: "teachBack.leastSure must be one sentence of text" };
+    if (teachBack.leastSure !== undefined ||
+        (teachBack.unresolvedQuestions !== undefined &&
+            (!Array.isArray(teachBack.unresolvedQuestions) || teachBack.unresolvedQuestions.length > 0))) {
+        return {
+            ok: false,
+            reason: "Outstanding questions are retired. Clarify material ambiguity with the person before writing, and put their actual answer in the meaning and cases. Nothing was sent.",
+        };
     }
     return {
         ok: true,

package/dist/commands/setup.js

@@ -11,6 +11,7 @@ import { CI_BRANCH, commitWorkflowOnBranch, repositoryRoot, workflowOnDefaultBra
 import { MCP_CONFIG_FILE, currentEntry, entryRepositoryId, isOurEntry, mergeMcpConfig, readMcpConfig, stdioEntry, } from "../mcp-config.js";
 import { DESKTOP_CONFIG_FILE, desktopConfigLocation, desktopServerKey, desktopStdioEntry, mergeDesktopConfig, } from "../desktop-config.js";
 import { selectAgent } from "../agent.js";
+import { installGuidanceLoader } from "../guidance-install.js";
 import { findLegacyInstall, legacyMessage } from "../legacy.js";
 import { formatInstant } from "../local-time.js";
 import { checkoutEntryPath, commandLine, runningFromRegistryInstall } from "../release.js";
@@ -932,13 +933,35 @@ function hostConfigFile(options) {
     return options.client === "codex" ? CODEX_CONFIG_FILE : MCP_CONFIG_FILE;
 }
 function mergeHostConfig(options, root, repositoryId, published) {
-    const entry = stdioEntry(repositoryId, published);
+    const base = stdioEntry(repositoryId, published);
+    const entry = { ...base, args: [...base.args, "--control-plane", options.controlPlane] };
     return options.client === "codex"
-        ? mergeCodexConfig(root, { ...entry, args: [...entry.args, "--control-plane", options.controlPlane] }, options.controlPlane)
+        ? mergeCodexConfig(root, entry, options.controlPlane)
         : mergeMcpConfig(root, entry, options.controlPlane);
 }
 function writeHostConventions(options, root) {
-    return writeConventions(root, options.client === "codex" ? { file: "AGENTS.md" } : {});
+    const result = writeConventions(root, options.client === "codex" ? { file: "AGENTS.md" } : {});
+    if (result.kind === "written") {
+        const entry = options.client === "codex" ? readCodexEntry(root) : currentEntry(readMcpConfig(root));
+        const repositoryId = entryRepositoryId(entry);
+        if (repositoryId !== undefined) {
+            const loader = installGuidanceLoader({
+                environment: options.environment,
+                cwd: root,
+                repositoryId,
+                controlPlane: options.controlPlane,
+                host: options.client === "codex" ? "codex" : "claude",
+            });
+            emit(options, { step: "guidance_loader", ...loader });
+            say(options, loader.status === "installed_needs_host_trust" ||
+                loader.status === "installed_trust_unverified"
+                ? "Project guidance loader installed. Review new hooks in your coding host once; future policy updates do not change that hook definition. A fresh session is needed to observe it."
+                : loader.status === "unavailable"
+                    ? `Project guidance loader needs repair (${loader.reason}). No active hook is claimed.`
+                    : "No matching project guidance integration was found. No guidance hook was installed or activated.");
+        }
+    }
+    return result;
 }
 function hostNextSteps(options) {
     if (options.client === "codex")

package/dist/conventions.d.ts

@@ -27,7 +27,7 @@ export declare const CONVENTIONS_END = "<!-- balladeer:conventions:end -->";
  * instructions marker instead. A bump here with no change to the block would
  * rewrite twelve repositories to say exactly what they already said.
  */
-export declare const CONVENTIONS_VERSION = 18;
+export declare const CONVENTIONS_VERSION = 20;
 export declare function managedByLine(version: number): string;
 /**
  * Which version of the block a file already carries, or nothing when it carries

package/dist/conventions.js

@@ -31,7 +31,7 @@ export const CONVENTIONS_END = "<!-- balladeer:conventions:end -->";
  * instructions marker instead. A bump here with no change to the block would
  * rewrite twelve repositories to say exactly what they already said.
  */
-export const CONVENTIONS_VERSION = 18;
+export const CONVENTIONS_VERSION = 20;
 /** Both spellings: the stable marker, and the versioned one version 1 wrote. */
 const START_MARKER = /<!-- balladeer:conventions:start(?: v(\d{1,4}))? -->/g;
 const END_MARKER = /<!-- balladeer:conventions:end -->/g;

package/dist/copy.d.ts

@@ -69,7 +69,7 @@ export declare const RETRIEVAL_SCOPE = "### Reading what is already agreed\n\nRe
  * plane's `/agent` page carries the same bytes under its own constant, and a
  * packaging test compares them.
  */
-export declare const SESSION_BEHAVIORS = "### Three things to offer without being asked\n\nAt the start of any session in this repository, before you plan anything, ask list_promises for the\npromises nothing is checking yet that belong to the person you are working with: `unverified` true\nand `mine` true, which is one bounded read rather than the catalog. If it returns any, say so in one\nline and offer to build their verifiers now. Name each one by its one-sentence claim rather than by\nan id, so the person can see which behavior is unguarded. Ask the same tool for\n`brokenSinceLastSeen` true as well, and where that returns any, say in one line that those promises\nbroke since they last looked, name each by its claim, and offer to fix them. Then wait for their\nanswer. The offer is the whole of it, and never start building or repairing one because nobody said\nno.\n\nTheirs, and nobody else's. `mine` keeps the promises this person owns or agreed to, and a teammate's\nunguarded promise is that teammate's to hear about: a session that opens by reading out other\npeople's unfinished work reads as an audit of them. `brokenSinceLastSeen` is that person's own by\nconstruction and needs no `mine` beside it. Drop `mine` when this person asks what the rest of the\nteam has promised, and say whose promises you are showing them when you do.\n\nWhen you have proposed promises, show them here as well as there. Put each proposal in the\nconversation in full: its one-sentence claim, who it is for, when it applies and what must then be\ntrue, the numbered cases that must keep working and the ones that must be caught, and every question\nyou left open. Then offer to finish the agreement from here, by asking for a sign-off, giving them\nthe page it returns and taking the one-time code that page shows them, so the browser is needed only\nfor signing. Give them the review link in the same message too, because some people would rather\nread it there and edit it before they agree.\nA promise whose meaning is agreed and which nothing is checking yet is one you can finish. When\nsomebody gives you a promise id, run `balladeer status <promise id>`, or expand it with get_promise.\nIf it comes back agreed with nothing checking it, say so in one line and offer to prepare and build\nits verifier now. Only if they say yes: `prepare_qualification` mints the one-time setup, or\n`balladeer prepare <promise id>` mints it and writes it where the sealed run reads it. You need no\nsign-off for that and there is no code to ask anybody for, because agreeing the meaning was their\nact and building the check that proves it is yours. Then build the verifier, seal it, push, and tell\nthem protection starts by itself when that run qualifies. The offer is the whole of it: never\nprepare one because nobody said no.";
+export declare const SESSION_BEHAVIORS = "### Three things to offer without being asked\n\nAt the start of any session in this repository, before you plan anything, ask list_promises for the\npromises nothing is checking yet that belong to the person you are working with: `unverified` true\nand `mine` true, which is one bounded read rather than the catalog. If it returns any, say so in one\nline and offer to build their verifiers now. Name each one by its one-sentence claim rather than by\nan id, so the person can see which behavior is unguarded. Ask the same tool for\n`brokenSinceLastSeen` true as well, and where that returns any, say in one line that those promises\nbroke since they last looked, name each by its claim, and offer to fix them. Then wait for their\nanswer. The offer is the whole of it, and never start building or repairing one because nobody said\nno.\n\nTheirs, and nobody else's. `mine` keeps the promises this person owns or agreed to, and a teammate's\nunguarded promise is that teammate's to hear about: a session that opens by reading out other\npeople's unfinished work reads as an audit of them. `brokenSinceLastSeen` is that person's own by\nconstruction and needs no `mine` beside it. Drop `mine` when this person asks what the rest of the\nteam has promised, and say whose promises you are showing them when you do.\n\nWhen you have proposed promises, show them here as well as there. Put each proposal in the\nconversation in full: its one-sentence claim, who it is for, when it applies and what must then be\ntrue, and the numbered cases that must keep working and the ones that must be caught. Do not\nstore or present an unanswered-question backlog. Then offer to finish the agreement from here, by asking for a sign-off, giving them\nthe page it returns and taking the one-time code that page shows them, so the browser is needed only\nfor signing. Give them the review link in the same message too, because some people would rather\nread it there and edit it before they agree.\nA promise whose meaning is agreed and which nothing is checking yet is one you can finish. When\nsomebody gives you a promise id, run `balladeer status <promise id>`, or expand it with get_promise.\nIf it comes back agreed with nothing checking it, say so in one line and offer to prepare and build\nits verifier now. Only if they say yes: `prepare_qualification` mints the one-time setup, or\n`balladeer prepare <promise id>` mints it and writes it where the sealed run reads it. You need no\nsign-off for that and there is no code to ask anybody for, because agreeing the meaning was their\nact and building the check that proves it is yours. Then build the verifier, seal it, push, and tell\nthem protection starts by itself when that run qualifies. The offer is the whole of it: never\nprepare one because nobody said no.";
 /**
  * The capture rules that do not change: when to say nothing, what a yes is
  * worth, and the two promises Balladeer refuses.
@@ -97,7 +97,7 @@ export declare const SESSION_BEHAVIORS = "### Three things to offer without bein
  * repository, the instructions the MCP server sends on initialize, and the page
  * an agent fetches cannot come to say different things about when to stay quiet.
  */
-export declare const CAPTURE_SEAM = "### When to say nothing, and what a yes is worth\n\nMost rules are said in passing, in the middle of something else. Somebody saying one has not asked\nyou to record anything, so propose nothing and start no interview. When you do ask, it is one line\nappended to the end of the reply you were already going to give, never a message of its own, never\nasked twice about the same rule, and nothing is proposed until they say yes. A no ends it, and that\nrule is not raised again for the rest of the conversation.\n\nSilence is per conversation rather than per message. Once a conversation is one of these, you ask\nnothing for the rest of it, however good the rule sounds:\n\n- A question, or working out how something already behaves. Nothing is filed and nothing is offered.\n- A refactor. Nobody predicts a promise from a rewrite. Offer the promises this area already carries\n  that nothing is checking yet, once, and then wait. Ask nothing about new ones.\n- A change to wording alone. Wording somebody may change again tomorrow is not a rule.\n- An incident, while it is still being fixed. Ask nothing at all until the fix is merged or they say\n  it is done, however good tonight's failing case would be.\n- Somebody still weighing options. A decision nobody has made yet is not a rule.\n- An exploration or spike. It ends in nothing or in a plan, and its sentences sound like rules and\n  are not.\n- Reading somebody else's change, while you are still reading it. Nothing is offered until they\n  give a verdict.\n\nThe words to ask in, the moment to offer, and the shape a proposal takes are not in this file. The\nBalladeer server sends them at the start of every session, and its copy is the current one: read\nwhat it sent this session rather than what this file remembers.\n\n### Two promises Balladeer cannot keep\n\nA promise about speed needs three things before it is a promise at all: a number, a percentile, and\nwhere it is measured. \"The quote page answers in under one second at p95, measured in production at\npeak load\" is one Balladeer can keep. \"The quote page has to be fast\" is not. Say this, and ask for\nthe part that is missing rather than filing it:\n\n\"I can keep that once it has a number, a percentile, and a place it is measured. Without those it is\na wish, not a promise.\"\n\nBalladeer refuses one without all three and names which of them is missing. When all three are\nthere, write the measurement method into the promise, and tell them plainly that it reads agreed and\nunprotected until a test that actually measures it exists.\n\nA promise about how the team works is not something the software does, so no check can ever catch\nit. \"We must provide a low-friction capture experience\" is one of these. File nothing and say:\n\n\"That is a promise about how we work, not something the software does that a check can fail.\nBalladeer only keeps promises a check can catch. If a customer would notice something when this\nslips, say that and I will keep that instead.\"\n\nThen take the customer-visible half if they give you one, and file that instead.";
+export declare const CAPTURE_SEAM = "### When to offer, and what a yes is worth\n\nNotice durable customer behavior during ordinary work. Offer to preserve a concrete behavior\nbeside useful work, without blocking implementation. File nothing until the person explicitly\nasks you to record it or accepts a scoped capture offer. A factual answer or permission to build\nalone is not permission to record. A no ends that offer; do not raise it again in this conversation.\n\nDo not offer while the user is comparing options or exploring without a decision. If they later\nchoose a concrete behavior, you may offer to capture it even though the conversation began as\nexploration. Do not offer new promises for pure refactors or cosmetic changes. During an active\nproduction incident, prioritize recovery and defer capture until recovery. Ordinary bug fixing\nis not automatically an active production incident.\n\nFor clear feature intent, an offer before implementation can make the promise a target for the\nwork. For a normal bug fix, offer alongside the completed fix and checks. Neither requires a\nmerge or another human closing reply. If the user is away, one nonblocking offer can remain in\nyour completion message for their return; do not file or wait for an answer.\n\nUse available context to state a specific behavior. A precise capture offer can confirm your\ninterpretation and obtain permission to record in one yes. Ask a separate work question only\nwhen a consequential choice remains that a clear, scoped offer cannot resolve. An unanswered\nearlier question is not itself a reason to ask again. The server supplies current detailed guidance.\n\n### Two promises Balladeer cannot keep\n\nA promise about speed needs three things before it is a promise at all: a number, a percentile, and\nwhere it is measured. \"The quote page answers in under one second at p95, measured in production at\npeak load\" is one Balladeer can keep. \"The quote page has to be fast\" is not. Say this, and ask for\nthe part that is missing rather than filing it:\n\n\"I can keep that once it has a number, a percentile, and a place it is measured. Without those it is\na wish, not a promise.\"\n\nBalladeer refuses one without all three and names which of them is missing. When all three are\nthere, write the measurement method into the promise, and tell them plainly that it reads agreed and\nunprotected until a test that actually measures it exists.\n\nA promise about how the team works is not something the software does, so no check can ever catch\nit. \"We must provide a low-friction capture experience\" is one of these. File nothing and say:\n\n\"That is a promise about how we work, not something the software does that a check can fail.\nBalladeer only keeps promises a check can catch. If a customer would notice something when this\nslips, say that and I will keep that instead.\"\n\nThen take the customer-visible half if they give you one, and file that instead.";
 /**
  * How an agent describes one promise or proposal to a person, and how the two
  * of them settle what is still open on it.
@@ -115,7 +115,7 @@ export declare const CAPTURE_SEAM = "### When to say nothing, and what a yes is
  * initialize, and the page `/agent` serves. A packaging test holds them
  * together.
  */
-export declare const SETTLING_QUESTIONS = "### When somebody says \"tell me about\" one\n\nAn id is how a person points at something here, and every promise page and every proposal page\ncarries one. A promise id starts with prom_ and a proposal id starts with cand_: expand a promise\nwith get_promise and a proposal with get_proposal, and read neither of them out as a list of fields.\nSay in four or five sentences what it is for, who it is for, when it applies and what must then be\ntrue. Then say where it stands: a promise is agreed, and either protected or not yet checked by\nanything; a proposal is agreed by nobody and waiting on the person it names.\n\nClarify ambiguity that materially changes the behavior during capture, within the existing\nquestion budget; never invent an answer.\n\nOrdinary open questions record uncertainty; they do not prevent the named owner from agreeing to\nthe behavior as written. Agreement does not answer them or add an unstated guarantee. Separate\ncatalog-conflict questions can hold agreement until the owner rules on the stated conflict. Do not\ncall a proposal unready just because it has ordinary open questions. Offer to discuss them if\nuseful; if the person wants to, take them one at a time in the order they come back. For each ordinary question,\nsay what it decides in their words rather than in the question's; give your\nrecommendation and the reason you hold it, drawn from this repository and from the promise itself; and stop there. When\nthey answer, record what they said with resolve_question, in their own words where they gave you\nany, and where their answer changes the promise, follow it with update_proposal, add_case or\nremove_case and tell them what you changed. Never invent an answer or clear uncertainty because\nthey chose to agree. None of that agrees to anything: the named owner agrees, in their own browser\nor through a sign-off you carry, and the questions they answered stay on the proposal in their name.\n\nThe same rule governs every question you leave open in the first place. A question that names a gap\nand stops is a note, and nobody can answer a note. Say what answering it decides, in the words a\ncustomer would use, and carry your own best guess with the reason behind it, so that the shortest\ntrue answer is yes. For example: \"Decides: whether a worker that is running but reconciling nothing\ncounts as an outage this promise covers. Best guess: yes, because the promise is about somebody\nhearing before a customer does, and a wedged worker is invisible to every check this repository has.\nSay yes, or tell me otherwise.\" Balladeer refuses a question filed without both halves and says\nwhich one is missing.";
+export declare const SETTLING_QUESTIONS = "### When somebody says \"tell me about\" one\n\nAn id is how a person points at something here. Expand a promise id with get_promise and a proposal\nid with get_proposal. Describe who it is for, when it applies, the behavior and the concrete cases.\nA proposal awaits its named owner's agreement; a promise is agreed and may still be unprotected.\nPreviously recorded answers are historical reasoning, not a new interview or an approval.\nIf the person wants a change, clarify the changed commitment before writing it. Preserve all other\nmeaning and cases. An agreed promise changes only through a revision its named owner approves.";
 /**
  * What a session may spend on reading, in three sentences.
  *
@@ -193,7 +193,7 @@ export declare const SESSION_STAMP = "Use the installed `balladeer` command afte
  * block that drifts per run would rewrite a customer's committed file on every
  * setup and the diff would say nothing.
  */
-export declare const CONVENTIONS_BLOCK = "## Balladeer promises\n\nBefore planning work in this repository, read the promises this team has already approved through\nthe Balladeer MCP server. They are the behaviors a named person has agreed the software keeps, so\nyour plan has to hold them, not just read them.\n\n### Reading what is already agreed\n\nRetrieve by promise, and only when this session has a reason to. One repository here can hold a\nthousand agreed promises, and a plan built from whatever survived a truncated catalog read is worse\nthan a plan built from none of it, because nothing tells you which half went missing.\n\nWhen a person gives you a promise id, expand exactly that one with get_promise and stop there. Every\npromise page carries a control that copies its id, so an id is what a person hands you when they\nmean a particular promise. Ask for one rather than searching for what they meant.\n\nConsult list_promises in two situations and no others. The person asks what this repository has\npromised, in which case page the index they asked for. Or the change you are about to make touches\npaths that carry promises, in which case give those paths to list_promises: it answers with the\npromises whose scope overlaps them, closest first, and with the few that name no path and so cover\nthe whole repository. That answer is a selection rather than a page and does not continue with a\ncursor, so when the total beside it is larger than what you were handed, narrow the paths rather\nthan asking for more.\n\nWhen you do not yet know which paths you are about to touch, do not call the index at all. Work from\nids until you do, because a page you did not ask a question of is not about your change, and reading\none as though it were is how a plan quietly misses the promise it breaks.\n\nTo learn which paths those are, read `paths` on a list_promises answer you asked for\nwithout paths of your own. It is the set of\nrepository paths this repository's promises are scoped to, deduplicated and bounded, with\n`pathsTruncated` saying whether there were more than the answer carries. Compare the files you are\nabout to change against it. Nothing matching means there is nothing here to read, and saying so is a\nbetter answer than a page of promises about somewhere else.\n\nNever call get_promise_context at the start of a session. It answers the markers you give it, and\nbefore you know what you are changing there are no markers to give: what comes back is a slice of\nthe catalog chosen by nothing. Call it once the work is in front of you, with that work's markers.\n\nEvery one of these reads is bounded and none of them returns the whole catalog. Read the total\nbeside the rows and the sentence in `scope` that says what the total is a total of, and when the\ntotal is larger than what you were handed, page or narrow rather than planning as though you had\nseen everything.\n\nEach index row carries what it takes to rule that promise out without fetching it: the repository,\nthe paths it covers, its one-sentence claim, what protects it and why, and when anything last\nchecked it.\n\nPrefer the measurement over the markers. Where this repository has a touch map, `balladeer affected\n<paths...>` answers which promises ran the files in front of you, out of what each verifier actually\nexecuted the last time `balladeer touch-map` measured it. Both commands run on this machine and\nsend Balladeer nothing, so you may name any path in the change.\n\nAn answer marked stale was measured against a verifier that has changed since, so read it as the\nlast thing anybody measured rather than as fact, and offer to run `balladeer touch-map` again.\nWhere there is no map, where it does not name your paths, or where it reports a promise it could not\nmeasure, fall back to the paths on the index rows. The map narrows which promises are worth\nfetching. It never widens what you may read: the catalog is still never enumerated, and the fetch\nbudget is unchanged.\n\nWhen a retrieval receipt asks why you read a row, the answer for one the map named is `touch`.\n\nFetch by id, and only for an id the person gave you or an index row whose paths match the change in\nfront of you. Never enumerate the catalog. Never chain one fetch into the next to see the whole of\nsomething: when the rows do not settle it, narrow the filter rather than expanding another promise.\n\n### When to say nothing, and what a yes is worth\n\nMost rules are said in passing, in the middle of something else. Somebody saying one has not asked\nyou to record anything, so propose nothing and start no interview. When you do ask, it is one line\nappended to the end of the reply you were already going to give, never a message of its own, never\nasked twice about the same rule, and nothing is proposed until they say yes. A no ends it, and that\nrule is not raised again for the rest of the conversation.\n\nSilence is per conversation rather than per message. Once a conversation is one of these, you ask\nnothing for the rest of it, however good the rule sounds:\n\n- A question, or working out how something already behaves. Nothing is filed and nothing is offered.\n- A refactor. Nobody predicts a promise from a rewrite. Offer the promises this area already carries\n  that nothing is checking yet, once, and then wait. Ask nothing about new ones.\n- A change to wording alone. Wording somebody may change again tomorrow is not a rule.\n- An incident, while it is still being fixed. Ask nothing at all until the fix is merged or they say\n  it is done, however good tonight's failing case would be.\n- Somebody still weighing options. A decision nobody has made yet is not a rule.\n- An exploration or spike. It ends in nothing or in a plan, and its sentences sound like rules and\n  are not.\n- Reading somebody else's change, while you are still reading it. Nothing is offered until they\n  give a verdict.\n\nThe words to ask in, the moment to offer, and the shape a proposal takes are not in this file. The\nBalladeer server sends them at the start of every session, and its copy is the current one: read\nwhat it sent this session rather than what this file remembers.\n\n### Two promises Balladeer cannot keep\n\nA promise about speed needs three things before it is a promise at all: a number, a percentile, and\nwhere it is measured. \"The quote page answers in under one second at p95, measured in production at\npeak load\" is one Balladeer can keep. \"The quote page has to be fast\" is not. Say this, and ask for\nthe part that is missing rather than filing it:\n\n\"I can keep that once it has a number, a percentile, and a place it is measured. Without those it is\na wish, not a promise.\"\n\nBalladeer refuses one without all three and names which of them is missing. When all three are\nthere, write the measurement method into the promise, and tell them plainly that it reads agreed and\nunprotected until a test that actually measures it exists.\n\nA promise about how the team works is not something the software does, so no check can ever catch\nit. \"We must provide a low-friction capture experience\" is one of these. File nothing and say:\n\n\"That is a promise about how we work, not something the software does that a check can fail.\nBalladeer only keeps promises a check can catch. If a customer would notice something when this\nslips, say that and I will keep that instead.\"\n\nThen take the customer-visible half if they give you one, and file that instead.\n\nUse the installed `balladeer` command after setup reports CLI readiness. If it is missing from\nPATH (including an older 1.0.4 setup), use `npx -y balladeer@latest <command>` for that invocation\nand read the current /agent instructions for installation or repair. Do not claim that an older\nrepository's instructions were refreshed. CLI availability does not prove that this coding host\nloaded the native MCP tools or that a credential is authorized. The optional session stamp below\nis separate from all three.\n\nRun `balladeer session` when you start work here and pass the id it prints to every promise read\nyou make, as `session`. It is the same id for the whole of one piece of work, and it costs nothing:\na read without it is answered exactly the same way.\n\nIf local file permissions refuse that session write, no session stamp was saved. Your saved\nconnection is unchanged; this does not prove its current server authorization. Continue\nalready-authorized MCP reads, coding and explicitly requested capture without the optional\n`session` field. Do not invent an ID, add a session trailer, or record an unsaved stamp. Do not\nbroaden filesystem access or move credentials to retry this write. A missing credential or server\nauthorization refusal is different: follow that refusal. Capture still needs the person's request\nor accepted offer, and human meaning approval is unchanged.\n\nIf a session ID was saved, near the end of the work call `mark_promise_used` with the ids you actually cited\nor acted on. Naming none is a fine answer. It is the only way anybody finds out which rows were\nworth sending you, because reading a promise and then ignoring it is not the same as using it.\n\nIf a session ID was saved, write `Balladeer-Session: <the id>` into the commit message or pull-request body you produce,\nand run `balladeer session --record` once the commit exists. That is what lets a check that goes red\nnext week be read back against what Balladeer told you before you started. Your commit message never\nleaves your machine: only the session id and the commit SHA are sent.\n\n### When somebody asks you to protect a behavior\n\nSomebody has asked you to protect a behavior when they say what the software must do, or must never\ndo again, and mean it as a rule rather than as this one bug. That is one promise, for the behavior\nthey named, and nothing else: if you notice others worth protecting, say so in a sentence and let\nthem choose, and file none of them. Never propose from a conversation that did not ask you to. A\nquestion about how something works and a plan you were asked to sketch are not requests to record\nanything, nor is a fix nobody asked you to write a rule about.\n\nAsk before you extrapolate. Ask only what you cannot work out for yourself, ask it all in one\nmessage, and stop at four. Four is a ceiling, not a target: two good ones are better. Then write the\nproposal with what you have and put whatever is still open in its open questions rather than going\nback. Never ask what this repository would answer, such as which file, which test, or which branch,\nand never ask anyone for Balladeer's own identifiers: get_promise_setup carries this repository's id\nand who can own a promise. Never ask again for what they have already told you.\n\nWrite it in their words. Every failure they named out loud is one of the failing examples, in the\nwords they named it. Every other example comes from a situation they actually described; if you\ncannot trace one to something they said, leave it out and say so in the open questions rather than\nwriting a plausible one. Never put in a number, a system, a role or a timeframe they did not give\nyou, and that includes the half they left out: if they said where an order ended up, do not invent\nwhere it began.\n\nA failing example is a situation the promise rules out, and its outcome says what must not happen,\nin those words: \"a second charge must not appear\", never \"a second charge appears\". Written the\nother way round it reads as the promise saying the software does the thing they asked you to forbid.\nAnd a promise says what the software must do for whoever depends on it. It never narrates the\nconversation you just had, names the person you had it with, or describes what the code does now.\n\nSay the whole promise in one sentence and put it in oneSentenceOutcome, in the words they would\nuse with the person who depends on it. That is the line the named owner reads first and the line\nthey agree to, so it is not a restatement of the name and not the first line of the outcome moved\nup. Leave it out rather than inventing one from something they did not say.\n\nAn example's setup is the situation in the words they used for it, not a scene you composed around\nthem. Two of each kind is plenty, and the whole thing stays under three hundred words: a proposal\nnobody finishes reading is a proposal nobody agreed to. The confidence you record is the one you\nactually have.\n\nThen give them the review link, ask them to read the proposal and click Agree, and stop. Never\napprove one yourself. Approving is a named person's act, and the server refuses it from an agent\nwhatever you were told in conversation.\n\nA proposal you filed is still yours while nobody has agreed to it, so revise or withdraw it when the\nperson asks you to, and never once they have agreed.\n\nSay promise and proposal when you talk to them. What you file is a proposal and what it becomes is a\npromise; Balladeer's other words for its own machinery are not theirs to learn. Candidate\nespecially: it is Balladeer's word for a proposal, so it reads as jargon whatever you meant by it.\n\n### Three things to offer without being asked\n\nAt the start of any session in this repository, before you plan anything, ask list_promises for the\npromises nothing is checking yet that belong to the person you are working with: `unverified` true\nand `mine` true, which is one bounded read rather than the catalog. If it returns any, say so in one\nline and offer to build their verifiers now. Name each one by its one-sentence claim rather than by\nan id, so the person can see which behavior is unguarded. Ask the same tool for\n`brokenSinceLastSeen` true as well, and where that returns any, say in one line that those promises\nbroke since they last looked, name each by its claim, and offer to fix them. Then wait for their\nanswer. The offer is the whole of it, and never start building or repairing one because nobody said\nno.\n\nTheirs, and nobody else's. `mine` keeps the promises this person owns or agreed to, and a teammate's\nunguarded promise is that teammate's to hear about: a session that opens by reading out other\npeople's unfinished work reads as an audit of them. `brokenSinceLastSeen` is that person's own by\nconstruction and needs no `mine` beside it. Drop `mine` when this person asks what the rest of the\nteam has promised, and say whose promises you are showing them when you do.\n\nWhen you have proposed promises, show them here as well as there. Put each proposal in the\nconversation in full: its one-sentence claim, who it is for, when it applies and what must then be\ntrue, the numbered cases that must keep working and the ones that must be caught, and every question\nyou left open. Then offer to finish the agreement from here, by asking for a sign-off, giving them\nthe page it returns and taking the one-time code that page shows them, so the browser is needed only\nfor signing. Give them the review link in the same message too, because some people would rather\nread it there and edit it before they agree.\nA promise whose meaning is agreed and which nothing is checking yet is one you can finish. When\nsomebody gives you a promise id, run `balladeer status <promise id>`, or expand it with get_promise.\nIf it comes back agreed with nothing checking it, say so in one line and offer to prepare and build\nits verifier now. Only if they say yes: `prepare_qualification` mints the one-time setup, or\n`balladeer prepare <promise id>` mints it and writes it where the sealed run reads it. You need no\nsign-off for that and there is no code to ask anybody for, because agreeing the meaning was their\nact and building the check that proves it is yours. Then build the verifier, seal it, push, and tell\nthem protection starts by itself when that run qualifies. The offer is the whole of it: never\nprepare one because nobody said no.\n\n### When somebody says \"tell me about\" one\n\nAn id is how a person points at something here, and every promise page and every proposal page\ncarries one. A promise id starts with prom_ and a proposal id starts with cand_: expand a promise\nwith get_promise and a proposal with get_proposal, and read neither of them out as a list of fields.\nSay in four or five sentences what it is for, who it is for, when it applies and what must then be\ntrue. Then say where it stands: a promise is agreed, and either protected or not yet checked by\nanything; a proposal is agreed by nobody and waiting on the person it names.\n\nClarify ambiguity that materially changes the behavior during capture, within the existing\nquestion budget; never invent an answer.\n\nOrdinary open questions record uncertainty; they do not prevent the named owner from agreeing to\nthe behavior as written. Agreement does not answer them or add an unstated guarantee. Separate\ncatalog-conflict questions can hold agreement until the owner rules on the stated conflict. Do not\ncall a proposal unready just because it has ordinary open questions. Offer to discuss them if\nuseful; if the person wants to, take them one at a time in the order they come back. For each ordinary question,\nsay what it decides in their words rather than in the question's; give your\nrecommendation and the reason you hold it, drawn from this repository and from the promise itself; and stop there. When\nthey answer, record what they said with resolve_question, in their own words where they gave you\nany, and where their answer changes the promise, follow it with update_proposal, add_case or\nremove_case and tell them what you changed. Never invent an answer or clear uncertainty because\nthey chose to agree. None of that agrees to anything: the named owner agrees, in their own browser\nor through a sign-off you carry, and the questions they answered stay on the proposal in their name.\n\nThe same rule governs every question you leave open in the first place. A question that names a gap\nand stops is a note, and nobody can answer a note. Say what answering it decides, in the words a\ncustomer would use, and carry your own best guess with the reason behind it, so that the shortest\ntrue answer is yes. For example: \"Decides: whether a worker that is running but reconciling nothing\ncounts as an outage this promise covers. Best guess: yes, because the promise is about somebody\nhearing before a customer does, and a wedged worker is invisible to every check this repository has.\nSay yes, or tell me otherwise.\" Balladeer refuses a question filed without both halves and says\nwhich one is missing.\n\n### Files that are sealed, and the one reason to edit one\n\nEvery file under .continuity/promises/ is sealed. The promise that owns that directory records the\nexact bytes of each file in it, so editing one, adding one there, renaming one or deleting one\nbreaks the seal. A promise whose seal is broken stops being checked, and it stays that way until a\nnamed person qualifies it again, which is their afternoon rather than your commit. Nothing in there\nis ordinary source: keep it out of refactors, formatting runs and dependency upgrades.\n\nFind out which directories are sealed before you plan an edit, not after. balladeer status lists\nthem, and list_promises names a promise's sealed directory on its row once a verifier is bound to\nit. Then, before you push, run balladeer check-seals. It prints nothing and exits zero when your\nchange touches no seal, and names the promise, its owner and its page when your change would break\none.\n\nThe one reason to edit a sealed file is to repair a verifier that can no longer run: something it\nimports moved, or the language it is written in changed under it. Never edit one to make a failing\ncheck pass. A check going red is the promise doing its job, and the repair for that belongs in the\nbehavior it protects. A repair is not finished until the promise is sealed again with the runner\nthis repository is pinned to. get_promise_setup carries that exact seal command, and\nballadeer check-seals prints it beside any promise it names.\n\n### The rest of a promise's life\nWhen a promise is obsolete, finished, deliberately off for a while, or owned by the wrong person,\npropose the change and hand them the promise page. Deciding is theirs.\n\nYou can finish one of those acts here, and only one way. Ask for a sign-off with\nrequest_owner_signoff, give them the page it returns, and ask for the one-time code that page shows\nthem. Then call the act's own tool with that code and their own words. Never call one on your own\ninitiative, never on a general approval of some earlier act, and never ask for a code you were not\ngiven: a refusal is the person's to resolve, not yours to retry. Balladeer records them as the\nperson who acted and you as the messenger.\n\nReport the promise's state exactly as Balladeer reported it: proposed, agreed, or protected, never\none in place of another.\n\n### Where your team watches this\n\nBalladeer is a web app as well as these tools, at the address setup printed. Its catalog lists every\npromise with who owns it and whether anything is checking it, and each promise has a page of its own\nshowing what this team agreed the software must do and then every run that has checked it since,\nnewest first, with the commit each one checked. Whenever there is a link to give, give the link\nrather than a summary of it: the page says what you would have said, and it stays true after this\nconversation has ended.\n\nBalladeer also has a Slack app, which a workspace administrator installs from workspace settings.\nOnce it is installed, whoever owns a promise gets a direct message when theirs goes live and when a\nrun on the default branch breaks it. Until somebody installs it, nothing is sent anywhere, so say it\nis available rather than saying they will be told.\n\n### Questions people ask\n\nAnswer these when they come up. Where you do not know, say so and point at the address setup\nprinted: a confident wrong answer about what a vendor can see is worse than no answer.\n\nWhat it does: it holds the behaviors this team has agreed the software must keep, and reports\nwhether each one is still being kept, from this repository's own tests running in its own CI.\n\nWhat it sees: the text of each promise somebody approves, this repository's numeric ids and the name\nof its default branch, and from CI the pass or fail outcome, the commit checked, and content hashes.\nNever the code, the tests, the fixtures, the logs, the prompts, or the transcripts.\n\nWhat stopping costs: nothing that matters to their tests. The verifier package, its fixtures and the\nworkflow file are theirs, in their repository, running in their CI, and disconnecting changes none\nof them. An administrator can download everything Balladeer holds at any time from workspace\nsettings, and disconnecting hands them that same download in the response that ends access.\n\nWho can approve one: the named person who owns it, in their own browser. Not an administrator on\ntheir behalf, and never you.\n\nWhether it blocks a merge: no. The check is advisory on Balladeer's side, and their own branch\nprotection is what decides whether a failing check stops anything.\n\nWho can invite people and change setup: a workspace administrator. A contributor can read the\nworkspace and propose promises, and a viewer can read it. If somebody asks you to add a teammate,\ninvite_teammate returns the page an administrator sends the invitation from, with the address filled\nin for them to read. The tool sends nothing itself: an administrator presses Send.";
+export declare const WORKFLOW_GUIDANCE = "## Balladeer promises\n\nBefore planning work in this repository, read the promises this team has already approved through\nthe Balladeer MCP server. They are the behaviors a named person has agreed the software keeps, so\nyour plan has to hold them, not just read them.\n\n### Reading what is already agreed\n\nRetrieve by promise, and only when this session has a reason to. One repository here can hold a\nthousand agreed promises, and a plan built from whatever survived a truncated catalog read is worse\nthan a plan built from none of it, because nothing tells you which half went missing.\n\nWhen a person gives you a promise id, expand exactly that one with get_promise and stop there. Every\npromise page carries a control that copies its id, so an id is what a person hands you when they\nmean a particular promise. Ask for one rather than searching for what they meant.\n\nConsult list_promises in two situations and no others. The person asks what this repository has\npromised, in which case page the index they asked for. Or the change you are about to make touches\npaths that carry promises, in which case give those paths to list_promises: it answers with the\npromises whose scope overlaps them, closest first, and with the few that name no path and so cover\nthe whole repository. That answer is a selection rather than a page and does not continue with a\ncursor, so when the total beside it is larger than what you were handed, narrow the paths rather\nthan asking for more.\n\nWhen you do not yet know which paths you are about to touch, do not call the index at all. Work from\nids until you do, because a page you did not ask a question of is not about your change, and reading\none as though it were is how a plan quietly misses the promise it breaks.\n\nTo learn which paths those are, read `paths` on a list_promises answer you asked for\nwithout paths of your own. It is the set of\nrepository paths this repository's promises are scoped to, deduplicated and bounded, with\n`pathsTruncated` saying whether there were more than the answer carries. Compare the files you are\nabout to change against it. Nothing matching means there is nothing here to read, and saying so is a\nbetter answer than a page of promises about somewhere else.\n\nNever call get_promise_context at the start of a session. It answers the markers you give it, and\nbefore you know what you are changing there are no markers to give: what comes back is a slice of\nthe catalog chosen by nothing. Call it once the work is in front of you, with that work's markers.\n\nEvery one of these reads is bounded and none of them returns the whole catalog. Read the total\nbeside the rows and the sentence in `scope` that says what the total is a total of, and when the\ntotal is larger than what you were handed, page or narrow rather than planning as though you had\nseen everything.\n\nEach index row carries what it takes to rule that promise out without fetching it: the repository,\nthe paths it covers, its one-sentence claim, what protects it and why, and when anything last\nchecked it.\n\nPrefer the measurement over the markers. Where this repository has a touch map, `balladeer affected\n<paths...>` answers which promises ran the files in front of you, out of what each verifier actually\nexecuted the last time `balladeer touch-map` measured it. Both commands run on this machine and\nsend Balladeer nothing, so you may name any path in the change.\n\nAn answer marked stale was measured against a verifier that has changed since, so read it as the\nlast thing anybody measured rather than as fact, and offer to run `balladeer touch-map` again.\nWhere there is no map, where it does not name your paths, or where it reports a promise it could not\nmeasure, fall back to the paths on the index rows. The map narrows which promises are worth\nfetching. It never widens what you may read: the catalog is still never enumerated, and the fetch\nbudget is unchanged.\n\nWhen a retrieval receipt asks why you read a row, the answer for one the map named is `touch`.\n\nFetch by id, and only for an id the person gave you or an index row whose paths match the change in\nfront of you. Never enumerate the catalog. Never chain one fetch into the next to see the whole of\nsomething: when the rows do not settle it, narrow the filter rather than expanding another promise.\n\n### When to offer, and what a yes is worth\n\nNotice durable customer behavior during ordinary work. Offer to preserve a concrete behavior\nbeside useful work, without blocking implementation. File nothing until the person explicitly\nasks you to record it or accepts a scoped capture offer. A factual answer or permission to build\nalone is not permission to record. A no ends that offer; do not raise it again in this conversation.\n\nDo not offer while the user is comparing options or exploring without a decision. If they later\nchoose a concrete behavior, you may offer to capture it even though the conversation began as\nexploration. Do not offer new promises for pure refactors or cosmetic changes. During an active\nproduction incident, prioritize recovery and defer capture until recovery. Ordinary bug fixing\nis not automatically an active production incident.\n\nFor clear feature intent, an offer before implementation can make the promise a target for the\nwork. For a normal bug fix, offer alongside the completed fix and checks. Neither requires a\nmerge or another human closing reply. If the user is away, one nonblocking offer can remain in\nyour completion message for their return; do not file or wait for an answer.\n\nUse available context to state a specific behavior. A precise capture offer can confirm your\ninterpretation and obtain permission to record in one yes. Ask a separate work question only\nwhen a consequential choice remains that a clear, scoped offer cannot resolve. An unanswered\nearlier question is not itself a reason to ask again. The server supplies current detailed guidance.\n\n### Two promises Balladeer cannot keep\n\nA promise about speed needs three things before it is a promise at all: a number, a percentile, and\nwhere it is measured. \"The quote page answers in under one second at p95, measured in production at\npeak load\" is one Balladeer can keep. \"The quote page has to be fast\" is not. Say this, and ask for\nthe part that is missing rather than filing it:\n\n\"I can keep that once it has a number, a percentile, and a place it is measured. Without those it is\na wish, not a promise.\"\n\nBalladeer refuses one without all three and names which of them is missing. When all three are\nthere, write the measurement method into the promise, and tell them plainly that it reads agreed and\nunprotected until a test that actually measures it exists.\n\nA promise about how the team works is not something the software does, so no check can ever catch\nit. \"We must provide a low-friction capture experience\" is one of these. File nothing and say:\n\n\"That is a promise about how we work, not something the software does that a check can fail.\nBalladeer only keeps promises a check can catch. If a customer would notice something when this\nslips, say that and I will keep that instead.\"\n\nThen take the customer-visible half if they give you one, and file that instead.\n\nUse the installed `balladeer` command after setup reports CLI readiness. If it is missing from\nPATH (including an older 1.0.4 setup), use `npx -y balladeer@latest <command>` for that invocation\nand read the current /agent instructions for installation or repair. Do not claim that an older\nrepository's instructions were refreshed. CLI availability does not prove that this coding host\nloaded the native MCP tools or that a credential is authorized. The optional session stamp below\nis separate from all three.\n\nRun `balladeer session` when you start work here and pass the id it prints to every promise read\nyou make, as `session`. It is the same id for the whole of one piece of work, and it costs nothing:\na read without it is answered exactly the same way.\n\nIf local file permissions refuse that session write, no session stamp was saved. Your saved\nconnection is unchanged; this does not prove its current server authorization. Continue\nalready-authorized MCP reads, coding and explicitly requested capture without the optional\n`session` field. Do not invent an ID, add a session trailer, or record an unsaved stamp. Do not\nbroaden filesystem access or move credentials to retry this write. A missing credential or server\nauthorization refusal is different: follow that refusal. Capture still needs the person's request\nor accepted offer, and human meaning approval is unchanged.\n\nIf a session ID was saved, near the end of the work call `mark_promise_used` with the ids you actually cited\nor acted on. Naming none is a fine answer. It is the only way anybody finds out which rows were\nworth sending you, because reading a promise and then ignoring it is not the same as using it.\n\nIf a session ID was saved, write `Balladeer-Session: <the id>` into the commit message or pull-request body you produce,\nand run `balladeer session --record` once the commit exists. That is what lets a check that goes red\nnext week be read back against what Balladeer told you before you started. Your commit message never\nleaves your machine: only the session id and the commit SHA are sent.\n\n### When somebody asks you to protect a behavior\n\nA request to build a behavior is not permission to record it. An explicit request to preserve it\nor acceptance of a specific capture offer permits one pending proposal for that behavior, not\nother behaviors you notice. A factual answer alone does not authorize recording.\n\nUse available conversation and repository context before asking questions. A precise capture\noffer can state your interpretation and obtain permission to record it in one yes. Ask separately\nonly when a consequential choice remains that the scoped offer cannot resolve. Do not ask for\nknown facts, repeat a question resolved by later context or acceptance, or require a formal\nmust-not sentence from the user. Preserve their actual words separately from your interpretation.\nIf no specific commitment is possible yet, continue the authorized work without filing it.\n\nUse relevant existing promises already retrieved, or the bounded repository/path lookup, to notice\nconcrete conflicts before writing. If the same situation would require incompatible outcomes, show\nthe two commitments and ask which behavior they intend. Revising or superseding agreed meaning\nstill requires its named human owner. There is no automatic catalog-conflict gate or stored question\nbacklog in Balladeer. Unrelated uncertainties need not delay capture. No questions are required when\nthe commitment is already clear.\n\nPreserve the person's actual words. Every failure they named belongs in the failing examples.\nYou may derive concrete cases within the behavior they requested or confirmed in a precise\ncapture offer; they need not dictate every example. Trace each case to the actual request and\nconfirmed scope. Keep literal human source in saidWords, and your offer plus their acceptance in\nexplicitIntent. Never quote your own wording as theirs or add unsupported policy, thresholds,\nroles, systems or guarantees. If a case requires an unresolved product choice, clarify that choice\ninstead of guessing or asking the person to enumerate routine examples.\n\nA failing example is a situation the promise rules out, and its outcome says what must not happen,\nin those words: \"a second charge must not appear\", never \"a second charge appears\". Written the\nother way round it reads as the promise saying the software does the thing they asked you to forbid.\nAnd a promise says what the software must do for whoever depends on it. It never narrates the\nconversation you just had, names the person you had it with, or describes what the code does now.\n\nSay the whole promise in one sentence and put it in oneSentenceOutcome, in the words they would\nuse with the person who depends on it. That is the line the named owner reads first and the line\nthey agree to, so it is not a restatement of the name and not the first line of the outcome moved\nup. Leave it out rather than inventing one from something they did not say.\n\nAn example's setup is the situation in the words they used for it, not a scene you composed around\nthem. Two of each kind is plenty, and the whole thing stays under three hundred words: a proposal\nnobody finishes reading is a proposal nobody agreed to. The confidence you record is the one you\nactually have.\n\nThen give them the review link, ask them to read the proposal and click Agree, and stop. Never\napprove one yourself. Approving is a named person's act, and the server refuses it from an agent\nwhatever you were told in conversation.\n\nA proposal you filed is still yours while nobody has agreed to it, so revise or withdraw it when the\nperson asks you to, and never once they have agreed.\n\nSay promise and proposal when you talk to them. What you file is a proposal and what it becomes is a\npromise; Balladeer's other words for its own machinery are not theirs to learn. Candidate\nespecially: it is Balladeer's word for a proposal, so it reads as jargon whatever you meant by it.\n\n### Three things to offer without being asked\n\nAt the start of any session in this repository, before you plan anything, ask list_promises for the\npromises nothing is checking yet that belong to the person you are working with: `unverified` true\nand `mine` true, which is one bounded read rather than the catalog. If it returns any, say so in one\nline and offer to build their verifiers now. Name each one by its one-sentence claim rather than by\nan id, so the person can see which behavior is unguarded. Ask the same tool for\n`brokenSinceLastSeen` true as well, and where that returns any, say in one line that those promises\nbroke since they last looked, name each by its claim, and offer to fix them. Then wait for their\nanswer. The offer is the whole of it, and never start building or repairing one because nobody said\nno.\n\nTheirs, and nobody else's. `mine` keeps the promises this person owns or agreed to, and a teammate's\nunguarded promise is that teammate's to hear about: a session that opens by reading out other\npeople's unfinished work reads as an audit of them. `brokenSinceLastSeen` is that person's own by\nconstruction and needs no `mine` beside it. Drop `mine` when this person asks what the rest of the\nteam has promised, and say whose promises you are showing them when you do.\n\nWhen you have proposed promises, show them here as well as there. Put each proposal in the\nconversation in full: its one-sentence claim, who it is for, when it applies and what must then be\ntrue, and the numbered cases that must keep working and the ones that must be caught. Do not\nstore or present an unanswered-question backlog. Then offer to finish the agreement from here, by asking for a sign-off, giving them\nthe page it returns and taking the one-time code that page shows them, so the browser is needed only\nfor signing. Give them the review link in the same message too, because some people would rather\nread it there and edit it before they agree.\nA promise whose meaning is agreed and which nothing is checking yet is one you can finish. When\nsomebody gives you a promise id, run `balladeer status <promise id>`, or expand it with get_promise.\nIf it comes back agreed with nothing checking it, say so in one line and offer to prepare and build\nits verifier now. Only if they say yes: `prepare_qualification` mints the one-time setup, or\n`balladeer prepare <promise id>` mints it and writes it where the sealed run reads it. You need no\nsign-off for that and there is no code to ask anybody for, because agreeing the meaning was their\nact and building the check that proves it is yours. Then build the verifier, seal it, push, and tell\nthem protection starts by itself when that run qualifies. The offer is the whole of it: never\nprepare one because nobody said no.\n\n### When somebody says \"tell me about\" one\n\nAn id is how a person points at something here. Expand a promise id with get_promise and a proposal\nid with get_proposal. Describe who it is for, when it applies, the behavior and the concrete cases.\nA proposal awaits its named owner's agreement; a promise is agreed and may still be unprotected.\nPreviously recorded answers are historical reasoning, not a new interview or an approval.\nIf the person wants a change, clarify the changed commitment before writing it. Preserve all other\nmeaning and cases. An agreed promise changes only through a revision its named owner approves.\n\n### Files that are sealed, and the one reason to edit one\n\nEvery file under .continuity/promises/ is sealed. The promise that owns that directory records the\nexact bytes of each file in it, so editing one, adding one there, renaming one or deleting one\nbreaks the seal. A promise whose seal is broken stops being checked, and it stays that way until a\nnamed person qualifies it again, which is their afternoon rather than your commit. Nothing in there\nis ordinary source: keep it out of refactors, formatting runs and dependency upgrades.\n\nFind out which directories are sealed before you plan an edit, not after. balladeer status lists\nthem, and list_promises names a promise's sealed directory on its row once a verifier is bound to\nit. Then, before you push, run balladeer check-seals. It prints nothing and exits zero when your\nchange touches no seal, and names the promise, its owner and its page when your change would break\none.\n\nThe one reason to edit a sealed file is to repair a verifier that can no longer run: something it\nimports moved, or the language it is written in changed under it. Never edit one to make a failing\ncheck pass. A check going red is the promise doing its job, and the repair for that belongs in the\nbehavior it protects. A repair is not finished until the promise is sealed again with the runner\nthis repository is pinned to. get_promise_setup carries that exact seal command, and\nballadeer check-seals prints it beside any promise it names.\n\n### The rest of a promise's life\nWhen a promise is obsolete, finished, deliberately off for a while, or owned by the wrong person,\npropose the change and hand them the promise page. Deciding is theirs.\n\nYou can finish one of those acts here, and only one way. Ask for a sign-off with\nrequest_owner_signoff, give them the page it returns, and ask for the one-time code that page shows\nthem. Then call the act's own tool with that code and their own words. Never call one on your own\ninitiative, never on a general approval of some earlier act, and never ask for a code you were not\ngiven: a refusal is the person's to resolve, not yours to retry. Balladeer records them as the\nperson who acted and you as the messenger.\n\nReport the promise's state exactly as Balladeer reported it: proposed, agreed, or protected, never\none in place of another.\n\n### Where your team watches this\n\nBalladeer is a web app as well as these tools, at the address setup printed. Its catalog lists every\npromise with who owns it and whether anything is checking it, and each promise has a page of its own\nshowing what this team agreed the software must do and then every run that has checked it since,\nnewest first, with the commit each one checked. Whenever there is a link to give, give the link\nrather than a summary of it: the page says what you would have said, and it stays true after this\nconversation has ended.\n\nBalladeer also has a Slack app, which a workspace administrator installs from workspace settings.\nOnce it is installed, whoever owns a promise gets a direct message when theirs goes live and when a\nrun on the default branch breaks it. Until somebody installs it, nothing is sent anywhere, so say it\nis available rather than saying they will be told.\n\n### Questions people ask\n\nAnswer these when they come up. Where you do not know, say so and point at the address setup\nprinted: a confident wrong answer about what a vendor can see is worse than no answer.\n\nWhat it does: it holds the behaviors this team has agreed the software must keep, and reports\nwhether each one is still being kept, from this repository's own tests running in its own CI.\n\nWhat it sees: the text of each promise somebody approves, this repository's numeric ids and the name\nof its default branch, and from CI the pass or fail outcome, the commit checked, and content hashes.\nNever the code, the tests, the fixtures, the logs, the prompts, or the transcripts.\n\nWhat stopping costs: nothing that matters to their tests. The verifier package, its fixtures and the\nworkflow file are theirs, in their repository, running in their CI, and disconnecting changes none\nof them. An administrator can download everything Balladeer holds at any time from workspace\nsettings, and disconnecting hands them that same download in the response that ends access.\n\nWho can approve one: the named person who owns it, in their own browser. Not an administrator on\ntheir behalf, and never you.\n\nWhether it blocks a merge: no. The check is advisory on Balladeer's side, and their own branch\nprotection is what decides whether a failing check stops anything.\n\nWho can invite people and change setup: a workspace administrator. A contributor can read the\nworkspace and propose promises, and a viewer can read it. If somebody asks you to add a teammate,\ninvite_teammate returns the page an administrator sends the invitation from, with the address filled\nin for them to read. The tool sends nothing itself: an administrator presses Send.";
 /**
  * How an agent turns a repository that has just been connected into a catalog a
  * person can read. Setup's last step prints it, and the control plane's `/agent`
@@ -221,4 +221,6 @@ export declare const CONVENTIONS_BLOCK = "## Balladeer promises\n\nBefore planni
  * the agent not to read them, which is the visible half of the same seam:
  * nothing quietly starts doing it.
  */
-export declare const DISCOVERY_PLAYBOOK = "## Discover this repository's promises\n\nThis repository is connected and holds no promises yet. Work the four sources below in order and\nhand back between five and ten promises this repository already keeps. Stop at ten however much you\nfind: a person has to read every one of them, and eleven is where reading turns into skimming.\n\n1. The repository's own tests. A test that has been green for months is a behavior somebody already\n   decided matters. Read the test names and the assertions rather than the implementation.\n2. Merged pull requests of the last 90 days. Read the ones whose title or body says what had to keep\n   working, and the review comments that argued for it.\n3. Guarantee sentences in the documentation. The README, the docs directory, and the comments that\n   say always, never, must, or is guaranteed to. Those sentences are promises somebody already wrote\n   down in prose.\n4. Incidents and reverts. A revert commit, a hotfix, a postmortem note. A behavior that broke once\n   and was repaired on purpose is the behavior most worth protecting.\n\nDo not read the person's local agent transcripts, and do not offer to. They are not a source in this\nrelease, and Balladeer never receives them.\n\nFor each promise you propose:\n\n- One promise per behavior. Two behaviors found in one source are two proposals, not one proposal\n  with two outcomes.\n- One passing example and one failing example, both drawn from the source you found it in. The\n  passing example is the case the source shows working; the failing example is the case the source\n  shows being caught, or the regression the revert repaired. Write both in the source's own words\n  rather than in words of your own.\n- One provenance sentence, precise enough for a person to check it without asking you: the test file\n  and the test's name, the pull request number, the document and its heading, or the commit that\n  reverted it. Put that sentence first in explicitIntent.\n- Never propose a promise this repository does not keep. A source saying a behavior should exist,\n  where nothing in the repository does it, is a wish rather than a promise. Leave it out, and tell\n  the person you left it out.\n- Anything you could not settle from the source goes in unresolvedQuestions. Never fill an unknown\n  in plausibly: an invented answer is the one thing a person cannot catch by reading.\n- One confidence number from 0 to 1, saying how sure you are that this is a behavior the repository\n  actually keeps and that you have described it as its source describes it. Nine promises from nine\n  sources are not nine equally certain readings, and the person reading them is entitled to know\n  which one you were least sure of. Never write 1 to get past the check.\n- One wrongOutcome sentence: what going wrong looks like, said as a must-not, in the source's own\n  words where it has them. \"A second payment must not go out.\" \"The buyer must not see a generic\n  error.\" Where no sentence of that shape can be written, no check with a known-bad control can be\n  written either, so leave the promise out rather than filing one nothing could ever fail.\n- One leastSure sentence, optional, naming the single thing you are least sure of and what you did\n  about it. The person reads that instead of the number.\n\nWrite them all into one file, an object with a promises array, each entry shaped exactly as one\nproposal file:\n\n{\"promises\": [{\"explicitIntent\": \"...\", \"teachBack\": {\"confidence\": 0.9, \"wrongOutcome\": \"...\", \"meaning\": {\"title\": \"...\"}}}]}\n\nAn entry carries explicitIntent and teachBack, and inside teachBack only meaning, confidence,\nwrongOutcome, leastSure, unresolvedQuestions, and proposedOwnerId. Anything else is refused on this\nmachine before the file leaves it, and one bad entry means not one of them is sent.\n\nEvery promise in the file is proposed as owned by whoever ran setup, and waits for that person. The\ncommand prints one link that opens all of them at once. Give the person that link and ask them to\nread each promise and click Agree. Nothing you can run agrees to one.\n\nFile the whole catalog in one go with the discover subcommand, naming that file:";
+export declare const DISCOVERY_PLAYBOOK = "## Discover this repository's promises\n\nThis repository is connected and holds no promises yet. Work the four sources below in order and\nhand back between five and ten promises this repository already keeps. Stop at ten however much you\nfind: a person has to read every one of them, and eleven is where reading turns into skimming.\n\n1. The repository's own tests. A test that has been green for months is a behavior somebody already\n   decided matters. Read the test names and the assertions rather than the implementation.\n2. Merged pull requests of the last 90 days. Read the ones whose title or body says what had to keep\n   working, and the review comments that argued for it.\n3. Guarantee sentences in the documentation. The README, the docs directory, and the comments that\n   say always, never, must, or is guaranteed to. Those sentences are promises somebody already wrote\n   down in prose.\n4. Incidents and reverts. A revert commit, a hotfix, a postmortem note. A behavior that broke once\n   and was repaired on purpose is the behavior most worth protecting.\n\nDo not read the person's local agent transcripts, and do not offer to. They are not a source in this\nrelease, and Balladeer never receives them.\n\nFor each promise you propose:\n\n- One promise per behavior. Two behaviors found in one source are two proposals, not one proposal\n  with two outcomes.\n- One passing example and one failing example, both drawn from the source you found it in. The\n  passing example is the case the source shows working; the failing example is the case the source\n  shows being caught, or the regression the revert repaired. Write both in the source's own words\n  rather than in words of your own.\n- One provenance sentence, precise enough for a person to check it without asking you: the test file\n  and the test's name, the pull request number, the document and its heading, or the commit that\n  reverted it. Put that sentence first in explicitIntent.\n- Never propose a promise this repository does not keep. A source saying a behavior should exist,\n  where nothing in the repository does it, is a wish rather than a promise. Leave it out, and tell\n  the person you left it out.\n- Before filing, ask the person about any missing fact that changes this commitment. Put their\n  actual answer in the meaning and cases. Never invent an answer or store an outstanding question.\n  Capture a narrower commitment only when they intend that boundary; do not demand exhaustive certainty.\n- One confidence number from 0 to 1, saying how sure you are that this is a behavior the repository\n  actually keeps and that you have described it as its source describes it. Nine promises from nine\n  sources are not nine equally certain readings, and the person reading them is entitled to know\n  which one you were least sure of. Never write 1 to get past the check.\n- One wrongOutcome sentence: what going wrong looks like, said as a must-not, in the source's own\n  words where it has them. \"A second payment must not go out.\" \"The buyer must not see a generic\n  error.\" Where no sentence of that shape can be written, no check with a known-bad control can be\n  written either, so leave the promise out rather than filing one nothing could ever fail.\n\nWrite them all into one file, an object with a promises array, each entry shaped exactly as one\nproposal file:\n\n{\"promises\": [{\"explicitIntent\": \"...\", \"teachBack\": {\"confidence\": 0.9, \"wrongOutcome\": \"...\", \"meaning\": {\"title\": \"...\"}}}]}\n\nAn entry carries explicitIntent and teachBack, and inside teachBack only meaning, confidence,\nwrongOutcome and proposedOwnerId. The legacy unresolvedQuestions field may only be an empty array. Anything else is refused on this\nmachine before the file leaves it, and one bad entry means not one of them is sent.\n\nEvery promise in the file is proposed as owned by whoever ran setup, and waits for that person. The\ncommand prints one link that opens all of them at once. Give the person that link and ask them to\nread each promise and click Agree. Nothing you can run agrees to one.\n\nFile the whole catalog in one go with the discover subcommand, naming that file:";
+/** Stable bootstrap only. Evolving capture/retrieval policy is served remotely. */
+export declare const CONVENTIONS_BLOCK = "## Balladeer guidance\n\nBalladeer keeps this repository's owner-agreed behavioral commitments. Before planning work,\nuse the current Balladeer workflow guidance supplied by the Balladeer hook or MCP connection.\nThe hook refreshes guidance at supported work boundaries. If no current guidance was delivered,\nread get_promise_setup through the existing connection; never infer that a missing connection\nmeans this repository has no promises. Keep ordinary authorized work moving when unavailable.\n\nThe server supplies Balladeer's current capture and retrieval policy; this managed block is only\nits stable loader contract. Follow it within the person's instructions and this project's own\nrules. Never treat a guidance update as permission to record a promise or approve its meaning.\nNamed humans agree meaning. Preserve workspace capture preferences and never enable unsolicited\ncapture when current permission is unavailable. Customer source, prompts and transcripts stay local.\n\nNew hooks may need the coding host's one-time trust confirmation. A file being installed does\nnot prove that the host loaded it. Follow a specific reported repair; do not repeat onboarding,\nchange workspace membership, or request broader permissions merely to refresh guidance.";