flower
/
All briefs
complete draft note flower

/rooms: add left-nav link + a lobby/index (rooms list with needs-you + last-activity)

canonical · plan

Spec

markdown

hand-off · dispatch

Dispatch

Auto-dispatch

when it reaches planned

Design-loop

design pass before build

This brief is complete — dispatch is closed.

provenance · append-only

Trace

live
or paste a screenshot uploading…
  1. link added 3d ago
    agent · system:commit-trailer
  2. participant joined 3d ago
    system · system:commit-trailer
  3. status change 3d ago
    agent · flower-orchestrator
  4. status change 3d ago
    agent · flower-orchestrator
  5. note added 3d ago

    ## Gap (operator, 2026-07-02) #39 shipped the per-project operator feed at `/rooms/{project:slug}`, but there's (a) NO left-nav link to it, and (b) no index/lobby — nowhere to land if you don't already have a project slug in the URL. ## Build 1. **Left-nav link** for the operator feed/rooms — match the existing nav pattern (e.g. the Briefs subitems #47/#59 added). Top-level "Rooms" (or under an activity section) is fine. 2. **/rooms lobby (index):** a Livewire index listing the per-project rooms (projects that have daemons/activity), each linking to its `/rooms/{project}` feed. For each room show at-a-glance signal: **needs_you count + last-activity time** (reuse #39's FeedService classification), sorted needs_you-first / most-recent, so the operator sees which room needs attention. 3. Optional: a combined "all projects" feed view — but the lobby list is the minimum. ## Acceptance - Left-nav link to rooms present; `/rooms` lobby lists rooms with needs_you count + last-activity, each linking to its per-project feed. Livewire/feature tests. No migration. sqlite tests only; pint; match the bloom design system. No Horizon reload. `Brief:` trailer with this id. ## Provenance Operator 2026-07-02: "no nav link for /rooms + no index/lobby — do something about that." Builds directly on #39 (the /rooms feed + FeedService).

    agent · flower-orchestrator
  6. participant joined 3d ago
    system · flower-orchestrator

epic · dependencies

Relationships

epic parent

depends on

No dependencies — dispatchable once planned.

agents · waves

Participants

  • flower-orchestrator participant · active
  • system:commit-trailer participant · active

trace · graph

Links

  • Commit #1586 execution

scope

Projects

  • flower · primary

dogfood · read-only

Agent’s-eye view

The literal recall_brief payload an agent gets — same service path as the MCP tool.