Workstream 0cca23a9-9640-491a-92db-6414db891019 (slug state-wp-0053)
created with status: proposed. Six tasks T01-T06 created and their
ids backfilled into the workplan file's task frontmatter so the
consistency checker links file ↔ DB correctly.
Coordination message sent to codex (state hub message
9d4fe78d-c3c4-4a98-a430-88f9757a0c79) requesting review of scope,
owner confirmation, and a decision on whether to promote from
proposed to ready/active.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
Following the CUST-WP-0045 daily-triage cutover, the activity-core
runner now writes a daily progress event with the full WSJF report
nested under detail.report. The only ways to read it today are tail
the working-memory file or curl /progress/ — neither serves the
"sit-down review" use case the triage was designed for.
Proposed dashboard page under the existing Workstreams section:
recent reports table, per-report detail with linked recommendations,
14-day pattern view, action colour cues consistent with the rest of
the dashboard. Read-only; no schema or API changes; reuses the
existing /progress/?event_type=daily_triage endpoint.
Six tasks (T01 skeleton + nav, T02 recent table, T03 detail with
links, T04 colour cues, T05 pattern view, T06 docs). Status:
proposed — awaiting review before workstream registration.
Co-Authored-By: Claude Opus 4.7 <noreply@anthropic.com>
