wicked-crew-api-types 0.97.0 → 0.99.0

package/index.d.ts

@@ -227,6 +227,8 @@ export interface HealthCapabilities {
   /**
    * `LaunchRunBody.revisesPr` is accepted (crew#550; crew ≥ 0.7.36). ABSENT on a daemon before
    * the field — read as `false`: do not send `revisesPr` to such a daemon.
+   * NOTE (crew#662): this CAPABILITY flag is a boolean; the LAUNCH field of the same name,
+   * `LaunchRunBody.revisesPr`, is the pull request NUMBER (a positive integer) — never `true`.
    */
   revisesPr?: boolean;
   /**
@@ -246,6 +248,12 @@ export interface HealthCapabilities {
    * as `false`: group such a daemon's runs one session per run.
    */
   runChatId?: boolean;
+  /**
+   * (crew#825; additive) `LaunchRunBody.excludeLinkedIssues` is accepted and
+   * `POST /linked-issues/preview` is served. ABSENT on an older daemon — read as `false`: do not
+   * send the field (its strict launch schema 400s on it) and do not call the preview.
+   */
+  linkedIssuesExclude?: boolean;
   /**
    * Repo-bound runs get an EVIDENCE ROOT for walkthroughs (WT-W1, api-types 0.74.0): the engine
    * addon takes `LaunchOptions.evidenceRoot` (wicked-core-ts ≥ 0.7.35), so a walkthrough step on a
@@ -818,6 +826,15 @@ export interface RosterSeat {
    * engine predating the field (serde omits `None`) and on seats with no known login flow.
    */
   login_invocation?: string;
+  /**
+   * The shell invocation that signs this seat OUT of its own configuration root (crew#615;
+   * wicked-core#807 `AgenticCli.logout_invocation`, core-ts >= 0.7.43): the CLI's own documented
+   * logout (`claude auth logout`, `codex logout`, `opencode auth logout`), prefixed with the seat's
+   * root exactly like {@link login_invocation}. Passed through VERBATIM; absent for a seat whose CLI
+   * documents no logout (copilot, pi, agy) and on an engine predating the field. `POST
+   * /seats/:cli/logout` runs it.
+   */
+  logout_invocation?: string;
   /**
    * Whether the seat LOOKS signed in — a cheap file/env-presence HEURISTIC computed by the
    * daemon (`seat-signin.ts`), never a spawned probe and never proof the credential still
@@ -2561,7 +2578,8 @@ export interface UnitPlannedEvent {
   description: string;
   stage: StageKind;
   role: PhaseRole;
-  gate: 'auto' | 'human_confirm' | 'human_confirm_if';
+  /** `consent_before` from wicked-core-ts 0.7.43 (core#801, crew#888). */
+  gate: 'auto' | 'human_confirm' | 'human_confirm_if' | 'consent_before';
   skill_ref: string | null;
   has_validator_pin: boolean;
   executor_type: 'agent' | 'tool';
@@ -4063,6 +4081,8 @@ export interface LaunchRunBody {
    * `deliver: 'none'` is a 400), and the PR must be OPEN and not from a fork (409 naming why).
    * Send it ONLY when `GET /health.capabilities.revisesPr === true` — an older daemon's strict
    * launch schema rejects the key with a 400.
+   * NOTE (crew#662): a positive integer PR number — not the boolean capability flag
+   * `HealthCapabilities.revisesPr` of the same name. A 400 names the field and what it expected.
    */
   revisesPr?: number;
   /**
@@ -4120,6 +4140,30 @@ export interface LaunchRunBody {
    * guard as `channel` above.
    */
   actor?: string;
+  /**
+   * (crew#825; additive) Issue refs the intent names that the daemon must NOT read and append to
+   * the problem (`"541"`, `"#541"`, `"owner/repo#541"`; at most 50) — a reference in passing is not
+   * a request to inline the issue. Answered as `LaunchRunResponse.linkedIssues[]` entries with
+   * `excluded: true`. Send only when `GET /health.capabilities.linkedIssuesExclude === true`.
+   */
+  excludeLinkedIssues?: string[];
+}
+
+/** `POST /linked-issues/preview` (crew#825): what a workflow launch of `problem` WOULD append. */
+export interface LinkedIssuesPreviewBody {
+  problem: string;
+  repoRef?: string;
+  excludeLinkedIssues?: string[];
+}
+
+/** The `POST /linked-issues/preview` 200 body: the same reading `POST /runs` does, nothing launched. */
+export interface LinkedIssuesPreviewResponse {
+  issues: LinkedIssue[];
+  /** Characters the block would add to the problem; `0` when nothing would be appended. */
+  appendedChars: number;
+  /** Present when the reading itself failed (the repo list or gh unreadable): a launch now runs on
+   *  the intent alone, exactly as `POST /runs` does on the same fault. */
+  error?: string;
 }
 
 /**
@@ -4136,6 +4180,10 @@ export interface LinkedIssue {
   title?: string;
   /** Present when not `resolved`: why, in one line. */
   error?: string;
+  /** (crew#825; additive) Present when `resolved`: characters this issue adds to the problem. */
+  chars?: number;
+  /** (crew#825; additive) `true` when the launch left this ref out (`excludeLinkedIssues`). */
+  excluded?: true;
 }
 
 /** The `POST /runs` 201 body. `linkedIssues` (crew#627, additive) is present when the intent of a
@@ -4149,6 +4197,12 @@ export interface LaunchRunResponse {
    * delivery), and `notice` says so in words a composer can show. ABSENT on every other launch.
    */
   freeText?: { notice: string };
