docs(spec): correct the tracing entry's lit control and name the released package version

Two corrections from the in-seat contract review of PR #18016.

The ADR-0087 entry's lit control said 20875 Schema occurrences on a corpus it
described as the tree excluding `packages/spec` AND the generated reference
pages. 20875 is the count with `content/docs/references` still in; the corpus
the sentence names reads 18920. Both numbers now come from one `git grep -o`
over `98bd7986fe` carrying both pathspec exclusions, and the sentence names
that corpus exactly.

The four tombstone prescriptions said `@objectstack/spec 18`. That conflates
two axes: the prose names the released PACKAGE version, which is 17 (this
ships in 17.5.0), while `RETIRED_KEYS_BY_MAJOR[18]` names the PROTOCOL major.
A reader told "18" would look in a v18 that does not carry it. The tree spells
it 17 in 265 places against 14, and this file's own `Span.duration` precedent
says 17.

`registry.ts` and the reference page are regenerated, not edited.

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

Author: claude

content/docs/references/system/tracing.mdx

@@ -53,7 +53,7 @@ OpenTelemetry compatibility configuration
 | **protocol** | `string` | optional | Protocol version |
 | **headers** | `Record<string, string>` | optional | HTTP headers |
 | **timeoutMs** | `integer` | optional (default: `10000`) | Exporter request timeout in milliseconds |
-| **timeout** | `never` | optional | [REMOVED] `OpenTelemetryCompatibility.exporter.timeout` was renamed to `timeoutMs` in @objectstack/spec 18 — the unit of a duration-shaped number lives in the key name, not only in the describe prose. Its unit (milliseconds) lived in a source JSDoc only and the key carried no describe at all, so the reference-page reader got a bare 10000 and could not tell it from 10000 seconds. Rename the key to `timeoutMs`; the value (milliseconds) and the 10000 default are unchanged. |
+| **timeout** | `never` | optional | [REMOVED] `OpenTelemetryCompatibility.exporter.timeout` was renamed to `timeoutMs` in @objectstack/spec 17 — the unit of a duration-shaped number lives in the key name, not only in the describe prose. Its unit (milliseconds) lived in a source JSDoc only and the key carried no describe at all, so the reference-page reader got a bare 10000 and could not tell it from 10000 seconds. Rename the key to `timeoutMs`; the value (milliseconds) and the 10000 default are unchanged. |
 | **compression** | `Enum<'none' \| 'gzip'>` | optional (default: `"none"`) |  |
 | **batch** | `{ maxBatchSize: integer; maxQueueSize: integer; exportTimeoutMs: integer; scheduledDelayMs: integer }` | optional |  |
 
@@ -498,7 +498,7 @@ Tracing configuration
 | :--- | :--- | :--- | :--- |
 | **asyncExport** | `boolean` | optional (default: `true`) |  |
 | **exportIntervalMs** | `integer` | optional (default: `5000`) | Background span-export interval in milliseconds |
-| **exportInterval** | `never` | optional | [REMOVED] `TracingConfig.performance.exportInterval` was renamed to `exportIntervalMs` in @objectstack/spec 18 — the unit of a duration-shaped number lives in the key name, not only in the describe prose. Its unit (milliseconds) lived in a source JSDoc only and the key carried no describe at all, so the reference-page reader got a bare 5000. Rename the key to `exportIntervalMs`; the value (milliseconds) and the 5000 default are unchanged. |
+| **exportInterval** | `never` | optional | [REMOVED] `TracingConfig.performance.exportInterval` was renamed to `exportIntervalMs` in @objectstack/spec 17 — the unit of a duration-shaped number lives in the key name, not only in the describe prose. Its unit (milliseconds) lived in a source JSDoc only and the key carried no describe at all, so the reference-page reader got a bare 5000. Rename the key to `exportIntervalMs`; the value (milliseconds) and the 5000 default are unchanged. |
 
 
 ---

packages/spec/src/migrations/entries/semantic/18.system-tracing-otel-exporter-durations-unit-in-key.ts

