T-I8E3-sdf-record-journal-runs
State: planning/draft · Impact: medium · Complexity: large
Build the record screens for the journal and runs: tail, run summary and trace timeline.
No journal or run screens exist, and the backend (journal, run kind) is not built.
Proposed
Section titled “Proposed”pages/record/index.vue shows a journal tail and run list; pages/record/runs/[id].vue shows a run
summary and trace, over fixtures JournalEvent {ts,kind,actor,subject,payload} and
Run {id,state,steps[],cost}.
Approach
Section titled “Approach”- Add
fixtures/record/{journal,runs}.ts. - Add
components/record/{JournalTail,RunSummary,TraceTimeline}.vueusingDRowList,DStatTileandDMeterRow. - Add
pages/record/index.vueandpages/record/runs/[id].vue. - Add stories per component, including Empty.
| Area | Note |
|---|---|
solutions/ontological/desktop/src-nuxt/app/pages/record/ | index and run detail |
solutions/ontological/desktop/src-nuxt/app/components/record/ | tail, summary, timeline |
solutions/ontological/desktop/src-nuxt/app/fixtures/record/ | journal and run fixtures |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: Journal tail, run summary and trace render from fixtures and have Empty states.
- AC-2: Opening a run from the index shows its trace.
- AC-3:
moon run sdf:checkandmoon run sdf:testpass, run detached one at a time;nuxi typecheckand vue-tsc are never run locally (CI typechecks). - AC-4: Every new story renders at the
tauriMediumviewport in light and dark, and a screenshot pair is committed underdocs/screenshots/sdf-record-journal-runs/{light,dark}.pngand embedded in the PR body. - AC-5: Only
--d-*tokens, no raw colors; D* components come from@determined/ui;app/generated/*,app.vue,nuxt.config.tsandpackage.jsonare untouched unless this task says so. - AC-6: Fixture timestamps are constants; any force layout has a deterministic seed and a cooldown.
Out of scope
Section titled “Out of scope”- Friction and proposals (next task) and the journal backend.
Dependencies
Section titled “Dependencies”- Depends on
T-XC1D.
Discovery context
Section titled “Discovery context”- Plan:
/Users/sksizer/.claude/plans/toasty-soaring-ullman.md(the adoption wizard and operator screens, built in SDF) andN-6DUQ. - Control spec:
docs/planning/strategy/wizard-prototype.html; strategy: N-HETB-adopting-a-project. - Rules every agent follows are in the plan and the shared acceptance criteria above; the derive step later replaces fixtures with generated transport.
Depends on
Section titled “Depends on”T-XC1D