The quickstart never ran this package, and one claim went stale - #33
Merged
Conversation
Two documentation corrections, both found while running the commands rather than reading them. THE QUICKSTART DID NOT USE THIS REPOSITORY. "Try it in five minutes" installed ds-mcp and never mentioned dspack-validate, the binary this package ships. A reader arriving at the specification repository was sent to a different one before seeing anything this one does. The harness now runs first: one command, no install, and it compiles every schema and validates the bundled examples, so you can see the spec is self-consistent before you commit to anything. Stated carefully, because the obvious phrasing would be wrong: dspack-validate does NOT accept a file argument. It checks this package's own schemas and examples. Describing it as "point it at your contract" would have been a plausible sentence that fails the moment anyone tries it. The agent step keeps its curl, which it needs, and is now clearly the second step rather than the first. A STALE VERSION CLAIM. The Implementations section said dspack-export "generates a dspack v0.2 file". It has declared v0.4 snapshots since 0.3.0, and this repository's own spec section describes v0.4 as current two paragraphs earlier. It now says "spec-current", which stops the sentence needing an edit at every spec revision. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
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
1 participant
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.
Two documentation corrections, both found by running the commands rather than reading them. Part of the Aesthetic Function lab-repositioning roadmap (Phase 4, ecosystem propagation).
The quickstart did not use this repository
"Try it in five minutes" installed ds-mcp and never mentioned
dspack-validate, the binary this package ships. A reader arriving at the specification repository was sent to a different one before seeing anything this one does.The harness now runs first: one command, no install, compiles every schema and validates the bundled examples.
Stated carefully, because the obvious phrasing would be wrong:
dspack-validatedoes not accept a file argument — it checks this package's own schemas and examples. Writing "point it at your contract" would have been a plausible sentence that fails the moment anyone tries it. (I made exactly that mistake on the website first, and am fixing it there too.)The agent step keeps its
curl, which it needs, and is now clearly the second step.A stale version claim
The Implementations section said dspack-export "generates a dspack v0.2 file". It has declared v0.4 snapshots since 0.3.0, and this README's own spec section describes v0.4 as current two paragraphs earlier. It now reads "spec-current", which stops the sentence needing an edit at every revision.
Verified
🤖 Generated with Claude Code