phase0-consumer-graph

Overview ¶

Command phase0-consumer-graph builds a per-resource consumer-dependency graph across the downstream repos and produces the Phase 0 Agent 0.D baseline (validation/baseline/consumer-graph.json) used by Phase 3 per- resource sequencing in the identifier-naming migration (docs/identifier-naming-migration.md §6, §9).

Two kinds of imports are attributed:

1. Go imports of github.com/meshery/schemas/models/<version>/<resource> are parsed precisely from each .go file's ImportSpec list, yielding per-file, per-resource attribution.
2. TypeScript imports of @meshery/schemas/... are detected by regex. Most TS consumers pull in the bundled `mesheryApi` or `cloudApi` client and therefore transitively consume every resource at once; those files are attributed to the coarse "bundled-client-consumer" bucket rather than to a specific resource, because attributing them to all 22 resources individually would bias the complexity score without adding Phase-3 signal.

The complexity score is documented: score = len(consuming_files) for the single-resource precision bucket, plus a separate `bundled_ts_consumers` count so Phase 3 sequencing can decide whether to factor TS depth in.