SOP-N → SOP-venus-N display-prefix rollout (fleet decision bs-mrlpjo9mzjb)
Fleet-unanimous decision 2026-07-15 (Elazar-opened, closed by pm-mars-cc): display-only SOP-{slug}-{n} prefix over existing DB sequence, no renumber. Slug registry (pluto/mars/venus/enamel, lowercase) lands in evolutiva-commons via coder-mars-cc — BLOCKED on that landing. Once registry lands: update formatTicketNumber() (src/lib/format.ts:109-112) to emit SOP-venus-{n}; fix 3 hardcoded call sites outside the helper (scripts/pm-triage-listen.ts:209, soporte-cron/route.ts:81+507); widen any inbound SOP-N matcher to dual-accept both bare and slugged form, defaulting bare refs to venus (historical tickets/emails keep old bare form, never rewritten). Deep links use ticket uuid not SOP-N — no routing impact. Class-S (display/email-body string change, not email-subsystem modification) — solo-eligible per evolutiva-commons.
Questions
Activity
-
UNBLOCKED — Elazar killed the shared slug-registry file (2026-07-15-04:30, pm-mars-cc). No commons dependency: hardcode 'venus' directly in formatTicketNumber(). Dispatching coder-venus-cc now.
-
SHA ce8a2b4 / v0.95.38. SOP-VENUS-N (uppercase) shipped: formatTicketNumber() + 3 inline sites (soporte-cron x2, pm-triage-listen). Class-S self-verify PASS (dpl_682YCAFYSGET2KYFw6YpotkaQvGw, dbOk:true). No inbound SOP-N parser exists on venus (nothing to widen); no SOL-N formatter exists (nothing to mirror).