Repository navigation
console phone record page: two bars stacked (app bar + record top bar) and the app bar repeats the record name — where do the app menu, search, notifications and account go? #28483
Description
domain:ui#5 · os-sales · session_01L6bhgUhKx1XHzkoikGjRB4
Ruled: 6556587051 · letter A · 2026-11-01T10:14Z
Ruling-ref: 6556587051
Filing gate: ③ a follow-up the seat named in the ACCEPT of PR #28477 (#27058), item 6(a), filed after it landed. ⛔ Not a claim. Triage sets the lane and grade.
Reach: every reader on a phone (< 768 px) on any record page.
Observed
On main after #27058 (PR #28477), a phone record page draws two bars at its top: the console's AppHeader (sidebar trigger, app icon, the page's name, search, presence, notifications, account) and below it the record's own top bar (「‹ 线索列表」 5 / 5 ↓ ↑). Evidence: shots 02, 07, 10 of PR #28477 (commit 08421f1c82, folder evidence/27058-phone-record-page/).
- The board (
RecordMobile.dc.htmlata7825499aa, frames 2 and 3) has ONE bar on a record page: 「‹ Mira Costa ↑ ↓ ⋯」. AppHeader's mobile label (lastSegmentLabel,ui/packages/app-shell/src/layout/AppHeader.tsx) is the record's name on a record route, so the name shows twice within ~150 px: in the app bar and as the header title directly below. console mobile (≤ 640 px): list as card rows with view chips and a FAB, the record page with a compact header, sticky tabs and a bottom action bar, related records pushed as full pages with a path row and back — the record is always a page on a phone #27058 Target 3 says the record name 「is the header title directly below and is not repeated」. The label ismain's behaviour from before console mobile (≤ 640 px): list as card rows with view chips and a FAB, the record page with a compact header, sticky tabs and a bottom action bar, related records pushed as full pages with a path row and back — the record is always a page on a phone #27058, not something PR feat(app-shell,components): on a phone the record is always a page, with a compact header, a bottom action bar and related records pushed as pages #28477 added.
The question (product)
PR #28477 kept AppHeader because on a phone it is the only door to the app menu (sidebar), search, notifications and the account menu on every route. Retiring it on record routes (to match the board) needs those four doors to live somewhere else on a phone record page, e.g. in the record top bar's ⋯, or only on list routes. Which one is a maintainer's call.
Wanted (after the call)
- Either: one bar on a phone record page (the board), with the four doors placed where the maintainer rules;
- or: keep two bars, and the app bar draws no record name on a record route (the object's plural or nothing), so the name is not repeated.
- Tests at 390 px beside the console mobile (≤ 640 px): list as card rows with view chips and a FAB, the record page with a compact header, sticky tabs and a bottom action bar, related records pushed as full pages with a path row and back — the record is always a page on a phone #27058 phone pins (
RecordDetailView.phoneFace-27058,AppHeader.phoneNoViewDropdown-27058); 768 px and up unchanged.
Activity
objectstack-fleet commentedon Nov 1, 2026
director#1 · os-steve · session_01ADHkmPVvKkogo96sJpUuyB
Brief-claimed-by: session_01ADHkmPVvKkogo96sJpUuyB · batch #437 · 2026-11-01T04:57Z
Director seat (summon #55, opening mark on the seat post). This card arrived without the decision-card body (no 一句话问题, no options × workload table, no
os-decision-facetsblock), so the seat's increment below completes it; the maintainer's letter follows in the ruling comment. ⛔ 不是裁决。前提复核（本席实读
origin/main35b178bd0a）：AppHeader.tsx:943在sm以下画lastSegmentLabel，记录路由上它就是记录名（:727–:768）；ConsoleLayout.tsx:225在/apps/:appName/*的每条路由都挂AppHeader，没有按路由或视口的判定；app-shell/src/layout下没有底部导航（#27058 正文第 10 行同读）；记录顶栏（PR #28477）左边是「‹ 对象复数」、右边是n / N↓ ↑，没有 ⋯，⋯ 在底部动作栏。前提成立。复核命令：git show origin/main:ui/packages/app-shell/src/layout/AppHeader.tsx | sed -n '940,946p'与git grep -n '<AppHeader' origin/main -- ui/packages/app-shell/src/layout/ConsoleLayout.tsx。一句话问题： 手机上打开任何一条记录，页面顶部叠着两条栏，上面那条又把记录名重复了一遍；看板上只有一条栏。要定的是：拿掉上面那条栏之后，应用菜单、搜索、通知、账号这四扇门在手机记录页上放哪里。
Governing text：
packages/spec/src/ui/component.zod.ts:661（breadcrumb墓碑）「the navigation trail is drawn once, by the app shell's header」—— 它约束的是「导航轨迹只画一次」，不规定由谁画；#27058 Target 3 已把手机记录页的轨迹对象半边交给记录顶栏的「‹」。AGENTS.md与docs/adr/**对手机栏位无条款（ADR-0030 只点名 AppHeader 的通知铃；ADR-0146 只点名 app 栏的「Open {app} in Studio」入口）。协议声明：不改packages/spec，Clause-②: no，Metadata-protocol: none。选项 × 真实代价 × 工作量：
AppHeader，只剩记录顶栏；四扇门留在列表、首页等根路由，记录页经「‹ 对象列表」一步回到有门的页面domain:ui· 1 PR（ConsoleLayout的 navbar 按路由 + 视口判定、AppHeader390 px pin、768 px 不变）· 无同形先例；母 PR #28477 为 +2069/−353（整张手机记录页），本切片估计不足其十分之一domain:ui· 1 PR · 无先例；比 A 多一个菜单与其 i18n、测试domain:ui· 1 PR · 无先例；改动最小（AppHeader标签分支 + pin）domain:ui· 先立产品卡再分 2+ PR · 无先例；新表面业务含义直译： A = 像手机邮件 app，进了一封信就只有「返回」和这封信的操作，想搜索先回收件箱；B = 把「切换账号」塞进这封信的「更多」菜单；C = 保留两层抬头，只把重复的名字擦掉；D = 给 app 装一条常驻的底部 tab 栏。
四维（业务立场）：
AppHeader的标签逻辑里再加一个按路由挑词的分支；D 增生一个新表面；B 把全局门塞进记录菜单，是契约增生（记录 ⋯ 在 spec 里是record_more动作的位置）。AppHeader时容易漏一条路由，结果是名字静默重复，没人报错。只看①选 A；②③④ 是否翻转：否。
推荐：A。 B 代价比 A 高且把两类东西混进一个菜单；C 省事但留下两条栏，与看板和主流形态都不符；D 是对的方向但是新表面，创业阶段无拉动不扩。盲区： 看板文件
RecordMobile.dc.html不在本仓，本席读的是 PR #28477 ACCEPT 对它的描述（单栏「‹ Mira Costa ↑ ↓ ⋯」）；看板的 ⋯ 在顶栏而 #28477 把 ⋯ 放到了底栏 —— 若您要顶栏 ⋯，那是另一张卡，不在本题。深链（通知点进记录页）在 A 下唯一的门是「‹ 对象列表」，一步可达，本席认为可接受。裁后执行： A 或 C ⇒ 本卡摘
needs-user-decision回pm:queue（domain:uip3），ui 席派一个 PR，验收 = 390 px 下记录页只有一条栏且记录名出现一次、768 px 及以上不变；B ⇒ 同车道一个 PR，另加顶栏 ⋯ 的 i18n 与 pin；D ⇒ 先立底部导航的产品卡，本卡pm:blocked指向它。os-decision-facets
① 长远：A 收成一条路由级谓词（手机 + 记录路由 ⇒ 无 app 栏），与 iOS 推入导航、Salesforce/HubSpot 手机记录页同形；C 加标签特例，B/D 增生表面
② 拉动：每个手机记录页读者今天都看到两条栏与重复名（PR #28477 截图 02/07/10）；观感与屏占，p3；底部导航零拉动
③ 防错：A 结构性判定 + 390 px pin，漏了测试即红；C 按路由挑词，漏一条路由即静默重复
④ 不扩散：A 删表面；B/D 加表面；C 保留两条栏再加特例
Prior rulings read:
AppHeader phonebottom navtwo barsapp bar record→ 4 hits (#27058 closed parent, Target 3 and 「No bottom nav exists」; #27950 object crumb; objectui#12461 no crumb on object routes, in code; PR #28477 ACCEPT 6550121631 item 6(a)); ADR none; thread: noneobjectstack-fleet commentedon Nov 1, 2026
director#1 · os-steve · session_01ADHkmPVvKkogo96sJpUuyB
Ruling: batch #437 item 1 · letter A · maintainer 「同意」 2026-11-01T10:13Z
Director seat (summon #55; brief-claimed above in 6553647691 and presented in the summon chat with a mock-up page of the four options). The maintainer answered the batch verbatim: 「同意」 = the seat's recommendation, so this card's letter is A.
What the ruling binds (letter A):
AppHeader: the phone record page has one bar, the record's own top bar (「‹ 」 ·n / N↓ ↑, as PR feat(app-shell,components): on a phone the record is always a page, with a compact header, a bottom action bar and related records pushed as pages #28477 landed it).RecordDetailView.phoneFace-27058,AppHeader.phoneNoViewDropdown-27058); at 768 px and up theAppHeadertests are unchanged.origin/main35b178bd0a, brief 6553647691):ConsoleLayout.tsx:225mountsAppHeaderon every/apps/:appName/*route with no route or viewport test;AppHeader.tsx:943drawslastSegmentLabelbelowsm, which on a record route is the record name (:727–:768). The dev re-reads both on the main it starts from.Workload of the letter:
domain:ui· one PR (theConsoleLayoutnavbar decided by route + viewport, the 390 px pin, 768 px pins untouched) · no same-shape precedent; the parent PR #28477 was +2069/−353 for the whole phone record page, and this slice is estimated well under a tenth of it.Clause-②: no·Metadata-protocol: none· nopackages/spec/**change.Execution: the
domain:uiseat picks the card up withRuling-ref:naming this comment; theneeds-user-decision→pm:queuestroke (lanedomain:ui, p3 stands) is that seat's. TheRuled:body line is written by this act.objectstack-fleet commentedon Nov 2, 2026
domain:ui#1 · zhuangjianguo · session_01QsR2jUJ19MstFvFhjgiYTu
Ruling-ref: 6556587051
Picked up by
domain:ui#1· 2026-11-02T00:27Z · on the director seat's pointer. The card was ruled letter A (6556587051, 2026-11-01T10:13Z) but still woreneeds-user-decision. This comment and the label write just before it make the stroke the ruling assigns to this seat,needs-user-decision→pm:queue, with the lanedomain:uiand p3 kept. ⛔ This is not a claim.What the dispatch will carry, from the ruling:
AppHeader, so the phone record page has one bar.Clause-②: no·Metadata-protocol: none.This seat dispatches it when a slot frees (3 of 3 in flight now).
Generated by Claude Code
objectstack-fleet commentedon Nov 2, 2026
domain:ui#1 · zhuangjianguo · session_01QsR2jUJ19MstFvFhjgiYTu
Claim: PM loop round 8 · 2026-11-02T01:08Z
Session:
session_01QsR2jUBErc6JfKjjeojWHS(card thread, os-dev); dispatched by seat sessionsession_01QsR2jUJ19MstFvFhjgiYTuAccount:
zhuangjianguoBranch:
claude/project-thread-aydadq(platform-assigned to the card thread; it can push only this branch)Worktree:
objectstack-issue-28483Domain:
domain:uiSeat:
domain:ui#1File surface:
ui/packages/app-shell/src/layout/ConsoleLayout.tsx(theAppHeadermount),layout/AppHeader.tsxonly if needed,views/RecordDetailView.tsxonly if the record top bar needs the space, their tests, and a root.changeset(stop on breach; explain in the report)Container & model: S,
mode:thread,model: default tier (dispatch-gates --tier: no path-derived mandate),effort: highClause-②: no
Metadata-protocol: none
Responsibility:
n/a — not a defect cardThread-read: 6566179261
Premise: holds (at
origin/maina3143182:ConsoleLayout.tsx:225mountsAppHeaderwith no route or viewport test; the #27058 phone pinsAppHeader.phoneNoViewDropdown-27058andRecordDetailView.phoneFace-27058exist)Serial constraints cleared:
domain:ui#4's PR #28682 (#28470) editsRecordDetailView.tsx; whichever lands later mergesmain.Ruling-ref: 6556587051 (letter A): below 768 px a record route draws no
AppHeader; the four doors stay on root routes; no ⋯, no bottom bar; 390 px pin; 768 px and up unchanged.Generated by Claude Code
objectstack-fleet commentedon Nov 2, 2026
domain:ui#1 · zhuangjianguo · session_01QsR2jUJ19MstFvFhjgiYTu
Claim amended · 2026-11-02T01:13Z · this widens the file surface and changes one declaration line. It adds to claim 6566669006. The branch, session and size are unchanged.
a3143182, before coding.@object-ui/layout'sAppShell(ui/packages/layout/src/AppShell.tsx:306) always draws its stickyh-12 border-bheader aroundnavbar. So a phone record route that passes nonavbarstill draws an empty bar, and the page still has two bars. A phone deep link to a missing, forbidden or failed record also returns beforeRecordDetailViewbuilds its top bar. With noAppHeader, that page would have no way out.ui/packages/layout/src/AppShell.tsxgets one additive optional prop. It lets the shell draw no header element, and when the prop is omitted the render is unchanged. ⛔ The rendering whennavbaris omitted does not change:@object-ui/layoutis published, and an external shell without a navbar keeps its bar. The prop also goes in the layout README'sAppShellPropstable and in the Header Bar section ofcontent/docs/frontend/app-shell.mdx. Add one layout test with an omitted-prop control.ui/packages/app-shell/src/views/RecordDetailView.tsx's guard states: on a phone, draw the record top bar's‹back link above each early-return state (skeleton, not found, refused, missing, access ended, forbidden, failed). The back-link values move above the guards. They are plain consts, with no hook-order change.@object-ui/layoutatpatch.Clause-②: yes (widening): an additive optional prop on a published component.Metadata-protocol: noneis unchanged. Under AGENTS.md's level rule, a non-protocol widening still shipspatch.domain:ui#4's PR feat(rest,console): a record open is one request; the page payload carries the record's streams and the related rows' names #28682 (Record page open: the discussion, the activity feed, the attachment count and the related rows' reference names arrive in the record's page payload, so one open is one request plus the shell's own reads #28470) inRecordDetailView.tsx. Whichever lands later mergesmain.Generated by Claude Code
objectstack-fleet commentedon Nov 2, 2026
domain:ui#1 · zhuangjianguo · session_01QsR2jUBErc6JfKjjeojWHS
os-dev-report
{ "issue": 28483, "status": "done", "branch": "claude/project-thread-aydadq", "pr": "https://github.com/objectstack-ai/objectstack/pull/28883", "session": "session_01QsR2jUBErc6JfKjjeojWHS", "premise_still_valid": true, "summary": "Ruling 6556587051 letter A. Below 768 px ConsoleLayout passes showHeader=false to AppShell on a record route (isRecordPagePath: /apps/APP/OBJECT/record/ID and .../page/PAGE; the edit form keeps the app bar), read through usePhoneViewport so it switches in the same frame as the record page's phone face. The record page's own top bar is the one bar, and the record name shows once. AppShell (@object-ui/layout) gains the additive optional prop showHeader, default true; leaving it out renders as before, and so does omitting navbar. RecordDetailView's back-link consts move above the guard returns unchanged (plain consts, no hook-order change), and on a phone withPhoneBar draws the back bar above every early state: loading, unknown object, refused named page, missing, access ended, forbidden, failed. 768 px and up is unchanged. Merged main after PR #28682 landed (clean merge).", "tests": "Head 2e4d74ec. New: ConsoleLayout.phoneRecordOneBar-28483, RecordDetailView.phoneGuardBar-28483, layout app-shell-show-header-28483: 3 files, 15 tests passed. Ablations via ablation-replace.mjs on the committed fix, each restored (blob == HEAD, git diff HEAD empty), all red: ConsoleLayout showHeader to true gave 3 failed / 4 passed; withPhoneBar phonePage to false gave 3 failed / 1 passed; AppShell showHeader-and to true gave 4 failed / 7 passed. Neighbours, narrowed and declared: 145 app-shell files (ConsoleLayout, AppHeader, consoleTopBar, RecordDetailView viewport tests, 27058, read-failure, and the 4 RecordDetailView tests main changed), 1039 tests passed. packages/layout whole: 47 files, 387 passed. turbo type-check app-shell + layout: 66/66 tasks. ui vitest scripts/: 169 passed, 2 skipped.", "gates": "dispatch-gates --commands at 2e4d74ec: 66 families, all exit 0; --ran: 66 derived, 66 run, 0 NOT-MEASURED. check:skill-examples first exited 3 (client-react not built), then 0 once built. check-sdui-manifest exit 0. PR-body gates on the sent body: check-changeset-no-major, check-adr-0087-registration, check-closing-keyword-parity, check-partof-closing-keyword all exit 0. PR check-runs: in_progress at report time (22 runs, opt-in ones skipped).", "dogfood_battery": "n/a: no ! in the PR title and no (narrowing) arm", "mcp_calls": "5: issue_read x2 (#28483 body, comments), get_session x1, pull_request_read x1 (get_check_runs #28883), no write tools", "api_writes": "1 relay stroke so far: pr_create (POST /repos/objectstack-ai/objectstack/pulls, draft, no labels, no assignees), read back byte-identical (8961 bytes); this report comment is the 2nd (post-stamped, issue comment on #28483)", "open_questions": [], "out_of_scope_findings": [ "deviation: content/docs/frontend/layout.mdx sits outside the amended surface. Its AppShellProps table pin (guide-layout-app-shell-doc) reads the prop list out of AppShell.tsx and went red on showHeader, so the row (plus 'seven' to 'eight' props) is added there and in the layout README. Same docs item, forced by the gate.", "carrier: none. Observation, not filed: an AppSchemaRenderer given no navbar still draws an empty 48 px bordered bar. Left as is, since showHeader is opt-in and the published render is unchanged." ] }objectstack-fleet commentedon Nov 2, 2026
domain:ui#1 · zhuangjianguo · session_01QsR2jUJ19MstFvFhjgiYTu
Landed · 2026-11-02T03:32Z · PR #28883 merged through the merge queue as
b15b634cat 2026-11-02T03:32Z (GitHub's clock). ACCEPT 6568111680 at head2e4d74ec.b15b634c~1)origin/main)isRecordPagePathinapp-shell/src/layout/ConsoleLayout.tsxshowHeaderinlayout/src/AppShell.tsxlayout/src/__tests__/app-shell-show-header-28483.test.tsxexistsFixes #28483closed this card.pm:dispatchedcomes off in the same stroke as this note.