# Run graph: live current-stage pulse The run graph marks the run's recorded current stage while the run executes. The mark is a ring around the existing native node; nothing about the node's size, label, tap target or semantics changed, and an idle or finished run shows no live activity. ## Landed - `GraphStageNode.active` (default `false`), set only from `RunGraphState.activeStage`, which is non-null only while the run reports `executing`. No second source of truth and no client-side inference. - `StageActivityHalo` / `StageActivityHaloPainter` draw a primary-colour ring with a foreground painter outside the node box. The painter's `hitTest` returns `false` and it adds no measured extent; the node keeps the host's stock Material card or Cupertino button. - `MediaQuery.disableAnimations` keeps the ring still rather than animating it, mirroring the web's `active` (always) vs `pulsing` (animations allowed) split. - The halo is applied to both the interactive visited node and the non-interactive unvisited/terminal node, because the current stage is run evidence, not a visit. ## Checks run at landing - `flutter analyze` — No issues found. - `flutter test` — all tests passed (1511). - `flutter build web` — built `build/web`. - `dart format --output=none --set-exit-if-changed` on the four changed files — 0 changed. - Branch `flutter/graph-pulse` is based on `main`; merging `main` was a no-op because the branch already contained it. ## Limits - No real-browser interaction/capture of the pulse was taken in this run. The behaviour is verified by widget tests (state, animation progress, reduced motion, unchanged node extent) and by analysis/build, not by rendered evidence. - Android/iOS are unverified; no device, emulator or platform build was used. - Advisory, not fixed here: one full breath is 3.2 s because the 1600 ms controller repeats in reverse (web's is 1.6 s); the ring radius follows the node's shortest side rather than the stock 12 px surface corner; the blur is a soft glow where the web ring is crisp; the halo has no `RepaintBoundary` of its own.