From 28c1b28d7c4a5d4689c763e86075c25f8a541bbb Mon Sep 17 00:00:00 2001 From: prode Date: Sun, 2 Aug 2026 20:44:09 -0300 Subject: [PATCH] docs(assets): state the stack rule without naming an ecosystem MIME-Version: 1.0 Content-Type: text/plain; charset=UTF-8 Content-Transfer-Encoding: 8bit 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) Claude-Session: https://claude.ai/code/session_01GchWF6iL5PjTdXAT8H3mhb --- internal/assets/templates/docs/stack.md | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-) diff --git a/internal/assets/templates/docs/stack.md b/internal/assets/templates/docs/stack.md index eadee33..2822830 100644 --- a/internal/assets/templates/docs/stack.md +++ b/internal/assets/templates/docs/stack.md @@ -2,8 +2,8 @@ Every adopted technology, with one line on why it earned its place. **Technology that is not listed here is an open decision, never something adopted silently** — -and because dependency manifests are structured data, that rule is checkable: a -direct dependency in `go.mod` or `package.json` that is absent from this file is +and because this project's dependency file is structured data rather than source, +that rule is checkable: a direct dependency declared there and absent from here is reported. So adding a dependency is a two-step act: add it, and say here why.