the-high-council 0.7.6 → 0.7.7

package/README.md

@@ -1,28 +1,28 @@
 # The High Council
 
-> **Repository status (2026-09-22): going private until the open-source release.** Development
-> continues in a private repository, and the public open-source release is planned for later this
-> year. Until then, the published npm package `the-high-council` (0.7.6) stays installable as it
-> is, and the `npx github:...` lines below only work for someone with access to this repository.
-> The licence of everything already released stays MIT.
+A planning harness that runs one idea past several AI models from different labs, makes them
+argue about software engineering, architecture, specific features, roadmaps and philosophy, and
+stops at a checkable result at an estimated price, with a variable number of debate rounds, model
+seats and labs (except xAI) and variable token limits per response and model.
 
 See it work right now - no keys, no setup, no cost:
 
     npx the-high-council council demo
 
-Add it to Claude Code as an MCP server the same way:
-
-    claude mcp add council -- npx -y the-high-council council --mcp
+The demo takes one example request (a tool that renames holiday photos by date) through every
+stage: blind proposals, an anonymised debate in which one proposal is withdrawn and two are
+amended, a panel that splits in round 1 and signs off in round 2, and the handoff file. Every
+model reply in it is written in advance; what is real is the code that runs the stages around
+them.
 
-*(With access to this repository, `npx github:muad-yasin/the-high-council-mcp council demo` runs
-the current source instead of the published package.)*
+Add it to Claude Code as an MCP server:
 
-A planning harness that runs one idea past several AI models from different labs, makes them
-argue about it on the record, and stops at a checkable result.
+    claude mcp add council -- npx -y the-high-council council --mcp
 
 Runs as an **MCP server** (so an agent like Claude Code can drive it) or as a **CLI**. Bring your
 own API keys. Nothing is resold, nothing is hosted for you, and your keys go only to the
 providers you choose, never to us.
+
 Run `npx the-high-council council doctor` to see which of your own keys are
 set, which shipped chains you can already run with them, and what each would cost - before
 spending anything.
@@ -33,10 +33,65 @@ spending anything.
 > disagreement between models *visible and recorded* instead of averaged away - you can read who
 > objected to what, who withdrew a proposal under argument, and who held their position.
 
