[self-care:reactive-ui] Correct reactive-ui skill view metadata guidance #20175

The reactive-ui skill told authors to record a view-level intent when adding a named UI element. Views have no intent field: it is valid only on pages and table actions. Views take subject, objective and acceptance. This change corrects the skill text only. No production JavaScript, dashboard documents or tests change, and rendered behavior is unaffected.

No eligible pure-declarative view-source migration was found. The remaining JavaScript row shaping (operationalValueEvidenceRows, measurementRows, simulationDaysSource) is source normalization inside the query engine, not view-owned shaping. Removing it would need production JavaScript changes, which this task forbids for a migration. The skill-drift fallback therefore applies.

Evidence

• docs/dashboard-language-specification.md line 341 lists the View keys: subject, objective and acceptance, with no intent.
• Page, built-in page and row-action tables list intent (lines 331, 332, 358).
• dashboard/site/src/validator-views.js validates view.subject and has no view intent handling.

Validation

Documentation-only change to a skill file. No code or dashboard document changed, so no test suites were run.

Control Plane

• Correlation ID: 41746791603-3278
• Central repository: githubnext/gh-cao
• Control plane run: https://github.com/githubnext/gh-cao/actions/runs/41746791603

cao: githubnext/gh-cao, correlation: 41746791603-3278

To route changes like this to a review issue instead of blocking, configure protected-files: fallback-to-issue in your workflow configuration.

Generated by SelfCare / Reactive UI Expert · copilot · auto · ~52 AIC · ⌖ ~1 AIC · ⊞ 16K · ◷

• expires on Nov 11, 2026, 12:39 AM UTC