Add TUI workflows for route inspection and recent logs

[yacosta738]

Summary

Support operational debugging by exposing the effective route chosen for a logical model and the most recent product events directly in the terminal surface.

Why this matters

This is one of the smallest independently shippable slices needed to make the parent issue real without mixing concerns or leaking product logic across layers.

Parent issue

#578 Operator TUI for health, routing inspection, and troubleshooting

Scope

• deliver the parent issue slice described in the title
• keep contracts reusable by the other Rook surfaces where applicable
• add or update targeted validation for the new behavior

Acceptance criteria

• the scope in this issue is implemented end to end
• behavior is covered by targeted tests or an explicit validation strategy
• the resulting contract is documented where operators or other developers need it

References

• tmp/2026-04-19-local-first-provider-gateway-prd-rfc.md §13.2-13.3, §17.1

[linear]

DALLAY-308

[yacosta738]

Reconciliation note: this issue appears functionally resolved by shipped work already merged, with one caveat preserved in archived verification.\n\nEvidence:\n- OpenSpec archive: \n- Archived verification report shows targeted route-inspection tests and clippy passing.\n- The archived report also preserved a warning that manual interactive verification of the TUI shell remained incomplete, so this slice should be treated as shipped with a documented partial/manual caveat rather than silently upgraded to stronger coverage.\n\nRecommended next step: close this issue as completed, while preserving that archived verification caveat in any parent/matrix tracking.