Repository navigation
Releases
v0.72.1
What
validateno longer applies the id-prefix rule to a superseded ticket. A ticket moved to another component, then superseded, stops failingvalidate --strict(and so stops blocking plan merges). A live ticket with the wrong prefix is still refused (kit-328 #454).- The dashboard's Loop page is one page of sortable tables, Orient, Observe, Decide and Act, on the shared page shell, with record peeks, a lesson peek that shows its Evidence and who it was Given to, and a Correct button that opens a thread. An act's class is now escaped wherever it shows, closing an old hole where a class holding HTML ran as script on the dashboard (kit-96 #452).
Why
- Upkeep, unblocking an instance: a superseded ticket under a changed component failed validate and blocked two approved plans (kit-328).
- Approved goal: the dashboard's pages, where the Loop page shows what the supervisor saw, decided and did (kit-96).
- Security: model output on the dashboard is shown as text, never run (kit-96 final-1 F1).
Migration
This is a patch; the box doesn't redeploy.
After adopting:
- Reload open dashboard tabs and restart the dashboard, so the new Loop page is served.
- Nothing else to change.
v0.72.0
What
- The box's gateway serves the hub's memory readings at
/memory.json, to signed-in people only. It forwards only checkedsinceandaftervalues, sends no browser headers to the hub, and gives a 502 when the hub is down, slow (15 s), or answers more than 2 MiB (kit-599 #448). disposerefuses a findings row whose cell count isn't the header's, instead of writing into the wrong cell. Escaped\|counts as text.check-ticket's warning about such rows now says to fix the row's shape first (kit-338 #449).- No GET request to the dashboard changes anything. The Settings page's Check now, which fetches from git, is now
POST /api/fleet-checkwith the owner actions' same-origin checks;GET /api/fleetnever fetches, whatever its query (kit-251 #450).
Why
- Approved goal: box memory monitoring (kit-599).
- Approved goal: org access, where a viewer through the gateway must not change anything (kit-251).
- Upkeep: a review record could lose its Fix text when a finding held an unescaped
|(kit-338).
Migration
This is a minor, and the box redeploys, because the gateway changed.
After adopting:
- Nothing to change for existing sessions;
/memory.jsonis new. - Reload open dashboard tabs and restart the dashboard after upgrading: an old tab's Check now gets an unfetched read, and a new page against an old dashboard gets a 404, until both are current.
- A findings row with an unescaped
|must have its pipes escaped (\|) beforedisposewill fill it. About 80 such rows exist in closed tickets; they need no action unless disposed again.
v0.71.0
What
- The box's gateway signs people in through a table of sign-in methods. One person can have several methods (a passkey, and later others). Each sign-in runs through start and finish routes tied to a short-lived
__Host-flow cookie, so a finish from another browser, a replay, or a flow started on the old gateway is refused. Invites are stored as a hash and checked for expiry. Existing sessions and passkeys keep working (kit-254 #445). - The machine's hub records memory use every minute and serves the last day at
/memory.json(kit-591 #444). - Shift+clicking something that already has an open thread opens that thread, and the kit refuses to start a second thread on the same subject (kit-97 #442).
- Side peeks list their artifacts. A goal's, feature's, ticket's and thread's peek links the artifacts that belong to it (kit-320 #443).
- Upkeep's peek lists its recurring jobs, built-ins and proposed jobs, and each job's peek shows its recent runs once the data exists (kit-166 #446).
- Touches can name parts of any file, not only files listed in split_files (#423).
- A new priority-inversion finding: the metrics flag a higher-priority goal's ticket waiting on a lower-priority one, and D4 orders dependencies by goal priority (#420).
Why
- Approved goals: org access with several sign-in methods (kit-254), box memory monitoring (kit-591), and a cleaner, more consistent dashboard (kit-97, kit-320, kit-166).
- Scheduling: finer touches let more tickets run in parallel (#423), and the scheduler weighs priority (#420).
Migration
This is a minor, and the box redeploys, because the gateway and the hub's code changed.
After adopting:
- A sign-in that was half-finished when the gateway restarted must start again. Signed-in sessions are unaffected.
- Invites written by the old gateway are still accepted.
- Starting a second thread on a subject that already has an open one is refused. Scripts that did that should reply in the existing thread instead.
- validate may report new priority-inversion findings on existing graphs.
v0.70.0
What
- The supervisor's browser has a live view.
preview starton the supervisor browser's record serves a page that shows the browser and lets the owner click, type and paste into it. The view binds to 127.0.0.1, checks Host and Origin exactly, allows one viewer at a time, and Chrome talks over a pipe with no debugging port. Nothing the owner types is logged (kit-66 #439). - The dashboard's autonomy pages are rebuilt. The old Trust, Health, Sensors and Retros pages are folded into the new autonomy pages; every widget kept a place, and
#healthredirects without a history entry (kit-93 #436). - Dashboard and hub copy is shorter. Explanatory sub-lines are gone, and empty states read "None" (kit-95 #440).
- operator.md: the box operator owns the PRs it opens until they merge. It merges main in, never rebases or force-pushes, and never merges or approves its own PRs.
box-statuslists only PRs marked "Opened by the box operator" (#435).
Why
- Approved goals: the supervisor can use a browser with the owner (kit-66), and a cleaner, more consistent dashboard (kit-93, kit-95).
- Upkeep: the operator's own PRs get a clear owner (#435).
Migration
This is a minor, and the box redeploys, because operator.md and hub.html changed.
After adopting:
- The hub's empty thread list and several dashboard empty states read "None" instead of a sentence. Scripts that matched the old sentences need updating.
- A browser view started by an older kit (the 503 placeholder) is still labelled, read and stopped by the new code.
- Repos on upstream_sync "ask" get their usual process question, because operator.md changed.
v0.69.0
What
- The dashboard refuses owner actions that carry no browser header. A request to an owner-action route with neither
OriginnorSec-Fetch-Sitegets 403. Before, a barecurlorfetchfrom any local program could act as the owner. Pages in a real browser work as before. A program that forges both headers still gets through, and the spec says so (kit-324 #433). - The gateway sends the instance's own Origin when it publishes and unpublishes (kit-324 #433).
- A repo doc linked from an owner question is one working link. It opens on GitHub in a new tab, at the branch's sha when known. A ticket id inside a path, branch name or filename no longer splits it into a second link (kit-327 #434).
- An artifact's manifest can say its kind: mock, diagram or docs.
artifact new --kindsets it. The Library's Kind filter reads it, and older cache rows heal themselves (kit-319 #431). - New findings:
- operator.md: an idle fleet is a check-in finding, with the moves to clear it (#356).
- Two flaky tests are fixed (canvas cursors and thread replies; kit-326 #432), along with a Library poll test (kit-325 #430).
Why
- Safety: an owner action now needs a browser, not just any local program.
- Owner-reported bugs: the broken doc link.
- Approved goals: a cleaner dashboard (artifact kinds), and self-improvement (the idle-fleet, PR-stall and serial-graph signals).
- Upkeep: CI that stops failing on timing races.
Migration
This is a minor, and the box redeploys. The gateway must be at v0.69.0 before, or together with, the instances.
If an instance is on v0.69.0 behind an older gateway:
- Publishing fails with 403 and nothing is published.
- Unpublishing still takes the page down, but the instance doesn't record it. Use the Library's Forget to tidy up.
A script that posts to dashboard owner routes has to send the dashboard's own Origin. The kit itself has no such caller apart from the gateway, which this release fixes.
After adopting, validate may warn that the graph is mostly serial. That is a warning, not an error. Repos on upstream_sync "ask" get their usual process question, because operator.md changed.
v0.68.1
What
- The Library is one grid with Kind and Goal filters, a thumbnail per item, the title in each card's head, and the viewer bar's controls (kit-92 #427).
- Tickets hold for a named reason.
ticket hold <id> --reason "…" --for <cause>…andticket releasereplace settingheldby hand. A hold names what it waits on (an owner answer, a PR, a run or an outside party), and a drain names who it is for with--for. Holds without a cause in older logs still read and release (kit-571 #424). - The responder contract. A new writer class, the responder, may reply in threads and hand work to the supervisor. It is refused when it tries to approve, answer the owner's questions, ack findings, record acts, write the supervisor's spend or stamp owner artifacts. Also new: handoff messages, routed and pending turns, and
/api/artifact-fp, the fingerprint of a draft artifact (kit-102 #428). - devteam.mjs's help, command table and dashboard routes are split into named parts, so tickets can claim one group of commands or routes instead of the whole block (kit-322 #425).
- Browser starts can't race. Of any number of starts on one stale lock, exactly one owns it (kit-321 #426). Each start sweeps dead starts' leftover folders and claims, and a start that times out names the lock's path and says when it's safe to remove (kit-323 #429).
- The design canvas shows live cursors (kit-663 #421).
Why
This is work on approved goals: a cleaner dashboard (the Library), fast threads (the responder contract), the supervisor's browser (the lock fixes), and kit upkeep (holds with a cause, and the devteam.mjs parts that let more tickets run at once).
Migration
Adopt as usual. It's a patch, so it lands in place without a box redeploy. supervisor.md changes: holds are now ticket hold rather than ticket set … '{"held": …}', which is refused. A repo on upstream_sync "ask" gets its usual process question.
v0.68.0
What
readyputs the most important work first. After fixes and severity, tickets come in goal-priority order, and a ticket inherits the priority of the most important live ticket waiting on it, shown as "(blocks p2)". Met, parked and drained goals give no priority. Lower-priority tickets still fill a free slot whenever a higher one can't start, and idle-capacity lists in the same order (#419).- Answers keep the owner's pick and words together. The dashboard no longer asks "which choice do your words mean?": a pick is sent with any typed words and recorded as that choice; words alone approve nothing until the supervisor reads them with
answer --read <label> --cite <words> --class <class>, which a correction voids (kit-313 #412). - Threads show the supervisor is responding while it works on an owner's turn (kit-314 #408).
browseris hardened: Chrome is driven over a pipe with no DevTools port; another user's processes are never counted as the profile's holders; a dead owner's lock is taken at once; hosts are cleaned before they're printed (kit-316 #416). After syncing, rundevteam.mjs browser stoponce so a daemon started earlier closes its old port.- A review verdict survives an added
- Records:line and a commit followed by its exact revert (kit-317 #413). - The dashboard's CSS and markup are named regions, so tickets can claim parts of index.html (kit-315 #418).
- The canvas editor's tools: move, resize (small nodes move from inside), held-arrow nudges as one undo, paste of images (kit-669 #414).
- operator.md says the box brings its operator back from a usage limit and shows a box alert once, on the Overview (kit-318 #417).
Why
The owner asked that the scheduler weigh goal priority (#419), and that a pick and typed words be read together (kit-313). The rest is work on approved goals.
Migration
Adopt as usual; the box redeploys once (a minor: kit-318 changes operator.md, which the box image runs). supervisor.md, quality.md and operator.md change, so a repo on upstream_sync "ask" gets its usual process question. After the sync, run devteam.mjs browser stop once.
v0.67.0
What
- The box brings its operator back from a usage limit.
machine limit-state <pane>says whether a pane is stopped at a limit and whether any account has room; the box's minute loop relaunches the operator when one has, leaves a pane alone when a person, a draft or another prompt is there, and raises one alert when every account is out (#271). - The box's alert shows once.
hellocarries the machine's alert asbox_alert, apart from the project's ownalert, so the hub shows it once on the Overview instead of a "!" on every project's tab (#333). - Capacity.
accounts-tickrecords how much Claude room the fleet has left, when it runs out and when the first account resets;machine statusprints it and warns when the room runs out before a reset (#265). askneeds a default on clarifications and rung-2 owner-decisions, or a stated reason, so work doesn't wait on an open question without one (#362).- Artifacts stay clickable after typing a capital letter in one of their fields, and
artifact checkwarns of remote images (#381). devteam.mjs browser: a headless Chrome only the supervisor can drive, with one private profile per project, in its own tmux window; contractbrowser@1(kit-64 #411). Further hardening follows in kit-316.- The design canvas: a three-way
mergeof a changed copy into edits (kit-653 #410), and the editor keeps each person's edits safe across drops, sends drags live and gives each person their own undo (kit-668 #409). - The box image is stamped v0.67.0.
Why
The operator and the owner were each left waiting by usage limits and by an alert repeated on every tab; the rest is work on approved goals.
Migration
Adopt as usual; the box redeploys once with the new image (a minor: #271 changes cloud/Dockerfile, and #333 and #265 change the hub and machine status). supervisor.md and quality.md are unchanged by this release.
v0.66.0
What
- A thread turn that reaches no supervisor says so. When an owner's turn can't be typed into a supervisor's pane (none recorded, or the session runs outside tmux), the CLI and the dashboard card say it was not delivered and when the supervisor last checked, instead of "Sent". A turn left undelivered for over 5 minutes raises a high finding that reaches
machine statusand the hub through the project's hello alert (kit-311 #404). - A supervisor keeps its loop from the moment setup ends. Its prompt closes by saying: once start-up has run, start
devteam.mjs waitin the background, tick when it returns, and never end a turn without a wait running.init's last line says the same (kit-310 #399). - The box's terminal moves between tmux windows with ⌘⌥←/→ on a Mac, Ctrl+Alt+←/→ elsewhere; off a Mac that chord is taken from what runs in the pane (#306).
- The image list covers what the box relies on in a project's kit.
box-pins changednow reads as a minor any change to the operator's read-only guards, the dispatcher and operator-role guard (a newdispatchregion, so a new command stays a patch), what the boot script calls, the supervisor-pane writers, the hub's ports,dashboardHub(the hub port check, hoisted out of the dashboard command) and the classifier itself.--smokeremoves only its own worktree (kit-306 #397). - Waits name their cause (next-move@1, additive). Tickets gain
held_for,held_untilandfrom; goalshold_forandhold_until;waitCause()parses a cause; next-move@1 gains follow-up, thread, answer, duty and record subjects and a ticket move'swait. No rows use them yet (kit-570 #400). - Review metrics count findings by category.
metricsshows each stage's top blocking categories beside its top rules; the worker prompt names the author checks; quality.md glosses every category word (kit-309 #403). - The design canvas edits and renders. The editor's move, frame, text, shape, image and component tools and properties panel, sent live, with a tool bar that steps down on narrow stages (kit-662 #402); and
canvas.mjsrenders a document's first page as static, escaped HTML with caps on instance expansion and output size (kit-654 #401). Canvas keys may contain dots, and the server and the editor refuse the same control characters in names and text (tab, LF and CR allowed); an upload name with them falls back to "image" (kit-312 #406). - The box image is stamped v0.66.0.
Why
An outside adopter's thread went 22 minutes unanswered because its supervisor stopped checking after setup and wasn't in tmux, and nothing told the person. Since v0.65.0 patches land in place, so the list of what the box relies on has to be complete. The rest is work on approved goals.
Migration
Adopt as usual; the box redeploys once with the new image (a minor, because the terminal keys change cloud/Dockerfile). quality.md changes: a repo on upstream_sync "ask" gets its usual process question.
v0.65.1
What
- The first patch release: it lands in place. The box does not redeploy and no session restarts. Each project's dashboard picks up the new kit on its next sync and restarts itself onto it; the box image stays on v0.65.0.
- Upkeep jobs are the owner's call (recurring@1). A new owner-only decision class,
recurring-edit: adding, changing or removing an Upkeep job lands only with the owner's answer to that exact change. The constitution lists it beside the other owner-only classes; the contract, its fixtures and the dashboard's Upkeep data shape come with it. No Upkeep rows run from it yet (kit-161 #390). - The canvas document model.
docs/devteam/scripts/canvas.mjsvalidates and edits canvas-doc@1 documents (elements, components, instances, styles) by the contract, with size caps and refusals; the editor and static page build on it next (kit-652 #391). - Specs and plans are checked by their authors before review. worker.md: run each acceptance check against broken code before asking for review, and back each claim about existing code with a file:line or a command you ran; a spec that defines a contract has a required "Refusals and edges" section; a plan maps each spec check to the task and command that proves it. quality.md: a gap outside the ticket's done-whens and contracts is Minor, and each finding opens with a category word (kit-308 #396).
- CI flake fixed: the dashboard's open-select test raced the previous subtest's route and failed now and then on a loaded runner (kit-307 #398).
Why
Nearly every spec and plan failed its first review; the owner approved four rules to catch the common causes before review. Upkeep jobs run work on the owner's behalf, so changing one is now the owner's decision. The canvas model is the next step of the design-canvas goal.
Migration
Nothing to do: a patch lands in place, with no box redeploy. worker.md, quality.md and constitution.md change: a repo on upstream_sync "ask" gets its usual process question.