rest: the served OpenAPI document's info block comes from api.documentation (9 keys) #20294

Activity

1. objectstack-fleet

   added

   pm:blocked

   and removed

   needs-user-decision

   on Sep 28, 2026
2. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetBot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   Transition: needs-user-decision → pm:blocked · Blocked-by: #20359 added to the body · 2026-09-28T02:45Z

   domain:spec seat 1 (session_01Rjy9MeetSfq34PKn81CRiN). At the maintainer's request in chat (「看不懂，开决裁卡」), the question in the Release: comment above now has its own decision card, #20359, written for a plain read. This card waits on it, and re-dispatches on its answer from the dev's kept resume plan (A), as eight ENFORCE plus one RETIRE (B), or as a RETIRE re-grade (C).
3. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetBot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   Unblocked: #20359 ruled B (batch #231 item 1, 5862477514) · pm:blocked → pm:queue · 2026-09-28T03:01Z

   Director seat (objectstack#12708, summon #30 续 2, session_01AsCNgFBs8HCjwhyHQsFbx3). The maintainer's word on #20359: 「同意 B」. This card's Blocked-by: #20359 is resolved by that ruling; the body line is replaced in the same stroke.

   Re-dispatch on the dev's kept worktree and resume plan as the seat's own B:

   • Eight api.documentation keys ENFORCE — title, description, termsOfService, contact.*, license.*: an authored value overlays the served info on both doors; nothing authored ⇒ byte-identical to the artifact; title becomes .optional(); contact / license replace whole.
   • documentation.version RETIRE — retiredKey() tombstone; the served info.version stays SPEC_VERSION per [finding] the served openapi.json overrides the info.version that packages/spec owns, so the published artifact says 17.2.0 and the served document says v1 #11646 (5405070350); ADR-0087 D3 entry.
   • Full parameters and the four pins are on the ruling. Clause-② yes, CONTRACT_REVIEW_TIER; @objectstack/spec minor. The landing PR closes [Decision] May an app owner put their own title, description, version, contact and license on the API document ObjectStack serves (/openapi.json)? #20359 too.
4. objectstack-fleet

   added

   pm:queue

   and removed

   pm:blocked

   on Sep 28, 2026
5. akarma-synetal

   added a commit that references this issue on Sep 28, 2026

   feat(spec,rest)!: retire api.responseFormat and api.documentation.ena…

   ...

   26daf0b
6. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetBot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   Claim: PM loop round 3
   Session: session_01ARcDurZ5j34RdqsGgc4jgH
   Account: os-warren (the seat's linked user as GET /user answers it; the card's assignee)
   Branch: claude/issue-20294-openapi-info-overlay
   Worktree: objectstack-issue-20294
   Domain: domain:spec
   Seat: domain:spec#4 (seat post #18917)
   File surface: a vertical dispatch (ruling A′ ② on #18900), with both ends declared. It executes ruling B on #20359 (5862477514).

   • packages/rest/src/rest-server.ts (domain:cli, the cross-lane surface): ONLY the registerOpenApiEndpoints region (a pure overlay helper plus the handler line that uses it, on both doors, and the [finding] the served openapi.json overrides the info.version that packages/spec owns, so the published artifact says 17.2.0 and the served document says v1 #11646 comment there). Plus its tests in packages/rest/src/.
   • packages/spec/src/api/rest-server.zod.ts: documentation.title → .optional(), a retiredKey() tombstone on documentation.version, and the describes of the eight enforced members. Plus regenerated JSON schema and reference docs.
   • The ADR-0087 D3 entry for api.documentation.version, and whatever the spec-property-retirement route requires with it: the retired-key entry, registry.ts and the step-18 lists, regenerated where a tool generates them. The precedent is spec(api): retire api.responseFormat and api.documentation.enabled (4 keys); the envelope is fixed and enableOpenApi already decides the document #20295's documentation.enabled (PR feat(spec,rest)!: retire api.responseFormat and api.documentation.enabled (ADR-0049) #20343, 26daf0b0).
   • packages/spec/liveness/rest_api.json: the eight rows (and the two container rows) → live, and the version row retires with the key. Plus state-counts.md from gen:liveness-counts, and the README row.
   • The two pins that assert the materialized 'ObjectStack API' default flip. The [finding] the served openapi.json overrides the info.version that packages/spec owns, so the published artifact says 17.2.0 and the served document says v1 #11646 whole-block pin in rest-openapi-route.test.ts stays as the unset control.
   • .changeset/: @objectstack/spec minor, and @objectstack/rest per its bump policy.
   • ⛔ Not build-openapi.ts (the artifact stays the default source). ⛔ api.version and the runtime version never enter info.version. ⛔ No other rest-server.ts region. ⛔ Not packages/runtime: [finding] the runtime dispatcher's /packages domain takes the organization from the raw session claim (resolveActiveOrganizationId, 9 sites), bypassing ruling B on #15409: a session naming a left organization may read and write it #20477's claim holds http-dispatcher.ts.
     (stop on breach; explain in the report)
     Container & model: M, mode:subagent, model: default judgment tier (no path-derived mandate). Clause-②: yes per the ruling, so an at-tier contract review at CONTRACT_REVIEW_TIER is owed before enqueue.
     Clause-②: yes
     Thread-read: 5862495365
     Serial constraints cleared: read at 2026-09-28T18:45Z on origin/main fc0db22b.
   • Of the 9 open PRs, none touches rest-server.ts, rest-server.zod.ts, rest_api.json or rest-openapi-route.test.ts. PR feat(spec)!: retire the inner name on cube measures and dimensions — the record key is the member's name (#20300) #20458 (spec(analytics): retire the inner name on cube measures and dimensions; the record key is the identity (2 keys) #20300, seat 1) edits packages/spec/liveness/README.md, and PRs feat(spec)!: retire the inner name on cube measures and dimensions — the record key is the member's name (#20300) #20458 / feat(spec,cli)!: one stack authoring shape — os validate / os build refuse a default export defineStack did not build #20460 / fix(spec): reword the CurrencyConfigSchema.precision clause in two major-18 D3 entries #20488 edit migrations/registry.ts. Both are ordinary concurrency: regenerate on merge, and edit the README's hand-written row after merging main.
   • [finding] the runtime dispatcher's /packages domain takes the organization from the raw session claim (resolveActiveOrganizationId, 9 sites), bypassing ruling B on #15409: a session naming a left organization may read and write it #20477 (domain:cli, p0) holds packages/runtime/src/http-dispatcher.ts and reads packages/rest/** only.
   • The last rest-server.ts change on main is 5c7aa467 (fix(rest, runtime): the dispatcher's /meta doors scope to the vetted organization, and its item read, book tree and list answer what RestServer answers (#20408) #20473), in the /meta doors, a different region.
   • area:api's other in-flight cards, objectql: refuse a non-numeric string compared against a number field at the engine's field-aware filter door (400, every driver and position) — the door half of #20336 #20351 (packages/objectql) and this seat's [finding] once PR #20218 lands, PackageInstallBodySchema's published docblock still says the install door answers 201 to residual classes 1b, 2, 3 and 4, which it then refuses 400 #20219 (package-api.zod.ts, prose), have disjoint file surfaces.
   • Seat 1's earlier dev kept a worktree and resume plan (5862210322) in seat 1's own container, which this seat cannot reach. The resume plan is carried as text, and the dev rebuilds from origin/main.

   Ruling carried: 5862477514 · #20359 · batch #231 item 1 · letter B · maintainer 「同意 B」. The landing PR closes #20359 too, per that ruling.

   _{domain:spec seat 4 · #18917 · session_01ARcDurZ5j34RdqsGgc4jgH}
7. objectstack-fleet

   added

   pm:dispatched

   and removed

   pm:queue

   on Sep 28, 2026
8. objectstack-fleet

   assigned

   os-warren

   on Sep 28, 2026
9. objectstack-fleet commented on Sep 28, 2026

   

   objectstack-fleetBot

   on Sep 28, 2026

   ContributorAuthor

   More actions

   os-dev-report

   {
     "issue": 20294,
     "status": "done",
     "branch": "claude/issue-20294-openapi-info-overlay",
     "pr": "https://github.com/objectstack-ai/objectstack/pull/20512",
     "session": "session_01ARcDurZ5j34RdqsGgc4jgH — the PM's session (mode:subagent); this dev's identity is the branch named by claim 5876330236, the newest Claim on the card (verified before any edit)",
     "premise_still_valid": true,
     "summary": "Ruling B on #20359 executed on draft PR #20512 (head 69b4d203; origin/main 2b24b8b8 merged in through os-regen-merge.sh, no generated path moved). ENFORCE half: RestServer.overlayDocumentationInfo, a pure private static helper directly above registerOpenApiEndpoints, lays the authored title / description / termsOfService and a whole-replaced contact / license over the bundled info. It returns the bundled object itself when nothing is authored (byte-identical, the #11646 control kept unedited) and a NEW object otherwise, never writing into the cached artifact. One handler line applies it before res.json; the same closure serves both doors. RETIRE half: documentation.version is a retiredKey() tombstone whose prescription names the protocol version (spelled as the @objectstack/spec package version, since the in-repo PROTOCOL_VERSION constant 17.0.0 is a different value) and sends an app release number to description. It is registered in RETIRED_KEYS_BY_MAJOR[18] with its own D3 entry rest-api-documentation-version-retired and no D2 conversion. title is .optional(); the ledger moves rest_api from 12 live / 12 dead to 20 / 4; changeset spec+rest minor, Clause-②: yes (narrowing). Premise re-measured at fc0db22b before editing: 0 of 9 honoured on both doors, unset controls byte-identical, served info === cached artifact info. One thing needs the PM: line 2 Fixes #20359 (as ordered) turns the advisory check \"The card this PR closes must claim this branch\" red, because #20359 carries no Claim naming this branch and a dispatched dev may not post one (see open_questions).",
     "mechanism_assumptions": [
       "1 HOLDS — measured at fc0db22b with a scratch vitest (deleted, never committed) driving both openapi.json handlers with project scoping on. All nine authored: served info equals the artifact on both doors, 0 of 9 honoured. Absent, {}, description-only and license-name-only: the served info equals the artifact, and the scoped door equals the unscoped one. sameRefAsCache was true in every case, so the overlay builds a new object; reverse-verified by leg B.",
       "2 HOLDS with one refinement. The route is retiredKey() on the non-strict inline documentation object, following the #20295 documentation.enabled precedent. It owes exactly: the RETIRED_KEYS_BY_MAJOR[18] exact-key entry api/RestApiConfig:documentation.version (retired-keys/18.api__RestApiConfig__documentation.version.ts), one D3 semantic entry per family rest-api-documentation-version-retired (semantic/18.rest-api-documentation-version-retired.ts), registry.ts regenerated by gen:migration-registry, no D2 conversion and so no MIGRATIONS_BY_MAJOR[18].conversionIds entry, and the ledger row kept dead with a REMOVED note. The Clause-② line takes the narrowing arm: Clause-②: yes (narrowing), where yes is the ruling's value and (narrowing) is required because a formerly accepted input is now refused (breakingDeclaration reads that arm). Refinement: the adr-0087 marker lives in the CHANGESET body, not the PR body. check-adr-0087-registration reads it there, as the HTML-comment marker registered rest-api-documentation-version-retired. The PR body carries only the Clause-② line and no marker, since HTML comments are banned on GitHub text.",
       "3 HOLDS. spec rest-api-config-dead-keys-retirement.test.ts (the documentation: {} control, was :172) now asserts {} with no title plus a description-only parse. rest rest-config-parse-not-cast.test.ts §D (was :352) now asserts no title and the block equal to exactly what was authored. Both flipped with the new substance asserted. The pins that authored documentation.version moved to the tombstone: the spec retirement CONTROL block and the two fixtures in packages/spec/src/api/rest-server.test.ts (:138 and the integration fixture). The tsc sweep found no other author, and the extended tree-scoped absence walk found none in packages/examples/skills/content/scripts.",
       "4 NEITHER is class a/b/c; this PR is not widened. (i) The /docs viewer HTML title literal ObjectStack API Docs is the Scalar page browser-tab title, not an info field. The page body renders the served (overlaid) info.title, no declared contract ties the tab to it and no key authors it, so it is polish. (ii) OpenApiGenerationConfigSchema.title third default: 0 non-test readers under packages/** (only migration-entry prose names the schema) against a lit control (RestApiConfigSchema found in rest-server.ts). No runtime parser, no ledger enrolment, no producer, so it is dormant. Both are in the PR Acceptance notes."
     ],
     "tests": "All at HEAD 69b4d203, heavy runs through os-verify-lock.sh, exit codes written to disk before any pipe. rest local: vitest run --project local exit 0, 219 files, 4185 passed, 34 skipped (VERDICT command-exit 0, held 172s). rest repo: exit 0, 1 file, 8 passed. spec local: exit 0, 572 files, 16794 passed, 1 todo (held 195s). spec repo (test:repo): exit 0, 38 files, 697 passed (held 583s; the tree-scoped absence walk runs here). rest typecheck and spec typecheck: both exit 0 (tsc --noEmit + check:test-typecheck; spec also check:scripts-typecheck). check:test-typecheck green proves the new @ts-expect-error pin bites. check:generated exit 0 (all 15 current); check:liveness exit 0. Narrowed eslint --no-inline-config --format json over the 11 changed code files: 11 files, 0 errors, 0 warnings. Population: eslint.config.mjs catch-all files glob; invariance: the config enables no type-aware linting. Pre-restart targeted run at 38a73bb4 (6 files) caught one wrong assertion of mine (the prescription itself names api.documentation.description); fixed in a98ace43 to assert the located-issue line. Reverse verification, one-time, from committed 69b4d203, each mutation through scripts/ablation-replace.mjs (anchor x1 to x0 on disk, blob changed, restore proven blob == HEAD and empty git diff HEAD). Control 11/11 passed. A, the overlay line removed (blob 3f01f03a to 5c7dde2c): 9 failed / 2 passed, the survivors being exactly the nothing-authored controls. B, the helper writes into the cached info via Object.assign (3f01f03a to 662c8f32): 3 failed / 8 passed. C, the tombstone neutralised as version: z.string().optional() ?? retiredKey( (e69191ec to 1acff1f8): spec retirement test 5 failed / 18 passed. D, cross-package type proof: a planted probe in packages/rest/src made rest tsc exit 1 with src/zz-typeproof-20294.ts(3,76): error TS2322 and 0 other errors, so rest reads the rebuilt spec .d.ts; the probe was removed and its absence confirmed. Post: both blobs == HEAD, git status empty. All subjects import source, so no dist preflight applies.",
     "gates": [
       {
         "cmd": "node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack",
         "exit": 0,
         "verdict_line": "115 derived commands; change set 16 paths vs merge base 2b24b8b82; 879 changed lines under the 5000 threshold",
         "tree": "69b4d203"
       },
       {
         "cmd": "node scripts/pm/dispatch-gates.mjs --ran ran2.list --repo objectstack-ai/objectstack",
         "exit": 1,
         "verdict_line": "Run reconciliation — 115 derived, 113 run, 0 NOT-MEASURED, 2 UNRUN. ✗ dispatch-gates --ran: 2 of 115 derived famil(ies) UNRUN.",
         "tree": "69b4d203",
         "note": "the 2 UNRUN are the declared skips below"
       },
       {
         "cmd": "113 derived gate commands (full list and per-command exit codes in the run record)",
         "exit": 0,
         "verdict_line": "112 exit 0, 1 exit 1",
         "tree": "69b4d203"
       },
       {
         "cmd": "pnpm check:platform-checklist",
         "exit": 1,
         "verdict_line": "check-platform-checklist: 1 problem(s) — areas/identity-auth.json: ABSENT SYMBOL — packages/plugins/plugin-auth/src/auth-plugin.ts#twoFactor",
         "tree": "69b4d203",
         "note": "INHERITED from main: 0 diff lines vs origin/main under docs/qa, packages/plugins/plugin-auth and scripts; stale since 7d630889; the gate is outside per-PR CI"
       },
       {
         "cmd": "pnpm --filter @objectstack/spec run check:skill-examples",
         "exit": 0,
         "verdict_line": "259 prose examples type-check across 3 surface(s)",
         "tree": "69b4d203",
         "note": "first run exit 3 PREREQUISITE NOT MET (no client-react .d.ts); rerun after building @objectstack/client + @objectstack/client-react under the lock"
       },
       {
         "cmd": "pnpm check:dual-build-cjs-loads",
         "exit": null,
         "verdict_line": "NOT MEASURED",
         "tree": "69b4d203",
         "note": "reason: reads every package dist/; a whole-tree build is outside this card's local scope (CI Build Core)"
       },
       {
         "cmd": "pnpm check:type-check-debt",
         "exit": null,
         "verdict_line": "NOT MEASURED",
         "tree": "69b4d203",
         "note": "reason: --re-measure rebuilds every package; the diff touches no DEBT/EXEMPT package; check:type-check-coverage ran exit 0"
       },
       {
         "cmd": "pnpm --filter @objectstack/spec check:generated",
         "exit": 0,
         "verdict_line": "✓ All 15 generated artifacts are up to date",
         "tree": "69b4d203"
       },
       {
         "cmd": "pnpm --filter @objectstack/spec check:liveness",
         "exit": 0,
         "verdict_line": "✓ packages/spec/liveness/state-counts.md is current",
         "tree": "69b4d203"
       },
       {
         "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/rest exec vitest run --project local --maxWorkers=2\"",
         "exit": 0,
         "verdict_line": "VERDICT command-exit 0 · held the lock 172s",
         "tree": "69b4d203"
       },
       {
         "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/spec exec vitest run --project local --maxWorkers=2\"",
         "exit": 0,
         "verdict_line": "VERDICT command-exit 0 · held the lock 195s",
         "tree": "69b4d203"
       },
       {
         "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/spec exec vitest run --project repo --maxWorkers=2\"",
         "exit": 0,
         "verdict_line": "VERDICT command-exit 0 · held the lock 583s",
         "tree": "69b4d203"
       },
       {
         "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/rest exec vitest run --project repo --maxWorkers=2\"",
         "exit": 0,
         "verdict_line": "VERDICT command-exit 0 · held the lock 1s",
         "tree": "69b4d203"
       },
       {
         "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/rest run typecheck\"",
         "exit": 0,
         "verdict_line": "VERDICT command-exit 0 · held the lock 25s",
         "tree": "69b4d203"
       },
       {
         "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/spec run typecheck\"",
         "exit": 0,
         "verdict_line": "VERDICT command-exit 0 · held the lock 63s",
         "tree": "69b4d203"
       },
       {
         "cmd": "bash scripts/pm/os-verify-lock.sh -c \"bash ablate.sh\" (legs A-D)",
         "exit": 0,
         "verdict_line": "VERDICT command-exit 0; ABLATION-DONE; every leg red as expected, all restores blob == HEAD",
         "tree": "69b4d203"
       },
       {
         "cmd": "PR #20512 CI at read time (one read, no polling)",
         "exit": null,
         "verdict_line": "32 check runs: 8 success, 2 skipped, 21 in_progress, 1 failure = \"The card this PR closes must claim this branch\" (PR #20512 closes #20359 with no Claim on the card naming this branch)",
         "tree": "69b4d203",
         "note": "advisory, not one of the seven required contexts; see open_questions"
       }
     ],
     "line_budget": "n/a — no skills/** or line-ratcheted ledger touched; diff 16 files, +777 / -102 (879 changed lines) vs the 5000 human-merge threshold: under",
     "files_changed": [
       ".changeset/20294-openapi-info-publisher-overlay.md",
       "content/docs/references/api/rest-server.mdx",
       "packages/rest/src/rest-api-config-dead-keys-refused.test.ts",
       "packages/rest/src/rest-api-config-defaults-follow-spec.pin.test.ts",
       "packages/rest/src/rest-config-parse-not-cast.test.ts",
       "packages/rest/src/rest-openapi-info-overlay.test.ts",
       "packages/rest/src/rest-server.ts",
       "packages/spec/liveness/README.md",
       "packages/spec/liveness/rest_api.json",
       "packages/spec/liveness/state-counts.md",
       "packages/spec/src/api/rest-api-config-dead-keys-retirement.test.ts",
       "packages/spec/src/api/rest-server.test.ts",
       "packages/spec/src/api/rest-server.zod.ts",
       "packages/spec/src/migrations/entries/retired-keys/18.api__RestApiConfig__documentation.version.ts",
       "packages/spec/src/migrations/entries/semantic/18.rest-api-documentation-version-retired.ts",
       "packages/spec/src/migrations/registry.ts"
     ],
     "deviations": [
       "PR body line 2 is Fixes #20359, as the dispatch orders. The advisory check \"The card this PR closes must claim this branch\" (scripts/check-closing-target-claim.mjs) is therefore red on #20512: #20359 has no Claim naming claude/issue-20294-openapi-info-overlay, and a dispatched dev may not post a second claim. The guard re-reads comments live, so a re-run clears it once the thread carries such a Claim. It is not among the seven required contexts.",
       "packages/spec/src/api/rest-server.test.ts is edited: two fixtures dropped documentation.version and one comment was updated. That file is not in the named landing sites; it falls under the dispatch's \"a pin that authors documentation.version today moves to the tombstone\". The tombstone would otherwise fail tsc and parse there.",
       "The rest-server.ts fence was obeyed. Two comments outside the registerOpenApiEndpoints region are now stale and were left unedited: NormalizedRestServerConfig.api.documentation near :1116 (\"inner defaults applied (.title)\") and the parseDeclaredApiConfig #14366 paragraph near :4112 (\"zero read sites\"). Neither is emitted into a published .d.ts. One-line fixes are named in the PR Acceptance notes.",
       "A container restart around 19:43Z killed the first full rest run, whose result was lost. Everything reported was re-run at 69b4d203 after merging origin/main 2b24b8b8 with os-regen-merge.sh. The merge left no conflict and no generated path to regenerate (check:generated all current), then pnpm install --frozen-lockfile and a closure rebuild.",
       "The verify lock queue-timed-out (exit 99) three times behind other seats' long holders (issue-20233 verifyC.sh about 10 min, issue-20289 verify2.sh about 15 min). Each retry used the same OS_VERIFY_LOCK_SLOT=dev-20294, and no heavy run went unlocked. Long waits were spanned by one background lock call plus a foreground tail --pid, never by polling.",
       "Commit trailers are the model-free pair (Claude-Session + Co-authored-by: Claude) per AGENTS.md, not the harness reminder's model-bearing Co-Authored-By. The merge commit is os-regen-merge.sh's own. The PR body footer is the session-URL form AGENTS.md specifies, not the reminder's wording.",
       "check:skill-examples needed @objectstack/client and @objectstack/client-react built (9s under the lock) to leave PREREQUISITE NOT MET."
     ],
     "cleanup": "git status empty at 69b4d203 (== the remote head). /home/user/objectstack-issue-20294/node_modules removed before this report was posted, and the worktree removed with a plain git worktree remove (no --force) right after. No dev server or monitor was started; every background run launched here had exited before the report.",
     "mcp_calls": "0",
     "api_writes": "3 — each one repository_dispatch through the fleet-write relay, executed as objectstack-fleet[bot]: (1) pr_create → POST /repos/objectstack-ai/objectstack/pulls (draft #20512, relay run 36481580438); (2) label-write --assign os-warren → POST /repos/objectstack-ai/objectstack/issues/20512/assignees (relay run 36481673037; read back: assignee os-warren, labels documentation/size/l/tests/tooling untouched); (3) this os-dev-report → POST /repos/objectstack-ai/objectstack/issues/20294/comments via post-stamped.mjs. git push is not a REST write. The REST calls to /issues/20294(+comments), /issues/20359(+comments), /issues/comments/5405070350, /pulls?head=, /pulls/20512 and its check-runs / annotations were GETs.",
     "open_questions": [
       {
         "question": "Closing-target claim guard vs line 2 of the PR body: PR #20512 says Fixes #20359 (ordered by the dispatch, and the ruling says the landing PR closes #20359). The advisory guard is red because #20359 has no Claim naming claude/issue-20294-openapi-info-overlay. How should it clear?",
         "options": [
           "A — The PM posts a Claim on #20359 naming claude/issue-20294-openapi-info-overlay (it is the ruling carrier, so a claim-for-closure only), then re-runs the guard job. No PR edit is needed.",
           "B — The PM edits the PR body so line 2 reads Part of #20359, and closes #20359 by hand after the merge. The body is edited once, by the seat.",
           "C — Leave it red. It is advisory, outside the seven required contexts, and the queue ignores it."
         ],
         "recommendation": "A, because it keeps the ruled closure mechanical. The guard exists to prove that the closer owns the card, and a single claim line records that ownership without a body rewrite, which by protocol only the seat may make."
       }
     ],
     "out_of_scope_findings": [
       "class: a · reach: named producer — commit 7d630889 (#20429) rewrote plugin-auth auth-plugin.ts so twoFactor is now only an inline plugins: { twoFactor: true } key. On origin/main 2b24b8b8, pnpm check:platform-checklist exits 1: \"areas/identity-auth.json: ABSENT SYMBOL — packages/plugins/plugin-auth/src/auth-plugin.ts#twoFactor\". This diff has 0 lines under docs/qa, packages/plugins/plugin-auth and scripts. The gate is outside per-PR CI, so the red is silent until someone runs it. Dedupe words: identity-auth twoFactor anchor, ABSENT SYMBOL auth-plugin.ts, check:platform-checklist red",
       "carrier: 承接者:无 · noted, not filed — /docs viewer HTML title literal ObjectStack API Docs (rest-server.ts registerOpenApiEndpoints, the /docs handler). Polish, not an info field (in the PR Acceptance notes). Dedupe words: ObjectStack API Docs, /docs viewer title, Scalar tab title",
       "carrier: 承接者:无 · noted, not filed — OpenApiGenerationConfigSchema.title third default ObjectStack API (packages/spec/src/api/plugin-rest-api.zod.ts). Dormant: 0 non-test readers against a lit control. Dedupe words: OpenApiGenerationConfigSchema title, plugin-rest-api openApi title default",
       "carrier: whoever next touches the rest-server.ts normalizeConfig / NormalizedRestServerConfig regions · noted, not filed — two comments there are now stale (see deviations). One-line fixes are in the PR Acceptance notes."
     ]
   }

   ---

   Generated by Claude Code
10. objectstack-fleet commented on Sep 28, 2026

    

    objectstack-fleetBot

    on Sep 28, 2026

    ContributorAuthor

    More actions

    os-dev-report

    {
      "issue": 20294,
      "status": "done",
      "round": "merge-only (sync with main + regenerate), requested after at-tier record 5878749194 PASSed at 69b4d203",
      "branch": "claude/issue-20294-openapi-info-overlay",
      "pr": "https://github.com/objectstack-ai/objectstack/pull/20512",
      "session": "session_01ARcDurZ5j34RdqsGgc4jgH — the PM's session (mode:subagent); identity = the branch named by claim 5876330236",
      "premise_still_valid": true,
      "new_head": "8e26fbbe887a339ca71d602db5dc46171281a2e2",
      "previous_head": "69b4d20391b1b2170d3b1c482859b81d0887647c",
      "merge_commit": "0945eb2169846a457ca35ef7b17e7df79ea95d2c (parents 69b4d203 + origin/main 0bbe4005)",
      "regeneration_commit": "8e26fbbe88 chore(spec): regenerate liveness state-counts on the merged tree",
      "regenerated_paths": [
        "packages/spec/liveness/state-counts.md (pnpm --filter @objectstack/spec gen:liveness-counts)"
      ],
      "resolved_by_hand": "nothing. git merge auto-committed 0945eb21 with no conflict on any path. os-regen-merge.sh step 2 took main's side of the one os-regen path both sides changed, state-counts.md, and its step-3 commit was refused by pre-commit as designed (\"1 generated artifact merged WITHOUT a text merge\"). I cleared that refusal by regenerating the file with gen:liveness-counts, then git add -A and commit. No hunk was hand-edited, and there was no rebase and no force-push.",
      "summary": "Worktree re-created at the remote head 69b4d203 (local == remote). origin/main 0bbe4005 (#20511 landed) was merged with scripts/pm/os-regen-merge.sh. The one generated path both sides touched was regenerated on the merged tree, then pushed with a plain git push. Nothing outside the regenerated path moved. git diff origin/main..HEAD is the same 16 files, +777 / -102, as the pre-merge delta 2b24b8b8..69b4d203. Per file the changed-line set is identical for 15 of 16; state-counts.md differs only in its generated totals row, 941/147 to 949/139 instead of 940/148 to 948/140, because main moved qa from 8/1 to 9/0. state-counts.md carries both rows: `qa` 9 | 0 | 0 | 0 | 0 | 9 (#20511) and `rest_api` 20 | 0 | 0 | 4 | 0 | 24 (this PR). The hand-written README rest_api row survived (the \"Live 20 =\" and \"documentation.version tombstone (RETIRED 2026-09-28\" sentences each grep 1). registry.ts carries both of this PR's entries (2 hits) and passes its check. PR body not edited: no line in it is made false by the merge; its measurements are stated at 69b4d203.",
      "gates": [
        {
          "cmd": "pnpm --filter @objectstack/spec check:generated",
          "exit": 0,
          "verdict_line": "✓ All 15 generated artifacts are up to date — measured against packages/spec/dist AS FOUND ON DISK",
          "tree": "8e26fbbe",
          "note": "dist rebuilt first: pnpm install --frozen-lockfile (the merge moved pnpm-lock.yaml), then pnpm --workspace-concurrency=2 --filter '@objectstack/rest^...' build under the lock, VERDICT command-exit 0 · held the lock 127s"
        },
        {
          "cmd": "pnpm --filter @objectstack/spec check:liveness",
          "exit": 0,
          "verdict_line": "✓ packages/spec/liveness/state-counts.md is current — the same 40 row(s), no count column left in the README.",
          "tree": "8e26fbbe"
        },
        {
          "cmd": "pnpm --filter @objectstack/spec check:migration-registry",
          "exit": 0,
          "verdict_line": "✓ src/migrations/registry.ts is current (313 semantic, 232 retired-key, 206 retired-def)",
          "tree": "8e26fbbe"
        },
        {
          "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/spec exec vitest run --project repo --maxWorkers=2\"",
          "exit": 0,
          "verdict_line": "Test Files 39 passed (39) · Tests 701 passed (701) · VERDICT command-exit 0 · held the lock 486s",
          "tree": "8e26fbbe"
        },
        {
          "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/rest exec vitest run --project local --maxWorkers=2\"",
          "exit": 0,
          "verdict_line": "Test Files 220 passed (220) · Tests 4189 passed | 40 skipped (4229) · VERDICT command-exit 0 · held the lock 188s",
          "tree": "8e26fbbe",
          "note": "the first attempt was queue-timeout exit 99 behind another seat's holder; retried on the same OS_VERIFY_LOCK_SLOT"
        }
      ],
      "files_changed": [
        "packages/spec/liveness/state-counts.md (regeneration commit only; the merge commit brings main's own files)"
      ],
      "deviations": [],
      "mcp_calls": "0",
      "api_writes": "1 — this os-dev-report: POST /repos/objectstack-ai/objectstack/issues/20294/comments via post-stamped.mjs through the fleet-write relay. The only other write is git push 69b4d203..8e26fbbe (not REST). No PR body edit.",
      "cleanup": "worktree /home/user/objectstack-issue-20294: node_modules removed before this post, then removed with a plain git worktree remove.",
      "open_questions": [],
      "out_of_scope_findings": []
    }

    ---

    Generated by Claude Code
11. objectstack-fleet commented on Sep 28, 2026

    

    objectstack-fleetBot

    on Sep 28, 2026

    ContributorAuthor

    More actions

    Review: ACCEPT · PR #20512 at head 8e26fbbe887a339ca71d602db5dc46171281a2e2 · 2026-09-28T22:41Z

    domain:spec seat 4 (session_01ARcDurZ5j34RdqsGgc4jgH), reviewer of record under claim 5876330236, with the closure claim 5878320739 on #20359. This seat took the readings below on GitHub or on the tree.

    check	reading
    Shape	Base main. Body line 1 Fixes #20294, line 2 Fixes #20359 (the ruling orders this PR to close its carrier), and Clause-②: yes (narrowing) stands alone. The closing-target claim guard is green, with the closure claim on #20359 naming this branch.
    Scope	16 files: ruling B (5862477514) on both halves. ENFORCE: eight api.documentation identity members overlay the served info on both doors, contact / license replace whole, title becomes .optional(), and nothing authored ⇒ the artifact's info, byte-identical. RETIRE: documentation.version is a retiredKey() tombstone with the RETIRED_KEYS_BY_MAJOR[18] key and a D3 entry, and the served info.version stays SPEC_VERSION. Ledger rest_api 12/12 → 20/4. Changesets: spec and rest minor with the BREAKING banner.
    Contract review	At-tier record PASS 5878749194 at 69b4d203. It verifies every ruled parameter and the four pins per door, and the cache discipline: the overlay returns the bundled object when nothing is authored, otherwise a new object, and never writes into the cached artifact; ablation leg B's 3 red were read off the assertions. The tombstone message is true of the served value, since info.version is pkg.version of @objectstack/spec, a different number from PROTOCOL_VERSION. The retirement route matches the documentation.enabled precedent.
    Head moved since the record	One pure-regeneration hop, 69b4d203 → 8e26fbbe: the merge of origin/main 0bbe4005 (#20511) through os-regen-merge.sh, plus gen:liveness-counts on the merged tree. Nothing was hand-resolved. Regen-provenance: 5879799287 carries the record forward. This seat checked the committed trees: 15 of 16 files have an identical changed-line set, and state-counts.md differs only in its generated totals row, by #20511's qa 8/1 → 9/0. The dev re-ran spec test:repo (701 passed) and the rest suite (4189 passed) at 8e26fbbe.
    CI at this head	33 success, 2 skipped, both on the roster (check-expected-skips.mjs --pr 20512, exit 0). mergeable_state: clean. git merge-tree against origin/main 0bbe4005 is clean.
    Governed / size	Not governed (check-governed-merges.mjs --pr 20512: 0 of 16 paths), 879 changed lines.

    Out-of-scope findings:

    • Two stale comments in rest-server.ts outside the fenced region (NormalizedRestServerConfig.api.documentation near :1116, the parseDeclaredApiConfig paragraph near :4112). The record corrects the dev: the :4112 JSDoc most likely ships on a private stub in @objectstack/rest's .d.ts. Both are prose with nil reach, and not an a/b/c finding. Carrier: this seat's next dispatch that touches rest-server.ts, as two one-line comment fixes named in its order.
    • The /docs viewer's literal HTML title, and OpenApiGenerationConfigSchema.title's dormant third default → Acceptance notes, not a/b/c, no carrier owed.
    • check:platform-checklist red on main → carrier [finding] check:platform-checklist is red on main: identity-auth.json anchors auth-plugin.ts#twoFactor, which #20429 turned into an inline nested key #20464.

    Landing next: ready + auto-merge through the relay. At MERGED, the Fixes lines close #20294 and #20359.

    _{domain:spec seat 4 · #18917 · session_01ARcDurZ5j34RdqsGgc4jgH}
12. objectstack-fleet

    closed this as completedin #20512on Sep 28, 2026
13. objectstack-fleet commented on Sep 28, 2026

    

    objectstack-fleetBot

    on Sep 28, 2026

    ContributorAuthor

    More actions

    Landed: PR #20512 → main 80153f5a4a9c641e78b21cd84a35069a84192a96 · 2026-09-28T23:06Z

    domain:spec seat 4 (session_01ARcDurZ5j34RdqsGgc4jgH), landing record for claim 5876330236. ACCEPT 5880040657 at 8e26fbbe, on the at-tier PASS 5878749194 carried over one pure-regeneration hop by Regen-provenance: 5879799287. Merged through the merge queue.

    Verified on origin/main:

    • 80153f5a has one parent, 9e1689f8, and is an ancestor of origin/main.
    • Its diff against that parent is 16 files, +777/−102, the same as the PR.
    • Content controls, parent → merge: overlayDocumentationInfo in packages/rest/src/rest-server.ts 0 → 3; the retired-key entry 18.api__RestApiConfig__documentation.version.ts is present. state-counts.md reads rest_api 20 live / 4 dead / 24, beside feat(spec,core,cli)!: a scenario's requires is checked before it runs — unmet params or services skip it with a reason; requires.plugins retires into requires.services #20511's qa row.
    • No queue branch for feat(spec,rest)!: the served OpenAPI info carries the publisher's api.documentation identity; api.documentation.version retired #20512 remains.

    Close-out: the PR's Fixes lines closed this card and #20359 completed, as ruling B ordered. pm:dispatched comes off both in this act. Ruling 5862477514 is executed: the eight identity members are honoured on both OpenAPI doors, and documentation.version is retired, with info.version staying SPEC_VERSION. Carried from the ACCEPT: two stale rest-server.ts comments ride this seat's next dispatch that touches that file.

    _{domain:spec seat 4 · #18917 · session_01ARcDurZ5j34RdqsGgc4jgH}
14. objectstack-fleet

    removed

    pm:dispatched

    on Sep 28, 2026
15. veigajoao

    added a commit that references this issue on Sep 29, 2026

    feat(spec,rest)!: the served OpenAPI info carries the publisher's api…

    ...

    This issue will close once commit 80153f5 is merged into the 'main' branch.

    80153f5
16. akarma-synetal

    added a commit that references this issue on Oct 7, 2026

    test(spec): the second api/ file group's test titles state each cited…

    ...

    dcf3eb4