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>
This commit is contained in:
@@ -1,3 +1,104 @@
|
||||
## [0.6.1] - 2026-11-05
|
||||
|
||||
### Fixed
|
||||
|
||||
- The input schema accepts the graph that dependency mapping 0.5.0 sends: edge type `represents` and evidence kind `reconciliation` (ADR 0019). Run `exec_071f83409cec` stopped at this step because the platform refused the input.
|
||||
- The input schema accepts the network step's `internet_exposure` findings, which its output schema already allowed.
|
||||
- `scripts/build_workflow.py` now refuses to build when a step's input schema would refuse a value the earlier step's output schema allows.
|
||||
|
||||
## [0.6.0] - 2026-11-05
|
||||
|
||||
### Changed
|
||||
|
||||
- A live run's dependencies are checked in code (`live_dependencies`, ADR 0019): every recorded dependency must be an edge or a folded dependency. Edges to `external` nodes, `represents` links and CMDB relationships are supported by their own evidence.
|
||||
- Includes 0.5.3: an injection the CMDB step flagged is not a guard hit.
|
||||
|
||||
## [0.5.3] - 2026-11-05
|
||||
|
||||
### Fixed
|
||||
|
||||
- An injection the CMDB step flagged (`cmdb_injections`) is not a guard hit: "guard hit not flagged by executor" is no longer raised for it (run `exec_93742bdd7e29`).
|
||||
|
||||
## [0.5.2] - 2026-11-05
|
||||
|
||||
### Fixed
|
||||
|
||||
- When `source_gaps` doesn't list `cmdb`, a CMDB was read and drift is expected: "drift with no CMDB source" is no longer raised for an uploaded export (run `exec_a0a3c486ec9b`).
|
||||
|
||||
## [0.5.1] - 2026-11-05
|
||||
|
||||
### Changed
|
||||
|
||||
- `cmdb_injections` (from the CMDB step) is added to `injections_found`; drift items citing `upload:` evidence are the CMDB step's own findings (ADR 0018).
|
||||
|
||||
## [0.5.0] - 2026-11-04
|
||||
|
||||
### Changed
|
||||
|
||||
- A live run's coverage is computed in code from the critic's own listing of every resource in scope, with the planner's rules, and given to the model as `live_scope` (ADR 0017). It was measured against servers, workloads, clusters and data stores only, so a resource of any other type was never counted as missing, and the critic passed a run that skipped it.
|
||||
|
||||
## [0.4.4] - 2026-11-04
|
||||
|
||||
### Changed
|
||||
|
||||
- `note` says the network agent also runs on `gpt-5.4`, so the critic shares a model with that one executor (ADR 0008).
|
||||
|
||||
## [0.4.3] - 2026-11-03
|
||||
|
||||
### Fixed
|
||||
|
||||
- `LITELLM_MAX_TOKENS` is 16384: `gpt-5.4` refuses 32000 ("max_tokens is too large"), which failed the critic step of `exec_b929f06cbb0c`.
|
||||
- Live-run checks: a scan dependency missing from the edges, and a project or subscription planned as an asset, each fail the run. Runs on `gpt-5.4`, a different model from the executors (ADR 0008).
|
||||
|
||||
## [0.4.2] - 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.1 failed with "Context variable not found: `provider`".
|
||||
|
||||
## [0.4.1] - 2026-11-03
|
||||
|
||||
### Fixed
|
||||
|
||||
- `mcp:` names the cloud servers by the gateway's display names, "Azure Discovery" and "Google Cloud Discovery". With the server ids, 0.4.0 failed at startup: the gateway offers servers by display name.
|
||||
|
||||
## [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). Live tools: `{provider}_list_servers`, `{provider}_list_workloads`, `{provider}_list_kubernetes_clusters`, `{provider}_list_data_stores`.
|
||||
|
||||
## [0.3.2] - 2026-11-02
|
||||
|
||||
### Changed
|
||||
|
||||
- Accepts a `reason` on each source gap: `not_requested` or `no_connection`.
|
||||
|
||||
## [0.3.1] - 2026-11-02
|
||||
|
||||
### Fixed
|
||||
|
||||
- Accepts the `unclassified` dependency type.
|
||||
|
||||
## [0.3.0] - 2026-11-01
|
||||
|
||||
### Fixed
|
||||
|
||||
- Reports the sources it couldn't vouch for in `not_checked` and in `note`. A pass read as covering them.
|
||||
|
||||
## [0.2.1] - 2026-11-01
|
||||
|
||||
### Fixed
|
||||
|
||||
- The input schema accepts the network agent's `unknown_source` finding, which stopped the run.
|
||||
|
||||
## [0.2.0] - 2026-11-01
|
||||
|
||||
### Fixed
|
||||
|
||||
- Tool-call integrity matches a finding to a call by tool, scope entry and outcome. The call log records no agent, so every finding failed the old check.
|
||||
- `note` states the model shared with the executors.
|
||||
|
||||
## [0.1.0] - 2026-10-29
|
||||
|
||||
### Added
|
||||
|
||||
Reference in New Issue
Block a user