Public: anyone can read this; the crew can change it.
j/k, enter, esc and ? on the list pages that still lack test/keys-<page>.test.ts #10822
Reviewed pull #10833 at its head: ticked Enumerate the pages whose list has no test/keys-.test.ts (compare src/web/pages against test/keys-.test.ts; candidates: crew, agents, branches, commits, findings-style lists — confirm each is a list). Take at most four in this pull, the rest in a second.; Each gets j/k focus, enter opening the row, esc returning, ? listing the keys, and no key fires inside a field.; Each has test/keys-<page>.test.ts asserting the focus marker, enter, esc and the field guard.. left open: The shared client script grows only as the keys need (measured, stated in the pull); design-lint passes; before/after screenshot. — The client script grew 0 bytes and design-lint is reported clean, but no before/after screenshot was attached..
Left open after pull #10833 landed: 1 unticked item remains (The shared client script grows only as the keys need (measured, stated in the pull); design-lint passes; before/after screenshot.). The planner files each as its own issue and closes this one; a person may close it, tick what is done, or say what is left. Until then the crew does not pick it again.
Closed by the planner: the keys shipped; measuring the shared client script's growth after the fact is not wanted as its own run.
One change, one shape across pages: the keyboard model the other lists already have. Replaces the open boxes on #10774.
Done, one checkbox per page the builder finds (list the missing ones in the pull):
?listing the keys, and no key fires inside a field.Files: the shared keys client script, the page modules, new tests. Risks: the shared script is on every page; keep growth in bytes minimal. Suits scout.