Files
cp1-agents/individual-agents/ALZ-F01: Discovery Workflow Agent/cp1-dependency-mapping-agent/RELEASE_NOTES.md
Jonathan Boniface 9e503885cc ALZ-F01 Discovery: package step, value scorecard, application grouping, cases
- New cp1-discovery-package-agent (ADR 0020): one package per reviewed run, every part
  hashed (sha256 over canonical JSON), with a manifest and a value scorecard.
- Applications grouped CMDB -> tag -> resource group with a judged model fallback (ADR 0021):
  CMDB 0.7.0 carries ownership, dependency mapping 0.6.0 groups, report 0.9.0 shows them.
- Critic 0.6.1 accepts the producers' enums; build_workflow.py refuses a consumer enum
  narrower than its producer's.
- Code hooks, sub-agents and tests for the inventory, CMDB, dependency, planner and critic
  agents; the report and Well-Architected review agents; ADRs 0012-0021.
- Workflow cases with value bars and run limits; run evaluation and usage collection scripts;
  the run context template and the field-by-field review for ADR 0016.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-05 22:13:25 +00:00

69 lines
2.8 KiB
Markdown

## [0.6.0] - 2026-11-05
### Added
- `applications`, `asset_owners`, `ungrouped_assets` and `applications_note` (ADR 0021, `app/applications.py`): records grouped by CMDB business service, then application tag (a tag every CMDB-grouped member shares joins tag-only records to that application, for review), then resource group or project (for review), then the `propose_application_groups` sub-agent for what's left, judged in code and always for review. Owners from the matched CI, else an owner tag.
- `pre_process` is now async, to call the sub-agent.
## [0.5.0] - 2026-11-05
### Changed
- A live run's graph is built in code from the scan's recorded dependencies (new input `findings`) and the CMDB step's CIs and relationships (ADR 0019): one graph of `resource`, `external` and `ci` nodes, parent-to-child edges, `represents` links from CIs to their resources.
- Nothing recorded is dropped and nothing is invented: targets outside the scope are `external` nodes, a resource's own components are `folded_dependencies`.
- New outputs: `folded_dependencies`, `dangling`, `graph_comparison` (confirmed, cmdb_only, discovered_only, not_comparable), `note`. The sample estate is unchanged.
## [0.4.2] - 2026-11-03
### Fixed
- A live run keeps every dependency the scan found: a target outside the scope (a network, subnetwork or disk) stays as its resource name, so the map is no longer empty and assets aren't reported as orphans.
## [0.4.1] - 2026-11-03
### Fixed
- Prompt placeholders are written `<provider>`, not `{provider}`: the runtime reads `{name}` in a prompt as a session variable, and 0.4.0 failed with "Context variable not found: `provider`".
## [0.4.0] - 2026-11-03
### Added
- The `provider` input: `sample` (unchanged) or a live cloud, `azure` or `gcp`, read through the existing discovery servers (ADR 0013).
## [0.3.2] - 2026-11-02
### Fixed
- An edge's type is `unclassified` unless evidence shows what it is. Unknown sources and outside ranges were given types nothing supported.
## [0.3.1] - 2026-11-01
### Fixed
- A flow from an asset to an outside range is always an edge. Runs on the same data disagreed.
## [0.3.0] - 2026-11-01
### Fixed
- A resource attached to a network has the type `network_attachment`, not `app_to_app`.
## [0.2.1] - 2026-11-01
### Fixed
- An edge from an unidentified source always needs SME validation, whatever its score. The rule is now part of the validation bands, because the agent ignored it as a separate rule.
## [0.2.0] - 2026-11-01
### Fixed
- A flow from an unidentified source to an in-scope asset becomes an edge that needs SME validation. `10.30.2.40` reached the database and appeared in no edge.
## [0.1.0] - 2026-10-29
### Added
- First release: Builds the evidenced upstream / downstream dependency graph with fan-in, fan-out and retire constraints, from declared, CMDB, configuration, flow and trace evidence.