Platform scripts, MCP servers, deployment and docs for the KAB runs

- Scripts to run workflows from a YAML context or run inputs (kab_run_workflow.py, with
  --input name=@file), store per-project discovery connections, bootstrap agent MCP keys,
  refresh the KAB token, publish reports and build estate snapshots.
- Hyperscaler discovery servers extended in place; cloud-knowledge folded into them.
- deploy/crucible-kab-dev.yaml: the Discovery package agent and the Assessment agents.
- Platform issue write-ups and current-wiring notes under docs/platform-issues/.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-11-05 22:13:25 +00:00
parent c14a94f33b
commit f659564208
71 changed files with 2818 additions and 2821 deletions

View File

@@ -9,6 +9,19 @@
| Status | Open; reported to the platform team for confirmation |
| Found by | Code review while building the CP1 Discovery workflows (`sub-agents/` and `individual-agents/`, ALZ-F01) |
## Update 2026-11-02
Further code reading, still @ `c89aedcb9`, answers two of the questions below:
- **Question 3, run-time ids: yes, already possible.** A run input named `<step_id>_artifact_ids` is mapped onto that
step's `artifact_ids` (`generic_workflow_executor.py:199-210`). An empty selection still fails.
- **Question 4, the `workflow_id` match: one run, chosen arbitrarily.** The query can match several runs' artifacts, but
`_resolve` returns the first document found (`artifacts_activities.py:139-146`). The match also has no tenant or
project filter: see [select-artifacts-tenant-scope](../select-artifacts-tenant-scope/report-2026-11-02.md).
Running or chaining one workflow from another is reported separately, in
[workflow-composition](../workflow-composition/report-2026-11-02.md).
## Summary
You can place an Artifacts step (`select_artifacts`) anywhere in a workflow, including between two agent steps. Within one run, though, it can't select anything an earlier step of that same run produced. The executor registers a run's step outputs as project artifacts only **after every step has finished**. While the run is in progress, its own outputs aren't artifacts yet.