flower:daemon-checkin --project defaults to 'flower' and silently mis-scopes non-flower daemons onto the flower roster when omitted

Running `flower:daemon-checkin --role=refine --actor-ref=home-tracker-refine` (no --project) from a home-tracker Solo agent registered the daemon under project flower (id 16) instead of home-tracker (22). Effect: the operator-pre-registered expected home-tracker refine daemon #31 stayed never-live, and a stray daemon #32 (actor_ref home-tracker-refine) was created on the flower roster. Both the home-tracker refine AND orchestrator sessions hit this (home-tracker #30 still expected; #33 home-tracker-orchestrator landed on flower). The output only says "checked in: refine @ flower", easy to miss. The command already self-resolves solo_process_id + session_id from the Solo PTY env, where SOLO_PROJECT_ID is set — suggest deriving --project from SOLO_PROJECT_ID by default (or erroring on ambiguity) rather than hardcoding default 'flower'. Also recommend the daemon spawn packet/charter include an explicit --project=<slug> in the check-in command it tells daemons to run.

{
    "tool": "flower:daemon-checkin (artisan command)",
    "observed": "registered @ flower instead of home-tracker",
    "workaround": "pass --project=home-tracker explicitly"
}

created

1d ago

triaged

—

resolved

—

resolved by

—