patchwork-os 0.2.0-beta.1 → 0.2.0-beta.10.canary.95

package/dist/recipeRoutes.d.ts

@@ -27,8 +27,10 @@
  * connectorRoutes.ts.
  */
 import type { IncomingMessage, ServerResponse } from "node:http";
+import type { LintIssue } from "./recipes/validation.js";
 import type { RecipeDraft } from "./recipesHttp.js";
 export declare function _resetGenerateRateLimitForTests(): void;
+export declare function _resetRepairRateLimitForTests(): void;
 export interface VarsValidationError {
     ok: false;
     error: string;
@@ -46,6 +48,12 @@ export declare const RECIPE_ROUTE_BODY_CAPS: {
     readonly run: number;
     /** /recipes (POST), PUT/PATCH /recipes/:name, /recipes/lint — yaml content. */
     readonly content: number;
+    /**
+     * /recipes/repair — `{ currentYaml: string, lintIssues: LintIssue[] }`.
+     * Cap matches `content` since the body carries the full recipe YAML
+     * (256 KB matches the existing PUT/POST/lint caps).
+     */
+    readonly repair: number;
 };
 /**
  * Read an HTTP request body up to `max` bytes. Returns the raw string or
@@ -62,6 +70,7 @@ export declare const RECIPE_ROUTE_BODY_CAPS: {
 export declare function readBodyWithCap(req: IncomingMessage, max: number): Promise<{
     ok: true;
     body: string;
+    bytes: Buffer;
 } | {
     ok: false;
     code: "too_large";
@@ -105,6 +114,17 @@ export interface RecipeRouteDeps {
         error?: string;
         unavailable?: boolean;
     }>) | null;
+    /** Phase 2A — sibling of generateRecipeFn for the repair endpoint. */
+    repairRecipeFn: ((args: {
+        currentYaml: string;
+        lintIssues: LintIssue[];
+    }) => Promise<{
+        ok: boolean;
+        yaml?: string;
+        warnings?: string[];
+        error?: string;
+        unavailable?: boolean;
+    }>) | null;
     recipesFn: (() => Record<string, unknown>) | null;
     loadRecipeContentFn: ((name: string) => {
         content: string;
@@ -142,8 +162,8 @@ export interface RecipeRouteDeps {
     }>) | null;
     lintRecipeContentFn: ((content: string) => {
         ok: boolean;
-        errors: string[];
-        warnings: string[];
+        errors: LintIssue[];
+        warnings: LintIssue[];
     }) | null;
     saveRecipeFn: ((draft: RecipeDraft) => {
         ok: boolean;
@@ -162,6 +182,27 @@ export interface RecipeRouteDeps {
         after?: number;
     }) => Record<string, unknown>[]) | null;
     runDetailFn: ((seq: number) => Record<string, unknown> | null) | null;
+    /**
+     * Aggregate halt categories across recent runs. `sinceMs` filters to runs
+     * created after `Date.now() - sinceMs`; default 7 days. `recipe` filters
+     * to runs whose `recipeName` matches exactly. Returns the `HaltSummary`
+     * shape from src/recipes/haltCategory.ts.
+     */
+    haltSummaryFn: ((opts?: {
+        sinceMs?: number;
+        limit?: number;
+        recipe?: string;
+    }) => import("./recipes/haltCategory.js").HaltSummary) | null;
+    /**
+     * PR3b sibling of haltSummaryFn — same windowing shape but aggregates
+     * judge-step verdicts instead. Returns the `JudgeSummary` shape from
+     * src/recipes/judgeSummary.ts.
+     */
+    judgeSummaryFn: ((opts?: {
+        sinceMs?: number;
+        limit?: number;
+        recipe?: string;
+    }) => import("./recipes/judgeSummary.js").JudgeSummary) | null;
     runPlanFn: ((recipeName: string) => Promise<Record<string, unknown>>) | null;
     runReplayFn: ((seq: number) => Promise<{
         ok: boolean;
@@ -174,6 +215,21 @@ export interface RecipeRouteDeps {
         taskId?: string;
         error?: string;
     }>) | null;
+    /**
+     * Best-effort notification that the on-disk recipe set just changed
+     * (install, save, delete, archive, …). The bridge wires this to
+     * `recipeScheduler.start()` so cron-triggered recipes start firing
+     * without a restart. Optional — non-bridge callers (tests, headless
+     * tooling) leave it null.
+     *
+     * Contract:
+     *   - Synchronous fire-and-forget. Implementations MUST NOT throw.
+     *   - Idempotent. Multiple calls in quick succession should coalesce
+     *     to at-least-once scheduler restart behaviour.
+     *   - Hot path is post-success: routes invoke after the disk write,
+     *     so a callback failure must never roll back the user's action.
+     */
+    onRecipesChangedFn: (() => void) | null;
 }
 /**
  * Try to handle a recipe / run-audit / template route. Returns true if