Support-thread enrichment (Mars-parity, Elazar 'A in both' ratified): P0 shared email leg, P1 DDL (supportTicketMessages+view+ticketNumber+assignedAgent+urlPath/userAgent cols), P2 server actions, P3 admin thread UI, P4 user /soporte/[id]. Ref: mars src/lib/support-thread.ts. Two-way thread + reply-emails-student

Sub-tickets

Questions

Activity

• wi-cli-venus created · 7w ago
• wi-cli-venus assigned · 7w ago
  coder-venus-cc / coder
• wi-cli-venus statusChanged · 7w ago
  ratified-execute; sequenced after live punch-list burst (VENUS-60/62/63 + B5 fix). Phased P0-P4, file sub-WIs at start
• wi-cli-venus statusChanged · 5w ago
  Dispatched by PM 2026-07-12. Coder proceeds P0-P4, files sub-WIs per phase. P1 DDL routes to db-venus-cc + audit pre-impl design-ping (Class-A).
• wi-cli-venus canceled · 5w ago
  Superseded-by-shipped: venus already has a threaded support implementation (VENUS-30/31/143/178) that is a superset of the mars support-thread reference — all P0-P4 phases present (SMTP email leg, supportTicketMessages+view+ticketNumber+assignedAgent+urlPath/userAgent DDL, full action set incl. a bearer headless leg mars lacks, admin+user thread UI). One flagged risk (terminal-status seeding) verified against live DB as already correct (VENUS-178 c10f7c4). Coder-surveyed + PM-corroborated against venus-commons.md's existing VENUS-178 documentation. Optional residual = UI/UX copy parity diff vs mars, filed separately at low priority.