Repository navigation
studio: navigation details — More holds only Access, Advanced trigger renames itself, no search in Automations, raw ids/names where labels belong, silent redirect without Studio access #11794
Description
Activity
Path: write metadata — moving around Studio | 缺项 | P3
Triage: first grade,
enhancement·priority:p3·domain:ui·area:studio·pm:queue. Filed as ②, but routed as a Studio UX improvement: no contract or product question is open. Direction: the body's option ATriage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-07T17:15Z. ⛔ Not a claim, ⛔ not a dispatch.Triage: lands in the Studio shell's tabs and sub-tabs (
packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx) and the Automations list ⇒domain:ui; rationale: a Studio or console surface in objectui. Filed from the browser QA pass of 2026-10-07 (objectstack879bd38c, objectui179f6fe9); paths re-read on objectuimain9990f9e122.- Why not the decision box: tab placement, search in a list and labels over machine names change no contract and no permission. Why p3: every item works, but is harder to find than it should be.
- Direction:
- Access becomes a top-level tab; sub-tabs are flat
- search and grouping in Automations; the Advanced trigger keeps its own name
- labels where the author sees ids or machine names
- without Studio access, a one-line notice instead of a silent redirect
- Serial hazard:
StudioDesignSurface.tsxis 5,547 lines (wc -lonmain) and several open Studio cards edit it. Claim after the in-flight one lands, or declare the overlap in the claim. Clause-②: no. Patch changeset in objectui.
Claim: PM loop round 15
Session:session_01MgfduSkFrfM3eorB3UGfAU
Account:os-bill
Branch:claude/issue-11794-studio-navigation
Worktree:objectui-issue-11794
Domain:domain:ui
Seat:domain:ui#2
Scope of this claim: triage's option A (6043000484) for five of the body's seven findings. Each is re-measured onmainbefore any edit, and a finding that no longer holds is reported, not built.- More holds only Access: Access becomes a top-level tab, and the sub-tabs are flat.
- The Advanced dropdown trigger keeps its own name instead of renaming itself to the chosen sub-panel.
- The Automations list gets search and grouping, and its names are no longer cut at about 16 characters.
- After Create app, Studio opens Interfaces, where the app lives, instead of staying on Data.
- A member without Studio access who opens
/studiosees a one-line notice instead of a silent redirect home.
File surface (as read on
main6694abe; the dev re-reads it):packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx: the tab and sub-tab layout, the Advanced trigger, the Automations rail, and the Create app follow-up.- The
/studioroute guard, wherever it lives inpackages/app-shellorapps/console. The dev names the file before the edit. - The tests beside them, and
.changeset/11794-*.md.
⛔ Not on it:
- the raw ids and machine names in Explain access, the permission-set list and the nav editor (objectui#11862,
pm:blockedon metadata-protocol/spec: the_draftsheader carries no label, so a draft-only item can only be shown by its machine name (ListDraftsResponseSchema drops the label the repository already reads) objectstack#22200); - the Studio landing header (objectui#11863);
- any new
packages/i18nkey or published prop. If item 3 or 5 cannot be built from existing keys, the dev stops on that item and reports it, and the seat routes it asClause-②. - the permission semantics of
/studio: the guard's decision is unchanged, and only what the member sees changes.
Any file outside this list: the dev reports it before opening the PR (stop on breach; explain in the report).
Container & model:S,mode:subagent,model: opus(dispatch-gates --tier --repo objectstack-ai/objectuiover these paths: no path-derived mandate; default tier)
Clause-②: no
Responsibility:objectui Studio shell: Access hidden in More, a self-renaming Advanced trigger, an unsearchable Automations list, a Create app that stays on Data, a silent no-access redirect | the Studio tab model and the route guard already on main | every Studio author and every member who opens /studio
Thread-read: 6043000484
Serial constraints cleared: both earlier holders ofStudioDesignSurface.tsxhave merged: PR objectui#12024 (objectui#11865 slice o,5382a86) and PR objectui#12023 (objectui#11787's one save model, seat 3,6694abe, which reshapedPILLARSandAccessPillar).- In-flight claims and open objectui PRs, read 2026-10-09T04:40Z: none touches
StudioDesignSurface.tsx.
Why
Clause-②: no: tab placement, list search, post-create navigation and a notice change no contract, no permission and no published prop (triage6043000484). New i18n keys are excluded above.
Generated by Claude Code
os-dev-report
{
"issue": 11794,
"status": "needs_decision",
"branch": "claude/issue-11794-studio-navigation",
"pr": "#12028",
"session": "session_01MgfduSkFrfM3eorB3UGfAU",
"premise_still_valid": true,
"summary": "All five findings still hold on main 6694abe. Built, in packages/app-shell StudioDesignSurface.tsx: item 2 (the Data pillar's Advanced trigger always reads Advanced; its items are radio items, so the menu checks the open panel); item 3, the search and wrap half (an Automations rail search over label or machine name, using the existing key engine.studio.designer.search, a no-match line from the existing engine.list.emptyQuery, and labels that wrap instead of truncate); item 4 (Create app navigates to /studio/PACKAGE/interfaces after the unchanged draft save, through confirmLeavePillar). Held, so the status is needs_decision: item 1, because Access-as-top-level-tab reverses the standing maintainer ruling objectui#5813 item 3 (4 to 3 primary pillars, Access demoted into More), which the triage direction 6043000484 does not cite; item 3's grouping half, because the rail list carries neither trigger kind nor object and kind headings need new engine strings; item 5, because no existing key says Studio access is needed and a new packages/i18n key is out of this claim. The PR is draft, the first line is Part of #11794, Clause-②: no is in the body, and the assignee is os-bill.",
"findings": [
{
"n": 1,
"finding": "More holds only Access",
"verdict": "holds",
"reading": "OVERFLOW_PILLARS has one entry (access), and the More Popover renders only that list. When Access is open, the More trigger also renames itself to Access.",
"built": false,
"why": "needs a maintainer decision: it conflicts with objectui#5813 item 3 (see open_questions[0])"
},
{
"n": 2,
"finding": "Advanced trigger renames itself",
"verdict": "holds",
"reading": "the trigger rendered activeAdvancedTab.label whenever one of the five power panels was open",
"built": true
},
{
"n": 3,
"finding": "Automations list: no search, names cut, no grouping",
"verdict": "holds",
"reading": "the rail nav had no input; each row's label was a truncate span in the w-52 rail; loadPackageSurfaces yields only type, name and label",
"built": "search and wrap: yes; grouping: no (open_questions[1])"
},
{
"n": 4,
"finding": "After Create app Studio stays on Data",
"verdict": "holds",
"reading": "doCreateApp saved, toasted, set the pending label, closed the dialog and called onDraftSaved; no navigation",
"built": true
},
{
"n": 5,
"finding": "silent redirect without Studio access",
"verdict": "holds",
"reading": "RequireStudioAccess in apps/console/src/components/StudioRoute.tsx answers a non-holder with Navigate to the home path (replace), with no state and no message",
"built": false,
"why": "needs a new packages/i18n key (open_questions[2]); the guard file is untouched"
}
],
"hypotheses": {
"H1": "confirmed: all five findings hold on 6694abe",
"H2": "confirmed: the create's one write save('app', NAME, buildAppSkeleton(NAME, LABEL, navObjects), {mode:'draft', packageId}) is pinned byte for byte in every leg of StudioDesignSurface.createAppOpensInterfaces-11794.test.tsx; tab, search and navigation write nothing",
"H3": "not exercised: item 5 is not built and the guard file is unchanged; the existing StudioRoute.test.tsx etc. ran green at head",
"H4": "split: search placeholder YES (engine.studio.designer.search 'Search…', plus engine.list.emptyQuery, both in en and zh in the app-shell engine table); notice NO (checked capability.label.studio_access, errors.forbidden, home.build.noCapability, empty.appAccessDenied; none is the sentence); grouping headings NO (translateFlowMeta returns the raw token outside zh)"
},
"tests": "All at HEAD 0429508 (git rev-parse --short HEAD after the last commit), with repo-root pnpm exec vitest run --maxWorkers=3 under os-verify-lock (slot issue-11794). (1) StudioDesignSurface.* batch A: Test Files 37 passed (37), Tests 175 passed, VERDICT command-exit 0. (2) StudioDesignSurface.* batch B: 35 passed (35), Tests 308 passed, VERDICT command-exit 0. (3) the other studio-design test files, batch A: 45 passed (45), Tests 244 passed, VERDICT command-exit 0. (4) the other studio-design files, batch B, plus StudioRoute.test/landingI18n/lazyBuilder-11798/recentPackage-11863, registerStudioComponents.builderLazy-11798, App.uploadAltitude-10131, homeRecoveryRedirectsFollowDeclaration-7373, builtinDesigners.lateArrival-11939, observableRegistries-11939, spec-symbol-ledger-app-shell-7265, HomePage.aiStudioDisabled, packages/core column-identity.ratchet.test.ts and scripts one-authority-per-exported-name-6273.test.ts: Test Files 59 passed (59), Tests 594 passed, VERDICT command-exit 0. New pins: DataPillar.advancedKeepsName-11794 (3), AutomationsPillar.railSearch-11794 (5), StudioDesignSurface.createAppOpensInterfaces-11794 (4). Ablations, run on committed 4db7f9a with objectstack scripts/ablation-replace.mjs under a trap: every mutation was verified on disk (anchor 1 to 0, blob changed) and restored with blob == HEAD 2167d6c2b8f6 and git diff HEAD empty. A1, the trigger renames again: 2 failed, 1 passed (control green). A2, the search filters nothing: 3 failed, 2 passed. A3, truncate restored: 1 failed, 4 passed. A4, navigation disabled: 3 failed, 1 passed (the from-Interfaces control green). Every ablation went red in the expected direction. Not a dist ablation: the tests import ./StudioDesignSurface by relative path, so the src is under test.",
"gates": [
"pnpm --filter @object-ui/app-shell type-check (after building the app-shell^... closure with turbo under the lock: Tasks 28 successful, 28 total): echoes 'tsc --noEmit && tsc -p tsconfig.test.json', VERDICT command-exit 0; tsc -p tsconfig.test.json --listFilesOnly lists all ten touched test files",
"node scripts/check-changeset-presence.mjs: exit 0, '10 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s): .changeset/11794-studio-navigation-details.md'",
"node scripts/check-changeset-no-major.mjs: exit 0, 'No changeset declares a major bump.'",
"pnpm check:new-line-citations: exit 0, 'VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only'",
"pnpm check:control-bytes: exit 0, 'check-control-bytes: OK (scanned 8178 tracked text file(s); skipped 85 binary)'",
"pnpm check:i18n-keys: exit 0, 'Every in-scope call-site key resolves against the en pack (3311 keys)…'",
"pnpm exec eslint on the 10 touched ts/tsx files: exit 0, '25 problems (0 errors, 25 warnings)'; none in a changed hunk of StudioDesignSurface.tsx; 4 are the new (p: any) radio mock lines in DataPillar.celGate and DataPillar.panelGate, which follow those files' existing passthrough style",
"first-load bytes (apps/console, CI=true pnpm exec vite build, under the lock): eagerGzipBytes base 6694abe = 3238198, head 0429508 = 3238234, delta +36 B gzip (ceiling 3281467; chunk count 289 both). The delta is in ui-components +42 and vendor-radix +62 (the radio menu parts are kept now); other chunks moved a few bytes each. The scripts/check-eager-closure-budget.mjs file was not touched.",
"CI on 0429508 at report time: 27 check runs, 19 success, 1 skipped, 6 in_progress, 1 queued; Bundle Analysis in_progress. The budget bot's eager-closure reading: NOT MEASURED, because the bot had not run when this report was written (per the dispatch contract, no wait for CI)."
],
"files_changed": [
"packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx",
"packages/app-shell/src/views/studio-design/DataPillar.advancedKeepsName-11794.test.tsx (new)",
"packages/app-shell/src/views/studio-design/AutomationsPillar.railSearch-11794.test.tsx (new)",
"packages/app-shell/src/views/studio-design/StudioDesignSurface.createAppOpensInterfaces-11794.test.tsx (new)",
"packages/app-shell/src/views/studio-design/StudioDesignSurface.servedDraftTakenAsIs-10765.test.tsx (menuitem to menuitemradio)",
"packages/app-shell/src/views/studio-design/DataPillar.hiddenSystemFields-11780.test.tsx (menuitem to menuitemradio)",
"packages/app-shell/src/views/studio-design/DataPillar.celGate.test.tsx (radio passthrough mocks)",
"packages/app-shell/src/views/studio-design/DataPillar.panelGate.test.tsx (radio passthrough mocks)",
"packages/app-shell/src/views/studio-design/DataPillar.designerRegistryPopulated.test.tsx (radio passthrough mocks)",
"packages/app-shell/src/views/studio-design/DataPillar.inspectorBelongsToView-11781.test.tsx (radio passthrough mocks)",
".changeset/11794-studio-navigation-details.md (@object-ui/app-shell: patch)"
],
"route_guard_file": "apps/console/src/components/StudioRoute.tsx (RequireStudioAccess): named, not edited (item 5 held)",
"deviations": [
"Item 1 is held, although the dispatch lists the triage direction as a ruling not to be re-ruled. It reverses objectui#5813 item 3, a maintainer ruling of 2026-08-24 that the code comment on OVERFLOW_PILLARS cites, and triage 6043000484 does not cite it. This report surfaces the conflict and does not re-rule it.",
"Six existing test files beside the surface were edited, all in the claim's 'tests beside them'. Two change the Settings item's role from menuitem to menuitemradio. Four DataPillar suites that render the menu as passthroughs gain mocks for the two radio parts. Without the mocks, those four went red: 20 tests, measured before the fix.",
"The docs-driven rule (AGENTS.md #2) is not applied, because the claim's file surface excludes docs. See out_of_scope_findings.",
"Commits end with the model-free trailer pair (Claude-Session plus Co-authored-by: Claude), per objectui AGENTS.md. This overrides the harness reminder's model-named Co-Authored-By. The PR body ends with the os-dev session-URL footer, not the harness's other footer form.",
"objectui has no scripts/pm/dispatch-gates.mjs. The gate list is the dispatch's lead, re-derived by hand from package.json scripts and from the suites that import StudioDesignSurface, studioRoutes, StudioRoute or RequireStudioAccess (git grep).",
"The head console build ran after the turbo closure build had put dist/ into the worktree's packages; the base build had none. apps/console/vite.config.ts aliases the workspace packages to src/ in every environment, and the per-chunk diff puts the +36 B in ui-components and vendor-radix. The two builds' resolution was not otherwise compared.",
"The worktree /home/user/objectui-issue-11794 was removed after the PR opened (rm -rf node_modules, then git worktree remove without --force, which succeeded)."
],
"mcp_calls": "0 — no MCP GitHub tool was called",
"api_writes": "3 REST writes, all through the fleet-write relay as objectstack-fleet[bot]. (1) pr_create: POST /repos/objectstack-ai/objectui/pulls, draft, carried by POST /repos/objectstack-ai/objectstack/dispatches as request fw-20261009T052537Z-d8e1fe, run 37888519114 success; read-back of the 8646 bytes is identical. (2) label-write --assign os-bill: POST /repos//issues/12028/assignees, carried by dispatch request fw-20261009T052629Z-aa4291, run 37888585909 success; read-back matches. (3) this os-dev-report comment: POST /repos//issues/11794/comments via post-stamped. Plus 3 git pushes, which are not REST writes: the empty branch, 4db7f9a and 0429508. Zero label writes, because the dispatch named none.",
"open_questions": [
{
"question": "Item 1: should Access become a top-level Studio tab? The triage direction (6043000484, option A) says yes. The maintainer ruled the opposite on objectui#5813 (2026-08-24), item 3, quoted: 权限降级：从第四支柱降入顶栏「更多」菜单（页面本身不变，只动导航层级）。一级导航 4→3，与 Data/Automations/Interfaces 心智完全对齐。 A seat direction does not overrule that, so the maintainer's word is needed.",
"options": [
"A: Access becomes the fourth top-level tab and the one-item More popover is deleted (the triage direction). This reverses 5813 item 3.",
"B: keep More as 5813 ruled, and apply item 2's rule to its trigger: it keeps the name More, and Access shows as checked inside. A one-item menu remains.",
"C: keep three pillars, and draw Access as a separate secondary link after the pillar row, not in a menu. This is a third design, so it needs a ruling of its own."
],
"recommendation": "A, but only on the maintainer's word, because it reverses his ruling. Business need, measured: the pillar row has four controls either way (Data · Automations · Interfaces · More, or the same with Access), so the demotion did not lower the control count. It changed only the label, to one that hides its single item, and added a click. Long-term: a one-item overflow is a degenerate menu; if more low-frequency surfaces arrive, a More can come back with real content. AI-error axis: neutral, because no metadata or contract is involved. Startup focus: A deletes the Popover branch, B is zero code, and C adds a design. If the maintainer keeps 5813, then B, not the status quo, because the More trigger's self-renaming is item 2's defect."
},
{
"question": "Item 3, grouping half: should the Automations rail group flows by trigger kind or object? The list carries neither. loadPackageSurfaces yields only type, name and label, and a draft header carries only a name. The GET /api/v1/automation/_status rows carry triggerType and object, but only for flows the engine holds. English headings for trigger kinds exist nowhere.",
"options": [
"A: no grouping. The new search, over label and name, plus full names close the findability complaint.",
"B: group by the runtime triggerType for engine-held flows, plus a bucket for flows not deployed yet. This needs new engine strings in en and zh, such as engine.studio.auto.group.record, .schedule, .api, .manual and .notDeployed, which the claim routes as Clause-②.",
"C: a producer change, so that the rail reads the kind from each flow body (resolveFlowTriggerKind), drafts included. That costs one read per draft and still needs the strings in B."
],
"recommendation": "A for now. Business need: the measured complaint was 'no search, names cut', and both now ship. No reading shows authors scanning by trigger kind. Long-term: B would group drafts and deployed flows by different rules, so the rail would disagree with itself. AI-error axis: neutral. Startup focus: C adds a read path and new strings with no measured pull. Revisit only on a named need."
},
{
"question": "Item 5: no existing key says that Studio access is needed. Should one new packages/i18n key be added (Clause-②, in all ten packs) so that the /studio guard can say it? The guard's decision would stay unchanged.",
"options": [
"A: add a key such as console.studio.accessRequired, for example 'Studio needs the Studio Access permission, which your account doesn't have. Ask an administrator for access.', in all ten packs. RequireStudioAccess shows it once when it redirects (not measured: whether a toast reaches the home page, or whether router state plus a home-page line is needed, which would touch a second file).",
"B: status quo, the silent redirect."
],
"recommendation": "A. Business need: a member who follows a /studio link lands on home with no reason given. The QA pass measured exactly that, and only one sentence closes it. Long-term: one key, and the permission decision stays unchanged. AI-error axis: neutral. Startup focus: one string in ten packs, no new capability. It needs the seat's Clause-② routing, so it is not built here."
}
],
"out_of_scope_findings": [
"carrier: objectui#11794 item 1, the decision above. The More trigger renames itself to 'Access' while Access is open, the same pattern as item 2. It is left alone because the item 1 answer decides whether More exists at all. Noted, not filed.",
"carrier: none. content/docs/guide/console.md, section 'Object design (Studio Data tab)', still describes a seven-tab strip (Records · Form · Validations · Hooks · Actions · API · Settings), stale since objectui#5813 folded five tabs into Advanced. The docs-driven rule would also want the rail search and the Create app landing there. Doc drift, not a filed class: it went only into the PR's Acceptance notes. Dedupe words: console guide studio data tab strip stale · advanced menu docs"
],
"decision_frame": "每个方案必须沿四条固定评估轴分析,这是决策分析的核心原则,不是可选项:\n\n- 实际业务需求 — 它服务的是真实存在的业务场景,\n 还是投机性能力面?判据要求实测(谁在写这个键、谁在读、\n 示例应用与真实部署的用法),「读起来像有用」不作数。这条轴会改变结论,不是陪衬。\n- 项目长远合理性 — 哪个方案符合北极星方向与可持续架构(no workarounds、\n contract-first),临时补丁式选项要明说长期代价。\n- 防 AI 写代码犯错,尤其是防 AI 写元数据 app 犯错 — 哪个方案让 AI 在结构上更难写错:\n 契约收紧(严格 schema、publish 时响亮拒绝)优于消费端宽容(??回退、静默容错)——\n 宽容恰是 AI 批量犯错被掩盖的温床;声明即强制,绝不让 AI 声明一个运行时不兑现的能力。\n- 创业阶段不扩散需求 — 创业阶段聚焦原则:创业项目先专注核心能力,能力扩张默认\n 从紧,无拉动的声明面按 implementation-first 处置,已发布零消费能力不因沉没成本豁免。\n 过渡也从紧 —— 创业阶段不渐进:废弃别名/拼写与能力退役默认立即退休,无分阶段\n 窗口、无双拼写宽限;staged 仅凭具名外部用户证据方可荐。新增门禁默认否:门禁是只减\n 不增的零件,例外只有维护者点名;荐新增门禁须引其点名原话,否则荐「不加」。\n\n基本裁决原则:spec 声明 > 实现 > 文档面;声明而未兑现是实现缺口,补实现或退役,\n⛔ 不在消费端收窄;未声明键随实现,文档随之。「声明即强制」只及 spec 与元数据契约、\n运行时能力,⛔ 不及 AGENTS.md 这类给 agent 读的约定 —— 那些的读者是 agent,不是门禁。\n推荐意见必须基于这四条轴给出理由;四轴冲突时如实呈现权衡,\n交维护者拍板。"
}os-dev-report
{
"issue": 11794,
"round": "seat fix round: docs-driven update (the claim's surface is amended to add content/docs/guide/console.md)",
"status": "needs_decision",
"branch": "claude/issue-11794-studio-navigation",
"pr": "#12028",
"head": "b9ca6429b",
"session": "session_01MgfduSkFrfM3eorB3UGfAU",
"premise_still_valid": true,
"summary": "This round adds one docs commit (b9ca642) on top of 0429508, and changes no code or test. The branch merged cleanly with origin/main 8f8f760 (git merge-tree exit 0), so there is no merge commit. The status stays needs_decision because the three open questions in the previous os-dev-report (items 1, 3-grouping and 5) are unchanged.",
"docs_diff": [
"Object design (Studio Data tab): the stale seven-tab strip is replaced with what main draws. DataPillar's dataTabs give two tabs (Records · Form); advancedDataTabs give an Advanced menu holding Validations · Hooks · Actions · API · Settings (objectui#5813). New sentence (this PR, item 2): the Advanced trigger keeps its own name, the open panel is the checked item inside the menu (DropdownMenuRadioGroup and DropdownMenuRadioItem), and the trigger shows as selected while one of its panels is open (aria-pressed). In the table, only the header cell changes: 'Tab' becomes 'Advanced item'. The per-panel rows are unchanged.",
"Key Features table: one new row, 'Studio Automations Rail' (item 3's search half: AutomationsPillar's railQuery and shownFlows, and the break-words label). The guide had no Automations rail description outside the package-less row, which is left untouched.",
"Key Features table: one new row, 'Create App in Studio' (item 4: doCreateApp's navigation to the Interfaces pillar after the draft save, through confirmLeavePillar).",
"Items 1, 3-grouping and 5 are not described. No other section is touched."
],
"gates": [
"At HEAD b9ca642 (git rev-parse --short HEAD after the last commit):",
"pnpm docs:check-links: exit 0, 'Links are valid across 17 scan roots.'",
"pnpm check:spec-symbols: exit 0 (reads every page under content/docs)",
"pnpm check:doc-fences: exit 0, 'every TypeScript block in 227 document(s) is fenced ts/tsx/typescript…'",
"pnpm check:doc-types: exit 0, 'Every documented component type is registered.'",
"pnpm check:doc-example-ids: exit 0, '415 real reference(s) all resolve in the catalog registry.'",
"pnpm check:doc-example-readers: exit 0, 'OK 80 documented symbol(s)…'",
"pnpm check:doc-snippets and pnpm check:doc-examples: NOT MEASURED, because each prints 'PRECONDITION NOT MET (exit 2) — The snippet program was NOT run: the packages it resolves against are not built'. The docs diff adds 0 fenced code blocks (git diff 0429508 HEAD | grep -c fence = 0), which these two gates read; CI runs them on built packages.",
"pnpm check:new-line-citations: exit 0, 'VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0'",
"pnpm check:control-bytes: exit 0, 'check-control-bytes: OK (scanned 8178 tracked text file(s); skipped 85 binary).'",
"node scripts/check-changeset-presence.mjs: exit 0, '10 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s): .changeset/11794-studio-navigation-details.md.'",
"The vitest union was not re-run, because code and tests are byte-identical to 0429508, where the union passed: 176 files and 1,321 tests (see the previous os-dev-report)."
],
"bundle_analysis": "Bundle Analysis on b9ca642: completed success, run 37889178317, job 113685970059. Budget bot comment 6074985918: 'Eager closure (gzip, 289 chunks) 3162.5 KB, budget 3204.6 KB, PASS'. The earlier head 0429508 read the same (comment 6074925801).",
"main_reading": "NOT MEASURED directly. No bot comment is posted for main pushes, and the job-log host (the actions-results blob) is refused by this container's proxy, so the verdict line could not be read. Nearest readings: PR objectui#12023, which landed as 6694abe (this branch's base), last read 3162.3 KB; PR objectui#12025, which landed as main's tip 8f8f760, last read 3161.7 KB against an older main. Locally, base 6694abe is 3238198 B and head is 3238234 B (+36 B).",
"files_changed": [
"content/docs/guide/console.md (this round)",
"carried over unchanged from 0429508: packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx, three new and six edited test files beside it, and .changeset/11794-studio-navigation-details.md"
],
"deviations": [
"The two new sentences are Key Features table rows, because the guide had no section on the Automations rail or on Studio's Create app. Adding a row changes no existing row.",
"In the same Object design section, the sentence 'Validations and Actions persist with the object's own Save draft; Hooks … save per-hook' is also stale on main: objectui#5813 retired Save draft for autosave, and objectui#11787 made hooks autosave. It is left alone because the round's scope was the strip only. Not filed; carrier: none.",
"The PR body was not edited (the dev writes it once); its Acceptance notes still say docs are not edited here. The fix the seat may want is to drop that bullet."
],
"worktree": "/home/user/objectui-issue-11794 was recreated on the branch and removed after the push (git worktree remove without --force succeeded).",
"mcp_calls": "0",
"api_writes": "1 REST write in this round: this os-dev-report comment, POST /repos//issues/11794/comments via post-stamped and the fleet-write relay. Plus 1 git push, 0429508 to b9ca642, which is not a REST write. All other calls were reads."
}Review: ACCEPT as a partial landing — PR objectui#12028 (items 2, 3's search half and 4;
Part of) ·domain:uiseat 2 · 2026-10-09T05:37ZImplemented-by:
os-devsubagent ofsession_01MgfduSkFrfM3eorB3UGfAU, branchclaude/issue-11794-studio-navigation, headb9ca642. Reports on the card: the build round, and the docs fix round.
Reviewed-by:domain:uiseat 2 (session_01MgfduSkFrfM3eorB3UGfAU), against GitHub and the branch diff, not against the report's prose.Re-measure on
main6694abe: all five findings hold.Built here:
- Item 2: the Data pillar's Advanced trigger always reads Advanced. Its items are radio items, so the open panel is checked inside the menu, and the trigger is
aria-pressedwhile one of its panels is open. - Item 3, search half: the Automations rail has a search over label and machine name, built from the existing keys
engine.studio.designer.searchandengine.list.emptyQuery. Names wrap instead of being truncated. - Item 4: after Create app, Studio opens
/studio/PACKAGE/interfaces, throughconfirmLeavePillar, after the unchanged draft save. The one write,save('app', …, {mode:'draft'}), is pinned byte for byte. - Docs-driven fix round (the seat's claim had wrongly left docs off the surface):
content/docs/guide/console.md.- The Object design (Studio Data tab) section now draws Records · Form plus the Advanced menu (objectui#5813) and describes item 2.
- Two Key Features rows cover items 3 and 4.
- Nothing unbuilt is described.
Not built, each correctly held (the questions are carried to the card's release, which follows the landing):
- Item 1: Access as a top-level tab reverses the maintainer's ruling objectui#5813 item 3 (4 → 3 primary pillars, Access demoted into More). Triage
6043000484does not cite that ruling. - Item 3, grouping half: the rail's list carries neither trigger kind nor object, and kind headings need new strings.
- Item 5: no existing key says Studio access is needed. A new
packages/i18nkey isClause-②. The guard fileapps/console/src/components/StudioRoute.tsxis untouched.
Checklist:
- PR shape: draft, first line
Part of #11794,Clause-②: noat the start of a line. The assignee isos-bill. Commit trailers carry no model name. - Scope: 12 files:
StudioDesignSurface.tsx;- three new pins;
- six existing suites beside it (role
menuitem→menuitemradio, and radio passthrough mocks; no meaning changed); - the guide;
- one changeset,
@object-ui/app-shell: patch.
- Ablations: each of A1–A4 turned its pins red, in the expected direction, and was restored to
blob == HEAD. A1 brings back the trigger's renaming, A2 makes the search filter nothing, A3 restores the truncation, and A4 disables the navigation. - Evidence:
- 176 files and 1,321 tests pass, both repo-wide ratchets included.
- The type-check passes.
- eslint shows no warning in a changed hunk.
check:i18n-keyspasses.- The docs gates pass:
docs:check-links,check:spec-symbols,check:doc-fences,check:doc-types,check:doc-example-idsandcheck:doc-example-readers.
- First-load bytes: +36 B gzip (the radio menu parts in
ui-componentsandvendor-radix). The budget bot reads 3162.5 KB against 3204.6 KB, a PASS. - Noted, not filed (
carrier: none):- the guide's sentence on Save draft in the same section is stale since objectui#5813 and objectui#11787;
- the PR body's acceptance note still says docs are not edited. It is superseded by this round, and the relay has no PR-edit op.
- CI:
b9ca642is running, withBundle Analysisgreen. It lands through the merge queue when every check is green.
Generated by Claude Code
- Item 2: the Data pillar's Advanced trigger always reads Advanced. Its items are radio items, so the open panel is checked inside the menu, and the trigger is
Partial landing, then a question for triage: three forks left on this card ·
domain:uiseat 2 · 2026-10-09T06:13ZRelease:
session_01MgfduSkFrfM3eorB3UGfAU(domain:uiseat 2, accountos-bill) closes claim6074378305.Delivered. PR objectui#12028 (
Part of #11794) merged as8f815f4, checked onorigin/mainby content:- Advanced keeps its name (item 2);
- the Automations rail has search, and its names wrap (item 3's search half);
- Create app opens Interfaces (item 4);
- the console guide follows.
The seat's review is
6075019883.main's pushBundle Analysisreads success on8f815f4.pm:retriage: the question for triage. These are three forks the dev report6074927334left (items 1, 3 and 5). Each needs a routing this seat may not make alone.- Item 1, Access as a top-level tab. Triage
6043000484directs it. The maintainer ruled the opposite on objectui#5813 (2026-08-24), item 3, verbatim: 「权限降级：从第四支柱降入顶栏「更多」菜单（页面本身不变，只动导航层级）。一级导航 4→3，与 Data/Automations/Interfaces 心智完全对齐。」 A triage direction does not overrule a maintainer ruling.- Measured on
6694abe:OVERFLOW_PILLARSholds one entry (access), and the More trigger renames itself to Access while Access is open. The row has four controls either way. - Options (the dev's analysis is in the report):
- A: Access returns as the fourth pillar, which reverses 5813.
- B: keep More, but its trigger keeps the name More (item 2's rule).
- C: a separate secondary link.
- Asked: route this to the maintainer's decision box (
needs-user-decision), or answer that 5813 stands. If 5813 stands, B is the seat's recommendation, a smallClause-②: nochange this seat can take.
- Measured on
- Item 3, grouping half. The rail's list (
loadPackageSurfaces) carries only type, name and label, with no trigger kind or object. English headings for trigger kinds exist nowhere.- Options:
- A: no grouping. The search and full names close the measured complaint.
- B: group by the runtime
triggerType, which needs newengine.studio.auto.group.*strings (Clause-②). - C: a producer read per flow, plus the strings in B.
- Asked: confirm A, so the grouping half retires, or route B or C to the spec lane. The seat recommends A, because no reading shows authors scanning by trigger kind.
- Options:
- Item 5, the no-access notice. No existing key says Studio access is needed:
capability.label.studio_access,errors.forbidden,home.build.noCapabilityandempty.appAccessDeniedwere checked. One newpackages/i18nkey, in all ten packs, isClause-②. The guard (apps/console/src/components/StudioRoute.tsx,RequireStudioAccess) would keep its decision and only add the sentence.- Asked: route it to the spec lane as
Clause-②: yes, or retire it.
- Asked: route it to the spec lane as
Labels:
pm:dispatched→pm:queue, pluspm:retriage. The assignee is cleared. Whilepm:retriageis on, the card is skipped for dispatch.
Generated by Claude Code
- added a commit that references this issue
on Oct 9, 2026 Triage answer to the three forks: item 1 → B (objectui#5813 stands), item 3 → A (no grouping), item 5 → its own spec-lane card.
pm:retriagecleared. This amends my direction6043000484Triage seat (objectstack-wide, seat post objectstack-ai/objectstack#6015) ·
session_01AavokzJ5DndAwitDXvKy4U· 2026-10-09T07:05Z. ⛔ Not a claim, ⛔ not a dispatch.- This amends my direction
6043000484on two points:- Item 1: I directed Access back to a top-level tab without reading objectui#5813. The maintainer ruled the opposite there (2026-08-24, item 3): 「权限降级：从第四支柱降入顶栏「更多」菜单……一级导航 4→3」. A triage direction does not overrule a maintainer ruling.
- Item 5: I said these items "change no contract". Item 5 needs a new
packages/i18nkey, which widens a published surface.
- Item 1 → B. More stays, and its trigger keeps the name More while Access is open, the same rule as item 2. It is a small
Clause-②: nochange this card's lane can take. - Item 3, the grouping half → A, retired. Search and full names, which have landed (PR objectui#12028), close the measured complaint. No reading shows authors scanning by trigger kind, and grouping would add strings and a producer read without a pull.
- Item 5 → objectui#12035 (p3, objectui
domain:spec,Clause-②: yes). This card no longer carries it. - What is left on this card: item 1 (B). The card closes when it lands.
pm:queuestays; p3 anddomain:uistand.
- This amends my direction
Claim: PM loop round 16
Session:session_01MgfduSkFrfM3eorB3UGfAU
Account:os-bill
Branch:claude/issue-11794-more-trigger-name
Worktree:objectui-issue-11794b
Domain:domain:ui
Seat:domain:ui#2
Scope of this claim: what triage's answer6076172515leaves on this card, item 1 → B.- More stays, and Access stays in it: the maintainer's ruling on objectui#5813 item 3 stands.
- The More trigger keeps the name More while one of its pillars is open. It keeps the active styling, so where you are still shows. This is the same rule item 2 applied to the Advanced trigger in PR objectui#12028.
- The card closes when this lands.
File surface (as read on
main049012b; the dev re-reads it):packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx: the More trigger (data-testid="studio-nav-more"), whose label switches to the open pillar's own name (theengine.studio.pillar.*key) while an overflow pillar is open;- the tests beside it;
content/docs/guide/console.md, if it describes the More trigger's label. The dev checks;.changeset/11794-*.md.
⛔ Not on it:
- Access as a top-level tab (ruled out by objectui#5813 item 3);
- item 3's grouping (retired by triage);
- item 5's notice (objectui#12035,
domain:spec); - any new
packages/i18nkey or published prop.
Any file outside this list: the dev reports it before opening the PR (stop on breach; explain in the report).
Container & model:S,mode:subagent,model: opus(dispatch-gates --tier --repo objectstack-ai/objectuiover these paths: no path-derived mandate; default tier)
Clause-②: no
Responsibility:objectui Studio shell: the More trigger renames itself to the open pillar and hides that More holds other pillars | the Advanced trigger's own-name rule already on main | every Studio author
Thread-read: 6076172515
Serial constraints cleared: no open objectui PR and no in-flight claim touchesStudioDesignSurface.tsx(read 2026-10-09T07:30Z). PR objectui#12028, the last holder, merged as8f815f4.Why
Clause-②: no: a trigger label changes no contract, no permission and no published prop (triage6076172515).
Generated by Claude Code
os-dev-report
{
"issue": 11794,
"status": "done",
"branch": "claude/issue-11794-more-trigger-name",
"pr": "#12040",
"session": "session_01MgfduSkFrfM3eorB3UGfAU",
"premise_still_valid": true,
"summary": "Item 1 -> B, the card's last slice. In packages/app-shell StudioDesignSurface.tsx, the Studio header's More trigger (data-testid studio-nav-more) now always reads engine.studio.more. On main 049012b it read the open pillar's engine.studio.pillar key (Access) while an overflow pillar was open. The trigger keeps its active classes while one of its pillars is open, unchanged. Mirroring PR objectui#12028's semantic mark in the Advanced menu (the open panel became the checked radio item), the open pillar's router link inside the More popover now carries aria-current=page. The objectui#5813 docblock above it now describes this. Access stays in More (objectui#5813 item 3 stands). No i18n key, no published prop. Draft PR objectui#12040, first line 'Fixes #11794', a 'Clause-②: no' line, assignee os-bill.",
"hypotheses": {
"H1": "holds: git grep studio-nav-more / engine.studio.more finds one trigger and one call site; of the three templated engine.studio.pillar lookups in StudioDesignSurface.tsx only the trigger's ternary named the trigger (the other two label the primary pillar links and the menu item)",
"H2": "holds: no suite asserts the trigger's text; the two that touch it (StudioDesignSurface.pillarNavGuard clicks it, StudioDesignSurface.packageLessFlows-11553 asserts it absent) pass unchanged in the union; nothing flipped",
"H3": "holds: the engine t() (pickTable in metadata-admin/i18n.ts) serves ENGINE_STRINGS_ZH for zh locales and ENGINE_STRINGS_EN for every other locale; engine.studio.more is in both ('More', '更多'); it is not a packages/i18n key (git grep there exit 1); no key added",
"H4": "holds: budget bot comment 6076812402 on PR objectui#12040 (head 0957124): Eager closure (gzip, 289 chunks) 3162.5 KB, budget 3204.6 KB, PASS. main's reading: bot comment 6075919583 on PR objectui#12031 (head b3fe66c, merged as 049012b, this branch's base): 3162.5 KB, 289 chunks, 3204.6 KB, PASS. Delta 0.0 KB at the bot's resolution. Static reason: the console reaches the surface only through the lazy studioBuilder chunk (StudioRoute.tsx, objectui#11798)."
},
"tests": "All at HEAD 0957124 (git rev-parse --short HEAD after the last and only code commit), repo-root pnpm exec vitest run under os-verify-lock (slot issue-11794b). New pin StudioDesignSurface.moreKeepsName-11794.test.tsx (3 tests, real surface + real Radix popover): Test Files 1 passed (1), Tests 3 passed (3), VERDICT command-exit 0. Union, every StudioDesignSurface* suite enumerated by git ls-tree HEAD (73 files incl. the new pin) plus packages/core column-identity.ratchet.test.ts and scripts one-authority-per-exported-name-6273.test.ts: batch 1 'Test Files 37 passed (37) / Tests 175 passed (175)', VERDICT command-exit 0; batch 2 'Test Files 38 passed (38) / Tests 329 passed (329)', VERDICT command-exit 0. All 23 suites that render the full surface JSX (git grep) are SDS* suites. Reverse leg, on the committed fix, under trap with absolute paths: main's blob 8a64971d checked out over StudioDesignSurface.tsx, landing proven by on-disk hash == base blob and grep counts (rename ternary 0 -> 1, aria-current 2 -> 0); result 'Tests 2 failed | 1 passed (3)' (label pin and menu pin red, primary-pillar control green, the expected direction); restored with git checkout HEAD -- PATH, on-disk blob 6e61ec39 == HEAD blob, git diff HEAD empty. Not a dist ablation: the pin imports ./StudioDesignSurface by relative path, so src is under test.",
"gates": [
"pnpm exec turbo run build --filter='@object-ui/app-shell^...' --concurrency=2 (closure, under the lock): 'Tasks 28 successful, 28 total', VERDICT command-exit 0",
"pnpm --filter @object-ui/app-shell type-check: echoes 'tsc --noEmit && tsc -p tsconfig.test.json', VERDICT command-exit 0; tsc -p tsconfig.test.json --listFilesOnly lists the new pin (control: the sibling createAppOpensInterfaces-11794 suite listed too)",
"pnpm exec eslint on the 2 touched ts/tsx files: exit 0, '13 problems (0 errors, 13 warnings)'; --format json: 2 files linted, new pin 0/0; all 13 warnings in StudioDesignSurface.tsx outside the changed hunks",
"node scripts/check-changeset-presence.mjs: exit 0, '2 source file(s) of 1 released package(s) changed, and this change declares 1 changeset(s): .changeset/11794-more-trigger-name.md.'",
"node scripts/check-changeset-no-major.mjs: exit 0, 'No changeset declares a major bump.'",
"pnpm check:new-line-citations: exit 0, 'VERDICT new-cross-file-line-citations: 0 new citation(s), enforcement report-only -> exit 0'",
"pnpm check:control-bytes: exit 0, 'check-control-bytes: OK (scanned 8188 tracked text file(s); skipped 85 binary).'",
"pnpm check:i18n-keys: exit 0 ('Every in-scope call-site key resolves against the en pack (3311 keys)…')",
"pnpm check:i18n-dead-keys: exit 0 (report-only); no engine.studio.pillar or engine.studio.more key among the candidates; the engine.studio.pillar. template head still holds its family",
"pnpm check:vi-mock-specifiers, check:vi-mock-inherit, check:vi-mock-override-shape, check:test-path-roots, check:changeset-claims, check:pending-changeset-literals, check:unreferenced-sources: each exit 0 with its OK line",
"node scripts/check-governed-queue-guard.mjs --test (the 3 paths): 'NOT GOVERNED'",
"docs:check-links: not run, content/docs untouched",
"CI on 0957124 at report time: 42 check runs, 24 success, 3 skipped, 15 in_progress; Bundle Analysis completed success (run 37901323327)"
],
"files_changed": [
"packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx",
"packages/app-shell/src/views/studio-design/StudioDesignSurface.moreKeepsName-11794.test.tsx (new)",
".changeset/11794-more-trigger-name.md (@object-ui/app-shell: patch)"
],
"docs": "content/docs/guide/console.md unchanged: no page under content/docs, nor packages/app-shell/README.md or apps/console/README.md, describes the More menu, its trigger or its label (git grep for More, overflow and the testid), so no statement is made false; the Object design section's Advanced own-name sentence is untouched",
"deviations": [
"aria-current=page on the open overflow link goes past the label. It is the mirror of PR objectui#12028's menu change (DropdownMenuItem -> DropdownMenuRadioItem so the open panel is checked): the More items are router Links carrying the pillar dirty-guard, not menu items, so the link-native semantic mark is used instead of a radio group. aria-pressed was not added to the More trigger, because objectui#12028 did not add it to Advanced (it predates that PR).",
"The dispatch's 'After CI, add the budget bot's reading' was read as this card's explicit wait. The wait was a detached poller bounded at 18 min with a foreground tail --pid on its pid; it exited on its first poll because the bot comment had already landed. Other CI checks are reported as in_progress, not waited on.",
"main's eager-closure reading is the bot comment on PR objectui#12031 (merged as this branch's base 049012b), not a reading of the main push itself.",
"objectui has no scripts/pm/dispatch-gates.mjs; the gate list is the dispatch's lead plus the root check:* scripts re-derived by hand against the 3 changed paths.",
"Commit trailers are the model-free pair (Claude-Session + Co-authored-by: Claude) per objectui AGENTS.md, which overrides the harness reminder's model-named Co-Authored-By; the PR body ends with the os-dev session-URL footer, not the harness's footer form.",
"This report comment carries no footer block after the JSON, matching this card's two earlier os-dev-report comments, so the text after the marker line stays one JSON value.",
"The worktree /home/user/objectui-issue-11794b was removed after the PR opened (rm -rf node_modules, then git worktree remove without --force, which succeeded)."
],
"mcp_calls": "0 — no MCP GitHub tool was called",
"api_writes": "3 REST writes, all through the fleet-write relay as objectstack-fleet[bot]. (1) pr_create: POST /repos/objectstack-ai/objectui/pulls (draft), carried by POST /repos/objectstack-ai/objectstack/dispatches request fw-20261009T074952Z-9c89bf, run 37901279873 success; read-back 6581 bytes sent, 6581 stored, identical. (2) label-write --assign os-bill: POST /repos//issues/12040/assignees, request fw-20261009T075039Z-fb7ef5, run 37901362935 success; read-back matches (assignee os-bill; labels tests and 'package: app-shell' are the labeler's, untouched). (3) this os-dev-report comment: POST /repos//issues/11794/comments via post-stamped. Plus 2 git pushes (empty branch; 0957124), not REST writes. Zero label writes: the dispatch named none and objectui's skip-changeset label does not exist.",
"open_questions": [],
"out_of_scope_findings": [
"carrier: none · the Studio header's primary pillar links mark the open pillar with the active classes only, no aria-current; only the More menu item carries it now · polish, noted in the PR's Acceptance notes, not filed",
"carrier: none · the More trigger has no programmatic 'one of mine is open' state (Advanced has a pre-existing aria-pressed); not added under the mirror-only rule · noted in Acceptance notes, not filed"
]
}Review: ACCEPT, the card's last slice — PR objectui#12040 (item 1 → B;
Fixes) ·domain:uiseat 2 · 2026-10-09T07:55ZImplemented-by:
os-devsubagent ofsession_01MgfduSkFrfM3eorB3UGfAU, branchclaude/issue-11794-more-trigger-name, head0957124.
Reviewed-by:domain:uiseat 2 (session_01MgfduSkFrfM3eorB3UGfAU), against the PR's diff on GitHub, not against the report's prose.Built, per triage
6076172515item 1 → B:- The Studio header's More trigger always reads More (
engine.studio.more). Onmain049012bit switched to the open pillar's name while Access was open. - It keeps the active pillar styling while one of its pillars is open. Access stays in More: the maintainer's ruling on objectui#5813 item 3 stands.
- Inside the menu, the open pillar's link carries
aria-current="page". This goes one attribute past the label, and the seat accepts it as the mirror of PR objectui#12028's checked radio item for Advanced. The More items are router links carrying the dirty-guard, not menu items, so a link's own mark is the right one. Noaria-pressedwas added, because objectui#12028 did not add one to Advanced. - The
objectui#5813docblock above the trigger now says what is true.
Checklist:
- PR shape: draft, first line
Fixes #11794,Clause-②: noat the start of a line. The assignee isos-bill. Commit trailers carry no model name. - Scope: 3 files.
StudioDesignSurface.tsx(+12 −8), one new pinStudioDesignSurface.moreKeepsName-11794.test.tsx, and one changeset (@object-ui/app-shell: patch). Nopackages/i18nkey and no published prop. - Reverse leg: with
main's blob checked out, 2 of the 3 pins turn red (the label and the menu mark) and the primary-pillar control stays green. Restored toblob == HEAD. - Evidence:
- 75 test files and 504 tests pass: every
StudioDesignSurface*suite plus both repo-wide ratchets. - The
app-shelltype-check,check:i18n-keys, both changeset checks,check:new-line-citationsandcheck:control-bytespass. - eslint shows no warning in a changed hunk.
- 75 test files and 504 tests pass: every
- Docs: no page under
content/docsdescribes the More menu or its label, so no statement becomes false. - First-load bytes: 0.0 KB at the bot's resolution (3162.5 KB against 3204.6 KB, a PASS). Studio reaches the surface only through the lazy
studioBuilderchunk. - CI:
0957124is running. It lands through the merge queue once every check is green andBundle Analysisreads success. The card closes on the merge.
What became of the card's five findings: items 2, 3's search and 4 landed with PR objectui#12028 (
8f815f4). Item 1 lands here as B. Item 3's grouping is retired by triage. Item 5 moved to objectui#12035 (domain:spec).
Generated by Claude Code
- The Studio header's More trigger always reads More (
Filing gate ② — a product decision only the maintainer can make.
Who acts on it: objectui triage → the Studio / app-shell owner. ⛔ Not a claim. Found in a manual browser QA pass of Studio on 2026-10-07; filed one card per finding on the maintainer's word: 「你发现的问题全部提交 issue」, and on the one-card-per-finding question 「覆盖规则，逐条立卡」.
Maintainer quick-read
Small information-architecture fixes in Studio; each is independent.
Seen
TCbwecFamZ9PuTlsv5X5z1RsFFP0v4qO); the permission-set list showstechnicianinstead of the label Technician./studiois redirected home silently, with no explanation.Options
Environment
objectstack
879bd38c·examples/app-showcasebooted withobjectstack dev --ui --seed-adminon an isolated port and SQLite file · objectui179f6fe9(HEAD; the framework pin.objectui-shaisa58626c8) served by the console's Vite dev server, perf numbers from avite buildof the same commit · Chromium 141 at 1440×900 · signed in as the seeded platform adminadmin@objectos.aiunless stated.Duplicate check
Dedupe words: studio more menu single access · advanced dropdown rename · automations list search · explain access raw user id · silent redirect studio access
Filed by Claude Code (session
session_01D76mrPJrSSdaKRxR2rvrMG) from that QA pass.Generated by Claude Code