[finding] plugin-auth comments still point at last-admin-ban-guard.ts — a filename that has not existed since the guard was renamed to last-admin-guard.ts #16477

Found while verifying the code anchors for the ADR-0132 mirror of cloud ADR-0024 (branch claude/issue-14506-adr-mirror-identity-access). ⛔ Not fixed there — that PR touches docs/adr/** only.

The finding

The break-glass last-administrator guard was renamed. packages/plugins/plugin-auth/CHANGELOG.md records the rename in its own words — the entry reads that the registration function is registerLastAdminGuard and was previously last-admin-ban-guard.ts. On origin/main (5a9138703) the files present are:

packages/plugins/plugin-auth/src/last-admin-guard.ts
packages/plugins/plugin-auth/src/last-admin-guard.test.ts
packages/plugins/plugin-auth/src/last-admin-guard.config-anchor.test.ts
packages/plugins/plugin-auth/src/last-admin-guard.re-pricing.test.ts
packages/plugins/plugin-auth/src/last-admin-standing-keys.test.ts

There is no last-admin-ban-guard.ts and no last-admin-ban-guard.test.ts. Five comments still send a reader to one of them:

git grep -n "last-admin-ban-guard" -- packages/plugins/plugin-auth/src

• packages/plugins/plugin-auth/src/invitation-role-cap.ts — the docblock on isOrgAdminGrade names its second consumer as "the break-glass ban guard (last-admin-ban-guard.ts, cloud ADR-0024 D5.2)"
• packages/plugins/plugin-auth/src/objectql-adapter.ts — "last-administrator ban guard (ADR-0024 D5.2, last-admin-ban-guard.ts)"
• packages/plugins/plugin-auth/src/break-glass-local-credential.test.ts — two sites
• packages/plugins/plugin-auth/src/objectql-adapter.test.ts — points at last-admin-ban-guard.test.ts for "the 403 arm is pinned in ..."; that file does not exist either, so the pin it names cannot be found by its name

(The CHANGELOG hits are historical entries and are correct as dated records — ⛔ they are not part of this finding.)

Why it is worth a card rather than a shrug

These are exactly the pointers AGENTS.md Prime Directive #13 tells the next author to follow ("grep the ADRs for the surface you are touching", "leave the ADR's id in the code"). A pointer to a file that does not exist costs the reader a search and then a guess, and the last of the five is the worst shape: it names a test file as the place an invariant is pinned, so an author checking whether the 403 arm is covered finds nothing under that name and may conclude it is not.

It is also the same failure class scripts/symbol-anchors.mjs was built to end for docs/adr/** — a citation that silently stops resolving — except that these live in source comments, which no corpus gate covers today.

Suggested fix

Mechanical: rewrite the four source/test comments to last-admin-guard.ts, and the objectql-adapter.test.ts one to whichever of last-admin-guard.test.ts / last-admin-guard.re-pricing.test.ts actually holds the 403 arm — read the test before repointing it, because "the name moved" and "the assertion moved" are different questions and only the second one decides the target.

No behaviour change; a skip-changeset candidate on the same rule the ADR PRs use (publishes nothing), though a comment-only diff inside a published package should be judged against docs/ policy rather than assumed.

Measurements

• Tree: origin/main @ 5a9138703 (non-shallow checkout; git rev-parse --is-shallow-repository = false).
• Dedup before filing: one targeted search_issues in this session returned five related cards ([finding] plugin-auth SCIM lifecycle after #14360: DELETE of the last administrator is unpinned, last-admin-guard.ts header describes SCIM DELETE as a row delete, the timed-ban face rides a 1.5 s real-clock window #14555, [finding] last-admin-guard.ts's sys_member.valid_from exclusion note says the role projection is not window-filtered — true until #10982, stale after it #11089, 最后一个管理员的「删除」路径无守卫:目标不持本地密码时,SCIM/admin remove 可删掉环境最后一个管理员 #5941, break-glass 不变量的第四条路径无守卫:删/改名 admin_full_access 那条 sys_permission_set 行,一次废掉所有 platform admin #6084, break-glass 不变量的第三条路径无守卫:撤掉最后一个管理员的「身份」(sys_member 降级 / 删 admin_full_access 授权)同样锁死环境 #5978) — all closed, and none of them is about the stale filename; the non-empty result is itself the proof that search answered in this session.