Background
Gap analysis vs the deployed ara-hub viewer (https://www.agenticresearch.sh/ara/AmberLJC/ara-paperbench/artifacts/speedrun/nanogpt-speedrun).
Problem
Replay stepping (crates/ara-viewer/src/replay.rs) is only reachable via the ‹ / › buttons. Arrow keys exist but are scoped to individual widgets: splitter (splitter.rs:418), tree (tree.rs:305), graph (scene.rs:415). There is no app-level keybinding, so keyboard users cannot step the trajectory without tabbing to the replay buttons.
The hub binds ← / → globally to previous/next step.
Proposal
Add a window-level keydown handler: ← / → step selection backward/forward in replay order when focus is not in a text input, select, or modal. Must not conflict with the splitter's arrow-key handling (splitter handles keys only when its separator has focus, which is fine).
Acceptance
Background
Gap analysis vs the deployed ara-hub viewer (https://www.agenticresearch.sh/ara/AmberLJC/ara-paperbench/artifacts/speedrun/nanogpt-speedrun).
Problem
Replay stepping (
crates/ara-viewer/src/replay.rs) is only reachable via the ‹ / › buttons. Arrow keys exist but are scoped to individual widgets: splitter (splitter.rs:418), tree (tree.rs:305), graph (scene.rs:415). There is no app-level keybinding, so keyboard users cannot step the trajectory without tabbing to the replay buttons.The hub binds
←/→globally to previous/next step.Proposal
Add a window-level keydown handler:
←/→step selection backward/forward in replay order when focus is not in a text input, select, or modal. Must not conflict with the splitter's arrow-key handling (splitter handles keys only when its separator has focus, which is fine).Acceptance
←/→step the selection globally