/roster action-button statefulness — disable Turn-out-lights / Water-the-garden per environment

MERGED to master on MAIN by orchestrator daemon 10 (proc 996). Worker 1001 (flower-91-worker, flower-wt2) built commit b4c2cee; merged --no-ff as 9ad3d95. Items [3][8][8b] shipped: per-project + platform button disable-states off derived_liveness; new CloseAllDaemons service reusing CloseDaemon; native wire:confirm (FluxUI is NOT installed — see #105) enumerating non-flower daemons before global shutdown. Scoped cleanly to index.blade.php + Roster/Index.php + CloseAllDaemons.php + 2 tests (daemon-row untouched, so parallel with #94). Verified on MAIN: RosterActionButtonStates + CloseAllDaemons + DaemonRosterTools = 29 pass, pint clean, /roster 200. Worker mocked SoloClient (never ran real shutdown). NOTE: worker caught a regression I introduced — DaemonRosterToolsTest hardcoded context_threshold_tokens===400000, which my 8fc1393 (400k→600k) broke; fixed it env-robustly (assert >0, not the default) in a83cea2. Worker 1001 closed.

Built items [3], [8], [8b] on branch flower/91-buttons — commit b4c2cee37f41564d365e64b338ed3d10df60b37b (base a4e3790 master). WHAT - [3] Per-project card: "Turn out the lights" now disabled when the project has no active (non-dead) daemons; "Water the garden" disabled when every expected role (config default_roles = orchestrator+refine) is already live/spawning. Computed in Index::render() as a `projectActionStates` map keyed by project id, driven off the `derived_liveness` already on each row (reactive to the daemon-checkin broadcast re-pull). - [8] Platform card: "And there was light" disabled when all expected platform roles (orchestrator/ops/refine) are up (`platformAllRunning`). - [8b] New flower-side GLOBAL "Turn out the lights" on the platform card. New service App\Services\Daemons\CloseAllDaemons shuts down EVERY daemon across all projects by REUSING the per-daemon CloseDaemon teardown — it force-marks each live daemon winddown_ready (via DaemonRosterService::markWinddownReady) to clear CloseDaemon's readiness guard, then calls CloseDaemon::close (no duplicated Solo stop logic). Already-dead daemons are skipped/counted. The confirm enumerates the non-flower daemons that will ALSO be closed and fires only when such daemons are live; cancel is a no-op. Button disables when nothing is active anywhere. CONFIRM MECHANISM: codebase has NO FluxUI installed (checked composer.json + vendor); the established confirm pattern is Livewire's native `wire:confirm` (used by daemon-row remove + briefs dispatch). Used `wire:confirm` with the enumeration message built server-side in render() and conditionally rendered only when non-flower daemons are live. This satisfies the spec's "FluxUI confirm … lists what else … cancel is a no-op" behaviorally. SCOPE HONORED: touched ONLY app/Livewire/Roster/Index.php, resources/views/livewire/roster/index.blade.php, new app/Services/Daemons/CloseAllDaemons.php (+ 2 tests). Did NOT touch daemon-row.blade.php (parallel sibling). Did NOT restyle the flower card (visuals left to #93) — new button reuses the existing header button's neutral classes. TESTS: 14 new tests (tests/Feature/Daemons/CloseAllDaemonsTest.php + tests/Feature/Roster/RosterActionButtonStatesTest.php) all green; SoloClient mocked — never invoked the real global shutdown. Ran ./vendor/bin/pint on all changed files (clean). Full `php artisan test`: 658 pre-existing pass + my 14. ONE PRE-EXISTING FAILURE (NOT mine, NOT fixed): tests/Feature/Mcp/DaemonRosterToolsTest::test_checkin_marks_reset_pending... asserts config('flower.reset.context_threshold_tokens') === 400000, but config/flower.php:304 defaults it to 600000 (verified identical on master). Stale-test-vs-config mismatch, unrelated to #91 and outside my scope (didn't touch config or that test). Flagging for the orchestrator. Did NOT merge/push; left Horizon/daemons alone.

## Scope (child of #87, Group B, items 3 + 8) Make the /roster daemon-control buttons environment-aware, and add a flower-side global shutdown (operator confirmed the global action 2026-07-03). ## Items - **[3] Per-project card button disable-states:** - "Turn out the lights" (retire/winddown) → **disabled when the project has no active daemons**. - "Water the garden" (ensure daemons) → **disabled when the project already has all expected daemons running**. - Drive off the roster/liveness data already on the card (expected vs. live daemon counts). - **[8] flower PLATFORM card:** - "And there was light" → **disabled when all flower daemons are already up**. - **[8b] Global "Turn out the lights" — CONFIRMED BUILD (operator answered "Yes — add the global shutdown with FluxUI confirm"):** add a flower-side action that shuts down **everything** (all daemons across all projects). If clicked while non-flower (project) daemons are still live, show a **FluxUI confirm** that lists what else will be shut down ("this will ALSO shut down N project daemons: …") before proceeding. Reuse the existing shutdown/CloseDaemon path per daemon; don't duplicate teardown logic. ## Acceptance - Buttons reflect live state (disabled exactly under the stated conditions), reactive to roster broadcast updates. - Global shutdown closes all daemons; confirm dialog fires only when non-flower daemons are live and enumerates them; cancel is a no-op. - `php artisan test` green; `./vendor/bin/pint`; verify in the real app (roster with/without daemons up). ## Constraints - bloom + FluxUI; Livewire 4. Commit trailer `Brief: #91`. Coordinate visual styling of the flower card with sibling #93 (don't fight over the same blade regions — #91 owns button state/logic, #93 owns card styling).

Child of #87 (Group B, items 3 + 8). ## Items - **[3]** Per-project card: "Turn out the lights" disabled when the project has **no active daemons**; "Water the garden" disabled when the project **already has all expected daemons running**. Drive off the roster/liveness data already on the card. - **[8]** flower PLATFORM card: "And there was light" disabled when all flower daemons are up. (Related styling of the flower card itself is Group D / a sibling child.) - **[8b] OPEN QUESTION (see brief question):** whether to add a flower-side "Turn out the lights" that shuts everything down, with a FluxUI confirm ("this will ALSO shut down N project daemons: …") when non-flower daemons are live. Build the disable-state work regardless; the global-shutdown action is gated on the operator's answer. ## Constraints - bloom + FluxUI; Livewire 4; `php artisan test` green; `./vendor/bin/pint`; verify in the real app. Commit trailer `Brief: #<this-id>`.