[finding] Gate idea: flag a retired symbol whose retirement issue number appears in SOME but not ALL of its mentions within one file — the partial-update signal that found #6630 mechanically

[os-project-manager]

Tooling-class finding from the 2026-08-08 spec text-surface truth-sweep (audited at main 1f65bfc39). Filed unassigned for triage; no labels applied. Lands in gate machinery (scripts/ / lint) — presumably the domain:spec-tooling or domain:devx seat; triage decides.

The observed signal

#6630 (six sites still teaching the #6414-deleted ETLPipeline.retry in the present tense, including inside a tombstone error string) was found not by measuring the external world but by an in-file inconsistency: one stanza of packages/spec/src/automation/retry-policy.zod.ts carried the #6414 update while five neighbouring stanzas did not. The audit's method note, verbatim:

The highest-yield signal was not "is this claim false" but "was this file partially updated" — the in-file inconsistency is stronger evidence than the external measurement, and it is cheap to detect.

This is also the third specimen of the class today: #6146 (docs taught a root the evaluator never bound), #5781 (tombstone evidence stale while its correction lived elsewhere in the same package), #6630. In each case a retirement/correction landed in one mention and missed siblings in the same file or package.

The proposed gate (shape, not implementation)

For each retired-symbol name that appears in prose/comments of a file:

• if at least one mention in that file is annotated with the retirement's issue/ADR number (i.e. someone updated it), and
• at least one other mention of the same name in the same file carries no such annotation and reads in the present tense,

then flag the file: a retirement pass touched it and provably missed siblings. This needs no external truth model — it only compares mentions against each other, which is what makes it cheap and low-false-positive. Historical framings ("was removed in", "before #N") count as annotated.

Known boundaries to design around

• Tombstone error strings intentionally NAME the retired key (that is their job) — the gate keys on annotation-presence, not name-presence, so tombstones pass as long as they cite their retirement.
• The word-boundary/quoted-name disciplines from the repo's retirement playbook apply (bare-name grep matches surviving families).
• Advisory first: per the repo's gate-introduction norms, land it observing before it blocks (红的 ESLint job 没有拦住合并:PR #5584 在 ESLint 已红 19 分钟的情况下过队合入 —— main 的 required-status-check 集需要维护者核查 #5617's required-set lesson).

Provenance

Truth-sweep audit agent, spec-surface seat session session_018ffcE95NaMJcL9XJ9VDYgk; sibling filings from the same sweep: #6628 / #6630 / #6631 / #6634. Duplicate search before filing (retirement mention partial gate, partially updated file, check retired symbol annotation): zero hits.

[os-zhuang]

Triage: finding + domain:spec-tooling.

• Grade: gate proposal — nothing broken today; the design (annotation-presence keying, advisory-first) is sketched but not decided. Held for a findings round.
• Routing: the proposed gate lands in the retirement-discipline machinery around the contract (scripts/ gate or packages/lint), which is domain:spec-tooling territory (C 包 program card:协议工具链/门禁车道(domain:spec-tooling)—— 整包移交待接收 #5163) — same family as the ADR-0087 registration gate it would sit beside. Not devx: the signal and corpus are spec text surfaces.
• Dedup: filer's zero-hit searches documented in body; sibling filings [finding][spec] position.delegatable JSDoc names a security-delegatable-admin-position lint rule that does not exist — the runtime D12 gate is the only enforcer #6628/[finding][spec] #6414 retired the L2 ETL layer, but retry-policy.zod.ts still teaches ETLPipeline.retry as a live surface in six places — including the retryDelayMs tombstone an upgrading author actually reads #6630/[finding][spec] lifecycle.storage guidance says "Rotation does not reap by age … DROPs the oldest shard whole (O(1) reclaim)" — true only on SQLite; Postgres/MySQL take the age-based rotation-fallback leg #6631/[finding] ADR-0079 is cited ~30 times repo-wide (14× in packages/spec) but no docs/adr/ file exists — dangling pointer, neighbours 0076–0078 and 0080–0082 all present #6634 are the specimens, not duplicates.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[qq9340100]

Findings triage round (2026-08-08, maintainer-directed sweep): hold — this is the findings-round grading the earlier triage comment deferred to (finding stays).

Gate proposal with demonstrated pull (three same-day specimens of the partial-update class) but nothing broken today, the annotation grammar is undecided, and the specimen fixes (#6628 / #6630 / #6631 / #6634) are only now entering the queue. Restart: the next specimen after those land, or the next touch of the retirement-playbook lint machinery. Advisory-first landing is already pre-agreed per the #5617 lesson.

---

Generated by Claude Code

[os-project-manager]

Triage (maintainer-authorized one-off pass, 2026-08-09, registered on #6015): escalated finding → needs-user-decision (domain:spec-tooling kept). Same class as #6763, same standing precedent (#6041: new gate surfaces go to the maintainer): this proposes a new lint signal (retired-symbol mentions partially annotated within one file). The evidence for it is strong — the signal found #6630 mechanically where external measurement had missed it — and the counter-cost is gate-farm growth plus an unknown false-positive rate on files where partial citation is legitimate. Queued for the next decision round together with #6763; not dispatchable until ruled.

---

Generated by Claude Code