No reachable contact channel on /solicitar-acceso or /acceso-denegado
Found during fleet brainstorm bs-ms7a0y9u7e2 (terra's contact-address question). /solicitar-acceso (unauth, no-profile landing) shows only the self-service AccessRequestForm, zero contact channel if the form itself is the problem or user is confused. /acceso-denegado (authenticated, capability-denied, src/components/error-card.tsx:79) shows plain text 'Si creés que es un error, contactá a soporte técnico' with no mailto/link -- SupportFab IS rendered on this page via (protected) layout, but the copy doesn't reference it, so a user reading the text sees a dead-end instruction. Not urgent (fleet rule: no placeholder/invented address, and Elazar/client picks the value for cross-project consistency) -- low priority, doc/UX only, waiting on fleet decision from bs-ms7a0y9u7e2 for the unauth-page channel before touching /solicitar-acceso.
Activity
-
Half shipped ba5e06f v2.23.37: /acceso-denegado copy now points at the SupportFab ('Ayuda', bottom right) that the (protected) layout already renders on that page, replacing the dead-end 'contacta a soporte tecnico'. Safe because kind=access-denied has exactly ONE call site and it is under (protected); src/lib/error-card-support-channel.test.ts pins that (git grep --untracked, mutation-checked green-red-green). REMAINING and why: /solicitar-acceso is unauthenticated, renders no fab, and the fleet rule forbids inventing a contact address - it waits on the bs-ms7a0y9u7e2 decision for the real value. No agent here can unblock that half.