patchwork-os 1.1.0-beta.4.canary.482 → 1.1.0-beta.4.canary.484

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "patchwork-os",
-  "version": "1.1.0-beta.4.canary.482",
+  "version": "1.1.0-beta.4.canary.484",
   "description": "Your personal AI runtime, local-first. Patchwork OS gives any AI model a consistent set of tools, YAML recipes, a delegation policy with approval queue, and a durable trace memory — all on your machine, all under your policy.",
   "type": "module",
   "main": "dist/index.js",

package/dist/workers/boundaryPreview.d.ts

@@ -1,47 +0,0 @@
-/**
- * The control boundary for a live worker — composition, not policy.
- *
- * `previewActions` answers "what would the gate say about these candidates?"
- * given a worker and its trust store. This resolves those two from a recipe
- * name, so a caller with nothing but "release-notes" can render the boundary.
- *
- * It reuses `loadWorkerTrustForRecipe` — the same resolution the live gate
- * performs in `buildWorkerAutonomyGate`. That matters for the same reason
- * `previewActions` reuses `decideWorkerAction`: if the preview resolved trust
- * its own way, it could show a boundary computed from a different worker
- * manifest or a staler store than the one enforcement will use, and be
- * confidently wrong. Every layer of this screen has to be a view of the gate.
- *
- * Returns null when no worker owns the recipe — the honest answer, and
- * distinguishable from "a worker that may do nothing", which is an empty
- * boundary rather than a missing one.
- */
-import type { ForbidRule } from "./forbidPolicy.js";
-import { type ActionBoundary, type CandidateAction } from "./previewActions.js";
-import type { RunWorkerShadowOpts } from "./runWorkerShadow.js";
-export interface WorkerBoundary {
-    workerId: string;
-    workerName: string;
-    recipeName: string;
-    boundary: ActionBoundary;
-    /**
-     * False when the worker-autonomy flag is off. The boundary is still computed
-     * and still correct as a statement of policy — but nothing is enforcing it,
-     * and a screen that does not say so would imply protection that is not
-     * running. The caller must surface this.
-     */
-    enforced: boolean;
-}
-export interface BoundaryPreviewOpts {
-    /** Caller-supplied candidates. Omitted ⇒ derived from the worker's `owns`. */
-    candidates?: readonly CandidateAction[];
-    forbidRules?: readonly ForbidRule[];
-    trustOpts?: RunWorkerShadowOpts;
-}
-/**
- * Compute the control boundary for whichever worker owns `recipeName`.
- *
- * Read-only: resolves trust, evaluates hypotheticals, writes nothing. No
- * approval is enqueued and no decision is recorded — see `previewActions`.
- */
-export declare function boundaryForRecipe(recipeName: string, opts?: BoundaryPreviewOpts): WorkerBoundary | null;

package/dist/workers/boundaryPreview.js

@@ -1,48 +0,0 @@
-/**
- * The control boundary for a live worker — composition, not policy.
- *
- * `previewActions` answers "what would the gate say about these candidates?"
- * given a worker and its trust store. This resolves those two from a recipe
- * name, so a caller with nothing but "release-notes" can render the boundary.
- *
- * It reuses `loadWorkerTrustForRecipe` — the same resolution the live gate
- * performs in `buildWorkerAutonomyGate`. That matters for the same reason
- * `previewActions` reuses `decideWorkerAction`: if the preview resolved trust
- * its own way, it could show a boundary computed from a different worker
- * manifest or a staler store than the one enforcement will use, and be
- * confidently wrong. Every layer of this screen has to be a view of the gate.
- *
- * Returns null when no worker owns the recipe — the honest answer, and
- * distinguishable from "a worker that may do nothing", which is an empty
- * boundary rather than a missing one.
- */
-import { FLAG_WORKER_AUTONOMY, isEnabled } from "../featureFlags.js";
-import { defaultCandidatesFor, previewActions, } from "./previewActions.js";
-import { loadWorkerTrustForRecipe } from "./runWorkerShadow.js";
-/**
- * Compute the control boundary for whichever worker owns `recipeName`.
- *
- * Read-only: resolves trust, evaluates hypotheticals, writes nothing. No
- * approval is enqueued and no decision is recorded — see `previewActions`.
- */
-export function boundaryForRecipe(recipeName, opts = {}) {
-    const trust = loadWorkerTrustForRecipe(recipeName, opts.trustOpts);
-    if (!trust)
-        return null;
-    const { worker, store } = trust;
-    const candidates = opts.candidates ?? defaultCandidatesFor(worker);
-    return {
-        workerId: worker.id,
-        workerName: worker.name,
-        recipeName,
-        boundary: previewActions(worker, candidates, store, {
-            ...(opts.forbidRules ? { forbidRules: opts.forbidRules } : {}),
-        }),
-        // Deliberately reported rather than used to suppress the result. An
-        // operator asking "what may this worker do?" while the flag is off should
-        // get the answer AND be told it is not being enforced — hiding the boundary
-        // would leave them with no information at all, which is worse.
-        enforced: isEnabled(FLAG_WORKER_AUTONOMY),
-    };
-}
-//# sourceMappingURL=boundaryPreview.js.map

package/dist/workers/boundaryPreview.js.map

@@ -1 +0,0 @@
-{"version":3,"file":"boundaryPreview.js","sourceRoot":"","sources":["../../src/workers/boundaryPreview.ts"],"names":[],"mappings":"AAAA;;;;;;;;;;;;;;;;;GAiBG;AAEH,OAAO,EAAE,oBAAoB,EAAE,SAAS,EAAE,MAAM,oBAAoB,CAAC;AAErE,OAAO,EAGL,oBAAoB,EACpB,cAAc,GACf,MAAM,qBAAqB,CAAC;AAE7B,OAAO,EAAE,wBAAwB,EAAE,MAAM,sBAAsB,CAAC;AAuBhE;;;;;GAKG;AACH,MAAM,UAAU,iBAAiB,CAC/B,UAAkB,EAClB,OAA4B,EAAE;IAE9B,MAAM,KAAK,GAAG,wBAAwB,CAAC,UAAU,EAAE,IAAI,CAAC,SAAS,CAAC,CAAC;IACnE,IAAI,CAAC,KAAK;QAAE,OAAO,IAAI,CAAC;IAExB,MAAM,EAAE,MAAM,EAAE,KAAK,EAAE,GAAG,KAAK,CAAC;IAChC,MAAM,UAAU,GAAG,IAAI,CAAC,UAAU,IAAI,oBAAoB,CAAC,MAAM,CAAC,CAAC;IAEnE,OAAO;QACL,QAAQ,EAAE,MAAM,CAAC,EAAE;QACnB,UAAU,EAAE,MAAM,CAAC,IAAI;QACvB,UAAU;QACV,QAAQ,EAAE,cAAc,CAAC,MAAM,EAAE,UAAU,EAAE,KAAK,EAAE;YAClD,GAAG,CAAC,IAAI,CAAC,WAAW,CAAC,CAAC,CAAC,EAAE,WAAW,EAAE,IAAI,CAAC,WAAW,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;SAC/D,CAAC;QACF,oEAAoE;QACpE,0EAA0E;QAC1E,4EAA4E;QAC5E,+DAA+D;QAC/D,QAAQ,EAAE,SAAS,CAAC,oBAAoB,CAAC;KAC1C,CAAC;AACJ,CAAC"}