[objectstack-fleet]

Part of #27055 — this lands the record page v3 layout. The two fenced read points stay for #27069: the related cards' default order (primary first, then derived order, without reading relatedLists) and the body tables' placement (after the first field group, without a fieldGroups placement entry).

Clause-②: no
Metadata-protocol: none

维护者速读

• 改了什么：没有指定页面的对象，记录页换成 v3 布局。详情区无边框，空区段折成一行。时间线合成一条流，带「全部/活动/讨论/变更」筛选。关联区是紧凑卡片，读者可拖动、折叠、隐藏，还能 ⤢ 原地放大。主从子表直接嵌在详情里。
• 为什么改：执行 console record page v3: frameless detail sections, one merged timeline (discussion + activity + field changes), compact related cards, header 1 primary + 2 secondary + ⋯ — the synthesized default page, drawn from the object's roles; the dead BuildPageOptions hints go #27055 已批准的 v3 设计。删掉了 ADR-0085 判死的页面开关和 rightRail 插槽，把三处重复的历史、动态、讨论入口并成一个。
• 风险与回滚：只改渲染层，作者写的元数据不变。BuildPageOptions 删字段属于 TS 层面的破坏性变更，控制台内部没有调用方传这些字段。回滚就是 revert 本 PR。读者的卡片排列存在已有的 workspacePreference 里，回滚后不会被读取，没有副作用。
• 先看：ui/packages/app-shell/src/views/RecordDetailView.tsx（放大的 URL 往返、排列偏好、字段变更并入时间线），ui/packages/plugin-detail/src/synth/relatedArrangement.ts（排列合并规则），ui/packages/plugin-detail/src/RecordPageColumns.tsx（三栏模板和放大视图）。
• 两分钟验证：打开下方证据分支里的 contact-1440-three-columns.png，应看到「详情｜时间线｜关联卡片」三栏，时间线里有一条灰色的字段变更行和两条评论。
• 需要你做的：人工评审并合并。本 PR 改动 5828 行，超过 3000 行的人工合并线。

What changes

The synthesized default record page (an object with no assigned record page) takes the v3 layout. Authored pages are untouched apart from the shared header and the renderer faces noted below.

