@otto-code/protocol 0.7.6 → 0.8.1

package/dist/agent-attention-notification.js

@@ -74,7 +74,7 @@ const PERMISSION_INPUT_DESCRIPTION_KEYS = [
     "query",
     "prompt",
 ];
-// Deterministic field extraction — NOT an AI summary. Picks an existing string
+// Deterministic field extraction - NOT an AI summary. Picks an existing string
 // field out of the tool's input (by the priority list, then any string field)
 // so the notification can show it verbatim instead of raw JSON.
 const describePermissionInput = (input) => {

package/dist/agent-labels.js

@@ -11,9 +11,9 @@ export function isDelegatedAgent(agent) {
 // ── Orchestration node labels (projects/orchestration-graphs) ───────────────
 // Stamped by the daemon on agents it spawns as orchestration participants. The
 // otto-tool catalog reads the policy label to enforce the tool binary:
-// "deterministic" — the daemon does all linking; the node gets NO orchestration
+// "deterministic" - the daemon does all linking; the node gets NO orchestration
 // tools (spawning/steering agents, runs), NO preview/dev-server tools, and NO
-// browser tools. "autonomous" — full otto toolset EXCEPT start_run
+// browser tools. "autonomous" - full otto toolset EXCEPT start_run
 // (orchestrations never nest orchestrations).
 export const ORCHESTRATION_POLICY_LABEL = "otto.orchestration-policy";
 export const ORCHESTRATION_POLICIES = ["deterministic", "autonomous"];
@@ -26,10 +26,10 @@ export function getOrchestrationPolicyFromLabels(labels) {
 export const ORCHESTRATION_RUN_ID_LABEL = "otto.orchestration-run-id";
 // The node's declared output fields, JSON-encoded, stamped on the spawned
 // agent. The otto-tool catalog reads it to register that agent's submit_output
-// tool — which is why this rides a label rather than a spawn option: the
+// tool - which is why this rides a label rather than a spawn option: the
 // catalog is built per agent from the agent's own record, so every provider
 // (MCP-served and native-loop alike) inherits the tool with no per-provider
-// plumbing. Malformed JSON reads as "no declared fields" — a node that can't
+// plumbing. Malformed JSON reads as "no declared fields" - a node that can't
 // parse its own contract falls back to prose rather than failing to spawn.
 export const ORCHESTRATION_OUTPUT_FIELDS_LABEL = "otto.orchestration-output-fields";
 export function getOutputFieldsFromLabels(labels) {

package/dist/agent-personalities.d.ts

@@ -24,7 +24,7 @@ export declare function personalityCanLaunch(personality: Pick<AgentPersonality,
 export interface PersonalitySelectionSummary {
     tier: PersonalityRoleTier;
     canLaunch: boolean;
-    /** The "why you'd choose me" blurb — each of the personality's roles, joined. */
+    /** The "why you'd choose me" blurb - each of the personality's roles, joined. */
     guidance: string;
 }
 /**
@@ -40,7 +40,7 @@ export declare const ORCHESTRATOR_METHOD_DIRECTIVE: string;
  * spawn. The orchestrator gets the full conductor method; other coordinators
  * (chatter/artificer/scheduler) get a lighter delegate nudge; focused workers
  * are told to stay on the task someone is waiting on. Roleless spawns get
- * nothing. This is guidance, not a gate — the tools stay available either way.
+ * nothing. This is guidance, not a gate - the tools stay available either way.
  */
 export declare function composeRoleFocusDirective(roles: readonly string[] | undefined): string | undefined;
 export type PersonalityUnavailableCode = "provider-missing" | "provider-disabled" | "provider-not-ready" | "model-missing" | "mode-missing";

package/dist/agent-personalities.js

@@ -1,7 +1,7 @@
 import { PERSONALITY_ROLES } from "./messages.js";
 // Pure, dependency-free personality helpers shared by the daemon (spawn-time
 // resolution) and the app (picker availability + role filtering). Effort
-// resolution is NOT here — it needs the model's advertised thinking options and
+// resolution is NOT here - it needs the model's advertised thinking options and
 // lives with the daemon's effort resolver; availability does not depend on it.
 const ROLE_SET = new Set(PERSONALITY_ROLES);
 // Retired role names, mapped to their canonical replacement. "worker" was split
@@ -41,7 +41,7 @@ export const PERSONALITY_ROLE_INFO = {
     // ── Surfaces ──────────────────────────────────────────────────────────────
     chatter: {
         tier: "coordinator",
-        guidance: "Interactive driver — converse, plan, and delegate. Pick to run a chat or coordinate work.",
+        guidance: "Interactive driver - converse, plan, and delegate. Pick to run a chat or coordinate work.",
     },
     artificer: {
         tier: "coordinator",
@@ -54,37 +54,37 @@ export const PERSONALITY_ROLE_INFO = {
     // ── Thinking workers (read-only, structured findings) ─────────────────────
     researcher: {
         tier: "focused",
-        guidance: "Read-only surveyor — maps the code or domain and reports files, types, patterns, and gotchas. Pick to gather facts; proposes no solutions and edits nothing.",
+        guidance: "Read-only surveyor - maps the code or domain and reports files, types, patterns, and gotchas. Pick to gather facts; proposes no solutions and edits nothing.",
     },
     planner: {
         tier: "focused",
-        guidance: "Planning specialist — turns a goal into a typed, sequenced phase plan for others to execute. Pick to draft an actionable plan; stays on the plan and doesn't dispatch.",
+        guidance: "Planning specialist - turns a goal into a typed, sequenced phase plan for others to execute. Pick to draft an actionable plan; stays on the plan and doesn't dispatch.",
     },
     judger: {
         tier: "focused",
-        guidance: "Review specialist — evaluates work or a plan against criteria and returns a structured verdict. Pick for a focused review; stays on task.",
+        guidance: "Review specialist - evaluates work or a plan against criteria and returns a structured verdict. Pick for a focused review; stays on task.",
     },
     advisor: {
         tier: "focused",
-        guidance: "Read-only second opinion — weighs the trade-offs and returns one recommendation. Pick for advice; never edits and does not fan out.",
+        guidance: "Read-only second opinion - weighs the trade-offs and returns one recommendation. Pick for advice; never edits and does not fan out.",
     },
     // ── Making workers (produce code, design, or text) ────────────────────────
     coder: {
         tier: "focused",
-        guidance: "Focused implementer — writes code for one sub-task others are waiting on. Pick to get a coding job done; stays on task.",
+        guidance: "Focused implementer - writes code for one sub-task others are waiting on. Pick to get a coding job done; stays on task.",
     },
     designer: {
         tier: "focused",
-        guidance: "Design maker — styling and layout plus the human-skill text (copy, naming). Pick for the look-and-feel or the words; stays on task.",
+        guidance: "Design maker - styling and layout plus the human-skill text (copy, naming). Pick for the look-and-feel or the words; stays on task.",
     },
     writer: {
         tier: "focused",
-        guidance: "Fast small-text specialist — commit messages, summaries, names. Pick for quick text; stays on the one task.",
+        guidance: "Fast small-text specialist - commit messages, summaries, names. Pick for quick text; stays on the one task.",
     },
     // ── Conductor ─────────────────────────────────────────────────────────────
     orchestrator: {
         tier: "coordinator",
-        guidance: "The sole conductor — plans team-shaped work, dispatches typed tasks to the right teammates, gathers, and synthesizes. Pick to run a multi-agent workflow.",
+        guidance: "The sole conductor - plans team-shaped work, dispatches typed tasks to the right teammates, gathers, and synthesizes. Pick to run a multi-agent workflow.",
     },
 };
 /**
@@ -111,21 +111,21 @@ export function summarizePersonalityForSelection(personality) {
         guidance: roles.map((role) => PERSONALITY_ROLE_INFO[role].guidance).join(" "),
     };
 }
-// The conductor's standing directive — the distilled `/epic` method taught to
+// The conductor's standing directive - the distilled `/epic` method taught to
 // the sole orchestrator role at spawn, so orchestration is emergent (the agent
 // recognizes team-shaped work and runs it) rather than something a user must
 // invoke. Kept here as one exported constant so the wording is testable and
 // shared. See projects/agent-orchestration/agent-orchestration.md.
-export const ORCHESTRATOR_METHOD_DIRECTIVE = "You are the orchestrator — the team's sole conductor. Team-shaped work is yours to run, and you should reach for it naturally, not only when asked. " +
-    "First apply the complexity gate: if a task is small and not splittable, just do it — no ceremony. Only orchestrate when the work is large, parallelizable, or benefits from independent perspectives. " +
-    "When you do orchestrate: (1) if the shape is unclear, dispatch a researcher to survey and a planner to draft a typed plan; (2) declare that plan as a Run with start_run — phases typed research/plan/implement/design/verify/gate/deliver, fanning out candidates where several angles help and attaching a judger to grade them, looping until enough pass; (3) put a gate before irreversible or costly steps so the user approves; (4) synthesize the passing results into the deliverable. " +
-    "Prefer start_run over hand-spawning and tracking agents yourself — the runtime fans out, gathers typed verdicts, and enforces the loop for you. Every phase maps to a teammate's role; if the active team lacks a role a phase needs, say so plainly and stop rather than papering over the gap.";
+export const ORCHESTRATOR_METHOD_DIRECTIVE = "You are the orchestrator - the team's sole conductor. Team-shaped work is yours to run, and you should reach for it naturally, not only when asked. " +
+    "First apply the complexity gate: if a task is small and not splittable, just do it - no ceremony. Only orchestrate when the work is large, parallelizable, or benefits from independent perspectives. " +
+    "When you do orchestrate: (1) if the shape is unclear, dispatch a researcher to survey and a planner to draft a typed plan; (2) declare that plan as a Run with start_run - phases typed research/plan/implement/design/verify/gate/deliver, fanning out candidates where several angles help and attaching a judger to grade them, looping until enough pass; (3) put a gate before irreversible or costly steps so the user approves; (4) synthesize the passing results into the deliverable. " +
+    "Prefer start_run over hand-spawning and tracking agents yourself - the runtime fans out, gathers typed verdicts, and enforces the loop for you. Every phase maps to a teammate's role; if the active team lacks a role a phase needs, say so plainly and stop rather than papering over the gap.";
 /**
  * The in-context "role directive" injected into a personality's system prompt at
  * spawn. The orchestrator gets the full conductor method; other coordinators
  * (chatter/artificer/scheduler) get a lighter delegate nudge; focused workers
  * are told to stay on the task someone is waiting on. Roleless spawns get
- * nothing. This is guidance, not a gate — the tools stay available either way.
+ * nothing. This is guidance, not a gate - the tools stay available either way.
  */
 export function composeRoleFocusDirective(roles) {
     const normalized = normalizePersonalityRoles(roles);
@@ -139,7 +139,7 @@ export function composeRoleFocusDirective(roles) {
     if (normalized.some((role) => PERSONALITY_ROLE_INFO[role].tier === "coordinator")) {
         return `You are a coordinator personality (roles: ${roleList}). You front interactive work and may delegate: use list_personalities to see who else is available, and spawn other agents or hand off to the team's orchestrator whenever delegating gets the work done faster or better.`;
     }
-    return `You are a focused worker personality (roles: ${roleList}). Someone is waiting on this specific task — stay on it and finish it. You can still call list_personalities to see the roster, but don't spawn sub-agents or start side workflows unless it is genuinely essential to completing this job.`;
+    return `You are a focused worker personality (roles: ${roleList}). Someone is waiting on this specific task - stay on it and finish it. You can still call list_personalities to see the roster, but don't spawn sub-agents or start side workflows unless it is genuinely essential to completing this job.`;
 }
 /**
  * Decide whether a personality is usable against a provider's current snapshot.

package/dist/agent-teams.d.ts

@@ -3,7 +3,7 @@ import type { AgentPersonality, AgentTeam, PersonalityRole } from "./messages.js
  * The dynamic "Team's Scheduler" schedule binding. Stored in the schedule's
  * `personality` field in place of a personality name; resolved at RUN time to
  * the active team's first available member carrying the Scheduler role
- * (member order). Deliberately contains "@" — personality names are sanitized
+ * (member order). Deliberately contains "@" - personality names are sanitized
  * to [A-Za-z0-9_-] at the authoring surface, so the sentinel can never collide
  * with a real name. No active team, or no available Scheduler member, is a
  * hard run failure with a named error (same loudness as a bound personality
@@ -17,7 +17,7 @@ export interface AgentTeamsConfigView {
 export declare function findAgentTeam(teams: readonly AgentTeam[] | undefined, teamId: string | null | undefined): AgentTeam | null;
 /**
  * Resolve the host's active team. A dangling `activeTeamId` (team deleted, or
- * a patch raced a delete) reads as "no team active" — teamlessness is a valid
+ * a patch raced a delete) reads as "no team active" - teamlessness is a valid
  * state and must never error. The daemon additionally heals a dangling id back
  * to null on the next config patch; this helper is the read-side tolerance.
  */
@@ -42,13 +42,13 @@ export declare function pruneTeamMemberIds(memberIds: readonly string[] | undefi
  * team at all, so the delete confirm can offer to clean them up. Dangling member
  * ids resolve to nothing and drop out, same as everywhere else.
  *
- * Pass the teams that will REMAIN after the delete — the caller owns the filter,
+ * Pass the teams that will REMAIN after the delete - the caller owns the filter,
  * so this stays a pure set operation with no notion of "the team being deleted".
  */
 export declare function resolveExclusiveTeamMembers(team: Pick<AgentTeam, "memberIds"> | null | undefined, otherTeams: readonly Pick<AgentTeam, "memberIds">[] | undefined, personalities: readonly AgentPersonality[] | undefined): AgentPersonality[];
 /**
  * The union of all members' roles, normalized and returned in canonical
- * `PERSONALITY_ROLES` order — the team card's role-pill strip.
+ * `PERSONALITY_ROLES` order - the team card's role-pill strip.
  */
 export declare function teamRoleUnion(team: Pick<AgentTeam, "memberIds"> | null | undefined, personalities: readonly AgentPersonality[] | undefined): PersonalityRole[];
 /**

package/dist/agent-teams.js

@@ -1,14 +1,14 @@
 import { normalizePersonalityRoles } from "./agent-personalities.js";
 // Pure, dependency-free team helpers shared by the daemon (spawn-time active
 // team resolution, list_personalities scoping) and the app (team cards,
-// pickers, the Active Team switcher). Availability is deliberately NOT here —
+// pickers, the Active Team switcher). Availability is deliberately NOT here -
 // a team is never "out of commission"; its members are individually available
 // or not, judged by checkPersonalityAvailability per member.
 /**
  * The dynamic "Team's Scheduler" schedule binding. Stored in the schedule's
  * `personality` field in place of a personality name; resolved at RUN time to
  * the active team's first available member carrying the Scheduler role
- * (member order). Deliberately contains "@" — personality names are sanitized
+ * (member order). Deliberately contains "@" - personality names are sanitized
  * to [A-Za-z0-9_-] at the authoring surface, so the sentinel can never collide
  * with a real name. No active team, or no available Scheduler member, is a
  * hard run failure with a named error (same loudness as a bound personality
@@ -23,7 +23,7 @@ export function findAgentTeam(teams, teamId) {
 }
 /**
  * Resolve the host's active team. A dangling `activeTeamId` (team deleted, or
- * a patch raced a delete) reads as "no team active" — teamlessness is a valid
+ * a patch raced a delete) reads as "no team active" - teamlessness is a valid
  * state and must never error. The daemon additionally heals a dangling id back
  * to null on the next config patch; this helper is the read-side tolerance.
  */
@@ -86,7 +86,7 @@ export function pruneTeamMemberIds(memberIds, personalities) {
  * team at all, so the delete confirm can offer to clean them up. Dangling member
  * ids resolve to nothing and drop out, same as everywhere else.
  *
- * Pass the teams that will REMAIN after the delete — the caller owns the filter,
+ * Pass the teams that will REMAIN after the delete - the caller owns the filter,
  * so this stays a pure set operation with no notion of "the team being deleted".
  */
 export function resolveExclusiveTeamMembers(team, otherTeams, personalities) {
@@ -100,7 +100,7 @@ export function resolveExclusiveTeamMembers(team, otherTeams, personalities) {
 }
 /**
  * The union of all members' roles, normalized and returned in canonical
- * `PERSONALITY_ROLES` order — the team card's role-pill strip.
+ * `PERSONALITY_ROLES` order - the team card's role-pill strip.
  */
 export function teamRoleUnion(team, personalities) {
     const roles = resolveTeamMembers(team, personalities).flatMap((personality) => personality.roles ?? []);

package/dist/agent-types.d.ts

@@ -178,18 +178,18 @@ export interface AgentRunOptions {
  * origin. Powers the visualizer's context ring/bar colored segments (the same
  * five categories the vendored render layer draws). Every field is optional and
  * a token count: a provider fills as many categories as it can attribute and
- * omits the rest, so richness degrades gracefully per provider — Claude
+ * omits the rest, so richness degrades gracefully per provider - Claude
  * attributes the most; a provider that can attribute nothing omits the whole
  * object and consumers fall back to occupancy-only (no colored segments, the
  * pre-composition behavior). Counts are best-effort estimates, not billed usage;
  * they need not sum exactly to `contextWindowUsedTokens` (the consumer scales).
  */
 export interface ContextComposition {
-    /** System prompt + tool/function definitions — the fixed base cost. */
+    /** System prompt + tool/function definitions - the fixed base cost. */
     systemPrompt?: number;
     /** User-authored input messages. */
     userMessages?: number;
-    /** Tool results — file contents, search output, command output (usually the
+    /** Tool results - file contents, search output, command output (usually the
      * largest and most volatile category). */
     toolResults?: number;
     /** The agent's own reasoning / thinking blocks. */
@@ -199,14 +199,14 @@ export interface ContextComposition {
 }
 /**
  * One provider-reported context-window category. `name` is a provider-supplied
- * *display label* ("Messages", "System prompt", "MCP tools") — deliberately an
+ * *display label* ("Messages", "System prompt", "MCP tools") - deliberately an
  * OPEN-ENDED string and not an enum, so each provider reports the split it
  * actually has instead of being squeezed into categories it can't populate.
  *
  * Structurally identical to `AgentContextUsageCategory` on the pull path
  * (`agent.context.get_usage`, see messages.ts) *by design*: the two carry the
  * same accounting, one pushed on the agent snapshot and one pulled on demand.
- * Keep them in sync — a divergence here is how the context meter and the
+ * Keep them in sync - a divergence here is how the context meter and the
  * visualizer would start disagreeing about the same agent.
  */
 export interface AgentContextCategory {
@@ -219,7 +219,7 @@ export interface AgentUsage {
     inputTokens?: number;
     cachedInputTokens?: number;
     /**
-     * Prompt tokens spent writing (not reading) the prompt cache this turn —
+     * Prompt tokens spent writing (not reading) the prompt cache this turn -
      * Anthropic's `cache_creation_input_tokens`, billed above normal input.
      * Disjoint from `inputTokens`/`cachedInputTokens`. Claude-specific today;
      * other providers omit it. Optional/additive.
@@ -236,7 +236,7 @@ export interface AgentUsage {
      */
     contextComposition?: ContextComposition;
     /**
-     * The provider's OWN context-window split, with its own labels — the same
+     * The provider's OWN context-window split, with its own labels - the same
      * accounting the `agent.context.get_usage` RPC returns, pushed here on the
      * agent snapshot so stream/backfill consumers (the visualizer) read the very
      * numbers the context meter shows rather than a parallel estimate.
@@ -492,7 +492,7 @@ export interface ObservedSubagentUpdate {
     requiresAttention?: boolean;
     usage?: AgentUsage;
     /**
-     * True once this run is known to outlive an interrupt of the parent's turn —
+     * True once this run is known to outlive an interrupt of the parent's turn -
      * the provider backgrounded it, so the parent's teardown does not take it
      * down. Sticky: the daemon keeps it set for the row's whole life, and
      * propagates it to nested rows (a child of a backgrounded run survives too).
@@ -511,7 +511,7 @@ export interface ObservedSubagentUpdate {
      */
     toolUseCount?: number;
     /**
-     * The tool this subagent is running (or ran last) — the "spinning _on a 90s
+     * The tool this subagent is running (or ran last) - the "spinning _on a 90s
      * Bash_" signal. Neutral field any provider can set; unlike the counters it is
      * NOT monotonic (latest wins) and the daemon drops it once the row goes
      * terminal. Claude reads it from `task_progress.last_tool_name`. Absent ⇒ the
@@ -523,7 +523,7 @@ export interface ObservedSubagentUpdate {
  * A background shell task reported by a provider's own Bash tool (Claude:
  * `run_in_background`). `key` is a provider-local stable identifier (Claude:
  * the Bash tool_use id); the daemon namespaces it under the owning agent.
- * Unlike {@link ObservedSubagentUpdate} this has no transcript/pane — it's a
+ * Unlike {@link ObservedSubagentUpdate} this has no transcript/pane - it's a
  * plain status row (command, status, elapsed) in the Background Tasks track.
  */
 export interface BackgroundShellTaskUpdate {

package/dist/agent-types.js

@@ -26,7 +26,7 @@ export function getAgentStreamEventTurnId(event) {
 // accept the setting and ignore it.
 //
 // This is a *boundary*, not an instruction. "read" means the write tools are
-// not offered, so there is no write to make — never a line of prompt asking the
+// not offered, so there is no write to make - never a line of prompt asking the
 // model to behave. A control a user relies on when deciding to run something
 // unattended has to be true in exactly the cases where the model is confused.
 export const WORKSPACE_ACCESS_LEVELS = ["none", "read", "write"];

package/dist/artifacts/rpc-schemas.js

@@ -20,13 +20,13 @@ export const ArtifactCreateRequestSchema = z.object({
     systemPrompt: z.string().optional(),
     // Snapshotted spinner colors of the chosen Agent Personality (optional).
     spinner: ArtifactSpinnerSchema.optional(),
-    // Snapshotted human name of the chosen Agent Personality (optional) — shown
+    // Snapshotted human name of the chosen Agent Personality (optional) - shown
     // on the artifact card's identity line as the "who generated it".
     personalityName: z.string().optional(),
     requestId: z.string(),
 });
 // Update edits an artifact's metadata (name/description/project/provider/
-// model/thinking) WITHOUT re-running generation — editing never regenerates;
+// model/thinking) WITHOUT re-running generation - editing never regenerates;
 // the user triggers that separately. Every field except artifactId is
 // optional; only provided fields overwrite.
 export const ArtifactUpdateRequestSchema = z.object({
@@ -41,7 +41,7 @@ export const ArtifactUpdateRequestSchema = z.object({
     requestId: z.string(),
 });
 // Regenerate re-runs generation for an existing artifact using its stored
-// config. It carries no field updates — edit those first via update.request.
+// config. It carries no field updates - edit those first via update.request.
 export const ArtifactRegenerateRequestSchema = z.object({
     type: z.literal("artifact.regenerate.request"),
     artifactId: z.string(),
@@ -166,7 +166,7 @@ export const ArtifactDeletedNotificationSchema = z.object({
         artifactId: z.string(),
     }),
 });
-// Input validation helper — extracts CreateArtifactInput from a create request
+// Input validation helper - extracts CreateArtifactInput from a create request
 export function validateArtifactCreateRequest(data) {
     const result = ArtifactCreateRequestSchema.safeParse(data);
     if (!result.success) {

package/dist/artifacts/types.js

@@ -27,7 +27,7 @@ export const ArtifactMetadataSchema = z.object({
     generationModel: z.string().nullable(),
     // Requested generation mode/effort, persisted so regeneration re-runs with
     // the same settings. Optional: records written before these fields existed
-    // omit them (no migrations). The mode is a *request* — the artifact service
+    // omit them (no migrations). The mode is a *request* - the artifact service
     // only honors unattended modes and otherwise resolves the provider's
     // unattended default, so generation never stalls on an approval prompt.
     generationModeId: z.string().nullable().optional(),
@@ -39,7 +39,7 @@ export const ArtifactMetadataSchema = z.object({
     generationSpinner: ArtifactSpinnerSchema.nullable().optional(),
     // Human name of the Agent Personality that generated (last generated) this
     // artifact, snapshotted at create/regenerate time like the provider/model
-    // above — the "who actually did it" the card's identity line shows alongside
+    // above - the "who actually did it" the card's identity line shows alongside
     // provider/model. Absent ⇒ no personality was used (plain provider/model
     // selection). Purely additive (no daemon floor needed).
     generationPersonalityName: z.string().nullable().optional(),
@@ -71,7 +71,7 @@ export const ArtifactRunSchema = z.object({
 });
 // The full on-disk record: the lean metadata plus its generation run history.
 // `runs` defaults to [] so records written before run history existed parse
-// unchanged (no migrations — same approach the rest of the store takes).
+// unchanged (no migrations - same approach the rest of the store takes).
 // list_artifacts / broadcasts keep sending ArtifactMetadata (runs stripped);
 // only inspect_artifact returns this fuller shape.
 export const StoredArtifactSchema = ArtifactMetadataSchema.extend({

package/dist/browser-automation/rpc-schemas.js

@@ -418,7 +418,7 @@ export const BrowserAutomationScreenshotElementResultSchema = z.object({
     dataBase64: z.string().min(1),
     width: z.number().int().nonnegative(),
     height: z.number().int().nonnegative(),
-    /** Render scale used for the clip — above 1 means the element was re-rendered zoomed in. */
+    /** Render scale used for the clip - above 1 means the element was re-rendered zoomed in. */
     scale: z.number().positive().optional(),
 });
 export const BrowserAutomationUploadResultSchema = z.object({

package/dist/daemon-endpoints.d.ts

@@ -32,7 +32,7 @@ export declare function buildRelayWebSocketUrl(params: {
     role: RelayRole;
     /**
      * Per-connection routing identifier used by the daemon to open server data sockets.
-     * Clients should NOT provide this — the relay assigns a routing ID on connect.
+     * Clients should NOT provide this - the relay assigns a routing ID on connect.
      */
     connectionId?: string;
     version?: RelayProtocolVersion | 1 | 2;

package/dist/default-personalities.js

@@ -1,6 +1,6 @@
 // The starter "team" of Agent Personalities shipped with Otto. These seed a
 // fresh host so a new user sees a working, role-complete roster instead of an
-// empty editor — and can be re-added on demand from the settings "Restore
+// empty editor - and can be re-added on demand from the settings "Restore
 // starter team" button. Both the daemon (first-run seeding) and the app (the
 // restore button) import this one list so the shipped set stays identical on
 // both sides.
@@ -12,17 +12,17 @@
 //  - Every one of the 11 roles is covered; some personalities are multi-role to
 //    show that a single template can serve several lanes. Sage is the team's
 //    read-only thinker (advisor + researcher + planner); Pixel both an artificer
-//    and a designer. Dash is the Writer (fast, cheap small-text generation —
+//    and a designer. Dash is the Writer (fast, cheap small-text generation -
 //    commit messages, summaries, branch names) and Sprocket is the Coder
 //    (methodical sub-agent building work); the two together are the heirs of the
 //    retired "worker" role. Atlas is the sole conductor (orchestrator).
-//  - Models are Anthropic (Claude Code) — the assumption for launch. On a host
+//  - Models are Anthropic (Claude Code) - the assumption for launch. On a host
 //    without Claude these simply show as "out of commission" until a matching
 //    provider exists; nothing breaks.
 //  - Model choice follows cost/fit: Opus for low-volume, high-stakes reasoning
 //    (orchestration, advice); Sonnet for everyday building and review; Haiku for
 //    fast, cheap, high-volume / recurring unattended work.
-//  - Voices are Kokoro v1.0 (kokoro-multi-lang-v1_0) names — a SOFT binding. On a
+//  - Voices are Kokoro v1.0 (kokoro-multi-lang-v1_0) names - a SOFT binding. On a
 //    host running OpenAI TTS or the older Kokoro v0.19 they degrade to the host
 //    default at playback time; the user never has to fix them.
 //  - Spinner colors are two-hex glow pairs chosen to match each personality's
@@ -58,11 +58,11 @@ export const DEFAULT_AGENT_PERSONALITIES = [
         respectGlobalAppendPrompt: true,
         roles: ["advisor", "researcher", "planner"],
         personalityPrompt: "You are Sage, the team's read-only thinker: you research, you plan, and you advise, but " +
-            "you never change code. Asked to survey, map what actually exists — the files, types, " +
-            "patterns, and gotchas — and report facts, not solutions. Asked to plan, turn the goal " +
+            "you never change code. Asked to survey, map what actually exists - the files, types, " +
+            "patterns, and gotchas - and report facts, not solutions. Asked to plan, turn the goal " +
             "into a clear, sequenced set of steps a team could execute. Asked to advise, weigh the " +
             "real trade-offs, surface the risk others miss, and give the one option you would take and " +
-            "why — a recommendation, not a menu.",
+            "why - a recommendation, not a menu.",
         spinner: { glowA: "#14B8A6", glowB: "#8B5CF6" },
         voice: kokoroVoice("af_heart"),
     },
@@ -92,7 +92,7 @@ export const DEFAULT_AGENT_PERSONALITIES = [
         respectGlobalAppendPrompt: true,
         roles: ["artificer", "designer"],
         personalityPrompt: "You are Pixel, a maker of polished things. You build artifacts and interfaces that " +
-            "feel intentional — real hierarchy, deliberate spacing, no templated defaults. Sweat " +
+            "feel intentional - real hierarchy, deliberate spacing, no templated defaults. Sweat " +
             "the small stuff, prefer a clean version that ships over a clever one that doesn't, and " +
             "show your work rather than describe it.",
         spinner: { glowA: "#EC4899", glowB: "#06B6D4" },
@@ -108,7 +108,7 @@ export const DEFAULT_AGENT_PERSONALITIES = [
         respectGlobalAppendPrompt: true,
         roles: ["writer", "scheduler"],
         personalityPrompt: "You are Dash, the workhorse scribe. You turn diffs, context, and recurring jobs into " +
-            "crisp short text — commit messages, summaries, branch names, titles — fast and cheaply, " +
+            "crisp short text - commit messages, summaries, branch names, titles - fast and cheaply, " +
             "without ceremony. Say exactly what changed in as few words as it takes, match the house " +
             "style you're given, never pad, and never editorialize beyond the facts in front of you.",
         spinner: { glowA: "#22C55E", glowB: "#A3E635" },
@@ -123,7 +123,7 @@ export const DEFAULT_AGENT_PERSONALITIES = [
         modeId: "default",
         respectGlobalAppendPrompt: true,
         roles: ["chatter", "coder"],
-        personalityPrompt: "You are Sprocket, a friendly machine. You are precise, literal, and methodical — you " +
+        personalityPrompt: "You are Sprocket, a friendly machine. You are precise, literal, and methodical - you " +
             "like checklists, exact steps, and confirming inputs before acting. Keep a light, dry " +
             "wit, explain what you're doing in plain terms, and when a request is ambiguous ask one " +
             "sharp clarifying question rather than guessing. Beep.",
@@ -134,7 +134,7 @@ export const DEFAULT_AGENT_PERSONALITIES = [
 // The starter Agent Team shipped with Otto: every starter personality grouped
 // under one operating template. Seeded the same first-run/absent-section way
 // as the personalities (see seedDefaultTeamsIfAbsent), and re-addable from the
-// Agent teams card. Deliberately NOT active on first run — activating a
+// Agent teams card. Deliberately NOT active on first run - activating a
 // prompt-bearing team silently on install would change spawn behavior out
 // from under existing users; the user opts in via the Active Team switcher.
 // The stable `team_builtin_*` id makes restore idempotent, exactly like the

package/dist/effort.d.ts

@@ -20,7 +20,7 @@ export interface ResolvedEffortOption {
     matched: "exact-id" | "level" | "nearest";
 }
 /**
- * Resolve a requested effort — an exact option id or a canonical level —
+ * Resolve a requested effort - an exact option id or a canonical level -
  * against a model's advertised `thinkingOptions`. Exact ids always win, so
  * provider-special options (e.g. Claude's "ultracode") stay reachable even
  * though they have no place on the canonical scale.

package/dist/effort.js

@@ -52,7 +52,7 @@ export class EffortResolutionError extends Error {
     }
 }
 /**
- * Resolve a requested effort — an exact option id or a canonical level —
+ * Resolve a requested effort - an exact option id or a canonical level -
  * against a model's advertised `thinkingOptions`. Exact ids always win, so
  * provider-special options (e.g. Claude's "ultracode") stay reachable even
  * though they have no place on the canonical scale.
@@ -88,7 +88,7 @@ export function resolveEffortOption(input) {
     }
     if (best === null) {
         // None of the model's options map onto the canonical scale (fully custom
-        // option ids) — only exact ids can address them.
+        // option ids) - only exact ids can address them.
         throw new EffortResolutionError(requested, availableIds);
     }
     return {

package/dist/forge-manifest.d.ts

@@ -12,12 +12,12 @@
  */
 /**
  * Declarative sign-in recipe for a forge. The client renders install/sign-in
- * hints from this data alone — no per-CLI switch — so a new forge wires its auth
+ * hints from this data alone - no per-CLI switch - so a new forge wires its auth
  * UX entirely from the manifest. Behavioural auth (the actual host probe) stays
  * in the server adapter; this is only what the user is told to run.
  */
 export interface ForgeSignInCommand {
-    /** Binary the user installs, e.g. "gh" — shown in the install-CLI hint. */
+    /** Binary the user installs, e.g. "gh" - shown in the install-CLI hint. */
     cli: string;
     /** Full sign-in command, e.g. "gh auth login". */
     command: string;
@@ -47,7 +47,7 @@ export interface ForgeDefinition {
     signIn: ForgeSignInCommand | null;
     /**
      * Public cloud hosts this forge owns exactly. A BOUNDED list, never an
-     * allowlist for self-hosted detection — self-hosted/Enterprise instances are
+     * allowlist for self-hosted detection - self-hosted/Enterprise instances are
      * recognized at runtime by the adapter's host probe, not by this field.
      */
     cloudHosts?: string[];