Ready the v0.2.0 changelog for release and draft the promotion post - #186
Merged
Conversation
The Unreleased section read as a reverse-chronological merge log: three usage-cap entries led Added while refine, quick-messaging and document links sat below the fold, and an audit of the 93 commits since v0.1.0 found two dozen user-facing changes with no line at all. Add entries for refine, the Config screen, mouse selection, markdown task bodies and the agent-voice gutter, state-coloured queue rows, hand-offs on the running strip, stale-branch detection, proportional re-review, project archiving, the unblock bonus, the Claude Code plugin, the footer's database name, the static review keys, the attention-priced queue, the answer-in-session pivot, the digit rebinding, the gated first run, the dropped dirty-tree guard, the prompt changes, and fixes for session liveness, status-line clipping, kind-keyed dependency edges, the incomplete-report marker and the jump-in verb. Reorder each section to lead with its headliners rather than its most recent merge, and correct three entries that had gone stale: dispatch session names now carry a title slug, the key map pages on tab, and CI pins the declared MSRV. The version heading, its compare link and the ReleaseDate placeholder are untouched; `Unreleased`, `...HEAD` and `ReleaseDate` each still occur exactly once, and a cargo-release dry run applies all four replacements without error.
Both images showed a UI that no longer exists. `voro-tui.png` predated the footer store indicator; `claude-voro.png` predated the state column, the running strip and the current key line, and was shot against the operator's real board, so it carried real project names and task titles into a README about to be promoted. Both are now taken against the `voro seed` fixture, which covers every state, live and dead sessions, and the proposal digests. One review task is dressed with a completion summary written in markdown, so the card shows what the agent-voice gutter and the body renderer actually do with one. `claude-voro.png` keeps its two-pane framing. The left pane is filtered with `claude agents --cwd`, which scopes the view to sessions started under one directory, so it shows exactly the two sessions Voro's running strip carries and nothing of the operator's real work. The cockpit pane is 110 columns because the window is narrow: at 109 the header runs the project list into the state counts (#487), and much above 115 the footer names the scratch database. The scripts that rebuild the board and render the capture are not committed; they live outside the repo.
MJohnson459
force-pushed
the
changelog-v0.2.0
branch
from
August 20, 2026 21:38
d96be89 to
b63ff45
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Editorial pass on the Unreleased section of CHANGELOG.md so it reads as v0.2.0's story rather than a merge log, and so cargo-dist's generated release notes are worth reading. Branch changelog-v0.2.0, one commit (d96be89), rebased onto origin/main (e68e85c), touching CHANGELOG.md only. 37 entries in, 62 out (Added 16 -> 29, Changed 13 -> 20, Fixed 8 -> 13), plus a lede paragraph. See the full report in the task's completion summary event; the branch also carries the #181 cap-reset entry, preserved verbatim through the rebase. Verified: cargo-release dry run applies all four replacements without error; Unreleased / ...HEAD / ReleaseDate each occur exactly once; cargo test --workspace 922 passed, 0 failed.