T-DK2Q-sdf-nav-unlock-wiring

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

Goal

Make locked screens explain themselves: lock hints and banners through the middleware and useAdoption().unlocked(), plus nav badges.

Today

Once adopted, no screen tells the user which wizard section feeds it, and the nav has no lock state.

Proposed

Work, control-plane, dispatch and model show a soft ‘complete section N to unlock’ banner, never a redirect, and the nav shows badges. No page file edits are expected.

Approach

1. Add the lock banner component and drive it from useAdoption().unlocked() via the middleware or layout.
2. Add nav badges in ProjectScopePane; serialize after the shell task.
3. Update ProjectScopePane.test.ts and add tests for banner visibility.

Areas

Area	Note
solutions/ontological/desktop/src-nuxt/app/components/ProjectScopePane.vue	nav badges
solutions/ontological/desktop/src-nuxt/app/middleware/adopt.global.ts	banner state
solutions/ontological/desktop/src-nuxt/app/composables/useAdoption.ts	read only: unlocked()

Acceptance criteria

• AC-1: A locked screen renders its content plus the banner and is never redirected.
• AC-2: Nav badges reflect unlock state.
• AC-3: ProjectScopePane.test.ts passes.
• 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-nav-unlock-wiring/{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

• New pages or edits to work, dispatch and model page files.

Dependencies

• Depends on T-XC1D and T-54ZE.

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-XC1D, T-54ZE

---

← Back to Tasks