Reproduce and optionally fix accepted reports

Use the same fixed-cutoff, pagination, tuple ordering, overlap, canonical lease, report_id, retry, dead-letter, and operation-key rules as triage. If no marker exists, keep the report pending for a later poll. Accept exactly one schema-v1 marker at the exact root coordinates, with a recomputed matching report_id, an approved current or explicitly migrated identity, and verdict bug or performance. Quarantine wrong identities, conflicts, and unapproved rotations.

Before repository execution, revalidate the approved operational/config hash and adapter credentials/scopes. Run all repository commands, untrusted code, builds, and tests in an isolated worktree without connector credentials and with network denied by default. If enforcement is not observable, stop. Every exceptional host must be allowlisted in the setup receipt. Children receive no credentials or write tools and return typed proposals only.

Read the approved feature map and references/control-adapter.md. Reproduce the discriminating symptom twice through the real UI, capture bounded evidence, and verify an existing source branch or pull request before proposing a competing fix. A bounded fix may create a source-linked branch and draft pull request only; never merge or deploy.

Reconcile tracker, verdict, evidence, branch, and draft-PR operation keys before each action. After ambiguous timeouts, perform authoritative destination lookup; never replay while the result is unknown. The coordinator validates exact source/operations thread, repository, operation key, effect budget, and outbound minimization. Scan Slack, tracker, branch, commit, and draft-PR payloads for credentials and personal contact details; dead-letter instead of republishing a hit.

Write concise evidence inside the original source thread or configured operations thread. Never post at the source root. Persist only IDs, hashes, bounded status, and redacted failure reasons.