discover-components

Generate a component-map.json by exploring breadcrumb signals such as installers, operators, and dependencies across your checkouts directory. It catalogs discovered platform components with metadata to support architecture documentation and dependency analysis without needing a manifest script.

Run component discovery against your checkouts directory to produce a component-map.json output. This structured file catalogs discovered platform components and their metadata, making it suitable for downstream architecture documentation and dependency analysis workflows.

Yes, component discovery works for platforms lacking a centralized manifest by relying on breadcrumb signals. It distinguishes shipped platform components from tools or helpers by analyzing installers, operators, dependencies, and build artifacts across the checkouts directory.

A component-map.json catalogs discovered platform components with their metadata for downstream analysis. It provides a structured representation of component ownership and relationships inferred from breadcrumb signals, supporting architecture documentation and diagram generation.

Component discovery is limited when breadcrumb signals like installers, operators, dependencies, and build artifacts are absent or inconsistent across the checkouts directory. Without these traces, inferring component ownership and relationships for the component-map.json becomes unreliable.