---
name: environment-build-runner
description: build_runner spurious "Access is denied" errors on .dart_tool path are environment noise, not real failures
metadata:
  type: project
---

Running `dart run build_runner build --delete-conflicting-outputs` in this repo emits errors of the form `PathAccessException: Deletion failed, path = '.dart_tool\build_resolvers\<hash>'` and exits with code 1 — but the generation itself completes successfully and writes the `.g.dart` outputs. Verify with `dart analyze lib` afterwards.

**Why:** The project lives under `C:\Users\phili\OneDrive\...`. OneDrive's file-sync engine holds short-lived locks on `.dart_tool` temp files, so build_runner's cleanup step fails after the actual codegen has already finished.

**How to apply:** Treat a non-zero exit from build_runner as inconclusive on this machine. Confirm success via:
1. The build log showing `wrote N outputs` (or earlier `samed`/`output` lines).
2. `dart analyze lib` reporting `No issues found!`.

Flutter SDK is not on PATH here — invoke it via `C:\flutter\bin\flutter.bat` / `C:\flutter\bin\dart.bat` or prepend `$env:Path = "C:\flutter\bin;$env:Path"`.