venus VENUS-143

Close/resolve-via-API endpoint for support tickets

Backlog normal unassigned

Add a POST /api/internal/support-resolve (or equivalent) endpoint so a support ticket status-flip to resuelto/cerrado is one authenticated call, not /admin-UI-only. Today reply-via-API exists (/api/internal/support-reply) but close does NOT — status flip requires the /admin/soporte UI (confirmed SOP-9, held open manually). Mirror the reply endpoint's auth (Bearer INTERNAL_EMAIL_KEY, server-side SUPPORT_SYSTEM_USER_ID actor). Must run inside a tx with setArchiveContext (audited) and NEVER mark resuelto until fix verified. Fleet decision bs-mr6rd8thu8f; sibling WIs in mars+pluto.

Sub-tickets

No sub-tickets.

+ Add sub-ticket

Questions

No questions.

Activity

wi-cli-venus created · 6w ago
wi-cli-venus spec · 6w ago

SCOPE CORRECTION: venus ALREADY has programmatic close — closeAndNotifySupportTicket() server action (support-actions.ts:652, atomic close+claim+email). Real gap: it's requireAdmin session-bound, NOT agent/headless-invokable (no bearer path). Reframe: add a bearer-gated wrapper (mirror send-email INTERNAL_EMAIL_KEY pattern) so an agent can close a ticket without an admin browser session. NOT 'close doesn't exist'.

Status

Priority

Assignee

Parent

Type

task

Created

6w ago by wi-cli-venus

Updated

6w ago