Brief detail view truncates long note/event bodies with no way to expand — operator couldn't read a full note
flower-orchestrator · submitted 2 days ago
detail
What they reported
On /briefs/{id}, long note_added / event bodies are visually truncated in the trace timeline with no "show more" / expand affordance, so the operator could not read a full multi-paragraph note (hit on brief #69, where the orchestrator's answer note was clamped). Repro: add a long note to a brief, open its detail view, observe the note body is cut off with no way to read the rest. Expected: notes should be fully readable — either not clamped, or a click-to-expand ("show more"). Related to #81 (markdown editor/rendered view on this view) and the broader /briefs/{id} readability work in #96. Reported while dogfooding as flower-orchestrator.
context
Structured context
{
"routed": {
"target": "orchestrator",
"todo_id": 377,
"authority": "autonomous",
"routed_at": "2026-07-03T13:18:32+00:00",
"routed_by": "operator:mike",
"project_id": 16,
"solo_todo_id": "697",
"solo_project_id": "49",
"coordination_queue": {
"kind": "route_feedback",
"drain": "orchestrator_recall_signals",
"status": "pending",
"latency": "<= one orchestrator heartbeat",
"signal_id": 12
},
"default_project_id": 16,
"coordination_signal_id": 12,
"fix_spec_scratchpad_id": 368,
"orchestrator_daemon_id": 12,
"solo_fix_spec_scratchpad_id": "1059",
"orchestrator_solo_process_id": 1015
},
"promotion_ledger": [
{
"at": "2026-07-03T13:18:32+00:00",
"action": "orchestrator_routed",
"target": "orchestrator",
"todo_id": 377,
"actor_ref": "operator:mike",
"cycle_key": "2026070313",
"fix_spec_scratchpad_id": 368
}
]
}state · operator override
Lifecycle
- created
- 2d ago
- triaged
- 2d ago
- resolved
- —
- resolved by
- ops
resolution
Low-severity UI readability bug (no crash/data loss). Confirmed 969's own dogfooding report (hit on brief #69). Ops pointer for the fixer: in resources/views/livewire/briefs/show.blade.php the 'truncate' classes are all on single-line titles/names/actor_refs (correct) — the multi-paragraph note_added/event BODY clamp is NOT one of those; look at how the trace-timeline event 'body' is rendered (likely a Str::limit in the Livewire component or a max-height/line-clamp prose container) and add a click-to-expand ('show more') or drop the clamp for note bodies. Already owned by 969's /briefs/{id} readability cluster (#81 markdown view, #96 readability) — NOT separately routed; fold into #96.