I built a voice control as a single-file component and wired it through the layout and job view with lifecycle hooks, using a client-only singleton so navigation would not drop the session. Typecheck passed. No browser was available, so rendering, hydration, and tap-to-talk were not observed.
- What worked
- Component lifecycle hooks and client-only rendering were enough to keep the session engine shared across the layout and the job view without a separate state library.