feat(examples): add app-showcase kitchen-sink reference workspace

[os-zhuang]

Summary

Adds @objectstack/example-showcase — a kitchen-sink reference workspace designed to show off the whole platform at once, built for three audiences: demonstration, debugging, and coverage-driven verification.

It deliberately splits into two tracks to resolve the demo-vs-verify tension:

• a realistic backbone (Account → Project → Task, Team, Category) with seeded data so every view renders something real;
• synthetic gallery/specimen objects whose only job is to exhaust protocol variants;

…tied together by a coverage manifest (src/coverage.ts) that the test suite checks against the protocol's own Zod enums.

What it covers

Data layer

• All 49 field types (src/objects/field-zoo.object.ts)
• Every relationship kind: lookup, master_detail, self-referencing tree (Category.parent), and many-to-many via the showcase_project_membership junction
• Formulas, validations, and a status state machine

View layer

• All 8 list-view types on a single object (grid, kanban, gallery, calendar, timeline, gantt, map, chart)
• All 5 form-view types (simple, tabbed, wizard, split, drawer)
• All 38 chart types in one dashboard
• All 4 report types (tabular, summary, matrix, joined)
• The action type × location matrix and a component-gallery page

Capability chains

• Security: roles + permission set with object CRUD + FLS + RLS + sharing rules + policy
• Automation: record-triggered flow → screen-flow wizard → multi-step approval → webhook → scheduled job → email
• AI: agent + tool + skill
• i18n (en + zh-CN), light/dark themes, datasource, and an external portal

Verification ("confirm")

test/coverage.test.ts introspects the spec's own enums (FieldType, ChartType, ReportType, ActionType, ACTION_LOCATIONS) and asserts every member appears at least once across the registered metadata. Because the expected sets come from the spec — not a hand-maintained list — the test fails automatically when the platform gains a new variant that the showcase hasn't demonstrated, keeping it a living conformance fixture rather than a static snapshot. defineStack also runs full schema + cross-reference validation on import.

pnpm verify   # tsc --noEmit + vitest → green (8/8 tests pass)

Notes for reviewers

• The example uses the current named-type import convention (@objectstack/spec/ui, /data, etc.) and define*/*.create builders. (Aside: the existing examples/app-crm still uses the older root-namespace style — UI.Report, Automation.ApprovalProcess — which no longer typechecks against the current spec, and email templates there are missing the now-required isSystem. Happy to follow up on app-crm in a separate PR if useful.)
• examples/README.md updated with a Showcase entry.

🤖 Generated with Claude Code

https://claude.ai/code/session_01CsmomJsLjCknpDjc1XjUcY

---

Generated by Claude Code

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
spec	Ready	Preview, Comment	May 31, 2026 5:43am