The feature flags list is keyboard-first: j/k move between rows, enter opens one #10372

Each flag row on the admin flags page (/settings/flags) now carries data-nav tabindex="-1", so j/k walk the rows the way they do on the pulls and apps lists. The empty page has none.

I ran test/keys-flags-list.test.ts, flags-settings, flags-timing, keys and help-keys, plus tsc --noEmit and bun scripts/design-lint.ts. All pass or are clean. In keys.test.ts, 10 tests were skipped because ssh-keygen isn't installed in the sandbox. I did not run scripts/gate.ts.

• What changed: one line, nav: true, in the row options in src/web/pages/flags.ts. No JavaScript was added.
• Enter: a flag has no page of its own, and the row is a <div> holding the edit form. Enter therefore opens the row's first link, the flag's owner issue (/<forge repo>/issues/N). That is the one primary link, and there is no nested data-nav. If the forge has no repo configured, the owner shows as plain text and enter does nothing on that row.
• Test: the new test seeds three flags and asserts one data-nav row per flag, each with its owner issue as the first link. It also asserts that the empty page has none. Without the nav: true line, the first test fails.
• Test deviation: the issue pointed at /flags, but the page is /settings/flags, so the test fetches that. Unlike the pulls-list test, which counts every data-nav on the page, it counts only data-nav on class="row" elements. The settings sidebar draws its own data-nav entries.
• Push: the first push was rejected until a commit message carried a Try: line, so the branch ends with an empty commit that has one: open /settings/flags as an admin and press j/k, then enter on a row.

To try it: open /settings/flags as an admin and press j/k to move between rows.

🤖 Generated with Claude Code

Closes #10358

The /settings/flags rows are now keyboard rows: j/k move between them and enter opens a flag's owner issue. The one-line change is nav: true on the flags rows in src/web/pages/flags.ts. test/keys-flags-list.test.ts covers it.

The check's two failures were not caused by this change:

• "each page stays inside its first-view budget": this test came in with #10331, which was on main but not on my branch. I merged main. The test still fails there, and it also fails on a bare origin/main checkout. The repository and app pages are over budget, at 197 words against 189 and 29 blocks against 28. The flags page is not named. Someone needs to either raise those budgets or trim those two pages.
• "a pin's cart > a captured cart plays sandboxed…": it passes when run alone, so I read it as a flake under shard load. I did not change it.

On the merged branch, bun scripts/gate.ts and bun x tsc --noEmit print nothing and test/build-cart.test.ts and test/keys-flags-list.test.ts pass. I did not run the full suite. I pushed the merge, so the check will run again. The budget test will probably fail it again until main is fixed.

To try it, open /settings/flags as an admin, press j/k, then enter on a row.

Flag rows on /settings/flags now join j/k traversal, and Enter on a row opens its owner issue.

The failing first-view budget test came from a stale base, not from this change. My branch was merged with an older main, where the repository and app pages went over their word and block budgets. I merged the current main into the branch. After that, test/attention.test.ts and test/keys-flags-list.test.ts pass, bun x tsc --noEmit is clean, and the push went through. I didn't run the full suite, and I didn't run scripts/gate.ts or scripts/design-lint.ts.

The only source change is nav: true on the flag rows in src/web/pages/flags.ts. test/keys-flags-list.test.ts covers the j/k and Enter behaviour. To try it, open /settings/flags as an admin, press j/k to move between rows, then Enter on a row.