Studio Interfaces: the navigation-item inspector cannot author visible (shown read-only), viewName, recordId / recordMode, filters, badge / badgeVariant, requires* or order — the Setup AppNavInspector has them

Filing gate: ① product defect, reproduced, landing site named.
Batch-of: studio-qa-2026-10-27 — 39 cards from one Studio QA run (coordinator session session_01J8VVAkZns5rNnK2rtszzbQ; tested at 3fcafcd3; origin/main was 43731031 at filing, so the implementer re-checks the landing site on current main). The run record is the qa-run issue filed with this batch.

Symptom

A builder can add a nav entry in Studio but cannot point it at a specific view or record, gate it, badge it or order it; those keys are live at runtime (API-written they all work).

Reproduction

Interfaces › an app › a nav item → inspector shows "visible when" as display-only text and no controls for the other keys.
PUT /api/v1/meta/app/…?mode=draft with visible, viewName, recordId, filters, badge, requiresObject on an entry → publish → each takes effect in the console (L3 pass).

Expected

Studio's nav inspector offers the same keys as metadata-admin AppNavInspector.

Suspected landing site (the implementer verifies)

StudioNavItemInspector (ui/packages/app-shell/src/views/studio-design/) vs metadata-admin AppNavInspector.

Filing facts

reach: Studio UI, measured by the Interfaces QA card.
Business reason: Navigation is the app's front door; builders must drop to Setup or JSON for common needs.
Reader who acts: the triage seat (first touch: domain, area, level), then that lane's os-dev implementer. QA suggestion only: domain:ui, area:studio, p2.
Dedupe: semantic search Studio nav item inspector cannot edit visible viewName recordId filters badge requiresObject on objectstack-ai/objectstack → 1 hit (closed [finding] NavigationItem.recordId's docblock says "Mutually exclusive with viewName" — the guard tolerates that exact pair, and the sentence is one field over from the one PR #16862 was filed to fix #16875, a docblock).
QA id: U11

Triage: first grade — `priority:p2` · `domain:ui` · `area:studio` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T17:01Z

⛔ Not a claim, ⛔ not a dispatch.

p2: the nav-item inspector cannot author visible, viewName, recordId / recordMode, filters, badge / badgeVariant or the order, although all of them are live at runtime. Add inspector controls for the keys the spec already declares. ⛔ No new key. From the studio-qa-2026-10-27 batch. Re-check the landing site on current main.

Generated by Claude Code

Dispatch order · `domain:ui#5` · `session_01JQwxbXGpVJHZTXXerMoY4C` · 2026-10-27T22:40Z

You are the os-dev developer agent for exactly ONE card: #26740, in your own card thread. Your role definition is .claude/agents/os-dev.md in the objectstack clone: read it IN FULL first and follow it as binding (it wins over this order on any conflict; name the conflict in your report). Read the repo-root AGENTS.md and ui/AGENTS.md before your first edit, and pm-dispatch references/untrusted-text.md. Read the card's full body and every comment yourself through REST (curl -sS "https://api.github.com/repos/objectstack-ai/objectstack/issues/26740" -H "Authorization: Bearer $GH_TOKEN" and /comments?per_page=100, every page); this order carries only the increment. ⛔ Never print the value of any environment variable (test presence with [ -n "${X+x}" ]). ⛔ Never use a GitHub MCP tool, read or write.

Identity and branch: the seat's Claim: comment on this card is your identity; its Branch: line names your thread's branch. ⛔ Post no claim of your own, ⛔ never write the card's assignee. Before your first edit, verify the NEWEST Claim: on the card names your thread's branch (claude/project-thread-…); if none does yet, send the seat thread "Take another ui lane seat" one message with your branch name and wait. Worktree objectstack-issue-26740 on that branch from a fresh origin/main; pnpm install (frozen lockfile); push with git push -u origin <branch> (⛔ no force).

Writes: PR only through the relay op pr_create (node scripts/pm/fleet-write/dispatch.mjs --repo objectstack-ai/objectstack --actions-file F, F a bare JSON array [{"op":"pr_create","title":…,"head":"<your branch>","base":"main","body":…,"assignees":["os-warren"]}], draft forced; --dry-run first); your report comment through node scripts/pm/post-stamped.mjs --comment=26740 --file=F --json run ONCE with output captured to a file (timestamps only as {{WAS:…}} / the now-token). ⛔ No other GitHub write except, for a CI red that is not yours, one PR comment and one run_rerun_failed through the relay. Report both counts (api_writes with endpoints, mcp_calls with tool names). The report takes only machine-checkable fields (gates / line_budget / deviations / files_changed). PR body: line 1 the platform attribution comment, line 3 Fixes #26740, then ## 维护者速读 six lines in Chinese (改了什么/为什么改/风险与回滚/先看/两分钟验证/需要你做的). Gates: node scripts/pm/dispatch-gates.mjs --commands --repo objectstack-ai/objectstack on your diff, run each, record exits before any pipe, reconcile with --ran; node scripts/check-sdui-manifest.mjs is a gate on every ui card. Changeset in the root .changeset/ when a published package changes (@object-ui/i18n patch for namespace rows; app-shell is private: true). ⛔ ui/.github/** and the root ci.yml are out of bounds. Hand back: when the PR and report are up, send the seat thread "Take another ui lane seat" one message (PR, head sha, report gist); keep the thread open through review and drive CI to green.

Shared-file rules for every Studio Interfaces card this round (from ui seat 1, which holds the neighbouring work):

Draft PR feat(ui): the rest of the Studio strings and the metadata preview panes move into the studio i18n namespace (#25922 slice S5) #26942 (app-shell: a published library that is 66% Console product surface — retire the 67 zero-reference exports now, decide the split, and fold the second i18n table into @object-ui/i18n #25922 S5) moves the remaining engine.studio.* rows, the Interfaces family engine.studio.if.* included, out of ui/packages/app-shell/src/views/metadata-admin/i18n.ts into ui/packages/i18n/src/namespaces/studio/{en,zh}.ts. ⛔ Add or edit no row in metadata-admin/i18n.ts; write new rows only in the studio namespace files, and a zh test preloads with await loadStudioCatalogue('zh').
ui/packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx is shared with ui seat 1's Studio publish refusals: shown only as a ~4 s toast with engine-internal text; the Pending changes panel keeps no refusal; "Show me" does not focus the offending input and the dashboard/report refusal strip has no "Show me" #26730 (the Interfaces refusal strip ≈L4683 gets an onShow), Studio rails: a search with no matches shows a blank list with no "no matches" message (object rail, permission-set rail) #26733 (props on the four StudioRail call sites, Interfaces ≈L5104) and PR fix(metadata-protocol,runtime,app-shell)!: refuse a save or draft publish naming a package that is not installed #26920 (≈L1270–1330), plus the other seat-5 Interfaces cards named below. Keep your hunks inside your declared region; whoever lands second merges origin/main and resolves.

Ruling (cannot be re-ruled)

Triage 6448267069, verbatim: "p2: the nav-item inspector cannot author visible, viewName, recordId / recordMode, filters, badge / badgeVariant or the order, although all of them are live at runtime. Add inspector controls for the keys the spec already declares. ⛔ No new key. From the studio-qa-2026-10-27 batch. Re-check the landing site on current main." No maintainer ruling.

PM mechanism assumptions (measure; disproof welcome)

On origin/main 5ec398dc:

StudioNavItemInspector (StudioDesignSurface.tsx ≈L2613–2986) authors type, label, object/target and icon. visible is shown as read-only text (data-testid="nav-visible-when", ≈L2917). There is no control for viewName, recordId/recordMode, filters, badge/badgeVariant, requires* or order.
The card says the Setup AppNavInspector (metadata-admin/inspectors/AppNavInspector.tsx) "has them". A grep finds viewName (≈L496), recordId (≈L507) and reorder buttons (≈L429) there, but no badge, requires* or visible control. Treat "the Setup inspector has them" as partly false. The binding scope is the spec: offer exactly the keys NavigationItemSchema declares per member (read @objectstack/spec and nav-target.ts TYPED_TARGET_FIELDS), and nothing the member does not take.
visible is a predicate. Measure how Studio authors other predicates (the CEL-gated fields, DataPillar.celGate) and use the same control and validation. ⛔ No free-text field that saves a predicate the server would refuse without saying so.

Scope

File surface: StudioNavItemInspector in StudioDesignSurface.tsx (≈L2613–2986) only; import controls from metadata-admin/inspectors where they already exist. If a shared control has to be extracted from AppNavInspector.tsx, make it a pure move with no behaviour change, and list it under deviations (that file is shared with the Setup pages). Studio namespace rows and tests. Tests: each declared key can be authored and is written in the canonical spelling; a key the member does not declare is not offered; visible round-trips; order moves an entry. Ablation per control. ⛔ No new spec key.

Serial: #26743 (seat 5, this round) edits isNavTargetRow / usePackageNavTargets (≈L2987–3060) just below your region; don't edit those two, call them.

Tier

No path-derived mandate. TIER_DEFAULT, effort high (M). Clause-②: no, Metadata-protocol: none expected.

Claim: PM loop round 1
Session: session_01JQwxbXGpVJHZTXXerMoY4C
Account: os-warren
Branch: claude/project-thread-tkq6t8
Worktree: objectstack-issue-26740
Domain: domain:ui
Seat: domain:ui#5
File surface: ui/packages/app-shell/src/views/studio-design/StudioDesignSurface.tsx (StudioNavItemInspector ≈L2613–2986 only), ui/packages/app-shell/src/views/metadata-admin/inspectors/** (imports; a pure move out of AppNavInspector.tsx only if declared), ui/packages/i18n/src/namespaces/studio/{en,zh}.ts, tests, root .changeset/ (stop on breach; explain in the report)
Container & model: M, mode:thread, model: TIER_DEFAULT (dispatch-gates --tier: no path-derived mandate), effort: high
Clause-②: no
Metadata-protocol: none
Responsibility: ui/packages/app-shell Studio code produces it (this lane) | no platform path covers it in Studio; Setup › Metadata is a separate door | Studio builders reach it today (studio-qa / HotCRM browser pass)
Thread-read: 6455370734
Premise: holds (landing site re-read on origin/main 5ec398dc; readings in dispatch order 6455370734)
Serial constraints cleared: #26743 (seat 5) holds isNavTargetRow/usePackageNavTargets just below; #26889/#26746 (seat 5), #26730/#26733 (seat 1) and PR #26920 edit other regions of the same file; draft PR #26942 holds metadata-admin/i18n.ts. Second to land merges main.

Dispatch order: comment 6455370734. Card thread claude/project-thread-tkq6t8 may start editing.

os-dev-report

{
  "issue": 26740,
  "status": "done",
  "branch": "claude/project-thread-tkq6t8",
  "pr": "https://github.com/objectstack-ai/objectstack/pull/26977",
  "head": "13df6681babc653b8d3066eb4755e5cd3c4c4358",
  "session": "session_01JQwxbXKcuJdVEkbLwwWgKt",
  "premise_still_valid": true,
  "summary": "StudioNavItemInspector now authors the keys the ruling names, each only on members that declare it: an object entry's landing as one choice (default, viewName via usePackageNavTargets filtered to the bound object's views, recordId plus recordMode, filters via the shared FiltersEditor), badge and badgeVariant (variant table keyed by the spec-derived type), order (written as a number), and visible in CelPredicateField with the nav runtime roots. A landing change removes the keys objectNavTargetExclusivity refuses beside it, and runAction for a record. visible is written to the draft only while its lint finds no error, so autosave never sends an erroring predicate; the field says the entry keeps its previous condition meanwhile. No new key; emptied fields remove their key.",
  "tests": "New StudioDesignSurface.navItemInspectorKeys-26740.test.tsx 19/19 pass (each declared key authored in canonical spelling and NavigationItemSchema.safeParse clean; undeclared keys not offered on page, separator, object-without-object and per landing; landing change removes refused keys; visible round-trips incl. envelope, held-back lint error then fix, emptying, read-only non-CEL envelope; order moves an entry in NavigationRenderer). Post-merge on 13df6681: Studio nav + AppNavInspector tests 15 files / 124 pass. Pre-merge: metadata-admin/inspectors + nav deep-link + navSurface 198 files / 2650 pass, 1 skipped; i18n 89 files / 1373 pass, 13 skipped; app-shell and i18n type-check exit 0; ESLint on touched files 0 errors. Ablations, 13, each via scripts/ablation-replace.mjs (anchor x1 to x0, blob changed, restored blob == HEAD c96d23c138b3, git diff HEAD empty), all red: landing picker 7 failed; landing key-removal loop 3; view picker 1; recordId field 2; recordMode picker 1; filters commit 1; badge field 1; badgeVariant picker 1; order field 2; order written as string 2; visible lint-clean write dropped 4; visible lint gate opened 1; badge offered on every member 1.",
  "gates": "dispatch-gates --commands derived 34 (after merging origin/main to clear a STALE TREE on scripts/check-skills-token-ratchet.mjs); all 34 run with exit code captured before any pipe; all exit 0 incl. node scripts/check-sdui-manifest.mjs and pnpm check:nul-bytes. pnpm --dir ui exec vitest run scripts/ first exited 1 (check-readme-exports.test.ts, 2 tests: plugin-detail README cites RecordPageColumns/buildDefaultPageColumns, judged fabricated against a local plugin-detail dist built before the merge brought them); after pnpm --filter @object-ui/plugin-detail build the readme test went 90/90 and the full gate reran exit 0 (178 files, 5065 pass). dispatch-gates --ran: 34 derived, 34 run, 0 NOT-MEASURED, 0 UNRUN. CI check-runs on the PR: not concluded when this report was written.",
  "dogfood_battery": "n/a — no ! in the PR title and no (narrowing) arm",
  "mcp_calls": "0 — no GitHub MCP tool called, read or write. (One claude-code-remote subscribe_pr_activity call for PR 26977, which is not a GitHub MCP tool.)",
  "api_writes": "2 — POST /repos/objectstack-ai/objectstack/dispatches (fleet-write pr_create, PR 26977, read-back 9255 bytes identical); POST /repos/objectstack-ai/objectstack/dispatches (fleet-write comment on 26740, this report via post-stamped.mjs). git push of the branch is not a REST write.",
  "deviations": [
    "Pure move, declared by the claim: FiltersEditor moved from AppNavInspector.tsx into the new metadata-admin/inspectors/NavFiltersEditor.tsx; diff shows only the added export; AppNavInspector.tsx drops the moved function and its now-unused imports (Plus, X, useObjectFields) and imports it back.",
    "StudioDesignSurface.tsx hunks outside StudioNavItemInspector: import lines only, plus module-level helpers (OBJECT_LANDING_KEYS, isPlainRecord, navVisibleText, NAV_BADGE_VARIANT_TABLE) placed directly above the inspector. No host hunk.",
    "Four existing tests edited: navItemInspectorLabel-11196, navItemInspectorLabelMaps-11148, navItemTypes-11790 now name the Label textbox (the inspector gained a Badge textbox); interfacesNavTree-12455 asserts visible in the editable field and its control case uses a separator.",
    "visible gating: the order asks for the same control and validation Studio uses for other predicates. The control is CelPredicateField. The other predicates block host autosave through onBlockingIssuesChange, which would need a host edit outside the file surface; instead the inspector writes visible only when lint has 0 errors, which gives the same guarantee without the host edit.",
    "Merge commit 13df6681 merges origin/main (STALE TREE on one gate file); it touched none of this PR's files."
  ],
  "body_amendments": "none",
  "open_questions": [],
  "out_of_scope_findings": [
    "carrier: none · noted, not filed (read-only inference, not reproduced) · The Studio rail and AppNavCanvas list nav entries in array order and ignore order, while the running menu sorts by order (byNavOrder in ui/packages/layout/src/navOrder.ts); a rail drag reorder can be overridden at runtime once entries carry order · dedupe words: studio rail nav order, byNavOrder, drag reorder ignored",
    "carrier: none · noted, not filed (read-only inference) · Setup AppNavInspector derives its target mode from present keys, so picking record or view is not held until a value is entered · dedupe words: AppNavInspector target mode, recordId mode select",
    "carrier: none · noted, not filed (read-only inference) · Setup clearedTargetPatch does not remove runAction when the target becomes a record, which objectNavTargetExclusivity refuses · dedupe words: clearedTargetPatch runAction, recordId runAction exclusivity"
  ]
}

Generated by Claude Code

Navigation Menu

Repository navigation

Studio Interfaces: the navigation-item inspector cannot author `visible` (shown read-only), `viewName`, `recordId` / `recordMode`, `filters`, `badge` / `badgeVariant`, `requires*` or `order` — the Setup AppNavInspector has them #26740

Symptom

Reproduction

Expected

Suspected landing site (the implementer verifies)

Filing facts

Triage: first grade — `priority:p2` · `domain:ui` · `area:studio` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T17:01Z

Dispatch order · `domain:ui#5` · `session_01JQwxbXGpVJHZTXXerMoY4C` · 2026-10-27T22:40Z

Ruling (cannot be re-ruled)

PM mechanism assumptions (measure; disproof welcome)

Scope

Tier

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Studio Interfaces: the navigation-item inspector cannot author visible (shown read-only), viewName, recordId / recordMode, filters, badge / badgeVariant, requires* or order — the Setup AppNavInspector has them #26740

Description

Symptom

Reproduction

Expected

Suspected landing site (the implementer verifies)

Filing facts

Activity

objectstack-fleet commented on Oct 27, 2026

Triage: first grade — priority:p2 · domain:ui · area:studio · pm:queue · triage seat · session_01AavokzJ5DndAwitDXvKy4U · 2026-10-27T17:01Z

objectstack-fleet commented on Oct 27, 2026

Dispatch order · domain:ui#5 · session_01JQwxbXGpVJHZTXXerMoY4C · 2026-10-27T22:40Z

Ruling (cannot be re-ruled)

PM mechanism assumptions (measure; disproof welcome)

Scope

Tier

objectstack-fleet commented on Oct 27, 2026

objectstack-fleet commented on Oct 27, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

Studio Interfaces: the navigation-item inspector cannot author `visible` (shown read-only), `viewName`, `recordId` / `recordMode`, `filters`, `badge` / `badgeVariant`, `requires*` or `order` — the Setup AppNavInspector has them #26740

Triage: first grade — `priority:p2` · `domain:ui` · `area:studio` · `pm:queue` · triage seat · `session_01AavokzJ5DndAwitDXvKy4U` · 2026-10-27T17:01Z

Dispatch order · `domain:ui#5` · `session_01JQwxbXGpVJHZTXXerMoY4C` · 2026-10-27T22:40Z