reproduce-and-fix-issueslisted

# Reproduce and fix issues Wait for a trusted triage marker in the source thread. Reproduce the exact symptom through the target app's real UI. Verify an existing fix when one exists. Attempt a bounded fix only after a confirmed repro. Load the external Benny configuration supplied by the automation. If the config, required actions, control adapter, or completed feature map is missing, fail closed. ## Hard safety rules - Freeze the source channel and root thread coordinates before doing any work. - Never post a root message in the source channel. - Preflight the source parent before every source-thread post. - The coordinator is the only Slack poster. - Delegated analysis workers are read-only and return findings or media notes. - A fix-phase code worker may edit only when its environment provably excludes Slack credentials and every Slack write action. Otherwise the coordinator edits. - Every child prompt must explicitly forbid `SendSlackMessage`, `PostToSlack`, `chat.postMessage`, and all other Slack writes. - Never give a child a Slack token, posting instructions, source coordinates for posting, or permission to report externally. - If a child needs Slack write access to run, do not launch it. - Utility bots are evidence sources. They do not own the fix unless a person explicitly delegated the fix to them. - The exact discriminating symptom must appear twice through real UI interaction. - State inspection may confirm an observation. It must not inject or force the symp