[lukemaj]

What: Add 16 backlog PR references to seven tracked parts in docs/map.md.
Why: Tonight's backlog merges deferred map edits to avoid conflicts, leaving their tracked parts without implementation references.
So what: Luna review and CI, then the backlog coordinator merges

Only docs/map.md changes. Existing primary refs, parts and formatting are preserved. This is the authorized documentation microfix, with no additional Issue or version bump.

Changed ref lines:

• %% PBI: #460 PR #470
• %% PZ: #92 PR #408 PR #430 PR #479 PR #489 PR #512 PR #471 PR #476
• %% BL: #289 PR #335 PR #467 PR #469 PR #480
• %% SN: #269 #341 #422 PR #431 PR #492 PR #488
• %% ST: #285 #298 PR #478 PR #495 PR #496 PR #493
• %% NR: #292 #358 PR #498 PR #497
• %% PRN: #323 #336 PR #477 PR #504 PR #473

Matching evidence:

• PBI: fix(desktop): pair WhatsApp main-frame browser identity #470 refs Preview browser: look like a regular Chrome browser (WhatsApp Web blocks the Electron user agent) #460, already listed on this part.
• PZ: test(prism): exercise existing successor ID rejection #471 closes test(prism): exercise existing successor ID in recovery admission case #432 and fix(prism): reconciling an old source no longer closes a newer run's retry #476 closes fix(prism): reconciling an old recovery source can close a newer running run's controller #436; both fix Prism retry/successor handling.
• BL: fix(scheduler): preserve bare read grants through task decorator #467 closes fix(scheduler): preserve bare read grants through task decorator #434 (bare grants), test(server): canonicalize bare-worktree fixture path #469 closes test(server): canonicalize the bare-worktree temporary path on macOS #390 (bare-worktree fixture), and fix(bare): recover after a run stops before provider start #480 closes fix(bare): recover after a run stops before provider start #343 (bare launch recovery).
• SN: fix(server): a follow-up wakes the parent after a Stop caught its task running #492 closes Delegated follow-up stays silent after a stop that caught its task running #214 (follow-up completion wakes the parent) and perf(orchestration): stop and resume wake only that thread's subtree #488 closes perf(orchestration): Stop and resume wake only that thread's subtree, not every child thread #450 (child-request reconciliation on Stop/resume).
• ST: fix(codex): late child interrupt no longer blocks the native reader #495 closes fix(codex): late-child cancellation waits on its serial reader #331, fix(codex): Stop reaches native work after a natural root end #496 closes fix(codex): Stop loses native work after a natural root end #332, and fix(server): background work survives same-run steering restarts #493 closes Verify surviving background ownership across same-run steering restarts #299, all interruption/cancellation/steering follow-ups identified by tracked Restore explicit urgent interruption after Claude steer queuing #285.
• NR: fix(connect): refresh shared discovery after account deregistration #498 closes fix(connect): refresh shared discovery after account deregistration #363 and fix(connections): offer only managed T3 Connect routes #497 closes fix(connections): exclude publish-only links from Add T3 Connect #361, both explicit follow-ups to tracked Every client uses LAN, then Tailscale, then T3 Connect to every server #292's route discovery.
• PRN: fix(auth): make verified renewal approval retries idempotent #477 closes listed fix(auth): make verified renewal approval retries idempotent #336; fix(web): retry transient cookie renewal during startup #504 closes fix(web): retry transient cookie renewal during startup #330 and fix(auth): pace renewal when the client clock is ahead #473 closes fix(auth): pace renewal when client time is ahead of the server #337, both session-renewal retry fixes.

Skipped PRs:

• fix(tooling): declare OS compiler in Knip configuration #462, closes Server Knip reports the OS cc compiler as an unlisted binary #270: Knip compiler configuration; no tracked tooling part or Issue ref.
• test(acp): remove default-PATH system Node assumption #465, closes test(acp): remove the cgroup wrapper test assumption of system Node #348: ACP test PATH assumptions; no tracked ACP runtime part or Issue ref.
• fix(issues): resolve cold project identities for issue links #481, closes Issue links drop project-derived links while the project identity cache is cold #241: cold project identities for Issue links; no matching tracked part or Issue ref.
• fix(grok): recognize custom native homes through filesystem aliases #472, closes fix(grok): recognize custom native homes reached through filesystem aliases #403: Grok native-home filesystem aliases; no matching tracked part or Issue ref. Provider updates does not track native-home discovery.
• fix(server): publish ACP replay status before responses #468, closes ACP replay tests flake: status file read while the replay agent rewrites it #244: ACP replay status publication; no matching tracked part or Issue ref.
• fix(dev): stop inheriting host Tailscale Serve activation #466, closes Plain dev servers inherit host Tailscale Serve configuration #287: dev-runner Tailscale isolation; no tracked development tooling part or Issue ref. Network routes tracks application connections.
• fix(web): watch descendant-linked PRs from the parent panel #474, closes fix(web): watch descendant-linked PRs from the parent panel #314: descendant PR watching in the parent panel; no matching tracked part or Issue ref.
• fix(auth): CLI session revocation closes open sockets in the running server #490, closes fix(auth): CLI revocation must invalidate sockets in the running server #325: CLI socket revocation; no matching tracked part or Issue ref. Paired session renewal does not track revocation, which fix(auth): CLI revocation must invalidate sockets in the running server #325 explicitly excludes from renewal work.
• fix(delegation): use destination commit for cross-project isolation #475, closes fix(delegation): cross-project isolation uses parent repository commit #429: already cited on DR.
• fix(server): replay accepted sends during replacement startup #478, closes Accepted MCP restart retries can fail during replacement startup #298: already cited on ST.

Proof:

• Base: 5f6b55e7d5569878f6b209f2134640cca1dfd8c2 on origin/main when checked; head: d1a8c17f6905b8e275e7c3f684dd71ba4fcdadcc.
• npx pnpm@11.10.0 exec vp test run apps/server/src/issues/featureMap.test.ts: 1 file passed, 22 tests passed, including the real map's zero unreadable refs assertion.
• git diff --check: passed. Self-review confirms only seven ref lines changed, using space-separated PR refs.
• Independent Luna review and CI remain pending. No merge or deployment performed. Website impact: none, only feature-map metadata changes.

Elon record:

Requirements and who asked: The user requested backlog PR citations on matching tracked parts, with no other edits and no new Issue.
Deleted: No new parts, Issue refs, prose changes, duplicate PR refs, context refs or version changes.
Bottleneck: Missing implementation citations after conflict-avoiding backlog merges.
Checked myself: Read the map and merged PR titles/closing Issues, inspected ambiguous follow-up Issues, reviewed the complete diff, and ran all 22 feature-map tests successfully.

Model: GPT-6.1 Sol (medium reasoning effort). Harness: Codex in T3 Code.

[lukemaj]

Luna review round 1 at d1a8c17: APPROVE

All 16 added PR refs are on their matching tracked parts: browser identity (#470), Prism (#471, #476), bare launch/receipts (#467, #469, #480), child notices (#492, #488), urgent interruption (#495, #496, #493), network routes (#498, #497), and paired session renewal (#477, #504, #473). The PR diff changes only those seven ref lines, and each ref follows the parser's space-separated format without commas.

The skipped Issue numbers have no matching part on the map; #429 and #298 are the exceptions already represented with PR #475 and PR #478 respectively. No actionable findings.