docs: document devup_visual_compare and devup_feature_trace in the tool inventory - #41
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
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.
The README said the server has seven tools and listed seven. It registers nine.
devup_visual_compareanddevup_feature_traceshipped without ever being written down.That matters more than a stale number: the README states outright that it, together with the schemas the server publishes, is the authority on the current tool list -
docs/superpowers/is explicitly described as a record of its own moment rather than current API documentation. So the one document a caller is told to trust was the one omitting two tools.What changed
프로젝트 쪽 도구, which previously described three of the five.The wording is taken from the tool descriptions the server actually publishes, not written fresh, so the README and the schema say the same thing:
devup_visual_compare- never renders, never launches a browser, never runs a command; the consumer producesactual.pngand this compares pixels in pure Rust. An absent, incomplete or invalid renderer environment manifest yieldsinconclusiveeven whenvisual.passedis true.devup_feature_trace- starts only from explicit anchors and refuses anchorless prose. Hops are evidence-backed orUNVERIFIED;requirement/acceptanceCriteriaare echoed without interpretation; static parsing never proves runtime behaviour.Documentation only - no crate changed, so no changepack.