Repository navigation
docs: sharpit 0.7.0 plan (BootUI 2.4.0 parity) - #208
Merged
Merged
Conversation
… the pin wave, and narrows the 2.5.0 claim
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.
Summary
The implementation plan for sharpit 0.7.0, which targets BootUI 2.4.0
(
docs/superpowers/plans/2026-11-18-sharpit-0.7.0/):PLAN.md: the master plan. A pin wave (W0) moves the parity tests and status files to the BootUI 2.4.0 fixtureswithout changing behaviour. Track A ports what 2.4.0 changed in existing features; Track B closes the remaining
gaps (routes, insight kinds and the journal sources they read); Track C is the command-line client (0.6.0: sharpit command-line client (BootUI CLI parity) #60, its own
plan); Track D holds the engineering items deferred from 0.6.0; Track E fixes the open bugs (0.5.0: a fully passing run exits 1 when one advisor can only partly assess the app #65, 0.5.0: a dismissed finding comes back when any line above it moves #66, 0.5.0: the same pytest --sharpit command gives different results depending on which tests ran #67, fix: --sharpit-app reports an uninspectable app as unknown, not as an empty pass #207).
The decisions the lanes depend on are recorded with the option chosen.
W0-pin.md: the pin wave, task by task.Every BootUI path and line cited was checked against tag
v2.4.0; the Track A BootUI tests named still exist atv2.5.0.Test plan
uv run ruff format --checkon the plan folderuv run pytest -q -n 4 tests/docsuv run python scripts/dev/active_plan.pyreads the plan