Re-audit the files or behaviors that were judged insufficient in the previous unit audit.

**Important:** Review the supervisor's verification results and understand:
- Unaudited files or behaviors
- Coverage claims lacking evidence
- Specific feedback on issue quality or scope

**Important:** Refer to the audit report: {report:02-unit-audit.md}

**What to do:**
1. Read the flagged production files and corresponding tests in full
2. Re-check the coverage claims for the flagged behaviors and identify what was previously skipped or weakly evidenced
3. Record findings with concrete evidence, explicit scope coverage, and missing-item reasons where applicable

**Output principles:**
- Preserve all existing results from the previous audit report, and integrate new results into a complete updated version
- Add newly audited files and behaviors to the audit results
- If unaudited items remain, state the reason explicitly

**Strictly prohibited:**
- Modifying tests or production code
- Claiming a behavior is covered without citing the actual test evidence
- Skipping a flagged file or behavior because it "looks fine"
