Follow-up (ADR-0085 PR4): real-backend browser-verify showcase detail pages + framework renderViaSchema comment cleanup

[os-zhuang]

Follow-up to #2181 / PR #2546 (which removed the legacy monolith detail renderer and the renderViaSchema kill-switch). PR #2546 was merged on green CI (type-check, unit 3012, DOM 2904, console production build, and a Playwright console smoke all passed). Two items from the original #2181 checklist could not be completed in the CI/agent environment and are tracked here.

1. Real-backend browser verification of detail pages (main) — ✅ DONE

Completed 2026-07-16 against framework@929efdf app-showcase + console dev on main (post-#2546). Full evidence in the comment below.

The console smoke in CI runs against a mocked build with no @objectstack backend, so the four representative detail-page shapes were never exercised against real data after the legacy branch was deleted. Now that schema-driven is the only path, confirm each renders correctly end-to-end:

• grouped — object with fieldGroups: groups render as titled cards in declared order; collapsible groups expand/collapse. (verified via showcase_semantic_zoo; groups whose fields are all promoted into the highlights strip correctly collapse away, ungrouped tail auto-splits into primary + "More details")
• ungrouped — object with no groups: falls through to the primary + collapsible "More details" auto-split (not one flat blob). (verified via showcase_contact)
• stageField:false — object that explicitly disables stage detection: no record:path stepper is emitted. (verified via showcase_semantic_zoo_legacy)
• related-heavy — e.g. showcase_account: Related tab / reference rail render, and each record:related_list self-fetches lazily when its tab is shown (no eager fan-out on page open — the removed legacy path used to preload all of them). (verified: Invoices/Projects own tabs + Related tab; exactly 1 child-data request, fired on tab click)

For each: no blank page, no fatal console errors, highlight strip present, audit meta footer at the bottom, and ?tab= survives a refresh (all verified). As a direct check that the kill-switch is gone, append ?renderViaSchema=0 to a detail URL and confirm it has no effect (still the schema page) (verified — structure identical with and without the param).

Repro (per-agent isolated stack, from AGENTS.md)

# backend — showcase, fresh temp DB, seeds admin@objectos.ai / admin123
cd framework && pnpm run setup   # NOT `pnpm setup` (that's pnpm's built-in)
pnpm exec turbo run build --filter=@objectstack/example-showcase...   # oclif CLI needs dist/commands
cd examples/app-showcase
pnpm exec objectstack dev --seed-admin --fresh -p 4010

# console pointed at it (VITE_SERVER_URL must be emptied — .env.development pins :3000)
cd objectui/apps/console
VITE_SERVER_URL= DEV_PROXY_TARGET=http://localhost:4010 pnpm exec vite --port 5190 --strictPort

Then log in at http://localhost:5190 (admin@objectos.ai / admin123), enter the showcase app via the launchpad (route by the app's name), and open a record for each shape above.

2. framework: drop the stale renderViaSchema source comment (minor) — still open

@objectstack/spec no longer types renderViaSchema / the per-object detail.* block (verified in the pinned @objectstack/spec@14.6.0 — types are already clean). Only a source comment remains, noting the field "retires together with the legacy monolith render path." Now that the render path is gone (PR #2546), that comment can be removed in the framework repo.

---

Filed as the deferred remainder of #2181 after PR #2546 merged.

[os-zhuang]

✅ Item 1 (real-backend browser verification) — DONE

Ran the full verification against a real stack: framework@929efdf app-showcase backend (objectstack dev --seed-admin --fresh -p 4010, 42 plugins, seeded demo data) + this repo's console dev server (VITE_SERVER_URL= DEV_PROXY_TARGET=http://localhost:4010, vite :5190), driven headless via Playwright/Chromium on main (post-#2546, commit a56c596). All checks passed, 0 console errors on every page.

Shape	Object / record	Result
grouped	showcase_semantic_zoo "Zoo Alpha"	Highlights strip (name/status/amount) ✓, record:path Draft→Active→Done ✓, groups whose fields were all promoted to highlights correctly collapse away, ungrouped tail splits into primary + collapsible "More details" (notes) ✓, audit meta footer + discussion ✓
ungrouped	showcase_contact "Nora West" (seeded)	Auto-derived highlights (phone/email/account) ✓, auto-detected path New→Working→Qualified→Closed ✓, Details/Related tabs ✓, flat field grid + "Show 1 empty fields" ✓
stageField:false	showcase_semantic_zoo_legacy	No record:path emitted ✓ (status renders as a plain Green badge field), declared highlights (name/amount) ✓
related-heavy	showcase_account "Northwind"	ADR-0085 prominence: Invoices & Projects as own tabs + aggregated Related tab ✓; related lists self-fetch lazily — exactly 1 child-data request fired only when the tab was clicked (the removed legacy path used to eager-fan-out all of them) ✓
authored page (bonus)	showcase_task (task-detail.page)	Authored PageSchema(record) path renders custom Overview/Schedule/Details sections + Log Time action ✓
kill-switch inert	same zoo record ± ?renderViaSchema=0	Page structure byte-for-byte identical (path/More details/Edit/body length 565=565) — the param is dead ✓
?tab= contract (#2257)	account → Projects tab → refresh	URL gains ?tab=related:showcase_project; after reload the Projects tab is still selected ✓

Notes for reproducers: the runbook in the issue body works, with two corrections — (1) run pnpm run setup (plain pnpm setup triggers pnpm's built-in), then turbo run build --filter=@objectstack/example-showcase... so the oclif CLI has its dist/commands; (2) start the console with VITE_SERVER_URL= emptied (.env.development pins it to :3000, which breaks auth fetches when your backend is elsewhere).

Item 2 (framework-side stale renderViaSchema source comment) remains open — framework repo write access wasn't available from this session.

---

Generated by Claude Code

[os-zhuang]

Item 2 pinpointed (from a framework@929efdf checkout) — the remaining cleanup is exactly one comment line:

• packages/spec/src/data/object.zod.ts:973 — the ADR-0085 removal note's last sentence, "renderViaSchema retires together with the legacy monolith render path." The render path is gone (objectui#2546), so this sentence can be dropped (or rephrased to past tense).

Not to be touched: packages/spec/src/data/object.test.ts:1124 also mentions renderViaSchema, but that's the guard test "strips the removed detail block on safeParse" using a retired key as its representative legacy input — the behavior it protects (old metadata doesn't explode) is still valid.

---

Generated by Claude Code