context-bootstrap

A hollow report output occurs when the reporting workflow lacks a populated findings cache, installed plugins, and proper framework metadata. You must bootstrap these prerequisites before executing report commands to ensure accurate coverage calculations.

To bootstrap the reporting workflow, run the guided setup to install required plugins via the marketplace, initialize the findings cache, and verify framework metadata presence in plugin.json. This validates prerequisites before executing reports.

Accurate coverage calculations require framework metadata to be present in plugin.json. The bootstrap process validates this metadata alongside the findings cache location and installed plugins before generating any reports.

Yes, you should run the guided bootstrap setup after plugin updates. Post-update environments require prerequisite verification to ensure the findings cache and framework metadata remain intact for accurate reporting workflows.

Use the guided first-collection flow during onboarding for new projects or when a report command detects missing findings, frameworks, or history. It walks you through installation and collection rather than generating a hollow report.

Yes, the bootstrap workflow is applicable when starting new projects across GitHub or inspector workflows. It organizes the reporting workflow by ensuring plugins, the findings cache, and framework metadata are installed before generating reports.