{{ conventions }}

## Task

Orient yourself in this repository and tell me what to do next.

Answer at **{{ depth }}** depth.

- `full` — work through all four sections below, then recommend.
- `recommendation` — do the same reading, but report only the recommendation
  and the reasoning that supports it. Brevity here is about output, not effort:
  do not skip the reading.

### 1. What is this repo for

State its purpose in your own words from `INTENT.md`, `SCOPE.md` and the code —
not by quoting the README. If intent and implementation disagree, say so; that
disagreement is usually the most useful thing you will find.

### 2. What work is pending

List open workplans and their unfinished tasks, from the workplan files rather
than from memory. For each, give its status and what is actually blocking it.
Note any task marked `ready` whose premises no longer hold.

### 3. What completing it is worth

For each significant piece of pending work, say what changes once it is done —
a capability gained, a risk retired, a manual step removed, a decision
unblocked. Be concrete. "Improves quality" is not a benefit; "removes the
manual reconciliation step that currently precedes every release" is.

Where the benefit is speculative, say so rather than inflating it.

### 4. What it would cost

Estimate effort per item as **small** (under a session), **medium** (a session
or two), or **large** (multiple sessions, or needs a decision first). Name the
main uncertainty driving each estimate. Do not give hour figures — they imply a
precision you do not have.

### 5. Recommendation

Recommend **one** next action, and say why it beats the alternatives you
considered. Prefer work that unblocks other work, retires a risk, or resolves a
decision others are waiting on. If the honest answer is that nothing here is
worth doing now, say that.