wicked-crew-api-types 0.10.0 → 0.19.0

package/index.d.ts

@@ -190,6 +190,66 @@ export interface AgentSession {
    * pre-populate the steer textarea when a gate arrives.
    */
   guidance?: string;
+  /**
+   * The run's delivery state (crew#393; api-types 0.18.0) — derived at DTO assembly on BOTH
+   * `GET /runs` and `GET /runs/:id`, so a run whose reviewable work is sitting uncommitted in
+   * its worktree can no longer look identical to one that delivered or had nothing to deliver:
+   *
+   *   - `'delivered'` — a PR was opened for this run (by the deliver phase, or post-hoc via
+   *     `POST /runs/:id/deliver`); `deliverUrl` carries the PR URL.
+   *   - `'stranded'`  — a COMPLETED repo-scoped run with no recorded PR whose worktree still
+   *     exists on disk AND carries work: reviewable work nobody lifted. Derived honestly for
+   *     OLD runs too — records written before this field existed strand exactly the same way.
+   *   - `'vacuous'`   — a COMPLETED repo-scoped run whose surviving worktree carries NO
+   *     contribution at all (crew#311: nothing uncommitted, no run-branch commit — units all
+   *     reached "done" while producing nothing). There is nothing to deliver; the recovery is a
+   *     retry launch (`POST /runs {"retryOf":"<id>"}`). Never silently green: this is the loud
+   *     spelling of the vacuous-completion class. Derived with the same two read-only git
+   *     instruments the engine's own evidence floor uses; any probe failure keeps `'stranded'`
+   *     (vacuity is only ever asserted on positive reads).
+   *   - `'none'`     — everything else: repo-less runs, non-terminal runs, failed/cancelled
+   *     runs, and completed runs whose worktree is gone.
+   *
+   * Always present on runs served by a 0.18.0+ daemon; absent only from an older server.
+   *
+   * ⚠ WIRE RESHAPE (0.17.0 → 0.18.0, NOT additive): 0.11.0–0.17.0 spelled this field as
+   * `delivery?: { kind: 'pull_request'; url: string }`. The object form is GONE — the state
+   * moved into this string and the URL into `deliverUrl`. A client reading `delivery?.url`
+   * must move to `deliverUrl`.
+   *
+   * FAILURE of a deliver phase is not spelled here; it is `units[].status === 'rejected'`
+   * plus `denial_reason` (crew#318's message), both already on the list wire.
+   */
+  delivery?: 'delivered' | 'stranded' | 'vacuous' | 'none';
+  /**
+   * The delivered PR's URL (crew#393; api-types 0.18.0) — present exactly when
+   * `delivery === 'delivered'`; absent otherwise (absence is the one spelling, never `null`).
+   *
+   * KNOWN LIMIT (inherited from 0.11.0): runs that delivered before a 0.11.0 daemon first saw
+   * their terminal frame have no durable `run.delivered` audit entry — they read as
+   * `'stranded'` while their worktree survives (post-hoc `POST /runs/:id/deliver` is
+   * idempotent against the existing branch) and `'none'` after it is cleaned up.
+   */
+  deliverUrl?: string;
+  /**
+   * The campaign this AD-HOC run was attached to at launch (`LaunchRunBody.campaignId`;
+   * wicked-studio#27, api-types 0.19.0) — daemon-joined at DTO assembly on `GET /runs` and
+   * `GET /runs/:id` from the launch record (audit trail), so it survives a daemon restart.
+   * ABSENT — never `null` — when the run was not attached (absence is the one spelling).
+   *
+   * NOT set on a campaign's own DAG-node runs: those are correlated through
+   * {@link Campaign.node_run_id} (their run ids are `{campaign}:{node}:a{attempt}`), and a
+   * caller-chosen `sessionId` may legally contain `:`, so id-shape parsing is unsound — read
+   * membership from the campaign, not from this field or the id.
+   */
+  campaign_id?: string;
+  /**
+   * The ad-hoc group label this run was launched under (`LaunchRunBody.groupLabel`;
+   * wicked-studio#27, api-types 0.19.0) — daemon-joined like {@link AgentSession.campaign_id}.
+   * ABSENT when the run is ungrouped. Runs sharing a label form one `RunGroup` on
+   * `GET /campaigns`.
+   */
+  group_label?: string;
 }
 
 /** An ordered unit of work within a run (`WorkUnit`). */
@@ -218,6 +278,14 @@ export interface WorkUnit {
   gate?: GateSpec | string;
   /** True when a pinned deterministic validator is attached to this unit. */
   has_validator_pin?: boolean;
+  /**
+   * True when this unit's backing phase declared `executes_code` (crew#311 / core#297 §2) —
+   * carried from the def at plan time. The engine's code-evidence floor holds such a unit to a
+   * worktree diff: a governed Creator unit with this flag cannot fold "done" over an untouched
+   * worktree. Additive and skip-if-false on the wire: absent on non-code units, on units planned
+   * before the field existed, and on an older engine.
+   */
+  executes_code?: boolean;
 }
 
 /** A run plus its ordered units (`SessionView`) — the shape `GET /runs` returns. */
@@ -359,7 +427,10 @@ export interface GateInfo {
   receivedAt: string;
 }
 
