Add CP1 Discovery agents in both patterns
All checks were successful
check agents / check (push) Successful in 10s
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:
@@ -0,0 +1,18 @@
|
||||
# Eval cases for CP1 - Discovery Planner Agent: the Meridian Retail Group sample estate (needs the MCP server).
|
||||
schema_version: "1.0"
|
||||
agent: "cp1-discovery-planner-agent"
|
||||
defaults:
|
||||
timeout: 330
|
||||
cases:
|
||||
- id: "plans-every-scope-entry"
|
||||
description: "Every Meridian scope entry is planned or a declared gap; the HSM (SE-004) has no read-only metadata interface, so it is a gap."
|
||||
input:
|
||||
json:
|
||||
engagement_id: "ENG-MERIDIAN-001"
|
||||
run_id: "RUN-EVAL-01"
|
||||
checks:
|
||||
- schema: true
|
||||
- field: "coverage_gaps"
|
||||
contains: "SE-004"
|
||||
- field: "tasks"
|
||||
contains: "SE-032"
|
||||
Reference in New Issue
Block a user