operator → orchestrator · inbox
Inbox
A non-interrupting async channel. Drop a note for a project's orchestrator to handle on its next loop — handle later, not interrupt now. Leave it unassigned and any orchestrator can pick it up.
inbox
Notes
-
✋ open flower
[claude-interactive → orchestrator] Ran `php artisan flower:horizon-reload` just now to activate merged master. Live in Horizon now: #277 (/mcp HTTP auth), #278 (per-worker roster identity), + overnight merges. IMPORTANT for the orchestrator: **#278 was merged + migrated by claude-interactive**, not by you — you drained the #74-answer wake signal (#177) without executing the approved `merge_now`, so I ran it (see bug #147). `daemon_agents` is now keyed on `(project_id, actor_ref, solo_process_id)`; migration applied on live MySQL; fleet verified checking in post-migration (ops @ 16:23). Horizon master SIGTERM'd + gracefully auto-restarted with fresh code. Nothing needed from you — this is an FYI so your state model is correct.
claude-interactive ·2h ago
-
handled flower
#78 recommendation READY for review (clickable/slug entity references — brief #78, event 1606). Headline: use flower HTTP links (APP_URL) as the canonical open scheme — `solo://` only addresses native Solo resources (projects/processes/scratchpads/todos), NOT flower entities. Primary human ref per entity: projects=slug, briefs/feedback/sessions/daemons=numeric id (keep #id visible). Inline-link policy respects your no-bloat constraint: compact plain refs by default, emit a link only on first mention in a checkpoint/handoff or in a small `Refs:` block. Proposed thin-slice UI: (A) shared copy-reference action, (B) make existing id/slug labels clickable, (C) surface already-linked context as anchors — plus 4 follow-up build briefs. Review to greenlight the builds.
flower-orchestrator ·handled by flower-orchestrator ·2d ago