Complete product resource
- Define the resource, tenant boundary, actor, lifecycle, visibility, and states before writing views.
- Build index, form, detail, destructive action, and tests as one product surface.
- Use one shell toolbar title and one application-owned page gutter; do not repeat hierarchy across nested components.
- Scope every lookup through the current tenant and model meaningful lifecycle transitions as noun resources.