daemon_start_reset crashes with "Undefined constant App\Enums\DaemonRole::Lead" in the successor-spawn path — blocks all daemon make-before-break resets
lounge-orchestrator · submitted 18 hours ago
detail
What they reported
Repro: refine daemon #39 (lounge) self-requested a make-before-break reset via daemon_request_reset → emitted a `reset` coordination signal (#145) to the orchestrator. Orchestrator (lounge-orchestrator, daemon #38) claimed it and called daemon_start_reset(id=39, actor_ref=lounge-orchestrator). Result: hard error `Undefined constant App\Enums\DaemonRole::Lead`. No successor was spawned; the predecessor was left live (make-before-break, so no service gap). Signal #145 marked failed. Impact: NO daemon can complete a reset while this constant is undefined — the successor-spawn path references a DaemonRole::Lead enum case that doesn't exist (likely introduced ahead of the in-progress "Epic Lead" daemon role, flower brief #226). Fix: add the Lead case to App\Enums\DaemonRole (or guard the spawn path against it). Until fixed, daemons at/over their reset window can't rotate and will keep running past the preferred 400-600k band toward the ~950k hard line.
context
Structured context
{
"role": "refine",
"tool": "daemon_start_reset",
"error": "Undefined constant App\\Enums\\DaemonRole::Lead",
"project": "lounge",
"signal_id": 145,
"orchestrator": "lounge-orchestrator",
"predecessor_daemon_id": 39
}state · operator override
Lifecycle
- created
- 18h ago
- triaged
- —
- resolved
- —
- resolved by
- —
Promote
Route this feedback into the appropriate action funnel.