toolroll 0.9.36 → 0.9.38

package/CHANGELOG.md

@@ -1,5 +1,82 @@
 # Changelog
 
+## 0.9.38 — 2026-10-06
+
+- **The release check is faster.** Its app journeys run in about 8 minutes
+  instead of about 12, with no journey or coverage dropped.
+- **Lead chat tool steps tell the truth.** A step shows done only when it
+  succeeded. A failed step says why in plain words.
+- **Telegram decision cards lead with the action.** Decisions, plans, lead
+  proposals, flow approvals and flow choices say what to do and what it does
+  first. "Nothing changes until you confirm." stays on every proposal, and
+  buttons on cards already sent still work.
+- **Crew rows say why.** A task that is waiting, failed or needs you shows the
+  reason in one line; tap it to read the rest. The whole row still opens the
+  task.
+- **Dependency updates.** @slack/socket-mode 3.1.0, imapflow 2.2.5,
+  nodemailer 10.0.15, mailparser 3.9.36, lucide-react 1.52.0, @xyflow/react
+  12.12.0, happy-dom 20.14.5 and tsx 4.23.15. Vitest takes the 4.1.11 security
+  patch and stays on 4; version 5 waits for its own migration. `npm audit`
+  reports no vulnerabilities.
+
+## 0.9.37 — 2026-10-06
+
+- **Zod revamp, waves 1 and 2 finished.** Every handoff between a model and
+  Toolroll, and the context passed between steps, is now one schema each in
+  `src/contracts/`: the lead's 51 tools and the 25 MCP gateway tools, the
+  scout report, task sizing, reviewer findings, decisions, teammate turns and
+  sort answers, the lead's context bundle, project knowledge, memory and
+  skills, chat actions and channel callbacks, and the desktop coding handoff,
+  context and session record. A model gets the schema as `--json-schema`
+  where its harness takes one; a refusal names the field
+  (`steps[0].routes[0].goesTo: required`). Everything that was accepted before
+  is still accepted: tool calls with extra or loose arguments, model answers
+  with nulls or overlong text (clipped as before), saved reports, rows,
+  sessions, chat buttons and proposals. Replayed against real saved data
+  (scout reports, findings, decisions, 410 scopes and 796 routes, 279 chat
+  buttons, every saved flow and card), all of it reads the same.
+- **Research can read PostHog.** A research run gets a connected service's
+  query tool (PostHog's `exec`) only when the access the service actually
+  granted is read-only. Otherwise it skips it and says why on the run and the
+  integration, with a **Reconnect read-only** action. Connecting PostHog as
+  usual is unchanged, and builds keep every tool. Connections made before this
+  release didn't record what was granted, so research skips them until you
+  reconnect read-only.
+- **A question's recommendation can carry its reason.** `connect: because…`
+  now counts as recommending `connect`, instead of failing the question.
+- **A Telegram update Toolroll can't read** is logged and answered OK, so
+  Telegram doesn't keep resending it. A Slack, Discord or Teams message part
+  that can't be read is dropped with its reason instead of retried forever.
+- **Rolling back:** flow cards written by 0.9.37 read as empty in 0.9.36, so a
+  rollback loses the step outputs of cards still in progress.
+- **Scopes, acceptance criteria and sealed routes have one contract.** A task's
+  scope (goal, exclusions, touch paths, rubric) and an acceptance criterion are
+  described once from the plan contract's own fields (`src/contracts/scope.ts`);
+  a sealed agent route, in both versions it has been saved in, with its
+  overrides and task size, is one schema (`src/contracts/route.ts`). The shared
+  rubric input schema is ready for the lead-tool migration. Every saved scope,
+  standing order and sealed route reads and digests exactly as before, so no
+  approval changes.
+  Nothing new is refused: a scope still names up to 50 paths and a criterion
+  still ignores keys it doesn't use. Rubric and route refusals are now
+  field-named lines (`acceptance[0].statement over 1,000 bytes`), and a route
+  made by a newer Toolroll says so.
+- **What a flow's steps hand on has one contract.** A finished zone's
+  `{{stage.…}}` words, a card's saved outputs, and what Send to me and Person
+  chooses send are each described once (`src/contracts/stage-output.ts`,
+  `flow-send.ts`, `flow-card.ts`). Saved cards and sends read exactly as
+  before. A build or research task filed after a step whose output was too
+  long to pass on now gets that output whole, not just a link to it.
+- **Tightened, on purpose.** Saving a flow with a new `{{stage.…}}` that its
+  zone doesn't hand on is refused, naming where:
+  `stages[2].instructions: stage.research.unknown is not available (Research
+  hands on {{stage.research}}, {{stage.research.items}} and
+  {{stage.research.report}})`. This covers the canvas, `toolroll flows
+  create/edit/import`, the lead and templates. A reference a flow already had
+  is never refused, and nothing changes for flows that are only read or run.
+  Card outputs and kept sends are saved with a version; ones a newer Toolroll
+  wrote are refused rather than misread or overwritten.
+
 ## 0.9.36 — 2026-10-06
 
 - **Flows have one contract.** Every kind of zone, step, route, answer,

package/dist/assignment-adapters.d.ts

@@ -1,87 +1,52 @@
 import { type AssignmentSnapshot } from "./assignment.js";
 import type { Store } from "./store.js";
-export declare const ASSIGNMENT_ACTIONS: readonly ["show", "updates", "claim", "check", "brief", "inbox", "ack"];
-export type AssignmentOperation = typeof ASSIGNMENT_ACTIONS[number];
+import { type AssignmentInput, type AssignmentOperation } from "./contracts/gateway-tools.js";
+export declare const ASSIGNMENT_ACTIONS: AssignmentOperation[];
+export type { AssignmentOperation };
 type Args = Record<string, unknown>;
 type Failure = {
     ok: false;
     reason: string;
     message: string;
 };
+/** The gateway's assignment tools: names and words. Each one's input is ASSIGNMENT_INPUTS[operation]
+ * (src/contracts/gateway-tools.ts), which `toolroll assignment` reads its flags with too. */
 export declare const ASSIGNMENT_TOOLS: readonly [{
     readonly name: "get_assignment";
     readonly operation: "show";
     readonly description: "Read one assignment's root, current execution, owner, exact result and handoff receipt. Approval, proof and deployment remain separate facts.";
-    readonly inputSchema: {
-        type: string;
-        properties: Record<string, unknown>;
-        required: string[];
-        additionalProperties: boolean;
-    };
 }, {
     readonly name: "list_assignment_updates";
     readonly operation: "updates";
     readonly description: "Read durable assignment updates in your projects after a cursor. Save nextCursor after processing; repeated reads do not acknowledge or deliver anything.";
-    readonly inputSchema: {
-        type: string;
-        properties: Record<string, unknown>;
-        required: string[];
-        additionalProperties: boolean;
-    };
 }, {
     readonly name: "claim_assignment";
     readonly operation: "claim";
     readonly description: "Record yourself as this assignment's lead. Repeating your claim is safe; another active owner cannot be replaced. This grants no approval or execution authority.";
-    readonly inputSchema: {
-        type: string;
-        properties: Record<string, unknown>;
-        required: string[];
-        additionalProperties: boolean;
-    };
 }, {
     readonly name: "acknowledge_assignment";
     readonly operation: "check";
     readonly description: "Acknowledge the exact ready-to-check receipt as its lead, using the current receipt digest. This does not accept failed proof, answer decisions, approve work, publish or deploy.";
-    readonly inputSchema: {
-        type: string;
-        properties: Record<string, unknown>;
-        required: string[];
-        additionalProperties: boolean;
-    };
 }, {
     readonly name: "get_assignment_brief";
     readonly operation: "brief";
     readonly description: "Catch up from the local database: current work, decisions, saved results and project knowledge. Bounded read only; no model call or task mutation.";
-    readonly inputSchema: {
-        type: string;
-        properties: Record<string, unknown>;
-        required: string[];
-        additionalProperties: boolean;
-    };
 }, {
     readonly name: "get_assignment_inbox";
     readonly operation: "inbox";
     readonly description: "Receive a durable batch of your assignments' status changes. Use a stable consumer name. Until acknowledged, the same batch survives reconnects and restarts. Receiving never completes or reruns work.";
-    readonly inputSchema: {
-        type: string;
-        properties: Record<string, unknown>;
-        required: string[];
-        additionalProperties: boolean;
-    };
 }, {
     readonly name: "acknowledge_assignment_delivery";
     readonly operation: "ack";
     readonly description: "Acknowledge receipt of an inbox batch after handling its updates. This advances only your delivery cursor; it never marks work complete, answers a decision or starts a revision.";
-    readonly inputSchema: {
-        type: string;
-        properties: Record<string, unknown>;
-        required: string[];
-        additionalProperties: boolean;
-    };
 }];
-/** The CLI and MCP use the same bounded input contract. MCP also validates its
- * descriptor before dispatch; this check protects direct adapter callers. */
-export declare function assignmentArgumentProblem(operation: AssignmentOperation, args: Args): string | null;
+/** The CLI and MCP read an assignment call with the same schema; MCP reads it before dispatch too, and this protects
+ * direct adapter callers. A refusal is its path-named lines; a ref or project path with control characters, which
+ * JSON Schema can't say, is refused after parsing. */
+export declare function readAssignmentArgs<O extends AssignmentOperation>(operation: O, args: Args): {
+    ok: true;
+    value: AssignmentInput<O>;
+} | Failure;
 /** Every read and mutation authenticates inside the same transaction as its
  * projection. A cached name/allowlist cannot keep a revoked identity alive. */
 export declare function assignmentForCoordinator(store: Store, token: string, operation: AssignmentOperation, args: Args, now: Date, evidenceRoot?: string): Failure | {
@@ -179,4 +144,3 @@ export declare function coordinatorToken(flags: Map<string, string | true>, env:
     token: string | null;
 } | Failure;
 export declare function runAssignmentCommand(positional: readonly string[], flags: Map<string, string | true>, context: AssignmentCliContext): number;
-export {};

package/dist/assignment-adapters.js

@@ -8,47 +8,36 @@ import { assignmentCatchUp } from "./assignment-brief.js";
 import { assignmentInbox, acknowledgeAssignmentDelivery } from "./assignment-delivery.js";
 import { syncAssignmentStatuses } from "./assignment-status.js";
 import { envelopeJson } from "./envelope.js";
-export const ASSIGNMENT_ACTIONS = ["show", "updates", "claim", "check", "brief", "inbox", "ack"];
+import { parseContract } from "./contracts/contract.js";
+import { ASSIGNMENT_INPUTS } from "./contracts/gateway-tools.js";
+export const ASSIGNMENT_ACTIONS = Object.keys(ASSIGNMENT_INPUTS);
 const failure = (reason, message) => ({ ok: false, reason, message });
-const reference = { type: "string", minLength: 1, maxLength: 64 };
-const digest = { type: "string", minLength: 64, maxLength: 64, pattern: "^[a-f0-9]{64}$" };
-const batchId = { type: "string", minLength: 32, maxLength: 32, pattern: "^[a-f0-9]{32}$" };
-const consumer = { type: "string", minLength: 1, maxLength: 64, pattern: "^[a-z0-9][a-z0-9-]{0,63}$" };
-const object = (properties, required = []) => ({ type: "object", properties, required, additionalProperties: false });
+/** The gateway's assignment tools: names and words. Each one's input is ASSIGNMENT_INPUTS[operation]
+ * (src/contracts/gateway-tools.ts), which `toolroll assignment` reads its flags with too. */
 export const ASSIGNMENT_TOOLS = [
-    { name: "get_assignment", operation: "show", description: "Read one assignment's root, current execution, owner, exact result and handoff receipt. Approval, proof and deployment remain separate facts.", inputSchema: object({ ref: reference }, ["ref"]) },
-    { name: "list_assignment_updates", operation: "updates", description: "Read durable assignment updates in your projects after a cursor. Save nextCursor after processing; repeated reads do not acknowledge or deliver anything.", inputSchema: object({ after: { type: "integer", minimum: 0, maximum: Number.MAX_SAFE_INTEGER }, limit: { type: "integer", minimum: 1, maximum: 100 } }) },
-    { name: "claim_assignment", operation: "claim", description: "Record yourself as this assignment's lead. Repeating your claim is safe; another active owner cannot be replaced. This grants no approval or execution authority.", inputSchema: object({ ref: reference }, ["ref"]) },
-    { name: "acknowledge_assignment", operation: "check", description: "Acknowledge the exact ready-to-check receipt as its lead, using the current receipt digest. This does not accept failed proof, answer decisions, approve work, publish or deploy.", inputSchema: object({ ref: reference, digest }, ["ref", "digest"]) },
-    { name: "get_assignment_brief", operation: "brief", description: "Catch up from the local database: current work, decisions, saved results and project knowledge. Bounded read only; no model call or task mutation.", inputSchema: object({ repo: { type: "string", minLength: 1, maxLength: 4096 }, limit: { type: "integer", minimum: 1, maximum: 25 } }) },
-    { name: "get_assignment_inbox", operation: "inbox", description: "Receive a durable batch of your assignments' status changes. Use a stable consumer name. Until acknowledged, the same batch survives reconnects and restarts. Receiving never completes or reruns work.", inputSchema: object({ consumer, limit: { type: "integer", minimum: 1, maximum: 100 } }, ["consumer"]) },
-    { name: "acknowledge_assignment_delivery", operation: "ack", description: "Acknowledge receipt of an inbox batch after handling its updates. This advances only your delivery cursor; it never marks work complete, answers a decision or starts a revision.", inputSchema: object({ consumer, batchId }, ["consumer", "batchId"]) },
+    { name: "get_assignment", operation: "show", description: "Read one assignment's root, current execution, owner, exact result and handoff receipt. Approval, proof and deployment remain separate facts." },
+    { name: "list_assignment_updates", operation: "updates", description: "Read durable assignment updates in your projects after a cursor. Save nextCursor after processing; repeated reads do not acknowledge or deliver anything." },
+    { name: "claim_assignment", operation: "claim", description: "Record yourself as this assignment's lead. Repeating your claim is safe; another active owner cannot be replaced. This grants no approval or execution authority." },
+    { name: "acknowledge_assignment", operation: "check", description: "Acknowledge the exact ready-to-check receipt as its lead, using the current receipt digest. This does not accept failed proof, answer decisions, approve work, publish or deploy." },
+    { name: "get_assignment_brief", operation: "brief", description: "Catch up from the local database: current work, decisions, saved results and project knowledge. Bounded read only; no model call or task mutation." },
+    { name: "get_assignment_inbox", operation: "inbox", description: "Receive a durable batch of your assignments' status changes. Use a stable consumer name. Until acknowledged, the same batch survives reconnects and restarts. Receiving never completes or reruns work." },
+    { name: "acknowledge_assignment_delivery", operation: "ack", description: "Acknowledge receipt of an inbox batch after handling its updates. This advances only your delivery cursor; it never marks work complete, answers a decision or starts a revision." },
 ];
-/** The CLI and MCP use the same bounded input contract. MCP also validates its
- * descriptor before dispatch; this check protects direct adapter callers. */
-export function assignmentArgumentProblem(operation, args) {
+/** The CLI and MCP read an assignment call with the same schema; MCP reads it before dispatch too, and this protects
+ * direct adapter callers. A refusal is its path-named lines; a ref or project path with control characters, which
+ * JSON Schema can't say, is refused after parsing. */
+export function readAssignmentArgs(operation, args) {
     if (!ASSIGNMENT_ACTIONS.includes(operation))
-        return "Choose show, updates, claim, check, brief, inbox, or ack.";
-    const allowed = operation === "brief" ? ["repo", "limit"] : operation === "inbox" ? ["consumer", "limit"] : operation === "ack" ? ["consumer", "batchId"] : operation === "updates" ? ["after", "limit"] : operation === "check" ? ["ref", "digest"] : ["ref"];
-    for (const key of Object.keys(args))
-        if (!allowed.includes(key))
-            return `Unknown argument: ${key}.`;
-    if (["show", "claim", "check"].includes(operation) && (typeof args["ref"] !== "string" || args["ref"].length < 1 || args["ref"].length > 64 || /[\u0000-\u001f\u007f]/.test(args["ref"])))
-        return "Choose a task id, 1–64 characters without control characters.";
-    if (operation === "check" && (typeof args["digest"] !== "string" || !/^[a-f0-9]{64}$/.test(args["digest"])))
-        return "Use the exact 64-character receipt digest from assignment show.";
-    if ((operation === "inbox" || operation === "ack") && (typeof args["consumer"] !== "string" || !/^[a-z0-9][a-z0-9-]{0,63}$/.test(args["consumer"])))
-        return "Use a stable consumer name with 1–64 lowercase letters, digits or hyphens.";
-    if (operation === "ack" && (typeof args["batchId"] !== "string" || !/^[a-f0-9]{32}$/.test(args["batchId"])))
-        return "Use the exact batchId from assignment inbox.";
-    if (args["repo"] !== undefined && (typeof args["repo"] !== "string" || args["repo"].length < 1 || args["repo"].length > 4096 || /[\u0000-\u001f\u007f]/.test(args["repo"])))
-        return "Choose a project path without control characters.";
-    for (const [name, min, max] of [["after", 0, Number.MAX_SAFE_INTEGER], ["limit", 1, operation === "brief" ? 25 : 100]]) {
-        const value = args[name];
-        if (value !== undefined && (typeof value !== "number" || !Number.isSafeInteger(value) || value < min || value > max))
-            return `${name} must be an integer from ${min} to ${max}.`;
+        return failure("usage", "Choose show, updates, claim, check, brief, inbox, or ack.");
+    const read = parseContract(ASSIGNMENT_INPUTS[operation], args);
+    if (!read.ok)
+        return failure("usage", read.issues.map(one => one.line).join("; "));
+    const value = read.value;
+    for (const field of ["ref", "repo"]) {
+        if (typeof value[field] === "string" && /[\u0000-\u001f\u007f]/.test(value[field]))
+            return failure("usage", `${field}: must not contain control characters`);
     }
-    return null;
+    return { ok: true, value };
 }
 function readAssignment(store, operation, args, now, access, root) {
     if (operation === "brief")
@@ -61,9 +50,10 @@ function readAssignment(store, operation, args, now, access, root) {
 /** Every read and mutation authenticates inside the same transaction as its
  * projection. A cached name/allowlist cannot keep a revoked identity alive. */
 export function assignmentForCoordinator(store, token, operation, args, now, evidenceRoot) {
-    const problem = assignmentArgumentProblem(operation, args);
-    if (problem !== null)
-        return failure("usage", problem);
+    const read = readAssignmentArgs(operation, args);
+    if (!read.ok)
+        return read;
+    args = read.value;
     // Authenticate before maintenance, then authenticate again inside delivery.
     // Reconciliation owns one short transaction per family and cannot sit under
     // the delivery transaction's writer reservation.
@@ -225,11 +215,11 @@ export function runAssignmentCommand(positional, flags, context) {
     for (const flag of operationFlags) {
         const value = flags.get(flag);
         if (value !== undefined)
-            args[flag === "batch" ? "batchId" : flag] = ["after", "limit"].includes(flag) ? typeof value === "string" && /^\d+$/.test(value) ? Number(value) : NaN : value;
+            args[flag === "batch" ? "batchId" : flag] = ["after", "limit"].includes(flag) && typeof value === "string" && /^\d+$/.test(value) ? Number(value) : value;
     }
-    const problem = assignmentArgumentProblem(operation, args);
-    if (problem !== null)
-        return emit(failure("usage", problem));
+    const read = readAssignmentArgs(operation, args);
+    if (!read.ok)
+        return emit(read);
     const credential = coordinatorToken(flags, context.env ?? process.env);
     if ("ok" in credential)
         return emit(credential);

package/dist/browser/THIRD_PARTY_NOTICES.txt

@@ -1460,7 +1460,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
 
-## Bundled dependency: @xyflow/react 12.11.6
+## Bundled dependency: @xyflow/react 12.12.0
 
 MIT License
 
@@ -1485,7 +1485,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
 
-## Bundled dependency: @xyflow/system 0.0.82
+## Bundled dependency: @xyflow/system 0.0.83
 
 MIT License
 
@@ -1971,7 +1971,7 @@ OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
 SOFTWARE.
 
 
-## Bundled dependency: lucide-react 1.47.0
+## Bundled dependency: lucide-react 1.52.0
 
 ISC License