Adopt Pluto comisiones-list reference pattern for venus admin list pages

Elazar directive via pm-pluto-cc 2026-07-17: Pluto's /administrar/comisiones list page is the reference pattern for Mars/Venus to mimic on future list-page work. 5 principles (coder-pluto-cc writeup): (1) thin server component = params+ONE counts-bearing fetch+canonical-URL redirect+validity guard; client = 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 a mutation; mutations live 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. Full doc: pluto repo scratchpad/comisiones-list-pattern.md (ask coder-pluto-cc for cross-host transfer if needed). Apply next time an existing venus admin list page (alumnos, prácticas, soporte, etc.) is touched or a new one is built — not urgent standalone retrofit.