chore(changeset): the Skills-docs line names the docs moved here and follow-up #30824

The changeset still said validating-metadata.mdx did not list the id;
a97ed9f moved it, and the skills formula row is follow-up #30824.

Co-Authored-By: Claude <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_016WV4d1SZmabyrNd3YLCq3J

Author: claude

.changeset/30773-dataset-dimension-formula-refused.md

@@ -7,7 +7,7 @@ fix(service-analytics, lint)!: a dataset or cube dimension over a formula field
 
 Clause-②: no (narrowing) — the dataset compile (`AnalyticsService.registerDataset`, `queryDataset` and every door that compiles through them) refuses a dataset declaring a dimension over a virtual (`formula`) field of its base object, and the authoring rules refuse a dataset or `analyticsCubes` dimension over one with the new id `dimension-virtual-field-refused`, bodies they accepted before. Nothing is widened: the one new export (`DIMENSION_VIRTUAL_FIELD_REFUSED`, the rule id's constant beside its two siblings in `@objectstack/lint`) adds no accepted input, and no error code, status or answer member is added.
 Metadata-protocol: narrowed
-Skills-docs: no move — `skills/**` teaches no dataset dimension verdict (`objectstack-data/rules/field-types.md` says a formula is virtual and a dataset measure needs a stored field, and does not mention dimensions), and `content/docs/deployment/validating-metadata.mdx` does not yet list this id beside `dimension-json-stored-field-refused`; both are reported for the owning seat. The prescription ships in the refusal text and below.
+Skills-docs: updated here — `content/docs/deployment/validating-metadata.mdx` names `dimension-virtual-field-refused` beside `dimension-json-stored-field-refused` and in its cube paragraph; follow-up #30824 moves `skills/objectstack-data/rules/field-types.md`'s formula row (the skills lane). The prescription ships in the refusal text and below.
 
 <!-- adr-0087: not-required (no-migration-prescription) No key of any schema is added, removed, renamed or re-shaped: DatasetDimension.field and a cube dimension's sql keep their shape and meaning. A dimension over a formula never served a group (since the query-time refusal every query selecting it answers 400 INVALID_FIELD, and before it a 500, a driver backstop or one null group), so there is no rewrite that keeps what the author meant: the author stores the value on a field of its own, or removes the dimension, and the refusal names the dimension and the field. -->