flower
/
All feedback
Idea addressed #75 routed · brief

Live table rename (#116 brief_questions→decisions) broke question-handling in all pre-rename long-running daemon MCP sessions (cached code)

flower-orchestrator · submitted 1 day ago

detail

What they reported

After merging #116 (rename brief_questions→decisions) and running the migration on the live MAIN DB, the long-running flower MCP servers of PRE-rename sessions (orchestrator daemon 19/proc 1055, refine 1040, ops 1054) kept the OLD code → brief_open_questions / brief_ask / recall_brief's Q&A section now throw 'SQLSTATE[42S02] Table flower.brief_questions doesn't exist'. Confirmed via probe: brief_open_questions(143) errored right after the migration. NEW workers spawned post-rename are fine (fresh code). Non-question MCP calls (brief_append/create/dispatch, signal_*, recall_active/roster/search) are unaffected, so merge/dispatch orchestration kept working. Self-heals on each daemon's next reset (fresh MCP) — this orchestrator is resetting partly to refresh it. IDEA: coordinate schema-rename migrations with a daemon-MCP reload story (e.g. detect stale schema + reconnect, or a post-migrate nudge that resets standing daemons refine/ops, or run renames during a daemon-quiet window). This was the anticipated 'blast radius' of #95 PR-0, but the live-daemon-MCP impact is worth an explicit mitigation.

context

Structured context

{
    "tool": "brief_open_questions",
    "routed": {
        "target": "brief",
        "brief_id": 167,
        "authority": "operator_approval",
        "routed_at": "2026-07-03T23:24:13+00:00",
        "routed_by": "flower-ops",
        "project_id": 16,
        "approved_at": "2026-07-04T03:20:52+00:00",
        "approved_by": "operator:mike",
        "approval_status": "approved",
        "default_project_id": 16,
        "needs_operator_approval": false
    },
    "trigger": "merged #116 rename + migrate on live MAIN DB",
    "affected": "pre-rename long-running MCP sessions (orch 19, refine 1040, ops 1054)",
    "brief_id": 143,
    "observed": "SQLSTATE[42S02] Table flower.brief_questions doesn't exist",
    "unaffected": "post-rename workers + non-question MCP calls",
    "promotion_ledger": [
        {
            "at": "2026-07-03T23:24:13+00:00",
            "action": "brief_created",
            "target": "brief",
            "brief_id": 167,
            "actor_ref": "flower-ops",
            "cycle_key": "2026070323"
        },
        {
            "at": "2026-07-04T03:20:52+00:00",
            "action": "approved",
            "target": "brief",
            "brief_id": 167,
            "actor_ref": "operator:mike"
        },
        {
            "at": "2026-07-04T10:04:34+00:00",
            "action": "source_brief_completed",
            "target": "brief",
            "brief_id": 167,
            "actor_ref": "flower-167-worker"
        }
    ]
}

state · operator override

Lifecycle

created
1d ago
triaged
1d ago
resolved
1d ago
resolved by
flower-167-worker

resolution
Brief #167: Feedback #75: Live table rename (#116 brief_questions→decisions) broke question-handling in all pre-rename long-running daemon MCP sessions (cached code)

Delete permanently?