Observed by the domain:spec seat (session session_01GDA48PuRFrHyRfdkBz8m21) in the CI build log of PR #14449 (#13723) and reported by that PR's dev as pre-existing and unmoved by the change. Filed unassigned for first-touch grading; no severity claimed.
Measured (CI job Dogfood Regression Gate (2/3), @objectstack/example-showcase:build, head e9c424e7; identical on origin/main per the dev's before/after run of objectstack validate — 33 advisory warnings both trees)
⚠ app "showcase_app" · nav "nav_<x>": navigation exposes object "<x>", but no permission set this stack declares grants read on it — the entry renders, and opening it fails for showcase_preference, showcase_expense_report, showcase_team, showcase_category, showcase_business_unit, showcase_field_zoo, showcase_cascade (each with the prescription: add the object to a permission set's objects with allowRead: true / viewAllRecords, or gate the nav entry with requiredPermissions / visible).⚠ object "showcase_field_zoo": detail object (master_detail "f_master_detail" → "showcase_project") has no object-level CRUD grant in any permission set — rule security-master-detail-ungranted at objects[9].fields.f_master_detail.
Why it is worth a card
The showcase is the reference app; a navigation entry that renders and fails on open is a user-visible defect in the demo, and a permanent advisory on every build hides the next real one. Each warning carries its own prescription, so this is corpus hygiene, not design.
Shape of the work
Read the showcase permission sets and decide per object: grant read (and CRUD for the detail object alongside its master showcase_project) or gate the nav entry; the instrument is the showcase build / objectstack validate warning count dropping by the number of entries fixed. Do not widen into the other advisory classes in the same log.
Refs: #13723 / PR #14449 (observed) · #13699 (census).
Generated by Claude Code
Observed by the
domain:specseat (sessionsession_01GDA48PuRFrHyRfdkBz8m21) in the CI build log of PR #14449 (#13723) and reported by that PR's dev as pre-existing and unmoved by the change. Filed unassigned for first-touch grading; no severity claimed.Measured (CI job
Dogfood Regression Gate (2/3),@objectstack/example-showcase:build, heade9c424e7; identical onorigin/mainper the dev's before/after run ofobjectstack validate— 33 advisory warnings both trees)⚠ app "showcase_app" · nav "nav_<x>": navigation exposes object "<x>", but no permission set this stack declares grants read on it — the entry renders, and opening it failsforshowcase_preference,showcase_expense_report,showcase_team,showcase_category,showcase_business_unit,showcase_field_zoo,showcase_cascade(each with the prescription: add the object to a permission set'sobjectswithallowRead: true/viewAllRecords, or gate the nav entry withrequiredPermissions/visible).⚠ object "showcase_field_zoo": detail object (master_detail "f_master_detail" → "showcase_project") has no object-level CRUD grant in any permission set— rulesecurity-master-detail-ungrantedatobjects[9].fields.f_master_detail.Why it is worth a card
The showcase is the reference app; a navigation entry that renders and fails on open is a user-visible defect in the demo, and a permanent advisory on every build hides the next real one. Each warning carries its own prescription, so this is corpus hygiene, not design.
Shape of the work
Read the showcase permission sets and decide per object: grant read (and CRUD for the detail object alongside its master
showcase_project) or gate the nav entry; the instrument is the showcase build /objectstack validatewarning count dropping by the number of entries fixed. Do not widen into the other advisory classes in the same log.Refs: #13723 / PR #14449 (observed) · #13699 (census).
Generated by Claude Code