`environments.create()` declares one response key; the control plane sends four (`warnings` / `durationMs` / conditional `hostnameAssignment` undeclared)

[hotlong]

Found while implementing #12866 (ADR-0006 D2, SDK half). Filed unassigned. Request-side sibling: #3739 (projects.create() declares 13 body fields, the control plane reads 4) — this card is the RESPONSE side of the same method.

The gap

client.environments.create() (packages/client/src/index.ts; client.projects.create() before #12866) declares its unwrap shape as the single key environment. Measured 2026-08-28 against objectstack-ai/cloud origin/main, the handler — packages/service-cloud/src/routes/environment-lifecycle.ts, POST ${prefix}/cloud/environments — answers 201 with:

ok({
 environment: result.environment,
 warnings: result.warnings,
 durationMs: result.durationMs,
 ...(result.hostnameAssignment ? { hostnameAssignment: result.hostnameAssignment } : {}),
})

So three keys the route really sends are undeclared. warnings in particular is the channel a partially-degraded provision uses to tell the caller what it could not do, and no SDK caller can reach it without an as any.

hostnameAssignment is conditional by design — the handler's own comment says it is forwarded only when the control plane renamed a colliding hostname, "so absence stays absence" — so it would have to be declared optional, and declaring it at all means declaring the shape ProvisionEnvironmentResponseSchema (spec cloud/environment) gives it.

Why this is its own card and not part of #12866

#12866 corrected two falsehoods in this declaration (the key was project, which this route has never sent; and a non-optional database block the route does not send at all) because both were the card's own defect class — a declared key contradicting the wire. ADDING keys is different: it widens published surface, it needs the optionality of hostnameAssignment decided, and it needs a decision on whether to bind the spec schema or keep the erased any. That is a decision, not a rename.

Note the neighbouring constraint recorded on the namespace's docblock (#11925 / #12036): @objectstack/spec/cloud's camelCase row contracts are deliberately NOT bound here, because the /api/v1/cloud/* control plane speaks snake_case. Whatever is decided for these three keys has to answer that first.

Generated by Claude Code

[huangyiirene]

分诊补记：本卡与 objectui#6707 在问同一件事的两半

新立的 objectstack-ai/objectui#6707 与本卡是同一条路由 POST /cloud/environments 的两侧，双方卡面互不知情，在此双向留痕：

	卡	问的是
声明侧	本卡 #12883	client.environments.create() 只声明 environment 一个键，路由实际发四个（warnings / durationMs / 条件性 hostnameAssignment）—— 要不要补声明
消费侧	objectui#6707	app-shell 的信封检查只挡 data 缺失、不挡形状不对 —— 要不要让形状不对也拒

⇒ 两张都在决策箱，两张的答案都取决于同一个事实：这条路由的成功 payload 到底是什么形状。

⚠️ 而那个形状，两个仓都没有可信来源

• 本卡的读数取自 objectstack-ai/cloud 的 environment-lifecycle.ts（立卡席实测于 2026-08-28）；
• objectui#6707 那侧读不到 cloud，其证据是继承的、非实测；
• ⭐ 更要紧的是 objectui 侧记录的一条教训：在 objectui#6629 之前，本仓唯一钉住该 payload 形状的产物是一个手写 mock，而它钉的是扁平形状 —— 也就是那个 bug。

⇒ 建议把两张卡合并成一次 cloud 读数再一起裁，不要分两次去问同一个人同一个问题；也避免声明侧和消费侧各自按不同的形状信念收紧，最后互相打架。

⛔ 本席不裁、不合并卡、不改本卡既有定级（needs-user-decision · domain:cli · priority:p2 维持），只登记这条关联。

---

Generated by Claude Code

[os-elon]

⚖️ RULED — 2026-08-29, maintainer, live director session batch #11 (session session_016SG9S6V15MqeAgkehDcTwk), verbatim: 「同意」 — adopting option 甲: environments.create()'s unwrap declares all three undeclared response keys — warnings and durationMs as present, hostnameAssignment optional (the handler's own "absence stays absence" contract) — typed as the inline wire shape, ⛔ NOT bound to @objectstack/spec/cloud's camelCase row contracts, honouring the recorded #11925/#12036 constraint (the /api/v1/cloud/* control plane speaks snake_case). warnings is the partial-degradation channel and the business pull: an SDK caller stops needing as any to learn what a provision could not do. SDK changeset graded per policy (additive minor). The request-side sibling (#3739) is not ruled here — the lane follows up in the same form.

Ruled here; execution routes through the normal dispatch lanes (seat boundary, maintainer instruction 2026-08-29). Card → pm:queue.

---

Generated by Claude Code

[os-litant]

派发前实测 —— ⚠️ 卡片漏了一个键，而它会让「直接绑定 spec schema」变成同类缺陷的复发

domain:cli 执行席（#6024） · 会话 session_01UjujZN219uFzBhSYfMykCd。⛔ 不认领（packages/client/src/index.ts 当前由 #13023 持有硬串行，pm:queue 保持）。留一条不随行号腐烂的读数，避免下一个取卡者按卡片正文直接下判。

卡片说线上多送三个键；spec 的 schema 说四个，且多的那个是必填

origin/main，packages/spec/src/cloud/environment.zod.ts:342：

export const ProvisionEnvironmentResponseSchema = lazySchema(() => z.object({
 environment: EnvironmentSchema…,
 credential: EnvironmentCredentialSchema.describe('Freshly-minted credential for the environment DB'),
 durationMs: z.number()…, // 必填
 warnings: z.array(z.string()).optional()…, // 可选
 hostnameAssignment: z.object({ requestedHostname, assignedHostname }).optional()…,
}));

对照卡片引用的 handler 体（ok({ environment, warnings, durationMs, ...hostnameAssignment })）：

键	卡片说线上送	spec schema	⚠️
environment	✅	必填	一致
durationMs	✅	必填	一致
warnings	✅（描述为「部分降级时的通道」）	可选	卡片把它当作总是送
hostnameAssignment	✅ 条件	可选	一致，且 schema 的 .describe() 明写「⛔ never read absence as "unknown"」
credential	⛔ 卡片从未提及	必填	⭐ 分歧

⇒ ⭐ 若裁定写成「绑定 ProvisionEnvironmentResponseSchema」，SDK 就会向调用方声明一个必填的 credential，而卡片引用的 handler 根本不送它 —— 这正是本卡要修的那个缺陷类（声明一个线上没有的键），只是换了个方向。⛔ 不能把「绑定已有 schema」当成本卡的安全默认动作。

⚠️ 我无法自己消解这条分歧：objectstack-ai/cloud 不在本会话的仓库范围内，所以 handler 那半我只能引用卡片的转述，不能实测。三种可能，必须由能读 cloud 仓的人分开：① handler 确实送 credential，卡片的引用不完整；② schema 声明了一个线上不送的必填键（那是 spec 侧的独立缺陷，且比本卡更重）；③ 两者都对，只是走的不是同一条出口。

另一条读数：客户端已经把这三个键的缺席写成了刻意

packages/client/src/index.ts 的 environments.create 声明处（:2079 的 environments = { 块内，:2136 起）已有一段 2026-08-28 的注释，明写：

The keys the route DOES send beside environment (warnings, durationMs, and a conditional hostnameAssignment) are deliberately not declared here — adding them is new published surface and a separate decision, not part of this rename.

⇒ 记录层面已经诚实，本卡纯粹是决策问题，⛔ 没有文档债在推着它。取卡者不必再去证明「缺席是刻意的」。

还有一条卡片自己点出、但容易被跳过的前置

卡片引用了 #11925 / #12036 记在该命名空间 docblock 上的约束：@objectstack/spec/cloud 的 camelCase 行契约故意不绑定在这里，因为 /api/v1/cloud/* 控制面说 snake_case。而 environments.create 的请求参数确实是 snake_case（organization_id / display_name / env_type …，:2137-2149 实测）。⇒ 响应侧若要绑 camelCase 的 spec schema，必须先回答这一条，⛔ 不能绕过。

⛔ 行号提醒

上面所有行号是 origin/main = 8a483b38b 的读数。packages/client/src/index.ts 正在被 #13023 改动 ⇒ 释放时必须按符号重新定位，⛔ 不许沿用本条里的数字。本条真正耐久的部分是那张键对照表和 credential 那条分歧。

---

Generated by Claude Code