Lock settings interaction docs and regressions (codex)

[numnx]

🧩 Task: Lock settings interaction docs and regressions

Automated task PR opened by Code UX for T05.

📋 Summary

Sprint: Sprint 155 · QS: UI - Interactions & Design Improvements · Task: T05

Refine the Settings page interaction layer so the scope selector and active-panel saved state stick together, search-only metadata appears only when useful, and the visual/copy treatment is cleaner without changing settings persistence behavior.

📝 Full Task Prompt

## Objective
Document the refined Settings interaction contract and add end-to-end-enough dashboard regression coverage so future changes keep the sticky bar, active-panel status, and search-only metadata behavior intact.

## Scope
- `dashboard/src/v2/components/settings/__tests__/SettingsControls.test.tsx`
- `docs/dashboard/design-system-settings.md`
- `docs/dashboard/dashboard-guide.md`
- `docs/dashboard/interaction-patterns.md` if the Settings row needs wording alignment
- `docs-web/content/docs/user-dashboard-settings.mdx`
- `docs-web/user/dashboard/settings.md`
- Do not edit branch, PR, release, or generated build artifacts

## Implementation Requirements
1. Replace older documentation that says the scope strip and active-panel strip are separate sticky surfaces with the new contract: one unified sticky Settings bar contains scope selection, scope context, active panel, and save state.
2. Document that `visible categories` is search-only metadata and should not be shown when Smart Find is idle.
3. Document the visual decision to avoid a long card background behind the scope controls while preserving focus rings, tokenized contrast, wrapping, and reduced-motion-safe status cues.
4. Add or update regression tests that assert `SettingsPage.tsx` uses the extracted `SettingsScopeControls` and `SettingsActivePanelStatus`, suppresses the duplicate `SettingsContentPanels` sticky strip, and keeps `SettingsContentPanels` capable of sticky mode for standalone use.
5. Run the docs-web sync/check command if documentation mirroring requires it, and update mirrored docs consistently if the sync tool reports drift.

## Constraints
- Do not use this task to redesign unrelated Settings panels or provider cards.
- Do not claim runtime/browser validation in docs unless it was actually performed.
- Keep public docs user-facing and avoid internal-only implementation jargon where possible.
- Preserve the repository rule that docs source of truth lives under `docs/` and public docs under `docs-web/` are updated consistently.

## Verification
- Run `pnpm exec vitest run dashboard/src/v2/components/settings/__tests__/SettingsControls.test.tsx`.
- Run `pnpm run check:docs-web` if docs-web sync is expected for edited pages; otherwise run `rg "visible categories|unified sticky|Active panel|Settings scope" docs/dashboard docs-web/content/docs/user-dashboard-settings.mdx docs-web/user/dashboard/settings.md` to verify wording.
- Run `pnpm run typecheck:dashboard`.
- Success means tests protect the new interaction contract and docs no longer describe the removed long background card or always-visible category-count chip.

✅ QA Review

⏳ QA review runs after this PR is opened. Check the task card in the dashboard for the outcome once it lands.

🤖 Model & Provider

Provider	Codex CLI
Model	gpt-5.5

⏱️ Timing

Started	2026-07-07 04:50:50 UTC
Finished	2026-07-07 04:55:36 UTC
Duration	4m 45s

📊 Token Usage

Metric	Value
Input tokens	149,435
Cached input tokens	1,327,744
Output tokens	7,846
Total tokens	1,485,025
Invocations	1
Tool calls	45
Active time	3m 55s

Included usage estimate (subscription/local login): $1.65

🌿 Branch Info

Base: feature/CODUX-155-qs-ui-interactions-design-improvements-8
Head: task/feature-codux-155-qs-ui-interactions-design-impr-t05-codex-mra685v9

---

🤖 Generated by Code UX