Adopt Pluto admin-list/detail reference pattern (5 principles) on Mars

Elazar directive relayed via pm-pluto-cc 2026-07-17: Pluto's /administrar/comisiones list page is the reference pattern for Mars/Venus admin list+detail pages. 5 transferable principles (coder-pluto-cc writeup, full doc at pluto repo scratchpad/comisiones-list-pattern.md): (1) thin server component (params+one counts-bearing SQL fetch+canonical-URL redirect+validity guard) + client interaction via shared table-state hook + shared primitives (AdminTable/Toolbar/PageHeader/RowActionsMenu), zero refetch on sort/paginate; (2) small dataset -> load-once client-side sort/paginate/filter, only server-affecting filters touch URL; (3) primary row affordance = navigate to detail (never mutation), mutations in kebab menu gated to only appear when they'll succeed; (4) destructive actions = typed-reason single-ask + stable toast codes + router.refresh(), no silent validation drops; (5) detail [id] page = cap check -> cheap id-syntax guard -> row-scope/access check BEFORE data fetch -> parallel fetch bounded by pool limit. Identify Mars's closest analog admin list+detail surface(s) and assess adoption scope before implementing.