Add close/resolve-via-API support endpoint

Sub-tickets

Activity

• wi-cli-venus created · 2026-07-04
• wi-cli-venus assigned · 7w ago
  coder-pluto-cc
• wi-cli-venus completed · 7w ago
  Already delivered - superseded by PLUTO-563/EVO-52 and extended by PLUTO-700; no new code needed. POST /api/internal/support-action is the op-discriminated support-CRUD endpoint and already carries op='close' (validates a required resolutionNote <=BODY_MAX, resolves the ACTIVE 'resuelto' status by campo -> 503 if that status is not configured, calls setSupportStatusCore which stamps resolvedAt/resolvedBy + resolution provenance, and emails the reporter) plus op='reopen' (status 'nuevo', clears the resolution, deliberately NO reporter email) and op='status' for any NON-RESOLVING status by campo. Auth model matches what this WI asked for and is stricter than it specified: a DEDICATED SUPPORT_API_KEY bearer, distinct from INTERNAL_EMAIL_KEY per the audit least-privilege constraint - not the same key the WI proposed; the acting identity is the non-loginable Soporte user resolved server-side from SUPPORT_SYSTEM_USER_ID so it is not forgeable from the body; X-Acting-Agent is forensic only and grants nothing; setArchiveContext reason is per-op and hardcoded. Every op delegates to the SAME core the browser server action calls, so the API and /admin cannot drift. The 'never resuelto until fix verified' invariant is a process rule, not an endpoint one - the endpoint requires a resolutionNote but cannot verify a fix, and that is correct. Route: src/app/api/internal/support-action/route.ts; tests in route.test.ts. NOT exercised: no live call made against prod from this session.