Repository navigation
docs(assets): state the stack rule without naming an ecosystem - #8
Merged
Merged
Conversation
The seeded docs/stack.md said a dependency "in go.mod or package.json" is reported, which names today's two parsers rather than the rule. The rule is about a project's dependency file being structured data, and it holds in any ecosystem that has one — the validator gains parsers, and a seed that enumerated them would read as wrong in every project that uses neither. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01GchWF6iL5PjTdXAT8H3mhb
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 seeded
docs/stack.mdsaid a direct dependency "ingo.modorpackage.json" is reported. That names the two parsersinternal/validate/stack.gohappens to have today, not the rule.The rule is that a project's dependency file is structured data rather than source, which is what makes "technology not listed here is an open decision" checkable at all — and it holds in any ecosystem that has one. The validator is expected to gain parsers; a seed that enumerated them reads as wrong in every project using neither, and goes stale in the rest.
Prose only, in a seed.
assets.Versionis untouched — a seed is not a managed file, so nothing in any manifest changes andscc updatehas nothing to offer here either way. Workspaces created before this ship keep the older wording; that is what untracked means.Note:
.claude/rules/knowledge-base.mdstill carries the same ecosystem-specific sentence. Changing it is a workspace-template edit and costs a template-version bump, so it is deliberately not in this PR.🤖 Generated with Claude Code
https://claude.ai/code/session_01GchWF6iL5PjTdXAT8H3mhb