Maurice f2329c9a63 feat(client): let a managed surface attach as an admin tab ...

The nav-entry seam was the wrong shape for what actually attaches here. A
subscription surface is about the install, not about a trip: /admin is already
behind an admin check, already grouped, and already where somebody looks to
change how their instance works. A top-level nav entry put it beside My Trips
for a screen opened once a month by one person.

Two lines in AdminPage rather than an overlay replacing the file: the tab list
gets the extra entries appended per group, and the body renders whichever one is
active. Appended rather than inserted because PageSidebar needs a group's tabs
contiguous.

The route and nav-entry seams stay. They are the right answer for a surface that
genuinely is a page, and both remain empty here.

2026-08-15 18:07:21 +02:00

..

index.test.ts

feat(client): let a managed surface attach as an admin tab

2026-08-15 18:07:21 +02:00

index.tsx

feat(client): let a managed surface attach as an admin tab

2026-08-15 18:07:21 +02:00