Rebind the history-door consumers to the newly declared HistoryMetaItem schemas (route-ledger row + client.meta.getHistory inline return) — #12038 class

[claude]

Recorded from the accepted #12005 delivery (PR #13521, report: #12005 (comment)). Unassigned — recording only, for triage grading. Same rebinding class as #12038, one route over.

The gap

With HistoryMetaItemRequestSchema/HistoryMetaItemResponseSchema now declared in packages/spec/src/api/protocol.zod.ts (PR #13521), two consumers still carry pre-declaration spellings:

1. The route ledger row for GET /meta/:type/:name/history cannot yet name HistoryMetaItemResponseSchema — it predates the declaration.
2. client.meta.getHistory still declares its return type inline instead of binding the published response schema's inferred type.

Why it matters

Inline shapes drift silently from the contract they duplicate — the exact class #12038 is burning down. Rebinding is mechanical once the declaration exists (it now does), and each rebind removes one silent-drift surface.

Sequencing

Only after PR #13521 lands — the schemas it declares are the binding target. The dead environmentId wire-spread on the same door is already recorded on card #12005 and is NOT part of this finding.

---

Generated by Claude Code

[zhuangjianguo]

定级补齐(skills 席代分诊):priority:p2(domain:spec 已在)—— #12038 类机械重绑,双消费者(route-ledger 行 + client.meta.getHistory 内联返回型),排序约束已在卡(PR #13521 落地后)。spec 车道按 #12038 族的既有法办。

---

Generated by Claude Code

[os-warren]

分诊定级 → domain:cli(自 domain:spec 改路由)· p2 · tooling · pm:queue。摘 finding。

⭐ 排序前提已满足,本卡现在可派。 卡片写「Only after PR #13521 lands」。在 origin/main 上核实,已落地:

packages/spec/src/api/protocol.zod.ts:1487   Request shape for `GET /api/v1/meta/:type/:name/history`
packages/spec/src/api/protocol.zod.ts:1539   The body of `GET /api/v1/meta/:type/:name/history`
packages/spec/export-origins/api.json:501/503  HistoryMetaItem{Request,Response}Schema → src/api/protocol.zod.ts

⇒ 绑定目标存在,本卡不再等任何东西。

⚠️ 改路由,理由是落点读数。 之前挂 domain:spec,但 schema 已经在 spec 里了 —— 本卡要改的是两个消费者,不是声明:

packages/rest/src/rest-route-ledger.ts:239
  { route: 'GET /api/v1/meta/:type/:name/history', family: 'metadata',
    source: 'route-manager', disposition: 'sdk', client: 'meta.getHistory', … }   ← 台账行

packages/client/src/index.ts:1204 / :6097   getHistory: async (…)                  ← 内联返回类型

packages/rest 与 packages/client* 都在 domain:cli 包家族 ⇒ domain:cli。⛔ 按「schema 在 spec 里」归 spec 是按声明归域,而锚定规则要的是修复落地的那个包。

定级 p2(沿用)。内联形状会静默偏离它复制的那份契约,这正是 #12038 在烧的那一类;声明已存在之后重绑是机械的,每重绑一处就少一个静默漂移面。无正确性伤害 ⇒ 不判 p1;不是纯文档 ⇒ 不判 p3。

⛔ 范围边界(卡片自己划的,原样保留):同一扇门上那条已死的 environmentId wire-spread 记在 #12005,不属于本卡。

⚠️ 一条给 dev 的提醒:packages/client/src/index.ts 里 getHistory 出现两处(:1204 与 :6097)。⛔ 只改其一是本卡最容易犯的错 —— 派发前确认这两处是同一个门的两个出口(例如常规与 scoped 变体)还是各自独立,两处都要绑。

---

Generated by Claude Code