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

[objectstack-fleet]

Filing gate: ① a declared≠enforced family, filed as one sweep card per family under ruling A′ item ④ on #18900 (5727134555). This is triage's standing request 5857165909 on the seat post. Family rest-api-documentation, seat verdict ENFORCE.

• reach: the declared authoring door. packages/spec parses these keys and publishes them in the reference docs. The liveness ledger rows cited below record them as not enforced, and the census re-measured the reader side (§5 cross-checks, each with a lit control).
• The criterion is the maintainer's: 「每族该问的是:主流平台有没有这个能力 —— 有 ⇒ 补消费端(一次做对);没有 ⇒ 退役,而不是看仓里有没有人读」.
• The maintainer's one word, per ruling A′ ④: ENFORCE (the seat's proposal: the mainstream has it, so build the consumer once, correctly) or RETIRE (retire the keys together with their ledger rows).

Census by the domain:spec execution seat 1 (session_01Rjy9MeetSfq34PKn81CRiN, seat post #6017), 2026-09-27. Bases: objectstack a9fb83ef, re-checked against 4d7e740d, where no ledger file or cited surface moved; objectui 6fa5f64a1 (pin f8a9d0fb); cloud 96eb092. Ledger instrument: check-liveness.mts --json, whose byStatus equals the committed state-counts.md row for row. ⛔ Filed bare: routing and grading belong to triage. ⛔ Not a claim. The ranking is by value, user-visible risk × keys. This family's rank is 8 of 16. The sibling family cards filed so far are #20273, #20274, #20281, #20282, #20287, #20288 and #20289. Ranks 8 and 9 are the two halves of rest_api: one ENFORCE, one RETIRE.

Capability: API documentation metadata (title, description, version, terms, contact, license) in the served API description

key	ledger status	ledger row	what the ledger cites
rest_api.documentation.title	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:115	note: Normalized by RestServer and read by NOTHING — the ADR-0049 fourth state (parsed, unmarked, unenforced). normalizeConfig lists documentation: api.documentation straight into this.config.api and no site ever reads it back. `api.documentation.title: '…
rest_api.documentation.description	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:121	note: Normalized by RestServer and read by NOTHING — the ADR-0049 fourth state (parsed, unmarked, unenforced). normalizeConfig lists documentation: api.documentation straight into this.config.api and no site ever reads it back. no consumer; the served `in…
rest_api.documentation.version	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:127	note: Normalized by RestServer and read by NOTHING — the ADR-0049 fourth state (parsed, unmarked, unenforced). normalizeConfig lists documentation: api.documentation straight into this.config.api and no site ever reads it back. no consumer; the served `in…
rest_api.documentation.termsOfService	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:133	note: Normalized by RestServer and read by NOTHING — the ADR-0049 fourth state (parsed, unmarked, unenforced). normalizeConfig lists documentation: api.documentation straight into this.config.api and no site ever reads it back. no consumer, and the served…
rest_api.documentation.contact.name	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:145	note: The contact name an OpenAPI info.contact would carry. No consumer: the served document's info.contact is the literal { name: 'ObjectStack', url: 'https://objectstack.io' } written by packages/spec/scripts/build-openapi.ts, and rest-server.ts#registerO…
rest_api.documentation.contact.url	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:151	note: The contact URL an OpenAPI info.contact would carry. No consumer; the served value is the build-openapi.ts literal. Drilled rather than left riding on its container's blanket verdict, and NOT by fanning the parent's status out over its children — the call…
rest_api.documentation.contact.email	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:157	note: The contact email an OpenAPI info.contact would carry. No consumer, and the served document carries no info.contact.email at all — build-openapi.ts writes only name and url. Drilled rather than left riding on its container's blanket verdict, and NOT…
rest_api.documentation.license.name	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:171	note: The license identifier an OpenAPI info.license would carry. ⚠️ The one member of either container that is REQUIRED by its own schema (z.string(), no .optional()), so authoring a license object at all forces a value the runtime then ignores. No consu…
rest_api.documentation.license.url	dead (verified 2026-09-21)	packages/spec/liveness/rest_api.json:177	note: The license URL an OpenAPI info.license would carry. No consumer; the served value is the Apache-2.0 literal URL from build-openapi.ts. Drilled rather than left riding on its container's blanket verdict, and NOT by fanning the parent's status out over its…

Mainstream evidence:

• The OpenAPI info object is the standard carrier. Azure API Management and Apigee let the API owner set it.
• ServiceNow Scripted REST APIs have a name, description and documentation per API, shown in the REST API Explorer.
• Power Platform custom connectors have a "General information" tab (description, icon, host).
• Salesforce and Dataverse publish fixed platform API docs with no admin-set info. The capability exists where the platform lets owners publish an API, which is this surface.

Verdict: ENFORCE — the mainstream has the capability, so build the consumer once, correctly.

Reader that must exist / disposition: objectstack packages/rest/src/rest-server.ts#registerOpenApiEndpoints (:4869) builds enriched from the bundled spec and overrides servers, paths and tags. It must also overlay enriched.info from this.config.api.documentation. Today normalizeConfig writes the key (:4252) and nothing reads it back.

User-visible risk (1): Developer-facing documentation text; the silent no-op is cosmetic.

Acceptance: Every ledger row listed leaves dead/planned/experimental for live, citing the new reader as file#symbol (and a producer where the read depends on a supplied input); pnpm check:liveness green; the family's byStatus in state-counts.md regenerated.

Lane: domain:spec parent + packages/rest sub-issue (objectstack)

File surface: packages/spec/src/api/rest-server.zod.ts:206-225 · packages/rest/src/rest-server.ts (normalizeConfig, registerOpenApiEndpoints) · packages/spec/liveness/rest_api.json

Dedupe: rest_api\b \| RestApiConfig \| responseFormat \| termsOfService \| documentation\.(enabled\|title\|contact\|license) \| includePagination → 1 open hit. None carries a key of this family:

• decision(pm): this seat dispatched 5 clause-② reviews at the RETIRED model tier after the maintainer ruling landed — two PRs merged on void verdicts #19603 — process decision about the feat(spec): enrol RestApiConfigSchema in the liveness ledger as rest_api #19594 rest_api ledger enrolment; carries no key

四轴:

• 实际业务需求: 对外发布 API 的团队需要在文档里写上标题、版本、联系人和许可。这是 OpenAPI 的标准字段。
• 项目长远合理性: 消费端只需在已有的 OpenAPI 组装函数里加一步覆盖,把声明与产物接起来。
• 防 AI 写错: 写进去却不出现在文档里,会让 AI 以为配置位置错了而反复改写。接上之后结果可见、可测。
• 创业阶段不扩散: 一个函数里十几行,零新机制。

Unblocked by ruling 5862477514 on #20359 (B, batch #231 item 1; note 5862495365) — was blocked by #20359 from 2026-09-28T02:45Z. Execution: eight keys ENFORCE + documentation.version RETIRE, per the ruling.

[objectstack-fleet]

Path: business objects, records and views | 缺项 (no item reads the served OpenAPI info block) | P2

Triage: first grade — enhancement · priority:p3 · domain:spec · area:api · pm:queue. Verdict: ENFORCE, by the maintainer's criterion

Triage: the reader lands in packages/rest/src/rest-server.ts#registerOpenApiEndpoints (:4869), which overlays enriched.info from this.config.api.documentation ⇒ domain:spec parent, with a packages/rest (domain:cli) sub-issue. Rationale: nine keys that normalizeConfig writes (:4252) and nothing reads back. Developer-facing and cosmetic ⇒ p3.

Triage seat (objectstack-wide, seat post #6015) · session_01W89enF2dYV7K4N2Fbfj33f · 2026-09-27T20:33Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card (no comments), the criterion on #18900 (5727134555), and the #20273 / #20274 / #20282 grades that applied it this week.

Verdict. Where a platform lets owners publish an API, the owner sets its info: Azure API Management, Apigee, ServiceNow Scripted REST APIs, and Power Platform custom connectors. By the criterion ⇒ ENFORCE, 「补消费端(一次做对)」. It is not a decision-box round-trip. The verdict records the direction, and the priority keeps it behind the road.

Execution notes.

1. Overlay info (title, description, version, contact, license, and the rest of the nine) onto the served document, with the bundled defaults where a key is unset.
2. Pin the served /openapi.json info against an authored config, with the defaults as the control.
3. Its sibling RETIRE family, spec(api): retire api.responseFormat and api.documentation.enabled (4 keys); the envelope is fixed and enableOpenApi already decides the document #20295 (responseFormat, documentation.enabled), is graded separately. The two share rest-server.zod.ts, so the first to claim goes first.

[objectstack-fleet]

Claim: PM loop round 1 · 2026-09-28T01:56Z
Session: session_01Rjy9MeetSfq34PKn81CRiN
Account: os-zhuang
Branch: claude/issue-20294-openapi-info-from-config
Worktree: objectstack-issue-20294
Domain: domain:spec
Seat: domain:spec#1
File surface: a vertical seam dispatch (ruling A′ ② on #18900), with both ends declared. packages/rest/src/rest-server.ts: ONLY registerOpenApiEndpoints (about :4941–:5120) and, if needed, the NormalizedRestServerConfig.api type. packages/spec/src/api/rest-server.zod.ts: the documentation block's describes only. packages/spec/liveness/rest_api.json (nine rows → live) plus regenerated counts and README row; tests in packages/rest/src/; .changeset/. ⛔ Not rest-server.ts's draft-read doors (about :5872, :6615–:6961, :11232; the cli lane's #20338). ⛔ packages/spec/scripts/build-openapi.ts is read only. (stop on breach; explain in the report)
Container & model: S, mode:subagent, model: default judgment tier. A published output changes (the served OpenAPI info), so the PR is reviewed at CONTRACT_REVIEW_TIER before enqueue.
Clause-②: no
Thread-read: 5859594397
Serial constraints cleared: Read at {{NOW}} on origin/main 26daf0b0. #20295 (the sibling RETIRE, the same schema block) landed as PR #20343 → 26daf0b0 (landing record on #20295). The only other claim naming rest-server.ts is #20338 (cli, 5861662698): its draft-read sites are disjoint from registerOpenApiEndpoints, so the later lander merges main. No open PR touches rest-server.zod.ts, liveness/rest_api.json or build-openapi.ts (15 read).

[objectstack-fleet]

os-dev-report

{
  "issue": 20294,
  "status": "needs_decision",
  "branch": "claude/issue-20294-openapi-info-from-config",
  "pr": null,
  "session": "session_01Rjy9MeetSfq34PKn81CRiN — the PM's session (mode:subagent); this dev's identity is the branch",
  "premise_still_valid": true,
  "summary": "Stopped on the dispatch's own Zone 2 stop condition (item 2), before writing any code. The card's premise holds. With all nine keys authored, both doors that serve the document (GET /api/v1/openapi.json and the scoped /api/v1/environments/:environmentId/openapi.json) serve the bundled `info` unchanged and ignore every authored value. Measured at 26daf0b0; the three commits up to the current tip 67047171 touch neither packages/spec nor packages/rest. The fork: the two title defaults differ. The bundled info.title is 'ObjectStack REST API' (build-openapi.ts:138, pinned at openapi-self-consistency.test.ts:301). The schema MATERIALIZES a different title, 'ObjectStack API', whenever the block is present: parse of documentation: {} yields { title: 'ObjectStack API' }, and parse of {} yields no block. So any overlay that reads the parsed title retitles the document for an owner who authored only, say, description. The only fixes that keep 'bundled default where a key is unset' are a schema change, which the dispatch fences, or a rest-side read of the raw input, which is the consumer-side second source of defaults that contract-first forbids. A second conflict the grade never cites: ENFORCE reverses part of the #11646 maintainer ruling ('the info block returns to being wholly packages/spec-owned') and its whole-block pin (rest-openapi-route.test.ts:320-355). The ledger rows' own notes flag it ('reopening who owns info, which is above this ledger'). The card body truncates those notes before that sentence, and triage read only the card. The rest-side code is the same under every option. What is open is one schema line and which ruling governs; resume_plan is ready to apply.",
  "tests": "No diff, so no gate ran on a change. Measurement only. (1) Closure build under the lock: `pnpm --workspace-concurrency=2 --filter '@objectstack/rest^...' build` gave `os-verify-lock: VERDICT command-exit 0 · held the lock 337s`. (2) A scratch single-file vitest measurement, never committed and deleted afterwards, ran under the lock: `vitest run --project local --maxWorkers=2 src/zz-scratch-20294-measure.test.ts` gave Test Files 1 passed, VERDICT command-exit 0. `git status --porcelain` read empty after the delete. The file booted RestServer plus registerRoutes() the way rest-openapi-route.test.ts#makeRest does, with enableProjectScoping true / projectResolution auto so both doors mount, and drove each openapi.json handler. CELLS, all-nine authored → served on both doors: title 'Acme Orders API' → 'ObjectStack REST API'; description → the bundled 'Auto-generated OpenAPI specification…'; version '2.3.0' → '17.4.0'; termsOfService → absent; contact.name 'Acme API Team' → 'ObjectStack'; contact.url → 'https://objectstack.io'; contact.email → absent; license.name 'Proprietary' → 'Apache-2.0'; license.url → the Apache-2.0 URL. Honoured: 0 of 9. Cases absent, documentation: {}, description only, license.name only and contact.email only: the served info equals the artifact info on both doors, and the scoped info equals the unscoped. The normalized config DOES carry the authored values (normalizeConfig forwards the block; confirmed, no change owed there). ITEM 3, license with url and no name: schema door → ZodError issue code invalid_type, path documentation.license.name, message 'Invalid input: expected string, received undefined'; server door → construction throws 'REST API configuration is invalid: `api` does not satisfy `RestApiConfigSchema` (@objectstack/spec/api)… api.documentation.license.name: Invalid input: expected string, received undefined'. No schema change is proposed for it, so this refusal stays verbatim. ITEM 4, cache: the handler's clone is shallow ({ ...spec, servers }), so enriched.info IS the cached artifact's object by reference. Today it is unmutated in every case (cacheUnchangedAfterServe true on all 6 served cases), and the overlay must build a new info object, never assign into enriched.info. Cells on disk: scratchpad/issue-20294/zone2-cells.json and zone2-cells.md.",
  "gates": [
    { "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --workspace-concurrency=2 --filter '@objectstack/rest^...' build\"", "exit": 0, "verdict_line": "VERDICT command-exit 0 · held the lock 337s", "tree": "26daf0b0" },
    { "cmd": "bash scripts/pm/os-verify-lock.sh -c \"pnpm --filter @objectstack/rest exec vitest run --project local --maxWorkers=2 src/zz-scratch-20294-measure.test.ts\"", "exit": 0, "verdict_line": "VERDICT command-exit 0 · held the lock 9s · waited 51s", "tree": "26daf0b0", "note": "measurement only; scratch file deleted, never committed" },
    { "cmd": "node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack", "exit": 2, "tree": "67047171", "note": "'this branch changes nothing against origin/main — nothing to derive'. Expected: the diff is empty; not a gate failure." },
    { "cmd": "node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack (resume surface: rest-server.ts, rest-openapi-route.test.ts, rest-server.zod.ts, liveness/rest_api.json, state-counts.md, README.md)", "exit": 0, "tree": "67047171", "note": "83 projected lines, NOT RUN (no diff); saved at scratchpad/issue-20294/gates-projected.log for the resumed round" }
  ],
  "files_changed": [],
  "line_budget": "n/a — no diff",
  "deviations": [
    "Worktree /home/user/objectstack-issue-20294 and its node_modules are kept after the report is read back, not removed. No PR was opened, and the resumed round reuses it: the closure build at 26daf0b0 is still valid for packages/spec and packages/rest at 67047171.",
    "The remote branch stays at the empty probe push (26daf0b0). The local branch is fast-forwarded to 67047171 with no commits, so there is nothing to push.",
    "Shared-ref race at fetch: 'cannot lock ref refs/remotes/origin/main: is at 67047171… but expected d498113b…', because a sibling's fetch advanced the ref concurrently. It resolved to 67047171, and BASE is pinned to that sha, not to the moving name.",
    "On resume the harness reported the primary working directory as /home/user/objectstack-seat-ro. Every command after that ran with an absolute cd into /home/user/objectstack-issue-20294; nothing ran in, or read from, the seat-ro tree."
  ],
  "clause2_projection": "Clause-②: no — projected for the recommended options (Q1 B, Q2 A, Q3 A); nothing is declared yet because nothing is written. Accept set: unchanged in both directions. Every config the schema accepts today it accepts after, and none it refuses becomes accepted; Q1 B removes a default, not an accepted input. Public surface: no new key, route, export or accepted value. The served document changes: owner values land in OpenAPI Info Object members the document already has, and termsOfService and contact.email appear only when authored. That is a new reader of already-accepted keys, closing a declared≠enforced gap. It does not widen, and the unset control stays byte-identical. Arm: none. Q1 B loosens the parsed OUTPUT type (title: string → string or undefined), which narrows no accept set; the key has 0 non-test readers. Changeset: @objectstack/rest minor (a served output now reflects config), @objectstack/spec patch (a describe and, under Q1 B, a default).",
  "mcp_calls": "0",
  "api_writes": "1 — POST /repos/objectstack-ai/objectstack/issues/20294/comments (this os-dev-report, via scripts/pm/post-stamped.mjs through the fleet-write relay). Also 1 `git push` (the empty branch probe), which is not a REST write. The REST calls to /issues/20294, /issues/20294/comments, /issues/11646(+comments) and /issues/comments/5727134555 were all GET reads.",
  "open_questions": [
    {
      "question": "Q1 — The schema MATERIALIZES documentation.title = 'ObjectStack API' whenever the block is present, and the bundled info.title is 'ObjectStack REST API'. Which fix keeps 'bundled default where a key is unset' for title?",
      "options": [
        "A — No schema change: the overlay reads the parsed title. Any authored block, even { description } alone or {}, retitles the served document to 'ObjectStack API', a string no deployment has ever served. This violates triage note 1 and the dispatch's rule that the schema default must not silently replace the bundled title.",
        "B — spec: `title: z.string().default('ObjectStack API')` → `z.string().optional()`, the shape the other eight keys already have. An unset title is unset, and the overlay leaves the bundled one. Accept set unchanged; the parsed output type loosens (title string → string or undefined). Two pins assert the materialized default and flip: spec rest-api-config-dead-keys-retirement.test.ts:172 and rest rest-config-parse-not-cast.test.ts:352. rest-api-config-dead-keys-refused.test.ts:153 authors its title, so it stays green. The describe and the reference row (content/docs/references/api/rest-server.mdx:260) regenerate.",
        "C — spec: change the default VALUE to 'ObjectStack REST API'. Shape and type unchanged, but two literals (the schema default and build-openapi.ts:138) must be held equal by a new cross-package pin, or a later retitle of the artifact drifts in silence.",
        "D — rest reads the RAW config to tell an authored title from a defaulted one. Rejected: it rebuilds the consumer-side second source of defaults that normalizeConfig dropped when it moved to parse-and-consume, and AGENTS.md PD#12 forbids it."
      ],
      "recommendation": "B. Need: the observable, published title is the bundled one (the @objectstack/spec/openapi.json export and its pin); 'ObjectStack API' has never reached a served byte (ledger: 0 read sites). Long-term: one source of defaults, the bundled document, which is the triage note's own rule. AI-proof: 'unset = bundled' becomes uniform across all nine keys, with no silent side effect from authoring a sibling key. Startup scope: one line, two pin flips and a regenerated reference row, no new mechanism. C is second-best: the same observable behaviour, but it buys a coupling that needs its own pin. The dispatch fences a spec shape change, hence the stop."
    },
    {
      "question": "Q2 — Executing ENFORCE reverses part of the #11646 maintainer ruling: 'the info block returns to being wholly packages/spec-owned', and C there, 'a config key for a demand nobody expressed', was declared dead. Its pin (rest-openapi-route.test.ts:320-355, 'serve-time enrichment must not touch info — the WHOLE block is the artifact's') asserts body.info toEqual artifact.info. Is the ENFORCE grade the superseding record for OWNER-AUTHORED values?",
      "options": [
        "A — Yes, for owner-authored values only. An absent block, or one with every key unset, serves info byte-identical to the artifact, and the #11646 whole-block pin keeps running as exactly that control. #11646's exclusions stay verbatim: api.version and OS_RUNTIME_VERSION never reach info.version (rest-openapi-route.test.ts:388-497 unchanged). An authored documentation.version becomes info.version. Only a host that writes the block sees a change, and that host is an embedder: os serve forwards only enableProjectScoping and projectResolution out of api, never documentation (#15543 reachability).",
        "B — Keep #11646 whole for version: enforce eight keys and RETIRE documentation.version (tombstone, ADR-0087 D3, changeset). This contradicts the ENFORCE grade for one key and splits the family.",
        "C — Keep #11646 entirely: ENFORCE cannot be executed, and the card returns to triage or the maintainer."
      ],
      "recommendation": "A. #11646 chose between two NON-authored facts, the route identifier and SPEC_VERSION, and rejected a config key for 'a demand nobody expressed'. The later #18900 criterion (5727134555) replaced exactly that demand test with the mainstream one, and triage applied it: Azure APIM and Apigee let the owner set info.version. Every value #11646 excluded stays excluded, and its invariant holds byte for byte in the unset control. Whether that reading is the PM's to make or needs the maintainer's word is the PM's call; the ledger itself says the question sits above the ledger."
    },
    {
      "question": "Q3 — Overlay granularity for the two containers. The triage note says 'bundled defaults where a key is unset', read per key. Per LEAF publishes mixed-party blocks: license { name: 'MIT' } would be served as { name: 'MIT', url: the Apache-2.0 URL }, and contact { email } as ObjectStack's name and URL with the owner's email.",
      "options": [
        "A — Per CONTAINER: an authored contact or license replaces the bundled one whole, and its unset members are absent, never inherited. The four scalars (title, description, version, termsOfService) overlay per key. info.license then always carries name, because the schema requires it (item 3).",
        "B — Per LEAF, as the note is literally worded."
      ],
      "recommendation": "A. Per leaf would make the served document state an MIT license at the Apache URL, a false statement in a machine-read contract (AGENTS.md route rule 4, machine-readable surfaces must not lie). Per container never publishes one. It adds no mechanism."
    }
  ],
  "resume_plan": "On the PM's answers (as recommended: Q1 B, Q2 A, Q3 A). (1) rest-server.ts, inside the registerOpenApiEndpoints region only: a pure exported helper overlayDocumentationInfo(bundledInfo, documentation) that returns a NEW info object (the cache holds info by reference); the handler sets enriched.info from it just before res.json. The same closure serves both doors, so both carry the overlay. The #11646 comment at :5095-5113 is rewritten to 'unset = the artifact's, authored = the owner's; api.version and the runtime version never'. (2) rest-server.zod.ts: title → .optional(); describes on the nine members state that the served /openapi.json info carries them, with the bundled value where unset; gen:schema and gen:docs. (3) Tests: a table-driven helper pin (each key alone, all nine, none = control equal to the artifact, license without url, contact partial), an HTTP pin on both doors with the no-config control, the #11646 whole-block pin kept as the unset control, and the two default pins flipped with their new substance asserted. (4) liveness/rest_api.json: the nine leaf rows plus the documentation.contact and documentation.license container rows → live; evidence packages/rest/src/rest-server.ts#overlayDocumentationInfo, producer packages/rest/src/rest-server.ts#normalizeConfig. Counts are regenerated by gen:liveness-counts (rest_api 12 live / 12 dead → 21 / 3, total 24), and the README rest_api row is edited, since its Notes prose is hand-written. (5) Changesets as in clause2_projection. The file surface stays inside the claim; build-openapi.ts is untouched, and runtime/qa need no pin.",
  "out_of_scope_findings": [
    "carrier: this card's resumed PR (the same function) · noted, not filed — the /docs viewer page's HTML title is the literal 'ObjectStack API Docs' (rest-server.ts registerOpenApiEndpoints, the /docs handler). That door serves a title from outside `info`, so a retitled API keeps that browser-tab title. It is not an `info` field and falls in no a/b/c class; it is an Acceptance-notes candidate. Dedupe words: 'ObjectStack API Docs', /docs viewer title, Scalar.",
    "carrier: 承接者:无 · noted, not filed — OpenApiGenerationConfigSchema.title (packages/spec/src/api/plugin-rest-api.zod.ts:570) carries a third OpenAPI title default, also 'ObjectStack API'. Its readers were not measured here, so this is an observation only. Dedupe words: OpenApiGenerationConfigSchema, plugin-rest-api title default, openApi.title."
  ]
}

---

Generated by Claude Code

[objectstack-fleet]

Release: session_01Rjy9MeetSfq34PKn81CRiN (domain:spec seat 1) · reason: a premise was falsified before any edit. Executing the ENFORCE grade reverses part of an earlier maintainer ruling · to: needs-user-decision, assignee cleared in this act · 2026-09-28T02:31Z

Decision needed: does the #18900 ENFORCE grade supersede #11646's 「info 块整块归 packages/spec」 for owner-authored values?

The dev (report above, on claim 5861942248) stopped on the order's own stop condition, before any edit. No PR exists. Its worktree and a ready resume plan are kept, so an answer re-dispatches in one step.

Measured (at 26daf0b0; the tip 67047171 touches neither package). With all nine api.documentation keys authored, both doors (/api/v1/openapi.json and the scoped /environments/:environmentId/openapi.json) serve the bundled info unchanged: 0 of 9 honoured. With nothing authored, documentation: {}, or one key alone, the served info equals the artifact's on both doors. The cells are on the dev report.

Governing text (both rulings quoted verbatim, retrieved in this act):

• [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, maintainer ruling 5405070350 (2026-08-25, 「全部同意」): 「the info block returns to being wholly packages/spec-owned」 … 「A (keep the two-meanings split) and C (a config key for a demand nobody expressed) are dead.」 Pinned at rest-openapi-route.test.ts (the whole info block equals the artifact's).
• [Decision] Route declared≠enforced work by the SEAM, not the layer — a Seam: line on filing, vertical dispatch by default in the spec lane, automatic parent + sub-issues for spec↔objectui seams, Journey as a filter, bulk retirement per spec family, Console Pin Gate back to required (the maintainer's 「同意」 on the five-line batch, 2026-09-18) #18900, maintainer criterion 5727134555: 「每族该问的是:主流平台有没有这个能力 —— 有 ⇒ 补消费端(一次做对)」.
• This card's grade (triage 5859594397): 「Verdict: ENFORCE, by the maintainer's criterion」 … 「Overlay info … with the bundled defaults where a key is unset」. Triage read the card and [Decision] Route declared≠enforced work by the SEAM, not the layer — a Seam: line on filing, vertical dispatch by default in the spec lane, automatic parent + sub-issues for spec↔objectui seams, Journey as a filter, bulk retirement per spec family, Console Pin Gate back to required (the maintainer's 「同意」 on the five-line batch, 2026-09-18) #18900, but not [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. The ledger rows' own notes say ENFORCE means 「reopening who owns info, which is above this ledger」.

The two sub-questions the seat folds into the same answer:

• Title default. The schema materializes documentation.title = 'ObjectStack API' whenever the block is present. The bundled title is 'ObjectStack REST API', and 'ObjectStack API' has never been served. So "bundled default where unset" needs title to become .optional(), like the other eight keys. That is a one-line spec change, with two pins flipped.
• Containers. An authored contact / license replaces the bundled one whole, never member by member. Otherwise the document could state an MIT licence at the Apache-2.0 URL, which is a false statement in a machine-read contract. The seat takes this as settled (AGENTS.md: machine-readable surfaces must not lie).

选项

• A(席位推荐)—— 作者写的值覆盖、不写即原样。
  • api.documentation 九个键若由作者写出,就覆盖到被服务文档的 info。
  • 一个都不写时,info 与制品逐字节相同:[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 的整块钉子原样保留,作为对照。
  • [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 排除的两样(路由版本 api.version、运行时版本)照旧永不进 info.version。
  • 同笔:title 改为 .optional();contact / license 按整块替换。
• B —— 只执行八个键,退役 documentation.version。 info.version 恒为 SPEC_VERSION,[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 的版本结论绝对成立;代价是同一族一半 ENFORCE、一半 RETIRE。
• C —— [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 整条优先,这一族改判 RETIRE。 九个键全部立墓碑(ADR-0087 D3),info 保持整块归 spec;[Decision] Route declared≠enforced work by the SEAM, not the layer — a Seam: line on filing, vertical dispatch by default in the spec lane, automatic parent + sub-issues for spec↔objectui seams, Journey as a filter, bulk retirement per spec family, Console Pin Gate back to required (the maintainer's 「同意」 on the five-line batch, 2026-09-18) #18900 的「主流有 ⇒ 补消费端」在此让位。

四维分析

• 实际业务需求
  • 实测:三个仓里 0 个作者写 api.documentation。os serve 只从 api 转发 enableProjectScoping / projectResolution,只有嵌入方能写到这个块。
  • 主流侧:Azure API Management、Apigee、ServiceNow Scripted REST、Power Platform 自定义连接器,都让 API 所有者设置 info(标题、描述、版本、联系人、许可)。
  • 拉动来自「主流有」,不是来自仓内用法,正是 [Decision] Route declared≠enforced work by the SEAM, not the layer — a Seam: line on filing, vertical dispatch by default in the spec lane, automatic parent + sub-issues for spec↔objectui seams, Journey as a filter, bulk retirement per spec family, Console Pin Gate back to required (the maintainer's 「同意」 on the five-line batch, 2026-09-18) #18900 换掉的那条判据。
• 项目长远合理性(权重 ≥50%)
  • A:一处真源(制品)给默认,作者值只在写出时生效,九个键规则一致。
  • B:把一族拆成两种处置,留下永久例外。
  • C:最干净,但等于宣布「平台不让 API 所有者给自己的 API 起名」,与主流相反,以后再补要重开一次 ADR-0087 迁移。
• 防 AI 写错
  • 现状是声明了九个键却一个不兑现,AI 写了等于白写,是最差的一种。
  • A 与 C 都消灭这个状态:A 让它生效,C 在发布时响亮拒绝。
  • B 保留一个「写了会被拒」的键和八个「写了生效」的键,最容易让 AI 以为 version 也能写。
• 创业阶段不扩散
  • A 不新增任何键、路由或导出,只让已接受的键生效,改动收在 registerOpenApiEndpoints 一处加一条 schema 行。
  • C 删面更多但要墓碑、迁移条目和文档。
  • 零作者这一事实倾向 C,主流判据倾向 A。

席位推荐:A。 长远轴领起:单一默认源,作者值写出才生效,不写时 #11646 的不变式逐字节保持;新的 #18900 判据恰恰替换了 #11646 用来否决 C 的「无人提出需求」这一条。如果你要 info.version 绝对等于 SPEC_VERSION,选 B。如果你要 info 整块归 spec 不变,选 C。

你要做的(一个动作): 回一个字母,A / B / C。