AzureScout v3.0.0

Version 3 replaces the retired per-collector PowerShell source tree with the declarative catalog under manifests/collectors. Production discovery, processing, and reporting execute that catalog only; there is no imperative fallback or environment-variable kill switch.

What changed

• 174 collector definitions are discovered directly from manifests/collectors.
• The legacy Modules/Public/InventoryModules tree has been removed.
• Collector execution remains under Set-StrictMode -Version Latest.
• Collector output is pinned by committed golden records: rows in order and worksheet cells for both tag modes.
• The deterministic processing pipeline uses the same manifest catalog in production and tests.

Verification

The release gate consists of the following evidence:

• 174/174 direct declarative collectors execute against optional-property fixtures under StrictMode.
• 174/174 golden row contracts pass.
• 348/348 golden workbook contracts pass (tag and no-tag export for every collector).
• 15 category-level manifest module checks pass independently.
• The catalog validator accepts all 174 definitions without requiring a legacy source file.

Migration notes

Users do not need to change Invoke-AzureScout commands or category names. Contributors add or change a collector definition in manifests/collectors/<Category>/<Name>.psd1, update its fixture and golden record, and run the catalog and golden tests. Do not add a .ps1 collector fallback.

See Category Reference for category names and Testing for the release gates.