Fix the comment shape in the files every new repo copies first

[ptr727]

The .editorconfig / .gitattributes / .gitignore entry from TODO.md, taken now because Blog is carrying the baseline this week and these are the first files it copies.

TODO.md states the reason itself: until they are fixed, a new repo learns the shape the rules forbid.

Result

36 findings gone..gitignore was already clean, so the 44 that TODO.md claimed was stale, most likely because #500 removed several .editorconfig findings on the way past.

File	Before	After	Fidelity
.editorconfig	22	0	intent
.gitattributes	14	0	intent
.gitignore	0	0	repo-owned

Both swept files are intent fidelity, so a downstream copy is adapted rather than byte-matched. Unlike #501 this obliges no re-vendor.

A recommendation I am reversing

In #501 I said a command-synopsis exemption in prose_lint.py was probably the better long-term answer than labeling each block. Having done this sweep, I no longer think so, and this PR labels instead.

Two bare commands appear here:

# git config --global core.autocrlf false
# git ls-files --eol

The difference from the bare-URI case in #500 is that relabeling a command is easy and improves it, where relabeling a URI is impossible without corrupting the address:

# Configure with: git config --global core.autocrlf false
# Inspect with: git ls-files --eol

The URI needed an exemption because there was no legal fix. A command has one, and it reads better. On top of that, "a comment body that is a command invocation" has no crisp form the way ^scheme://...$ does, and a fuzzy exemption inside a gate silently swallows real prose. So the rule stays as it is.

What was corrected, by shape

• Wrapped prose rewritten one sentence per line, which is the bulk of the 36.
• Comments opening on git or uv restructured rather than capitalized, per GOVERNANCE's tooling-casing rule. For example # uv regenerates uv.lock ... became # The uv tool regenerates uv.lock ....
• Bare commands labeled, as above.

Fixed in passing, since these files were open

A mid-sentence semicolon in .gitattributes and several spaced hyphens in both files. GOVERNANCE bans both in agent-authored prose, and neither was reported here because the semicolon and dash rules are still markdown-only. Leaving them would have carried the banned construction into every repo copying these files.

No setting or pattern changed

The whole point is that this is comment-only, so it is evidenced rather than asserted:

• Every non-comment line in both files is byte-identical, checked by diffing the files with comment lines stripped.
• repo_gate's eol check still passes. That check cross-validates the two files against each other, asserting every path pinned LF in .gitattributes has the matching .editorconfig override, so it would catch a mangled pattern or section header.

Verification

prose_lint .editorconfig .gitattributes --check comment-wrap --check comment-case clean
prose_lint . --check charset --check dupword --check spelling clean
prose_lint . --diff HEAD clean, all default rules
python3 scripts/repo_gate.py eol 0, sha-pin 0
python3 scripts/test_prose_lint.py 141 tests, OK
python3 spec/validate.py OK, 21 cataloged

Tree-wide warn-only backlog moves 1152 -> 1116.

TODO.md

Drops the two swept entries, and adds the fleet re-vendor of configure.sh that #501 obliges, which was previously recorded only in the PR body. The README.md entry is reworded: it was deferred because two edits to that file were in flight, and both have since landed, so it is now free to take.

🤖 Generated with Claude Code

[Copilot]

Pull request overview

This PR cleans up comment prose/shape in the “first-copied” repo bootstrap files so new repos don’t inherit comment-wrap / comment-case lint findings, and updates the repo TODO list to reflect completed work and the follow-up re-vendor obligation.

Changes:

• Rewrite .editorconfig and .gitattributes comments to a one-sentence-per-line shape and restructure comments that previously started with bare tool invocations.
• Label previously bare command comments (e.g., git config ...) so they read as prose without violating tooling-casing guidance.
• Update TODO.md to drop the completed sweep items and add a fleet re-vendor task for the verbatim repo-config/configure.sh change from #501.

Reviewed changes

Copilot reviewed 3 out of 3 changed files in this pull request and generated 1 comment.

File	Description
.editorconfig	Comment-shape and wording cleanup to eliminate prose-lint findings without changing settings.
.gitattributes	Comment-shape and wording cleanup for EOL pin rationale without changing patterns.
TODO.md	Removes completed sweep entries and records the configure.sh fleet re-vendor follow-up.

Suppressed comments (2)

.editorconfig:67

• The phrase "..., being the PreToolUse hook and its installer" is ungrammatical; "namely" (or similar) reads more clearly.

# The agent-safety kit's Python is shebang-executable tooling run by path, being the PreToolUse hook and its installer.

.editorconfig:78

• "reds on every" is slang and may be unclear to readers; consider using a more explicit verb like "fails".

# Without the pin an EOL check (editorconfig-checker or CI) reds on every `uv lock` or `uv sync` until the file is manually reconverted.

[Copilot]

Pull request overview

Copilot reviewed 4 out of 4 changed files in this pull request and generated no new comments.