oficina / docs Public

Plan 7 drives a browser before it merges

The header fix this commit used to carry is gone: the word-processor
session landed the same correction on main as 1859534, and did it
better. Theirs names both symptoms and says explicitly that neither is
the diagnosis, which generalises the point mine made about the quoted
error being stale, and it narrows the open CI question to "may a gate
step run unsandboxed" rather than "can this run here". Taking theirs
whole rather than reconciling two paragraphs we agree about.

What is left is the consequence for this plan, which is not a comment
but a requirement.

Plan 7's UI is the exact shape a green gate cannot see: a disabled menu
item that must become enabled, a NodeView that shows a preview and then
swaps it for the real image, and an upload that can fail in front of a
person. 250db1c's merge went 44/44 to 39/44 on that drive with the gate
green throughout, including a real WCAG SC 1.4.10 failure at 320px. So
D3 and the risk table now require a browser drive before merge instead
of leaving it to judgement.

With the trap that comes with it. Enabling insert-link and insert-image
gives each command a second home, and menu items precede the toolbar in
document order — so a bare [data-docs-command="insert-link"] returns the
MENU item, which sits inside a closed <details> with a zero-size rect,
every click lands at the page corner, and the failure surfaces thirty
seconds later as "timed out waiting for the link". Drive selectors scope
to [docs-toolbar] or to the dialog's own root. clickSelector now refuses
a zero-size target and refuses to pick the first of several matches, but
only for code that goes through it.

Verified rather than asserted: the drive runs from here at 44/44,
exit 0, on 68273a4 plus this branch.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>