fix(spec): the platform-global entry's printed guidance names no tracker id (ADR-0131 D7)

The step-18 D3 entry's reason said the declaration by its tracker number;
os migrate meta prints that field, and author-shown guidance carries none.
The step rationale fragment says it the same way.

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

Author: claude

packages/spec/src/migrations/entries/semantic/18.platform-global-object-organization-column-retired.ts

@@ -29,7 +29,7 @@ export const entry: SemanticMigration = {
   reason:
     'ADR-0131 D7: "an object a deployment declares platform-global gets no organization column on that '
     + 'deployment (the injected-columns plan reads the declaration), so Layer 0 and the driver agree by '
-    + 'having nothing to scope". The #12699 declaration used to stand the security layer\'s organization '
+    + 'having nothing to scope". Before this, the declaration stood the security layer\'s organization '
     + 'wall down for the object while the column stayed, so the SQL driver went on scoping a read by the '
     + 'caller organization that the wall had stopped scoping — measured on a booted kernel with a fixture '
     + 'provider, before the change. ADR-0131 retires that stand-down ("replaced by D7\'s no-column"). The '

packages/spec/src/migrations/registry.ts

@@ -6185,7 +6185,7 @@ const STEP18_RATIONALE: readonly RationaleFragment[] = [
     id: 'platform-global-object-organization-column-retired',
     order: 89,
     text:
-      'It also makes the #12699 deployment declaration total (ADR-0131 D7): an object a deployment '
+      'It also makes the deployment\'s platform-global declaration total (ADR-0131 D7): an object a deployment '
       + 'declares platform-global in its `org-scoping` service\'s `platformGlobalObjects` gets no '
       + 'organization column on that deployment, because the injected-columns plan reads the declaration, '
       + 'so the organization wall and the driver agree by having nothing to scope. The engine reads it at '
@@ -17041,7 +17041,7 @@ const step18: MigrationStep = {
       reason:
         'ADR-0131 D7: "an object a deployment declares platform-global gets no organization column on that '
         + 'deployment (the injected-columns plan reads the declaration), so Layer 0 and the driver agree by '
-        + 'having nothing to scope". The #12699 declaration used to stand the security layer\'s organization '
+        + 'having nothing to scope". Before this, the declaration stood the security layer\'s organization '
         + 'wall down for the object while the column stayed, so the SQL driver went on scoping a read by the '
         + 'caller organization that the wall had stopped scoping — measured on a booted kernel with a fixture '
         + 'provider, before the change. ADR-0131 retires that stand-down ("replaced by D7\'s no-column"). The '