README: what the gates actually caught - #8
Merged
Merged
Conversation
The README asserted its benefits and offered no evidence, in a repository whose PRINCIPLES.md says evidence beats opinion. A fair reading called that out. Six defects, each with the gate that caught it: the broken links shipped to every adopter, the registry row blanked instead of removed, the JSON parsed from a stream carrying stderr, the scoped bootstrap resolving to 404, the five gates reporting "no package.json" to a project that has one, and the P0 blocker invented out of prose. Stated for what it is: devia run on devia and on one real project, not independent adoption. Claiming more would be the same failure the last two entries describe.
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.
The README asserted its benefits and offered no evidence, in a repository whose PRINCIPLES.md says evidence beats opinion. A fair reading called that out.
Six defects, each with the gate that caught it: the broken links shipped to every adopter, the registry row blanked instead of removed, the JSON parsed from a stream carrying stderr, the scoped bootstrap resolving to 404, the five gates reporting "no package.json" to a project that has one, and the P0 blocker invented out of prose.
Stated for what it is: devia run on devia and on one real project, not independent adoption. Claiming more would be the same failure the last two entries describe.
Summary
Type
Devia compliance
.devia/layout, CLI contract):CHANGELOG.mdupdated:npm run build:index):Checks
npm run validatepassesnpm testpassesnode bin/devia.mjs check --root .passesdevia initstill produces a valid project (devia validateclean in a scratch repo)Not verified