-**A visual walkthrough of all of this - the stages, one real run's debate board, and what that run
-cost - is at [muad-yasin.github.io/the-high-council-mcp](https://muad-yasin.github.io/the-high-council-mcp/).**
-A different write-up, built around one run's actual debate board, is at
-[sower-industries.de/en/MCP/](https://sower-industries.de/en/MCP/).
+## Your first ten minutes
+
+New to API keys, or to this? This path costs nothing until step 4, and step 4 tells you the price
+before anything is spent.
+
+1. **Watch one.** `npx the-high-council demo` walks an example request through every stage with
+   scripted replies. No key, no network, $0.
+2. **Make it yours.** `npx the-high-council init` writes `tasks/my-first-task.md` (edit it into
+   your own idea, in plain words) and `chains/my-first-chain.json`, and runs a $0 mock pass so
+   you can look inside a real run folder.
+3. **Find the least setup.** `npx the-high-council doctor` lists what your keys can run. Its
+   "Start here" block names the chains that need **one key only**: a single `OPENROUTER_API_KEY`
+   (one account at [openrouter.ai](https://openrouter.ai) that reaches many labs' models) is
+   enough for a seven-lab panel. Put the key in a file called `.env` in the folder you run from,
+   as `OPENROUTER_API_KEY=...`, and add `.env` to your `.gitignore` so it is never committed.
+4. **Price it, then run it.** Add `--dry-run` to see the worst-case price for your task, then run
+   it without:
+
+       npx the-high-council --task tasks/my-first-task.md --chain cheap-7-v2 --dry-run
+       npx the-high-council --task tasks/my-first-task.md --chain cheap-7-v2
+
+   Every run stops before it would pass its spend cap ($7 unless you set `--max-usd`). A run
+   stopped by the cap keeps what it paid for but has no plan yet, so pick a cap at or above the
+   dry run's price. A panel that signs off early costs less than the worst case.
+
+   The plan lands in `runs/<time>/deliverable.md`; the argument behind it is in `BOARD.md`.
+
+No key and no budget? A chain can run on models on your own machine through
+[Ollama](#local-models-ollama-lm-studio-) at $0, if your computer can run them.
+Everywhere below, `council` means `npx the-high-council` unless you installed it globally.
+
+## Words used here
+
+- **Lab** - a company that makes AI models (Anthropic, OpenAI, Google, DeepSeek, ...). "Different
+  labs" means models trained by different companies.
+- **Provider** - where a call goes and who bills it: a lab's own API, OpenRouter (many labs, one
+  key and one bill), or `ollama` (your own machine).
+- **API key** - a secret string from a provider that lets a program use your account there. You
+  pay the provider for what the program uses; nobody else sees the key.
+- **Seat** - one job in a run, filled by one model: the one that writes criteria, the builder, a
+  critic, and so on.
+- **Chain** - a JSON file that says which model sits in which seat and which stages run. Pick one
+  with `--chain`; `council doctor` lists them all.
+- **Task** - your request, a plain text file in `tasks/`. No format.
+- **Criteria** - yes/no checks the plan has to pass, written from your task before anyone plans.
+- **Proposal, debate** - each lab suggests parts of the plan without seeing the others, then
+  they read each other's (with names hidden) and object, support or merge.
+- **Panel, round, sign-off** - the critics grade the draft against the criteria; each failed check
+  goes back for a revision, which is one round. Sign-off means a critic found nothing failing.
+- **Dry run** - `--dry-run`: price a run, call nothing.
+- **Spend cap** - the most one run may cost. It is checked before every paid call.
+- **Mock** - a fake provider with scripted replies, for trying the machinery for free.
+- **External** - a seat that waits for a person or another agent (such as your Claude Code session)
+  to answer it from a file.
+- **Handoff** - `HANDOFF.md`, the build instructions a coding agent works from.
+
+**A visual write-up of all of this, built around one real run, is at
+[sower-industries.de/MCP](https://sower-industries.de/MCP).** What changed in each release:
+[CHANGELOG.md](CHANGELOG.md).
 
 ## How it works
 
@@ -63,11 +118,13 @@ withdrawal), `HANDOFF.md`, a per-lab scoreboard, and the real token/cost account
 ### Reading a run with a program
 
 `BOARD.md` is for people. **`report.json` is the same board, structured** - if you are building
-anything on top of a run, read that instead. Do not parse the markdown.
+anything on top of a run, read that instead. Do not parse the markdown. The format is versioned
+(`schemaVersion`) and published as a JSON Schema, `schemas/report-v1.json`; which fields are stable,
+which are experimental, and how versions change: [docs/report-format.md](docs/report-format.md).
 
 ```jsonc
 {
-  "runId": "...", "chain": "...", "passed": false, "maxUsd": 5,
+  "schemaVersion": 1, "runId": "...", "chain": "...", "passed": false, "maxUsd": 5,
   "criteria":  [ "each acceptance criterion, as written before the debate" ],
   "questions": [ { "question": "...", "why": "...", "default": "..." } ],  // null if the chain skipped them
   "proposals": [ { "id": "DEEPSEEK-1", "lab": "deepseek", "model": "...",
@@ -90,7 +147,17 @@ anything on top of a run, read that instead. Do not parse the markdown.
     "replies": [ { "id": "GLM-ALT", "action": "keep|amend|withdraw", "text": "..." } ],
     "dropouts": [ { "lab": "...", "model": "...", "stage": "alternatives", "reason": "..." } ]
   },
-  "signoff": [ { "provider": "qwen", "model": "...", "signedOff": false,
+  // Only on chains with `argued: { enabled: true }` (off by default, on in no shipped chain): the
+  // "How this plan was argued" section, written to ARGUED.md next to deliverable.md (never inside it)
+  // by the handoff seat, from a fact pack of this run's own record. unknown_refs / unknown_labs are
+  // ids and labs it named that the run never had; each is also a line in WARNINGS.md.
+  "argued": {
+    "file": "ARGUED.md",
+    "facts_counts": { "labs": 7, "alternatives": 7, "proposals": 14, "objections": 9, "...": 0 },
+    "unknown_refs": [], "unknown_labs": [], "missing_labs": [], "missing_sections": [],
+    "refs_cited": 23, "ok": true
+  },
+  "signoff": [ { "lab": "qwen", "provider": "qwen", "model": "...", "signedOff": false,
                  "objections": [ { "criterion": "...", "problem": "...", "fix": "..." } ] } ],
   "lastCritique": { "meets": false, "failures": [ { "criterion": "...", "lab": "qwen" } ] },
   "scoreboard": {
@@ -122,6 +189,8 @@ those plus `text` and may carry more (an `amend` often brings a `how`). `replace
 when the action is `withdraw`. `proposals[]` likewise carries `withdrawn` / `amended` /
 `replaced_by` only when they apply. Read defensively: check for a field, do not assume it.
 
+`signoff[].lab` is the seat's lab; `signoff[].provider` holds the same value under an older,
+misleading name and is deprecated (kept until the report format's version 2).
 `signoff[].objections` is why a seat declined, on the seat's own record. `signedOff: null` means
 the seat gave no usable reply and abstained - neither a pass nor an objection, and `objections` is
 `null` rather than empty so the two stay apart. A seat that agreed has an empty list.
@@ -129,7 +198,7 @@ The same objections also appear flattened in `lastCritique.failures[]`, tagged w
 the reviser wants the union across the whole panel. Both are built in one pass; they cannot drift.
 
 **Before you publish a run,** note that `report.json` records `task` as the path to your task file
-on your own disk. Nothing transmits it anywhere - but if you are rendering a board onto a public
+(relative to where you started the run, never absolute). Nothing transmits it anywhere - but if you are rendering a board onto a public
 page, drop that field. The debate itself is the part worth showing.
 
 ## Requirements
@@ -139,14 +208,18 @@ page, drop that field. The debate itself is the part worth showing.
 
 ## Setup
 
+Nothing to install beyond Node: `npx the-high-council council <command>` fetches the published
+package and runs it. To keep a `council` command on your PATH instead:
+
 ```bash
-git clone https://github.com/muad-yasin/the-high-council-mcp.git
-cd the-high-council-mcp
-npm install
-cp .env.example .env
+npm install -g the-high-council
+council doctor
 ```
 
-Fill in `.env` with only the keys your chosen chain needs. Supported providers:
+`council` reads and writes in the directory you run it from: `.env` for keys, `tasks/` for
+requests, `runs/` for output, and a `chains/` of your own there takes precedence over the bundled
+ones. Put only the keys your chosen chain needs in that `.env`, one `NAME=value` per line
+(`.env.example` in the package lists them all). Supported providers:
 
 `ANTHROPIC_API_KEY` · `OPENAI_API_KEY` · `GOOGLE_API_KEY` · `MISTRAL_API_KEY` ·
 `DEEPSEEK_API_KEY` · `GROQ_API_KEY` · `TOGETHER_API_KEY` · `COHERE_API_KEY` ·
@@ -159,6 +232,19 @@ refuses such a seat, with no override. There is no `xai` provider.
 The CLI refuses to start if any seat in the chosen chain is missing its key, rather than failing
 halfway through a paid run. `ollama` (below) is the one exception - it needs no key at all.
 
+### From source
+
+```bash
+git clone https://github.com/muad-yasin/the-high-council-mcp.git
+cd the-high-council-mcp
+npm install
+cp .env.example .env
+```
+
+In a clone, `node src/cli.js` does what `council` does, on the current source rather than the
+published package. `npx github:muad-yasin/the-high-council-mcp council demo` runs the current
+source without cloning.
+
 ### Standalone binaries (build them yourself)
 
 There are no published binary downloads yet. From a clone you can build a single-file `council`
@@ -218,17 +304,20 @@ mkdir -p tasks
 echo "Plan the data model for a bookmarking app. Single user, offline-first." > tasks/your-idea.md
 
 # see what's available and what it would cost
-node src/cli.js --help
-npm run dry -- --task tasks/your-idea.md --chain verify
+council --help
+council --task tasks/your-idea.md --chain verify --dry-run
 
 # a real run
-node src/cli.js --task tasks/your-idea.md --chain verify
+council --task tasks/your-idea.md --chain verify
 ```
 
-`tasks/` and `runs/` are both gitignored. Your requests and everything the council writes about
-them stay on your machine - if you fork this repo, you will not accidentally publish them.
+Your requests and everything the council writes about them stay on your machine, in `tasks/` and
+`runs/` under the directory you ran from. In a clone of this repo both are gitignored, so a fork
+will not accidentally publish them.
 
-`verify` is the cheap default: two labs, a hard two-round cap. Start there.
+`verify` is the default when you name no chain: a panel of two labs, a hard two-round cap. It
+needs three keys (Anthropic, OpenAI and Google, one account each). With one OpenRouter key, start
+with `cheap-7-v2` instead; `council doctor` lists every chain that runs on the keys you have.
 
 ### Exit codes
 
@@ -287,8 +376,8 @@ stage - a stage that could take the run past the ceiling is never called, so the
 than reporting the overspend afterwards.
 
 ```bash
-node src/cli.js --task tasks/x.md --max-usd 2     # this run stops at $2
-node src/cli.js --task tasks/x.md --max-usd none  # no ceiling
+council --task tasks/x.md --max-usd 2     # this run stops at $2
+council --task tasks/x.md --max-usd none  # no ceiling
 export MAX_USD_PER_RUN=20                         # change the default
 ```
 
@@ -298,7 +387,7 @@ stage it stopped at, and what that stage would have cost. Nothing is half-writte
 with a higher ceiling - completed stages replay from disk and cost nothing the second time:
 
 ```bash
-node src/cli.js --resume runs/<id> --max-usd 10
+council --resume runs/<id> --max-usd 10
 ```
 
 A stage replays only if it would be asked the same thing again: the task text, the chain config
@@ -312,11 +401,11 @@ changed prompt: it is set aside the same way and the run asks you again.
 The cap governs one run. To see what you have spent across all of them:
 
 ```bash
-node src/cli.js --spend            # today
-node src/cli.js --spend --days 7   # the last week
-node src/cli.js --cost-today       # today by calendar day, with a per-model breakdown
-node src/cli.js --cost-today --date 2026-09-01
-node src/cli.js --stats --days 30    # how the debate mechanism itself is doing
+council --spend            # today
+council --spend --days 7   # the last week
+council --cost-today       # today by calendar day, with a per-model breakdown
+council --cost-today --date 2026-09-01
+council --stats --days 30    # how the debate mechanism itself is doing
 ```
 
 That is read back off the run folders on disk - there is no ledger file, nothing is recorded
@@ -328,7 +417,7 @@ To watch this work without spending anything, the `mock-budget` chain calls no A
 fixture prices:
 
 ```bash
-node src/cli.js --task tasks/your-idea.md --chain mock-budget --max-usd 1
+council --task tasks/your-idea.md --chain mock-budget --max-usd 1
 ```
 
 If a chain pauses for your input, it writes `NEEDS-<stage>.md` into the run folder and tells you
@@ -336,7 +425,7 @@ how to resume:
 
 ```bash
 # write your answer to runs/<id>/answers.md, then:
-node src/cli.js --resume runs/<id>
+council --resume runs/<id>
 ```
 
 ## Quick start (MCP)
@@ -347,9 +436,8 @@ Register the server with your MCP client. No clone needed - from the published n
 claude mcp add council -- npx -y the-high-council council --mcp
 ```
 
-With access to this repository (private until the open-source release), the same line with
-`npx -y github:muad-yasin/the-high-council-mcp` runs the current source instead. The clone and
-plugin-marketplace routes below need that access too.
+The same line with `npx -y github:muad-yasin/the-high-council-mcp` runs the current source
+instead.
 
 Or from a clone of this repo:
 
@@ -378,20 +466,16 @@ clone itself, so run `npm install` in it first.
 Registering with a client other than Claude Code (DeepSeek Harness, OpenHands, Cline, goose,
 Continue): [docs/mcp-clients.md](docs/mcp-clients.md) has the real config for each.
 
-An npm package is also live:
-
-```bash
-claude mcp add high-council -- npx -y the-high-council --mcp
-```
-
-Either way the server reads and writes in **your** working directory, not inside the package:
-`.env` for keys, `tasks/` for requests, `runs/` for output, and a `chains/` of your own takes
-precedence over the bundled ones.
+Whichever way you add it, the server reads and writes in **your** working directory, not inside
+the package: `.env` for keys, `tasks/` for requests, `runs/` for output, and a `chains/` of your
+own takes precedence over the bundled ones. In a git project, add `.env` (and `runs/` if your
+ideas are private) to `.gitignore` before an agent commits everything; `council doctor` warns
+when `.env` is not ignored.
 
-To run it by hand, from a clone:
+To run it by hand:
 
 ```bash
-npm run mcp          # or: node src/cli.js --mcp
+council --mcp        # from a clone: npm run mcp
 ```
 
 Then drive it with these tools:
@@ -425,7 +509,7 @@ for anyone with a subscription, since the project's cost story depends on it.
 
 ## Chains
 
-48 chain configs live in `chains/`. Each one is plain JSON - the seat roster, which models fill
+49 chain configs live in `chains/`. Each one is plain JSON - the seat roster, which models fill
 which seat, the round cap, and whether proposals/debate/handoff stages run. They are meant to be
 copied and edited.
 
@@ -461,57 +545,6 @@ Read a chain's `description` field before running it; they say what they cost yo
   before. **No efficacy claim**: this ships the mechanism, not evidence that it helps - see
   CHANGELOG.md's 0.6.0 entry.
 
-## New in 0.6.0
-
-- **Role-assigned debate seats** - see the `role` field above. Ships the mechanism only; whether
-  it changes anything about a real debate is untested by this release.
-- **`report.json`'s `debate.diagnostics`** - four failure-mode signals computed from a run's own
-  real debate output (never from an offline probe): a seat quoting no evidence despite objecting
-  or merging, textual overlap between differently-lensed seats' posts on the same proposal, a
-  same-run gap between role-bearing and role-less seats' evidence quoting, and the share of a
-  seat's own words that fall inside quoted evidence versus voice. Present (with nulls/empty
-  flags where there's nothing to compute) on any run that had a debate stage; absent otherwise.
-- **`debate.tie_break`** - a `report.json` field recording a weighted-tiebreak event, when one
-  fires. Not yet wired into a live vote-counting decision in this release.
-- **`PERSONAS.md`** - the five default public persona names and their voice directives, and how
-  an operator replaces the whole set with their own via `COUNCIL_PERSONAS_FILE`.
-
-## New in 0.5.0
-
-- **`council init [--yes]`** - the first thing to run in a fresh clone with no keys yet. Prints a
-  key check, writes a starter chain and task file you own (`chains/my-first-chain.json`,
-  `tasks/my-first-task.md` - a rerun never overwrites an edit you made to either), prices the
-  starter chain with no network call, then runs a canned, all-mock, $0 task end to end so the
-  first thing you inspect is a real run folder, not just terminal output.
-- **`council doctor --chain <file>`** - lints one chain config before you ever run it: a seat
-  under a misspelled key (never wired to any stage), a missing or empty `seats.critics` (the
-  review round can't run), or a seat naming a provider this codebase doesn't know. The same check
-  also runs automatically, fail-loud, the moment you try to actually run a broken chain - before
-  any paid call.
-- **`council doctor --scan-artifacts`** - scans your `tasks/` and `chains/` for the key formats
-  listed in `src/secret-patterns.js` before you commit or share them. A format not on that list is
-  not caught. Reports the file and line, never the matched text.
-- **`council --forecast-cost --chain <name> [--days N]`** - a realistic-case USD range for a
-  chain, built from its own historical runs on your machine and repriced at today's rates -
-  distinct from `--dry-run`'s worst-case estimate from a chain's declared token assumptions.
-- **`council export-board --run <folder> --out <file>`** - a run's proposals, debate, replies and
-  verdict as one self-contained HTML file. No external assets, no server, `<details>` sections.
-- **`council replay --run <folder> [--json]`** - a numbered, step-by-step transcript of a run's
-  reasoning in your terminal, with a `--json` mode for scripting.
-- **A structured error catalog** (`COUNCIL-E001`-`COUNCIL-E005`, see [TROUBLESHOOTING.md](TROUBLESHOOTING.md))
-  for the hard-fail paths this project actually has - a missing key, an unpriced model, a
-  malformed chain file, an unreadable stage reply - each with a plain-words cause, a concrete fix
-  naming the real file, and a doc pointer. Degradable conditions exit 5; fatal ones exit 6.
-- **Structured per-stage JSON logs** - every run now also writes `stage-log.jsonl` (one line per
-  stage: seat, lab, token counts, cost, timing - no prompt content) alongside the existing
-  markdown/`report.json` artifacts.
-- **[CONTRIBUTING.md](CONTRIBUTING.md)** - the three smallest landable contribution shapes, for
-  anyone who wants to send a PR rather than only file an issue.
-
-None of the above change any existing chain's behaviour. `schemaVersion` and
-`max_proposals_per_seat` are both opt-in; a chain file that predates 0.5.0 runs exactly as it did
-before.
-
 ## How this was built
 
 Vibecoded, with **Claude Code** doing the writing, by one person at
@@ -602,16 +635,14 @@ what each rule guards against and why. Copy the folders you want into your proje
 
 ## Privacy
 
-This tool and the [demo page](https://muad-yasin.github.io/the-high-council-mcp/demo.html)
-collect nothing. Stated plainly, not as a claim about quality:
+This tool collects nothing. Stated plainly, not as a claim about quality:
 
 - No telemetry, no analytics, no tracking of any kind, anywhere in this repo.
 - The only network calls this tool ever makes are to the AI provider APIs you configure with
   your own keys (`ANTHROPIC_API_KEY`, `OPENROUTER_API_KEY`, and so on) - and only when you start
   a real run with a non-mock, non-external seat. `council doctor` and `council demo` make zero
   network calls; both are implemented to read only local files and environment variable names.
-- The landing page (`docs/`, moving from GitHub Pages to sower-industries.de while this
-  repository is private) ships no JavaScript and loads no third-party resource - see
+- The landing page in `docs/` ships no JavaScript and loads no third-party resource - see
   `test/landing-page.test.js`, which fails the build if either ever changes.
 - Everything a run produces - the task, the debate, the deliverable, the cost - is written to a
   folder on your own disk (`runs/<id>/`) and nowhere else. Deleting that folder deletes the
@@ -646,8 +677,10 @@ hand, 2026-09-13, on the live site:
 
 ## Reporting a bug
 
-Write to [contact@sower-industries.de](mailto:contact@sower-industries.de). (GitHub issues open
-again with the public release; while the repository is private, email is the only route.)
+Open an issue at
+[github.com/muad-yasin/the-high-council-mcp/issues](https://github.com/muad-yasin/the-high-council-mcp/issues).
+For anything security-related, or that should not be public, write to
+[contact@sower-industries.de](mailto:contact@sower-industries.de) instead.
 
 ## If this makes you money
 

package/TROUBLESHOOTING.md

@@ -56,3 +56,51 @@ starts, so nothing was spent.
 **Fix:** if the file itself won't parse, fix its JSON syntax. Otherwise, either
 change the chain so it no longer violates the listed limit(s), or change
 `policy.json` if the limit itself was wrong. See [docs/policy.md](docs/policy.md).
+
+## Before any code: first-run problems
+
+These have no code of their own. Each is something a first-time user hit when the path was
+walked from zero (2026-09-25).
+
+### `council: command not found`
+
+`council` is only a command after `npm install -g the-high-council`. With `npx`, type
+`npx the-high-council` wherever the docs say `council` (for example
+`npx the-high-council doctor`). The CLI's own hints use the `npx` form when you started it
+with `npx`.
+
+### `HTTP 401` - the key was not accepted
+
+The provider rejected the key in the named variable (for example `OPENROUTER_API_KEY`). Check
+that it was copied whole, with no quotes or spaces around it, that it is still active on the
+provider's site, and that it belongs to that provider (an OpenAI key does not work as an
+OpenRouter key). Fix `.env`, then `council --resume runs/<id>`.
+
+### `HTTP 402` - no credit
+
+The provider would not bill the call: the account has no credit or reached its own spend limit.
+A new account usually needs credit added before paid models answer. Add it on the provider's
+site, then resume. Completed stages replay for free.
+
+### `HTTP 403` - refused
+
+A disabled key, a model your account is not allowed to use, or a block on the provider's side.
+Check the key and the model name on the provider's site.
+
+### `nothing is listening at http://localhost:11434`
+
+A seat uses `ollama` and no Ollama server is running. Start Ollama (the app, or `ollama serve`),
+pull every model the chain names (`ollama pull llama3.1`), then resume. `council doctor` lists
+local chains as runnable because they need no key, not because the server is up.
+
+### A run stopped with `STOPPED: per-run spend cap reached` (exit 4)
+
+The next stage's worst case would have crossed the cap. Nothing past the cap was spent, and no
+plan was written yet. `council --resume runs/<id> --max-usd <higher>` continues from where it
+stopped. The run tells you at the start when a chain's worst case is above your cap.
+
+### `.env holds your API keys and git would commit it`
+
+`council doctor` found a `.env` in a git repository that `.gitignore` does not cover. Add a line
+`.env` to `.gitignore` before the next commit. If a key was ever committed or pushed, revoke it on
+the provider's site and make a new one: deleting the file later does not remove it from history.

package/chains/mock-criteria-kinds.json

@@ -0,0 +1,19 @@
+{
+  "name": "mock-criteria-kinds",
+  "description": "Offline. Calls no API and costs nothing. The mock chain with criterion kinds on: every criterion is checkable (with its command) or judgement, and the board counts them.",
+  "maxRounds": 2,
+  "stopOnPass": true,
+  "handoff": true,
+  "criteria_kinds": { "enabled": true },
+  "estimate": { "promptTokens": 1000, "draftTokens": 1000, "critiqueTokens": 300 },
+  "seats": {
+    "criteria": { "provider": "mock", "model": "mock-criteria" },
+    "builder":  { "provider": "mock", "model": "mock-builder" },
+    "reviser":  { "provider": "mock", "model": "mock-builder" },
+    "critics": [
+      { "provider": "mock", "model": "mock-critic-a" },
+      { "provider": "mock", "model": "mock-critic-bare-met" }
+    ],
+    "handoff":  { "provider": "mock", "model": "mock-builder" }
+  }
+}

package/package.json

@@ -1,8 +1,19 @@
 {
   "name": "the-high-council",
-  "version": "0.7.6",
+  "version": "0.7.7",
+  "mcpName": "io.github.muad-yasin/the-high-council",
   "description": "The High Council: a multi-model planning harness. One builder, independent critics from other labs, checkable acceptance criteria, a debate on the record, and a hard stop.",
   "type": "module",
+  "main": "./src/api.js",
+  "types": "./types/index.d.ts",
+  "exports": {
+    ".": {
+      "types": "./types/index.d.ts",
+      "import": "./src/api.js",
+      "default": "./src/api.js"
+    },
+    "./package.json": "./package.json"
+  },
   "license": "MIT",
   "bin": {
     "council": "src/cli.js"
@@ -44,6 +55,8 @@
   "files": [
     "src/",
     "chains/",
+    "schemas/",
+    "types/",
     "README.md",
     "TROUBLESHOOTING.md",
     "CONTRIBUTING.md",
@@ -70,6 +83,7 @@
     "cli"
   ],
   "devDependencies": {
-    "@yao-pkg/pkg": "6.22.0"
+    "@yao-pkg/pkg": "6.22.0",
+    "ajv": "^8.20.0"
   }
 }