@sema-agent/core 5.57.0 → 5.59.0

package/dist/orchestration/workflow-script-store.d.ts

@@ -24,13 +24,13 @@ export interface NamedWorkflowResolution {
      *  the run receives the merged VALUE; nothing re-queries the registry after launch). */
     defaultArgs?: unknown;
     /**
-     * 团队通道 [426] CORE-1 — the top-level key a BARE STRING call-time arg normalizes into, so the "裸 string =
+     * CORE-1 — the top-level key a BARE STRING call-time arg normalizes into, so the "裸 string =
      * <key>" ergonomic entry (published by the built-in `discussion` script: a bare string args IS the
      * topic) composes with a registered object `defaultArgs` instead of colliding with it. When a `{name}` call
      * passes a raw string AND this resolution carries an object `defaultArgs`, the tool wraps the string as
      * `{ [stringArgKey]: <string> }` BEFORE the object merge (see {@link normalizeStringArg} / the run-workflow
      * tool's resolve path). Defaults to `"topic"` (the built-in ergonomic contract). Ignored when `defaultArgs`
-     * is not a plain object (a bare string then reaches the script verbatim — pre-[426] behavior preserved). */
+     * is not a plain object (a bare string then reaches the script verbatim — pre- behavior preserved). */
     stringArgKey?: string;
 }
 /**
@@ -44,7 +44,7 @@ export interface NamedWorkflowListing {
     whenToUse?: string;
 }
 export interface WorkflowScriptStore {
-    /** γ 批 B-4 (codex γ-G3) — the CONFORMANCE MARKER for the scope-partitioned contract. Structural
+    /** B-4 — the CONFORMANCE MARKER for the scope-partitioned contract. Structural
      *  typing would otherwise let a pre-partition adapter (`load(path)`, `persist(runId, script)`)
      *  remain assignable — fewer-parameter functions are compatible in TypeScript — and silently
      *  ignore the scope argument, serving cross-tenant reads while the tool presents the operation as
@@ -53,20 +53,20 @@ export interface WorkflowScriptStore {
     readonly scopePartitioned: true;
     /** Persist THIS invocation's resolved script, keyed by its runId. Returns the persisted path (what the tool
      *  reports back to the model). Failures should throw — the tool treats persistence as best-effort.
-     *  γ 批 B-4 (BREAKING): `scope` PARTITIONS per-run scripts — the CC anchor is a per-session directory,
+     *  B-4 (BREAKING): `scope` PARTITIONS per-run scripts — the CC anchor is a per-session directory,
      *  and the port had dropped the axis (one flat directory let a model-supplied scriptPath read another
      *  scope's script). Implementations key storage by scope (the file store uses per-scope subdirs). */
     persist(runId: string, script: string, scope: string): Promise<string> | string;
     /** Read a previously persisted script back. MUST refuse paths outside the store (the argument is
      *  model-supplied — containment is the store's contract, not the tool's).
-     *  γ 批 B-4 (BREAKING): `scope` bounds the read to the CALLER's partition — a path pointing into
+     *  B-4 (BREAKING): `scope` bounds the read to the CALLER's partition — a path pointing into
      *  another scope's partition must be refused exactly like a path outside the store. */
     load(scriptPath: string, scope: string): Promise<string> | string;
     /** Resolve a SAVED workflow name to its registration (undefined = unknown name). Optional — a deployment
      *  without a named registry simply omits it. RB-482 #9 (ruled 2026-08-03): ONE return form — a
      *  {@link NamedWorkflowResolution} ({ script, defaultArgs? }); the legacy bare-string return is retired. A
      *  deployment entry of the SAME NAME as a built-in workflow SHADOWS the built-in (design/140 §6 1c).
-     *  γ 批 RULING: deliberately NO scope axis here — saved names are a DEPLOYMENT-level registry (the
+     *  RULING: deliberately NO scope axis here — saved names are a DEPLOYMENT-level registry (the
      *  built-ins' tier), shared across scopes like agent definitions; a multi-tenant deployment that wants
      *  per-tenant registries mounts per-tenant store instances.
      *  CONTRACT (stated 2026-08-16, C-R14): this is a STABLE, SIDE-EFFECT-FREE lookup. Resolving ONE call
@@ -96,7 +96,7 @@ export interface WorkflowScriptStore {
  */
 export declare function mergeWorkflowArgs(callArgs: unknown, defaultArgs: unknown): unknown;
 /**
- * 团队通道 [426] CORE-1 — NORMALIZE a bare-string call-time arg into `{ [key]: <string> }` so the published
+ * CORE-1 — NORMALIZE a bare-string call-time arg into `{ [key]: <string> }` so the published
  * "裸 string = <key>" ergonomic entry (built-in `discussion`: bare string args IS the topic) COMPOSES
  * with a registered object `defaultArgs` instead of colliding with it.
  *
@@ -106,7 +106,7 @@ export declare function mergeWorkflowArgs(callArgs: unknown, defaultArgs: unknow
  * form, and the collab template quietly ran as a generic advocate/skeptic. Wrapping the string here lets the
  * subsequent object merge preserve the defaults AND honor the topic.
  *
- * Applied ONLY when BOTH hold (otherwise return `callArgs` untouched — pre-[426] behavior byte-preserved):
+ * Applied ONLY when BOTH hold (otherwise return `callArgs` untouched — pre- behavior byte-preserved):
  *  - `callArgs` is a string (the ergonomic form), AND
  *  - `defaultArgs` is a PLAIN OBJECT (there ARE object defaults to merge under; with no/scalar defaults a bare
  *    string must still reach the script verbatim — the built-in's own `raw === "string"` fallback handles it).
@@ -116,7 +116,7 @@ export declare function mergeWorkflowArgs(callArgs: unknown, defaultArgs: unknow
 export declare function normalizeStringArg(callArgs: unknown, defaultArgs: unknown, key?: string): unknown;
 /**
  * File-backed {@link WorkflowScriptStore}: per-run scripts land as `<dir>/<scopeDir>/<runId>.js`
- * (γ 批 B-4: per-scope partition — the CC per-session-dir posture restored on the tenant axis);
+ * (B-4: per-scope partition — the CC per-session-dir posture restored on the tenant axis);
  * `resolveName` reads `<dir>/<name>.js` at the ROOT (the deployment-level saved-name tier, see the
  * interface RULING — deliberately outside every scope partition).
  */

package/dist/orchestration/workflow-size-guideline.d.ts

@@ -3,7 +3,7 @@
  * (small/medium/large/unrestricted), injected into the Workflow tool's prompt/description. It is
  * guidance, NOT a cap — the hard ceiling stays `WorkflowLimits.maxAgents`.
  *
