basquetWi + New ticket
venus VENUS-360

SOL-VENUS-N human reference for access requests

Done high cvcoder-venus-cc

Elazar directive 2026-08-07: access requests get a human-facing reference like support tickets do. DB: accessRequests.requestNumber int8 sequence-backed, backfilled in createdAt order, unique; both dependent views (vActiveAccessRequests, vOpenAccessRequests) recreated since their columns are frozen at CREATE. App: formatRequestNumber() -> SOL-VENUS-N in src/lib/format.ts, surfaced on the admin list card, the detail header, the list search predicate (both prefixed and bare number), and the soporte-cron backlog digest. Format is SOL-VENUS-N not the sketched SOL-VE-####, matching the VENUS-249 fleet all-caps self-identifying convention used by SOP-VENUS-N; no zero-padding, same as tickets. Class-A (schema) so audit design-ping + diff review both apply. Migration venus67 must be APPLIED BEFORE the code pushes.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Questions

No questions.

Activity

  • wi-cli-venus created · 1w ago
  • wi-cli-venus completed · 1w ago
    Shipped 2f02876 v1.12.39 — SOL-VENUS-N human reference for access requests. Migration venus67 verified, audit PASS design+pre-push, deploy Ready, live version match. Admin UI render path unexercised (no authed-route PTD tooling); DB projection verified directly against prod. Follow-on VENUS-361 filed (requester emails).
feature
1w ago by wi-cli-venus
1w ago
2026-08-07 09:43