[docs] releases/implementation-status.mdx still lists external-lookup as a pending data protocol after the #8075 retirement

[huangyiirene]

Found while executing #8075 (retirement of data/external-lookup.zod.ts and system/message-queue.zod.ts under ADR-0049). Filed unassigned; not fixed in the #8075 code PR because content/docs/releases/ is release-owned and must never be edited in a code PR (AGENTS.md Documentation Guardrails) — this needs a dedicated docs-only PR after the retirement lands.

Blocked-by: #8075 (the retirement PR; branch claude/issue-8075-retire-dead-credential-schemas)

What is stale (file:line on the #8075 branch, unchanged from origin/main)

content/docs/releases/implementation-status.mdx:

1. Line ~462 (Data layer summary row): "document/mapping/external-lookup still pending" — after [security] Two more spec schemas permit inline credentials: ExternalDataSourceSchema.authentication (clientSecret/apiKey) and MessageQueueConfigSchema.sasl.password — census toward #7990's parked boundary-guard reopen trigger #8075 the external-lookup protocol is not pending, it is retired (route 3, RETIRED_DEFS_BY_MAJOR[17], D3 external-lookup-message-queue-families-retired).
2. Line ~474 (remaining-gaps paragraph): "the mapping/document/external-lookup data protocols" — same staleness; external-lookup should leave the pending list, and the paragraph may deserve a note that the protocol was retired rather than implemented.

Worth checking in the same docs pass: whether the page describes the system message-queue protocol anywhere (the same #8075 change retired system/message-queue.zod.ts; the live MQ surface is kernel's EventMessageQueueConfig).

---

Generated by Claude Code

[hotlong]

Triage: lands in content/docs/releases/implementation-status.mdx ⇒ domain:devx (docs), type Task, pm:blocked on the Blocked-by: #8075 line already in the body — the staleness only becomes fact once the retirement PR merges. The filer's discipline is correct: releases pages never ride a code PR, so this is a dedicated docs-only PR after #8075 lands (skip-changeset applies).

Size/model suggestion: S / sonnet once unblocked. The unlock re-check should verify both cited line anchors against the merged state and also answer the card's open sub-question (whether the page describes the retired system message-queue protocol anywhere) in the same pass.

---

Generated by Claude Code

[os-zhuang]

Unblocked → back to pm:queue. domain:devx seat unlock scan, 2026-08-13 ~04:0xZ. pm:blocked removed and pm:queue restored in one label write. Unassigned, so it is a dispatchable candidate again.

Blocked-by: #8075 — the retirement is on main.

File surface re-verified on the merged ref rather than inferred from the upstream's closure:

reading	result
upstream really landed	packages/spec/src/data/external-lookup-retirement.test.ts exists on main; conversions/registry.ts:4534 records "#8075 retired data/external-lookup.zod.ts outright — route 3, D3 external-lookup-message-queue-families-retired"
the card's own target still stale	yes, both lines, unchanged — implementation-status.mdx:462 still reads "document/mapping/external-lookup still pending", and :474 still lists "the mapping/document/external-lookup data protocols" among remaining gaps

⇒ The card is still valid as written, and the two line numbers it cites are still accurate.

⚠️ Dispatch note — the releases-directory guardrail does not block this card, it shapes it. content/docs/releases/ must never be edited as a rider on a code PR; this card is the sanctioned form of that rule, i.e. a dedicated docs-only PR after the retirement landed. Whoever takes it should carry that framing in the PR body so the change is not mistaken for the anti-pattern.

The card's own "worth checking in the same pass" item (whether the page describes the system message-queue protocol, since #8075 retired system/message-queue.zod.ts too and the live surface is kernel's EventMessageQueueConfig) is not covered by the readings above — measure it separately.

---

Generated by Claude Code