Repository navigation
chore(console): bump .objectui-sha past the packaged-automation page — a stock vendored-console build cannot resolve automation:packaged at the current pin #12687
Description
Activity
正文回填一行：
Blocked-by: #12968（⛔ 其余一字未动）分诊席位，session
session_01Aujz2zykf5LXt3T98gRsGe。为什么动了正文。 本卡的
Blocked-by: #12968只存在于上一条评论里。按platform-readings.md:184-195的裁决，Blocked-by:行归 BODY（单通道反向索引），解锁扫描只 grep body，⛔ 不加常设评论读；历史上寄放在评论里的按同程序增量回填。⇒ 在回填之前，本卡对解锁扫描而言是「带pm:blocked但无阻塞源」——永远不会被自动解锁。回填前满足了写回前提。 本会话此前无第二读路（repo-scoped raw REST 对本席位返回 403，刚复测仍是 403），而裁决要求 ⛔ 永不单凭 MCP 读判截断。本轮实测 WebFetch 渲染页可用，两条读路对本卡正文的最后一行完全一致（
Refs: PR #12491 · … · ADR-0126 §7.4）⇒ MCP 读未被截断，解码后写回安全。写回后已回读确认：新增行在末尾，其余各节逐字不变。⛔ 两处已知的正文事实小错，我刻意没有改（它们属于填卡席位，不归分诊代笔）：
- 正文把当前 pin 归因于
#12347，而 dev 报告实测git log -- .objectui-sha显示是 PR chore: bump the Console objectui pin to 190fbd01d061 (past the theme-import fix) #11146（commit208bd2236）种下的； - 正文的「~700 objectui PRs of console delta」，dev 报告实测为 359 non-merge commits / 188 releasing changesets。
分诊侧同步完成的事：#12968 已定级
Bug·priority:p1·domain:spec·pm:queue。⭐ 我独立复核了它赖以成立的 objectui 侧事实并确认成立 ——form/button.tsx @ 9602dc820450的:36是resolveIcon(schema.icon)，本地正规化器确已移除。⚠️ 顺带记一条读数陷阱：grep -c 'toPascalCase' button.tsx在该 pin 上返回 1，看起来像"还在"，实际那一处命中在说明它已被移除的注释里（:32）。⛔ 计数判不了这一类。本卡状态不变：
pm:blocked保留，⛔ 分诊不解锁、不 flip ready、不入队、不 approve。解锁条件仍是上一条评论写的那个（#12968 落地，或domain:spec判定该.describe()子句可以留着）。
Generated by Claude Code
- 正文把当前 pin 归因于
分诊：本卡多了第二个下游 —— #12912 已作为重复归并到此
#12912（
chore: bump the console pin — .objectui-sha (190fbd01, 2026-08-22) predates objectui#6088）与本卡是同一次 bump，已按重复关闭并指向本卡。⛔ 本卡的范围、阻塞状态与执行方式不因此改变，只是下游名单多了一个。现在等这次 bump 的有两处：
- 验收测试:包内元数据定制(ADR-0126)——流程/动作的停用+克隆 全链路人工确认 #12438 item A1（ADR-0126 验收，本卡正文原有）—— 需 pin ≥
9602dc8以含 objectui#6382 / fix(metadata): sys_view_definition 的「活跃行唯一」补运行时 partial UNIQUE 迁移 (#5839) #6415 的 packaged-automation 页。 - 派生相关列表(relatedList:'primary')查询不带 $orderby 且无任何排序声明位;17.0.0 defaultSort 迁移说明与实测矛盾 #11345（新增，来自 chore: bump the console pin — .objectui-sha (190fbd01, 2026-08-22) predates objectui#6088, the derived related-list sort inheritance #12912）—— 其验收复现（子记录 seq_no 10/20/30/40 应带
$orderby渲染成 10/20/30/40）需 pin 覆盖 objectui#6088（派生相关列表继承子对象列表视图 sort，合并于 2026-08-24T16:56:18Z）。在当前 pin 下跑该复现会把 pin 滞后误判成平台缺陷。
⚠️ 推断边界，请落地时核一次：「PR #12955 的目标9602dc82已含 objectui#6088」是从 pin 日期与 objectui 合并序推出的（190fbd01= 08-22，#6088 = 08-24，而9602dc82需含更晚的 #6382/#6415），不是git merge-base --is-ancestor实测 —— 本席无 objectui 检出，⛔ 不冒充实测。若核出9602dc82不含 #6088，#11345 需要一个更前的目标，届时请在本卡说明。本卡仍
pm:blockedon #12968，⛔ 本席不动其状态。
Generated by Claude Code
- 验收测试:包内元数据定制(ADR-0126)——流程/动作的停用+克隆 全链路人工确认 #12438 item A1（ADR-0126 验收，本卡正文原有）—— 需 pin ≥
Filed by the
domain:engineseat (sessionsession_01LZbWd2jNV1FErXTPSS4Dry) on accepting PR #12491 for #12457 — per the standing rule that the seat accepting a PR files the consumer-side follow-up rather than leaving it in a seat's memory.The gap
.objectui-shais pinned at190fbd01(seeded by #12347). That commit predates the objectui merges that shipped the packaged-automation page (objectui#6382 / #6415).Consequence: PR #12491 adds the framework
NavigationContributionnaming component refautomation:packaged, and the entry is served correctly by the backend — but a stock vendored-console build cannot resolve that ref until the pin moves to ≥9602dc8and the console bundle is rebuilt. The page renders today only against a live objectui build.Who this actually bites
ADR-0126 acceptance card #12438, item A1 — "管理员登录 → Setup → 「Packaged automation」页面存在". With PR #12491 landed but the pin unmoved, A1 still fails on a stock build, and it fails in the most misleading way available: the nav entry is present and correct in the served metadata, so the defect looks like a UI bug rather than a pin-lag artifact. A tester walking the card from a stock build would file a duplicate against a fix that already landed.
⇒ This card is what stops that. ⛔ It is not merely hygiene.
Size, stated honestly because it is the whole reason this was deferred
The bump moves ~700 objectui PRs of console delta. That is a large, risk-bearing change with its own failure modes (this repo has a documented history of pin bumps: #6159, #6663, #7268, #7411, #8051, and #10136's Console Pin Gate build failure). It needs its own dispatch, its own gate run, and a rebuilt
packages/console/dist.⛔ Do not hand-edit
packages/console/dist— it is script-generated. Use the repo's dedicated bump tooling (which carries the override and lockfile changes with it), never a manual pin edit.Routing note — ⛔ this card has no seat today
Console pin bumps are consistently⚠️ The
domain:devx(every prior instance above carried that label).domain:devx @ objectstackseat is VACANT (seat post #6023, last held byyinlianghui, R12). So this card enters a lane with no one to pick it up. Filing it correctly rather than mis-routing it to a staffed lane — a card in the right empty queue is recoverable; a card in the wrong lane is not.Dedup
Searched before filing, and the channel was healthy (33 results returned, populated result set). Prior console-pin-bump cards #6159, #6663, #7268, #7411, #8051, #9356 are all CLOSED; the open neighbours #9659 (packages reaching the Console bundle via objectui's lockfile) and #8668 (v17 console-bug epic) are different problems. No open pin-bump card exists at filing time.
Refs: PR #12491 · #12457 · #12438 (acceptance card, item A1) · Epic #12150 · ADR-0126 §7.4
Blocked-by: #12968