Recording / Local API

The recording capability is structured as a local stack rather than a single browser page.

Main layers

• Python Local API owns sessions, events, timelines, and assets
• the local bridge handles live mirror and control forwarding
• the web UI provides a lightweight inspection surface
• the recording runtime keeps the recording domain logic separate

Browser entry

Use munk serve and then open the site entry point exposed by the local API. The browser should consume bridge information returned by the API instead of hardcoding internal sidecar URLs.

Why this layering exists

This split keeps the system local-first and easier to reason about. It also avoids turning the recording web surface into the owner of state that belongs in the backend domain.