…coverage

The PR's SessionsPageTests referenced a non-existent SessionsViewModel.ResumeSessionId
(resume state lives on ChatNavigationState), which broke the build on every Test-* job.
Rewrite it to observe the shared ChatNavigationState, register a stub /chat landing
route so the Enter/N resume paths don't throw 'No route matches', use the real
SessionId (strips the 'session-' prefix), and enqueue Ctrl+Q in the render-only cases
so they stop burning the 10s cancellation timeout.

The corrected tests pass against current dev: arrow keys reach the ViewModel,
SelectedIndex tracks, and Enter resumes the highlighted session — the two-way
selection binding netclaw-dev#1363 preserved is intact, so the described regression does not
reproduce in dev.

Add IdentityRedoPageTests: first page-level coverage of the identity-redo flow through
Termina's real render + input pipeline, asserting the timezone submit reaches the saved
screen (the user-visible symptom of the redo loop).

The session list is rendered as a focusable SelectionListNode (FocusPriority 10,
added by netclaw-dev#1363). On a populated list, ReactivePage.ApplyFocusPolicy hands it
keyboard focus, and Termina's input dispatch routes keys to the focus manager
(SelectionListNode.HandleInput consumes UpArrow/DownArrow/Enter/Escape, returning
true) BEFORE they ever reach the ViewModel. SessionsPage had no HandlePageInput
override and relied on a ViewModel.Input subscription, so on a real terminal the
focused list swallowed every navigation/selection key: the highlight could not be
driven, SelectedIndex stayed 0, and Enter resumed nothing — 'you can't select
anything in netclaw sessions'.

Fix: claim the keys in SessionsPage.HandlePageInput (dispatched before the focus
manager) and forward them to a new public SessionsViewModel.HandleKey. The list
stays a pure renderer driven one-way by .WithHighlightedIndex(SelectedIndex). This
matches what HandlePageInput is documented for ('page-level input before focused
components') and the established pattern in the other list pages.

Why no test caught it: the empty-state tape (sessions-tui) renders a TextNode, not
a focusable list, so it never hit the path; and the headless xUnit harness does not
hand the list focus during input processing, so keys fell through to the ViewModel
and the prior tests were false positives. They now drive the real HandlePageInput
path — removing the override fails them — but faithful focus-eating coverage still
needs native/manual validation.

…er regression test (#1518)

* fix(tui): prevent identity redo loop on timezone submit

The IdentityStepView is a singleton on IdentityRedoViewModel. Each layout
rebuild creates new TextInputNode instances with new subscriptions added
to _stepSubs, but old subscriptions were never cleared. After the user
submitted the timezone field, stale callbacks from the previous render
would re-fire and re-trigger GoNext(), creating an infinite loop back
to the timezone input screen.

Clear _stepSubs inside the DynamicLayoutNode callback before creating
new subscriptions to prevent this accumulation.

* test(tui): correct sessions regression test + add identity-redo page coverage

The PR's SessionsPageTests referenced a non-existent SessionsViewModel.ResumeSessionId
(resume state lives on ChatNavigationState), which broke the build on every Test-* job.
Rewrite it to observe the shared ChatNavigationState, register a stub /chat landing
route so the Enter/N resume paths don't throw 'No route matches', use the real
SessionId (strips the 'session-' prefix), and enqueue Ctrl+Q in the render-only cases
so they stop burning the 10s cancellation timeout.

The corrected tests pass against current dev: arrow keys reach the ViewModel,
SelectedIndex tracks, and Enter resumes the highlighted session — the two-way
selection binding #1363 preserved is intact, so the described regression does not
reproduce in dev.

Add IdentityRedoPageTests: first page-level coverage of the identity-redo flow through
Termina's real render + input pipeline, asserting the timezone submit reaches the saved
screen (the user-visible symptom of the redo loop).

* test(smoke): add native redo-identity flow tape

Adds init-redo-identity.tape (+ sibling assertion) to the light smoke set: the
existing-install menu had a redo path with no native coverage. The tape walks
the menu -> 'Redo identity setup' -> all four identity sub-steps to the saved
screen, and the assertion proves the redo wrote SOUL.md/TOOLING.md without
clobbering netclaw.json (redo never calls WriteConfig).

This is forward-progress coverage: a regression that blocks advancing past any
redo sub-step (the symptom of the timezone loop) hangs the Wait+Screen anchor
and fails the tape. It deliberately does NOT claim to reproduce the original
loop, whose trigger is a non-step-transition re-render (cursor-blink/resize)
that deterministic VHS input does not generate — verified by reverting the fix
and watching the tape still pass.

Runs sequentially within the already-parallel smoke-linux/smoke-macos jobs;
~40s added on the critical path (~3-4% of the ~20m smoke job).