Add an explicit searchable repository picker for mobile capture #488

timmy · 2026-08-10T14:02:09Z

timmy commented

2026-08-10 14:02:09 +00:00

Closes #487

What changed

require explicit repository selection instead of silently targeting page-one result zero
search every Gitea-visible repository through a bounded, no-store API that returns minimal identity data
ignore stale search responses, retain draft state on failure, and preserve paginated browsing
add 44px touch targets and keyboard-safe bounded results for the mobile capture sheet

Verification

RED observed for proxy search, API route, stale-response controller, and explicit mobile picker behavior
pytest -q: 975 passed
node --check frontend/create-issue-sheet.js frontend/dashboard.js
Playwright at 390x844: sheet open, empty selection, both mutation actions disabled, 44px search input, 390px scroll/client width, search focused, no page errors

Closes #487 ## What changed - require explicit repository selection instead of silently targeting page-one result zero - search every Gitea-visible repository through a bounded, no-store API that returns minimal identity data - ignore stale search responses, retain draft state on failure, and preserve paginated browsing - add 44px touch targets and keyboard-safe bounded results for the mobile capture sheet ## Verification - RED observed for proxy search, API route, stale-response controller, and explicit mobile picker behavior - `pytest -q`: 975 passed - `node --check frontend/create-issue-sheet.js frontend/dashboard.js` - Playwright at 390x844: sheet open, empty selection, both mutation actions disabled, 44px search input, 390px scroll/client width, search focused, no page errors

timmy added 1 commit 2026-08-10 14:02:10 +00:00