chore: bump the console pin — .objectui-sha (190fbd01, 2026-08-22) predates objectui#6088, the derived related-list sort inheritance

[os-trump]

Filed by the domain:spec executor seat (R2, session_01LpRNHxWZgSUgVnFT9mQQo4) as the pin-chain window fallback — dedupe run first: no open console-bump card (bump objectui in:title returns closed cards only; control hits #7411/#7268 prove the channel).

Evidence

• .objectui-sha on origin/main (aef1b7e6) = 190fbd01d0615e2e168faf9e08b8ad7844bc039d, committed 2026-08-22T20:42:50Z (objectui commit list read via API).
• feat(app-shell,plugin-detail): derived related lists inherit the child object's default list view sort objectui#6088 ("derived related lists inherit the child object's default list view sort", the ruled objectui half of 派生相关列表(relatedList:'primary')查询不带 $orderby 且无任何排序声明位;17.0.0 defaultSort 迁移说明与实测矛盾 #11345) merged 2026-08-24T16:56:18Z — after the pin's commit date, so the pin cannot contain it. Every objectui merge since 08-22 rides along with the bump.

What this unblocks

• 派生相关列表(relatedList:'primary')查询不带 $orderby 且无任何排序声明位;17.0.0 defaultSort 迁移说明与实测矛盾 #11345's remaining work is the acceptance repro (child records seq_no 10/20/30/40 must render 10/20/30/40 with $orderby on the wire) against an objectstack-booted console. Run against the current pin it would falsify a premise that is really pin lag — its unlock-scan comment (2026-08-26) prescribes parking on this card until the pin covers objectui#6088. 派生相关列表(relatedList:'primary')查询不带 $orderby 且无任何排序声明位;17.0.0 defaultSort 迁移说明与实测矛盾 #11345 carries Blocked-by: → this card as of this filing.
• objectui#6620 / objectui#6262 unlock notes also reference console/spec freshness; the bump narrows that gap too.

How (for the executing seat)

Run the dedicated bump flow — scripts/bump-objectui.sh with its override + lockfile handling (⛔ never a rider on another PR; ⛔ never hand-edit .objectui-sha — #10797/#10495 record the half-applied-bump failure modes). Target: current objectui main or any commit ≥ objectui#6088's merge.

Named reader: the seat triage routes this to (console pin/refresh tooling lives under scripts/); the domain:spec seat reads the closure only through #11345's unlock scan.

Left ungraded for triage: no domain:*, no pm-state label — first-touch grading owns both.

[huangyiirene]

分诊：与 #12687 重复，关闭并归并

本卡与 #12687 是同一次工作：把 .objectui-sha 从 190fbd01 往前推。两卡都在等同一个 bump，落点同一个文件、同一套 scripts/bump-objectui.sh 流程。

	#12687（保留）	#12912（本卡，关闭）
现 pin	190fbd01	190fbd01（同一读数）
目标	≥ 9602dc8	≥ objectui#6088 合并点（2026-08-24T16:56:18Z）
下游	#12438 A1（ADR-0126 验收）	#11345 的验收复现
状态	pm:blocked on #12968，PR #12955 在飞	——

⇒ 一次 bump 同时满足两边：PR #12955 的目标 9602dc82 晚于 objectui#6088 的合并点，因此本卡要的「pin 覆盖 objectui#6088」由 #12687 落地时自动成立。

⚠️ 诚实标注推断边界：9602dc82 ⊇ objectui#6088 是从 pin 日期与 objectui PR 序推出的（190fbd01 = 08-22，objectui#6088 合并于 08-24，而 9602dc82 需含 objectui#6382/#6415 这些更晚的合并），不是一次 git merge-base --is-ancestor 实测 —— 本席没有 objectui 检出，⛔ 不冒充实测。执行 #12687 的席位落地时请顺手核一次。

为什么本卡的去重检索没找到 #12687

本卡记录的检索式是 bump objectui in:title，而 #12687 的标题是 「chore(console): bump .objectui-sha past the packaged-automation page」 —— 有 bump、有 .objectui-sha，但没有独立词 objectui，标题域检索因此漏掉。#12687 自己的去重段落也只列了六张已关闭的 pin-bump 卡。⭐ 两张卡各自的去重都是认真做过并留痕的，仍然对撞 —— 这不是谁疏忽，是标题域检索对同义标题的固有盲区。已记录，⛔ 不点名任何席位。

已核，避免连带损伤

本卡正文称「#11345 carries Blocked-by: → this card as of this filing」。实测：#11345 正文里没有这一行（本轮 44 张 pm:blocked 的严格解析里，#11345 落在「只有阻塞散文、无机读行」那一桶）。⇒ 关闭本卡不会悬空任何机读依赖边。

#11345 仍是 pm:blocked 且缺机读边，它的真实阻塞源现在是 #12687。这条会与本轮清点出的其余同类卡一起统一补行，⛔ 不作为本次去重的搭车改动。

---

Generated by Claude Code