T-PARC-sdf-adopt-apply-driftreport

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

Goal

Finish the adopt flow: the Apply section, the Plan tab, the adopted-mode drift report and the preview pane tabs.

Today

The shell stubs Apply; actionSetupProject is called only through useProjectSetup, and the preview pane has no tabs.

Proposed

Apply calls actionSetupProject through useProjectSetup (keeping its generation counter), shows the Plan tab on DPathChangeTree, and the adopted-mode /adopt renders a drift report. The preview pane tabs (Files, sdlc.yaml, Model, Routing, Journal) reflect the section drafts.

Approach

1. Fill the Apply section and Plan tab on DPathChangeTree; keep the useProjectSetup generation counter.
2. Add the adopted-mode drift report to /adopt.
3. Wire the preview pane tabs to the section drafts.
4. Add stories Apply and DriftReport.

Areas

Area	Note
solutions/ontological/desktop/src-nuxt/app/components/adopt/sections/ApplySection.vue	Apply
solutions/ontological/desktop/src-nuxt/app/components/adopt/AdoptPreviewPane.vue	tabs
solutions/ontological/desktop/src-nuxt/app/composables/useProjectSetup.ts	consumed, generation counter kept
solutions/ontological/desktop/src-nuxt/app/pages/adopt.vue	drift report mode

Acceptance criteria

• AC-1: In fixture mode a project is adopted end to end: sections, Apply, then /adopt shows a drift report.
• AC-2: The generation counter still discards stale setup results.
• AC-3: Stories Apply and DriftReport exist.
• AC-4: 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-5: Every new story renders at the tauriMedium viewport in light and dark, and a screenshot pair is committed under docs/screenshots/sdf-adopt-apply-driftreport/{light,dark}.png and embedded in the PR body.
• AC-6: 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-7: Fixture timestamps are constants; any force layout has a deterministic seed and a cooldown.

Out of scope

• Real apply backend beyond the existing actionSetupProject.

Dependencies

• Depends on T-R0S1, T-511U and T-T425.

Discovery context

• 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.

Depends on

T-R0S1, T-511U, T-T425

---

← Back to Tasks