wicked-crew-api-types 0.97.0 → 0.98.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
@@ -4063,6 +4071,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 +4130,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 +4170,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 +4187,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 };
 }
 
 /**
@@ -6504,7 +6548,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 +6564,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.98.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",