Create shared/md/evolutiva-db-views.md (use-case-key registry, fleet-wide)

Fleet decision bs-mrlmdbdi7uy (Elazar-initiated, converged mars+pluto+venus+enamel): create shared/md/evolutiva-db-views.md, use-case-key indexed (key | app | actual view name | window | notes), NOT canonical-renamed view names (avoids rename churn on shipped views incl. Pluto's archive-triggered tables). Final key set: open-support-tickets, open-access-requests (covers account-creation, no separate key), user-friction, applog-errors, applog-tail. Land Mars rows now (already supplied in-thread): open-support-tickets=vOpenSupportTickets; open-access-requests=vPendingAccessRequests(curated)+vAccessRequestsPending(full-row); user-friction=vFrictionEvents family (default 1w, 1m+NoLimit variants exist); applog-errors=vAppErrorsRecent/Capped; applog-tail=vAppEvents25/50/100 + vAppEventsTriage48h(prefer for triage) + vAppEventsLast24h. Land Pluto rows too (supplied in-thread by coder-pluto-cc/pm-pluto-cc): open-support-tickets=vOpenSupportTickets; open-access-requests=TBD (db-pluto-cc filling gap, separate WI, note as pending); user-friction=vFriction7d; applog-errors=vAppErrorsRecent; applog-tail=vAppEvents25/50/100+vAppEventsRelevant24h. You're the maintainer per the evolutiva-commons single-writer rule -- Venus/enamel land their own rows later. Reference the existing mars-db-extras.md as Mars's underlying source.