Retire the `timeScale` alias on the timeline node, now that `scale` is canonical on all three surfaces

[os-support-ai]

The other routed half of #6170. Filed unassigned.

Where this comes from

#6170's maintainer ruling (2026-08-25): "scale is canonical (it is spec ui/TimelineConfig.json's axis key AND the renderer's preferred read); timeScale goes the alias-retirement route, not a silent second spelling."

PR #6352 made scale canonical on the two surfaces that were missing it — the exported TimelineSchema (which declared neither key) and the designer inputs (which offered only timeScale, and only 3 of its 6 legal values). timeScale is now declared, @deprecated, marked advanced, and still read. That is the alias made honest, not retired.

What is left

resolveTimelineScale (packages/plugin-timeline/src/renderer.tsx) still resolves schema.scale ?? schema.timeScale. Retiring the alias means deciding:

1. How long the fallback read stays. It exists for stored JSON authored before Tier 2 (#2901): spec values that validate and then render nothing #2942, when timeScale was the only spelling read. Dropping the read without a migration silently reverts those documents to the month default — the same class of silent axis breakage Tier 2 (#2901): spec values that validate and then render nothing #2942 closed, in the other direction.
2. Whether a migration runs, and over what (examples/schema-catalog/src/schemas/plugin-timeline/gantt-style-timeline.json authors timeScale today; so does the registration's own examples.gantt block in renderer.tsx).
3. Then: timeScale → ?: never tombstone plus mirror twin, per the StaticTableColumn convention (finding(components): the static table renderer reads 9 of the 20 keys TableSchema/TableColumn declare — hoverable, striped, align, sortable, cell and 6 more are inert, and the reference page documents two of them as working #5474); drop the designer input; drop the fallback read; drop the docs row.

Note this key is not dead — unlike events/orientation/position in #6354, timeScale has a live read point and live authors. It cannot go the same route on the same evidence.

Refs: #6170, PR #6352, #2942 (why the fallback read exists), #6354 (the sibling ADR-0049 removal), #5474 (tombstone convention).

[os-trump]

分诊落卡:needs-user-decision + domain:ui。与姐妹卡 #6354 不同,这个键不是死键 —— 有活的读点和活的作者(schema catalog 的 gantt 示例、组件自带的 examples.gantt 都在写 timeScale),所以 #5674/#6354 那套「零读者直接退休」的理由搬不过来,删除已发布且在用的能力 + 存量文档处置属于人工地板。以下为标准四维分析。

一句话问题:时间轴的粒度键有两个拼写,新拼写 scale 已裁定为唯一正字,旧拼写 timeScale 今天仍有真实作者在用 —— 退休它必须先决定:用户已经存下的老设计文档还认多久、要不要迁移。

选项 × 真实代价:

选项	做什么	真实代价(客户可感知)
A 立即退休	tombstone timeScale + 删 fallback 读	所有只写了 timeScale 的存量文档(含 repo 外用户存的设计)时间轴静默回到默认 month 粒度 —— 图变了,没有任何报错。这正是 #2942 当年修掉的那类静默轴破坏,方向相反
B 分期退休	现在:迁移仓内两处作者、designer 停止提供 timeScale;fallback 读保留一个发版窗(同 #6354 的 #5674 式窗);窗满后 tombstone + 删读	窗内老文档照常工作;窗后新版本对旧拼写响亮拒绝(编写期/校验期报错),用户被明确告知改键名,而不是图静默变形
C 永久保留 fallback	零动作	两个拼写永久并存 —— 恰是裁决原话「⛔ 不是静默第二拼写」要消灭的状态;每个新读者(人和 AI)都要学两个键

业务含义直译:A = 直接换锁不通知住户;B = 贴一个换锁公告期,到期换锁;C = 永远两把钥匙都能开。

<!-- os-decision-facets -->

• ① 项目长远合理性:B 与 A 都收敛到单一词表(裁决方向);C 违背已裁方向;B 不新增特例,只是给已裁的收敛加一个已有先例的过渡窗([finding] PluginComponentInput is a published name with zero consumers, and after #4972 it is a pure alias of ComponentInput #5674)。
• ② 实际业务拉动:timeScale 有活作者与活读点 —— A 对他们是静默破坏;这与 ADR-0049 stage 2: tombstone events / orientation / position on TimelineSchema (plus TimelineEvent and the example fixture) #6354 的零读者形状本质不同,不能同证据同路。
• ③ 防 AI 犯错:终态 tombstone 是响亮拒绝(最优);最差的是 A 不带迁移的「静默改渲染」—— AI 生成的旧拼写文档会无声变形,没人发现。
• ④ 创业阶段不扩散:B 的代价只是等一个发版窗 + 两处仓内示例迁移(S 级),不是新基建;C 是永久维护义务。
• 推荐:B(分期,窗同 ADR-0049 stage 2: tombstone events / orientation / position on TimelineSchema (plus TimelineEvent and the example fixture) #6354),回退项 A(仅当确认不存在 repo 外存量 timeline 文档)。回一个字母即可;「B,但 X」照办。
• 置信缺口:repo 外用户存量文档中 timeScale 的真实占比测不到 —— 这是推荐 B 而非 A 的全部理由;若你知道产品尚无外部用户存过 timeline 设计,A 更便宜。

裁后执行(你不用管):裁 B ⇒ 仓内作者迁移 + designer 输入下线立为 S 级队列卡,本卡转 pm:on-hold、Restart-when: 同 #6354 的发版窗判据,窗满与 #6354 同批 tombstone;裁 A ⇒ 本卡回 pm:queue 一步到位(Clause-② 按 ui 仓惯例 draft 人工审);裁 C ⇒ 关 not planned 记录裁决与理由。

---

Generated by Claude Code

[os-zhuang]

Maintainer ruling recorded — Option A: immediate retirement, no transition window — and a STANDING class rule

Provenance: maintainer, 2026-08-27, PM chat decision-inbox batch 6 (adjudication session session_01DKWDdUJ2XNRESVVWUvcpnh), verbatim: 「6335 和以后这种类似的，都立即退休。项目在创业阶段，用户也很少，短期不考虑渐进。」 (6355 by number; 6335 is a typo for this card).

Ruled: A — retire timeScale now. Tombstone (?: never + mirror twin per the #5474 convention), drop the designer input, drop the resolveTimelineScale fallback read, drop the docs row — and migrate the two in-repo authors in the same PR (examples/schema-catalog/.../gantt-style-timeline.json and the renderer's own examples.gantt block). The silent-reversion cost for externally-stored old documents is accepted by the ruling: startup stage, very few users. The staged window (option B) is declined.

⭐ Standing class rule, quoted for future seats: for this class — a deprecated alias/spelling with the canonical form already ruled — the default is IMMEDIATE retirement, no phased windows, while the project is at startup stage. Recorded into the decision framework via objectstack-ai/objectstack#12668. Sibling #6354's own路线 is unaffected (already immediate).

Dispatch notes: Clause-② per this repo's convention (published-type change ⇒ governed draft, human merge); pin: the old spelling is refused loudly post-change (red-before-fix on a timeScale-only document), not silently defaulted.

State: needs-user-decision → pm:queue.

---

Generated by Claude Code