The review stated the finder had no e2e coverage and that
209-rundown-shortcuts.spec.ts never opened it. Both are wrong: a
"Find in rundown" smoke test opens the modal and closes it with
Escape. Describe the coverage that exists and what it leaves unguarded.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DzALEq9gGWwFmwTdgAiFcY
Reviews the existing rundown Finder and sets out a phased roadmap.
Findings:
- bare queries search title only; note and custom fields are never
searched, making custom field data unfindable
- selected index is never reset when results change, so a shrinking
result list can dereference undefined
- row clicks read selection from state rather than the clicked element,
so touch input navigates to the wrong entry
- no visible affordance anywhere, leaving the feature unreachable on
touch devices where no keyboard is available
- cuesheet already registers a scroll handler for finder jumps but the
Finder is never mounted there
Roadmap covers correctness, search depth, visibility and polish,
cuesheet reach, and a find-and-replace expansion. Records the
constraints that shape the work: cuesheet URL preset column permissions,
index memoisation on rundown revision, and the absence of any undo.
Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01DzALEq9gGWwFmwTdgAiFcY
Claude