+  /**
+   * (crew#874) PRESENT when the installed wicked-garden is not the one the published skills
+   * generation was built from: the run executes the PUBLISHED generation, and this says so — the
+   * same `skills.installed-ahead` finding `GET /diagnostics.skills.findings` carries.
+   */
+  skillsWarning?: { kind: 'skills.installed-ahead'; severity: 'warning'; message: string };
 }
 
 /**
@@ -4257,9 +4311,17 @@ export interface GraphKind {
 /** Gate position in the value→strategy→execution ladder. */
 export type GateType = 'value' | 'strategy' | 'execution';
 
-/** Human-confirm spec for a phase gate (serde flattened from Rust enum). */
+/**
+ * Human-confirm spec for a phase gate (serde flattened from Rust enum).
+ *
+ * `'consent_before'` (wicked-core#805 / core#801, core-ts >= 0.7.43; crew#888): the engine pauses
+ * BEFORE the phase runs, with `awaitingHuman{gateKind: 'consent'}`, whatever the run-level
+ * `humanConfirm` policy, and nothing pauses after it. Approve runs the phase; reject cancels the run
+ * with nothing in the phase run. A standing order never answers a `consent` gate.
+ */
 export type GateSpec =
   | 'auto'
+  | 'consent_before'
   | { human_confirm: { unconditional: boolean } }
   | { human_confirm_if: 'verdict_not_pass' };
 
@@ -4378,6 +4440,28 @@ export interface DomainCoverage {
   resolved: number;
 }
 
+/**
+ * `POST /seats/:cli/login` and `POST /seats/:cli/logout` (crew#615): the PTY size for the terminal
+ * the daemon opens running the seat's own `login_invocation` / `logout_invocation`. Both optional
+ * (default 100 x 30).
+ */
+export interface SeatSessionBody {
+  cols?: number;
+  rows?: number;
+}
+
+/**
+ * The answer to {@link SeatSessionBody}: the terminal running the seat's sign-in / sign-out
+ * command. Drive and read it over `/ws/terminals/:id` (a device URL streams there). 404 when the
+ * seat is unknown or its CLI documents no such command.
+ */
+export interface SeatSessionResponse {
+  terminalId: string;
+  /** The seat key the command was run for. */
+  cli: string;
+  action: 'login' | 'logout';
+}
+
 /** The open-terminal request body (`POST /terminals`, DES-TERMINAL-001 §6). */
 export interface OpenTerminalBody {
   /** Working directory the PTY opens in. */
@@ -6504,7 +6588,12 @@ export interface DiagnosticsSkillsFinding {
    *  generation landed with (a reference the skill's author owns that names nothing in the
    *  snapshot — published as found); `message` names the publish finding's kind, `file:line` and
    *  evidence. Reported while that generation is current, from the publish that found them until the
-   *  daemon restarts (a restart re-verifies `current` without re-scanning it). */
+   *  daemon restarts (a restart re-verifies `current` without re-scanning it);
+   *  `skills.installed-ahead` (`warning`, crew#874) = the installed wicked-garden's content hash is
+   *  not the baseline the published generation was built from — runs use the published (older)
+   *  skills; `message` names both versions and the remedy (refresh-baseline, then publish). A
+   *  daemon boot refreshes and publishes on its own when nothing in the catalog is user-edited
+   *  (`WICKED_CREW_SKILLS_AUTO_REFRESH=0` turns that off); when it did not, the message says why. */
   kind:
     | 'skills.fallback'
     | 'skills.blocked'
@@ -6515,7 +6604,8 @@ export interface DiagnosticsSkillsFinding {
     | 'skills.base-skill'
     | 'skills.phase-skill'
     | 'skills.garden'
-    | 'skills.publish-warning';
+    | 'skills.publish-warning'
+    | 'skills.installed-ahead';
   severity: 'warning' | 'error';
   message: string;
 }

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wicked-crew-api-types",
-  "version": "0.97.0",
+  "version": "0.99.0",
   "description": "The wire contract of the wicked-crew daemon's /api/v1 REST surface and /ws CoreEvent frames \u2014 types only, zero runtime",
   "type": "module",
   "types": "./index.d.ts",