Daemon reset crashes spawning a 'lead'-role successor: "Undefined constant App\Enums\DaemonRole::Lead"

Observed live via recall_roster (project flower) on 2026-07-05 while doing decoupling work (epic #263). The lounge-refine daemon (roster id 39) shows reset_state="failed" with reset_last_error="successor spawn failed: Undefined constant App\\Enums\\DaemonRole::Lead" (reset_requested_at/reset_failed_at 2026-07-05T01:16:46Z). Scope/existing-functionality bug: daemon_checkin accepts role='lead' (enum orchestrator|ops|refine|lead|other), but App\Enums\DaemonRole appears to have no Lead case, so any code path that constructs a 'lead' successor (the daemon reset / make-before-break successor spawn) throws an "Undefined constant" fatal and the reset fails. Either the enum is missing the Lead case, or the reset/spawn path references a role the enum no longer defines. Not new functionality — the 'lead' role is already advertised and used; its scope just isn't implemented consistently. Repro pointer: inspect App\Enums\DaemonRole for a Lead case vs. the successor-spawn path used by daemon reset; recall_roster surfaces the failed state on daemon 39.

{
    "epic": 263,
    "tool": "recall_roster",
    "error": "Undefined constant App\\Enums\\DaemonRole::Lead",
    "project": "flower",
    "observed": "reset_state=failed",
    "observed_daemon_id": 39
}

created

14h ago

triaged

—

resolved

—

resolved by

—