Author eval suite for agent `azure-principal-architect`
- Dominant language
- JavaScript
- Stars
- 269
- Forks
- 45
- Avg merge
- 18h 41m
- Merged PRs (30d)
- 11
Description
## Agent
`azure-principal-architect` — source: `.github/agents/azure-principal-architect.agent.md`
## Scope
Author the eval suite at `.github/evals/agents/azure-principal-architect/`:
- [ ] `eval.yaml` — suite config (executor, model, graders)
- [ ] At least 2 positive tasks under `tasks/positive-*.yaml`
- [ ] At least 1 negative task under `tasks/negative-*.yaml`
- [ ] Entry added to `.github/evals/manifest.yaml` at `tier: expanded`
## Procedure
1. `/agent-bench azure-principal-architect` drafts the suite from the live `.agent.md`.
2. `waza run .github/evals/agents/azure-principal-architect/eval.yaml -v` locally.
3. `/agent-improve azure-principal-architect` to iterate on graders.
4. Open PR.
5. Mock CI runs automatically. A maintainer will dispatch a real-model run before merge.
## Acceptance
- [ ] Suite runs cleanly in `mock` executor.
- [ ] At least one positive task passes in a real-model run.
- [ ] All negative tasks produce a refusal or out-of-scope acknowledgement.
- [ ] `manifest.yaml` entry added; PR description includes the real-model run summary.
## Conventions to follow
- Persona lock: refusal graders should accept the agent's own scope language.
- Prompt graders need `continue_session: true` in their grader config.
## Related
- Umbrella: #93
- Harness: #61
Contributor guide
Assessment
This issue has not been assessed yet.