T-UD57-sdf-record-friction-proposals
State: planning/draft · Impact: medium · Complexity: medium
Add friction list and proposal cards to the record screens: accept, reject, promote to task.
The record page shows journal and runs only; no friction data exists.
Proposed
Section titled “Proposed”Friction and proposals render on pages/record/index.vue with accept, reject and promote-to-task
actions.
Approach
Section titled “Approach”- Add
fixtures/record/friction.ts. - Add
components/record/{FrictionList,ProposalCard}.vue. - Wire them into
pages/record/index.vue; rebase after the journal-and-runs PR merges since both edit this page. - Add stories Friction, Proposals and Empty.
| Area | Note |
|---|---|
solutions/ontological/desktop/src-nuxt/app/components/record/ | friction list and proposal card |
solutions/ontological/desktop/src-nuxt/app/fixtures/record/friction.ts | fixtures |
solutions/ontological/desktop/src-nuxt/app/pages/record/index.vue | shared with the journal-and-runs task |
Acceptance criteria
Section titled “Acceptance criteria”- AC-1: Accept, reject and promote emit events and update fixture state in stories.
- AC-2: Stories Friction, Proposals and Empty exist.
- 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-friction-proposals/{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”- The
frictionentity kind and retro aggregation.
Dependencies
Section titled “Dependencies”- Depends on
T-I8E3(shared record page).
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-I8E3