fix(spec): repo-rooted anchors in the CubeMeta docblock; leave the stage-2 changeset untouched

The pending stage-2 release note is restored byte-for-byte from the merge base
(the foreign changeset rule); this change's own changeset states which of its
sentences /meta now supersedes.

Claude-Session: https://claude.ai/code/session_01Sfe5YjBLwB9J3y8fvm2xq1
Co-authored-by: Claude <noreply@anthropic.com>

Author: claude

.changeset/20282-analytics-cube-format-granularities-enforced.md

@@ -13,7 +13,7 @@ Clause-②: yes (narrowing)
 
 Until this change both keys were read on the compiled-dataset path only. One cube shape has three producers — cubes authored with `defineCube()` / `defineStack({ analyticsCubes })`, cubes the dataset compiler mints, and cubes inferred for an ad-hoc query — and only a compiled dataset's cube reached the two readers:
 
-- **`measures.<metric>.format`** reached a caller as `fields[].format` only because the dataset door copies it from the DATASET measure. An authored cube has no dataset, so `POST /api/v1/analytics/query` described its measure columns with `name` and `type` alone. Now every measure column a query names carries the `format` its cube measure declares, whichever strategy answered, and a column that declares none carries no `format` key at all. A client that formats a result column reads `format` off the query result's `fields[]`, as the Data API page says; `GET /api/v1/analytics/meta` also publishes each measure's declared `format`, a separate entry in this release. The value is relayed verbatim; the vocabulary `fields[].format` documents is a numeral pattern such as `"$0,0.00"` or `"0.0%"`.
+- **`measures.<metric>.format`** reached a caller as `fields[].format` only because the dataset door copies it from the DATASET measure. An authored cube has no dataset, so `POST /api/v1/analytics/query` described its measure columns with `name` and `type` alone. Now every measure column a query names carries the `format` its cube measure declares, whichever strategy answered, and a column that declares none carries no `format` key at all. `GET /api/v1/analytics/meta` is unchanged: its projection stays `name`, `type` and `title`, and a client reads `format` off the query result's `fields[]`, as the Data API page already says. The value is relayed verbatim; the vocabulary `fields[].format` documents is a numeral pattern such as `"$0,0.00"` or `"0.0%"`.
 - **`dimensions.<dimension>.granularities`** was the default bucket only for a compiled dataset, which the dataset executor filled in before querying. An authored cube's time dimension grouped raw timestamps whatever it declared. Now `query()` and the `generateSql()` dry run read it the same way, through the one rule both paths share: a single-entry list is the dimension's default bucket for a query that groups by it; a granularity the query states always wins, and one the list does not name is not refused (the dataset path compares against no list either); a list of two or more states no default; and a `timeDimensions` entry that carries only a `dateRange` for a dimension the query does not group stays a filter.
 
 What to expect after upgrading:

.changeset/20282-analytics-cube-meta-descriptions.md

@@ -10,3 +10,5 @@ Clause-②: yes (widening)
 - `CubeMeta` (`@objectstack/spec/contracts`) gains an optional `description` on the cube and on each measure and dimension, and an optional `format` on each measure. `AnalyticsMetadataResponseSchema` declares the same members. A definition that declares none of them is published exactly as before.
 - `AnalyticsService.getMeta` copies what the definition declares and fills in nothing. A cube compiled from a dataset carries each dataset measure's `format` and no `description`.
 - The liveness ledger rows `analytics_cube.description`, `measures.description` and `dimensions.description` move from `dead` to `live`.
+
+This supersedes one sentence of this release's note on an authored cube's measure `format` and `granularities`: it says `GET /api/v1/analytics/meta` is unchanged and keeps `name`, `type` and `title`. With this change `/meta` also publishes each measure's declared `format`. A client that formats a result column still reads `format` off the query result's `fields[]`.

packages/spec/src/contracts/analytics-service.ts

@@ -217,8 +217,9 @@ export interface AnalyticsResult {
  *
  * `description` (on the cube and on each member) and a measure's `format` are
  * copied from the cube definition when it declares them and absent when it
- * does not; `api/analytics.zod.ts#AnalyticsMetadataResponseSchema` declares
- * the same shape and `api/analytics.test.ts` binds the two at compile time.
+ * does not; `packages/spec/src/api/analytics.zod.ts#AnalyticsMetadataResponseSchema`
+ * declares the same shape and `packages/spec/src/api/analytics.test.ts` binds
+ * the two at compile time.
  */
 export interface CubeMeta {
     /** Cube name */