docs: document the Go toolchain-floor policy#109
Merged
Conversation
The Go floor in go.mod is tooling-driven (raised to 1.25 because the shared validate-go-project Dead Code Analysis step installs deadcode, which needs Go >= 1.25), but the selection rule lived only as a one-line rationale in the project overview. State the forward-looking policy explicitly in the Maintenance section — floor = highest minimum the house tooling requires, not latest Go and not a language-feature choice; go.mod is the single source of truth; bump only when tooling/security forces it and record the trigger in the PR body; don't over-raise. Add a toolchain-floor-freshness task-menu item. Fixes #106 Co-Authored-By: Claude Opus 4.8 (1M context) <noreply@anthropic.com>
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.
Fixes #106 (part of epic #104, theme 2 — toolchain & scaffold currency).
Problem
The Go floor in
go.mod(1.25.10) is tooling-driven, not a language-feature choice: it was raised from 1.24 because the sharedvalidate-go-projectDead Code Analysis step installsdeadcode, which needs Go ≥ 1.25. That rationale lived only as a one-line sentence in the project overview. Without a stated policy, a future bump (or a failure to bump) looks arbitrary, and "why 1.25, not latest, not 1.24" gets re-litigated each time the toolchain moves.Change (docs / agent-file only)
AGENTS.md## Maintenance:Toolchain-floor policyparagraph — the floor = the highest minimum the house tooling requires (todaydeadcode⇒ 1.25), not "latest Go" and not a language-feature need;go.modis the single source of truth; bump only when a shared-tooling requirement forces it (or a security / end-of-life reason), never speculatively, and record the trigger in the PR body; don't over-raise.Toolchain-floor freshnesstask-menu item — on any toolchain/tooling bump, re-confirm the floor is still exactly the minimum the tooling needs and that nothing reintroduced a hard-coded Go version that could drift fromgo.mod.Accuracy note
Verified live before writing: nothing in the repo hard-codes the Go version —
copilot-setup-steps.ymlreadsgo-version-file: go.modand the README points atgo.mod. So the policy states there is no second copy to keep in sync, rather than implying phantom duplicates (the generic issue text assumed badges/setup hard-code it; they don't).Acceptance criteria
AGENTS.mdstates the floor-selection rule + current trigger, withgo.modnamed as the source of truth.No code touched → the ruleset-injected
validate-go-projectGo jobs skip via change-detection; MegaLinter/cspell cover the prose (British spelling + acronym reworded to safe terms to keep cspell green).