platform-objects: 45 system objects declare `id` as `text` while the platform emits `varchar(255)` — the whole remainder of #12015's post-narrowing corpus

[os-warren]

Filed unassigned, from the corpus measurement carried out under #12015 (PR #12109). Not fixed there: that card owns the driver's diagnostic, and this is a metadata change in packages/platform-objects and its siblings.

What was measured

#12015 makes SqlDriver say out loud when a declaration on a builtin column name (id / created_at / updated_at) asks for storage the platform's own column does not deliver. The measurement is a real boot, not a grep: all 45 object definitions exported by @objectstack/platform-objects, driven through SqlDriver.initObjects on SQLite with a spy logger.

• Before the narrowing: 116 warnings (id 45, created_at 42, updated_at 29).
• After the narrowing: 45 warnings — all of one shape, and every one of them a genuine disagreement:

sys_account.id: lost ["type"] — declared type 'text'
sys_api_key.id: lost ["type"] — declared type 'text'
…
sys_migration.id: lost ["type","maxLength"] — declared type 'text'
…
sys_view_definition.id: lost ["type"] — declared type 'text'

Every platform object declares its key as id: Field.text({ label: …, required: true, readonly: true }). The platform emits table.string('id').primary() — varchar(255), not TEXT. So the declared type is not what lands, on the platform's own metadata, 45 times. sys_migration.id additionally declares a maxLength that binds nothing.

The created_at / updated_at declarations are not part of this: they declare type: 'datetime' and defaultValue: 'NOW()', which is exactly what createAuditTimestampColumn emits, so they are silent and correct as written.

Why it matters

The presentation half of these declarations is load-bearing and must stay — label feeds the generated *.objects.generated.ts translation files in four locales, highlightFields, FLS and sortability, and required is the ADR-0113 write contract. ⛔ So this is not "delete the id declaration". What disagrees with reality is one key: the declared type.

Left alone, these 45 lines are what a stock boot prints once #12015 lands — true, but a standing reminder that the platform's own metadata says TEXT where the platform stores varchar(255).

Shape of a fix (not decided here)

Either the declaration is corrected to the type the platform actually emits (Field.string(...), keeping every other key), or the platform's key column is what should change. The first is a mechanical metadata edit across ~45 files in platform-objects / metadata-core / the plugin and service packages; the second is a storage decision nobody has asked for. Which one is right is a judgement about what id should be, adjacent to (but not the same as) the question #12015 deliberately left unanswered — whether declaring id should be meaningful for the key's type.

Related: #12015 (where it was measured), #11431, #11374.

---

Generated by Claude Code

[os-warren]

Triage (domain:engine seat): decision card — needs-user-decision + domain:engine. The two routes are a real fork with different blast radii, and neither is a dev's to pick.

One-line problem, in business terms: the platform's own metadata says these 45 system objects store their key as TEXT; the platform actually stores varchar(255). Nobody is broken by it today — the key works — but the platform is telling authors (increasingly, AI authors reading metadata whole) something about its own shape that is not true.

Why it is a decision and not an edit. The card names the fork correctly, and the cheap-looking option is not as cheap as it looks:

• A — correct the declarations (Field.text → Field.string on ~45 files across platform-objects / metadata-core / plugins / services, keeping every other key). Mechanical and zero-DDL. ⚠️ But text and string are not interchangeable to consumers: the declared type is published metadata that the UI reads to choose a rendering (multi-line vs single-line input), and type-compat's canonical map reads it too. So this is a visible change to 45 published objects, not a comment fix.
• B — change the platform's key column to match the declarations. A storage decision nobody has asked for, touching every table the platform creates.
• C — accept and document. The 45 lines print once per boot after driver-sql: a declared field named id / created_at / updated_at is silently discarded by initObjects — declared type, length and constraints all ignored with no diagnostic #12015 lands. True, quiet, and a standing reminder.

Recommendation: A, but the veto surface is the rendering question, and it should be answered before the sweep rather than discovered by it — measure whether any shipped view actually renders a system id from its declared type, since readonly: true may make the distinction moot in practice. If it is moot, A is nearly free and closes the last of this corpus honestly. If it is not, C is the honest hold.

