`views:` 数组的三个门形状判断不一致:栈级 schema 只收容器、授权 lint 按记录门映射、运行时注册循环全收 —— declared ≠ enforced 的「运行时更宽」向

[os-zhuang]

#4959 前提实测(PR #5319 rider,2026-08-04)的两条残余观察,原单前提已证伪关闭,残余按 finding 纪律归档。实测证据全文见 #5074 验收链与 PR #5319 正文「Rider」节。

观察一:授权 lint 与栈级 schema 对同一数组的映射不一致

metadata-authoring-lint 把 views 集合映射到 view 元数据类型 schema(接受 ViewItem 的 union),而 ObjectStackSchema.views(stack.zod.ts:250)只收容器。方向良性(parse 更严且拒绝带处方:「viewKind belongs to a single VIEW, not to the container. Wrap it: defineView({...})」),但 lint 的预解析告警够不到这类拒绝 —— 作者要到 parse 才知道。

观察二:运行时比 schema 宽

objectql/engine.ts(~:1999)的注册循环把 views: 数组里每一项都注册为 view 类型,仅当 isAggregatedViewContainer 为真时额外展开 —— 一个 ViewItem 放进 manifest 的 views: 数组在运行时注册成功,而 defineStack 会拒。今天无用户可撞(授权门先拒且带处方),但属「声明 ≠ 生效」的运行时更宽向,与 #3950 同型。

持有理由

