docs(status): eighteenth-block coordination subsection and the nineteenth block

[Chris0Jeky]

Docs-only, one file: docs/STATUS.md.

• Eighteenth block, coordination-lane subsection (the heading space PR #2711 left): the #2707 record and the board moves applied from the alpha lane's packets in that range (#1940, #2682, #2214, #2636).
• Nineteenth block, written by the coordinator because the alpha product-trust session closed at about 21:50Z on the owner's request with three ready PRs open, which the coordinator carried to merge under the same gate: #2711 (the eighteenth block itself, docs review done by the lane, merged on CI green at 09299bd74), #2712 (#2599 items 1 and 2; round-1 SHIP, round 2 verified by diff as comments and the rail spec only), #2713 (#2591; the lane's SHIP review plus the coordinator's fresh-context review, one MEDIUM each fixed in-PR, local specs 151 of 151, CI green at 032fa4f68). Board state and what stays open on #2599, #2591 and #2708.

No maintainer decision is inferred; OUTSTANDING_TASKS.md is unchanged (nothing ticked, D-15 still open).

Verified: node scripts/check-docs-governance.mjs passed; git diff --check clean; merge SHAs from gh pr view; the #2712 round-2 scope from git diff e618311b9 80631e221 (no non-comment production line).
NOT verified: nothing executable changed; no screen-reader pass behind #2712.

Refs #2599, #2591, #2708

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, add credits to your account and enable them for code reviews in your settings.

[Chris0Jeky]

Review gate (Codex review credits exhausted, SC-9; documentation-only): one fresh-context read-only reviewer (Opus 5) on the first head. Verdict: SHIP; the two wording LOWs were applied in the follow-up commit.

Checked by reading (reviewer, against the merged code on main): landedQueueScope is written at two sites, both after the supersession guards on a successful read (explicit and poll, the poll behind isCurrentRead), and cleared only in recordQueueAccessRevoked; both skins' count gates read queueScopeLoaded instead of the loading term and its false default is what silences the first render; the inbox latch is { scopeKey, repairIssued }, the repair re-enters as a plain load with the flag raised, a second drop clears flag and latch, and the sole-Paper-side-caller caveat is present in the comment; PaperTriageTable hides rows and count under the raised flag and shows the loading branch while the store's loadingList is set; InboxView.spec's mock is Promise resolving true; the block layout matches the file's conventions; no em dashes in the added lines.

Findings and disposition:

• LOW, fixed: the announcement sentence could be read as "re-key and stay silent"; it now says the node stays mounted, an unchanged queue is silent and a moved queue is announced once.
• LOW, fixed: the focus clause names the Arrow-handler section with the cursor untouched and each skin's empty-state fallback.
• LOW, verified: 4ddb68c is [Frontend][A11y][Review] Queue live-region residuals: no repeat announcement on a same-scope reload, focus after the unavailable-pin return #2712's merge commit per gh pr view.

[Chris0Jeky]

CI note (coordinator, 2026-09-05): at head ca39c6d the only red is Frontend Unit (windows-latest) in run 33997974092, failing inside the 'Run source launcher regression suite' step (23:11:52Z to 23:18:02Z) before any frontend test ran; this PR changes docs/STATUS.md only. #2378 Windows launcher-suite class; one diagnostic rerun of the failed job follows once the run completes.