govkit-ui-spec-planninglisted

# Spec Planning — UI You are performing Spec Planning for a UI feature. Determine the feature name from the user's request; if it is not provided, ask before proceeding. Read the following before proceeding: - `features/<feature_name>/acceptance.feature` - `features/<feature_name>/nfrs.md` - `features/<feature_name>/architecture_preflight.md` - `docs/ui/architecture/MVVM_CONTRACT.md` - `docs/ui/evaluation/eval_criteria.md` - `governance/ui/templates/plan.md` - `governance/ui/schemas/eval_criteria.schema.json` --- Produce or update `features/<feature_name>/plan.md` and `features/<feature_name>/eval_criteria.yaml`. ## plan.md must include: ### 1. Feature Summary One paragraph describing the feature from the user's perspective. ### 1.5 Scope Boundaries Populate the plan's `### Out of scope` from `nfrs.md` `## Out of scope`: - If `nfrs.md` has a non-empty `## Out of scope` section, copy its entries into the plan verbatim (author-declared — no marker). - If `## Out of scope` is missing or empty, infer the deferred capabilities from the spec's negative space, then BOTH: - insert `<!-- INFERRED: not declared in nfrs.md ## Out of scope; confirm with feature owner -->` directly under the plan's `### Out of scope` heading, and - state in the planning summary that Out-of-scope was inferred and should be confirmed. ### 2. MVVM Breakdown For each layer: - Components to create (with props interface summary) - Hooks / query inject functions to create (query keys, data shape, tr