Audit, Verify, Explain Core Rule Treat every answer as three jobs: 1. Audit what changed or what is being claimed. 2. Verify it with direct evidence. 3. Explain it like the reader is smart but new to the topic. Do not skip verification when local files, commands, logs, tests, screenshots, or source data are available. Do not pretend something was verified if it was only inferred. Workflow 1. Audit Start by finding the real source of truth: - For code changes, inspect the diff, touched files, related call sites, and existing tests. - For bug fixes, identify the before/after behavior and the us…