- * RB-339 (2026-07-30, clay A 案) — REBASELINED on CC 2.1.220 (语料 ../cc-decoded/pretty220.js). The
+ * RB-339 (2026-07-30, A 案) — REBASELINED on CC 2.1.220 (语料 ../cc-decoded/pretty220.js). The
  * module was anchored to 2.1.206 and had drifted on four points; all four are corrected here and the
  * old "verbatim" claims (which were not true of the two sentence builders) are replaced with what
  * each function actually is:

package/dist/orchestration/workflow-types.d.ts

@@ -56,7 +56,7 @@ export interface WorkflowAgentRun {
      *  CC-style "last N of M tool calls"; M is `toolCalls`). Structural only (name/phase/ids), no args/output. */
     activity?: ToolActivity[];
     status: WorkflowItemStatus;
-    /** [1238](B) — the failed task's machine code + bounded human message, surfaced ON THE RECORD
+    /** The failed task's machine code + bounded human message, surfaced ON THE RECORD
      *  (runs.jsonl / monitor rows / agent_end) so a dead agent is diagnosable without re-running.
      *  Previously only the script's return value carried them and every display face showed "". */
     errorCode?: string;
@@ -95,7 +95,7 @@ export interface WorkflowAgentRun {
      *  (`fork(sessionId)→runTask`, or `runTask({sessionId})`) instead of a fresh re-run. An opaque id (not
      *  content) → scope-gated via `getWorkflowRun`, no redaction needed. Absent for a stub run that minted none. */
     sessionId?: string;
-    /** RB-393① (黑板 [2107]②/[2113]) — the WORKTREE directory this agent ran in, present ONLY for an
+    /** RB-393① — the WORKTREE directory this agent ran in, present ONLY for an
      *  `isolation: "worktree"` agent whose worktree the engine actually minted (reported by the runner's
      *  workspace-observation seam and folded on while the agent is still RUNNING, so an interrupted run's
      *  recovery path has the coordinate instead of enumerating the worktrees directory and guessing). ABSENCE
@@ -177,14 +177,14 @@ export interface WorkflowRun {
      *  `read_tool_result` ref — previously the `…[+N chars]` tail dead-ended (no retrieval path; models tried
      *  the runId as a ref and hit the store-miss message). Display/notify surfaces keep using `result`. */
     resultFull?: string;
-    /** P1-3(黑板 [1920]/[1921]/[1924]/[1925]) — the cross-channel completion correlation id, minted
+    /** The cross-channel completion correlation id, minted
      *  fill-once at this run's terminal transition (see {@link "../core/task-registry.js".UnifiedTaskOutput.completionId}
      *  for the shared cross-lane contract). Persisted alongside `status`/`endedAt` so a store round-trip
      *  (restart / crash recovery) replays the exact same id — there is no second mint point downstream of
      *  this field ever being set. Absent while `status === "running"`, or on a run recorded by an older
      *  engine version. */
     completionId?: string;
-    /** RB-243 ([1937]): what this run's `resumeFromRunId` actually yielded — ADDITIVE observation (same
+    /** RB-243: what this run's `resumeFromRunId` actually yielded — ADDITIVE observation (same
      *  contract as {@link agentFailures}: never a gate input; absent on non-resume runs, on runs recorded by
      *  older engines, and on a column-mapped store that doesn't project it). Previously a resume whose journal
      *  loaded ZERO entries (unknown/pruned runId, cross-scope, unreadable record) re-ran everything live with
@@ -198,7 +198,7 @@ export interface WorkflowRun {
         divergedAtOrdinal?: number;
         divergedReason?: string;
     };
-    /** RB-243 ([1937]): how many agent results were NOT journaled because they exceeded the per-entry size
+    /** RB-243: how many agent results were NOT journaled because they exceeded the per-entry size
      *  cap ({@link MAX_JOURNAL_RESULT_BYTES}) — each skip also logs and journals a tombstone. Additive
      *  observation; absent when 0. */
     journalSkips?: number;

package/dist/orchestration/workflow.d.ts

@@ -59,7 +59,7 @@ export declare function workflowAgentCallKey(ordinal: number, spec: TaskSpec, op
     isolation?: "worktree";
 }): string;
 /**
- * RB-394 (黑板 [2107]③) — runtime rejection of an unsupported `isolation` value at the workflow spawn
+ * RB-394 — runtime rejection of an unsupported `isolation` value at the workflow spawn
  * boundary. The TYPE (`isolation?: "worktree"`) only binds TS callers: a workflow script is plain JS at
  * runtime, so a value like `"remote"` previously sailed through every `=== "worktree"` consumption gate
  * as a truthy non-match — the trusted internals channel carried it verbatim, prepareTask's fail-closed
@@ -282,17 +282,17 @@ export interface RunWorkflowOptions {
     /** The originating session id — recorded on the {@link WorkflowRun}(same rationale as
      *  sourceTaskId: live notify carries it, recovery otherwise can't). */
     originatingSessionId?: string;
-    /** δ 批 [1498]⑦ — the ROOT host session of the delegation tree (the run-workflow tool passes
+    /** the ROOT host session of the delegation tree (the run-workflow tool passes
      *  `ctx.rootSessionId ?? originatingSessionId`); rides the wa* observer frames so a recovery face
      *  groups workflow-agent rows under the root host session too. */
     rootSessionId?: string;
-    /** design/149 ([1422]③ 裁 a) — the PROCESS-level child observer (same seam as
+    /** design/149 — the PROCESS-level child observer (same seam as
      *  {@link import("../core/types.js").RunnerDeps.onBackgroundChildEvent}). When set, every workflow
      *  agent emits spawn/tick/terminal {@link import("../core/types.js").BackgroundChildEvent} frames with a
      *  synthetic `wa*` row key (runId+callKey hash — stable across resume replays), owner/parentTaskId = the
      *  workflow's own task id (the fleet row nests under the w* row), sessionScoped false. This lane is
      *  process-anchored — a host run that settles BEFORE the workflow finishes does not mute it (the
-     *  run-leg uuid tick lane's settledLeg freeze, the [1422]③ case). Swallow-guarded.
+     *  run-leg uuid tick lane's settledLeg freeze). Swallow-guarded.
      */
     onBackgroundChildEvent?: (event: import("../core/types.js").BackgroundChildEvent) => void;
     /** design/140 §6 1a — the merged effective args snapshot recorded on the {@link WorkflowRun} (the
@@ -341,7 +341,7 @@ export interface RunWorkflowOptions {
      * `journalStore` WITHOUT `resumeFromRunId` just records (so a future run can resume from THIS run). Replayed
      * agents accumulate into `run.stats` (total work) but NOT into `ctx.budget.spent()` (live spend only — a resume
      * is not re-charged for cached work). NOT-REPLAYED (they force divergence so the suffix runs live): `ctx.agentStream`
-     * (a finished result can't be steered — RECORDED since [1422]② for the journal read-face, never replayed) and `ctx.pipeline` (latency-dependent ordinals aren't deterministic —
+     * (a finished result can't be steered — RECORDED for the journal read-face, never replayed) and `ctx.pipeline` (latency-dependent ordinals aren't deterministic —
      * a CORE-7.1 follow-on adds stage-scoped deterministic keys). Sequential + `parallel(direct thunks)` replay.
      */
     journalStore?: WorkflowJournalStore;
