AI Flow

@@ -359,3 +359,11 @@ Derive continuous heat cases from the actual voltage/current/power envelope and ### Repeated physical pads in explicit current boundaries  When multiple physical lands share one logical pin number, use the reviewed Fields physical-pad selector (`at: [x_mm, y_mm]`, adom/adom-fields PR10 and dependencies). Declare each branch current and its assumption; never silently divide the load to obtain a pass. AIFlow resolves and injects current at each declared physical pad, then matches each reported boundary once, including its coordinates. Missing, ambiguous, duplicate or changed selectors refuse; integer and decimal coordinate spellings are equivalent. Recheck coordinates after moving a footprint. Preserve owner review and shared runtimes; source support is not a deployed release or package-resistance model.++## One live dashboard per run++The main timeline uses the app-creator SSE channel: CLI workflow commands update durable run files and the server pushes state to the existing page. `timeline present --json '{"caption":"Current passed; thermal open","image":"review.png"}' --run <run> --ai-thread <name>` sends presentation changes through the server's HTTP control endpoint; it never changes engineering gates. Images must already exist in `<run>/timeline/`. Reconnect replays current state. Static exports and older servers retain polling fallback.++Do not reopen the webview to show progress. `timeline open` activates the existing named tab; a changed proxy URL navigates that tab. Repeated status/step/artifact calls reuse it. Keep one tab for this run. Tests must set `AIFLOW_DASHBOARD=off` unless Hydrogen is explicitly mocked; never let a temporary fixture open the user's workspace.++After a live-channel upgrade, restart only the verified server for this run, preserving the tab and its URL. Inspect `/health` for the active version and `liveChannel: sse`; an installed new binary does not update a running old server.