toolroll 0.9.33 → 0.9.36

package/CHANGELOG.md

@@ -1,5 +1,62 @@
 # Changelog
 
+## 0.9.36 — 2026-10-06
+
+- **Flows have one contract.** Every kind of zone, step, route, answer,
+  option, trigger and the flow file is described once
+  (`src/contracts/flow.ts`), and that description is what the lead's
+  `propose_flow` is told, what `toolroll flows create/edit/import` and the
+  console check, and what `docs/flow-file.schema.json` publishes (now
+  generated, so it includes Send to me, Person chooses and `ifReplied`, which
+  the hand-written one had missed). A refusal names the field and suggests the
+  one meant: `steps[0].routes[0]: unknown key 'to' (did you mean goesTo?)`,
+  `zones[2]: unknown key 'onFail' (did you mean ifFails?)`, instead of
+  "there's no step called ." Every saved flow, template, starter, kit and
+  gallery flow reads exactly as before: the same saved bytes and digests, and
+  the same exported files.
+- **Tightened, on purpose.** A step, flow file zone, trigger setting or
+  `propose_flow` argument with a key its kind doesn't take is refused by name
+  rather than silently ignored: `planning` on a Holding step, `remindAfter` on
+  a Wait step, `ifFails` on a Sort step (use `ifNotSure`, which it meant) or
+  `next` on a Sort or Person chooses step. A sort's `sureAt` is 0.5–99. A flow
+  file's zones keep only the words their kind uses when exported, and a file
+  or drawing made by a newer Toolroll is refused as such. Messages for flows
+  and triggers changed from "Zone Build: …" sentences to path-named lines.
+
+- **Builder handoffs and proofs have one contract.** The handoff a builder
+  leaves, its proof and the verification receipt are versioned schemas. Fifteen
+  real past runs replay with identical verdicts, receipt bytes and digests.
+- **One compact review packet.** `toolroll task review <id> --brief` (or
+  `--json`) shows a build's conclusion, changed files, check result, review
+  findings by severity, screenshot paths and what to do next, in about 40
+  lines and without logs or diffs.
+- **PostHog connects in one short step.** Its sign-in now uses PostHog's own
+  MCP permission preset instead of listing every permission, which showed a
+  75-group permission screen. Sign-in returns are now logged.
+- **Tests can't mistake a real process for a fake one.** Fake process IDs in
+  tests sit above every platform's limit, and a guard refuses new low ones (a
+  Brave tab and a GitHub runner process had made tests fail at random).
+
+## 0.9.35 — 2026-10-05
+
+- **One-click sign-ins ask for every permission a service lists.** Toolroll
+  asked for only the first 20, so a service needing one later in its list
+  issued a token it then refused (PostHog needs `user:read`, its 140th).
+  Reconnect a service that failed its test after signing in.
+
+## 0.9.34 — 2026-10-05
+
+- **Plans have one contract.** The first step of making every handoff robust:
+  a plan is described once, and that description is both what the planner is
+  told to return and what Toolroll checks. Limits come from one place, so the
+  2,000-versus-8,000 mismatch from 0.9.30 can't happen again, and a malformed
+  plan's retry quotes the exact field that was wrong.
+- **Projects added from the command line show in the console.** `toolroll
+  repos add` (you or the lead) admits a project the same way the console's Add
+  a project does, and it appears within seconds without a restart. Removing
+  works the same way. Every addition is recorded with who made it.
+- **Crew rows show when they last changed** ("4m", "2h", "3d").
+
 ## 0.9.33 — 2026-10-05
 
 - **A restart never breaks a project's builds.** A project's identity no

package/README.md

@@ -117,10 +117,17 @@ toolroll project use /path/to/project
 toolroll project show
 toolroll brief
 toolroll assignment show <task>
+toolroll task review <task> --brief
 toolroll task complete <task>
 toolroll task revise <task> --feedback "Keep the filter selected after reload."
 ```
 
+`task review <task> --brief` combines the latest finished build or report's conclusion,
+file counts, checks, review findings, screenshot paths, plan and next actions.
+Use `--run <id>` for an earlier attempt, `--json` for the same fields, and `--all`
+to include LOW findings. Lists stay bounded, with omitted entries counted; missing
+fields say `not recorded`. The lead token works through `--token` or `TOOLROLL_LEAD_TOKEN`.
+
 Completion and revisions use the local sign-in already saved by `up`. Completion
 reports the exact run, commit and check outcome it handled. Agents use a scoped
 credential (`project use /path/to/project --token-file /path/to/credential`) and

package/dist/assignment.d.ts

@@ -170,6 +170,7 @@ export declare function assignmentBrief(assignment: AssignmentSnapshot | null):
         status: "not-recorded";
     };
 } | null;
+export declare function assignmentChecksForRun(store: Store, root: string | undefined, runId: number, now: Date): AssignmentChecks;
 export declare function assignmentOf(store: Store, taskId: string, now: Date, access: AssignmentAccess, root?: string): AssignmentSnapshot | null;
 type MutationResult = {
     ok: true;

package/dist/assignment.js

@@ -83,7 +83,7 @@ function ownerOf(store, rootId, repo) {
 }
 // Report the recorded check outcome, never turn a model verdict into a check.
 // Follow-up checks on the same commit (Run checks) upgrade a pass and show a failure.
-function nativeChecks(store, root, runId, now) {
+export function assignmentChecksForRun(store, root, runId, now) {
     const own = buildChecks(store, root, runId);
     const run = store.getRun(runId);
     const followUps = followUpChecksOf(store, runId, now, root);
@@ -163,7 +163,7 @@ export function assignmentOf(store, taskId, now, access, root) {
     const reports = artifacts.filter(a => a.kind === "report");
     const unavailable = family.versions.flatMap(version => store.runsFor(version.refId).flatMap(run => store.artifactsFor(run.id).filter(artifact => root === undefined || !readVerifiedArtifact(root, artifact).ok)
         .map(artifact => `Saved ${artifact.kind} #${artifact.id} (run ${run.id}) is unavailable or changed.`)));
-    const checks = result === null ? null : nativeChecks(store, root, result.id, now);
+    const checks = result === null ? null : assignmentChecksForRun(store, root, result.id, now);
     const finishedBuild = result?.role === "builder" && (result.outcome === "built" || result.outcome === "no-change") &&
         result.finishedAt !== null && /^[a-f0-9]{40}$/.test(result.headRevision ?? "");
     // Finished work returns to its lead or user. Strict terms and previous model