Chaos Code Risk Scan

Find resilience risks in a repository that a chaos experiment can turn into a pass/fail result, and send them to Harness as a CodeRepository risk scan. Harness then scores them, adds them to the scan report and, for modules linked to a chaos service, recommends experiments.

The work is split so evidence cannot be invented: scripts extract facts and verify snippets; you only map verified facts to rules and write the explanation; the server re-validates everything.

One prompt runs the whole flow. Do not ask the user to choose an org, project, module, service, rule, or to approve a create or a submit. The only stops are a missing origin remote, or a tool error that a single retry does not clear. Report those at the end; do not pause the scan to ask how to proceed.