refactor(layout): extract composable DetailsColumns primitive
What
Extracts the responsive two-column detail-screen layout out of ObjectDetails into a reusable DetailsColumns primitive with Main / Aside slots, so a page can compose its own cards into the columns rather than injecting content into a specific details component.
ObjectDetails now consumes the primitive; rendered output is unchanged (pure refactor).
Why
First of a 3-PR stack splitting the user & organisation preferences UI (was #9776) for easier review. The Profile tab (PR 3) needs to compose the account details alongside a preferences card in the same responsive layout without a bespoke prop on ObjectDetails โ this primitive is the shared seam.
Stack
- this PR โ
DetailsColumnslayout primitive feat(permission): frontend global-permission checksfeat(preferences): user & organisation preferences UI (IFC-2720)
Test
biome ciclean;tscintroduces no new errors; no behavior change.
๐ค Generated with Claude Code
Summary by cubic
Extracted a reusable DetailsLayout primitive with Main and Aside slots and updated ObjectDetails to use it. Keeps the same responsive two-column UI and lets other pages (e.g., Profile) compose cards, supporting IFC-2720.
- Refactors
- Added
frontend/app/src/shared/components/layout/details-layout.tsxwithDetailsLayout.MainandDetailsLayout.Aside. - Replaced inline layout in
ObjectDetailswithDetailsLayout.
- Added