# Case: `council-unanimous-only-default-report-through-bundled-cli`

## Test Type

This is a `forward-test` and a unanimous-only reporting validation.

The goal is to verify that a leader using the packaged `council-review` skill can run a unanimous-only council and observe the expected default report behavior after tally.

## Purpose

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

- the leader can start a council run with `--only-unanimous`
- three reviewer agents can complete their tasks through the packaged inbox skill
- the leader can tally and report through the bundled council-review skill
- the final report defaults to `consensus` only while preserving the full summary counts

## 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

```text
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_002 with --only-unanimous, 2) wait until all three reviewers complete, 3) tally with normal similarity, 4) report with default settings, 5) stop after reporting RUN_ID and the default show buckets you observed. Do not use ordinary chat to coordinate with the reviewers.
```

### Reviewer Prompts

- Reuse the same reviewer body JSON and inbox-only workflow as in [council-brainstorm-end-to-end-through-bundled-cli.md](./council-brainstorm-end-to-end-through-bundled-cli.md), but target run `council_skill_002`.

## Execution Parameters

- use the shared execution contract from [README.md](./README.md)
- use the shared timeout defaults from [README.md](./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. Resolve `RUN_ID=council_skill_002` from the agent outputs
8. Independently run the validation commands from the main thread

## Validation Commands

```bash
COUNCIL_SKILL_PATH/assets/orch --db TMPDIR/coord.db --json council report --run council_skill_002
COUNCIL_SKILL_PATH/assets/orch --db TMPDIR/coord.db --json status --run council_skill_002
```

## Expected Outcomes

- the unanimous-only run completes successfully
- the report default `show` value is only `consensus`
- the underlying summary still contains `consensus`, `majority`, and `minority` counts
- only the consensus group is returned in `grouped_recommendations`

## Assertions

- `report.data.show == ["consensus"]`
- `report.data.summary.consensus == 1`
- `report.data.summary.majority == 1`
- `report.data.summary.minority == 1`
- `report.data.grouped_recommendations` length is `1`
- the sole returned recommendation has `bucket == "consensus"`

## Cleanup

- use the default cleanup policy from [README.md](./README.md)
- if the run fails, retain `TMPDIR` and `coord.db` for replay and manual inspection