docs: flow debugger script entry — component specs, CLAUDE.md, design pointers

Claude-Session: https://claude.ai/code/session_01NcMG6xXdsJbmD2wYAgkK29

docs/plans/2026-09-05-flow-debugger-design.md

@@ -23,7 +23,7 @@ on the `DelmiaReceiver` child → seven attribute writes → wait for Galaxy to
 | # | Decision | Rejected |
 |---|----------|----------|
 | D1 | **Two modes: Live and Replay.** Live is a real run with real values, real writes, audited like any inbound call. Replay executes nothing — it rebuilds the flow from an existing ExecutionId's trace rows. | *Dry run* (execute scripts but capture writes/ES/DB/Notify instead of sending). Needs an interception seam in the site runtime that does not exist and would fork the semantics of every helper. |
-| D2 | **Two entry points in v1:** an Inbound API method, and a value-change-triggered site script on a named instance. Both may land on a site script on instance X. | Alarm/timer trigger simulation, direct "call script X" — see §11. |
+| D2 | **Two entry points in v1:** an Inbound API method, and a value-change-triggered site script on a named instance. Both may land on a site script on instance X. | Alarm/timer trigger simulation, direct "call script X" — see §11. Superseded by `2026-09-08-flow-debugger-script-entry-design.md` (site → instance → script) as the page's second entry point. |
 | D3 | **Value-change on a data-sourced attribute does a REAL tag write** through the instance actor's normal write path; the device echo fires the trigger. Correlation is by a short-lived *trace arm* on the instance actor (§5.3). | A debug-only "inject value" command that synthesises the change without touching the device — leaves the instance's cached value diverged from the device until the next real update. |
 | D4 | **Live gets its trace inline; Replay reads audit rows.** Site audit telemetry forwards on a 5 s busy / 30 s idle cadence (`AuditLog:SiteTelemetry`), too slow to drive an interactive run, so the routed reply carries the site steps back and the same steps are *also* written as audit rows for Replay. | Live waiting on the audit pipeline. |
 | D5 | **Tracing is gated, not always-on.** Sites run scripts at high rates from timers and value changes; a trace flag rides beside `ParentExecutionId` and only flagged runs emit trace rows. One exception is always-on: a central `RouteCall` row per `Route.To().Call` (inbound-driven volume, joins the two halves of a Replay). | Tracing every run (volume), or a purely time-window join. |
@@ -55,6 +55,8 @@ Reference the mockup's two full-fidelity boards; this section only records what
 
 **Toolbar.** Entry point (`Inbound API method` | `Value-change trigger`) + a picker for the method or
 the instance + script; Mode (`Live` | `Replay`); `Edit inputs`, `Load from audit…`, `Run`.
+Superseded by `2026-09-08-flow-debugger-script-entry-design.md`: the second entry point is
+site → instance → script, not site → instance → attribute.
 
 **Status strip.** State chip (`Not run` / `Running` / `Completed` / `Failed` / `Timed out`), run
 number, wall-clock and node, total duration, counts (steps, boundaries crossed, attribute writes),
@@ -77,6 +79,9 @@ instance, composed child, connection, attribute kind, source line) with `Open in
 `ParameterDefinitions` (type, required) or, for a value-change entry, one field for the trigger
 attribute's new value plus read-only current value/quality. `Fill from last real call` pre-fills
 from the most recent `InboundRequest` row for that method.
+Superseded by `2026-09-08-flow-debugger-script-entry-design.md`: the script entry point's Inputs
+card is a `ParameterValueForm` from the script's own `ParameterDefinitions` for call kinds, and the
+single value field (attribute derived from the trigger, not picked) for write kinds.
 
 **Replay.** `Load from audit…` takes an ExecutionId (or arrives via a new `Open in Flow Debugger`
 action on the Audit Log drawer and the Execution Chain page). The graph is built from trace rows