-/** Approve / reject payload for the steering gate (`POST /runs/:id/gate`). */
+/** Approve / reject payload for the steering gate (`POST /runs/:id/gate`). On a
+ *  `steering-author` propose gate, an approve — amend note or not — also LANDS the proposal
+ *  into the rules store and the 200 body carries a {@link SteeringLandingResult}; the amend
+ *  steers the RUN's continuation, never the landed rule text (crew#388). */
 export interface GateDecision {
   approve: boolean;
   amend?: string;
@@ -503,10 +574,39 @@ export interface CoreEvent {
   latencyMs?: number;
   /** workerStalled: silent seconds before the stall event fired. */
   stalledSecs?: number;
+  /**
+   * `workerStalled` / `workerStallEscalated` (DAEMON-SYNTHETIC, crew#287/crew#341): how long the
+   * run had been silent on the daemon's CoreEvent relay when the frame fired, ms. Distinguishes
+   * the daemon's synthetic `workerStalled` frame (this field) from the engine's PTY-path
+   * `workerStalled` event (`stalledSecs` above) — same `type` tag, different producers.
+   */
+  quietForMs?: number;
+  /** `workerStallEscalated` (crew#341): what the watchdog did — `'reassign'` | `'notify'`. */
+  action?: string;
+  /** `workerStallEscalated`: how the action ended — `'ok'` | `'failed'` | `'exhausted'`. */
+  outcome?: string;
+  /**
+   * `workerStallEscalated`: `true` when a human should look — the action failed, the automatic
+   * recovery budget is exhausted, or the configured action is `'notify'` (surface, don't touch).
+   * `false` means the platform recovered on its own; the narrator shows it, nobody is paged.
+   */
+  needsYou?: boolean;
+  /** `workerStallEscalated` (action `'reassign'`): automatic reassigns consumed for this run, this one included. */
+  escalations?: number;
+  /** `workerStallEscalated` (outcome `'failed'`): bounded excerpt of what the recovery call threw. */
+  error?: string;
   /** failureTriaged: the triage judge's decision. */
   decision?: string;
   /** failureTriaged: the judge's bounded reasoning. */
   analysis?: string;
+  // campaign* frames (DES-CAMPAIGN-001 / TH-9) — camelCase per event_to_json; the exact
+  // per-variant shapes are the CampaignEvent union below.
+  /** campaign* frames: the campaign id. */
+  campaign?: string;
+  /** campaignNode* frames: the node id within the campaign. */
+  node?: string;
+  /** campaignNodeStarted / campaignNodeAwaitingHuman: the node's attempt-keyed Run id. */
+  runId?: string;
   // assumptionRecorded (external-transform convention) — camelCase per event_to_json
   kind?: string;
   library?: string;
@@ -526,6 +626,63 @@ export interface CoreEvent {
  * named live, and a bundle assembled after a run cannot describe it in different
  * words than the operator watched it happen in. (FINDING-014)
  */
+/**
+ * The stall watchdog's DETECTION frame (crew#287; api-types 0.18.0 — previously daemon-local).
+ * DAEMON-SYNTHETIC: broadcast straight to `/ws` when a run in `executing` has been silent on the
+ * daemon's CoreEvent relay past `SystemSettings.workerStallMinutes` — never re-relayed through
+ * the engine, one frame per quiet period, re-armed by any new event for the run. Detection only:
+ * the run is not touched. (The engine's PTY-path event shares the `workerStalled` tag but
+ * carries `stalledSecs`; this frame carries `quietForMs`.)
+ *
+ * `type` aliases on purpose, not `interface`s: only anonymous object types satisfy `CoreEvent`'s
+ * index signature, which is what lets these frames flow through CoreEvent-typed broadcast seams.
+ */
+export type WorkerStalledFrame = {
+  type: 'workerStalled';
+  /** The stalled run's id. */
+  session: string;
+  /** The current unit ord, when any observed event or the run header named one. */
+  ord?: number;
+  /** How long the run has been silent when the frame fired, ms. */
+  quietForMs: number;
+};
+
+/**
+ * The stall watchdog's ESCALATION frame (crew#341; api-types 0.18.0). DAEMON-SYNTHETIC, emitted
+ * only when escalation is armed (`SystemSettings.workerStallEscalateMinutes` > 0 — OFF by
+ * default) and a detected stall stays silent past that threshold. Reports what the watchdog DID
+ * and how it ended, one escalation per quiet period:
+ *
+ * - `action: 'reassign'` — the wedged cursor unit was recycled in place (engine `reassignUnit`:
+ *   the stale turn is superseded, the session closed, the unit re-dispatched; queued operator
+ *   injects survive into the fresh turn). `outcome: 'ok' | 'failed' | 'exhausted'`.
+ * - `action: 'notify'` — surface loudly without touching the run (the fail-loud rung).
+ *
+ * `needsYou: true` marks the frames a human should act on (failed / exhausted / notify).
+ */
+export type WorkerStallEscalatedFrame = {
+  type: 'workerStallEscalated';
+  /** The stalled run's id. */
+  session: string;
+  /** The cursor unit's ord, when known. */
+  ord?: number;
+  /** How long the run had been silent when the watchdog escalated, ms. */
+  quietForMs: number;
+  /** What the watchdog did. */
+  action: 'reassign' | 'notify';
+  /** How it ended: `ok` (acted / surfaced), `failed` (the recovery call threw), `exhausted`
+   *  (the per-run automatic budget was already spent — nothing was attempted). */
+  outcome: 'ok' | 'failed' | 'exhausted';
+  /** True when a human should look; false = the platform recovered on its own. */
+  needsYou: boolean;
+  /** action `reassign`: the seat the unit was re-dispatched to, when known. */
+  cli?: string;
+  /** action `reassign`: automatic reassigns consumed for this run, this one included. */
+  escalations?: number;
+  /** outcome `failed`: bounded excerpt of what the recovery call threw. */
+  error?: string;
+};
+
 export interface RecordedEvent extends CoreEvent {
   /** Capture time, epoch millis — when core emitted the frame, not when it was read. */
   ts: number;
@@ -885,9 +1042,30 @@ export interface GovernancePolicy {
   retired?: boolean;
 }
 
+/**
+ * The steering-type vocabulary (STEERING program) — one sub-page per type in the studio's
+ * Steering surface. Enum-as-string on the wire; the engine's serde default is `architecture`,
+ * so a rule row written before the field existed reads back as an architecture rule.
+ */
+export type SteeringType =
+  | 'architecture'
+  | 'development'
+  | 'security'
+  | 'testing'
+  | 'operations'
+  | 'compliance'
+  | 'design-ux';
+
 /**
  * A prescriptive conformance rule (`wicked-governance::ConformanceRule`).
  * `rule_type`: `pattern` | `policy`. `severity`: `info` | `warn` | `error` | `critical`.
+ *
+ * STEERING (unified model): the wiki/rules model and the old policy model merged into ONE
+ * steering-rule model. The steering fields below are all optional on the wire — additive for
+ * older consumers, and ABSENT on rows served by a pre-steering engine (wicked-core-ts < 0.7.5),
+ * where absence reads as the serde defaults (`steering_type` architecture, `weight` 1.0, no
+ * enforcement half). A rule WITHOUT `effect` is recall-only, exactly as before the merge; a rule
+ * WITH one participates in decide()/select() the way a `GovernancePolicy` used to.
  */
 export interface ConformanceRule {
   id: string;
@@ -898,9 +1076,25 @@ export interface ConformanceRule {
   targets: { language?: string; layer?: string; framework?: string };
   symbol_ref?: string;
   compliance?: { framework: string; control_id: string };
+  /** Where the rule came from. Doc-ingested rules keep `path@sha#id` in `ref`; UI/chat-authored
+   *  rules carry `source: "ui"` / `source: "chat"` — first-class provenance, not second-class. */
   provenance: { source: string; ref?: string; source_kinds: string[] };
   /** Withdrawn from recall. Same contract as {@link GovernancePolicy.retired}. */
   retired?: boolean;
+  /** Which Steering sub-page this rule belongs to. Engine default: `architecture`. */
+  steering_type?: SteeringType;
+  /** Phases / tools this rule is selected for (inclusion — {@link GovernancePolicy.applies_to} semantics). */
+  applies_to?: string[];
+  /** Exclusion twin of `applies_to`: phases / tools this rule is NEVER selected for. */
+  excludes?: string[];
+  /** Ordering within a severity band + gate priority. Engine default: 1.0. */
+  weight?: number;
+  /** Enforcement half (from the retired policy model). Absent ⇒ the rule is recall-only. */
+  effect?: 'deny' | 'allow_with_conditions' | 'allow';
+  trigger?: { contains?: string };
+  obligations?: string[];
+  /** The frozen acceptance-criteria text (becomes a claim's `criteria` when the rule decides a gate). */
+  criteria?: string;
 }
 
 /** Facet query for `GET /governance/rules/preview`. All fields are optional. */
@@ -912,6 +1106,368 @@ export interface RulePreviewQuery {
   rule_type?: string;
 }
 
+/**
+ * Facet query for `GET /governance/rules` (the wiki BROWSE surface). Unlike
+ * {@link RulePreviewQuery} — whose recall semantics treat an absent rule facet as a wildcard
+ * match, enforcement's question — browse filters are EXACT matches over the listed rows
+ * ("show me the rules tagged `layer=api`"), and `status` keeps retired rules reachable so the
+ * kill switch stays visible (`all` is the default).
+ */
+export interface RuleBrowseQuery {
+  severity?: 'info' | 'warn' | 'error' | 'critical';
+  layer?: string;
+  rule_type?: 'pattern' | 'policy';
+  status?: 'active' | 'retired' | 'all';
+  /**
+   * Steering-type facet (the Steering sub-page's filter). Answers 501 on a pre-steering engine
+   * (wicked-core-ts < 0.7.5): rows there carry no `steering_type`, so an empty answer would
+   * impersonate "no rules of that type".
+   */
+  type?: SteeringType;
+  /**
+   * Boolean spelling of the retire filter: `true` ⇒ `status=all`, `false` ⇒ `status=active`.
+   * Mutually exclusive with `status` — sending both is a 400 (two spellings of one filter can
+   * contradict, and picking a winner silently would answer a question the caller didn't ask).
+   */
+  include_retired?: 'true' | 'false';
+}
+
+// ── Steering management (STEERING program) ──────────────────────────────────────
+
+/**
+ * One entry of a `POST /governance/steering/import` batch: either a frontmattered markdown
+ * document (`kind: 'doc'` — the same format `rules ingest --dir` consumes) or a ready rule
+ * object (`kind: 'rule'`). Every entry runs through the engine's ingest normalize/validate
+ * path, fail-closed PER ENTRY: one bad entry rejects alone, the rest still land.
+ */
+export type SteeringImportEntry =
+  | { kind: 'doc'; name?: string; content: string }
+  | { kind: 'rule'; rule: ConformanceRule };
+
+/** The `POST /governance/steering/import` request body (JSON — this daemon speaks no multipart). */
+export interface SteeringImportBody {
+  /** The page's inferred steering type, applied as the DEFAULT `steering_type` for entries that omit one. */
+  type?: SteeringType;
+  entries: SteeringImportEntry[];
+}
+
+/** Per-entry outcome of a steering import (same order as the submitted batch). */
+export interface SteeringImportResult {
+  /** Index into the submitted `entries` array. */
+  index: number;
+  /** The doc entry's `name`, when one was given. */
+  name?: string;
+  status: 'imported' | 'rejected';
+  /** Rule ids the entry minted (a doc can mint several; a rejected entry mints none). */
+  ids?: string[];
+  /** Why the entry was rejected (present only on `rejected`). */
+  error?: string;
+}
+
+/** The `POST /governance/steering/import` 200 body — 200 even with rejections: per-entry results ARE the answer. */
+export interface SteeringImportResponse {
+  results: SteeringImportResult[];
+  imported: number;
+  rejected: number;
+}
+
+/**
+ * The `POST /governance/steering/author` request body — "add with chat". Launches a governed
+ * authoring run (the `steering-author` workflow) that analyzes the named files/directories plus
+ * the operator's intent and emits PROPOSED steering rules at a human gate (the TH-12
+ * propose-as-gate pattern): the run PAUSES `awaiting_human` after the propose phase, and the
+ * operator approves/amends/rejects through the standard `POST /runs/:id/gate`. On APPROVE the
+ * daemon lands the proposal into the rules store with `provenance.source: "chat"` and the gate
+ * response carries a {@link SteeringLandingResult} — the run itself writes nothing to any store.
+ */
+export interface SteeringAuthorBody {
+  /** The operator's conversational intent — what steering to author, and why. */
+  instructions: string;
+  /** Default `steering_type` for the proposed rules (the page's inferred type). */
+  type?: SteeringType;
+  /** ABSOLUTE paths on the daemon host (files or directories) the run should analyze. */
+  paths?: string[];
+  /** Inline documents — written into the run's steering inbox on the daemon host and analyzed like `paths`. */
+  documents?: { name: string; content: string }[];
+  /** Registered repo to run within (the run analyzes that worktree's context too). */
+  repoRef?: string;
+  /** Stable run id; minted when omitted. */
+  sessionId?: string;
+}
+
+/** Where a landed steering proposal was read from, most-preferred first: the propose phase's
+ *  machine-readable artifact file, the propose unit's stored transcript, the cached gate prompt. */
+export type SteeringProposalSource = 'deliverable' | 'transcript' | 'gate-prompt';
+
+/**
+ * The `landing` field on the `POST /runs/:id/gate` (and gated `POST /runs/:id/resume`) 200 body
+ * — present ONLY when the approved gate was a `steering-author` propose gate (crew#388). It is
+ * how the skin learns the approved chat proposal actually reached the rules store — or, loudly,
+ * that it did not: on `failed` the run still advanced (the approve stands) but `error` carries
+ * the operator-readable reason, mirrored on the audit trail as
+ * `governance.steering.landing_failed`. Landed rules are audited per rule as
+ * `governance.rule.upserted` with the chat provenance. Idempotent: a replayed approve reports
+ * `alreadyLanded: true` and re-lands nothing. An approve WITH an amend note lands the proposal
+ * UNCHANGED — the amend steers the RUN, not the rule text. A reject lands nothing.
+ */
+export interface SteeringLandingResult {
+  outcome: 'landed' | 'failed';
+  /** Rule ids actually upserted (all of them on `landed`; the partial set on a partial `failed`). */
+  ruleIds: string[];
+  /** Where the proposal was read from. Absent when no source yielded one. */
+  source?: SteeringProposalSource;
+  /** `true` when a replayed approve found the durable landing marker — nothing was re-landed. */
+  alreadyLanded?: boolean;
+  /** Present iff `outcome: "failed"` — the loud, operator-readable reason. */
+  error?: string;
+}
+
+// ── Governance wiki management (scoreboard + meta) ─────────────────────────────
+
+/**
+ * Typing-coverage half of the wiki scoreboard — % of doctrine statements typed into
+ * enforcement classes. Doc-side by construction (the class lives in doc frontmatter, never on
+ * the rule node), so it is measurable only when the daemon was pointed at the same docs root
+ * `rules ingest --dir` used; otherwise `available` is `false` and `reason` says why.
+ */
+export interface WikiTypingCoverage {
+  available: boolean;
+  /** Why typing could not be measured (present only when `available` is `false`). */
+  reason?: string;
+  docs_scanned: number;
+  statements_total: number;
+  statements_typed: number;
+  /** `statements_typed / statements_total` in [0,100]; absent when the corpus mints no statements. */
+  percent?: number;
+  /** Typed statements per class (`policy` / `validator` / `guidance`). */
+  by_class: Record<string, number>;
+  /** Docs that mint statements but declare no class — the actionable backlog. */
+  docs_untyped: string[];
+}
+
+/** Connection-coverage half — do the active rules' `symbol_ref`s resolve, and are the links live? */
+export interface WikiConnectionCoverage {
+  rules_with_ref: number;
+  refs_resolving: number;
+  refs_unresolvable: number;
+  /** `refs_resolving / rules_with_ref` in [0,100]; absent when no rule carries a ref. */
+  percent?: number;
+  /** Active rules with at least one live `Governs` edge. */
+  rules_linked: number;
+}
+
+/** One rule's enforcement evidence (only rules with any evidence appear). */
+export interface WikiRuleEvidenceRow {
+  rule_id: string;
+  /** Distinct deny claims citing this rule (`evidenced_by` edges in). */
+  denial_claims: number;
+  /** Accumulated `evidence_count` across the rule's `Governs` edges. */
+  governs_evidence: number;
+}
+
+/** Enforcement evidence — gate denials citing wiki rules (retired rules included: a past denial
+ *  stays explicable after its rule retires, so its evidence stays countable). */
+export interface WikiEnforcementEvidence {
+  denial_claims: number;
+  rules_evidenced: number;
+  evidenced_by_edges: number;
+  governs_evidence_total: number;
+  /** Per-rule breakdown, most-evidenced first — the "which rules actually fire" list. */
+  per_rule: WikiRuleEvidenceRow[];
+}
+
+/** Recall volume — documented UNAVAILABLE in-band (an honest "cannot measure" beats a
+ *  fabricated zero); `reason` says why. */
+export interface WikiRecallVolume {
+  available: boolean;
+  reason: string;
+}
+
+/**
+ * The wiki population/connection scoreboard (`wicked-governance::Scoreboard`, AW-23/arch-R23) —
+ * the report that tells a populated wiki from an ingested-once-and-decaying one.
+ * Served by `GET /governance/wiki/scoreboard`; 501 when the installed engine addon predates the
+ * `governanceScoreboard` binding (wicked-core-ts ≥ 0.7.4).
+ */
+export interface GovernanceScoreboard {
+  rules_total: number;
+  rules_active: number;
+  rules_retired: number;
+  typing: WikiTypingCoverage;
+  connection: WikiConnectionCoverage;
+  evidence: WikiEnforcementEvidence;
+  recall_volume: WikiRecallVolume;
+}
+
+/**
+ * `GET /governance/wiki/meta` — the wiki's honest empty-state signal, cheap enough for the UI
+ * to call on mount. `ruleset_count` is `null` (not 0) when the installed engine build cannot
+ * count `RuleSet` rows: "no rulesets" is a real answer about a seeded store, and "cannot count"
+ * must never impersonate it.
+ */
+export interface GovernanceWikiMeta {
+  /** Any doctrine on the store at all (rules listable, or RuleSet rows counted). */
+  seeded: boolean;
+  ruleset_count: number | null;
+  /** Rules the engine lists (pre-0.7.4 addons list active rules only — the recall funnel). */
+  rule_count: number;
+  /** Whether `GET /governance/wiki/scoreboard` will answer 200 on this deployment. */
+  scoreboard_available: boolean;
+  /** The authoring guide / seed runbook the empty state points at. */
+  doc: string;
+}
+
+// ── Testing surface (crew-testing) — governance evals + eval corpora ───────────
+
+/**
+ * The behavior signals of one eval sample — the facts the governance decide path is asked to
+ * judge (mirrors the engine's decision inputs: run phase, tool invoked, files touched, content).
+ * All optional: a sample carries only the signals its behavior is about.
+ */
+export interface GovernanceEvalSignals {
+  phase?: string;
+  tool?: string;
+  files?: string[];
+  content?: string;
+}
+
+/**
+ * One eval sample: a described behavior (`kind: 'bad'` ⇒ the steering corpus SHOULD deny it,
+ * `'good'` ⇒ it should pass) tagged with the steering type it exercises. Field names are the
+ * engine's serde spelling (snake_case) — the report echoes them back verbatim.
+ */
+export interface GovernanceEvalSample {
+  id: string;
+  description: string;
+  kind: 'good' | 'bad';
+  steering_type: string;
+  signals: GovernanceEvalSignals;
+}
+
+/**
+ * The `POST /testing/evals/run` request body. `type` narrows the run to one steering type;
+ * `corpus` names an estate scope (`evals:<name>`, as minted by `POST /testing/corpora/import`);
+ * omitted, the engine runs its built-in default corpus.
+ */
+export interface RunGovernanceEvalsBody {
+  type?: SteeringType;
+  corpus?: string;
+}
+
+/** A near-miss rule on a `gap` verdict — the rule that ALMOST fired, with its similarity score. */
+export interface GovernanceEvalNearestRule {
+  rule_id: string;
+  similarity: number;
+}
+
+/**
+ * One sample's outcome. `expected` is derived from the sample's `kind` (`bad` ⇒ `deny`);
+ * `fired` lists the rule ids that actually fired; `verdict` is the comparison: `caught` (a bad
+ * behavior denied), `gap` (a bad behavior that sailed through), `false_positive` (a good
+ * behavior denied). `nearest_rules` is present on gaps (an empty array is allowed) — the
+ * remediation pointer for "which rule needs sharpening".
+ */
+export interface GovernanceEvalResult {
+  sample: Pick<GovernanceEvalSample, 'id' | 'description' | 'kind' | 'steering_type'>;
+  expected: 'deny' | 'allow';
+  fired: string[];
+  verdict: 'caught' | 'gap' | 'false_positive';
+  nearest_rules?: GovernanceEvalNearestRule[];
+}
+
+/** The report's roll-up counts (snake_case — the engine's serde output, passed through verbatim). */
+export interface GovernanceEvalSummary {
+  total: number;
+  caught: number;
+  gaps: number;
+  false_positives: number;
+}
+
+/**
+ * The `POST /testing/evals/run` 200 body — the engine's serde report passed through VERBATIM
+ * (snake_case field names, `degraded` spelled `null` when the run was full-fidelity;
+ * `'facet-only'` when the embedding side was unavailable and only facet matching ran).
+ */
+export interface GovernanceEvalReport {
+  results: GovernanceEvalResult[];
+  summary: GovernanceEvalSummary;
+  degraded: 'facet-only' | null;
+}
+
+/** The `POST /testing/corpora/import` request body — a named eval corpus for later runs. */
+export interface ImportEvalCorpusBody {
+  name: string;
+  samples: GovernanceEvalSample[];
+}
+
+/**
+ * The `POST /testing/corpora/import` 200 body. `scope` is the estate scope the samples landed
+ * under (`evals:<name>` — the string `RunGovernanceEvalsBody.corpus` names); `embedded` reports
+ * whether the samples were embedded for similarity matching (false ⇒ later runs degrade to
+ * facet-only).
+ */
+export interface ImportEvalCorpusResponse {
+  imported: number;
+  scope: string;
+  embedded: boolean;
+}
+
+/**
+ * The `POST /testing/recon` request body (api-types 0.15.0) — the Testing page's campaign-recon
+ * trigger. `problem` is the recon brief, passed to every launched run VERBATIM (the client owns
+ * the framing). The two optional fields are the multiscope wire, shared with
+ * {@link LaunchCampaignBody}:
+ *
+ *  - `repoRefs` — explicit codebase attachments: registered repo refs (ids; a unique repo NAME
+ *    also resolves), deduped; a ref that does not resolve fails the whole request with a 400
+ *    naming it.
+ *  - `projectId` — crew resolves the project's `crew.repo` members server-side (404 unknown
+ *    project; 400 when the project has zero repo members and no `repoRefs` cover for it) AND
+ *    files every launched run into the project (the `POST /runs` §2.2 semantics: atomic
+ *    membership + project-graph binding).
+ *
+ * BOTH ⇒ the union (`repoRefs` order first). NEITHER ⇒ one unscoped recon run — the launch the
+ * Testing page sent before this wire existed, unchanged.
+ *
+ * One engine run carries ONE repo, so a multi-repo recon FANS: one governed run per resolved
+ * repo, all under one shared campaign label (`TestingReconResponse.campaign`) — and a real fan
+ * (>= 2 repos) registers an ENGINE campaign under that same id, so `GET /campaigns` serves it
+ * (api-types 0.17.0, crew#390).
+ *
+ * Every launched sibling pauses at its INTAKE GATE (`human_confirm: before:1` — the launch
+ * banner's promise) by default; `ungated: true` is the EXPLICIT opt-out for an unattended fan
+ * (api-types 0.17.0, crew#391). It is never the silent default, and it is audited.
+ */
+export interface TestingReconBody {
+  problem: string;
+  projectId?: string;
+  repoRefs?: string[];
+  /** EXPLICITLY launch the siblings unattended (no intake gate). Default `false`: each sibling
+   *  pauses at its intake gate before any unit runs. */
+  ungated?: boolean;
+}
+
+/**
+ * The `POST /testing/recon` 201 body. `runIds` is the source of truth (`length >= 1` always —
+ * one run per resolved repo in the caller's order; exactly one for an unscoped recon); `runId`
+ * is its first entry, kept as the single-run spelling existing launch readers expect;
+ * `campaign` is the shared label every fanned run's `run.launched` audit entry carries — and,
+ * when `campaignRegistered` is `true`, the id of the ENGINE campaign the fan was filed under
+ * (`GET /campaigns/:id` serves it; the `runIds` are its nodes' attempt-0 run ids,
+ * `{campaign}:{node}:a0`). `campaignRegistered: false` = a single/unscoped recon, or an engine
+ * addon without the campaign bindings — the launch will NOT appear on `GET /campaigns`.
+ */
+export interface TestingReconResponse {
+  runId: string;
+  runIds: string[];
+  campaign: string;
+  /** Whether an engine campaign was registered for this launch (api-types 0.17.0). */
+  campaignRegistered: boolean;
+  /** Present only when the fan was campaign-registered with a `projectId` and filing a sibling
+   *  into the project failed — the runs are LIVE; re-attach via POST /projects/:id/members. */
+  projectAttachError?: string;
+}
+
 // ── Governance claims (crew#40/43) ─────────────────────────────────────────────
 
 /**
@@ -949,17 +1505,29 @@ export interface LaunchRunBody {
    */
   projectId?: string;
   /**
-   * Delivery mode (crew#293). `"pr"` ⇒ the daemon appends a hardened deliver Tool phase (push
-   * the run's branch, rebase onto origin's default branch, `gh pr create`; the PR URL is the
-   * phase output's last line) to a PER-RUN copy of the selected workflow def — the shared def
-   * is never mutated, and merge stays human. Requires `workflow`; sending `deliver` without it
-   * is a 400. Omit ⇒ no delivery phase.
+   * Delivery mode (crew#293, defaulting reworked by crew#393 / api-types 0.18.0).
+   *
+   * `"pr"` ⇒ the daemon appends a hardened deliver Tool phase (push the run's branch, rebase
+   * onto origin's default branch, `gh pr create`; the PR URL is the phase output's last line)
+   * to a PER-RUN copy of the selected workflow def — the shared def is never mutated, and
+   * merge stays human. Requires `workflow`; sending `deliver: "pr"` without one is a 400.
+   *
+   * `"none"` ⇒ explicitly no delivery phase (the run's work stays in its worktree and the run
+   * will read `delivery: 'stranded'` on the wire once completed — recoverable any time via
+   * `POST /runs/:id/deliver`).
    *
-   * NOTE for the next api-types release: added daemon-side first (workspace copy, 0.6.0 +
-   * crew#293) — fold into the published `LaunchRunBody` when 0.7.0 cuts. Optional, so the
-   * field is forward-additive on the wire (DES-STUDIO-001 §5.1).
+   * OMITTED ⇒ the daemon decides (crew#393): a repo-scoped launch (`repoRef` set) that names a
+   * CODE-WORK `workflow` — a def carrying at least one `executes_code` phase (feature, bug,
+   * migration; not chat/onboarding/recon defs, whose clean worktree the deliver script would
+   * fail loudly) — DEFAULTS to `"pr"`: a completed code run must end with a reviewable
+   * deliverable or an explicit decision not to. The daemon setting `deliverDefault: 'none'`
+   * flips that default off. Repo-less launches, free-text launches (no `workflow`, so there is
+   * no def to append the phase to), and read-only-workflow launches default to `"none"`.
+   *
+   * `"none"` is additive (0.18.0): an older daemon's launch schema rejects it with a 400 —
+   * omit the field entirely against pre-0.18 servers.
    */
-  deliver?: 'pr';
+  deliver?: 'pr' | 'none';
   /**
    * Retry lineage (DES-UX-001 §8.3, CREW-UX-3; api-types 0.8.0): the id of the run this
    * launch retries. Must name an EXISTING run id — an unknown id fails the launch (400 with
@@ -969,6 +1537,28 @@ export interface LaunchRunBody {
    * Omit when the launch is not a retry.
    */
   retryOf?: string;
+  /**
+   * Ad-hoc campaign attach (wicked-studio#27; api-types 0.19.0): file this run onto an EXISTING
+   * campaign's surface. Validated at launch, loudly: an unknown campaign id fails the launch
+   * with a 404 naming it (nothing is launched); a deployment whose engine addon lacks the
+   * campaign bindings answers 501 ("upgrade the engine", never "fix your request").
+   *
+   * The attach is daemon-side provenance ONLY (recorded in the `run.launched` audit entry,
+   * restart-durable, echoed as `AgentSession.campaign_id`): the run executes byte-identically
+   * to an unattached launch — it does NOT become a DAG node, is never scheduled, gated, or
+   * cancelled by the campaign, and the campaign's own lifecycle ignores it. It appears on the
+   * campaigns surface as a `Campaign.attached_runs` entry. Mutually exclusive with
+   * `groupLabel` (both ⇒ 400). Omit both for pre-0.19 behavior, byte for byte.
+   */
+  campaignId?: string;
+  /**
+   * Ad-hoc label grouping, created on first use (wicked-studio#27; api-types 0.19.0): runs
+   * launched with the same label form one group — no pre-registration, no scheduler, no DAG,
+   * no shared gates; pure provenance for "these sibling launches are one effort". 1–200
+   * chars. Served as a `RunGroup` row beside the campaigns on `GET /campaigns` and echoed as
+   * `AgentSession.group_label`. Mutually exclusive with `campaignId` (both ⇒ 400).
+   */
+  groupLabel?: string;
 }
 
 /**
@@ -988,6 +1578,45 @@ export interface SetGuidanceResult {
   guidance: string;
 }
 
+/**
+ * Response of `POST /runs/:id/deliver` (crew#393; api-types 0.18.0) — post-hoc delivery: lift a
+ * COMPLETED repo-scoped run's stranded worktree into a PR with the SAME hardened script the
+ * deliver phase runs (crew#293/#317: commit the run's work, refuse the default branch, rebase
+ * onto origin's default branch — a conflict fails LOUDLY with nothing pushed — push, `gh pr
+ * create`, and re-derive success from a real PR URL). Takes no body.
+ *
+ * Idempotent: a run that already delivered answers 200 with the SAME recorded `prUrl` — a second
+ * call never opens a second PR. Failure is loud, never silent: 404 (unknown run), 409 (run not
+ * completed / repo-less / worktree gone / a delivery already in flight / the script itself failed
+ * — the body's `error` carries the script's own words, e.g. the rebase-conflict message), 500
+ * (the script produced no verifiable PR URL, or could not be spawned).
+ */
+export interface DeliverRunResult {
+  prUrl: string;
+}
+
+/**
+ * The 409 body of `POST /runs/:id/resume` on a TERMINAL run (crew#311; api-types 0.18.0).
+ *
+ * The engine's `resume_run` no-ops on a completed/cancelled run and answers the status token, so
+ * the route used to reply `200 {"status":"cancelled"}` — on the exact runs an operator was trying
+ * to rescue, the recovery affordance read as "resume destroyed my run". A terminal run is now
+ * refused with 409 and the ACTUAL recovery named machine-readably:
+ *
+ *   - `'retry'`   — relaunch as a new run with `POST /runs {"retryOf":"<id>"}` (cancelled runs,
+ *     and completed runs with nothing liftable — including a `delivery: 'vacuous'` run, whose
+ *     units produced no work at all);
+ *   - `'deliver'` — the run completed with unlifted work in its worktree (`delivery:
+ *     'stranded'`): lift it with `POST /runs/:id/deliver`.
+ *
+ * A FAILED run is not terminal for resume: it re-enters at the cursor as before (200 + status).
+ */
+export interface ResumeRefusal {
+  /** Human-readable refusal naming the run's terminal status and the recovery, verbatim. */
+  error: string;
+  recovery: 'retry' | 'deliver';
+}
+
 // ── Governance types (crew#40/41) ──────────────────────────────────────────────
 
 /** Per-app breakdown within a `CoverageReport`. */
@@ -1177,6 +1806,47 @@ export interface SystemSettings {
    * the engine default `~/.wicked-worker`.
    */
   worker_config_root?: string;
+  /**
+   * The repo-scoped launch delivery DEFAULT (crew#393; api-types 0.18.0, additive). What a
+   * `POST /runs` with `repoRef` + a CODE-WORK `workflow` (a def with at least one
+   * `executes_code` phase) and NO explicit `deliver` resolves to: `'pr'` (the shipped default —
+   * completed code runs open their PR) or `'none'` (work stays in the worktree, surfaced as
+   * `delivery: 'stranded'`). Absent reads as `'pr'`. Never consulted when the launch body sets
+   * `deliver` explicitly, and never applied to repo-less, free-text, or read-only-workflow
+   * launches (those are always `'none'`).
+   */
+  deliverDefault?: 'pr' | 'none';
+  /**
+   * The stall watchdog's DETECTION threshold (crew#287; api-types 0.18.0 — previously a
+   * daemon-local extension): minutes a run in `executing` may go without ANY engine event on the
+   * daemon's relay before one synthetic `workerStalled` frame per quiet period is broadcast on
+   * `/ws`. Integer 1..1440; absent = the daemon default (15). Detection never touches the run.
+   */
+  workerStallMinutes?: number;
+  /**
+   * The stall watchdog's ESCALATION threshold (crew#341; api-types 0.18.0): quiet minutes before
+   * the watchdog ACTS on a detected stall (see {@link WorkerStallEscalatedFrame}). Integer
+   * 0..1440; **absent or 0 = escalation OFF — the shipped default** (the issue's design: automatic
+   * recovery on a run that is merely slow would be worse than the wedge). Values below
+   * `workerStallMinutes` escalate at the detection threshold — the ladder never acts before it
+   * has notified.
+   */
+  workerStallEscalateMinutes?: number;
+  /**
+   * What an armed escalation DOES (crew#341): `'reassign'` (default) recycles the wedged cursor
+   * unit in place — the engine supersedes the stale turn, closes the worker session, bumps the
+   * attempt, and re-dispatches (queued operator injects survive into the fresh turn);
+   * `'notify'` is the fail-loud rung — a `needsYou` `workerStallEscalated` frame + an audit
+   * entry, the run untouched.
+   */
+  workerStallEscalateAction?: 'reassign' | 'notify';
+  /**
+   * Per-run budget of AUTOMATIC reassigns (crew#341): integer 1..10, default 2. Once spent, a
+   * still-silent run gets `outcome: 'exhausted'` `needsYou` frames instead of further recovery —
+   * a worker that wedges deterministically must reach a human, not loop through seats forever.
+   * Ignored when `workerStallEscalateAction` is `'notify'`.
+   */
+  workerStallMaxEscalations?: number;
   /**
    * SKIN-OWNED preference blobs (crew#323). The settings store is shared: alongside the
    * engine's keys it carries the studio's own state — `studio.appearance` (accent/logo/theme),
@@ -1226,6 +1896,14 @@ export interface RequirementsPage {
   /** Which source served the corpus: the live estate store, or the evidence-gated
    *  `requirements_graph.json` snapshot, which can lag it by hours (FINDING-065). */
   source: 'store' | 'artifact';
+  /**
+   * Keys in `requirements_overrides.json` that matched NO requirement in the corpus. Operator
+   * edits are keyed by SymbolId (store) or `domain::reqId` (artifact); an estate id-scheme
+   * migration re-mints method/field SymbolIds, so overrides keyed by the old ids stop matching and
+   * would otherwise vanish silently. Non-zero means edits exist that no row is showing — re-run
+   * the annotation workflow, then re-apply or delete the stale keys.
+   */
+  orphanedOverrides?: number;
 }
 
 export interface RequirementPatch {
@@ -1239,7 +1917,11 @@ export interface RequirementPatch {
 export interface BlastRadius {
   target: string;
   dependents: Array<{ id: string; name: string; kind: string; file: string; line: number }>;
-  /** Unresolved call-sites referencing the target — absence of dependents never means "safe". */
+  /**
+   * References to the target that no resolver bound (ENGINE-CONTRACT §2.1). Repeat call-sites of
+   * an already-bound relationship are NOT counted, so 0 is a legitimate value for a fully-resolved
+   * hot symbol. When non-zero, an empty `dependents` still never means "safe".
+   */
   unresolved: number;
 }
 
@@ -1349,6 +2031,57 @@ export interface AttachMemberBody {
   attachedBy?: 'studio' | 'interactive' | 'cli' | 'api';
 }
 
+/**
+ * The crew half of a governed doc delete (crew#338) — what
+ * `DELETE /projects/:projectId/interactive/docs/:doc` did to crew's four handoff ledgers
+ * (`interactive-{draft,edit,chat,demo}-ledger.json`). Present on every answer of that route so
+ * a partial result can never hide.
+ */
+export interface InteractiveDocDeleteLedgerReport {
+  /** True iff every ledger was swept without error. On the 502 refusal paths this is false with
+   *  `skipped: true` — the sweep deliberately did not run because interactive's half did not
+   *  happen (nothing diverged). */
+  ok: boolean;
+  /** Every replay-dedup row key actually dropped (`<doc>`, `<doc>:v<n>`, `<doc>:m:<id>`, …).
+   *  Empty ⇒ nothing was there — deleting a never-drafted doc is a clean no-op on this side. */
+  removed_keys: string[];
+  /** The ledgers that could NOT be swept, by seam name (`draft`|`edit`|`chat`|`demo`) and cause.
+   *  Present only when `ok` is false and the sweep actually ran. */
+  errors?: { ledger: string; error: string }[];
+  /** True ⇒ the sweep was deliberately skipped (interactive refused/failed the retire, so
+   *  crew's rows are still doing their job and nothing diverged). */
+  skipped?: boolean;
+}
+
+/**
+ * `DELETE /projects/:projectId/interactive/docs/:doc` (crew#338) — 200: the bridge's own retire
+ * answer (interactive#189's wire, relayed verbatim) plus crew's ledger report. The route's
+ * non-200 answers carry `error` plus the same `ledger` report (404 unknown doc — the ledger is
+ * STILL swept, cleaning ghosts of hand-deleted workspaces, but ONLY on the retire wire's own
+ * 404 body `{"error":"unknown doc"}`; 500 partial — interactive retired but the sweep failed,
+ * the body names both halves; 502 — interactive did not retire (5xx, unreachable, or a 404
+ * without the wire's body from a bridge predating the retire route), nothing swept; 409 — the
+ * bridge's build-in-flight refusal relayed verbatim, no `ledger` field).
+ */
+export interface InteractiveDocDeleteResponse {
+  /** The doc name (slug). */
+  name: string;
+  kind: 'doc' | 'html' | 'source' | 'demo';
+  retired: true;
+  /** True on a repeat delete — idempotent, with the ORIGINAL `retired_at` and no `event_id`. */
+  already_retired: boolean;
+  /** ISO-8601 retirement timestamp. */
+  retired_at: string;
+  /** Head version at retirement. */
+  head: number;
+  /** Lineage size at retirement. */
+  versions: number;
+  /** The `wicked.interactive.doc.retired` bus event id — first retire only (no re-emit). */
+  event_id?: number;
+  /** What crew dropped from its handoff ledgers. */
+  ledger: InteractiveDocDeleteLedgerReport;
+}
+
 /**
  * One normalized entry of the merged project activity feed
  * (`GET /projects/:id/activity`, ADR §5.2): core events of member runs/chats
@@ -1419,3 +2152,569 @@ export interface ChatOpenBody {
   /** File the chat into a project (`crew.chat` membership, attached on open). */
   projectId?: string;
 }
+
+// ── Project code graph (DES-PROJECT-001; the co-located multi-repo graph) ──────
+//
+// A project's `crew.repo` members indexed into ONE wicked-estate database, each under a stable
+// label, so one query answers over every repo the project contains.
+//
+// THE LIMIT, stated on the wire because it is not obvious from the results: this is CO-LOCATION,
+// NOT LINKAGE. estate resolves edges within a labelled repo's own nodes only, exactly as if each
+// repo sat in its own database. `studio → wicked-crew-api-types → crew` does NOT traverse; what
+// these shapes carry is per-repo results gathered in one place, with the repo named on every hit.
+// Every response repeats it in `linkage` + `note` so a consumer cannot read a cross-repo answer as
+// a cross-repo TRACE.
+
+/** Co-location, never linkage — a single-valued field so a future linked mode is additive. */
+export type ProjectGraphLinkage = 'co-located';
+
+/**
+ * Why a project graph cannot answer, or the terms on which it can.
+ *
+ * - `ready` — indexed, two or more repos.
+ * - `ready-single-repo` — indexed, exactly one repo: answers are correct but can never be
+ *   cross-repo, which a caller asking a project-scoped question needs told.
+ * - `no-repo-members` — the project has no `crew.repo` member. Not an error and not an empty
+ *   graph: there is nothing to build one from.
+ * - `not-indexed` — it has repo members and no database yet. `POST /projects/:id/graph/refresh`
+ *   is the fix, and the `detail` says so.
+ * - `engine-too-old` — the running wicked-core addon does not publish `code_graph_db` on the repo
+ *   record (wicked-core#170), so its repo-record contract predates this surface.
+ */
+export type ProjectGraphState =
+  | 'ready'
+  | 'ready-single-repo'
+  | 'no-repo-members'
+  | 'not-indexed'
+  | 'engine-too-old';
+
+/** One member repo's standing in the project graph. */
+export interface ProjectGraphRepo {
+  /** Registry id (`RepoEntry.id`) — the member ref this came from. */
+  repoId: string;
+  /** The estate label its rows carry, and the prefix on every `file` path it contributes. */
+  label: string;
+  rootPath: string;
+  /** `false` ⇒ its symbols are NOT in the graph; `reason` says why and results stay partial. */
+  indexed: boolean;
+  /** Commit indexed, when git could answer. */
+  head?: string;
+  /** Unix millis of the index that put these rows in. */
+  indexedAt?: number;
+  /**
+   * Present when `indexed` is false: registry miss, index failure, never refreshed, or the rows
+   * under this label were indexed from a DIFFERENT root than the registry now names (a repo that
+   * moved — wicked-estate binds a label to the root it first saw and refuses to rebind it, so the
+   * graph keeps the old checkout's symbols until the project graph is rebuilt).
+   */
+  reason?: string;
+  /**
+   * The action that actually resolves THIS cause, when one action does. Carried per-row because
+   * the causes do not share a remedy: "never refreshed" and "attached since the last refresh" are
+   * fixed by a refresh, a DANGLING member ref is not (the registry no longer knows the ref, so a
+   * refresh indexes nothing new), and a MOVED root needs a rebuild when estate refuses to rebind
+   * the label. Absent ⇒ no single action fixes it, or `reason` already spells the remedy out.
+   * Never assume a refresh: telling an operator mid-incident to run one that cannot work costs
+   * them the time it takes to run it and the trust to believe the next message.
+   */
+  remedy?: string;
+}
+
+/** `GET /projects/:id/graph` — what the project graph holds and what it cannot answer. */
+export interface ProjectGraphStatus {
+  projectId: string;
+  state: ProjectGraphState;
+  /** One sentence naming the state's cause and its remedy. Always present, never empty. */
+  detail: string;
+  /** Absolute path of the co-located database; `null` when there is none to point at. */
+  dbPath: string | null;
+  repos: ProjectGraphRepo[];
+  /** Member repos absent from the graph — any answer is PARTIAL while this is non-empty. */
+  missingRepos: string[];
+  /** Labels still in the database whose repo is no longer a member; excluded from results. */
+  staleRepos: string[];
+  linkage: ProjectGraphLinkage;
+  note: string;
+  /** Unix millis of the last refresh; `null` when never refreshed. */
+  updatedAt: number | null;
+}
+
+/**
+ * `POST /projects/:id/graph/refresh` body. Optional — an empty body is the plain incremental
+ * refresh.
+ *
+ * `force: true` exists for MIGRATION, not for routine use: the plain refresh skips any member repo
+ * whose clean checkout is still at the HEAD the manifest recorded, so after a wicked-estate upgrade
+ * an UNCHANGED repo never re-indexes and its rows keep the old binary's id scheme and unresolved
+ * accounting (ENGINE-CONTRACT §2.1) indefinitely. Force bypasses that skip for every member repo
+ * AND passes `--force` to `wicked-estate index`, so estate performs a full re-extract even when its
+ * own incremental digest would skip. Expect it to take as long as the project's first build.
+ */
+export interface RefreshProjectGraphBody {
+  /** Re-index every member repo, bypassing the clean-HEAD skip and estate's digest skip. */
+  force?: boolean;
+}
+
+/**
+ * One member repo's outcome in a refresh — why it did or did not index. `skipped-head-unchanged`
+ * is the row an operator reads when asking why a repo did not migrate after an estate upgrade:
+ * the plain refresh trusts a clean checkout at the manifest's HEAD, so only `force` (or a new
+ * commit) makes that repo re-index.
+ */
+export interface ProjectGraphRefreshRepo {
+  repoId: string;
+  /** The estate label its rows carry. */
+  label: string;
+  /** What this refresh did with the repo. */
+  action: 'indexed' | 'skipped-head-unchanged' | 'failed';
+  /**
+   * Bounded tail (last 2 KiB) of `wicked-estate index` stderr, present when the binary said
+   * anything — notably estate's id_scheme migration notice explaining why a refresh that used to
+   * skip in a second ran a full re-extract for minutes.
+   */
+  stderrTail?: string;
+  /** Present when `action` is `failed` — the same message the `failed` array carries. */
+  error?: string;
+}
+
+/** `POST /projects/:id/graph/refresh` — an incremental (re)build, repo by repo. */
+export interface ProjectGraphRefreshResult {
+  status: ProjectGraphStatus;
+  /** Labels re-indexed this run. */
+  indexed: string[];
+  /** Labels skipped because the checkout is clean and its HEAD is already in the graph. */
+  skipped: string[];
+  /** Repos that failed to index, with the reason; the graph keeps whatever it already had. */
+  failed: Array<{ repoId: string; label: string; error: string }>;
+  /** Per-repo outcomes with the WHY (and any index stderr) attached — one row per member repo. */
+  repos?: ProjectGraphRefreshRepo[];
+}
+
+/** One hit, always attributed: a cross-repo answer that does not say WHERE is not an answer. */
+export interface ProjectGraphHit {
+  /** The repo's registry id. */
+  repoId: string;
+  /** The repo's estate label. */
+  repo: string;
+  /** estate SymbolId — carries the label, so it is unique across the project. */
+  id: string;
+  /**
+   * The graph node's name, VERBATIM from estate. For a `kind: 'file'` node that name IS the
+   * label-prefixed path (`wicked-vault/src/vault/vault.mjs`) — left as estate minted it, because
+   * rewriting it would produce a name that resolves to nothing. Use `repo` + `file` to display it.
+   */
+  name: string;
+  kind: string;
+  /** REPO-RELATIVE path, label stripped — the same spelling `/repos/:id/graph` returns. */
+  file: string;
+  line: number;
+}
+
+/** Per-repo hit counts, so "which repo does this touch" is answerable without scanning hits. */
+export interface ProjectGraphRepoCount {
+  repoId: string;
+  repo: string;
+  count: number;
+}
+
+/** `GET /projects/:id/graph/blast-radius?name=` — dependents across every member repo. */
+export interface ProjectBlastRadius {
+  projectId: string;
+  target: string;
+  dependents: ProjectGraphHit[];
+  byRepo: ProjectGraphRepoCount[];
+  /**
+   * References to the target that no resolver bound (ENGINE-CONTRACT §2.1). Repeat call-sites of
+   * an already-bound relationship are NOT counted, so 0 is a legitimate value for a fully-resolved
+   * hot symbol. When non-zero, an empty `dependents` still never means "safe".
+   */
+  unresolved: number;
+  /** Labels actually covered by this answer. */
+  reposSearched: string[];
+  /** Member repos NOT covered — the answer is partial while this is non-empty. */
+  missingRepos: string[];
+  linkage: ProjectGraphLinkage;
+  note: string;
+}
+
+/** `GET /projects/:id/graph/search?name=` — exact-name symbol resolution across member repos. */
+export interface ProjectGraphSearch {
+  projectId: string;
+  query: string;
+  matches: ProjectGraphHit[];
+  byRepo: ProjectGraphRepoCount[];
+  reposSearched: string[];
+  missingRepos: string[];
+  linkage: ProjectGraphLinkage;
+  /**
+   * Carries the co-location limit AND the matching rule: this is EXACT-NAME resolution, so an
+   * empty `matches` means "no symbol by that exact name" and never "not in this project". A
+   * partial or fuzzy name returns nothing even when the symbol exists.
+   */
+  note: string;
+}
+
+// ── Campaigns (DES-CAMPAIGN-001 / crew#342 slice 1 + TH-9) ───────────────────
+// The engine's Campaign scheduler — a durable, crash-resumable, dependency-aware parallel DAG of
+// governed Runs — exposed over `/api/v1/campaigns`. The GET routes return the ENGINE's persisted
+// shapes verbatim (wicked-core `src/campaign.rs` serde: snake_case fields, snake_case enum
+// tokens), same doctrine as `SessionView`: one producer of the wire shape, zero re-spelling in
+// the daemon. The POST body (`LaunchCampaignBody`) is the daemon's own camelCase request contract
+// — crew maps it onto the engine def, composing one Tool-executor workflow per deterministic
+// scenario (spec FILE PATHS on the argv, never scenario bodies — the 1022-byte PTY prompt trap).
+
+/** Per-node lifecycle status. Terminal = `completed` | `failed` | `blocked` | `cancelled`. */
+export type CampaignNodeStatus =
+  | 'pending'
+  | 'ready'
+  | 'running'
+  | 'awaiting_human'
+  | 'ready_to_resume'
+  | 'completed'
+  | 'failed'
+  | 'blocked'
+  | 'cancelled';
+
+/** Campaign lifecycle status — also the token `POST /campaigns/:id/resume` / `/cancel` resolve to. */
+export type CampaignStatus =
+  | 'running'
+  | 'paused'
+  | 'completed'
+  | 'partially_completed'
+  | 'failed'
+  | 'cancelled';
+
+/** When a dependency edge is satisfied: dep `completed` only, or any terminal outcome. */
+export type CampaignEdgeCondition = 'on_success' | 'on_terminal';
+
+/** How a node failure propagates (DES-CAMPAIGN-001 §5.2). */
+export type CampaignFailurePolicy = 'fail_fast' | 'continue_independent' | 'human_gate_on_failure';
+
+/**
+ * What one campaign node runs — the engine's reusable Run specification (mirrors a launch minus
+ * the session id, which the scheduler derives as `{campaign}:{node}:a{attempt}`). A node inherits
+ * governance, worktree isolation, HITL gates, live output, and per-Run resume from the Run it is.
+ */
+export interface CampaignRunSpec {
+  /** The free-text problem this node's Run decomposes — for a scenario node, a short human label
+   *  (the scenario body lives in its spec FILE; it is never inlined here). */
+  problem: string;
+  /** The council roster (`AgenticCli` seats) convened for this node's Run. */
+  clis: unknown[];
+  entity_mode: EntityMode;
+  /** The node's internal human-confirm gate policy (engine serde shape); absent = none. */
+  human_confirm?: unknown;
+  /** The registered repo the node's Run targets, if any (creates an isolated worktree). */
+  repo_ref?: string | null;
+  /** The registered `WorkflowDef` id this node's Run follows — for a deterministic scenario node,
+   *  the per-node composed Tool workflow (`campaign-<campaign>-<node>`). */
+  workflow_id?: string | null;
+}
+
+/** A schedulable unit of the DAG — one node = one governed core Run. */
+export interface CampaignNode {
+  /** Stable node id, unique within the campaign (never contains `:` — it keys the run id). */
+  node_id: string;
+  run_spec: CampaignRunSpec;
+}
+
+/** A dependency edge `from -> to`: `to` becomes eligible once `from` satisfies `condition`. */
+export interface CampaignEdge {
+  from: string;
+  to: string;
+  condition: CampaignEdgeCondition;
+}
+
+/** The static campaign definition — validated at launch (cycle / empty / duplicate-edge /
+ *  unknown-endpoint rejects) and persisted verbatim inside the live {@link Campaign}. */
+export interface CampaignDef {
+  id: string;
+  name: string;
+  nodes: CampaignNode[];
+  edges: CampaignEdge[];
+  policy: CampaignFailurePolicy;
+  /** Global concurrency cap (>= 1) — a resource guard on parallel worktrees + CLI subprocesses. */
+  max_concurrency: number;
+}
+
+/**
+ * The live campaign instance (`GET /campaigns`, `GET /campaigns/:id`) — durable and
+ * crash-resumable; the scheduler re-derives the ready set from these persisted statuses on
+ * resume, never re-running a completed node.
+ */
+export interface Campaign {
+  id: string;
+  def_id: string;
+  status: CampaignStatus;
+  /** The full definition, embedded so a resume needs no second store. */
+  def: CampaignDef;
+  node_status: Record<string, CampaignNodeStatus>;
+  /**
+   * node_id -> live Run id, always `{campaign}:{node}:a{attempt}` (attempt-keyed, idempotent).
+   *
+   * These values ARE the engine session ids: a node's run is an ordinary governed run, so it is
+   * served by `GET /runs` / `GET /runs/:id` under exactly this id, and every session-scoped
+   * CoreEvent frame on `/ws` carries it as `session` (the `campaignNodeStarted` /
+   * `campaignNodeAwaitingHuman` frames additionally spell it as `runId`). Live narration for a
+   * campaign card is therefore a pure client-side correlation:
+   * `frame.session === campaign.node_run_id[node]` — no extra wire, no per-node fetch
+   * (wicked-studio#27).
+   */
+  node_run_id: Record<string, string>;
+  /** node_id -> 0-based attempt counter (a `human_gate_on_failure` Retry bumps it). */
+  node_attempt: Record<string, number>;
+  /** Persisted amend text of an approved-but-unslotted per-node gate decision (crash-safe). */
+  pending_decision_amend: Record<string, string | null>;
+  /** `human_gate_on_failure` queue — failed nodes awaiting a Retry/Skip/Abort decision. */
+  pending_failure_gates: string[];
+  /** Whether a fail-fast (or Abort) tripped — finalization lands on `failed`. */
+  fail_fast_tripped: boolean;
+  /**
+   * Per-node delivery (wicked-studio#27; api-types 0.19.0) — DAEMON-JOINED at DTO assembly on
+   * `GET /campaigns` and `GET /campaigns/:id`, never engine-persisted: the exact same
+   * `delivery`/`deliverUrl` derivation every run already carries on the runs wire
+   * (`AgentSession.delivery`, crew#393/#311), keyed by node_id like {@link Campaign.node_status}.
+   * A node appears here once its current-attempt run (`node_run_id[node]`) exists on the store —
+   * a still-pending node has no entry. With `node_run_id` + `node_status`, this is everything a
+   * "N of M delivered" rollup needs from ONE campaigns fetch — no per-node run fetch, and no
+   * dependence on the runs list's archived-run filtering. ABSENT only from a pre-0.19 daemon.
+   */
+  node_delivery?: Record<string, CampaignNodeDelivery>;
+  /**
+   * Ad-hoc runs attached to this campaign at launch (`LaunchRunBody.campaignId`;
+   * wicked-studio#27, api-types 0.19.0) — DAEMON-JOINED like {@link Campaign.node_delivery},
+   * launch order. These are NOT DAG nodes: the campaign's scheduler and lifecycle ignore them;
+   * each entry is an independent governed run that an operator filed onto this campaign's
+   * surface. Absent from a pre-0.19 daemon; `[]` when none. Narration correlation is the same
+   * as for nodes: each `runId` is the engine session id on `/ws` frames (`frame.session`).
+   */
+  attached_runs?: AttachedRunView[];
+}
+
+/**
+ * One member's delivery snapshot on the campaigns surface (wicked-studio#27; api-types 0.19.0)
+ * — the same tri-state + URL contract as `AgentSession.delivery`/`deliverUrl` (crew#393/#311),
+ * derived by the same code at DTO assembly. `deliverUrl` present exactly when
+ * `delivery === 'delivered'`.
+ */
+export interface CampaignNodeDelivery {
+  delivery: 'delivered' | 'stranded' | 'vacuous' | 'none';
+  deliverUrl?: string;
+}
+
+/**
+ * An ad-hoc run on the campaigns surface (wicked-studio#27; api-types 0.19.0) — a member of
+ * `Campaign.attached_runs` or `RunGroup.runs`. `runId` is the engine session id: the run is
+ * served in full by `GET /runs/:id`, and live `/ws` CoreEvent frames for it carry it as
+ * `session`. `status`/`delivery`/`deliverUrl` are snapshots of the same fields the run wire
+ * serves, so a rollup needs no second fetch.
+ */
+export interface AttachedRunView {
+  runId: string;
+  status: SessionStatus;
+  delivery: 'delivered' | 'stranded' | 'vacuous' | 'none';
+  deliverUrl?: string;
+}
+
+/**
+ * An ad-hoc label group (wicked-studio#27; api-types 0.19.0): the runs launched with the same
+ * `LaunchRunBody.groupLabel`, in launch order. NOT an engine campaign — no DAG, no scheduler,
+ * no status of its own (derive a rollup from the members); it exists the moment the first run
+ * is launched under the label. Served beside the campaigns in `CampaignsListResponse.groups`.
+ */
+export interface RunGroup {
+  label: string;
+  runs: AttachedRunView[];
+}
+
+/**
+ * `GET /campaigns` 200 body (api-types 0.19.0 — `groups` is ADDITIVE: a pre-0.19 daemon sends
+ * only `campaigns`). One fetch answers the whole grouping surface: engine campaigns (each
+ * carrying its own per-node rollup fields) plus the ad-hoc label groups.
+ */
+export interface CampaignsListResponse {
+  campaigns: Campaign[];
+  groups: RunGroup[];
+}
+
+/**
+ * One scenario of `POST /campaigns` — the daemon maps each onto a {@link CampaignNode}.
+ *
+ * Exactly one of `tool` / `agent` per scenario:
+ *  - `tool` (deterministic): the daemon composes a single-phase Tool-executor workflow running
+ *    `cmd` verbatim (no council, no LLM). Every argv token must be a single line of ≤ 1022
+ *    bytes — pass the scenario/spec as a FILE PATH argument, never inline its body. A body
+ *    smuggled into the argv is rejected with a 400 naming the offending token.
+ *  - `agent` (exploratory/authoring): a governed agent run over `problem` — same byte
+ *    discipline, because the problem text reaches PTY workers as prompt material.
+ */
+export interface CampaignScenario {
+  /** Node id, unique within the campaign (letters/digits/dots/hyphens/underscores; no `:`). */
+  id: string;
+  /** Short human label for the scoreboard; defaults to the id. NOT the scenario body. */
+  title?: string;
+  /** Ids of scenarios that must reach `depsCondition` before this one dispatches. */
+  deps?: string[];
+  /** Edge condition applied to every dep edge of this scenario (default `on_success`). */
+  depsCondition?: CampaignEdgeCondition;
+  /** Deterministic execution: argv run by the engine's Tool executor, file paths not bodies. */
+  tool?: { cmd: string[] };
+  /** Governed agent execution: the problem statement (short — reaches workers as a prompt). */
+  agent?: { problem: string; workflow?: string };
+  /** Registered repo this node runs within (isolated worktree). Omit for a repo-less node. */
+  repoRef?: string;
+}
+
+/** `POST /campaigns` request body → 201 {@link LaunchCampaignResponse}. */
+export interface LaunchCampaignBody {
+  /** Campaign id (also the def id). Defaults to a generated `campaign-<uuid>`. */
+  id?: string;
+  name?: string;
+  scenarios: CampaignScenario[];
+  /** Failure propagation policy (default `continue_independent`). */
+  policy?: CampaignFailurePolicy;
+  /** Global concurrency cap, >= 1 (default 2). */
+  maxConcurrency?: number;
+  /** JSON array of `AgenticCli` seats for agent scenarios; defaults to the daemon roster. */
+  clisJson?: string;
+  /**
+   * The multiscope wire (api-types 0.15.0), shared with `POST /testing/recon`: scope the launch
+   * to a PROJECT — crew resolves the project's `crew.repo` members server-side. Unknown project
+   * ⇒ 404; a project with zero repo members (and no `repoRefs` to fall back on) ⇒ 400 naming
+   * the fix. Combined with `repoRefs` ⇒ the union. Because one campaign node runs against ONE
+   * repo, every scenario that does not pin its own `repoRef` is FANNED — one node per resolved
+   * repo, same campaign — and the 201 body carries the fanned nodes' run ids (`runIds`).
+   * Omit both fields ⇒ the launch behaves exactly as before (backward compatible).
+   */
+  projectId?: string;
+  /**
+   * The multiscope wire (api-types 0.15.0): explicit codebase attachments — registered repo
+   * refs (ids; a unique repo NAME also resolves), deduped, min 1 when present. A ref that does
+   * not resolve fails the WHOLE launch with a 400 naming it — never a silently narrowed scope.
+   */
+  repoRefs?: string[];
+}
+
+/**
+ * `POST /campaigns` 201 body. `runIds` is ADDITIVE (api-types 0.15.0): present exactly when
+ * the launch used the multiscope fields (`projectId`/`repoRefs`), carrying the attempt-0 run
+ * ids (`{campaign}:{node}:a0`) of the launch's nodes — repo-major over the fanned scenarios
+ * (repos in resolved input order), then the scenarios that pinned their own `repoRef`.
+ * Consumers treat `runIds.length >= 1` as the source of truth for what launched; a legacy
+ * body keeps the legacy `{ campaignId }` answer.
+ */
+export interface LaunchCampaignResponse {
+  campaignId: string;
+  runIds?: string[];
+}
+
+/**
+ * The 11 campaign frames of the `/ws` stream (wicked-core `event_to_json`, camelCase tags), as a
+ * discriminated union for consumers that narrow on `type` — the TH-14 scoreboard renders node
+ * status from exactly these. They also flow through the permissive {@link CoreEvent}; the daemon
+ * relay is allowlist-free, so every frame below reaches `/ws` clients byte-for-byte.
+ */
+export type CampaignEvent =
+  | { type: 'campaignLaunched'; campaign: string }
+  | { type: 'campaignNodeReady'; campaign: string; node: string }
+  | { type: 'campaignNodeStarted'; campaign: string; node: string; runId: string }
+  | { type: 'campaignNodeAwaitingHuman'; campaign: string; node: string; runId: string; prompt: string }
+  | { type: 'campaignNodeCompleted'; campaign: string; node: string }
+  | { type: 'campaignNodeFailed'; campaign: string; node: string }
+  | { type: 'campaignNodeBlocked'; campaign: string; node: string }
+  | { type: 'campaignPaused'; campaign: string }
+  | { type: 'campaignCompleted'; campaign: string }
+  | { type: 'campaignFailed'; campaign: string }
+  | { type: 'campaignCancelled'; campaign: string };
+
+// ── Diagnostics (api-types 0.16.0) ──────────────────────────────────────────────
+
+/**
+ * Component versions of the running deployment (`GET /diagnostics`). The honesty rule of the
+ * whole diagnostics surface: a version the daemon cannot determine is `null` — never guessed.
+ */
+export interface DiagnosticsComponents {
+  /** The wicked-crew daemon's own package version (always known). */
+  crew: string;
+  /** The bundled studio SPA's version, read from the manifest the bundle ships
+   *  (`testid-inventory.json` → `studioVersion`); `null` on a headless daemon or a bundle
+   *  that predates the manifest. */
+  studioBundle: string | null;
+  /** The installed `wicked-core-ts` engine binding's version; `null` when unresolvable. */
+  coreTs: string | null;
+  /** Engine binary versions via `--version`, keyed by binary name (`wicked-core`,
+   *  `wicked-estate`) — probed ONLY through paths crew already resolves (`WICKED_CORE_EXE`,
+   *  bare PATH name); `null` per binary when unresolved or the probe fails. */
+  engineBinaries: Record<string, string | null>;
+}
+
+/** Daemon process runtime facts (`GET /diagnostics`). */
+export interface DiagnosticsDaemon {
+  /** Milliseconds since this daemon process started. */
+  uptimeMs: number;
+  /** Epoch ms the process started (now − uptime). */
+  startedAt: number;
+  /** The actually-bound HTTP port (honours --port / CREW_PORT / port 0). */
+  port: number;
+}
+
+/** One store file (or dir, sized as a content total) under the daemon's state home. Paths and
+ *  sizes only — file contents never ride this wire. */
+export interface DiagnosticsStoreFile {
+  /** Filename relative to the state home (`core.db`, `core.db-wal`, `core.db.events`, …). */
+  name: string;
+  /** Absolute path. */
+  path: string;
+  /** File size, or the total of a directory's contents (the events dir). */
+  bytes: number;
+}
+
+/** One captured error-level line from the daemon's own log ring (`GET /diagnostics`). */
+export interface DiagnosticsRecentError {
+  /** Epoch ms the line was logged. */
+  ts: number;
+  /** Which record produced it (`daemon` = the in-process pino error ring). */
+  source: string;
+  /** The logged message, length-bounded. */
+  line: string;
+}
+
+/**
+ * Per-CLI ACP health, folded from the durable run event logs
+ * (`<state-home>/core.db.events/*.ndjson`, `acpSessionStarted` / `acpFallback` frames).
+ * A CLI that never appears in the logs has no key — absence spells "no ACP traffic recorded",
+ * and zero counts are never invented for it.
+ */
+export interface AcpCliDiagnostics {
+  /** Count of `acpSessionStarted` events for this cliKey. */
+  sessionsStarted: number;
+  /** Count of `acpFallback` events (ACP unavailable/failed; run continued single-shot). */
+  fallbacks: number;
+  /** Fallback counts by `fallbackKind` (`session_died`, `auth_required`, `binary_unavailable`, …). */
+  fallbackKinds: Record<string, number>;
+  /** Epoch ms of the newest `acpSessionStarted`, or `null` when none recorded. */
+  lastStartedTs: number | null;
+  /** Epoch ms of the newest `acpFallback`, or `null` when none recorded. */
+  lastFallbackTs: number | null;
+}
+
+/** The ACP fold of `GET /diagnostics` — keyed by `cliKey` (`claude`, `pi`, `codex`, …). */
+export interface AcpDiagnostics {
+  byCli: Record<string, AcpCliDiagnostics>;
+}
+
+/**
+ * `GET /diagnostics` (api-types 0.16.0) — the daemon's read-only self-knowledge surface:
+ * what is deployed, what it stores, what has gone wrong recently, and whether ACP is really
+ * working across the CLIs. Every field is derived from records the daemon already owns;
+ * anything it cannot answer is `null` / empty, never fabricated.
+ */
+export interface DiagnosticsResponse {
+  components: DiagnosticsComponents;
+  daemon: DiagnosticsDaemon;
+  /** `core.db` + sidecars + the events dir (as a total), sorted by name. */
+  stores: DiagnosticsStoreFile[];
+  /** Bounded tail of the daemon's own error-level log lines, newest first. */
+  recentErrors: DiagnosticsRecentError[];
+  acp: AcpDiagnostics;
+}