chore: the manifest described a repo that no longer exists - #235
Merged
Merged
Conversation
gh reposync --apply put spec-kit back as a topic and would do it again every run. The manifest is not inert: it is what --apply writes to GitHub, so a stale entry actively restores wrong public metadata rather than just sitting there. Nothing in the repository checks it, and this one described a Spec Kit workspace that has not existed since the reorganization. An audit of the other six found them accurate, so this was the only one. CONSTITUTION.md still described the old shape. It talked about memory, archival, features and spec.md, and the rule about a rule being reachable from its repository carried three paragraphs on how the attempt to make it a charter fragment failed. That is the history of how it was written rather than what it says, which is the thing the document itself forbids two sections above. Both sections now describe what this is: a tree of pages, a component README linking its subjects, a change merged into the page that already covers it.
|
Thank you for contributing to this project! 😊🕹️ |
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 stale descriptions of a repository that changed shape.
The manifest
gh reposync --applyputspec-kitback as a topic, and would do it again every run.The manifest is not inert. It is what
--applywrites to GitHub, so a stale entry actively restores wrong public metadata rather than just sitting there looking wrong. This one described a Spec Kit workspace that has not existed since the reorganization.I audited the other six manifests against what each repository actually is. All accurate, so this was the only one.
CONSTITUTION.md
It still described the old shape: memory, archival, features,
spec.md. And the rule about a rule being reachable from its repository carried three paragraphs on how the attempt to make it a charter fragment failed, which is the history of how it was written rather than what it says.That is the thing the document forbids two sections above: "What never appears is commentary about the document: how a fact was found, that a fact is important, or what an earlier version said."
Both sections now describe what this is: a tree of pages, a component README linking its subjects, a change merged into the page that already covers it. The rule keeps its evidence, which is the measurement that produced it, and loses the story.
🤖 Generated with Claude Code
https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c