## [0.8.1] - 2026-11-02 ### Fixed - A phase's checks count only a sub-agent's own records. `inventory-sources`, tool data the orchestrator fetched, was taken as the inventory, so an analyse phase with no inventory passed, and so did the run. - The critique fails when an analyse output is missing. - A hand-off naming a record the run didn't store goes ahead and says so. With ITSM off, `collect/itsm-records` didn't exist, and every analyse hand-off failed. ## [0.8.0] - 2026-11-02 ### Added - `include_cmdb` and `include_itsm` from the run form, stored as `plan/run-options` and applied by the planner. The report says why each source wasn't used. ## [0.7.2] - 2026-11-02 ### Fixed - `dsc_06_dependency_mapping` types an edge only when evidence shows it, and otherwise `unclassified`. - `dsc_03_inventory` keeps `compliance_scope` and `support_status` from the scan when the CMDB has none. - `dsc_01_planner` names the tool each task type really uses. ## [0.7.1] - 2026-11-01 ### Fixed - `fetch` lists each tool's arguments and rejects a wrong name before calling. With the raw tools withheld, the model guessed `site_id`, and every network call was refused. ## [0.7.0] - 2026-11-01 ### Changed - MCP results no longer pass through the model. `fetch` calls the tools and stores the results in code, and the raw tools are withheld from the model (ADR 0014). ### Fixed - `dsc_07_network`, `dsc_06_dependency_mapping` and `dsc_05_data_classification` have explicit rules for a sole firewall, outside ranges, unknown sources and citing evidence. ## [0.6.1] - 2026-11-01 ### Fixed - The plan checks read MCP results in their `{"success", "data"}` wrapper. They saw no scope entries, and the rate budget was skipped without warning. - Only `scan_target` tasks are held to the scope lock. `classify_data` and `trace_dependencies` tasks may name a connector. ## [0.6.0] - 2026-11-01 ### Added - A `report` phase after critique writes the customer's report as Markdown and HTML, in code, from the workspace (ADR 0013). The approval gate moves to it. ### Fixed - The plan phase's own check now applies network coverage. Only `check_plan` did before. - The analyse skill respects `source_gaps`, and passes the plan to `dsc_05_data_classification`. ## [0.5.1] - 2026-11-01 ### Fixed - `dsc_03_inventory` cites the finding's evidence on a `scan` source. ## [0.5.0] - 2026-11-01 ### Fixed - The prompts declare missing sources and respect them, keep the scan's asset class, report unclassified stores and type network attachments. ## [0.4.3] - 2026-11-01 ### Fixed - `dsc_03_inventory` keeps the `scope_entry_id` of an entry that is in scope but can't be scanned. ## [0.4.2] - 2026-11-01 ### Fixed - `dsc_03_inventory` lists a `scan` source only for an entry with a finding. ## [0.4.1] - 2026-11-01 ### Fixed - `dsc_06_dependency_mapping` replaces the `score_edge` band on an edge from an unidentified source. ## [0.4.0] - 2026-11-01 ### Added - `dsc_07_network` reports an `unknown_source` finding, and `dsc_06_dependency_mapping` keeps that flow as an edge needing SME validation. ### Fixed - `check_plan` no longer refuses a `collect_network` task that names a site, which is what the planner is told to do. It now checks that every site has one. - The planner plans every site `get_scope` returns. - `dsc_07_network` emits a finding for each overlap, `dsc_02_scan_executor` keeps every declared dependency, and `dsc_08_critic` states the shared model. ## [0.3.0] - 2026-11-01 ### Changed - The critic uses `gpt-5.6-sol`: the cluster's gateway doesn't serve `claude-sonnet-5-5` (ADR 0009). ### Fixed - The planner declares an entry with no scan interface as a gap, and sets `assigned_agent` from a fixed mapping. - CMDB reconciliation works out unscanned sites from `facts.site`, because tasks hold no sites. ## [0.2.0] - 2026-10-29 ### Added - Files uploaded at run time (`source_documents`, from a Parse Assessment Files step) and project artifacts (`artifacts`, from an Artifacts step) are imported in the plan phase as write-once workspace records, with provenance kept apart; sub-agents get the records only. ### Fixed - `EXECUTION_STORAGE_ROOT` is set to the shared volume, so the run workspace survives restarts. ## [0.1.0] - 2026-10-29 ### Added - First release: runs one phase of Agentic Landing Zone discovery (plan, collect, analyse or critique) for an engagement, with the eight ALZ-DSC agents as sub-agents, a hash-chained run workspace and a critic verdict enforced in code.