Shipped and released
Now
Page 11 of 14. Every release ever published is still here — across these pages, in theAtom feed, and at its own permanent link. Nothing is dropped as it ages.
Released highlights, page 11
- Every experience-design skill now tells you how to start it. None of the pack's twenty skills documented an example phrase, so a person had to guess the wording and the agent had nothing to match against. Each skill now carries two to four phrases someone would actually type, sharpened so neighbouring skills in a twenty-skill pack do not claim the same request.
- Every frontend-engineering skill now tells you how to start it. As with experience-design, none of the nine skills documented an example phrase. Each now carries example utterances that match what the skill genuinely handles.
- Evidence from a run now has a place to go that the approved plan does not. Once a plan is approved it is pinned, so a task that asked for its own observed result to be written back into it could never be satisfied. Plans now keep the obligation and a sibling verification ledger keeps the observation — the mutation that was applied, the check that went red, the digest that was compared. One convention states when substantive edits stop, and a check fails if that statement is reverted.
- Work-loop now gives each scheduled plan task a bounded sequential implementer dispatch. The controller retains lifecycle, review, and closeout ownership while the task brief carries its execution root and applicable craft guidance.
- A local dependency can keep resolving after the delivery it names has been closed out and pruned. Put a completion receipt with
delivery_id,outcome,completion_event, andevidence_refon the citing local need. Onlycompletedsatisfies the dependency;abandonedandsupersededkeep the refusal visible. - Completion receipts now fail before they are written when their delivery result or evidence fields do not match the published contract. This keeps a malformed receipt from becoming the only surviving account of a pruned dependency.
- A local dependency can keep resolving after the delivery it names has been closed out and pruned. Put a completion receipt with
- Closeout no longer offers to close an initiative that still has shaping or delivery-brief work open. Eligibility was read from the initiative's spec work alone, so an initiative whose every spec had shipped was recommended for closeout while its intents and draft delivery briefs were untouched. It now reports a named blocker instead, and stops recommending the skill that distils and dispositions.
- Both record shapes now count as remaining shaping work. A shaping record written in the canonical form was invisible to the check, which read only the older shape — so an initiative whose remaining shaping work was written entirely in the current form looked empty. Retiring a record now stops it counting in both shapes alike, where before the two forms disagreed. A shipped, withdrawn, or cancelled delivery brief is still correctly treated as finished.
- The deferral-token convention now states the rule the tooling enforces. An open register entry needs an artifact of its own in
Draft, unless it is a defect; it cannot point at the shipped document that recorded the deferral, because a shipped or accepted carrier and an open register membership cannot coexist. The previous wording directed authors to exactly that shape, so following it produced a record the tooling refuses to route. - The convention now warns that a deferral marker outlives its own record. A
(deferred: <slug>)marker left in a body that later freezes pins its register entry open permanently, because the frozen body can no longer be edited to retire the marker. - Removed a reference to a repository-only test path. The clause pointed adopters at a file that exists only in this repository, and at a count ceiling that no longer exists.
- The deferral-token convention now states the rule the tooling enforces. An open register entry needs an artifact of its own in
- Closeout no longer offers to close an initiative whose remaining work the status surface says it cannot route. Deciding what a lifecycle record has retired now reads the same verdict the reconciliation layer reached, instead of rebuilding a guess from the entry's name. An entry recorded in an older shape is retired exactly when its artifact is; an entry the surface declines to route at all is never quietly treated as finished.
- An initiative whose work has all been retired now reaches closeout instead of reporting unfinished work forever. Whether anything is still outstanding is decided once, by a single pass that excludes what a lifecycle record has already retired — so two halves of the same answer can no longer disagree. An artifact named by one of a record's alternative locators counts the same as one named by its main locator.
- When that reading is incomplete, the status surface withholds its suggestion to close out rather than making it anyway. A record that cannot be read, or whose review date cannot be judged, is reported as a named blocker instead, so a workflow that distils and disposes is never recommended on partial evidence. The prompt an agent renders reads the same facts, so the two agree.
- Repair and migration are settled as unaffected by retirement, not left pending. Planning, applying, recovering and rolling back a repair or a migration behave identically whether or not lifecycle records are present, pinned by paired runs so a later change has to alter those lines and say why.
- Quality review now spots four tests that can stay green while proving nothing. It calls out empty-set assertions without a positive control, unstubbed negative cases, source-text checks that do not exercise a security control, and prose that substitutes for a captured baseline.
- Each reviewer now owns its concerns outright, so the same defect stops arriving twice under different severities. Adversarial owns contract conformance, scope and structural fit; quality owns whether a test can actually fail and the edge cases a spec never named; security owns every threat finding. A reviewer that notices another lens's concern says so in its own lens instead of emitting that lens's finding.
- A clean review no longer pays for a model call to confirm it is clean. The loop classifies a persisted reviewer report structurally rather than comparing it byte-for-byte to one sentence, so an ordinary clean pass skips adjudication. A report carrying security-reviewer's mandatory coverage-disclosure footer still takes the full adjudication path, because that footer is prose and prose is what adjudication exists to read.
- A naming quibble no longer costs the same as a correctness blocker. Nits do not block readiness and are never fixed automatically. They are recorded with their citation, deferred, and acted on only when the thread means to change the code because of one — and promoted first if that repair turns out to change behaviour, architecture, dependencies, or more than one file.
- Security findings are now priced against a named attacker. A finding has to be reachable on a path this codebase runs and must not rest on a capability that already gives the attacker an easier route. This narrows severity and never coverage: an unpriced real weakness is still reported, and a trust-boundary crossing, missing authentication check, leaked secret, or spec-required control never drops on likelihood alone.
- Delivery briefs now distinguish withdrawal before execution from cancellation after execution starts. Open programmes remain Executing when their current slices have shipped but later slices are not materialized, and successful closure still needs an explicit Shipped decision.
- Re-issuing a review recording no longer risks counting the round twice.
loop-cohort review recordtakes an optional--operation-idnaming the round. Repeat the same recording under that id and the command reports a completed write and changes nothing; supply a different payload under it and the command refuses rather than silently accepting it. A session that dies before it learns whether the write landed can now simply repeat the command.
- Re-issuing a review recording no longer risks counting the round twice.
- `workspace-status` now tells you what closed-out work is waiting on you, and stops showing you work that is already finished. Orientation reports how many cooling reviews are due, names each one, and lists retention exceptions with the role that owns them and the date they are due. An artifact that has finished cooling is no longer offered as something to start, and is no longer opened, so a session begins on live work rather than on settled deliveries.
- A retention exception stays visible, because someone still owes work against it. Only artifacts whose lifecycle record says
CoolingorRetiredare excluded;RetainedandExternalAdvisoryrecords are projected and their artifacts remain available to start. - Orientation says whether the exclusion is complete. If a lifecycle record or the cooling module cannot be read, the run still projects the workspace and reports
cooling_context_visible: true. That means the exclusion may be incomplete, not that it did not happen: one unreadable record leaves every other record still cooling its artifact, and the accompanying finding says which case you are in. - A brief whose declared child has cooled holds its dependants back. When a spec names a brief through
source.parentinworkspace.tomland that spec cools, the brief stops satisfyingkind = "brief"dependencies until its child scope is re-established. Cooling is otherwise subtractive; this is the one place it withholds work, and it exists so a lifecycle record cannot make a blocked spec dispatchable by hiding a child's real state. - Repair and migration keep their previous behaviour and still reach cooled entries; whether cooling constrains them is a later decision.
- Assimilated primitives finish against the target catalogue's own release contract. Catalogue curators now close version, inventory, release-history, and projection duties instead of stopping after the content write.
- New pack proposals reuse the target catalogue's RFC workflow. The proposal adds its primitive inventory without copying or drifting the canonical RFC template.
- The spec-metadata check now looks at the specs you touched, so finishing a work loop takes about two seconds instead of about thirty. It used to re-read all 423 specs and start a Git process for each one. Two checks still cover every spec regardless: the dangling-reference scan, and the one that resolves each deferral marker — because retiring a tracked follow-up can invalidate a marker in a spec you never opened. The remaining per-spec checks cover what you changed, and
--allruns the full audit — wire that into a gate.
- The spec-metadata check now looks at the specs you touched, so finishing a work loop takes about two seconds instead of about thirty. It used to re-read all 423 specs and start a Git process for each one. Two checks still cover every spec regardless: the dangling-reference scan, and the one that resolves each deferral marker — because retiring a tracked follow-up can invalidate a marker in a spec you never opened. The remaining per-spec checks cover what you changed, and
- When saving project knowledge runs out of time, it now says so and tells you to try again. It used to report a storage-capacity problem and advise fixing the request, and on the save path it could even claim another writer was mid-migration — so a run that simply needed more time looked like a request you had to rewrite, and the step that records lessons could not finish for anyone who did not read the exit code.
- The corpus now answers how a skill composes with subagents, hooks and packaged bundles, and keeps the portable question separate from any one tool's answer. Three portable floors were admitted — skills with subagents, hooks, and plugin packages. Each states the questions worth asking before reaching for a tool's syntax, and each says out loud that event names, configuration paths and output protocols belong to the tool rather than to the floor. Sixteen of thirty-six subjects are now carried and twenty remain recorded as absent.
- A capability claim about a tool now carries a lifecycle state, so nobody reads "we checked" where the truth is "we read the manual". Each claim records its first-party source, the date it was retrieved, the version that source exposed, and one of four states. A claim confirmed by actually exercising the behaviour reads
verified; a claim taken from documentation alone readsexperimentaland is not a support claim; a claim whose verification window has run out readsstaleand returns provenance instead of guidance; an absent capability readsunavailableand is recorded as a difference rather than a gap. - Claude Code is the first tool profiled, and three of its seven capabilities are backed by an actual probe rather than a citation. Skill body loading, subagent context isolation and worktree isolation were exercised directly and read
verified. Nesting limits, hook scoping, managed hook policy and package-supplied agent precedence are documented but unexercised, and readexperimentalon purpose.
- The reference corpus now answers language and execution questions, and says out loud which ecosystem and which versions each answer holds for. Five topics were admitted: Python with pytest, TypeScript/Node with JavaScript test runners, process and filesystem cost, pack and continuous-integration critical paths, and worktrees with state locks on a shared host. Twelve of thirty-six subjects are now carried and twenty-four remain recorded as absent.
- Two answers that a single ecosystem's own documentation settles are now admissible. Earlier, a claim shipped only on two independent observations or two vendors agreeing. That bar silently excluded anything true of exactly one ecosystem — a language's own test runner, for instance. Such a claim now ships only when it names its ecosystem, an explicit version range with both bounds, and the vendor documentation it comes from.
- Exact clean reviews now finish without a redundant adjudicator call, while low-risk agent-context changes can remain in light mode. Mandatory automated reviewers no longer make work multi-person, and security review is tied to changed trust boundaries, data flows, or guarding controls.