docs(validation): update agent configs, skills, ADRs, specs

- qa-tester: add validation v2 testing checklist
- speckit.plan: add component reuse scan for frontend
- molecular-cot-logging: add Svelte logger + CLI reader
- semantics-svelte: add RSM model-first protocol, frontend stack
- templates: update plan/tasks/ux-reference templates
- ADR-0004: add llm_dashboard_validation plugin registration
- ADR-0008: add assistant tool registry for v2 validation
- Specs: update 017 tasks from 51 to 99

.specify/templates/ux-reference-template.md

@@ -40,10 +40,11 @@ $ command --flag value
     *   **[Button Name]**: Primary action. Color: Blue.
     *   **[Input Field]**: Placeholder text: "Enter your name...". Validation: Real-time.
 *   **Contract Mapping**:
-    *   **`@UX_STATE`**: Enumerate the explicit UI states that must appear later in `contracts/modules.md`
+    *   **`@UX_STATE`**: Enumerate the explicit UI states that must appear later in `contracts/modules.md`. For complex screens, these derive from the Screen Model's `@STATE` declarations.
     *   **`@UX_FEEDBACK`**: Define visible system reactions for success, validation, and failure
     *   **`@UX_RECOVERY`**: Define what the user can do after failure or degraded state
-    *   **`@UX_REACTIVITY`**: Note expected Svelte rune bindings with `$state`, `$derived`, `$effect`, `$props`
+    *   **`@UX_REACTIVITY`**: Note the model-driven reactive chain: Model atoms (`$state`, `$derived`) → component props → DOM binding. For route-level data loading, use SvelteKit `load()` functions; `$effect` is for browser-side side effects only.
+    *   **Screen Model**: For screens with cross-widget logic, reference the planned `[TYPE Model]` (`.svelte.ts` file in `frontend/src/lib/models/`). The model declares `@STATE`, `@ACTION`, and `@INVARIANT`. Components bind to the model via `@RELATION BINDS_TO -> [ModelId]`.
 *   **States**:
     *   **Idle/Default**: Clean state, waiting for input.
     *   **Loading**: Skeleton loader replaces content area.