fix(spec): the cursor-retirement upgrade entry names the served /api/v1 runs path

Patch round 1 on the AutomationApiContracts path fix:

- The ADR-0087 D3 entry automation-runs-cursor-retired named
  GET /api/automation/:name/runs three times; it now names
  GET /api/v1/automation/:name/runs, the path the contract publishes
  and the dispatcher mounts. registry.ts regenerated with
  gen:migration-registry; gen:upgrade-guide and gen:spec-changes
  re-run with no byte change (the entry is in step 18).
- Two comments (runtime query-param.ts, service-automation
  run-list-truncation.test.ts) quote the same path in the v1 form.
- The changeset declares Clause-② no: no key added, no accept set
  widened, no export grown. The level stays minor.

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

Author: claude

.changeset/20034-automation-contract-api-v1-paths.md

@@ -6,7 +6,7 @@
 
 The dispatcher mounts the automation door at its `prefix` plus `/automation`, the prefix defaults to `/api/v1`, and `objectstack serve` passes none. So all nine declared paths answered `404 ENDPOINT_NOT_FOUND` on the default composition while the same requests under `/api/v1/automation` answered `200`, and the generated API reference printed the nine unserved paths as the endpoints. Every other `*ApiContracts` map in `@objectstack/spec/api` already carried `/api/v1`; this one was the only outlier. The runtime is unchanged — only the declaration moves.
 
-Clause-②: yes
+Clause-②: no
 
 **What moved on the published surface**
 

packages/runtime/src/query-param.ts

@@ -176,7 +176,7 @@ export function parseIntegerParam(
 
 /**
  * A CLOSED-SET parameter — a filter whose declared values are an enum on the
- * wire (`?status=failed` on `GET /api/automation/:name/runs`, whose
+ * wire (`?status=failed` on `GET /api/v1/automation/:name/runs`, whose
  * `ListRunsRequestSchema` bounds it to `ExecutionStatus` itself — the enum
  * rather than a copy of its members, so the bound is whatever that vocabulary
  * declares rather than a count fixed on the day this line was written. #7359

packages/services/service-automation/src/run-list-truncation.test.ts

@@ -3,7 +3,7 @@
 /**
  * #19543 — `AutomationEngine.listRunsPage` and the truncation boundary.
  *
- * `GET /api/automation/:name/runs` used to answer `{ runs, hasMore: false }`
+ * `GET /api/v1/automation/:name/runs` used to answer `{ runs, hasMore: false }`
  * with the `false` written as a literal, beside a list the engine had already
  * cut with `.slice(0, limit)`. A caller asking for one row of a thousand was
  * handed one row and told that was all of them, with a `200` and nothing in

packages/spec/src/migrations/entries/semantic/18.automation-runs-cursor-retired.ts

@@ -8,7 +8,7 @@ export const entry: SemanticMigration = {
   // code span AND a table cell.
   surface:
     'api.listRuns cursor — the pagination query parameter of '
-    + 'GET /api/automation/:name/runs declared by ListRunsRequestSchema, its slot on '
+    + 'GET /api/v1/automation/:name/runs declared by ListRunsRequestSchema, its slot on '
     + 'IAutomationService.listRuns, and its option on all three @objectstack/client run-list '
     + 'surfaces (automation.runs.list, automation.listRuns, environment().automation.listRuns). '
     + 'The limit parameter of the same door is NOT part of this retirement and is unchanged, '
@@ -40,7 +40,7 @@ export const entry: SemanticMigration = {
     + "the Console's flow-runs page sends it today. Retiring it would have been a "
     + 'regression, and its `.default(20)` stays with it. '
     + 'The same card computes `hasMore`, which is the half a bare retirement would have left '
-    + 'lying. `GET /api/automation/:name/runs` shipped a literal `hasMore: false` beside a '
+    + 'lying. `GET /api/v1/automation/:name/runs` shipped a literal `hasMore: false` beside a '
     + 'list the engine had already truncated with `.slice(0, limit)`, so a caller asking for '
     + 'one row of a thousand was handed one row and told that was all of them. The engine '
     + 'now reports truncation to the door through a new optional contract member, '
@@ -69,7 +69,7 @@ export const entry: SemanticMigration = {
     + '#6361 retired the notifications `cursor`: the client dropped the option and recorded '
     + 'the removal in its docblock. ADR-0049 / ADR-0087, #19543.',
   acceptanceCriteria:
-    'No caller sends `cursor` to `GET /api/automation/:name/runs`, and that is true of every '
+    'No caller sends `cursor` to `GET /api/v1/automation/:name/runs`, and that is true of every '
     + 'channel this repo ships rather than of the schema alone. Writing it on a '
     + '`ListRunsRequest` is a `tsc` error (the input type is `never`), and any value reaching a '
     + 'parse raises the prescription rather than a generic unrecognized-key issue. The option is '

packages/spec/src/migrations/registry.ts

@@ -5940,7 +5940,7 @@ const step18: MigrationStep = {
       // code span AND a table cell.
       surface:
         'api.listRuns cursor — the pagination query parameter of '
-        + 'GET /api/automation/:name/runs declared by ListRunsRequestSchema, its slot on '
+        + 'GET /api/v1/automation/:name/runs declared by ListRunsRequestSchema, its slot on '
         + 'IAutomationService.listRuns, and its option on all three @objectstack/client run-list '
         + 'surfaces (automation.runs.list, automation.listRuns, environment().automation.listRuns). '
         + 'The limit parameter of the same door is NOT part of this retirement and is unchanged, '
@@ -5972,7 +5972,7 @@ const step18: MigrationStep = {
         + "the Console's flow-runs page sends it today. Retiring it would have been a "
         + 'regression, and its `.default(20)` stays with it. '
         + 'The same card computes `hasMore`, which is the half a bare retirement would have left '
-        + 'lying. `GET /api/automation/:name/runs` shipped a literal `hasMore: false` beside a '
+        + 'lying. `GET /api/v1/automation/:name/runs` shipped a literal `hasMore: false` beside a '
         + 'list the engine had already truncated with `.slice(0, limit)`, so a caller asking for '
         + 'one row of a thousand was handed one row and told that was all of them. The engine '
         + 'now reports truncation to the door through a new optional contract member, '
@@ -6001,7 +6001,7 @@ const step18: MigrationStep = {
         + '#6361 retired the notifications `cursor`: the client dropped the option and recorded '
         + 'the removal in its docblock. ADR-0049 / ADR-0087, #19543.',
       acceptanceCriteria:
-        'No caller sends `cursor` to `GET /api/automation/:name/runs`, and that is true of every '
+        'No caller sends `cursor` to `GET /api/v1/automation/:name/runs`, and that is true of every '
         + 'channel this repo ships rather than of the schema alone. Writing it on a '
         + '`ListRunsRequest` is a `tsc` error (the input type is `never`), and any value reaching a '
         + 'parse raises the prescription rather than a generic unrecognized-key issue. The option is '