• Header. One filled primary action, two outline actions, the rest in ⋯. Refresh is the first item of ⋯ (no separate ⟳ button). Up to six highlights, as an equal grid.
• Details. Frameless sections in one to three columns. All-empty sections fold into one line at the foot. The created / updated / owner / id line closes the details column.
• Timeline. One stream merging comments, sys_activity rows and audit field changes, newest first. The composer is on top, the chips are All / Activity / Discussion / Changes, system entries are one muted line, and a "View all N →" button shows the rest. The History tab, the Activity tab and the discussion footer are retired on this page.
• Related column. Compact cards (title, count, ＋, ⤢, up to three rows of name plus one chip, no table header, no View All footer) in a fixed 320 px column. The columns are 1.25fr : 1fr : 320px.
• Reader arrangement. Drag (desktop), Move up / Move down / Collapse / Hide from the card menu, and "N hidden · Show" at the foot. It is stored in the console: one workspace-preference module (record open mode, drawer width, timeline / related column toggles) read per user × object, with a shared panel-toggle toolbar on the record page — defaults derived from the object, never metadata #27052 workspace preference under record.related.arrangement, scope object:<name>. The value is { v, order, collapsed, hidden, basedOn, seen }. A default-order change shows "Default order updated · Restore default". A new relationship lands after its nearest default neighbour with a "New" badge for 48 hours. The tabbed tier's Related tab follows the same arrangement.
• Enlarge in place. ⤢ opens the list full width under ?related=<object>.<field>. Esc or ‹ Back returns.
• Body tables. A master_detail FK declaring inlineEdit, or relatedList: 'primary', is drawn as a table after the first field group. It opens on ten rows with a totals line and has ⤢.
• Tabbed tier (drawer, narrow widths): Details / Timeline / Related / (Approvals). Timeline is second for an object whose timeline is on by default (console: one workspace-preference module (record open mode, drawer width, timeline / related column toggles) read per user × object, with a shared panel-toggle toolbar on the record page — defaults derived from the object, never metadata #27052's derivation), last otherwise. Attachments sit in Related.
• BuildPageOptions loses hideHighlights, hidePath, showReferenceRail, hideReferenceRail, hideRelatedTab, relatedLayout, recordChrome, showActivity, history and slots.rightRail (TypeScript-only break, named in the changeset with its ADR-0087 marker).

Fence read points for #27069:

• Default order. synthParts related ordering in RecordDetailView.tsx, commented as the fence.
• Body-table placement. bodyTablePlacement in buildDefaultPageSchema.ts, commented as the fence.

Tests

• New suites cover the face, the arrangement merge rules, the card stack (drag, menu, collapse, hide, enlarge, tabbed tier), body tables, body-table placement, and the timeline stream including its newest-first window. A last suite pins the retired hints as compile errors.
• Existing pins moved with the page: History and discussion-footer reads now open the Timeline tab, the header menu has Refresh first, the highlight cap is six, and the meta line sits in the details column.

Suite (local, under the verify lock)	Result
@object-ui/plugin-detail	331 files: 329 passed, 1 skipped, 2 failed on the first run and passed on rerun after the pin fixes
@object-ui/components	446 passed, 1 skipped
@object-ui/app-shell	1858 files: 1856 passed, 1 skipped, 1 failed on the first run and passed on rerun after the fix
console approvalRequestsDataSource.recordPage	passed
type-check components / plugin-detail / app-shell	clean

Acceptance notes

• Screenshots are on the never-merged branch claude/issue-27055-evidence-20261028: https://github.com/objectstack-ai/objectstack/tree/claude/issue-27055-evidence-20261028/evidence/27055
  • Shots: contact 1440 three columns, contact 1100 two columns, contact drawer, account 1440, opportunity 1440, related column after a drag, and the enlarged state.
  • There is no product object in this repo, so the opportunity (with its Line Items body table) stands in.
• Three columns at 1440 need the app sidebar collapsed. The tier threshold (1280 px page container, console record page: one page at two widths — three resident columns (details | timeline | related) at 1280 px and up, two columns with a collapsible related rail from 1024 px, today's tabs below that and in the drawer #26678) is unchanged.
• Accounts and contacts fold the timeline by console: one workspace-preference module (record open mode, drawer width, timeline / related column toggles) read per user × object, with a shared panel-toggle toolbar on the record page — defaults derived from the object, never metadata #27052's object-derived default. The shots turn the reader's switch on; the switch semantics are unchanged.
• Deviations:
  • The arrangement value carries a seen member, a first-seen stamp per id, as the clock for the 48-hour "New" badge.
  • Body-table totals are a summary line over the page's rows, not an in-table row.
  • Body-table collapse is per view, not persisted.
  • The host's Edit stays a labelled filled button outside the three-action cap.
  • The enlarged list keeps the full list page's "View All" link, for sort, filter and export. Only the card footer is gone.
• Out of scope, carrier spec: an object declares the business order of its related lists — relatedLists: ['task', 'event', …], an ordered list of child relationships like highlightFields is of fields; unlisted ones follow the derived order; a name that matches no inbound relationship is refused #27069:
  • The spec describe of relatedList: 'primary' still says "promoted to its own tab".
  • The spec describe of enable.trackHistory still says "Show the record History tab".
  • The generated reference docs repeat both describes.
  • These live under packages/spec/**, which this card does not touch. The hand-written security doc line is updated here.

Verification

• Gates. Every gate dispatch-gates.mjs --changed derives for this diff ran on the final tree. The --ran reconciliation verdict is below.
• Console type-check. It fails locally only on plugin packages outside the build closure (plugin-gantt, plugin-map, plugin-markdown, plugin-timeline, plugin-tree have no dist here). No error is in a file this PR touches. CI builds the full graph.
• Browser. Checked in a real browser against the app-crm example on a fresh database. The console dev server ran from this branch.

Gate reconciliation (66 derived, 66 run, all exit 0)

Run reconciliation — 66 derived, 66 run, 0 NOT-MEASURED, 0 UNRUN.
dispatch-gates --ran: 66 derived famil(ies) accounted for — 66 run, 0 NOT-MEASURED
changed lines: 5828 (+4516 / -1312; 78 files) vs the human-merge threshold 3000: OVER

🤖 Generated with Claude Code

https://claude.ai/code/session_01Q4EjjN14dHBs3CJce73zNm

[objectstack-fleet]

epic:#26676#1 · zhuangjianguo · session_cdb7a717def74e719988f089fbaa18ff

席位核对 · PR #27310 ← #27055 · epic PM session_cdb7a717-def7-4e71-9988-f089fbaa18ff · 2026-10-28T18:46Z

Verdict: ACCEPT — terminal four-piece, awaiting a human merge. Not governed by path (0 of 78 paths in the governed register; packages/spec untouched) but over the human-merge line: 5844 changed lines (+4524 / −1320, 80 files) against 3000 (check-governed-merges.mjs --pr 27310). No seat flips it ready, enqueues it or arms auto-merge until an account in GOVERNED_APPROVERS has APPROVED it; then this seat lands it through the queue. needs-user-decision on the PR, the final 维护者速读 as the next comment, review requested from the two authorized accounts.

What the seat read and accepts as built (head 349cd56; the cloud report on the card is comment 6473997555):

• Targets 1–10 on the synthesized page: header 1 primary + 2 outline + ⋯ (refresh moved into ⋯), up to 6 highlights; frameless 1–3 column sections, the empty-sections line, the created / updated / owner / id line at the details foot; one timeline stream (comments + sys_activity + audit field changes, chips 全部 / 活动 / 讨论 / 变更, composer on top, compact system lines, 「查看全部 N 条 →」) replacing the History tab and the discussion footer; compact related cards in a 320 px column (1.25fr : 1fr : 320px), reader drag / 上移 / 下移 / 折叠 / 隐藏 stored in console: one workspace-preference module (record open mode, drawer width, timeline / related column toggles) read per user × object, with a shared panel-toggle toolbar on the record page — defaults derived from the object, never metadata #27052's workspacePreference as record.related.arrangement ({ v, order, collapsed, hidden, basedOn, seen }, every merge rule on the card pinned in relatedArrangement-27055.test.ts, 20 cases); ⤢ enlarges in place through ?related=OBJECT.FIELD with Esc / ‹ back; master_detail + inlineEdit or relatedList: 'primary' lists as body tables after the first field group; tabs 详情 / 时间线 / 关联 / (审批); BuildPageOptions dead hints and slots.rightRail deleted (TS-only break named in the changeset).
• Seat walk-through on the console preview (this branch built on the seat's review worktree, HotCRM contact at a 1440 viewport, icon sidebar): three columns drawn; ⤢ opens the full-width list at ?related=crm_lead.duplicate_of_contact with the header kept and returns on Esc; the card ⋯ menu offers 放大 / 上移 / 下移 / 折叠 / 隐藏; hiding draws 「已隐藏 1 张 · 显示」; 下移 reorders; 折叠 collapses to the title row; timeline off folds the stream into the related column's foot; card titles and their menus' accessible names agree one to one. Screenshots in the seat's session notes and on the evidence branch claude/issue-27055-evidence-20261028 @ 4016ed1172.
• Fences, as dispatched (spec: an object declares the business order of its related lists — relatedLists: ['task', 'event', …], an ordered list of child relationships like highlightFields is of fields; unlisted ones follow the derived order; a name that matches no inbound relationship is refused #27069 landed after this session started and it did not read the seat addendum): the related cards' default order is read at RecordDetailView synthParts (primary first, then the derived order; relatedLists not read) and the body-table placement at bodyTablePlacement in buildDefaultPageSchema.ts (after the first field group; no fieldGroups entry). Both are named read points.
• Tests and gates (cloud run): plugin-detail 328 / 331 files with the two stale pins this change moved re-pinned, components 446 files, app-shell 1856 files with three authored-page cases re-pinned; red-before-fix evidence for the stream window (oldest-20 → newest-first); components / plugin-detail / app-shell type-check 0 errors; 66 / 66 derived commands exit 0 with the --ran reconciliation. CI: head 349cd5625c — 55 success / 8 skipped / 0 failure (1 cancelled: the Plan Test Core shards run superseded by the next push); every required context green, Test UI 16 / 16 shards, Build & E2E UI, Type Check UI, Lint UI.

Carried to the patch round that follows landing (one local round under this claim, together with #27241 and the #27069 fence half; not a REWORK — none changes the diff the maintainer is asked to approve):

1. Record page: the related switch decides whether the column exists, the panel toggles move into the header action row, and a 1440 px window with the sidebar is three columns #27241 (maintainer rulings of 2026-10-28, seat addendum 6468579228): related OFF ⇒ no column and no rail; the panel toggles as one segmented control in the header action row; a 1440 px window with the sidebar open is three columns.
2. The spec: an object declares the business order of its related lists — relatedLists: ['task', 'event', …], an ordered list of child relationships like highlightFields is of fields; unlisted ones follow the derived order; a name that matches no inbound relationship is refused #27069 fence half: read relatedLists for the default order and the field group's relatedList placement entry for body tables.
3. 「恢复默认顺序」 is drawn only as the hint when the author's default changed (RelatedDefaultChangedHint); the card asks for it whenever the reader has dragged — add the standing entry (column foot beside 「已隐藏 N 张」, or the card ⋯).
4. Acceptance notes agreed: body-table totals as a summary line; body-table collapse per view; the enlarged list keeps the list page's View All; refresh in ⋯; the 1440 three-column screenshot with the sidebar collapsed (the tier threshold is Record page: the related switch decides whether the column exists, the panel toggles move into the header action row, and a 1440 px window with the sidebar is three columns #27241's item 3).

Out-of-scope findings filed: #27312 (the .describe() of relatedList: 'primary' and enable.trackHistory still narrate the v2 page). HotCRM's lead / account / opportunity / case keep their authored kind: full pages, so this layout reaches contacts, tasks, products and the rest of HotCRM only — the epic parent carries the hotcrm follow-up.

Deviations recorded: the cloud session ran on the seat's model until the maintainer switched it; its pushes and the fleet's PR-open / reopen events fired no PR workflow here (reopen tried at 16:12Z), so a local os-dev round merges origin/main and pushes with a user token to put the final head under CI — patch round 0 (report 6476103358) merged origin/main d4427aedcf (three conflict hunks resolved toward both sides, one dead tabs-slot pin removed after #27219), patch round 1 (report 6477355363) fixed the six branch-inherent CI reds the first real run surfaced — a render-time Date.now() moved to a mount-time read, OWNER_FIELD backed by SystemFieldName.OWNER_ID, the detail.add residue pin raised to the three real affordances, body-table totals and the compact date chip routed through useDisplayLocale, the header-width e2e re-anchored on the toolbar row, one unused test import — no functional change beyond the 48 h badge clock being read at mount; the head this review names is the one after those rounds; the cloud report comment carries no seat signature line (written before #27263 landed).

---

Generated by Claude Code

[objectstack-fleet]

epic:#26676#1 · zhuangjianguo · session_cdb7a717def74e719988f089fbaa18ff

维护者速读（终稿） · PR #27310 ← #27055 记录页 v3 布局 · 2026-10-28T18:47Z

• 改了什么：没有 authored 页面的对象，记录页换成 v3 默认布局——头部 1 主 + 2 次 + ⋯（刷新进 ⋯）、要点最多 6 个；详情区无边框分区、空分区折成一行、底部一条 meta 行；历史页签 + 讨论尾栏 + 活动流合成一条时间线（全部 / 活动 / 讨论 / 变更）；关联区是 320 px 的紧凑卡片，读者可拖、上移下移、折叠、隐藏、⤢ 原地放大（URL ?related=），排列按对象记在读者偏好里；主从明细（FK 带 inlineEdit 或 relatedList: 'primary'）作为正文表嵌在第一个字段组之后；抽屉/窄屏是 详情 / 时间线 / 关联 三页签。删掉 ADR-0085 判死的 BuildPageOptions 开关和 rightRail 槽。
• 为什么改：console record page v3: frameless detail sections, one merged timeline (discussion + activity + field changes), compact related cards, header 1 primary + 2 secondary + ⋯ — the synthesized default page, drawn from the object's roles; the dead BuildPageOptions hints go #27055 你批准的 v3 设计（canvas「记录页 v3」一行）；把三处重复的历史 / 动态 / 讨论入口并成一个。
• 风险与回滚：只改渲染层，不改 spec、不改元数据；BuildPageOptions 删字段是 TS 层面的破坏性变更，控制台内无调用方传这些字段（changeset 已点名）。回滚即 revert 本 PR；读者的卡片排列存在 localStorage，回滚后不被读取、无副作用。HotCRM 的线索 / 客户 / 商机 / 工单有 authored kind: full 页，本 PR 不影响它们（hotcrm 迁移另立卡）。
• 席位意见：ACCEPT。我在预览里亲手走了三栏、放大、菜单、隐藏 / 移动 / 折叠、时间线折叠，与设计稿一致（截图已发你）。三件事不在本 PR 而在合入后的同一补丁轮：你裁的 Record page: the related switch decides whether the column exists, the panel toggles move into the header action row, and a 1440 px window with the sidebar is three columns #27241 三条（关联 OFF 无栏、分段式开关进头部动作行、1440 窗口即三栏）、spec: an object declares the business order of its related lists — relatedLists: ['task', 'event', …], an ordered list of child relationships like highlightFields is of fields; unlisted ones follow the derived order; a name that matches no inbound relationship is refused #27069 的围栏半（按 relatedLists 排序、字段组定位）、以及读者拖过之后常驻的「恢复默认顺序」入口（现只在作者默认变了时出现）。两处 spec describe 过期已立 spec: the describe() of relatedList 'primary' and of enable.trackHistory still narrate the v2 record page (own tab, History tab) after the v3 layout #27312。CI 读数：head 349cd5625c — 55 success / 8 skipped / 0 failure (1 cancelled: the Plan Test Core shards run superseded by the next push); every required context green, Test UI 16 / 16 shards, Build & E2E UI, Type Check UI, Lint UI。
• 你要做的：在 PR feat(plugin-detail,app-shell,components): record page v3 layout #27310 上点一次 Approve（5828 行超过 3000 行人工合并线，席位不能自己落地）；批完我翻 ready、挂 auto-merge、入队。

---

Generated by Claude Code

[objectstack-fleet]

director#1 · os-bill · session_01Utp6CbQLcy8yg6vhJVXXi8

Brief-claimed-by: session_01Utp6CbQLcy8yg6vhJVXXi8 · batch #425 · 2026-10-29T01:35Z

Director seat, summon #54 (ledger objectstack#12708). Presented to the maintainer in batch #425 as item 2 of 4 — over the 3000-line human-merge line (5844 changed lines, +4524 / −1320, 80 files; 0 governed paths), terminal four-piece.

Four-item check before presenting (read 2026-10-29T01:35Z):

• Seat record: ACCEPT 6477637657 (pinned to head 349cd562), 维护者速读 终稿 6477649188 — both by the epic PM epic:#26676 (zhuangjianguo, assignee).
• Review requested: hotlong, os-zhuang. Author objectstack-fleet[bot].
• Head 349cd562: 69 check-runs, 0 failure; every required context green (Test UI 16 / 16, Test Core 8 / 8, Build & E2E UI, Type Check UI, Lint UI, Governed Surface Queue Guard). The one cancelled run is Plan Test Core shards (superseded; the shards it plans all passed), which is also why mergeable_state reads unstable rather than clean — not a red. Draft.
• Carried to a patch round after landing, per the seat record: the three Record page: the related switch decides whether the column exists, the panel toggles move into the header action row, and a 1440 px window with the sidebar is three columns #27241 rulings (related OFF ⇒ no column, segmented toggle in the header row, 1440 px window ⇒ three columns), the spec: an object declares the business order of its related lists — relatedLists: ['task', 'event', …], an ordered list of child relationships like highlightFields is of fields; unlisted ones follow the derived order; a name that matches no inbound relationship is refused #27069 fence half, and a standing 「恢复默认顺序」 entry. None changes the diff under approval; the two stale spec describes are filed as spec: the describe() of relatedList 'primary' and of enable.trackHistory still narrate the v2 record page (own tab, History tab) after the v3 layout #27312.
• Seat's reading of the ask: approve on head 349cd562. After it, the epic PM seat lands it through the queue; the director seat submits no review and clicks nothing.

[objectstack-fleet]

domain:spec#3 · os-support-ai · session_01WGufzgbJhFoXYsLSe5WSPP

Finding for this PR, from the os-dev-report of PR #27352 (#27312, which rewrites the spec describes to this PR's v3 page and lands after it). ⛔ Not a review and not a claim.

On this PR's head, ui/content/docs/guide/slotted-pages.md:130-132 (a file this PR already edits) still says the default tab strip is Details, then one tab per relatedList: 'primary' list, then a shared Related tab, then History, and that promoting a child table to its own tab is a one-word change. On the v3 page as PR #27352 measured it, a primary list is a body table inside the details column with no tab of its own, and field changes join the timeline stream under its Changes filter, with no History tab. If that reading is right, the paragraph becomes false when this PR lands.