ennodia 0.3.0-rc.2 → 0.4.0

package/docs/getting-started.md

@@ -19,7 +19,35 @@ Your agent will identify any client restart or reload needed to make the new too
 After setup, [try your first useful result](#your-first-useful-result).
 For manual setup, follow the instructions below.
 
-## Manual Setup
+## Your first useful result
+
+After installation, give your primary agent a small request:
+
+```text
+Use Ennodia MCP to get one additional opinion on this function.
+Choose an available agent. Keep the review read-only.
+Return one concrete issue or explain that no issue was established.
+Bring the findings back to this conversation.
+```
+
+Start with one worker and a small set of files.
+Discovery checks installed commands, not authentication, model access, or provider quota.
+A live task establishes which configuration works in your environment.
+
+Your agent can call `ennodia_list_harnesses`, then `ennodia_run` with a selected `harnessId`, `mode: "single"`, and `compare: false`.
+Poll `ennodia_get_run` with the returned run identifier (ID).
+Stop when the status is `succeeded`, `failed`, or `cancelled`.
+
+Inspect the result before starting more work.
+Use the [recipes](/docs/guides/recipes/) for a stuck task, a skill trial, or conflicting answers.
+See [Understand Results](/docs/guides/understand-results/) when the attempt is incomplete or unhelpful.
+
+Expect live runs to take time. A timeout budget is not a completion prediction.
+Compare adds a Judge pass and a Result Advisor pass after child agents finish.
+
+For a local development checkout, run `bun run verify` before relying on changes.
+
+## Manual setup
 
 ### Requirements
 
@@ -44,7 +72,7 @@ To use Bun directly, run `bunx ennodia`.
 The JSR package `@cherninlab/ennodia` exposes TypeScript modules for import.
 Use the npm package for the stdio MCP executable.
 
-### Local Checkout
+### Local checkout
 
 Use a checkout to modify Ennodia:
 
@@ -55,7 +83,7 @@ bun install
 bun run verify
 ```
 
-### MCP Client Config
+### MCP client config
 
 ```json
 {
@@ -83,40 +111,15 @@ For a local checkout, use the source file:
 
 Replace `/absolute/path/to/ennodia` with your local repository path.
 
+Ennodia loads six core tools by default. For Plan Advisor, compositional slices, raw tasks, and skill installation, add `"--tools", "all"` to `args`. See [tool sets](/docs/reference/mcp-tools/#tool-sets).
+
 Use your client's supported configuration method.
 Preserve existing server entries.
 Reload the tools or restart the client if its setup instructions require this step.
 
-## Your first useful result
-
-After installation, give your primary agent a small request:
-
-```text
-Use Ennodia MCP to get one additional opinion on this function.
-Choose an available agent. Keep the review read-only.
-Return one concrete issue or explain that no issue was established.
-Bring the findings back to this conversation.
-```
-
-Start with one worker and a small set of files.
-Discovery checks installed commands, not authentication, model access, or provider quota.
-A live task establishes which configuration works in your environment.
-
-Your agent can call `ennodia_list_harnesses`, then `ennodia_run` with a selected `harnessId`, `mode: "single"`, and `compare: false`.
-Poll `ennodia_get_run` with the returned run identifier (ID).
-Stop when the status is `succeeded`, `failed`, or `cancelled`.
-
-Inspect the result before starting more work.
-Use the [recipes](/docs/guides/recipes/) for a stuck task, a skill trial, or conflicting answers.
-See [Understand Results](/docs/guides/understand-results/) when the attempt is incomplete or unhelpful.
-
-Expect live runs to take time. A timeout budget is not a completion prediction.
-Compare adds a Judge pass and a Result Advisor pass after child agents finish.
-
-For a local development checkout, run `bun run verify` before relying on changes.
-
-## Optional Team Advice
+## Optional team advice
 
+Team advice uses the [full tool set](/docs/reference/mcp-tools/#tool-sets).
 For a proposed work split, call `ennodia_start_plan_advice`. The Plan Advisor
 proposes explicit harness, model, and skill assignments. It cannot execute them.
 
@@ -138,7 +141,7 @@ completed answers. Then the Result Advisor recommends one answer.
 If Judge analysis is not available, the Result Advisor can use only the
 candidate outputs. The Compare result shows this condition.
 
-## Next Pages
+## Next pages
 
 - [Budgets and Limits](/docs/guides/budgets-and-limits/) explains
   `ennodia_estimate_budget` and run limits.
@@ -148,7 +151,7 @@ candidate outputs. The Compare result shows this condition.
   and installation notes.
 - [MCP Tools](/docs/reference/mcp-tools/) is the full parameter reference.
 
-## Expected Behavior
+## Expected behavior
 
 An Ennodia run is visible. You can inspect:
 

package/docs/guides/agent-skills.md

@@ -3,6 +3,8 @@ title: Agent Skills
 description: Install bundled Ennodia skills in native harness locations and tell child agents to use them during a run.
 ---
 
+Listing skills is in the core tool set. Installing them needs the [full tool set](/docs/reference/mcp-tools/#tool-sets).
+
 A new Agent Skill can help a task, add irrelevant advice, or make no difference.
 Try the skill in a separate Ennodia task and bring useful findings back to your main conversation.
 
@@ -11,9 +13,8 @@ Ennodia discovers that folder and requests the selected skill by name.
 It does not inline the full instructions into each delegated prompt.
 
 The primary agent can keep useful partial findings without adopting every recommendation.
-The [skill trial example](/docs/evidence/skill-trial/) shows a controlled small exercise.
 
-## List Available Skills
+## List available skills
 
 ```json
 {
@@ -27,7 +28,7 @@ The [skill trial example](/docs/evidence/skill-trial/) shows a controlled small
 The response includes bundled skills, installed native skills, searched
 directories, and load warnings.
 
-## Preview Installation
+## Preview installation
 
 Bundled skills use dry-run installation by default. The caller can inspect the
 planned writes before any change:
@@ -47,7 +48,7 @@ planned writes before any change:
 
 Review the planned paths. If they are correct, repeat with `dryRun: false`.
 
-## Use a Skill in a Run
+## Use a skill in a run
 
 ```json
 {
@@ -81,7 +82,7 @@ Bundled skills include:
 | `release-readiness` | Public release candidate checks. |
 | `benchmark-critic` | Benchmark credibility and reproducibility review. |
 
-## Native Install Locations
+## Native install locations
 
 | Harness | Project path | User path |
 | --- | --- | --- |
@@ -96,5 +97,5 @@ exact tool parameters.
 ## Main-agent delegation skill
 
 The bundled `pragmatic` skill guides the main agent through bounded delegation and result verification.
-Install it using `skillIds: ["pragmatic"]`. Do not pass it to workers through run `skillIds`.
+Install it using `skillIds: ["pragmatic"]`. A delegated coordinator can use it when orchestration is part of its assignment.
 See [Pragmatic mode](/docs/guides/pragmatic-mode/) for the experimental recipes.

package/docs/guides/budgets-and-limits.md

@@ -1,8 +1,10 @@
 ---
-title: Budgets and Limits
+title: Budgets and limits
 description: How Ennodia estimates preflight input-token budgets and enforces local run limits before child agents start.
 ---
 
+The tools on this page are in the [full tool set](/docs/reference/mcp-tools/#tool-sets). Add `--tools all` to the Ennodia server arguments to load them.
+
 Ennodia can estimate the input-token budget before a costly run starts. The
 estimate is a budget limit check, not a provider invoice. Child-task estimates
 are lower bounds.
@@ -13,7 +15,7 @@ not visible before the run.
 Use it before parallel work or long reviews. Also use it when the user limits
 cost, subscription use, or child-task count.
 
-## What the Estimate Includes
+## What the estimate includes
 
 `ennodia_estimate_budget` reports:
 
@@ -29,7 +31,7 @@ cost, subscription use, or child-task count.
 The estimate does not claim to know provider billing, output tokens, tool-call
 cost, cache behavior, harness-internal context, or private subscription quota.
 
-## Estimate Before a Run
+## Estimate before a run
 
 ```json
 {
@@ -54,7 +56,7 @@ If the estimate is too high, use one or more of these changes:
 - Decrease `maxOutputChars`.
 - Use a narrower first pass.
 
-## Enforce Limits on a Run
+## Enforce limits on a run
 
 The same budget object can be passed to `ennodia_run`:
 
@@ -78,7 +80,7 @@ Ennodia checks these local limits before child tasks start. The run fails early
 if estimated input tokens or the child-task count exceed a cap. Ennodia does
 not start the excess model work.
 
-## Subscription Limits
+## Subscription limits
 
 Subscription quota checks are conservative by design. Ennodia uses only
 supported local command-line interface (CLI) and application programming
@@ -93,7 +95,7 @@ supported local surface exposes a reliable account limit. An older fail-closed
 quota gate has been retired until at least one current harness exposes a real
 supported quota surface.
 
-## Practical Defaults
+## Practical defaults
 
 - Start with one agent and a narrow task. Add attempts when they address a specific uncertainty.
 - Use `maxOutputChars` to keep Compare input bounded.

package/docs/guides/pragmatic-mode.md

@@ -1,47 +1,76 @@
 ---
 title: Pragmatic mode
-description: Delegate bounded investigation and patch proposals to one explicitly selected model.
+description: Organize independent model attempts and compare evidence against complete acceptance criteria.
 ---
 
-Pragmatic mode is experimental in `0.3.0-rc.2`, available through `ennodia@next`.
+The tools on this page are in the [full tool set](/docs/reference/mcp-tools/#tool-sets). Add `--tools all` to the Ennodia server arguments to load them.
+
+Pragmatic mode is an opt-in beta in `0.3.0`, available through `ennodia`.
 It helps your main agent delegate bounded work without loading entire logs or files into the main conversation.
 It does not guarantee lower costs or select the cheapest model automatically.
 
-## Start a bounded task
+## Organize independent attempts
 
 Use this prompt in your main agent:
 
 ```text
-Use Ennodia MCP in Pragmatic mode to investigate the failing requests in /absolute/path/to/server.log.
-Select a supported lower-cost model from my configured harnesses.
-Return the affected timestamps, exact errors, likely cause, and evidence locations.
-Keep the full log outside this conversation. Verify the decisive evidence before recommending a fix.
+Use Ennodia MCP in Pragmatic mode to solve this task.
+Organize independent model attempts and tailor questions where useful.
+Discover relevant skills and compare a skill trial with a matched trial without requested skills.
+Compare the evidence with Judge and Result Advisor, then verify the complete acceptance criteria.
+Count planning, all attempts, retries, comparison and verification in the total cost.
 ```
 
-The main agent can call the existing run tool:
+Ennodia supports one main agent coordinating N independent workers.
+N=1 remains useful for a specialist or handoff.
+The main agent can delegate planning through Plan Advisor. It does not need to design every specialist question or locate every skill manually.
+
+1. Discover harnesses, supported model IDs and native skills.
+2. Start Plan Advisor with the full objective, model allowlists and explained limits.
+3. Inspect the validated plan and launch it with its exact digest.
+4. Inspect terminal task evidence and compare useful results with Judge and Result Advisor.
+5. Verify the complete task locally and include all attempts in the measurement.
+
+For caller-defined assignments, compositional tasks support a separate prompt, model and skill list per slice.
+A slice with `skillIds: []` requests no skills but can still discover native skills.
+A controlled skill trial requires matching environments and evidence of actual skill loading.
+
+## Finish difficult work in chunks
+
+Workers do not need to occupy a session for the full timeout.
+Use bounded chunks for investigation, implementation and integrated verification.
+Each chunk returns its artifacts, executed checks, remaining work and next step.
+A completed chunk is distinct from an accepted complete task.
+
+Independent workers can explore alternatives within a stage.
+Compare evidence at useful decision points and continue with owned sessions or compact handoffs.
+Count every chunk and handoff in the total cost.
+A deadline is a maximum allowance, not a target duration.
+
+## Evidence contracts in version 0.3.0
+
+`ennodia_run`, `ennodia_estimate_budget`, `ennodia_start_compositional` and `ennodia_estimate_compositional_budget` accept:
 
 ```json
 {
-  "tool": "ennodia_run",
-  "arguments": {
-    "harnessId": "claude-code",
-    "model": "<supported-model-from-your-configuration>",
-    "cwd": "/absolute/path/to/project",
-    "prompt": "Find the cause of failed requests in /absolute/path/to/server.log between 10:00 and 10:10. Do not modify files.",
-    "pragmatic": {
-      "recipe": "investigate",
-      "acceptanceCriteria": "Cite exact errors and timestamps. Distinguish confirmed causes from hypotheses. Report any unread ranges."
-    },
-    "timeoutMs": 120000,
-    "budget": { "maxChildTasks": 1 }
+  "pragmatic": {
+    "recipe": "investigate",
+    "acceptanceCriteria": "Cite decisive source evidence and executed checks. Report unresolved requirements."
   }
 }
 ```
 
-Replace the model placeholder with a supported identifier before calling the tool.
-The caller supplies both `harnessId` and `model`.
-The run uses `mode: single` and `compare: false`, including when these fields are omitted or set to `auto`.
-Explicit parallel execution or comparison is rejected before workers start.
+The contract preserves routing and comparison choices. It does not force one worker.
+Explicit models are optional. Omitted models use native harness defaults.
+
+Use discovered model IDs for reproducible comparisons. Use compositional slices for different models on the same harness.
+Version 0.3.0 preserves independent workers and comparison.
+
+### Select reasoning effort
+
+Source builds accept `reasoningEffort` on `ennodia_run` and `ennodia_start` for Codex workers. For example, select `model: "gpt-5.6-luna"` with `reasoningEffort: "max"`, or `model: "gpt-6-astra"` with `reasoningEffort: "low"`, when supported by your installed Codex and account. Ennodia forwards the setting to the native CLI. It does not infer the cheapest setting. Other adapters reject explicit effort settings. Omit the field to preserve native defaults.
+
+This setting applies to workers, not the Judge or Result Advisor. Run and task records preserve the requested setting. That does not prove the provider used it or establish its price.
 
 ## Get findings or a patch
 
@@ -50,7 +79,8 @@ Explicit parallel execution or comparison is rejected before workers start.
 | `investigate` | Return cited findings, small excerpts, coverage limits, and unresolved questions | Verify decisive evidence |
 | `patch` | Return a complete unified diff proposal without applying it | Review, apply, and test the patch |
 
-Both recipes instruct workers to avoid file changes, side effects, recursive delegation, and repeated failed approaches.
+Both recipes instruct workers to avoid file changes, side effects and repeated failed approaches.
+Additional delegation stays within caller-authorized scope and allowance and must be counted.
 These are worker instructions, not an enforced permission sandbox.
 Native harness permissions remain authoritative.
 A worker can fail to follow instructions, so use appropriate native permissions for sensitive work.
@@ -75,6 +105,7 @@ Use `ennodia_estimate_budget` with the same `pragmatic` settings and model to in
 Estimates do not measure total task spend, internal tool reads, or subscription quota consumption.
 
 The foundation does not retry automatically or track retries across separate runs.
+Plan Advisor, independent workers, Judge and Result Advisor all contribute to total task cost.
 Escalate unresolved work in a separate run after inspecting its evidence.
 Compare total elapsed time, verified outcomes, and all reported usage across attempts before claiming savings.
 
@@ -82,4 +113,12 @@ Compare total elapsed time, verified outcomes, and all reported usage across att
 
 The bundled `pragmatic` skill guides delegation from your main conversation.
 Install it through [Agent Skills](/docs/guides/agent-skills/) using `skillIds: ["pragmatic"]`.
-Do not request this skill on workers through run `skillIds`.
+A delegated coordinator can use this skill when its assignment includes orchestration.
+
+In version 0.3.0, wait for the worker with `ennodia_get_run`, `waitMs: 30000`, and `includeEvents: false`. A nonterminal response means the worker is still running. Read its terminal answer and verify the acceptance criteria before reporting completion. The wait itself never cancels the run.
+
+## Deadlines, permissions and continuation
+
+Workers receive an execution deadline and their configured permissions. Inspect partial findings before continuing. Use a normal authorized run for file edits.
+
+See [execution deadlines and session continuation](/docs/reference/mcp-tools/#execution-deadlines), [Troubleshooting](/docs/guides/troubleshooting/) and [Budgets and Limits](/docs/guides/budgets-and-limits/) for details.

package/docs/guides/recipes.md

@@ -3,9 +3,7 @@ title: Recipes
 description: Three small ways to get useful help from Ennodia.
 ---
 
-# Start with one useful attempt
-
-A focused request is easier to check and integrate.
+Start with one useful attempt. A focused request is easier to check and integrate.
 Give your primary agent the relevant files, attempted fixes, and the result you need.
 
 ## A task is stuck
@@ -30,7 +28,6 @@ Show which skill and model were requested and what remains unverified.
 
 Check native installation with your agent before the task starts.
 A requested skill is not proof that the worker loaded it.
-Use the [small skill trial](/docs/evidence/skill-trial/) to practice comparing two attempts.
 
 ## Two answers disagree
 

package/docs/guides/running-better-audits.md

@@ -1,5 +1,5 @@
 ---
-title: Better Audits
+title: Better audits
 description: How Ennodia audits can detect product problems that users see, not only consistency issues.
 ---
 
@@ -11,7 +11,7 @@ This pass can find broken links, mismatched documentation, release metadata erro
 errors, and copy drift. It does not prove that the page is clear to a first-time
 visitor.
 
-## Quick Recipe
+## Quick recipe
 
 Use a source-grounded audit for answers that depend on documentation,
 standards, package behavior, or another product's public surface:
@@ -31,7 +31,7 @@ standards, package behavior, or another product's public surface:
 Install the skill first if the harness does not have it. See
 [Agent Skills](/docs/guides/agent-skills/).
 
-## Pick the Audit Mode
+## Pick the audit mode
 
 Name the failure mode you want reviewers to catch.
 
@@ -50,7 +50,7 @@ For a large review, split the work into focused slices. Do not send the entire
 prompt to each reviewer. See
 [Compositional Audits](/docs/concepts/compositional-audits/).
 
-## Landing Page Rubric
+## Landing page rubric
 
 For landing pages, require each reviewer to answer these questions:
 
@@ -64,7 +64,7 @@ For landing pages, require each reviewer to answer these questions:
 For Ennodia, use `mode: "parallel"` and `compare: true` for this type of review.
 A single source-only answer is not sufficient for product pages.
 
-## Include Rendered Evidence
+## Include rendered evidence
 
 Source-only review misses visual problems. Before an Ennodia website review,
 include desktop and mobile screenshots. You can also use a harness with browser
@@ -79,7 +79,7 @@ Then inspect the child outputs for access errors.
 If a harness cannot read the files, put them in an accessible location and run
 the task again. Do not treat that failure as a normal design review.
 
-## Ground Standards in Sources
+## Ground standards in sources
 
 Include primary sources when an audit depends on an external standard, registry
 convention, or product behavior. Require reviewers to separate facts from
@@ -99,7 +99,7 @@ The bundled `source-grounded-audit` skill supports this case. Install it in the
 harnesses that perform standards-sensitive audits. Then tell Ennodia to use the
 skill when the answer depends on external documentation.
 
-## Good Prompt Shape
+## Good prompt shape
 
 ```text
 Audit this landing page as a first-time visitor, not as a code consistency

package/docs/guides/troubleshooting.md

@@ -3,8 +3,6 @@ title: Troubleshooting
 description: Resolve failed starts without confusing configuration errors with model quality.
 ---
 
-# When an attempt cannot finish
-
 Start with the task’s failure reason and captured output.
 Use `ennodia_get_task` for details and `ennodia_list_harnesses` to inspect supported commands.
 

package/docs/guides/understand-results.md

@@ -3,8 +3,6 @@ title: Understand results
 description: Distinguish useful findings, disagreement, missing evidence, and failed execution.
 ---
 
-# Understand the result
-
 Process completion is one signal. A useful answer also needs evidence that fits your task.
 
 | Result | Meaning | Next step |

package/docs/index.md

@@ -3,8 +3,6 @@ title: What is Ennodia?
 description: Try other agents, models, and skills while staying in your familiar conversation.
 ---
 
-# Keep your agent. Get another way forward.
-
 Ennodia lets your primary artificial intelligence (AI) agent try another agent, model, or skill on a focused task.
 The findings return to your existing conversation.
 
@@ -17,7 +15,7 @@ Even an unsuccessful attempt can show which approach was tested under the record
 - [Get your first result](/docs/getting-started/).
 - [Choose a recipe](/docs/guides/recipes/).
 - [Understand the result](/docs/guides/understand-results/).
-- [Read a development case](/docs/evidence/building-ennodia/).
+- [Read a recorded run](/articles/can-gemini-hear-this-file/).
 
 ## Your existing tools
 
@@ -33,7 +31,7 @@ A native agent can also choose unrequested skills from its environment.
 - [Agent skills](/docs/guides/agent-skills/)
 - [Troubleshooting](/docs/guides/troubleshooting/)
 - [Data movement and history](/docs/concepts/data-governance/)
-- [Examples and evidence](/docs/evidence/)
+- [Evidence](/docs/evidence/)
 - [Roadmap](/docs/roadmap/)
 - [Technical reference](/docs/reference/mcp-tools/)
 

package/docs/install.md

@@ -1,5 +1,5 @@
 ---
-title: Installation for Agents
+title: Installation for agents
 description: A copy-paste installation page for agents that install Ennodia in Codex, Claude Code, OpenCode, Antigravity, and other Model Context Protocol (MCP) clients.
 ---
 
@@ -7,7 +7,7 @@ This page gives setup instructions to the user's agent.
 Install Ennodia as a local Model Context Protocol (MCP) server.
 Then connect it to the user's preferred compatible client.
 
-## Copy-Paste Prompt
+## Copy-Paste prompt
 
 ```text
 try-ennodia.cherninlab.com
@@ -16,7 +16,7 @@ try-ennodia.cherninlab.com
 The user can send this address in a new or existing agent conversation.
 The agent handles the setup steps below.
 
-## Check the Environment
+## Check the environment
 
 1. Identify the user's client and the machine where Ennodia will run.
 2. Check that the client can launch a local standard input/output (stdio) MCP server.
@@ -31,7 +31,7 @@ If the current client cannot launch a local MCP server, explain the missing capa
 Use a compatible local client for Ennodia.
 See [Supported Harnesses](/docs/reference/supported-harnesses/) for the worker agents Ennodia can call.
 
-## Install Command
+## Install command
 
 Use the npm package for normal MCP client installation:
 
@@ -42,7 +42,7 @@ npx -y ennodia
 Ennodia requires Bun `1.3.14` or newer. `npx` downloads Ennodia. Bun runs it.
 If the client supports Bun directly, use `bunx ennodia`.
 
-## MCP Configuration
+## MCP configuration
 
 Add this server to the user's MCP client configuration:
 
@@ -70,12 +70,14 @@ For a local Ennodia checkout, use:
 }
 ```
 
+Ennodia loads six core tools by default. For Plan Advisor, compositional slices, raw tasks, and skill installation, add `"--tools", "all"` to `args`. See [tool sets](/docs/reference/mcp-tools/#tool-sets).
+
 The configuration above shows the server command and arguments.
 Adapt its format to the client's documented configuration method.
 Reload the tools or restart the client only when its setup instructions require this step.
 Tell the user which step is needed before trying to call Ennodia.
 
-## Get One Useful Result
+## Get one useful result
 
 After the client exposes Ennodia's tools, start with one small task:
 
@@ -98,7 +100,7 @@ The first run does not require separate planning, budget estimation, or Compare
 These tools remain available for larger tasks.
 See [MCP Tools](/docs/reference/mcp-tools/) for exact parameters and identifiers (IDs).
 
-## Installed Components
+## Installed components
 
 Ennodia is a local MCP server. It lets the user's main agent request help from
 other installed agent CLI programs during the same task.
@@ -123,7 +125,7 @@ answer.
 Tell the user a real run can take minutes. Compare adds two serial model passes
 after the selected child agents finish.
 
-## Example Requests
+## Example requests
 
 Use Ennodia when the user permits more model work to get a better answer than
 one agent usually gives.
@@ -148,7 +150,7 @@ Compare the results before you recommend the final documentation edit.
 Compare is model-led. The user does not normally need to judge the parallel
 answers. The trace remains available for inspection.
 
-## Optional Next Steps
+## Optional next steps
 
 - Use [Budgets and Limits](/docs/guides/budgets-and-limits/) before costly
   parallel runs.

package/docs/reference/controlled-english.md

@@ -3,15 +3,13 @@ title: Controlled English
 description: Ennodia terminology and writing rules for ASD-STE100 Issue 9.
 ---
 
-# Controlled English
-
 Ennodia documentation uses ASD-STE100 Issue 9 as its writing standard.
 This policy applies to the README, documentation, website text, and visible asset text.
 
 Commands, API fields, status values, model IDs, and quoted interface text are data.
 Keep this data exact, even when its text does not use controlled English.
 
-## Writing Rules
+## Writing rules
 
 - Use American English.
 - Use active voice when the agent is known.

package/docs/reference/ennodia-io.md

@@ -57,7 +57,7 @@ Environment variables:
 | `ENNODIA_IO_MAX_REQUEST_BODY_SIZE` | Default request body byte cap. |
 | `ENNODIA_IO_MAX_CONCURRENT_CHAT_COMPLETIONS` | Default in-flight chat completion cap. |
 
-## Security and Browser Access
+## Security and browser access
 
 IO binds to loopback by default and refuses non-loopback hosts unless an API key
 is configured. Bearer tokens are compared with a timing-safe comparison.
@@ -94,7 +94,7 @@ boundary.
 | `GET /v1/models` | Supported | Returns local virtual model IDs for compatible clients. |
 | `POST /v1/chat/completions` | Supported subset | Non-streaming text messages only. Requires a JSON media type. |
 
-## Provider Options
+## Provider options
 
 Use provider options when building a settings screen:
 
@@ -135,7 +135,7 @@ Option statuses:
 
 Add `?includeUnavailable=false` to return only ready options.
 
-## Virtual Models
+## Virtual models
 
 `GET /v1/models` returns local virtual models for OpenAI-compatible clients:
 
@@ -148,7 +148,7 @@ Add `?includeUnavailable=false` to return only ready options.
 Older aliases `ennodia-auto`, `ennodia/auto`, and `ennodia/compare` are accepted
 for compatibility. Prefer `local/*` IDs in new app integrations.
 
-## Chat Completions
+## Chat completions
 
 Minimal request:
 
@@ -234,7 +234,7 @@ HTTP error response:
 - timeout, disappeared run, or start failure -> `502 ennodia_run_error`
 - failed run or run with `cancelled` status -> `502 ennodia_run_failed` plus run metadata
 
-## Library Use
+## Library use
 
 Apps can import the same primitives without running the HTTP server:
 
@@ -249,7 +249,7 @@ const providerOptions = await listAppProviderOptions(core);
 The app stays in control of its settings UI, labels, persistence, and consent
 flow. Ennodia supplies local discovery and execution primitives.
 
-## Smoke Test
+## Smoke test
 
 From a checkout:
 
@@ -260,7 +260,7 @@ bun run io:smoke
 The smoke test starts a local IO server and checks `/health`,
 `/v1/provider-options`, and `/v1/models` without launching child agents.
 
-## Not Implemented
+## Not implemented
 
 IO deliberately rejects or omits: