Fix Briefs nav open-questions badge: realign count to the Open Questions view + move badge to the child row

You are being dispatched from flower Brief #154: Fix Briefs nav open-questions badge: realign count to the Open Questions view + move badge to the child row

Recall pointer:
- Use recall_brief with id 154 for the full folder if you need provenance.

Target:
- project: flower (/Users/mikeferrara/Documents/code/flower)
- branch: flower/154-badge-fix
- worktree: not specified
- kind: fresh

Current brief spec:
(no spec yet)

This is a direct request, not a fully-specced plan. If it's clear, resolve it. If you hit a blocking ambiguity, call brief_ask (or brief_append) with your questions and flip the brief to `refining` before proceeding — don't guess.

Recent/key trace events:
[1] participant_joined flower-orchestrator: (no body)
[2] note_added flower-orchestrator: Operator-reported (2026-07-03): the left-nav "Briefs" badge shows 8 open questions but the Open Questions view shows 4. Two fixes.

PROBLEM: The badge = `BriefQuestion::openCount()` (app/Models/BriefQuestion.php ~lines 38-41) = count of ALL open questions regardless of brief status or project (currently 8: 4 on brief #143 which is COMPLETE + 4 on brief #54 in another project). The Open Questions view (briefs.index?questions=open) uses `briefQuery(hideCompleted=true)`, so it hides completed briefs and shows 4. Hence 8 vs 4.

FIX A (realign count): Scope `BriefQuestion::openCount()` to EXCLUDE open questions whose brief status is complete/cancelled/abandoned — count only questions on live briefs — so the badge matches the Open Questions view. openCount() is the single source of truth shared by the layout badge, the OpenQuestionsChanged broadcast payload, and its tests (see the docblock) — keep them consistent and update the test.

FIX B (relocate badge): In resources/views/components/layouts/app.blade.php the `[data-open-questions-badge]` span currently lives inside the "Briefs" parent nav `<a>` (~lines 91-98). Move it onto the "Open Questions" child sublink (~line 100, the `<a>` to route('briefs.index', ['questions'=>'open'])). Preserve the live-update JS hook (data-open-questions-badge) + hidden-when-0 behavior.

ACCEPTANCE: badge count == Open Questions view count; badge renders on the Open Questions child row (not the Briefs parent); hidden when 0; `php artisan test` green (update the openCount test); pint. `Brief: #<id>` trailer.

Provenance: operator-reported. Related: bug #71 (a prior orchestrator completed brief #143 while it had 4 open questions — the deeper cause of stale-open-on-complete questions).
[3] status_change flower-orchestrator: (no body)

Recommended linked context:
{
    "todos": [],
    "scratchpads": []
}

Execution notes:
- Treat the brief as the source of truth.
- Keep work scoped to this dispatch request.
- Use brief_append / brief_update_status when reporting material progress; as your final dispatched-worker step, call brief_dispatch_complete with dispatch_request_id (or brief_id) and actor_ref.
- Codex workers should verify mutating Flower tools with tool_search query `brief_append brief_dispatch_complete flower_feedback` (limit 20) when tool availability is in doubt; report raw SEE/LOAD vs NOT visible instead of silently using local fallbacks.
- Add a git commit trailer `Brief: #154` to every commit for this brief so flower can exact-link commits back to the brief.