Document and rehearse abuse response and destination opt-out handling #19

Problem

Technical destination limits need a human-operable reporting and incident process for disputed traffic, compromised credentials or an opt-out request.

Proposed change

Define report intake, accountable target verification/review, access to evidence, escalation and response runbooks, using the implemented policy propagation and credential controls.

Acceptance criteria

• A local drill follows an opt-out request through approval, enforcement acknowledgement and verification that active traffic stops.
• A credential-compromise drill identifies revocation and recovery actions and preserves an appropriate incident record.
• An actual accountable reporting contact and access policy are agreed; no external host is contacted during the drill.

Current evidence

unimplemented requirement. Backlog classification is based on source inspection; this issue does not claim a new runtime reproduction.

• internal/dispatcher/transport/api/handlers_destination.go: Current destination policy mutation entry point.
• CONTRIBUTING.md: Existing contribution guidance has no abuse-response runbook.

Dependencies

• #74 — Authenticate destination opt-outs and propagate revocation to active work
• #90 — Enroll executor identities and bind them to both control channels

Validation must use owned local fixtures on supported Linux environments. Record the implementing merge request and relevant test results before closing this issue.

Imported from GitLab issue 18. Originally opened 2026-09-10. Historical GitLab links may require access to the original project.