两条今天都无用户可见伤害;观察二在 manifest 绕过 defineStack 的路径上才成立(该路径本身受 #5086/#5311 一族门治理演进影响)。发现分诊轮按过时前提检查后定级。

关联:#4959(已关,前提证伪)、PR #5319(实测)、#5311(直写第三通路)、#3950。

[os-zhuang]

分诊轮判级(spec 车道 PM,session_018fxLGQdatPbBUvCgiVxg6D,2026-08-05):持有(finding 留)。理由:三门形状不一致的收敛方向(栈级收紧 vs 运行时对齐)未定,且「运行时更宽」向意味着收紧会拒存量 —— 需与 #4001 战役 view 面的批次同做以带全套 guidance/conversion 纪律,不宜单点动。重启条件:#4001 view 面批次开列时并入。

---

Generated by Claude Code

[claude]

发现分诊轮(#4949 纪律):持有(留 finding + domain:spec),08-05 判级维持。本轮产出是一条重启条件可达性预警 —— 现在还不构成重新锚定,但再拖一步就会变成 #5299 那种「谁也退不出的状态」。

过时前提检查(origin/main @ 9e3709a)

两条观察的机制面未见变化,持有理由(「运行时更宽」向、收紧会拒存量、无用户今日可撞)不变。

⚠️ 重启条件的可达性预警

08-05 写的重启条件是「#4001 view 面批次开列时并入」。核 #4001 现状:

• 该伞单仍 open(pm:queue + pm:dispatched + protocol:breaking + domain:spec);
• 但其时间线最后一次批次派发是 2026-08-04 的 批 19 / 批 20,自陈为「campaign 剩余 authorable strip 的最后两组」(data/app.zod.ts + data/object.zod.ts 内层块),PR feat(spec)!: object 内层块拒绝未知键 —— 13 站点收紧,2 个站点依据实测保留 (#4001 批 19/20) #5250;其后未见任何 view 面批次开列,伞单自陈状态是「待终局重测后收口」。

⇒ 若 #4001 就此收口而始终不开 view 面批次,本单的重启条件将永远不触发。

处置(本轮不改判,设一个明确的复查触点)

• 暂不重新锚定:未知键静默剥离仍是全仓默认:把 #3405 的 strict 收紧从一个 schema 推广到整个可授权面(ADR-0078 完整性闸门) #4001 尚未收口,view 面批次仍有可能作为终局重测的产物开列 —— 现在改锚定是抢跑;
• 复查触点:未知键静默剥离仍是全仓默认:把 #3405 的 strict 收紧从一个 schema 推广到整个可授权面(ADR-0078 完整性闸门) #4001 关闭之时。届时若仍无 view 面批次,本单须由发现分诊轮当轮重新锚定(候选新锚:与 saveMetaItem 的 direct-active 写入是 api 的第三条门外通路 —— 命名空间门(ADR-0121 D1/D2)与去重门在这条路上无人跑 #5311「直写第三通路」一族的门治理批次并案,或独立晋级为「三门形状对齐」的收敛单),⛔ 不得让它继续挂在一个已经不会发生的条件上;
• 本条预警即为那时的现成依据,省一次重新推导。

关联:#4001(伞单)、#5311、#3950。

本评论来自分诊座位 Routine(#5474 试点),不构成认领。

---

Generated by Claude Code

[claude]

Findings triage round (#4949 discipline): HOLD (finding + domain:spec kept). Two concrete updates: the cited line number has drifted, and last round's reachability warning on the restart condition got worse, not better.

Stale-premise check (origin/main)

Observation two's mechanism is intact but has moved: the registration loop that registers every item in a manifest views: array as type view, expanding only when isAggregatedViewContainer is true, is now at packages/objectql/src/engine.ts:2334 — the issue body cites ~:1999. Worth correcting on the record, because engine.ts took 5 commits since 2026-08-06T20:00Z (148d451b, 13630842, ee3bde1b, eda599ea, 2680cd37) and a stale line number invites a future reader to conclude the premise died. It did not: all five are transactions / migration / seed work (#5351, #5696, #6063, #4795, #5979), none touch the views loop. The "runtime is wider than the schema" asymmetry is unchanged.

⚠️ Restart-condition reachability — the warning is now stronger

Last round (08-06 22:56Z) flagged that the 08-05 restart condition — "fold in when #4001 opens its view-face batch" — may never trigger, and set the recheck touchpoint at #4001's closure. State of #4001 today:

• still open, still pm:queue + pm:dispatched, still assigned;
• last updated 2026-08-04T12:22:25Z — no timeline movement in ~3 days, against a repo averaging ~18 merges a day.

So the anchor issue is not merely "hasn't opened a view-face batch yet"; it has gone quiet entirely. That does not license re-anchoring this round (the touchpoint is #4001 closing, and a stalled issue has not closed), and stale-claim handling on #4001 is the executing seat's business, not this seat's — this seat does not touch claims. But it sharpens the standing instruction for whichever round sees #4001 close: re-anchor that round, do not roll it forward again. Candidate anchors recorded last round remain the two on file (fold into the #5311 "third direct-write path" gate batch, or promote standalone as a "three gate shapes align" convergence issue).

⇒ HOLD this round; no exit condition invented, none rolled over silently.

本评论来自分诊座位 Routine(#5474 试点),不构成认领。

---

Generated by Claude Code

[os-project-manager]

Findings sweep (maintainer-authorized one-off, 2026-08-07 — registered on #6015): hold confirmed. Runtime-wider-than-schema, but the authoring gate rejects first with a prescription, so no author reaches the wide path today. Restart: when the #5086/#5311 manifest-write governance opens that bypass face, align the runtime registration loop in the same change.

---

Generated by Claude Code

[os-zhuang]

Findings triage round: HOLD maintained (finding + domain:spec kept). Stale-premise check @ origin/main b88f5e8 — the mechanism is intact; both anchors drifted, recorded so a future reader doesn't mistake line noise for a dead premise.

• Observation 1: the stack-level schema still accepts containers only — but the cited file is gone: packages/spec/src/data/stack.zod.ts no longer exists on main. The field is now packages/spec/src/stack.zod.ts:251 (views: z.array(ViewSchema)), and ViewSchema (packages/spec/src/ui/view.zod.ts:1920) is still the strict container shape ("surface: 'this view container'"). Same asymmetry, new address.
• Observation 2: the runtime registration loop still registers every views: item under type view and only additionally expands aggregated containers — now at packages/objectql/src/engine.ts:3050 (was :2334 at the 08-07 grading, ~:1999 in the body). Runtime-wider-than-schema unchanged.
• Restart condition (08-08 sweep's re-anchor) unchanged and not fired: when the metadata: allowRuntimeCreate:false is not enforced — PUT /meta creates job and agent items the registry declares code-only #5086/saveMetaItem 的 direct-active 写入是 api 的第三条门外通路 —— 命名空间门(ADR-0121 D1/D2)与去重门在这条路上无人跑 #5311 manifest-write governance opens that bypass face, align the runtime loop in the same change. Touchpoint watch: 未知键静默剥离仍是全仓默认:把 #3405 的 strict 收紧从一个 schema 推广到整个可授权面(ADR-0078 完整性闸门) #4001 is still open and still quiet (no timeline movement since 2026-08-04) — the 08-07 standing instruction holds: the round that sees 未知键静默剥离仍是全仓默认:把 #3405 的 strict 收紧从一个 schema 推广到整个可授权面(ADR-0078 完整性闸门) #4001 close must re-anchor that round, not roll forward.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[claude]

Findings round (periodic re-verification): HOLD maintained (finding + domain:spec unchanged). Re-checked @ origin/main 603cab8: packages/spec/src/stack.zod.ts:251 still views: z.array(ViewSchema) and the strict container prose survives with line drift only (view.zod.ts:1920 → :2221, same 'this view container' surface). The three-gate asymmetry the card records is intact; restart conditions unfired.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[claude]

Findings round (quota re-verification): HOLD maintained (finding + domain:spec unchanged). Re-checked @ origin/main a76a3af: packages/spec/src/stack.zod.ts:251 still views: z.array(ViewSchema); the strict container prose drifted view.zod.ts:2221 → :2230 ('this view container', same surface); the runtime registration loop (isAggregatedViewContainer expansion) drifted engine.ts:3050 → :3722. The three-gate asymmetry the card records is intact; restart condition (the #5086/#5311 manifest-write governance opening the bypass face) unfired; #4001 touchpoint unchanged (still open).

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[claude]

Findings round (quota re-verification): HOLD maintained (finding + domain:spec unchanged). Re-checked @ origin/main c546c89: packages/spec/src/stack.zod.ts:251 still views: z.array(ViewSchema); the strict-container prose drifted again view.zod.ts:2230 → :2328 ('this view container', same surface); the runtime registration loop is at engine.ts:3722 (isAggregatedViewContainer). Three-gate asymmetry intact; no evidence on the card that the #5086/#5311 restart condition fired. Held.

本评论来自分诊座位 Routine(#5474 试点),不构成认领。

---

Generated by Claude Code

[os-zhuang]

Findings triage (cadence re-check): HOLD — stays finding.

Premise re-verified on origin/main @ a3c0865: stack.zod.ts:251 still container-only (views: z.array(ViewSchema)), and the engine registration loop still carries the wider isAggregatedViewContainer path — the three-door inconsistency stands. Still no user-visible harm: the authoring door refuses first with a prescriptive message, and the wider runtime path only matters on manifests that bypass defineStack, a route governed by the #5086/#5311 gate family whose evolution this card correctly waits on.

本评论来自分诊座位 Routine（#5474 试点），不构成认领。

---

Generated by Claude Code

[os-zhuang]

Findings triage round, 2026-08-11 (maintainer-directed). Graded: hold — no user-reachable harm (the authored path refuses with a prescription); the runtime-wider divergence only matters on the direct-manifest third path, which the #5086/#5311 gate family is still reshaping. Restart: #5311-family lands (re-check whether the registration loop is still wider than defineStack).

---

Generated by Claude Code