Mirror of framework#2615 (P2 — highest-ROI item there), found by the Studio package-create UX dogfood (framework#2609). Reproduced against the pinned console build 7782698.
What happens
"Create app" produces an app with zero nav items. The object the user just built isn't offered anywhere; they must discover Interfaces → Edit → Add nav item → set Label → Link to object. In the dogfood run this manual wiring was the single biggest discontinuity in an otherwise smooth create-package → publish loop.
Expected
The create-app popover gains an "Add existing objects as menu items" option (checked by default when the package has objects). Each generated nav item is pre-labeled with the object's label and linked to its record list — exactly what the manual flow produces today.
Notes
Small surface: the nav editor and object→nav-item binding already exist; this only pre-populates them at app creation.
🤖 Generated with Claude Code
https://claude.ai/code/session_01DHQc5BdGhTzPfazex3vWdt
Mirror of framework#2615 (P2 — highest-ROI item there), found by the Studio package-create UX dogfood (framework#2609). Reproduced against the pinned console build
7782698.What happens
"Create app" produces an app with zero nav items. The object the user just built isn't offered anywhere; they must discover Interfaces → Edit → Add nav item → set Label → Link to object. In the dogfood run this manual wiring was the single biggest discontinuity in an otherwise smooth create-package → publish loop.
Expected
The create-app popover gains an "Add existing objects as menu items" option (checked by default when the package has objects). Each generated nav item is pre-labeled with the object's label and linked to its record list — exactly what the manual flow produces today.
Notes
Small surface: the nav editor and object→nav-item binding already exist; this only pre-populates them at app creation.
🤖 Generated with Claude Code
https://claude.ai/code/session_01DHQc5BdGhTzPfazex3vWdt