v4.1.0 — synced to the self-improvement rule; no gate to add

Synced to baseline v4.1.0, commit 99a94e0 — gaps found in a project flow back to the corpus. SPEC.md is the only file that moved here, and that is the finding rather than an omission.

What the baseline changed. SKILL.md Handing the work back now takes a baseline gap as a next step — the checklist had no section and you settled it by inventing, or a rule names a dependency the standard library now covers — and forbids editing the baseline as a side effect of project work. README.md takes the other direction at every Go major: read the release notes for what moved into stdlib, and rewrite the pattern that prescribed the dependency rather than retiring it.

Nothing moved here, because neither rule is a property a repository can hold. One governs what an agent reports at the end of a task; the other governs what a maintainer reads on the 90-day cycle. There is no gate to add and no line of code to change. The run happened anyway. A rules commit this repository cannot gate is exactly the kind that gets tagged on a reading, and the half that catches a rule contradicting another one is the running application, not the diff.

GOTOOLCHAIN=go1.26.7 ./verify.sh exits 0 over 76 gates — the same count as v4.0.0, since no gate moved — and GOTOOLCHAIN=go1.26.7 make ci is green on this commit with go version go1.26.7 darwin/arm64 as its first line. The toolchain pin still stands in for this machine's Go 1.27.0, which the baseline does not adopt until 1.27.1.