T-IFU1-sdf-config-explorer

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

Goal

Build the config explorer: sdlc.yaml as a tree with per-key provenance, an explain popover and the extends list; also reused by the adopt preview pane.

Today

There is no config screen; provenance is only visible through the CLI.

Proposed

pages/config.vue shows a DTree of config keys with DBadge provenance, a DDescriptionList explain popover, and an extends list, over fixture ConfigEntry {path,value,source:{kind,file,line},overridden_by[]} with layers default, pack, project, local, filesystem.

Approach

1. Add fixtures/config/*.ts with ConfigEntry data across all five layers.
2. Add components/config/{ConfigTree,ProvenanceBadge,ExplainPopover,ExtendsList}.vue.
3. Add pages/config.vue.
4. Add stories Tree, Explain and Extends.

Areas

Area	Note
solutions/ontological/desktop/src-nuxt/app/pages/config.vue	new page
solutions/ontological/desktop/src-nuxt/app/components/config/	tree, badge, popover, extends list
solutions/ontological/desktop/src-nuxt/app/fixtures/config/	fixtures

Acceptance criteria

• AC-1: Every layer’s badge is distinguishable, and an overridden key shows what overrides it.
• AC-2: The explain popover shows file and line.
• AC-3: Stories Tree, Explain and Extends 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-config-explorer/{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 config explain wiring (derive step).

Dependencies

• Depends on T-XC1D.

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

---

← Back to Tasks