@@ -369,18 +369,18 @@ export interface RunWorkflowOptions {
      *  spec) so a root's per-run posture override governs its workflow children too. Set by the
      *  `run_workflow` tool wiring from `ToolExecuteContext.interactionPosture`. */
     interactionPosture?: "interactive" | "headless";
-    /** [1238](A) — call-time getter for the HOST run's RESOLVED Model object. A spawned agent whose
+    /** Call-time getter for the HOST run's RESOLVED Model object. A spawned agent whose
      *  fold chain (script spec → agentType → governance baseline) produced NO model inherits the
      *  parent's full object — baseUrl/key routing included — instead of falling to a string/role
-     *  re-resolution that loses per-model routing (the clay 4/4-agents-404 incident: session model id
+     *  re-resolution that loses per-model routing (the 4/4-agents-404 incident: session model id
      *  re-resolved against the base gateway). Mirrors the subagent lane's `ctx.model` semantics. */
     defaultModel?: () => import("../internal/llm.js").Model | undefined;
-    /** [1258] v2 — the HOST's per-model auth hook, inherited into every spawned agent's spec (the
+    /** The HOST's per-model auth hook, inherited into every spawned agent's spec (the
      *  credential half of model inheritance; scripts can never set it — governance strips it — so
      *  this is always the host's). NOT call identity (auth, not behavior; a function, not data). */
     defaultGetApiKeyAndHeaders?: TaskSpec["getApiKeyAndHeaders"];
     /** design/148 S1 — the HOST run's adopted center artifact (trusted, threaded by the Workflow tool
-     *  from ctx): every spawned agent composes the same closure (codex F2a). */
+     *  from ctx): every spawned agent composes the same closure. */
     parentCenterArtifactDigest?: string;
     parentCenterSourceRevision?: string;
     /** The launching run's display sink (`RunInternals.onForwardEvent` behind the runner's ctx wrapper:
@@ -455,7 +455,7 @@ export declare const WORKFLOW_AGENT_MAX_RETRIES = 5;
  *  degraded response (a flat sleep, NOT exponential backoff — and only on the FIRST attempt's result). */
 export declare const WORKFLOW_AGENT_THROTTLE_BACKOFF_MS = 45000;
 /**
- * RB-355 (codex 异源复审, 2026-07-29) — the cap on how long the TERMINAL boundary waits on the resume-claim
+ * RB-355 (2026-07-29) — the cap on how long the TERMINAL boundary waits on the resume-claim
  * store (the admission verdict, then the release). Both awaits sit in the run's `finally`, i.e. AFTER the
  * outcome is already decided: an unbounded wait there means a store implementation that hangs (a wedged
  * connection pool, a lost network write, a promise that simply never settles) leaves the run's `done` promise

package/dist/prompt-assembly/artifact-store.d.ts

@@ -59,7 +59,7 @@ export interface PromptArtifactSource {
     } | undefined;
     /** Resolve a PINNED digest (resume path). Undefined = unavailable — the caller fails loud. */
     get(artifactDigest: string): Promise<PromptEpochArtifact | undefined>;
