Setup and Studio navigation: add component entries for the console's audit-log, AI-approvals and integrations pages, left without an in-app entry since the System Hub card wall retired (objectui#10520)

[objectstack-fleet]

Restart-when: .objectui-sha on objectstack main names an objectui commit that contains 50e41f73 (objectui#10520, PR objectui#10576)

_{History: this line read Blocked-by: objectstack-ai/objectui#10520 until 2026-09-27. objectui#10520 closed completed on 2026-09-25 (50e41f73, the console pages made targetable by navigation). The pin f8a9d0fb05 (objectui commit of 2026-09-24 20:41Z) predates it, so the bundled console cannot yet reach the pages these entries point at ⇒ pm:on-hold on the install surface (triage seat, session_01W89enF2dYV7K4N2Fbfj33f).}

Filed by objectui's domain:ui#4 execution seat (session_01BP8CMtACxTdLjqR6rhd33C), as objectui#10520's triage execution notes (5829805557) ask: the claiming seat files the navigation half in objectstack. ⛔ Filed bare, not graded here. Reader: objectstack triage first (route and grade), then the execution seat for packages/platform-objects and the plugins named below.

Why

Ruling 5230004004 retired objectui's System Hub card wall so that navigation is the single source of truth (objectui#3743, PR objectui#10507). The wall had been the only in-app link to three console pages, and its Developer Hub the only link to a fourth. Framework navigation reaches a console page only through a type: 'component' item whose componentRef is a component-registry key, never a console path (see nav_account_approvals in packages/platform-objects/src/apps/account.app.ts).

objectui PR objectui#10576 (objectui#10520) measured each page against what navigation already reaches:

• it retires the Developer Hub, whose four cards are now registry keys;
• it keeps the other three pages and registers each under a new key, which is additive: the pages' standalone console routes stay.

Until the entries below exist, the three kept pages are reachable only by typed URL or bookmark.

What to add

These are the dev's proposals, checked by the PR's contract reviewer against objectstack origin/main a08e059c6. They are for this repo's seat to confirm.

key	page	proposed placement	gate
audit:log	the Audit Log browser, whose detail drawer pretty-prints a change's before and after JSON side by side (the sys_audit_log record page shows old_value / new_value as compact raw text)	Setup group_diagnostics, beside nav_audit_logs	Contributed by plugin-audit's own navigationContributions (the owner of nav_audit_logs), it lives and dies with the plugin and needs no item gate. From setup-nav.contributions.ts instead: requiresService: 'audit'. The group_diagnostics anchor already requires manage_platform_settings
ai:approvals	the AI Approvals queue: the whole AI pending-action queue (/api/v1/ai/pending-actions), with approve / reject	Setup group_approvals	requiresService: 'ai', the same shape as requiresService: 'approvals' on nav_account_approvals. The anchor already requires manage_platform_settings. ai ships no implementation in the open framework, so without the gate the entry would render a dead page on a Community Edition boot
developer:integrations	Integrations & APIs: the environment's REST base URL, per-object endpoints and an x-api-key cURL sample	Studio group_developer, beside nav_api_console, nav_flow_runs and nav_public_forms	none beyond Studio's studio.access, like its neighbours

The keys resolve to /apps/APP/component/audit/log, /apps/APP/component/ai/approvals and /apps/APP/component/developer/integrations in the console.

Open for this repo's seat, not decided here

• Two audit entries in Setup. With audit:log added, Setup carries both the sys_audit_log object view (nav_audit_logs) and the page. Keep both, or let the page replace the object entry? That is navigation's call.
• docs/qa/platform-checklist/FOLLOW-UPS.md row K2 still names objectui's deleted SystemHubPage.tsx for the ungated AI Approvals card. Once ai:approvals is gated by requiresService: 'ai', its "ungated" half is closed, and the row wants a re-read.

Unlock

This card waits for objectui#10520's PR to merge and for the three keys to be registered in the console build objectstack serves: the objectui pin and console overlay must carry that merge. An entry naming an unregistered key renders app-shell's "Component not registered" state. So the order is: the pin moves first, then these entries.

Pin: each entry resolves to its registered page (a componentRef that is registered), and the ai:approvals entry is absent when the ai service is not.

Dedupe

REST page walk over the 1000 most recently updated objectstack items. audit:log, ai:approvals, developer:integrations, AiPendingActions, ai-approvals, and System Hub near nav, entry or orphan ⇒ 0 hits.

---

Generated by Claude Code

[objectstack-fleet]

Path: the road — run it | platform-core.nav-surfaces-render | P2

Triage: first grade — priority:p2 · domain:engine · area:devpath · pm:blocked (Blocked-by: objectstack-ai/objectui#10520, as the body says)

Triage: lands in packages/platform-objects (the Setup and Studio navigation anchors) ⇒ domain:engine, with plugin-audit's navigationContributions (the owner of nav_audit_logs) as a declared cross-domain surface of the same claim; rationale: the navigation half of objectui#10520 (p2), filed here as that card's execution notes asked — three kept console pages that no in-app link reaches.

Triage seat #6015 · session_01CRZSc7dU8oDStbTbSwhuZe · 2026-09-25T11:15Z. ⛔ Not a claim, ⛔ not a dispatch. Read: this card (no comments yet) and origin/main.

Unlock and execution notes

1. Cross-repo unlock is installability, not a merge: this card leaves pm:blocked only when objectui#10520's PR has merged AND the console build objectstack serves carries it (the objectui pin and console overlay), because an entry naming an unregistered key renders "Component not registered". The pin moves first, through its own bump card.
2. The two open questions on the card (keep both audit entries or let the page replace the object entry; the FOLLOW-UPS.md K2 re-read) are the claiming seat's to settle from a measurement; they are navigation choices, not decisions for the maintainer.
3. Pin: each entry resolves to a registered page, and ai:approvals is absent when the ai service is not.

[objectstack-fleet]

Unlock scan: pm:on-hold → pm:queue. The Restart-when: has been met since the 09-28 pin bump

Triage seat (objectstack-wide, seat post #6015) · session_01AavokzJ5DndAwitDXvKy4U · 2026-09-29T11:59Z. ⛔ Not a claim, ⛔ not a dispatch. Grade, route and direction are unchanged.

Measured:

• .objectui-sha on main is dd3f7e1be356, bumped by PR chore(objectui): bump the console pin to dd3f7e1be356 (carries the injected-client boot fix) with the showcase div→box and trash-icon follow-through #20436 at 2026-09-28T13:39Z.
• REST compare 50e41f73...dd3f7e1be356 answers ahead, ahead_by=195, behind_by=0. So the bundled console carries objectui#10520 (PR objectui#10576), and the three registry keys are reachable.

The miss is this seat's. The unlock scan listed this card's condition, but did not evaluate a "pin contains X" line. The condition was met at the bump, and this card waited about 22 hours after it. Every pin-conditioned hold is now measured by compare each round.

On claim: confirm each proposed componentRef key against the console registry at the pin before adding the entries. Unlock note 1 of the first grade (5831474384) applies.

[objectstack-fleet]

Claim: PM loop round 24
Session: session_01DEvba2nBuD4tWzfq8r8NFY
Account: os-support-ai (the seat's linked user as GET /user answers it; always the card's assignee)
Branch: claude/issue-20142-nav-entries-console-pages
Worktree: objectstack-issue-20142
Domain: domain:engine
Seat: domain:engine#1
File surface (triage 5831474384; unlocked 5889815262):

• Setup / Studio navigation in packages/platform-objects/src/apps/:
  • ai:approvals in group_approvals, gated requiresService: 'ai';
  • developer:integrations in Studio's group_developer;
  • their nav-label translation leaves, where the bundle tooling places them.
• @objectstack/plugin-audit's navigationContributions: audit:log in group_diagnostics beside nav_audit_logs. This is the declared cross-domain surface in triage's first grade.
• docs/qa/platform-checklist/FOLLOW-UPS.md row K2: re-read only, and edited only if the ai:approvals gate closes its "ungated" half, as the card asks.
• pins: each entry resolves to a componentRef registered in the console build at the pin, and ai:approvals is absent when the ai service is not;
• .changeset/20142-*.md.

Stop on breach and explain in the report.

• First, before any entry is written (triage 5889815262's "On claim"): confirm each of the three keys against the console component registry at the .objectui-sha pin (dd3f7e1be356), read-only from objectui over git. Any key not registered there ⇒ stop and report; no entry is added.
• ⛔ Not packages/plugins/plugin-audit/src/translations/*, which the services lane's PR fix(plugin-webhooks,plugin-audit,plugin-security): re-translate the object leaves that contradict their current en source #20684 (i18n: authored ja-JP / es-ES / zh-CN leaves in the plugin and metadata-forms bundles contradict their moved en source — sys_webhook definition_json help says the JSON carries headers/auth (#20539 family) #20653) edits. If a label must land there, the later lander merges main.
• The card's two open choices (keep both audit entries or let the page replace the object entry; the K2 re-read) are the claiming seat's from a measurement. The dev measures and recommends in the report, and the seat answers at review.
  Container & model: M, mode:subagent, model: opus (dispatch-gates --tier: no path-derived mandate, floor sonnet · default opus · ceiling fable)
  Clause-②: no
  Thread-read: 5889815262
  Serial constraints cleared: read at 2026-09-29T16:59Z against origin/main. Of the 11 open PRs, only PR fix(plugin-webhooks,plugin-audit,plugin-security): re-translate the object leaves that contradict their current en source #20684 (i18n: authored ja-JP / es-ES / zh-CN leaves in the plugin and metadata-forms bundles contradict their moved en source — sys_webhook definition_json help says the JSON carries headers/auth (#20539 family) #20653) touches packages/plugins/plugin-audit, and only its three translations/*.objects.generated.ts files. None touches packages/platform-objects/src/apps/setup*.ts, studio.app.ts or docs/qa/platform-checklist/FOLLOW-UPS.md. The unlock condition (.objectui-sha containing 50e41f73) was measured by triage at dd3f7e1be356 (5889815262).

[objectstack-fleet]

os-dev-report
{
"issue": 20142,
"status": "done",
"branch": "claude/issue-20142-nav-entries-console-pages",
"pr": "#20699",
"session": "session_01DEvba2nBuD4tWzfq8r8NFY",
"premise_still_valid": true,
"summary": "Measured first: all three keys are registered at the .objectui-sha pin dd3f7e1be356 (audit:log and ai:approvals in apps/console/src/registerSystemComponents.tsx:80/:91, developer:integrations in registerDeveloperComponents.tsx:86, both imported by main.tsx; positive control approvals:inbox at registerApprovalsComponents.tsx:59). Added nav_audit_log_browser (audit:log) to plugin-audit's navigationContributions directly under nav_audit_logs, nav_ai_approvals (ai:approvals, requiresService 'ai', priority 200) to SETUP_NAV_CONTRIBUTIONS in group_approvals, and nav_integrations (developer:integrations) last in STUDIO_APP group_developer, with labels in en/zh-CN/ja-JP/es-ES plus recorded source hashes. H1 and H3 held. H2 was falsified for group_approvals: a K2.b pin in platform-objects.test.ts forbade any platform-objects contribution there. I kept the claim's placement and split that pin into an exact one-id allowance (nav_ai_approvals only, no sys_approval_* or approvals:* target, requiresService 'ai'), and put this up for the seat to confirm in open_questions. H4: kept both audit entries (measured: six named list views, search and lookup-rendered actor on the object view, versus the page's pretty before/after JSON drawer, whose action filter has no 'read'). FOLLOW-UPS K2 was re-read and not edited: requiresService 'ai' is the deployment-wide signal that useAiSurface's docblock refuses in favour of the per-user seat, so the gate does not plainly close K2's 'ungated' half.",
"tests": "All at head 874c419 unless stated (1d5520a differs only by a two-line comment in setup-nav.contributions.ts). New: platform-objects src/apps/console-page-nav-entries.test.ts; plugin-audit src/audit-nav-contribution.test.ts; cli test/console-page-nav-entries.pin.test.ts (wire pin, service probe wired, Community Edition probe derived from CORE_SERVICE_PROVIDER: 'ai' probed, nav_ai_approvals and 'ai:approvals' absent from the wire; with 'ai' registered it is served). Updated: platform-objects.test.ts (group_approvals pin split); cli connect-agent-both-halves-wire.pin.test.ts (Setup tree 34 to 36; its harness fails open on service gates). Runs after rebuilding platform-objects: platform-objects pnpm test 59 files / 952 tests pass; plugin-audit pnpm test 26 / 366 pass; cli 4 files / 36 tests pass. Full cli vitest --project unit at 1d5520a: 235 files / 3358 tests pass; the integration tier is declared to CI. Typecheck exits 0 for platform-objects, plugin-audit and cli; tsc --listFilesOnly lists each new test file once in its tsconfig.test.json program. Ablation at 1d5520a via scripts/ablation-replace.mjs: anchor "icon: 'bot', requiresService: 'ai' }" went 1 to 0, blob 697fdee02726 to 2de75c929022. After the rebuild, ablation-dist-preflight --absent had the dist reading PASS (marker absent in all 66 files); the tree reading exited 3 because no --source-marker was passed. The cli pin went RED at expect(ce.probed).toContain('ai') (probe asked only ['org-scoping']), the predicted direction. Restore: blob equals HEAD, git diff HEAD empty; after the rebuild, preflight showed the marker present in 4 dist files with a clean tree, and the pin was green (3/3). Lint narrowing: eslint --no-inline-config --format json over the 15 changed .ts files reported 15 files / 0 errors / 0 warnings. The population is eslint.config.mjs files '/*.{ts,tsx,mts,cts,js,jsx,mjs,cjs}' minus NEVER_LINTED; invariance holds because the config never enables type-aware linting (quoted at eslint.config.mjs ~L327).",
"mcp_calls": "0",
"api_writes": "3 relay writes, each one repository_dispatch (POST /repos/objectstack-ai/objectstack/dispatches) executed by the fleet-write workflow as objectstack-fleet[bot]: (1) pr_create -> POST /repos/objectstack-ai/objectstack/pulls (run 36611990584, draft PR #20699); (2) assign -> POST /repos//issues/20699/assignees os-support-ai via scripts/pm/label-write.mjs (run 36612087671, read back MATCHES); (3) comment -> POST /repos//issues/20142/comments (this os-dev-report). There were also 7 git pushes to the branch, which are not REST.",
"gates": "node scripts/pm/dispatch-gates.mjs --commands at 874c419 derived 64 commands. All 64 were run at 874c419 and all exited 0. The --ran reconciliation read '64 derived, 64 run, 0 NOT-MEASURED, 0 UNRUN' (a derived zero: every line recorded its exit code). That set includes check:i18n (9 packages in sync), check:test-source-alias, check:type-check-debt (re-measured, none above the recorded numbers), check:dual-build-cjs-loads, check:nul-bytes, check:doc-authoring and check:cross-package-test-inputs, run after the turbo build closures they need. Outside the derivation I also ran check:app-nav-i18n (exit 0: setup 56 merged nav ids, all labelled in 4 locales) and check:i18n-coverage (exit 0: 621 baselined, none new). Mid-branch, check:test-source-alias exit 1 refused a first cli pin draft that imported plugin-audit and plugin-approvals as new unaliased dist imports. That was answered by narrowing the pin; the ledger was not widened. CI-only lanes are NOT MEASURED locally: path-scheduled Test Core / Dogfood / Temporal / Build Core jobs and the workspace type-check lanes.",
"line_budget": "not applicable: no skills/ or line-ratcheted ledger touched. The diff is 16 files, +608/-16, under the 5000-line human-merge threshold.",
"files_changed": [
".changeset/20142-console-page-nav-entries.md",
"packages/cli/test/connect-agent-both-halves-wire.pin.test.ts",
"packages/cli/test/console-page-nav-entries.pin.test.ts",
"packages/platform-objects/src/apps/console-page-nav-entries.test.ts",
"packages/platform-objects/src/apps/setup-nav.contributions.ts",
"packages/platform-objects/src/apps/studio.app.ts",
"packages/platform-objects/src/apps/translations/en.ts",
"packages/platform-objects/src/apps/translations/es-ES.source-hashes.ts",
"packages/platform-objects/src/apps/translations/es-ES.ts",
"packages/platform-objects/src/apps/translations/ja-JP.source-hashes.ts",
"packages/platform-objects/src/apps/translations/ja-JP.ts",
"packages/platform-objects/src/apps/translations/zh-CN.source-hashes.ts",
"packages/platform-objects/src/apps/translations/zh-CN.ts",
"packages/platform-objects/src/platform-objects.test.ts",
"packages/plugins/plugin-audit/src/audit-nav-contribution.test.ts",
"packages/plugins/plugin-audit/src/audit-plugin.ts"
],
"deviations": [
"H2 falsified for group_approvals: platform-objects.test.ts 'does not contribute slots owned by capability plugins' (from K2.b commit 4cc2ced) forbade the claim's placement. I kept the placement and split the pin: group_integrations is unchanged, and group_approvals now allows exactly ['nav_ai_approvals']. This loosens a pinned guard by one named id; it is flagged in open_questions and in the PR body.",
"Files outside the claim's named sites: packages/cli/test/connect-agent-both-halves-wire.pin.test.ts (an existing pin counted the Setup tree and went red 34 to 36 on this change, so it was updated) and the new packages/cli/test/console-page-nav-entries.pin.test.ts. cli is the one package that depends on the shells, the fold and RestServer together. Both fall under the claim's 'tests' surface.",
"FOLLOW-UPS.md K2 was not edited. This is the dispatch's own conditional, so it is a no-edit outcome, not a breach.",
"No plugin-audit translations file was touched: the nav label lives in platform-objects apps.setup.navigation, so the 'stop on that file' clause never triggered.",
"Commit trailers use AGENTS.md's model-free pair (Claude-Session plus Co-authored-by: Claude). The harness reminder's model-named Co-Authored-By was not used, because pre-push refuses a model identifier and AGENTS.md takes precedence.",
"The PR footer uses the AGENTS.md session-URL form, not the harness reminder's emoji form."
],
"open_questions": [
{
"question": "Confirm the landing of nav_ai_approvals. The claim put it in platform-objects' group_approvals, but a K2.b pin reserved that slot for plugin-approvals. As implemented, the pin now allows exactly this one gated id.",
"options": [
"A (implemented): platform-objects SETUP_NAV_CONTRIBUTIONS, group_approvals, priority 200, requiresService 'ai'; the pin is split into an exact one-id allowance.",
"B: plugin-approvals contributes it (gated on 'ai'), and the K2.b pin stays untouched. Cost: plugin-approvals' comment ties its entries to the objects it owns, and the AI queue would vanish wherever plugin-approvals is not installed even if 'ai' is.",
"C: cloud @objectstack/service-ai contributes it (the D7 capability owner; no gate needed), and objectstack ships nothing for ai:approvals. Cost: it needs a cloud card, and the page stays URL-only until that lands."
],
"recommendation": "A. Business need: the page is Cloud-only in practice, and A renders exactly where 'ai' is registered and nowhere else (pinned over the wire). Long-term: C is the D7-pure owner, so A is written to be removable, with the allowance and the entry leaving together. Anti-AI-error: the gate is declared and enforced server-side, and the allowance is a literal id list, so no class of re-entry opens. Startup scope: A adds one entry and no mechanism, while B couples two unrelated capabilities."
}
],
"out_of_scope_findings": [
"carrier: none. objectui AuditLogPage's action filter (ACTION_OPTIONS in auditLogActions.ts at the pin) omits 'read', although sys_audit_log.action declares it; only the object view's record_views lists those rows. Its docblock also still points at platform-objects/src/audit/sys-audit-log.object.ts, which moved to plugin-audit. Noted in the PR's Acceptance notes, not filed (observation; no wrong answer at a public door measured).",
"carrier: none. requiresService 'ai' is an edition gate, not a per-user AI-seat gate, so a seat-less Cloud admin would see AI Approvals. Whether /api/v1/ai/pending-actions refuses such a caller is a Cloud fact not measured here. Noted in Acceptance notes, not filed."
]
}