Add CP1 Discovery agents in both patterns
All checks were successful
check agents / check (push) Successful in 10s

ALZ-F01 Discovery as a sub-agent orchestrator (sub-agents/) and as eight
individual declarative agents (individual-agents/), with their KAB workflow
exports. Shared check, render and import scripts, the alz-discovery-sample
MCP server, the crucible-kab-dev deploy profile, deployment docs, platform
issue reports and the source material. Agent steps time out at 20 minutes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This commit is contained in:
2026-10-29 18:25:57 +00:00
commit 416c66ced4
331 changed files with 33561 additions and 0 deletions

View File

@@ -0,0 +1,23 @@
# cp1-discovery-critic-agent
CP1 - Discovery Critic Agent (ALZ-DSC-08): a declarative KAB agent, one step of the CP1 Discovery workflow. Read first:
@.agents/CONTEXT.md
## Rules
- Declarative only: no `app/`, no functions, no hooks. The repository's shared `scripts/check_agents.py` (cp4's rules) refuses an `app/`
to any agent that declares no functions, hooks or sub-agents.
- Keep `kubernetes/` placeholders and the pinned runtime in `Dockerfile`.
- After a `schemas/` change: update `README.md`, run `../scripts/build_workflow.py`, and check the steps that
consume this agent's output still map (`from_steps` in `../workflows/cp1-alz-discovery-individual.json`).
- A change to the ALZ-DSC-08 requirement gets an ADR in `../docs/adr/`, linked from `docs/adr/README.md`, and a
row in `../.agents/PLAN.md`.
- People's docs go in `README.md` and `docs/`; agent context goes in `.agents/`.
- Never put a key in any file; never apply to the cluster without explicit approval.
## Check
```sh
python3 ../../../scripts/check_agents.py --runtime-image cruciblecoredevacr.azurecr.io/kab/agent-runtime-adk:0.35.7 .
```