Segment error boundaries drop the client error payload PLUTO-83 added

11 of 12 route-segment error.tsx boundaries render <ErrorCard kind="error" digest={error.digest} reset={reset} /> and never forward error.message/name/stack. ErrorCard (src/components/error-card.tsx:94) forwards whatever it is given into logClientError, and client-log-actions.ts:45 writes those into the first-class appEvents errorName/errorMessage/errorStack columns - so every error caught by a SEGMENT boundary persists a row with all three columns null and digest null, which is exactly the opaque {path, digest:null} shape PLUTO-83 existed to eliminate. Only src/app/error.tsx forwards them; PLUTO-83 fixed the root boundary and the card and missed the segments, so this is drift, not an original omission. Measured on a live alert: appEvents 6e774408-ee52-4ad8-b4ab-398a3f799c72, clientError:error on /practicas/nueva 2026-09-10T20:30:19Z, appVersion 2.23.80, detail={path,digest:null,referrer} and nothing else - the user's actual failure is unrecoverable. Affected: (protected)/ admin, administrar, alumnos, equipo-academico, informes, mi-cursada, mi-cursada/[id], notificaciones, perfil, practicas, practicas/[id]. Scope: forward the three props in all 11, matching src/app/error.tsx exactly; add a guard test walking src/app for error.tsx files that asserts each forwards all three, mutation-checked by reverting one file. Do NOT copy the STALE_ACTION_PATTERN reload block into the segments - that is a separate defect, tracked as the follow-up below. FOLLOW-UP (do not fold in): the stale-Server-Action auto-reload exists only in root error.tsx and global-error.tsx, but a segment boundary catches first, so a stale action thrown inside /practicas or /admin shows the card and never reloads. If a post-fix row on this path carries errorMessage matching /Server Action .* was not found/, that is the confirmed cause of this incident and the reload gap becomes its own WI.