docs(adr): renumber the ADR-018 identity stub to ADR-030

[lilyshen0722]

main has carried two files named ADR-018 since 2026-08-11:

• ADR-018-agent-identity.md — Proposed stub, merged 08-04 via docs(ADR-018): agent identity #790
• ADR-018-agent-attention-claims.md — Accepted 08-17, merged 08-11 via docs(ADR-018): agent attention claims — claim, lease, turn-taking (Proposed) #889

Disjoint filenames share no text to conflict on, and docs/adr/ has no index, so nothing went red and nothing could. This is the same class as the ADR-025 pair now arriving on #1295, and #1142 / #1424.

Which file moves is determined, not chosen

The stub declares zero D<n> tokens — its headings are "Why this is open" / "The shape of the decision" / "Open questions" / "Deliberately not decided here" / "Not yet decided". Verified at f1e7a92c:

$ git show origin/main:docs/adr/ADR-018-agent-identity.md | grep -coE '\bD[0-9]+\b'
0

So every ADR-018 D<n> citation in the repo — including the four in agentMentionService.ts and the three in CLAUDE.md — can only mean attention-claims. Renaming the stub breaks none of them and disambiguates the rest. Renaming attention-claims instead would break all of them.

Scope

Exactly one reference names the stub by filename anywhere on main — ADR-028's evidence bullet, which cites the duplicate as a missing-record finding. It is updated in place: the finding stands (nothing detected the collision for 22 days, and a third instance arrived before it was resolved), and the tense is corrected.

030 is free against both populations — main carries 001–028, open PRs claim 017/020/024/025. 029 is deliberately left for the Connections ADR.

Why now

@sprint-review has a duplicate-number guard written (globs docs/adr/, groups by number, fails naming both files) and is holding it because it goes red on main today for exactly this pair. That is the whole blocker, and it is a one-file rename rather than a governance call. This is the cheapest form of the question — press it or close it.

Docs-only. After the rename, ls docs/adr/ | grep -oE '^ADR-[0-9]+' | sort | uniq -d returns empty.

🤖 Generated with Claude Code

[lilyshen0722]

Gated at head 4dbdf5f487de32f3e465d04c7fb9c8d45fa8b770, base main = f1e7a92ca. PASS.

All three claims in the PR description re-derived independently:

1. Stub carries zero D<n> tokens — confirmed, grep -cE '\bD[0-9]+\b' over ADR-018-agent-identity.md at main returns 0. So every ADR-018 D<n> citation in the repo already resolved to attention-claims and the rename moves none of them.
2. Exactly one filename reference — confirmed, git grep -l ADR-018-agent-identity at main returns only ADR-028-work-claims-and-decision-ledger.md, updated in place here.
3. uniq -d empty after — confirmed: main has 18 duplicated, the PR head has none.

Two checks beyond the description, both clean:

• Bare prose ADR-018 citations (19 sites: tests, models/Task.ts, config/native-agents/, reactionController.ts, CLAUDE.md). Every one carries attention-claims semantics — claims, leases, D3/D4/D7/D8, kernel CAS. None means identity. The rename is safe for all of them.
• Target number free across open PRs. 030 is unclaimed on main and by every open PR that touches docs/adr/. Worth checking explicitly because this exact collision class is live: #1295 adds a second ADR-025 without deleting ADR-025-connector-substrate.md.

The internal header, status line and the renumber note in the moved file are all consistent with the new number.

One note, not a blocker: this clears 018, but the numbering guard isn't in this PR, so nothing catches 025 when #1295 merges. The guard would go red on that merge — which is the desired behaviour, and an argument for wiring it before #1295 rather than after.