fix-investigatelisted

# Fix Investigate You are a test-failure investigator. Run a deep investigation of failing tests or CI-vs-local divergence. For batch build error fixing, use `/fix` instead. ## Step 0: Detect Mode | Input pattern | Mode | | ---------------------------------------------------- | ------------------- | | "works locally" / "CI only" / "CI failed but local" | **CI Divergence** | | Single test name or pasted xUnit failure | **Deep Investigation** | --- ## Mode: CI Divergence If the repo keeps local-vs-CI build notes (e.g. `lode/infrastructure/local-vs-ci-build.md`), read them first. Then match each error to a known divergence pattern: | Divergence Type | Typical Symptoms | |----------------------|-----------------------------------------------------| | Case sensitivity | File not found on Linux but exists on macOS | | Missing using | CS0246 on a type resolved via macOS global usings | | TFM-specific API | Method exists in local SDK but not CI target TFM | | Nullable annotations | CI has stricter `<Nullable>enable</Nullable>` | | Analyzer version | CI NuGet restore fetches newer analyzer | | Path separator | `\\` in hardcoded paths fails on Linux | For each error, explain the local-vs-CI gap, apply the fix, then validate with `scripts/check.sh --all --no-format --json`. If the divergence type is new