Files
ai-workflow-skill/docs/tests/council-review-skill/council-report-rejects-invalid-show-through-bundled-cli.md
T

3.5 KiB

Case: council-report-rejects-invalid-show-through-bundled-cli

Test Type

This is a forward-test and an invalid-input report-filter validation.

The goal is to verify that a leader using the packaged council-review skill reaches the stable invalid_input error contract when it asks council report for an unsupported bucket list.

Purpose

Validate that all of the following can be true at the same time:

  • the leader can drive a real council run through start -> wait -> tally
  • three reviewer agents can complete their tasks through the packaged inbox skill
  • the leader can attempt council report --show consensus,invalid
  • the skill surfaces the stable invalid_input error instead of silently dropping the bad bucket

Preconditions

  • council-review skill path exists: COUNCIL_SKILL_PATH=skills/council-review
  • inbox skill path exists: INBOX_SKILL_PATH=skills/inbox
  • bundled CLI executables exist at COUNCIL_SKILL_PATH/assets/orch and INBOX_SKILL_PATH/assets/inbox
  • use an empty temporary directory TMPDIR
  • initialize TMPDIR/coord.db before launching role agents through INBOX_SKILL_PATH/assets/inbox --db TMPDIR/coord.db --json init

Agent Topology

  • leader
  • architecture-reviewer
  • implementation-reviewer
  • risk-reviewer

Inputs

Leader Prompt

Use $council-review at COUNCIL_SKILL_PATH to act as leader on the already initialized SQLite DB TMPDIR/coord.db. Only coordinate through the bundled orch CLI from the skill. Workflow: 1) start council run council_skill_006 with a short architecture review prompt, 2) wait until all three reviewers complete, 3) tally with normal similarity, 4) attempt council report with --show consensus,invalid, 5) stop after reporting RUN_ID, exit code, and the error payload you observed. Do not use ordinary chat to coordinate with the reviewers.

Reviewer Prompts

Execution Parameters

  • use the shared execution contract from README.md
  • use the shared timeout defaults from README.md
  • do not override the default cleanup policy

Execution Steps

  1. Initialize TMPDIR/coord.db once through the bundled inbox CLI before launching agents
  2. Inject skills/council-review/ into leader
  3. Inject skills/inbox/ into the three reviewer agents
  4. Point all agents at the same database path TMPDIR/coord.db
  5. Launch leader, architecture-reviewer, implementation-reviewer, and risk-reviewer in parallel
  6. Wait for all agents to finish
  7. Independently run the validation commands from the main thread

Validation Commands

COUNCIL_SKILL_PATH/assets/orch --db TMPDIR/coord.db --json council report --run council_skill_006 --show consensus,invalid

Expected Outcomes

  • the leader successfully starts council_skill_006
  • reviewer completion and tally both succeed before the invalid report attempt
  • the report command exits with the stable invalid-input contract
  • the error message names the accepted bucket values

Assertions

  • command exit code is 30
  • error code is invalid_input
  • the error message mentions consensus
  • the error message mentions majority
  • the error message mentions minority
  • the error message mentions all

Cleanup

  • use the default cleanup policy from README.md
  • if the run fails, retain TMPDIR and coord.db for replay and manual inspection