@@ -57,9 +57,10 @@ export const entry: SemanticMigration = {
     + 'system-tracing-span-duration-unit-in-key recorded for the other key on this file. '
     + 'Measured at 98bd7986fe: NO in-repo reader exists outside packages/spec — '
     + 'OpenTelemetryCompatibility, TracingConfig and all three batch key names occur 0 times '
-    + 'across the whole tree at that ref excluding packages/spec and the generated reference '
-    + 'pages, against a lit control of 20875 Schema occurrences on that same corpus and ref '
-    + 'and a dark control of 0; inside packages/spec the '
+    + 'across the whole tree at that ref excluding packages/spec and content/docs/references, '
+    + 'against a lit control of 18920 Schema occurrences on exactly that corpus and ref — both '
+    + 'counts from one git grep -o over 98bd7986fe with those two pathspec exclusions — and a '
+    + 'dark control of 0; inside packages/spec the '
     + 'only occurrences are tracing.zod.ts, its test, and the generated rows in '
     + 'content/docs/references/system/tracing.mdx, which this rename regenerates. And the '
     + 'pinned objectui checkout — `.objectui-sha` = `53ded82bf7a494f54e344e19099dbf00854b8694` — names none of it: all 37 exports of '

packages/spec/src/migrations/registry.ts

@@ -10599,9 +10599,10 @@ const step18: MigrationStep = {
         + 'system-tracing-span-duration-unit-in-key recorded for the other key on this file. '
         + 'Measured at 98bd7986fe: NO in-repo reader exists outside packages/spec — '
         + 'OpenTelemetryCompatibility, TracingConfig and all three batch key names occur 0 times '
-        + 'across the whole tree at that ref excluding packages/spec and the generated reference '
-        + 'pages, against a lit control of 20875 Schema occurrences on that same corpus and ref '
-        + 'and a dark control of 0; inside packages/spec the '
+        + 'across the whole tree at that ref excluding packages/spec and content/docs/references, '
+        + 'against a lit control of 18920 Schema occurrences on exactly that corpus and ref — both '
+        + 'counts from one git grep -o over 98bd7986fe with those two pathspec exclusions — and a '
+        + 'dark control of 0; inside packages/spec the '
         + 'only occurrences are tracing.zod.ts, its test, and the generated rows in '
         + 'content/docs/references/system/tracing.mdx, which this rename regenerates. And the '
         + 'pinned objectui checkout — `.objectui-sha` = `53ded82bf7a494f54e344e19099dbf00854b8694` — names none of it: all 37 exports of '

packages/spec/src/system/tracing.zod.ts

@@ -549,7 +549,7 @@ export const OpenTelemetryCompatibilitySchema = lazySchema(() => z.object({
     /** Tombstone for the rename above (#17785, ruling A on #15939). */
     timeout: retiredKey(
       '`OpenTelemetryCompatibility.exporter.timeout` was renamed to `timeoutMs` in '
-      + '@objectstack/spec 18 — the unit of a duration-shaped number lives in the key name, '
+      + '@objectstack/spec 17 — the unit of a duration-shaped number lives in the key name, '
       + 'not only in the describe prose. Its unit (milliseconds) lived in a source JSDoc '
       + 'only and the key carried no describe at all, so the reference-page reader got a '
       + 'bare 10000 and could not tell it from 10000 seconds. Rename the key to `timeoutMs`; '
@@ -600,15 +600,15 @@ export const OpenTelemetryCompatibilitySchema = lazySchema(() => z.object({
       /** Tombstones for the two renames above (#17785, ruling A on #15939). */
       exportTimeout: retiredKey(
         '`OpenTelemetryCompatibility.exporter.batch.exportTimeout` was renamed to '
-        + '`exportTimeoutMs` in @objectstack/spec 18 — the unit of a duration-shaped number '
+        + '`exportTimeoutMs` in @objectstack/spec 17 — the unit of a duration-shaped number '
         + 'lives in the key name, not only in the describe prose. Its unit (milliseconds) '
         + 'lived in a source JSDoc only and the key carried no describe at all, so the '
         + 'reference-page reader got a bare 30000. Rename the key to `exportTimeoutMs`; the '
         + 'value (milliseconds) and the 30000 default are unchanged.',
       ),
       scheduledDelay: retiredKey(
         '`OpenTelemetryCompatibility.exporter.batch.scheduledDelay` was renamed to '
-        + '`scheduledDelayMs` in @objectstack/spec 18 — the unit of a duration-shaped number '
+        + '`scheduledDelayMs` in @objectstack/spec 17 — the unit of a duration-shaped number '
         + 'lives in the key name, not only in the describe prose. Its unit (milliseconds) '
         + 'lived in a source JSDoc only and the key carried no describe at all, so the '
         + 'reference-page reader got a bare 5000. Rename the key to `scheduledDelayMs`; the '
@@ -777,7 +777,7 @@ export const TracingConfigSchema = lazySchema(() => z.object({
     /** Tombstone for the rename above (#17785, ruling A on #15939). */
     exportInterval: retiredKey(
       '`TracingConfig.performance.exportInterval` was renamed to `exportIntervalMs` in '
-      + '@objectstack/spec 18 — the unit of a duration-shaped number lives in the key name, '
+      + '@objectstack/spec 17 — the unit of a duration-shaped number lives in the key name, '
       + 'not only in the describe prose. Its unit (milliseconds) lived in a source JSDoc '
       + 'only and the key carried no describe at all, so the reference-page reader got a '
       + 'bare 5000. Rename the key to `exportIntervalMs`; the value (milliseconds) and the '