T-M7JN-sdf-adopt-docs

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

Goal

Close the adoption set: document the SDF flow and retire the HTML mock.

Today

docs/planning/notes/N-HETB-adopting-a-project.md references a throwaway HTML prototype and has no screen links.

Proposed

adoption.md links each screen’s story and screenshots and notes the HTML mock is retired; the hub README gains a row; src-nuxt/README.md documents fixtures mode and story shots.

Approach

1. Update docs/planning/notes/N-HETB-adopting-a-project.md with story and screenshot links per dimension.
2. Mark wizard-prototype.html retired.
3. Add the hub README row.
4. Document fixture mode and sdf:story-shots in src-nuxt/README.md.

Areas

Area	Note
docs/planning/notes/N-HETB-adopting-a-project.md	screen links
docs/planning/strategy/README.md	hub row
solutions/ontological/desktop/src-nuxt/README.md	fixtures mode and story shots

Acceptance criteria

• AC-1: Every wizard section links its story and screenshots.
• AC-2: The README documents ?fixtures=1, NUXT_PUBLIC_FIXTURES and sdf:story-shots.
• 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).

Out of scope

• Any code change.

Dependencies

• Depends on every other sketch task in the set.

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-GTKM, T-YHMF, T-XC1D, T-R0S1, T-0D40, T-KGQJ, T-511U, T-T425, T-U9W0, T-54ZE, T-IFU1, T-I8E3, T-UD57, T-PARC, T-DK2Q

---

← Back to Tasks