Filed by the domain:spec seat (session_01LpRNHxWZgSUgVnFT9mQQo4) from #12522's charter item 4 (fork condition), so the question survives #12522's closure when PR #13019 merges. Exactly one member of the 132 audited tombstone prescriptions hit the fork.
The member
packages/spec/src/api/batch.zod.ts — options.validateOnly:
FROM: …was removed from BatchOptions in @objectstack/spec (#4052).
TO: …was removed from BatchOptions in @objectstack/spec.
Its ONLY reference was the internal issue id: no ADR, no os migrate command, and — uniquely among the 132 changed prescriptions (96 carry an ADR id, 83 the migration command, 59 a FROM→TO mapping, 128 a version anchor) — no version anchor either. The instruction itself is complete and actionable ("drop the key", plus what to do instead); what is missing is a citation. PR #13019 landed option A (strip, no invented replacement), per the charter's ⛔ on inventing references.
一句话问题:132 条被剥离 tracker id 的墓碑处方里,唯独这一条剥完后没有任何耐久引用(无 ADR、无迁移命令、也没有版本锚)——要不要由你补一个「该键在哪个版本被移除」的事实?
选项 × 真实代价
| 做什么 | 真实代价 |
|---|
| A | 维持现状(已随 PR #13019 落地):处方指令完整,只是缺引文 | 零动作;代价是这条与其余 131 条兄弟的形制永久不一致,而「墓碑带耐久引用」正是本次卡要守的公约 |
| B | 你提供 options.validateOnly 被移除的发布版本号,跟进单加一行版本锚(与其余 128 条同形)(推荐) | 你答一个事实 + 一行 PR;移除版本是不可猜测的事实,只有查得到发布史的人能供 |
| C | 保留该条的 issue id | ⛔ 已排除:扩宽后的规则会在自己的 diff 上变红,与同 PR 落规则不相容(dev 已论证) |
四棱:① 长远合理性 — B 恢复公约一致性;② 业务拉动 — 零(纯引文);③ 防 AI 犯错 — 版本号是不可猜的事实,B 把它固定下来,防止后人臆造;④ 不扩散 — B 是一行,不是新机制。
推荐:B。A 已落地故今天可合,B 是一行跟进。裁 B 时请直接在本卡回复版本号,spec 席跟进单执行;裁 A 则关本卡即可。
Refs: #12522 (the charter, item 4) · PR #13019 (landed as option A) · the audit numbers above are from that PR's tombstone audit.
Filed by the domain:spec seat (session_01LpRNHxWZgSUgVnFT9mQQo4) from #12522's charter item 4 (fork condition), so the question survives #12522's closure when PR #13019 merges. Exactly one member of the 132 audited tombstone prescriptions hit the fork.
The member
packages/spec/src/api/batch.zod.ts—options.validateOnly:Its ONLY reference was the internal issue id: no ADR, no
os migratecommand, and — uniquely among the 132 changed prescriptions (96 carry an ADR id, 83 the migration command, 59 a FROM→TO mapping, 128 a version anchor) — no version anchor either. The instruction itself is complete and actionable ("drop the key", plus what to do instead); what is missing is a citation. PR #13019 landed option A (strip, no invented replacement), per the charter's ⛔ on inventing references.一句话问题:132 条被剥离 tracker id 的墓碑处方里,唯独这一条剥完后没有任何耐久引用(无 ADR、无迁移命令、也没有版本锚)——要不要由你补一个「该键在哪个版本被移除」的事实?
选项 × 真实代价
options.validateOnly被移除的发布版本号,跟进单加一行版本锚(与其余 128 条同形)(推荐)四棱:① 长远合理性 — B 恢复公约一致性;② 业务拉动 — 零(纯引文);③ 防 AI 犯错 — 版本号是不可猜的事实,B 把它固定下来,防止后人臆造;④ 不扩散 — B 是一行,不是新机制。
推荐:B。A 已落地故今天可合,B 是一行跟进。裁 B 时请直接在本卡回复版本号,spec 席跟进单执行;裁 A 则关本卡即可。
Refs: #12522 (the charter, item 4) · PR #13019 (landed as option A) · the audit numbers above are from that PR's tombstone audit.