Summary

• add an openapi-generator-cli generated-source detector based on literal -o / --output paths
• restrict detection to explicit JS/TS OpenAPI generators
• keep the detector shallow by classifying only immediate child source files under the declared output directory
• watch declared output paths even when they do not exist yet so later-created files are reclassified on refresh

Why

• PR JS-1597 support GraphQL near-operation-file outputs #7133 added the GraphQL foundation for generated-source metadata; this stacked PR extends the same approach to OpenAPI outputs
• the initial OpenAPI shape needed the same conservative path-watching behavior as GraphQL to avoid missing outputs created after the first scan
• current Peachee evidence supports top-level generated files under dedicated API output directories, not recursive nested source discovery

Impact

• committed JS/TS OpenAPI client outputs can now be recognized as generated sources from package script metadata
• non-JS generators remain out of scope
• nested directories without evidence remain out of scope for now

Validation

• npx tsx --tsconfig packages/tsconfig.test.json --test packages/analysis/tests/jsts/project-metadata/generated-sources.test.ts
• npm run bbf
• git diff --check