Repository navigation
Description
Part of #744, and the first work PR. Do this before the domain children (#747-#750).
Why this one first
The owner's words were "reads like a vague story dereferencing past PRs and issues." That shape is measurable, and it is the one cut that lets a reviewer check one rule instead of 3,903 individual judgments.
Scope
Blocks citing two or more distinct issue numbers: 108 blocks, 991 comment lines. Counted, not estimated.
The worst offenders:
| Lines | Location | Cites |
|---|---|---|
| 50 | src-tauri/src/platform/macos/dock.rs:1 |
#39 #148 |
| 41 | src-tauri/src/model.rs:4652 |
#144 #175 #230 #244 |
| 32 | crates/mcp-server/src/lib.rs:1 |
#470 #497 #501 |
| 28 | crates/core/src/director.rs:597 |
#588 #609 |
| 27 | src-tauri/src/harness.rs:1455 |
#243 #499 #514 |
| 26 | crates/core/src/engine/geometry.rs:262 |
#141 #176 #361 |
Find them with a script; do not hunt by hand. A block is any run of consecutive //-prefixed lines, and the rule is len(set(re.findall(r"#\d{2,4}", block))) >= 2.
The rule
Keep the one issue the current code's constraint came from. Delete the narrative of the others.
Inside those blocks only, also cut:
- Sentences describing a former state: "used to", "previously", "before #NNN", "was answered here", "this replaced".
git logholds it better. - Sentences reporting a measurement or investigation outcome rather than a constraint on the code — sample sizes, percentages, run counts.
src-tauri/src/model.rs:4652 is the exemplar: 41 lines of doc comment on an #[ignore]d benchmark narrating four issues' worth of findings. A decision log, verbatim, which docs/agents/comments.md:48 already forbids. Nine-tenths of it goes.
Exempt, do not touch
//!module docs are exempt from the length ceiling, butdock.rs:1andmcp-server/src/lib.rs:1are in scope for the multi-issue rule only — cut the issue narration, keep the orientation.ponytail:blocks.SAFETY:blocks.src-tauri/src/settings.rs,settings/form.rs, and the threeplatform/*/settings_window.rs— see Comments are 20% of the tree: compact them to a stated bar #744.- Do not strip a fenced-code tag.
model.rs:4662sits inside your exemplar block and is tagged```sh. Keep the fence and its tag intact while cutting the prose around it.
Verify
This is the PR that proves the safety property, so do it properly:
- The diff touches no code line. Prove it over
git diff -U0. cargo test --workspaceandcargo clippy --workspace --all-targets -- -D warningsgreen.node --test tests/*.test.jsbefore and after, with the pass list diffed, not just the exit code.harness.rsanddirector.rsare both read as raw text by meta-tests (tests/connect-buttons.test.js:24-27,tests/chat-composer-limit.test.js:12), and a comment edit can disarm one silently.- Add the
windowslabel, or that leg is lint-only and skips the tests. - Report the block count and line count removed.
Expected yield
About 2 points of ratio. Say the real number in the PR rather than rounding it up.
— Claude Code agent, on @omesser's behalf.
Metadata
Metadata
Assignees
Labels
Projects
- StatusShow more project fieldsDone
Activity
omesser commentedon Sep 16, 2026
Landed on main via #763
Merged PR #763 (
7f174f3) closes this ticket.What shipped
#106false positive from quotingjavascript:inplatform.rs; one real issue cite, left alone).git diff -U0: every touched line is//).cargo test --workspace,node --testpass-list (203 identical names), and clippy all green; Windows label ran the real test leg.Acceptance for this first #744 work PR is met. Domain children (#747–#750) and the census/hook work stay separate.
— Cursor agent (Coder), on @omesser's behalf.