Skip to content

T-R0S1-sdf-adopt-sections-identity-ontology

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

Build adopt sections 1 (identity and adoption) and 2 (ontology and dev packs) as props-in, emit-out components with fixtures.

The shell stubs both sections with a placeholder; no fixtures or controls exist.

Both sections render real controls bound to the draft through the shell, 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/{Identity,Ontology}Section.vue filling the stubs.
  2. Add fixtures/adopt/{identity,packs}.ts with typed data and constant timestamps.
  3. Emit update:value; do not write the draft from the section.
  4. Add stories Empty and Filled per section.
AreaNote
solutions/ontological/desktop/src-nuxt/app/components/adopt/sections/IdentitySection.vuesection 1
solutions/ontological/desktop/src-nuxt/app/components/adopt/sections/OntologySection.vuesection 2
solutions/ontological/desktop/src-nuxt/app/fixtures/adopt/identity and packs fixtures
solutions/ontological/desktop/src-nuxt/app/types/adopt.tsextend the temporary draft types
  • AC-1: Both sections render Empty and Filled stories and emit update:value on every control change.
  • AC-2: Completing both marks sections 1 and 2 complete in useAdoption() in fixture mode.
  • 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-sections-identity-ontology/{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.
  • Other sections, Apply, and backend wiring.
  • Depends on T-XC1D for the registry and stubs.
  • 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