The skill's SPECs stop narrating the caller's dashboard - #1744
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
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.
Reading
packages/skill-branches/SPEC.mdon GitHub after #1743, I saw it still narrates The Framework's dashboard — its checkout list and its Remove/Prune buttons — as if the package had one. A dashboard is a fine example of a caller; its buttons are not the package's business. Three lines, SPEC text only.🤖 curated · Fable 5, effort high
SPEC.md: "a daemon that starts agents (allocation, teardown, the reclaim sweep), a dashboard (the retained-checkouts list, the Remove and Prune buttons)" → "a daemon that starts agents, a dashboard that lists and reclaims checkouts".src/cli.SPEC.md: "without opening the dashboard" → "without any other tool".src/reclaim.SPEC.md: "a dashboard's Remove button" → "a dashboard's remove action".Kept: the '"remove this" button' rationale in
worktree.SPEC.md/worktree-size.test.SPEC.md— it explains why the size read is best-effort, and names no product.Proof: skill-branches 117/117, framework 1471/1471 green in a fresh worktree off
6611a77a.