basquetWi + New ticket
venus VENUS-252 · child of EVO-52 SOP support-ticket API: full CRUD + private stakeholder comments + notify-list, per app Backlog

SOP support-api: add ticket CRUD (close/status/notify) + private stakeholder comments

Done urgent dvdb-venus-cc

Sub-item of EVO-52. Venus support-api needs: full ticket status transitions (incl. close/resolve) callable by PM/coder via API, a private comment type visible only to Elazar + the ticket's stakeholder agent (never the end user), and a notify-list (agent name + email) that fires notifications on ticket events. No direct DB writes or chrome-mcp driving tickets — API only. Priority 0 (urgent): SOP-VENUS-15 is the live trigger case — solved but stuck un-notified/un-closed because coder-venus-cc has no API path today.

Sub-tickets

No sub-tickets.
+ Add sub-ticket

Questions

No questions.

Activity

  • wi-cli-venus created · 4w ago
    parent=#2024
  • wi-cli-venus statusChanged · 4w ago
    Dispatching db-venus-cc (schema) + coder-venus-cc (API surface), Class-A full-team lane
  • wi-cli-venus assigned · 4w ago
    db-venus-cc
  • wi-cli-venus note · 4w ago
    db-venus-cc: VENUS-143 (S0-S3, ae542c9 2026-07-06) already ships the headless reply/close foundation - service actor row, POST /api/internal/soporte-action, soporte-action-lib.ts, scripts/soporte-action.ts, 16 tests, secrets confirmed live in Vercel prod. Nothing to build for that half. SOP-VENUS-15 closable now via existing route - dispatched coder-venus-cc. VENUS-252 net-new scope narrows to: private-comment-type (Elazar+stakeholder-only visibility) + notify-list mechanism. db-venus-cc proceeding to design-ping audit-venus-ca before implementing (Class-A).
  • wi-cli-venus note · 4w ago
    Elazar/EVO-52 fleet ruling: (1) visibility=hidden-from-reporter-only/any-admin-sees/no-ACL - matches shipped design. (2) notify-list=free-text comma-separated, no FK/enum - shipped design uses single assignedAgent+agentNotifyDirectory (one recipient); flagged to db-venus-cc to reconcile against multi-recipient free-text requirement.
  • wi-cli-venus note · 4w ago
    Process gap found: VENUS-143's headless reply|close bearer route (ae542c9, shipped 2026-07-06) was uncallable the ENTIRE 9 days since ship - SOPORTE_ACTION_SECRET was set in Vercel prod but no agent ever retained a readable copy, so SOP-15 was the first real invocation attempt and it failed. Not an SOP-15-specific gap - any assumption that headless close/reply was live during that window was wrong. Secret regenerated + saved to ltm.md (db-venus-cc), coder-venus-cc redeploying to pick up new value, will confirm live + close SOP-15.
  • wi-cli-venus completed · 4w ago
    SOP support-api CRUD shipped, SHA 8ad6cdc/v0.97.0, live+version-verified, audit diff PASS, Class-A PTD closed (deploy READY, build clean, 0 runtime errors 1h; new surface had 0 prod invocations - not yet exercised). POST /api/internal/support-action reply|note|close|reopen|notify-set + GET read, agent-note filtered from reporter/session reads. Follow-ons NOT started (fleet pause): (1) provision SUPPORT_API_KEY in Vercel prod + drop legacy env fallback, (2) notify-FIRE wiring off notifyList, (3) admin-UI note rendering.
task
4w ago by wi-cli-venus
4w ago
2026-07-15 09:33