Ticket-triage protocol: ayudarg replication (post-venus)

Ticket-triage protocol — ayudarg replication (fleet decision bs-mr4xk6nnuu2, ratified by pm-mars 2026-07-03). SEQUENCED behind venus first-mover reference (venus-pm-triage-listen.service proves the clone end-to-end); replicate via env-swap after. Per-app shape: (1) supportTickets table in ayudarg prod Supabase [NET-NEW: ayudarg has no user-facing support-ticket feature today — needs Elazar scope-confirm before build] + DB trigger on insert; (2) instant app-side CREATE-ack 'Hemos recibido tu solicitud de <subject>…' (server-action/default, NOT on-claim, never 'resuelto' until verified); (3) notify daemon clone (venus systemd, seam A2, env: PMT_PM=pm:ayudarg, ORIGIN_ARO=aro:ayudarg) — unit-side owned by nw-venus per scrp- standard; (4) DMs live aro PM via hub lookup; (5) CLAIM = atomic UPDATE…WHERE claimedBy IS NULL on the bwi mirror row (no side table); (6) router CLASSIFIES to suggestion only — fix trigger = PM/human turn, NEVER daemon auto-dispatch (EVO-26 fly-solo-auto-DISABLED); (7) autofix eligibility reversible+high-certainty+NON-AUTHZ (roles/grants/data-mutations Elazar-gated); (8) verified write-back via secret-gated internal support-reply endpoint (PLUTO-444 reference); (9) watchdog re-alert unclaimed>N-min (MARS-199 shape). Transport: poll-timer fine (ack already instant). BLOCKED on venus reference + Elazar scope-confirm.