# Manual Consultant Checkpoints

Manual consultant checkpoints are advisory Runtime workflow checkpoints. They
let an operator export a structured planning packet, manually copy-paste that
packet to an external reasoning consultant, import the structured response, and
record advisory plan revision recommendations.

This first implementation wave only activates the `plan_review` slot in
`manual_only` mode. `requirement_shaping` and `completion_review` remain
inactive and must not block workflow progression.

## Authority Boundaries

- Blueprint Runtime daemon/API is the canonical authority.
- Packet export is read-only and parallel-safe.
- Response import is Runtime lease-protected.
- Advisory recommendation recording is Runtime lease-protected.
- Consultant responses are advisory evidence only.
- Consultant responses must not approve implementation, lifecycle transitions,
  dispatcher execution, `close_commit`, Runtime lease bypass, or plan mutation.
- External API integration and autonomous consultant calls are out of scope.

## Canonical Commands

Use the Runtime CLI/API:

```bash
node ai/runtime/dist/cli.js consultant status --json
node ai/runtime/dist/cli.js consultant export-packet --slot plan_review --json
node ai/runtime/dist/cli.js consultant validate-packet --file <path> --json
node ai/runtime/dist/cli.js consultant validate-response --file <path> --json
node ai/runtime/dist/cli.js consultant import-response --file <path> --json
node ai/runtime/dist/cli.js consultant list-responses --json
node ai/runtime/dist/cli.js consultant show-response --id <id> --json
node ai/runtime/dist/cli.js consultant record-plan-revision-recommendation --from-response <id> --json
```

Shell wrappers are not canonical for consultant checkpoint behavior. If a
wrapper is added later, it must be a thin Runtime API facade and registered in
the shell-entrypoint registry.

## Manual Workflow

1. Inspect checkpoint status.
2. Export a `plan_review` packet.
3. Manually send the packet to the external consultant.
4. Save the consultant response as YAML or JSON.
5. Validate the response.
6. Import the response through Runtime CLI/API.
7. Record the advisory plan revision recommendation.
8. Orchestrator reviews the advisory evidence and decides the next plan action.

Imported responses are stored in Runtime working state under
`.tmp/consultant-checkpoints/` and durable report artifacts under
`ai/reports/consultant-checkpoints/`.

## Workflow State

`waiting_for_manual_consultant_review` is a Runtime workflow/run-path state. It
blocks implementation progression, but read-only status, export, validation,
and inspection commands remain allowed. This state is intentionally not a chunk
lifecycle state in the first wave.