Skip to content

T-KGQJ-sdf-adopt-section-record

State: planning/draft · Impact: medium · Complexity: medium

Build adopt section 10, the operational record, as a props-in, emit-out component with fixtures.

The shell stubs section 10 with a placeholder.

Section 10 captures how the project’s operational record is kept, with Empty and Filled stories. Sections are props-in, emit-out (update:value); only useAdoption() writes the draft. Controls map from sectionRender in docs/planning/strategy/wizard-prototype.html: text to DFieldRow+DInput; packs and posture to DChipChoice; enums and toggles to DSettingRow+DSelect.

  1. Add components/adopt/sections/RecordSection.vue filling the stub.
  2. Add fixtures/adopt/record.ts.
  3. Add stories Empty and Filled.
AreaNote
solutions/ontological/desktop/src-nuxt/app/components/adopt/sections/RecordSection.vuesection 10
solutions/ontological/desktop/src-nuxt/app/fixtures/adopt/record.tsrecord fixtures
solutions/ontological/desktop/src-nuxt/app/types/adopt.tsextend draft types
  • AC-1: Section 10 renders Empty and Filled stories and emits update:value.
  • AC-2: Completing it marks section 10 complete in useAdoption().
  • AC-3: moon run sdf:check and moon run sdf:test pass, run detached one at a time; nuxi typecheck and vue-tsc are never run locally (CI typechecks).
  • AC-4: Every new story renders at the tauriMedium viewport in light and dark, and a screenshot pair is committed under docs/screenshots/sdf-adopt-section-record/{light,dark}.png and 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.ts and package.json are untouched unless this task says so.
  • AC-6: Fixture timestamps are constants; any force layout has a deterministic seed and a cooldown.
  • The record screens (journal and runs task) and the journal backend.
  • Depends on T-XC1D.
  • Plan: /Users/sksizer/.claude/plans/toasty-soaring-ullman.md (the adoption wizard and operator screens, built in SDF) and N-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.

T-XC1D


← Back to Tasks