⛔ Not available: deleting the id declarations. Their label feeds the generated *.objects.generated.ts translation files in four locales plus highlightFields, FLS and sortability, and required is the ADR-0113 write contract — verified against sql-driver.ts:14021, where storage.notNull (not required) drives the DDL. Only the declared type disagrees with reality.

Adjacency worth stating: this sits next to — but is not — the question #12015 deliberately left unanswered (whether declaring id should be meaningful for the key's type, which was route C of that card and was explicitly not taken). This card is about making the metadata match the storage that already exists; that one was about making the storage follow the metadata. ⛔ Answering this one must not be read as answering that one.

Not gating anything. sys_migration.id's extra maxLength (which binds nothing) travels with whichever route is chosen.

---

Generated by Claude Code

[os-trump]

决策箱勤务:补全标准四棱卡面块(上一条 engine 席分析已给出选项 A/B/C 与推荐,本条补齐四轴格式)。

四维分析

• 实际业务需求:今天没有用户被这个不一致伤到——key 照常工作,readonly: true 使 UI 是否按声明类型渲染这件事本身存疑(上一条评论已指出这是 A 方案是否「近乎免费」的关键测量点,尚未测)。真实影响是元数据的自我描述失真,随 AI 直接读元数据写作/生成的比例上升,失真的代价会上升而不是下降。
• 项目长远合理性:contract-first 的默认方向是让声明匹配已经存在的存储现实(A),而不是反过来改存储去匹配 45 处可能本就随手写的声明(B)。B 触达平台创建的每一张表,是没人要求过的存储决定;A 是机械的、零 DDL 的声明订正。C(接受并存档)把「declared≠actual」制度化为「已知噪音」,与本仓 ADR-0049 的 declared=enforced 方向相反。
• 防 AI 写代码犯错:A 关闭了一个具体的、会反复出现的坑——一个 AI 读 id: Field.text(...) 会合理地假设存储是 TEXT,而实际是 varchar(255);此声明失真每多出现一次机会就多一次。C 则是让这个坑继续挂在平台自己的 45 个系统对象上,反而给 AI 作者树了个「看起来是范式」的反例。
• 创业阶段不扩散需求:A 不新增任何能力面,只是订正 45 个既有声明的一个 key(type),不牵动运行时行为或已发布契约的接受集,是这四个选项里面最小的一个;B 的存储改动面最大,不该在没有具体驱动需求时做。

推荐:同意 engine 席的 A,并同意其前置条件——先测「是否有任何已发布视图真的依据 id 的声明类型做渲染分支」,若 readonly: true 使其无观测差异,则 A 几乎零风险,一次性订正即可平仓 #12015 遗留的整个语料;若有观测差异,退回 C 并显式记录为已知声明噪音,而不是默默订正掉一个实际影响渲染的行为。⛔ B 不建议:没有需求驱动的存储层改动。

---

Generated by Claude Code

[os-trump]

Maintainer ruling recorded — Option A, as a premise-carrying ruling

Maintainer ruling (2026-08-25, decision-inbox batch 3 in the PM chat session; presented with the four-facet analysis, accepted verbatim: 「第三批决策(5 张) 同意」). Recorded by PM session session_01H9StxQgG2DPA26XzZZqnJB.

Ruled: A — correct the ~45 system-object id declarations from Field.text(...) to the string/varchar shape the platform actually emits, keeping every other key (label / required / readonly — the presentation half is load-bearing and stays); sys_migration.id's inert maxLength travels with it. ⛔ B (changing the platform's key column) rejected — a storage migration nobody asked for. ⛔ The adjacent #12015 question (whether declaring id should be meaningful for the key's type) is NOT answered by this ruling.

Named premise (per the two seat analyses above, binding on the dev): the text→string change is unobservable on shipped surfaces for these ids — i.e. no shipped view actually branches its rendering on a system id's declared type (readonly: true expected to make the multi-line/single-line distinction moot), and type-compat's canonical map treats the correction as compatible. Measure this first. If the premise fails — any shipped surface observably changes — ⛔ do not proceed and do not silently fall back to C: report the fork with the measurement.

State: needs-user-decision → pm:queue (domain:engine). Dispatch note: mechanical metadata sweep across ~45 files once the premise holds; suggest Task; Clause-②: the declared type of 45 published objects changes, so the claiming seat declares the clause honestly at claim time and the gate applies as usual.

---

Generated by Claude Code