DevCake v0.6.2

Patch release in the v0.6 "Kentucky Butter" line — the activity repository becomes the record of a mission's run (ADR-0043). devcake-cli stays at 0.1.8.

Every Dev receives the whole record of every mission upstream of its work. The upstream folders in a Dev's workspace are now copies of each upstream mission's activity repository: the decomposition ancestors to the root, the project the mission belongs to, and every direct blocker that finished. Each folder holds that mission's brief, its full feed and every attachment, so a starting attachment on a blocker's ticket reaches the dependent instead of being lost in the thread. The byte budget is decided from the record's sizes before anything is fetched; a mission that never ran is rebuilt from the vendor and marked as such; an unreadable blocker is disclosed, never a reason to hold a dispatch.

The activity repository is kept current. It used to be written once, before a step launched. It is now refreshed at every run boundary: each step close including failures, completion, hand-offs, a pull request closed unmerged, and a conflict routed back. Reading the record from the internal forge costs nothing against a vendor's request budget, which is what makes "every direct blocker, no count cap" affordable.

A project's own run leaves a record. DevCake used to suppress every write to a project, so the step that split a project, its transcript and its reasoning were invisible to the children. A project run's step card, its notices and its decomposition note now post as project updates, the transcript uploaded and linked, through the same chokepoint issues use. Those cards appear in the project's Updates tab.

Upgrading a host.

devcake up --release

Full detail: CHANGELOG.md, ADR-0043 and the living log in docs/16-roadmap.md.