docs: point at the design docs, and stop describing Spec Kit - #72
Merged
Merged
Conversation
The private dependency recipes ran `go get -tool` for gofumpt, golines, golangci-lint and gocover-cobertura. Every one of those tools is already recorded in the consuming module's `tool (...)` block, so `go tool <pkg>` resolves it from the module graph and nothing needs installing. What `go get -tool` added was a re-resolution to whatever is newest, rewriting go.mod and go.sum in the process. That rewrite made `go-mod-check` unpassable. It runs in the same `go-test` chain, so CI mutated the checkout and then failed the build for being mutated: `upgraded go-diff v0.8.0 => v0.9.0` followed two lines later by `untidy: .`. Any upstream tool release turned every open pull request red across the organization, while each default branch stayed green because its run predated the release. Depend on _go-mod-download instead, which downloads and changes nothing. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c
CONTRIBUTING.md and AGENTS.md both said the conventions live in the specs repo "whose .specify/memory/ is the standing record", and both carried a paragraph forbidding superpowers because Spec Kit governed specification and planning. Neither is true now. That repo is reorganized to components/<name>/ with the docs at the top level of each, and Spec Kit is removed from it entirely, so the prohibition has nothing left to protect and the pointer named a directory that no longer exists. Both now say the same shorter thing, in the same words as every sister repository: how this repository is built is documented under components/osapi-justfiles/ in the specs repo. Read it before changing behaviour, change it when you do.
|
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.
Paired with osapi-io/specs#226, which reorganizes the specs repo and removes Spec Kit.
CONTRIBUTING.mdandAGENTS.mdboth said the conventions live in the specs repo "whose.specify/memory/is the standing record", and both carried a paragraph forbidding superpowers on the grounds that Spec Kit governed specification, planning and implementation.Neither holds now. That repo is reorganized to
components/<name>/with the docs at the top level of each, and Spec Kit is gone from it, so the prohibition protects nothing and the pointer named a directory that does not exist.Both files now say the same shorter thing, in the same words as every sister repository:
just testpasses.🤖 Generated with Claude Code
https://claude.ai/code/session_01FuKUsHFG1EqZXamffh9M2c