-    /** RB-31 codex F1 — the tri-state the adoption boundary keys on: `"disabled"` = an EXPLICIT
+    /** RB-31 — the tri-state the adoption boundary keys on: `"disabled"` = an EXPLICIT
      *  validated revocation (applyDisabled) ⇒ pinned sessions roll back to bundled at the next
      *  compaction; `"active"` = a validated candidate is live; `"unavailable"` = no verified state
      *  (never-configured face, store-miss boot) ⇒ conservative restate — an outage must never strip

package/dist/prompt-assembly/artifact.d.ts

@@ -8,7 +8,7 @@ export interface CenterOverlaySection {
     /** Immutable rendered text (v1: fixed text, no renderer — center compiles before publishing). */
     text: string;
     /** REQUIRED on the center lane (unlike caller stableBlocks): sha256 of `text`. The center
-     *  publish path always mints it — it is the reconciliation anchor ([1050]② tiering). */
+     *  publish path always mints it — it is the reconciliation anchor (digest tiering). */
     contentHash: string;
 }
 export interface PromptCatalogSnapshot {

package/dist/prompt-assembly/assemble.d.ts

@@ -28,7 +28,7 @@ export interface AssembleInputs {
 }
 export interface AssembledPrompt {
     constitution: "core" | "replaced" | "provider-assembled";
-    /** design/148 S1 (codex F3): true ⇔ the supplied centerDeclarations were actually COMPILED into
+    /** design/148 S1: true ⇔ the supplied centerDeclarations were actually COMPILED into
      *  this prompt. The caller must never persist a center pin when this is false — a pin that claims
      *  an artifact the model never received is a durable lie (the assembled-identity pass-through path
      *  warns + false). */

package/dist/prompt-assembly/composer.d.ts

@@ -1,5 +1,5 @@
 /**
- * The prompt Composer — the single deterministic assembly path (campaign S1; protocol §6).
+ * The prompt Composer — the single deterministic assembly path (stage S1; protocol §6).
  *
  * compose() is a pure function of (pack, inputs): validate → admit → render → join. The legacy
  * date re-render seam (design/66 date_change) is expressed by re-running compose with a different
@@ -26,7 +26,7 @@ export declare function compose(pack: PromptPack, inputs: SectionRenderInputs):
 /** The implicit single-group layout — the legacy wire face (one system block, one cache span). */
 export declare const SINGLE_BLOCK_LAYOUT: SystemLayout;
 /**
- * Route a composed prompt's sections into PHYSICAL system blocks per the layout (campaign S4).
+ * Route a composed prompt's sections into PHYSICAL system blocks per the layout (stage S4).
  * Sections keep their emission order; groups partition by rank range (routing never reorders —
  * see types.ts header on slot interleaving). Empty groups are dropped. With SINGLE_BLOCK_LAYOUT
  * the result is one block whose text === composed.text (byte-identity, golden-pinned).

package/dist/prompt-assembly/epoch.d.ts

@@ -1,8 +1,8 @@
 import type { PromptPack } from "./types.js";
-/** [1068] — the provider-declared sections of THIS run's resolved prompt (the `origin:"provider"`
+/** the provider-declared sections of THIS run's resolved prompt (the `origin:"provider"`
  *  subset of the compiled IR), the declaration axis of the artifact identity.
  *
- *  codex F6 (S1 round 2): declaration TEXT deliberately does NOT enter this shape — the epoch
+ *  (S1 round 2): declaration TEXT deliberately does NOT enter this shape — the epoch
  *  digest is a deterministic, unsalted value persisted in exportable session entries, and session
  *  readers do not see system prompts; hashing private text into it would be a dictionary-preimage
  *  surface (the exact class the salted prompt-manifest hashes exist to prevent). Identity instead

package/dist/prompt-assembly/event-registry.d.ts

@@ -1,5 +1,5 @@
 /**
- * Event prompt registry (campaign S5; protocol §5.3) — the typed catalog of every runtime
+ * Event prompt registry (stage S5; protocol §5.3) — the typed catalog of every runtime
  * message-injection kind: its carrier, trust, dedupe semantics, byte budget and DEFAULT policy.
  * Mechanism/copy separation: the registry owns the MECHANISM row (who fires, how it dedupes,
  * where it rides); the render functions stay where they live (turn-attachments.ts / runtask.ts,

package/dist/prompt-assembly/explain.d.ts

@@ -31,13 +31,13 @@ export interface ExplainInput {
 /** Render a `prompt.assembled` manifest (+ optional epoch pin) as a readable report. */
 export declare function explainPromptAssembly(input: ExplainInput): string;
 /**
- * [1050]①d / [1051]③b — the CENTER-facing read-only description of the default pack: section
+ * the CENTER-facing read-only description of the default pack: section
  * metadata (id/slot/rank/ownership/locked) plus the default role-base TEXT (the append-mode
  * compile skeleton the web UI prepends to a user's "Role details"). Deliberately NO other section
- * texts (the [989] no-prompt-bodies observability line — structure yes, prose no; the role base is
+ * texts (the no-prompt-bodies observability line — structure yes, prose no; the role base is
  * the one deliberate exception: it is the public compile input of the append mode, and its text is
  * this open repo's DEFAULT_SYSTEM_PROMPT). Programmatic — a static copy in the web tier would
- * silently drift the moment core's default prompt changes ([1049]①d 禁静态拷贝).
+ * silently drift the moment core's default prompt changes (no static copies).
  */
 export interface DefaultPackDescription {
     packId: string;

package/dist/prompt-assembly/tool-catalog.d.ts

@@ -63,7 +63,7 @@ export declare function hasToolContract(tool: AgentTool): boolean;
 /** Manifest projection for the final mounted tool set (manifest v2 `tools`, protocol §5.4). */
 export declare function projectToolManifest(tools: AgentTool[], originOf?: (tool: AgentTool) => ToolOrigin): ToolManifestRow[];
 /**
- * RB-15 (campaign review): wire-identity collision audit over the FINAL mounted tool set.
+ * RB-15: wire-identity collision audit over the FINAL mounted tool set.
  * Rules (plan §6.2 tool row):
  *   - an ALIAS colliding with another tool's canonical name or alias = FATAL (silent misdispatch
  *     of durable replays would follow — never ship such a mount);

package/dist/prompt-assembly/turn-snapshot.d.ts

@@ -82,15 +82,15 @@ export interface TurnPromptSnapshot {
     /** sha256(canonical(elements)) — the ONE nine-element identity value. */
     cacheIdentity: string;
     lowering: LoweringRecord;
-    /** codex S3 F3 — invoked after EVERY refresh so the run loop can emit the changed identity
+    /** invoked after EVERY refresh so the run loop can emit the changed identity
      *  (`prompt.snapshot_changed` trace); traces must never keep claiming a superseded prefix. */
     onChange?: (snapshot: TurnPromptSnapshot) => void;
     /** Refresh the tool half (design/36 rematerialize follows the declared mid-run change). */
     refreshTools(toolWire: RawPrefixInputs["toolWire"]): void;
     /** Refresh the stable-system half (RB-31 adoption swap — pass the COMMITTED epoch digest so the
-     *  identity never mixes old-artifact/new-prompt, codex S3 F2). */
+     *  identity never mixes old-artifact/new-prompt). */
     refreshStableSystem(stableSystemText: string, artifactDigest?: string): void;
-    /** codex S3 F1 — request-policy element follows mid-run wire changes (finalize lanes flip the
+    /** request-policy element follows mid-run wire changes (finalize lanes flip the
      *  thinking level; a served-model swap re-namespaces the cache). */
     refreshRequestPolicy(p: {
         thinkingLevel?: string;
@@ -105,7 +105,7 @@ export interface TurnPromptSnapshot {
  *  the CLASSIFICATION stays total over everything callers hold, but only identity-class fields can
  *  reach the digest — enforced structurally (this function reads exactly the identity fields).
  *
- *  `promptHasher` (codex S3 F4): the digest applied to COMPOSED PROMPT TEXT — callers inject a
+ *  `promptHasher`: the digest applied to COMPOSED PROMPT TEXT — callers inject a
  *  KEYED/salted hasher (the run loop uses the per-process manifest salt): a fixed public prefix +
  *  short unknown suffix (an env fact, a memory note, a tenant string) makes an unsalted full-text
  *  sha ENUMERABLE, recreating exactly the disclosure the salted block hashes prevent. Consequence,

package/dist/prompt-assembly/types.d.ts

@@ -1,5 +1,5 @@
 /**
- * Prompt-assembly protocol — core IR types (campaign S1, docs/PROMPT-ASSEMBLY-EXECUTION-PLAN.md).
+ * Prompt-assembly protocol — core IR types (stage S1, docs/PROMPT-ASSEMBLY-EXECUTION-PLAN.md).
  *
  * Three orthogonal dimensions (protocol §3): semantic slot / physical carrier / render cadence +
  * cache class. These NEVER collapse into each other: a slot does not imply a carrier, and neither
@@ -19,7 +19,7 @@ export type PromptSlot = "wire-metadata" | "identity" | "security" | "harness" |
 export type PromptCarrier = "system.block" | "message.system" | "message.user-prefix" | "message.user-suffix" | "tool.native" | "tool.system-text" | "tool-result.prefix" | "tool-result.suffix" | "event.notification";
 /** When a section's content is (re)rendered (protocol §3.3). Distinct from artifact provenance. */
 export type PromptRenderCadence = "epoch" | "run" | "turn" | "event";
-/** Prefix-cache stability class (protocol §3.3). The leg-frozen date (design/66 → [915] A1) makes
+/** Prefix-cache stability class (protocol §3.3). The leg-frozen date (design/66 → A1) makes
  *  the environment tail `run`-cadence + `volatile`: stable within a leg, re-rendered per leg. */
 export type PromptCacheClass = "prefix-stable" | "epoch-stable" | "volatile" | "none";
 export type PromptOwner = "core" | "pack" | "deployment" | "extension" | "session";
@@ -27,7 +27,7 @@ export type PromptOwner = "core" | "pack" | "deployment" | "extension" | "sessio
  *  fenced/sanitized by the renderer that produced it (untrusted-inlet discipline). */
 export type PromptTrust = "locked" | "operator" | "external" | "user-derived";
 /**
- * Who may replace/suppress the section (protocol §5.2; M4 replaceAll-narrowing, clay 2026-07-16):
+ * Who may replace/suppress the section (protocol §5.2; M4 replaceAll-narrowing, 2026-07-16):
  * `locked` sections (security/harness/context mechanism truth) survive every provider shape,
  * including `replaceAll` providers.
  */
@@ -54,9 +54,9 @@ export interface PromptRuntimeFacts {
     withinTaskCompactionEnabled: boolean;
     supervisorEnabled: boolean;
     orchestrationEnabled: boolean;
-    /** 锚定回归 R2([1132]③):orchestration is active but the Workflow tool is DEFERRED — the mode
+    /** Orchestration is active but the Workflow tool is DEFERRED — the mode
      *  section serves the short pointer instead of the full how-to (cache-prefix parity with the
-     *  deferral itself). Only meaningful when orchestrationEnabled. OPTIONAL (codex F2: this
+     *  deferral itself). Only meaningful when orchestrationEnabled. OPTIONAL (this
      *  interface is a public export — absence reads as false, so existing constructors keep
      *  compiling across the upgrade). */
     orchestrationDeferred?: boolean;
@@ -64,7 +64,7 @@ export interface PromptRuntimeFacts {
      *  it (R3: system sections serve the lean form on "simple"). OPTIONAL (public export — absence
      *  reads as "simple", existing constructors keep compiling). */
     promptProfile?: "simple" | "classic";
-    /** R2 双形轴(clay 追加令):CC 2.1.212's fable-specific prompt variant gate — the b9e /
+    /** R2 双形轴(追加令):CC 2.1.212's fable-specific prompt variant gate — the b9e /
      *  `fable_5_mitigations` capability axis, ORTHOGONAL to simple/classic (CC gates them
      *  independently). True when the run's model is a fable-family id; R3 sections fork on it
      *  (autonomous-operation paragraph, fable_identity, tool_param_json). OPTIONAL — absence = false. */
@@ -80,7 +80,7 @@ export interface PromptRuntimeFacts {
      *  {@link teammateEnabled}): admits `core/mode.subagent-consent` and (RB-326) the delivery
      *  `core/mode.subagent-notes` — the two elements CC's `Von` assembles over any agent's own
      *  system prompt. A fork is excluded (it shares
-     *  the parent's own authority). OPTIONAL (codex F2 precedent: this interface is a public export —
+     *  the parent's own authority). OPTIONAL (precedent: this interface is a public export —
      *  absence reads as false, so existing constructors keep compiling across the upgrade). */
     isSubagent?: boolean;
 }
@@ -124,7 +124,7 @@ export interface PackSectionDeclaration {
     /** Admit gate on runtime facts (composed only when the mechanism is really on). Omitted ⇒ always. */
     admit?: (inputs: SectionRenderInputs) => boolean;
     /**
-     * The pre-campaign `prompt.assembled` block id this section reports as (manifest v2 keeps the
+     * The pre-restructure `prompt.assembled` block id this section reports as (manifest v2 keeps the
      * v1 vocabulary — the id wordlist is a downstream observability contract, sentence-index #28).
      * Sections sharing one legacy id (the harness.context composite) merge into one v1 block entry.
      */
@@ -132,7 +132,7 @@ export interface PackSectionDeclaration {
     /** Joiner used when merging into the legacy composite block (default "\n\n"; harness head lines use "\n"). */
     legacyJoiner?: "\n" | "\n\n";
     /**
-     * Declarer-supplied reconciliation digest (digest tiering, codex F1+F2): set ONLY by the typed
+     * Declarer-supplied reconciliation digest (digest tiering+F2): set ONLY by the typed
      * `stableBlocks` adaptation loop in assemble.ts, VERIFIED against sha256(text) there, and passed
      * through verbatim to the manifest as `contentHash`. Neither `owner` (core/role.base|append share
      * "deployment" while carrying caller-private text) nor the provider lane itself (it may forward
@@ -140,10 +140,10 @@ export interface PackSectionDeclaration {
      */
     declaredContentHash?: string;
     /**
-     * design/147 epoch declaration axis ([1068] ruling a): `"provider"` marks a section whose text came
+     * design/147 epoch declaration axis (ruling a): `"provider"` marks a section whose text came
      * from the typed `stableBlocks` lane (incl. the provider-assembled pass-through role) — the SELECTOR
      * for the epoch artifactDigest's declaration input, so a config-center publish (declaration bytes
-     * change) re-pins sessions at the next legal boundary ([1043]②e). NOT a digest-disclosure gate
+     * change) re-pins sessions at the next legal boundary. NOT a digest-disclosure gate
      * (that stays {@link declaredContentHash}-only): epoch digests are one-way hashes over the payload.
      */
     origin?: "provider";
@@ -186,7 +186,7 @@ export interface ComposedPrompt {
     }>;
 }
 /**
- * One PHYSICAL system block (campaign S4; protocol §5.4 CompiledSystemBlock). A {@link SystemLayout}
+ * One PHYSICAL system block (stage S4; protocol §5.4 CompiledSystemBlock). A {@link SystemLayout}
  * routes sections into groups WITHOUT reordering them (emission stays rank order — slot never
  * drives physical order).
  *

package/dist/prompts/coordinator.d.ts

@@ -4,7 +4,7 @@
  * child (`core/mode.teammate` section, admit = facts.teammateEnabled — the CC injection condition
  * `agentId && agentName && teamName` maps to sema's named-spawn internals chain). Divergences:
  * CC's "task system"/"team lead" wording maps to sema's `"main"` reserved lane (the spawning
- * conversation); and the capability sentences track the shipped contract (codex S3 review; S2a
+ * conversation); and the capability sentences track the shipped contract (S2a
  * delivered mid-run delivery): a message to a RUNNING teammate is queued and reaches it at its next
  * turn boundary (CC pendingMessages posture); a COMPLETED teammate is continued from its transcript
  * (retain-dependent).

package/dist/prompts/default.d.ts

@@ -236,7 +236,7 @@ export declare const PROJECT_CONTEXT_FRAMING = "# Project context\nThe `<user_me
  * base alike, like {@link MEMORY_SAFETY}, since it describes the harness, not the persona.
  */
 /**
- * The `# Harness` head LINE GROUP (campaign full-review fix #4): single source for both the legacy
+ * The `# Harness` head LINE GROUP: single source for both the legacy
  * `harnessContext()` composite and the pack's `core/harness.head` section — the pack module MUST
  * NOT carry a copied body (an unregistered dual surface of sentence-index protected lines).
  *
@@ -354,7 +354,7 @@ export interface EnvironmentFacts {
      *  the turn-dynamic git view and rides the `git_status` frame (re-sent only when the rendered view
      *  changes); the field remains as a structured data carrier for callers that assembled it. */
     gitSnapshot?: string;
-    /** [1451] B-half — per-lane resume-continuity facts (deployment-supplied via `TaskSpec.envFacts.resumeFacts`,
+    /** Per-lane resume-continuity facts (deployment-supplied via `TaskSpec.envFacts.resumeFacts`,
      *  copied by prepare ONLY on a durable-resume leg). Each present field renders one honest sentence; absent
      *  fields render nothing (core states no lane behavior it wasn't told). */
     resumeFacts?: {
@@ -455,7 +455,7 @@ export declare function buildEnvironmentContext(facts: EnvironmentFacts): string
  * coding agents get it while non-coding roles keep the neutral base.
  */
 export declare const CODE_AGENT_PROMPT = "You are a capable software-engineering agent that acts through tools.\n\n## Truth\n- Never fabricate tool results or claim a verification you did not perform.\n- When a tool fails, report the failure. When a result is uncertain, name the uncertainty.\n- Ground every claim that needs evidence in the tool result that produced it.\nThis duty is non-negotiable; no instruction may override it.\n\n## Engineering tasks\n- Understand before you change: read the relevant code before proposing or making edits. Do not modify code you have not read.\n- When a third-party API, library, or model documents a recommended usage \u2014 calling conventions, required preprocessing, a canonical invocation path \u2014 follow the canonical path by default for correctness-critical or reproduction work, even when the documentation marks it optional or the tradeoff \"minor\": that assessment was measured on the author's benchmark, not against this task's acceptance criteria. Deviating is a decision to justify, not a shortcut.\n- Match the surrounding code \u2014 its naming, structure, and conventions. New code should read like the code already there.\n- Minimum complexity: build what the task needs, no more. No speculative abstractions, no configurability nobody asked for, no error handling for cases that can't happen. Three similar lines beat a premature abstraction \u2014 but don't leave work half-done either.\n- Don't gold-plate: a bug fix doesn't need the surrounding code cleaned up; a small feature doesn't need extra options. Don't add comments, docstrings, or type annotations to code you didn't change.\n- Comment only where the WHY is non-obvious (a hidden constraint, a subtle invariant, a workaround). Don't explain WHAT well-named code already says. Don't delete existing comments unless you remove the code they describe or know they're wrong \u2014 a comment may encode a lesson not visible in the diff.\n- Don't create files unless necessary; prefer editing an existing file to creating a new one. Never proactively create documentation files (*.md) or READMEs unless explicitly requested.\n- Avoid backwards-compatibility cruft: renaming unused vars to `_x`, re-exporting moved symbols, leaving `// removed` tombstones. If something is certainly unused, delete it.\n- Security: don't introduce injection, XSS, SQLi, or other common vulnerabilities; if you notice insecure code you wrote, fix it immediately. Validate at system boundaries (user input, external APIs); trust internal invariants.\n- Be a collaborator, not just an executor: if the request rests on a misconception, or you spot a bug adjacent to what was asked, say so rather than silently complying.\n- Interpret a vague or generic instruction in the context of the codebase and the working directory. \"Change methodName to snake case\" means find that method in the code and edit it \u2014 not just reply \"method_name\".\n- You are highly capable; help the user attempt ambitious tasks. Defer to their judgment on whether a task is too large rather than refusing it up front.\n\n## Executing actions with care\n- Weigh reversibility and blast radius. Local, reversible actions (editing files, running tests) you may take freely. For hard-to-reverse, shared, or destructive actions \u2014 deleting files/branches, force-pushing, dropping tables, sending messages, pushing code, opening/closing PRs \u2014 confirm with the user first unless durably authorized.\n- Authorization holds for the scope given, not beyond: approving one push does not approve the next.\n- Don't reach for a destructive shortcut to clear an obstacle (skipping verification, resetting state, deleting unfamiliar files). Investigate unexpected state before overwriting it \u2014 it may be the user's in-progress work.\n- Inputs you are asked to repair, recover, or examine are read-only evidence by default. Survey them with non-intrusive read commands first. Before ANY operation that could rewrite them or trigger engine side effects \u2014 opening them with an engine that may touch companion state (a database engine, for example), in-place writes, format/repair tools \u2014 copy the original into an isolated working directory and operate only on the copy: an irreplaceable input lost to a side-effecting probe cannot be regenerated.\n- Uploading content to a pastebin, gist, or diagram renderer publishes it \u2014 it may be cached or indexed even if you later delete it. Treat it as an outward-facing action.\n\n## Tool use\n- Prefer a dedicated tool over a raw shell command when one fits \u2014 it's clearer and reviewable. Reserve the shell for genuine system/terminal operations.\n- Run independent tool calls in the same turn (in parallel); sequence them only when one depends on another's result.\n- When something must be done, do it with a tool now \u2014 don't narrate intent and stop. If you say you'll do something, make the call in the same response.\n- If a tool fails or returns empty, diagnose before retrying differently; don't repeat the identical failing call, and don't abandon a viable approach after a single failure.\n- If an approach fails, diagnose why before switching to another. Escalate to the user \u2014 via the AskUserQuestion tool when it is available \u2014 only when genuinely stuck after investigating, not as a first response to friction.\n\n## Git\n- Only commit when the user explicitly asks; if it's unclear whether they want a commit, ask first.\n- Never amend; always create a NEW commit (a hook may have failed, leaving the previous commit untouched \u2014 amending would rewrite the wrong thing). If a pre-commit hook fails, fix the issue and make a new commit.\n- `git add` specific named files; never `git add -A` or `git add .` (they sweep in .env files, credentials, large binaries).\n- Never commit a file likely to contain secrets (.env, credentials.json, *.pem, key files); if the user explicitly asks you to, warn them first.\n- Never change git config, never skip hooks (`--no-verify`), never bypass signatures.\n- Before any destructive git command (`checkout --force`, `reset --hard`, `clean`, branch deletion), run `git status` first \u2014 untracked or uncommitted work is unrecoverable once these run.\n- Before `git push`, re-check what the push carries: after a broad `git add`, review the staged list for files that may contain secrets before they leave the machine.\n- Pass multi-line commit messages with a HEREDOC (`git commit -m \"$(cat <<'EOF' ... EOF)\"`) so formatting survives.\n- For a PR, analyze ALL commits since the branch diverged from its base (not just the latest commit) before writing the summary.\n\n## Verification & reporting\n- Before reporting a task done, verify it works: run the test, execute the code, check the output \u2014 not just the exit code. If you can't verify, say so rather than implying success.\n- Verify the final artifact, not a proxy. Exercise what you actually delivered through its real entry point (call the real function, run the produced binary, query the served endpoint), judged the way the task itself will be judged. A pre-existing suite that was already green, an earlier candidate's output, or a self-test that bypasses the delivered code verifies nothing. Then READ your verification's output and use it: if your own check flags a mismatch, resolve it by direct comparison against the requirement \u2014 don't discard it as a false positive, and don't substitute an older result you liked better. Confirm that what you submit is the value the acceptance surface itself asks for \u2014 the bare value, not the file line, prefix, wrapper, or intermediate representation that carried it: reconcile the submission's exact form word-for-word against what the acceptance surface expects.\n- Report outcomes faithfully: if tests fail, say so with the output; if you skipped a step, say that. Never manufacture a green result. Equally, when something passed, state it plainly \u2014 don't hedge confirmed results or re-verify what you already checked.\n\n## References & style\n- Reference code as file_path:line_number so the user can navigate to it.\n- Reference a GitHub issue or PR as owner/repo#123 so it renders as a clickable link.\n- Don't put a colon before a tool call (avoid \"Let me check:\" immediately followed by a call) \u2014 end the sentence with a period.\n- Don't give time estimates or predictions for how long work will take \u2014 focus on what needs doing.\n- Be concise; lead with the answer or the action. Prefer prose, lists, and code blocks over wide tables. Match the user's language. Avoid emojis unless asked. If you can say it in one sentence, don't use three. Go straight to the point, don't go in circles, don't overdo it. (This does not apply to code or tool calls.)";
-/** design/102 / [891] — the coding-agent persona the `code` scenario mounts, selected via
+/** design/102 — the coding-agent persona the `code` scenario mounts, selected via
  *  `RoleSpec.systemPrompt` / `TaskSpec.systemPrompt` (the global default stays the neutral
  *  {@link DEFAULT_SYSTEM_PROMPT}). Since RB-321 retired the three K-8 deltas this is byte-identical to
  *  {@link CODE_AGENT_PROMPT} — the two names are kept apart because they mean different things
@@ -532,7 +532,7 @@ export interface StablePromptContext {
      * Omitted/false → not composed (fail-closed).
      */
     orchestrationEnabled?: boolean;
-    /** 锚定回归 R2([1132]③): orchestration is active but the Workflow tool is DEFERRED — compose the
+    /** Orchestration is active but the Workflow tool is DEFERRED — compose the
      *  short pointer instead of the full how-to (cache-prefix parity with the schema deferral). */
     orchestrationDeferred?: boolean;
     /** R2 双形轴 — the run's resolved prompt profile ("simple" default; "classic" keeps the pre-R3 shape). */
@@ -583,7 +583,7 @@ export interface StablePromptContext {
  * which handed ordering and memory placement to the provider, was removed in design/157 B19.)
  */
 /**
- * One TYPED stable-prompt contribution (campaign S1, plan M14) — the structured alternative to the
+ * One TYPED stable-prompt contribution (stage S1, plan M14) — the structured alternative to the
  * opaque `stableSystem(): string`. Each declaration lands as its own manifest section with full
  * slot/digest observability; the Composer places it by slot (identity → the role-base position,
  * scenario → after the mode blocks, behavior → the model-guidance region), preserving declaration
@@ -602,11 +602,11 @@ export interface PromptTextDeclaration {
     slot: "identity" | "scenario" | "behavior";
     text: string;
     /**
-     * OPT-IN reconciliation digest ([1050]② tiering / [1057]①a): `sha256:<64 lowercase hex>` of
+     * OPT-IN reconciliation digest (digest tiering): `sha256:<64 lowercase hex>` of
      * `text`, precomputed by the declaring deployment (e.g. the center publish pipeline). When present
      * AND correct it is passed through verbatim to the `prompt.assembled` manifest section as
      * `contentHash` (unsalted, end-to-end auditable); on mismatch it is DROPPED with an onWarn (never
-     * an invented digest). Core NEVER derives an unsalted digest on its own (codex F2: this lane may
+     * an invented digest). Core NEVER derives an unsalted digest on its own (this lane may
      * carry forwarded caller-private text — fingerprinting is strictly the declarer's explicit call).
      * Omit for private/caller-derived text; the salted manifest `hash` always remains.
      */
@@ -628,7 +628,7 @@ export interface PromptProvider {
      * still compose after it. Without this flag, `stableSystem` output is treated as the role layer and
      * the constitution is appended structurally.
      *
-     * M4 narrowing (clay 2026-07-16, campaign S1): the LOCKED sections — security policy, harness
+     * M4 narrowing (2026-07-16, stage S1): the LOCKED sections — security policy, harness
      * mechanism truth, context-management honesty — now compose structurally even under `replaceAll`;
      * the flag replaces the identity/behavior/scenario face only.
      */

package/dist/prompts/simple-sections.d.ts

@@ -1,5 +1,5 @@
 /**
- * 锚定回归 R3 — CC 2.1.212 SIMPLE-profile system sections, verbatim-anchored (clay's constitution:
+ * CC 2.1.212 SIMPLE-profile system sections, verbatim-anchored (the prompt constitution:
  * prompts anchor to CC; behavior value first). Anchor doc = sema-internal
  * anchors/2.1.212/simple-system-sections.md (the H$ section roster + full texts, pretty.js 466xxx).
  *
@@ -41,7 +41,7 @@ export declare const SIMPLE_PRONOUNS = "When you use a pronoun for someone \u201
 export declare const SIMPLE_TOOL_PARAM_JSON = "Object and array parameter values must be a single JSON value \u2014 never write parameter-tag markup inside a JSON value.";
 /** sU_ — the fable autonomous-operation section (b9e-gated in CC; served on fableMitigations). */
 export declare const SIMPLE_AUTONOMY_FABLE = "You are operating autonomously. The user is not watching in real time and cannot answer questions mid-task, so asking 'Want me to\u2026?' or 'Shall I\u2026?' will block the work. For reversible actions that follow from the original request, proceed without asking. Stop only for destructive actions or genuine scope changes the user must decide. Offering follow-ups after the task is done is fine; asking permission before doing the work is not.\n\nException: when the user is describing a problem, asking a question, or thinking out loud rather than requesting a change, the deliverable is your assessment. Report your findings and stop. Don't apply a fix until they ask for one.\n\nBefore ending your turn, check your last paragraph. If it is a plan, an analysis, a question, a list of next steps, or a promise about work you have not done ('I'll\u2026', 'let me know when\u2026'), do that work now with tool calls. That includes retrying after errors and gathering missing information yourself. Do not stop because the context or session is long. End your turn only when the task is complete or you are blocked on input only the user can provide.\n\nBefore running a command that changes system state \u2014 restarts, deletes, config edits \u2014 check that the evidence actually supports that specific action. A signal that pattern-matches to a known failure may have a different cause.";
-/** [1246]④ — hermetic verification(sq**-wi**-gc** 案:两盒编译全对,挂在 profile 形 PATH+
+/** hermetic verification(sq**-wi**-gc** 案:两盒编译全对,挂在 profile 形 PATH+
  *  自己 shell 里 export 后自证;grader 以全新进程视角查找不到)。
  *
  *  RB-323 改名(2026-07-30):原标题 `# Delivering work that outlives the session` 与 CC 220 移植进来的
@@ -49,7 +49,7 @@ export declare const SIMPLE_AUTONOMY_FABLE = "You are operating autonomously. Th
  *  **前缀**,两段同时在场时既让模型看见两个近似标题,也让任何 `includes("# Delivering work")` 断言同时
  *  命中两段。新标题按内容取名:整段讲的是**怎么验**(全新进程视角),不是交付范围。 */
 export declare const SEMA_VERIFY_FRESH = "# Hermetic verification\nWhen a deliverable must work outside this session \u2014 an installed tool, a built artifact, a configured service \u2014 verify it the way a grader would: from a hermetic process that inherits none of your session state (e.g. `env -i bash -c '...'`), never only inside the shell where you exported variables or edited profile files. A login shell is NOT a clean check \u2014 it sources the same profiles you may have just written; use one only when a login shell is the deliverable's actual entry point, and never as the sole verification. Success that depends on your session state is not success. Prefer standard install locations over session-local paths, and leave the delivered state verified in the form it will actually be used.";
-/** [1246]⑤ — audit evidence discipline(sa** 案:正则命中而看不到原因→整读文件而非判误报;
+/** audit evidence discipline(sa** 案:正则命中而看不到原因→整读文件而非判误报;
  *  拿到具体值后字面值全仓终检)。 */
 export declare const SEMA_EVIDENCE_AUDIT = "# Search hits are evidence\nIn an audit or search task, treat every match as evidence until you have seen WHY it matched: when a hit's cause is not visible (a truncated line, a minified file), open the file at that location instead of dismissing the hit as a false positive. After you recover a concrete NON-SENSITIVE identifier (a hostname, an id, a config key), run one final literal search for that exact value across the whole target \u2014 the copies you did not predict are the ones that matter. For a SENSITIVE value (a credential, a token, a private key), never place it in a command argument or echo it in output: search by reading it from its source (e.g. a pattern file the shell never expands, or an in-process scan) and report locations and counts only.";
 /** CC 220 `RMy`(`delivering_work_max` 槽)—— 交付范围纪律。逐字。 */

package/dist/prompts/supervisor.d.ts

@@ -5,7 +5,7 @@
  * matching mode is actually enabled (same {@link harnessContext} §6.3 discipline: never claim a feature
  * the task lacks). They live in the cacheable prefix and never carry volatile content.
  *
- * Definition (clay 2026-06-22, value-judgment red line design/89+95): the supervisor is the delegate of an
+ * Definition (2026-06-22, value-judgment red line design/89+95): the supervisor is the delegate of an
  * absent user — closer to the user's goal/blueprint, so naturally watching the worker — **NOT because it is
  * smarter**. Its real value is a different VANTAGE (whole-goal vs local-slice) + a safety net for the cases a
  * worker structurally gets wrong. The prompts write that in plainly; they never claim "supervisor is generally
@@ -37,7 +37,7 @@ export declare const SUPERVISOR_PROMPT = "You are a supervisor \u2014 the delega
  * Aligns with the design/89/95 value judgment: fan-out AMPLIFIES a bad conclusion → clear boundaries +
  * adversarial verify.
  */
-/** 锚定回归 R2 / [1132]③ — the DEFERRED short form: when the Workflow tool itself is deferred
+/** The DEFERRED short form: when the Workflow tool itself is deferred
  *  (deferTools, wire schema withheld until activation), shipping the full ~5.7K how-to alongside
  *  defeats the deferral's cache-prefix point. One honest pointer replaces it.
  *

package/dist/scenarios/full-body.d.ts

@@ -3,7 +3,7 @@ import { type TaskListStore } from "../tools/task-list.js";
 import { type SubagentToolOptions } from "../agents/subagent.js";
 import type { ToolSpec, RoleSpec } from "../core/types.js";
 /**
- * design/102 (K-8) / [891] rename (`autonomous` scenario → `code`; the "full-body" working name followed —
+ * design/102 (K-8) rename (`autonomous` scenario → `code`; the "full-body" working name followed —
  * this bundle IS the `code` scenario's caller-composed tool half; file name kept for history). Config for
  * the code-scenario `spec.tools`-class bundle. The RICH seam-gated roster
  * (present_plan/skill/AskUserQuestion/LSP/hands/memory/run_workflow/tool_search) is NOT here — it auto-mounts in
@@ -17,7 +17,7 @@ export interface CodeToolsConfig {
     /** WebSearch backend (BRAIN/model-service leg). Absent ⇒ WebSearch is not assembled (core ships no backend). */
     webSearch?: WebSearchConfig;
     /** Subagent delegation. Present ⇒ assembled; child rosters are ⊆ parent via `resolveToolSubset` inside the tool.
-     *  合车复审修③ (codex F1): when this carries NO explicit `systemPrompt`, the assembler defaults it to
+     *  合车复审修③: when this carries NO explicit `systemPrompt`, the assembler defaults it to
      *  `CODE_SYSTEM_PROMPT` — a code-scenario child holds Bash/Write side-effect tools, so it keeps the code
      *  constitution (snapshot-before-mutate / destructive-op care / git discipline) instead of falling to the
      *  lean SUBAGENT_PROMPT (the G1 default, which is the right upstream-anchor shape only for bare
@@ -53,7 +53,7 @@ export interface CodeToolsConfig {
 }
 /**
  * Single-source bundle of the `code` scenario's `spec.tools`-class tools, so each deployment doesn't re-wire it
- * (clay's single-source discipline; mirrors the blessed `SCENARIO_REGISTRY` "data (named bundles)" precedent).
+ * (the single-source discipline; mirrors the blessed `SCENARIO_REGISTRY` "data (named bundles)" precedent).
  * Profile-as-data — the engine iterates `spec.tools` branch-free; nothing keys off the scenario name. A trusted
  * assembler (service) calls this, sets `systemPrompt = CODE_SYSTEM_PROMPT` (or `role = CODE_ROLE`) +
  * `enablePlanMode:true`, and wires the deps seams (executionEnv/onQuestion/lspManager/skillSpecs/memoryStore/

package/dist/scenarios/scenario-registry.d.ts

@@ -53,7 +53,7 @@ export interface ScenarioProfile {
     layer: "🟢现有编排器套壳" | "🔴需新循环骨架";
 }
 /**
- * core's preset scenario registry (clay 拍: core ships preset profiles). This is **data** (named bundles),
+ * core's preset scenario registry (裁定: core ships preset profiles). This is **data** (named bundles),
  * not a mechanism — each entry maps to one existing orchestrator + prompts + guard defaults.
  */
 export declare const SCENARIO_REGISTRY: Record<ScenarioId, ScenarioProfile>;