feat: add the burnlist lifecycle CLI#3
Merged
Merged
Conversation
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
2 participants
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.
Adds the authoring/execution CLI for burnlists: create, inspect, and move
them through their lifecycle from the terminal.
New commands:
burnlist new— allocate a collision-safe id and scaffold a draftburnlist show <id>[#item]— read-only view + a copy handle (repoKey/id#item) and, when a dashboard is running, its URLburnlist ready/start/close— move a burnlist draft → ready → inprogress → completed, each gated and atomicburnlist burn <id> <item>— complete an active item (ledger + delete +--check)Lifecycle moves take a per-id lock, revalidate under it, publish with a single
rename, and append the completion digest idempotently before closing — so a
reader or the dashboard never observes a half-moved burnlist.
Under the hood, plan parsing/validation is extracted from the dashboard server
into
src/server/plan-model.mjs(byte-identical) so the CLI and the read-onlyobserver share one implementation. The dashboard stays a pure observer; only
the CLI mutates canonical state.