copper-pilot-cli 0.1.8__tar.gz → 0.1.10__tar.gz

copper_pilot_cli-0.1.10/HISTORY.md

@@ -0,0 +1,420 @@
+Changelog
+=========
+
+
+(unreleased)
+------------
+
+Fix
+~~~
+- Skip the killed-background resume test on Windows. [AdityaNG, Cursor]
+
+  os.killpg is POSIX-only, and that failure was the Windows CI break.
+- Resume the agent when a background shell already exited. [AdityaNG,
+  Cursor]
+
+  The continuation turn only ran while a background command was still alive, so a search that finished during the rest of the turn never woke the agent.
+
+Other
+~~~~~
+- Merge pull request #23 from CopperPilot/feat/acp-image-prompts.
+  [Aditya]
+
+  feat(acp): accept image prompts
+- Feat(acp): accept image prompts. [AdityaNG, Cursor]
+
+  T3 Code refused to start any ACP turn that carried an image because initialize never advertised promptCapabilities.image, and prompt() dropped image blocks anyway. Advertise image support, save each image block under .copperpilot/attachments, pass it as a path-first runtime attachment like the TUI does, and list the saved paths in the query so the agent reads the workspace copy.
+- Merge pull request #22 from CopperPilot/fix/resume-finished-
+  background-shell. [Aditya]
+
+  fix: resume the agent when a background shell already exited
+- Merge pull request #21 from CopperPilot/feat/validate. [Aditya]
+
+  feat: copper-pilot validate, a stage-gated read-only review graph
+- Fix(validate): default reviewers to agent mode and pass Windows CI.
+  [AdityaNG, Cursor]
+
+  Agent mode is the better default for hosted reviewers; the read-only broker still blocks design writes. Windows treated POSIX virtual paths and library URIs as relative, and os.kill(SIGTERM) aborted pytest before it could report.
+- Fix(validate): enforce reviewer.timeout_s and treat SIGTERM like
+  Ctrl-C. [AdityaNG, Claude Fable 5.1]
+
+  A hosted architecture review on a 68-part board outlived an external
+  timeout(1) wrapper; SIGTERM killed the process with no report, and the
+  graph's reviewer.timeout_s had never been applied. Each reviewer slice now
+  runs under asyncio.timeout(reviewer.timeout_s) and times out as an ERROR,
+  and the CLI maps SIGTERM onto the same partial-report path as Ctrl-C.
+- Fix(validate): scope release.repo to the project folder; tolerate
+  markdown escapes in replies. [AdityaNG, Claude Fable 5.1]
+
+  Running validate on a repository that keeps generated boards outside the
+  KiCad project (video/build/tmp_pcbs) counted them as portability failures.
+  The workspace walker now skips the same build/dist/node_modules folders as
+  discover_workspace, and release.repo only scans the project folder.
+
+  A live sch.ratings reviewer wrote '\*' inside JSON strings, which is not a
+  JSON escape and cost a repair turn; invalid escapes are now dropped before
+  the repair path is used.
+- Feat(validate): explain, --context, Python validate() API, and live
+  test. [AdityaNG, Claude Fable 5.1]
+
+  Add copper-pilot validate explain CHECK_ID (config, rendered prompt, input
+  hashes, last result), --context FILE ... (appended to every reviewer prompt
+  under Reference material and folded into the cache key), the
+  copper_pilot_cli.validate.validate()/avalidate() API returning a
+  ValidationReport, and a pytest -m live end-to-end run of validate --until S2
+  on examples/001_esp32.
+- Feat(validate): --json events, --junit, --emit-fix-prompt, MCP
+  validate tool, skill and docs. [AdityaNG, Claude Fable 5.1]
+
+  Stream validate.start/check/result/end events (plus copper.retry pass-through)
+  with --json, write JUnit XML with --junit (FAIL/ERROR -> failure/error,
+  SKIPPED -> skipped naming the blocker, WARN -> system-out), and print a
+  ready fix message for copper-pilot --mode agent with --emit-fix-prompt.
+  Expose validate(workspace?, profile?, gate?, until?, only?, effort?,
+  no_cache?) on the MCP server with per-check progress and the fixed read-only
+  reviewer policy. Add a Validate section to the review skill and plugin,
+  docs/validate.md, and the CLI reference with the exit-code table.
+- Feat(validate): hosted agent reviewers with read-only broker,
+  grounding and consensus. [AdityaNG, Claude Fable 5.1]
+
+  Add the reviewer adapter: each agent check runs CopperPilot in Ask mode
+  against a read-only snapshot of the workspace through a Manual broker whose
+  policy approves reads, scratch-folder writes and non-dangerous shell only.
+  The snapshot is re-hashed after every check; any change outside scratch is
+  an ERROR. Replies must end with a fenced json findings block (two repair
+  turns, then ERROR); findings are grounded against the design index and
+  ungrounded ones can never fail a check. per_part, per_sheet and per_netclass
+  checks fan out in batches, repeat: N takes a majority consensus, and a
+  non-retryable usage-limit block stops scheduling agent checks and exits 4.
+  default.yaml gains the agent checks for S1-S8 and the CLI gains --effort,
+  --concurrency and --repeat.
+- Feat(validate): engine, builtin checks, reports, and validate
+  list|graph|run. [AdityaNG, Claude Fable 5.1]
+
+  Add the copper-pilot validate subcommand: a stage-gated graph of read-only
+  checks loaded from a packaged default.yaml and extended by
+  .copperpilot/validate.yaml. This slice ships the engine (config models and
+  graph validation, design snapshot/hash/index, kicad-cli wrappers, dependency
+  waves, stage/full/strict gating, result cache) with the deterministic builtin
+  checks (intake.tools, intake.project, intake.intent, parts.bom_fields,
+  sch.erc, pcb.parity, pcb.rules, pcb.drc, release.outputs, release.repo) and
+  writes report.json, REPORT.md and next_actions.json under
+  .copperpilot/validate/runs/<id>/ with a latest pointer.
+- Merge pull request #20 from CopperPilot/feat/acp-session-updates.
+  [Aditya]
+
+  feat(acp): usage, plan, subagent, elicitation, and /effort session updates
+- Merge origin/main into feat/acp-session-updates. [AdityaNG, Claude
+  Fable 5.1]
+- Merge pull request #19 from CopperPilot/feat/client-turn-durability.
+  [Aditya]
+
+  feat: make hosted turns durable across transport drops
+- Fix(background): normalize CRLF shell output on Windows. [AdityaNG,
+  Claude Fable 5.1]
+- Feat: make hosted turns durable across transport drops. [AdityaNG,
+  Claude Fable 5.1]
+
+  Port the desktop client's chat-manager resilience into the shared graph
+  node so every front-end (TUI, headless, MCP, ACP) benefits:
+
+  - Retry a dropped stream up to three times with 5/10/20 s backoff and a
+    stitched "Resume where we left off" re-prompt carrying the partial
+    transcript, so the hosted agent continues instead of restarting.
+  - Classify failures like `_categorizeError`: drops, timeouts, 5xx and 429
+    retry; 4xx, invalid/oversized requests, plan refusals and auth fail fast.
+  - Capture the websocket close code and reason in the error message and log,
+    including drops that happen while a tool result is being sent.
+  - Checkpoint partial progress (text, tool calls, results) on a terminal
+    failure or cancellation with a hidden interruption note, so a later
+    manual "continue" has the prior work in context.
+  - Surface retry progress as `copper.retry` events: ACP agent thoughts, TUI
+    status/notification, headless yellow lines, MCP progress.
+  - Honour the desktop foreground-to-background shell contract: commands
+    outliving their timeout keep running, the turn continues, and their
+    output is fed back in a continuation turn after the final frame.
+  - Drop the 300 s idle-frame timeout; websocket keepalive still detects dead
+    peers and long hosted reasoning no longer trips a client limit.
+  - Fix the ACP cancel race where a server close after `session/cancel`
+    surfaced as an error instead of `cancelled`.
+- Fix(acp): read slash commands from the first prompt block. [AdityaNG,
+  Claude Fable 5.1]
+
+  T3 Code appends runtime context as a second text block, so /effort was
+  reaching the hosted agent instead of being answered locally.
+- Fix(acp): elicit option questions, unwrap T3 prompts, bound question
+  waits. [AdityaNG, Claude Fable 5.1]
+
+  T3 Code in Full access auto-selects the first option of a permission prompt,
+  so clarifying questions with options now use form elicitation (enum) when the
+  client supports it. /effort is recognised inside T3's <user_request> envelope.
+  Questions nobody answers within 100 seconds are skipped with a note, because
+  the hosted service drops a turn whose tool result takes longer than two minutes.
+- Feat(acp): usage, plan, subagent, elicitation, and /effort updates.
+  [AdityaNG, Claude Fable 5.1]
+
+  Emit usage_update from hosted token counts so T3 Code's context meter works,
+  project hosted todo_list events and .copperpilot/plans artifacts onto ACP plan
+  entries, render Intelligence survey workers as think tool calls, collect
+  free-text clarifications through ACP form elicitation when the client supports
+  it, and advertise a locally handled /effort command.
+
+
+0.1.9 (2026-10-16)
+------------------
+- Release: version 0.1.9 🚀 [AdityaNG]
+- Merge pull request #18 from CopperPilot/feat/acp-server. [Aditya]
+
+  feat: add `copper-pilot acp` Agent Client Protocol server
+- Fix(acp): surface hosted turn failures in the JSON-RPC error message.
+  [AdityaNG, Claude Fable 5.1]
+
+  T3 Code showed a bare "Internal error" for a prompt the hosted service
+  had refused with "Upgrade to a paid plan to use Intelligence." because the
+  explanation only lived in the error's `data`, which T3 does not display.
+  Carry the hosted message in the error `message` (keeping the code), map a
+  refused websocket handshake to auth_required when it is 401/403, log every
+  failed turn to the diagnostics log, and never let an unexpected exception
+  escape to the SDK's generic handler.
+- Fix(acp): accept `copper-pilot acp auth login` for clients that append
+  login args. [AdityaNG, Claude Fable 5.1]
+
+  T3 Code runs an ACP terminal auth method by appending the method's args to
+  the configured agent command, so the advertised `auth login` was spawned as
+  `copper-pilot acp auth login`. The acp parser rejected the extra arguments
+  with exit code 2 and T3 reported "The provider login command did not finish
+  successfully." Normalize `acp auth ...` onto `auth ...` before parsing and
+  document the alias.
+- Feat: add `copper-pilot acp` Agent Client Protocol server. [AdityaNG,
+  Claude Fable 5.1]
+
+  Serve the hosted CopperPilot agent over ACP stdio so editors such as Zed
+  can drive it with streaming messages, tool calls, permission prompts,
+  session modes (ask/plan/agent), an effort config option, session/load
+  resume of existing threads, and session/cancel.
+
+  - New copper_acp.py built directly on the agent-client-protocol SDK;
+    approvals and clarifying questions map onto session/request_permission.
+  - `acp` optional extra; the command prints an install hint without it.
+  - CI license gate ignores agent-client-protocol (Apache-2.0 LICENSE file,
+    no license metadata in the wheel).
+  - Tests: tests/test_acp.py (100% coverage of copper_acp.py, including a
+    real stdio JSON-RPC round trip), parser and entrypoint tests, and a
+    release-gate check for the extra.
+  - Docs: cli.md, harness.md (Zed setup), README.
+
+
+0.1.8 (2026-10-14)
+------------------
+
+Fix
+~~~
+- Annotate async context managers for ty 0.0.87. [AdityaNG]
+
+  CI resolves the unpinned ty dependency to 0.0.87, which rejects AsyncIterator returns on asynccontextmanager.
+- Upgrade the pinned Deep Agents runtime to 0.7.19. [AdityaNG]
+
+  Keep the exact runtime pin while picking up the filesystem and media-handling fixes from 0.7.14.
+- Align the CLI with hosted usage limits. [AdityaNG]
+
+  Keep blocked turns machine-readable, shrink oversized resumed chats to the desktop frame budget, and report the installed client version.
+
+Other
+~~~~~
+- Release: version 0.1.8 🚀 [AdityaNG]
+- Merge pull request #16 from CopperPilot/update/14_oct_2026. [Aditya]
+
+  Add Intelligence effort, hosted survey workers, and modal keyboard focus
+- Fix(tests/test_tui.py) [AdityaNG]
+- Feat(src/copper_pilot_cli/copper_status_events.py) [AdityaNG]
+- Merge pull request #3 from
+  CopperPilot/dependabot/github_actions/softprops/action-gh-release-3.
+  [Aditya]
+
+  build(deps): bump softprops/action-gh-release from 2 to 3
+- Build(deps): bump softprops/action-gh-release from 2 to 3.
+  [dependabot[bot]]
+
+  Bumps [softprops/action-gh-release](https://github.com/softprops/action-gh-release) from 2 to 3.
+  - [Release notes](https://github.com/softprops/action-gh-release/releases)
+  - [Changelog](https://github.com/softprops/action-gh-release/blob/master/CHANGELOG.md)
+  - [Commits](https://github.com/softprops/action-gh-release/compare/v2...v3)
+
+  ---
+  updated-dependencies:
+  - dependency-name: softprops/action-gh-release
+    dependency-version: '3'
+    dependency-type: direct:production
+    update-type: version-update:semver-major
+  ...
+- Merge pull request #4 from CopperPilot/dependabot/pip/websockets-
+  gte-15-and-lt-18. [Aditya]
+
+  build(deps): update websockets requirement from <17,>=15 to >=15,<18
+- Build(deps): update websockets requirement from <17,>=15 to >=15,<18.
+  [dependabot[bot]]
+
+  Updates the requirements on [websockets](https://github.com/python-websockets/websockets) to permit the latest version.
+  - [Release notes](https://github.com/python-websockets/websockets/releases)
+  - [Commits](https://github.com/python-websockets/websockets/compare/15.0...17.1)
+
+  ---
+  updated-dependencies:
+  - dependency-name: websockets
+    dependency-version: '17.1'
+    dependency-type: direct:production
+  ...
+- Merge pull request #5 from CopperPilot/dependabot/pip/uuid-utils-
+  gte-0.12-and-lt-2. [Aditya]
+
+  build(deps): update uuid-utils requirement from <1,>=0.12 to >=0.12,<2
+- Build(deps): update uuid-utils requirement from <1,>=0.12 to
+  >=0.12,<2. [dependabot[bot]]
+
+  Updates the requirements on [uuid-utils](https://github.com/aminalaee/uuid-utils) to permit the latest version.
+  - [Release notes](https://github.com/aminalaee/uuid-utils/releases)
+  - [Commits](https://github.com/aminalaee/uuid-utils/compare/0.12.0...1.0.0)
+
+  ---
+  updated-dependencies:
+  - dependency-name: uuid-utils
+    dependency-version: 1.0.0
+    dependency-type: direct:production
+  ...
+- Merge pull request #2 from
+  CopperPilot/dependabot/github_actions/actions/setup-python-7. [Aditya]
+
+  build(deps): bump actions/setup-python from 5 to 7
+- Build(deps): bump actions/setup-python from 5 to 7. [dependabot[bot]]
+
+  Bumps [actions/setup-python](https://github.com/actions/setup-python) from 5 to 7.
+  - [Release notes](https://github.com/actions/setup-python/releases)
+  - [Commits](https://github.com/actions/setup-python/compare/v5...v7)
+
+  ---
+  updated-dependencies:
+  - dependency-name: actions/setup-python
+    dependency-version: '7'
+    dependency-type: direct:production
+    update-type: version-update:semver-major
+  ...
+- Merge pull request #13 from
+  CopperPilot/update/deepagents_0_7_19_3_oct. [Aditya]
+
+  Upgrade the pinned Deep Agents runtime to 0.7.19
+- Merge pull request #1 from
+  CopperPilot/dependabot/github_actions/actions/checkout-7. [Aditya]
+
+  build(deps): bump actions/checkout from 4 to 7
+- Build(deps): bump actions/checkout from 4 to 7. [dependabot[bot]]
+
+  Bumps [actions/checkout](https://github.com/actions/checkout) from 4 to 7.
+  - [Release notes](https://github.com/actions/checkout/releases)
+  - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md)
+  - [Commits](https://github.com/actions/checkout/compare/v4...v7)
+
+  ---
+  updated-dependencies:
+  - dependency-name: actions/checkout
+    dependency-version: '7'
+    dependency-type: direct:production
+    update-type: version-update:semver-major
+  ...
+- Merge pull request #12 from
+  CopperPilot/update/contract_alignment_3_oct. [Aditya]
+
+  Align the CLI with hosted usage limits
+
+
+0.1.7 (2026-10-03)
+------------------
+- Release: version 0.1.7 🚀 [AdityaNG]
+- Merge pull request #11 from
+  CopperPilot/feat/python_versions_support_expansion. [Aditya]
+
+  Support Python 3.11 and future releases
+- Ci: probe Python 3.15 weekly instead of on pull requests. [AdityaNG]
+
+  Keep the upstream install failure visible without turning required pull request checks red.
+- Feat(py11) [AdityaNG]
+- Merge pull request #7 from CopperPilot/feat/example_002_cm5_camera.
+  [Aditya]
+
+  feat(examples/002_cm5_camera): add 3D pose audit and generated carrier
+- Fix(examples/002_cm5_camera): render the README PCB as a dimetric 3D
+  view. [AdityaNG, Cursor]
+
+  Use an orthogonal high-quality camera with a slight isometric tilt so the
+  hero PNG shows connector height instead of a flat top-down shot.
+- Fix(examples/002_cm5_camera): skip library dirs relative to the
+  workspace. [AdityaNG, Cursor]
+
+  Absolute path parts named tmp (Linux /tmp pytest roots) were skipping the
+  entire haystack, so libraries_ready failed on Ubuntu CI.
+- Feat(examples/002_cm5_camera): add 3D pose audit and generated
+  carrier. [AdityaNG, Cursor]
+
+  Lock connector 3D offsets, Module1 pad orientation, and the generated
+  KiCad project so the example reproduces NANO-C assembly parity.
+- Feat(examples/002_cm5_camera/main.py): new example. [AdityaNG]
+
+
+0.1.6 (2026-09-18)
+------------------
+- Release: version 0.1.6 🚀 [AdityaNG]
+- Merge pull request #6 from CopperPilot/feat/plugins. [Aditya]
+
+  feat: add MCP conductor and Claude Code plugin
+- Clarify server restrictions in PR template. [Aditya]
+
+  Updated checklist item to clarify server restrictions.
+- Feat: add MCP conductor and Claude Code plugin. [AdityaNG, Cursor]
+
+  Let Claude Code, Cursor, and Codex delegate electronics work to the hosted agent via copper-pilot mcp, a portable review skill, and an in-repo plugin.
+
+
+0.1.5 (2026-09-17)
+------------------
+- Release: version 0.1.5 🚀 [AdityaNG]
+- Fix(README.md) [AdityaNG]
+
+
+0.1.4 (2026-09-17)
+------------------
+- Release: version 0.1.4 🚀 [AdityaNG]
+- Fix(tests/test_release_gates.py) [AdityaNG]
+
+
+0.1.3 (2026-09-17)
+------------------
+- Release: version 0.1.3 🚀 [AdityaNG]
+- Docs. [AdityaNG]
+
+
+0.1.2 (2026-09-17)
+------------------
+- Release: version 0.1.2 🚀 [AdityaNG]
+- Ci(pyproject.toml) [AdityaNG]
+- Fix(tests/test_tui.py) [AdityaNG]
+
+
+0.1.1 (2026-09-17)
+------------------
+- Release: version 0.1.1 🚀 [AdityaNG]
+
+
+0.1.0 (2026-09-17)
+------------------
+- Release: version 0.1.0 🚀 [AdityaNG]
+- Fix(tests/test_release_gates.py) [AdityaNG]
+- Test. [AdityaNG]
+- Docs. [AdityaNG]
+- Docs. [AdityaNG]
+- Example(examples/001_esp32/) [AdityaNG]
+- Makefile. [AdityaNG]
+- Ci. [AdityaNG]
+- Docs. [AdityaNG]
+- Refactor(name) [AdityaNG]
+- Init. [AdityaNG]
+
+

{copper_pilot_cli-0.1.8 → copper_pilot_cli-0.1.10}/PKG-INFO

@@ -1,6 +1,6 @@
 Metadata-Version: 2.5
 Name: copper-pilot-cli
-Version: 0.1.8
+Version: 0.1.10
 Summary: CopperPilot hosted agent for the terminal and LangChain
 Project-URL: Homepage, https://copperpilot.ai
 Project-URL: Repository, https://github.com/CopperPilot/copper-pilot-cli
@@ -37,7 +37,10 @@ Requires-Dist: rich<16,>=15
 Requires-Dist: textual<9,>=8.2.8
 Requires-Dist: uuid-utils<2,>=0.12
 Requires-Dist: websockets<18,>=15
+Provides-Extra: acp
+Requires-Dist: agent-client-protocol<1,>=0.12; extra == 'acp'
 Provides-Extra: dev
+Requires-Dist: agent-client-protocol<1,>=0.12; extra == 'dev'
 Requires-Dist: build<2,>=1.4; extra == 'dev'
 Requires-Dist: gitchangelog==3.0.4; extra == 'dev'
 Requires-Dist: pip-audit<3,>=2.10; extra == 'dev'
@@ -119,6 +122,22 @@ Balanced effort is the default. Paid-plan users can select Intelligence with
 server-owned survey subagents and shows their lifecycle through the existing
 Deep Agents task rows; Intelligence Plan turns survey before writing a plan.
 
+## Validate
+
+```console
+copper-pilot validate ./my-board
+```
+
+Runs a stage-gated graph of read-only reviewers over the KiCad workspace:
+`kicad-cli` checks (ERC, DRC, schematic parity, board rules, Gerbers) plus
+hosted Agent-mode reviewers, each scoped to one concern, in the order a hardware
+engineer reviews a board. It never edits design files. The verdict, a
+`REPORT.md`, and `next_actions.json` (only the earliest failing stage, worst
+first) land in `.copperpilot/validate/latest/`; `--emit-fix-prompt` prints a
+ready message for `copper-pilot --mode agent`. Exit codes: 0 pass, 1 fail,
+2 config error, 3 incomplete, 4 not logged in or usage limit. See
+[docs/validate.md](docs/validate.md).
+
 ## Use from Claude Code, Cursor, or Codex
 
 CopperPilot stays the electronics agent. Copy
@@ -136,9 +155,11 @@ Claude Code can also install the in-repo plugin:
 /plugin install copper-pilot
 ```
 
-That plugin starts `copper-pilot mcp` and adds `@copper-pilot` plus
-`/copper-pilot-review`. Setup for Cursor, Codex, and approvals:
-[docs/harness.md](docs/harness.md).
+That plugin starts `copper-pilot mcp` (tools `status`, `ask`, `plan`, `run`,
+`resume`, `threads_list`, `validate`) and adds `@copper-pilot` plus
+`/copper-pilot-review`. Editors that speak the Agent Client Protocol, such as
+Zed, can run `copper-pilot acp` after `pip install "copper-pilot-cli[acp]"`.
+Setup for Cursor, Codex, Zed, and approvals: [docs/harness.md](docs/harness.md).
 
 ## Configuration
 
@@ -197,7 +218,8 @@ normalizes hosted tool names, approval decisions, and result envelopes.
 Computer use, model/provider selection, local model execution, LangSmith
 tracing, content telemetry, MCP **host**/plugin-runtime controls, and server
 implementation code are not part of this package. A thin MCP **server**
-(`copper-pilot mcp`) that delegates to the hosted agent is.
+(`copper-pilot mcp`) and an ACP **server** (`copper-pilot acp`) that delegate
+to the hosted agent are.
 
 See [UPSTREAM.md](UPSTREAM.md) and [NOTICE](NOTICE) for the retained Textual
 client attribution.

{copper_pilot_cli-0.1.8 → copper_pilot_cli-0.1.10}/README.md

@@ -68,6 +68,22 @@ Balanced effort is the default. Paid-plan users can select Intelligence with
 server-owned survey subagents and shows their lifecycle through the existing
 Deep Agents task rows; Intelligence Plan turns survey before writing a plan.
 
+## Validate
+
+```console
+copper-pilot validate ./my-board
+```
+
+Runs a stage-gated graph of read-only reviewers over the KiCad workspace:
+`kicad-cli` checks (ERC, DRC, schematic parity, board rules, Gerbers) plus
+hosted Agent-mode reviewers, each scoped to one concern, in the order a hardware
+engineer reviews a board. It never edits design files. The verdict, a
+`REPORT.md`, and `next_actions.json` (only the earliest failing stage, worst
+first) land in `.copperpilot/validate/latest/`; `--emit-fix-prompt` prints a
+ready message for `copper-pilot --mode agent`. Exit codes: 0 pass, 1 fail,
+2 config error, 3 incomplete, 4 not logged in or usage limit. See
+[docs/validate.md](docs/validate.md).
+
 ## Use from Claude Code, Cursor, or Codex
 
 CopperPilot stays the electronics agent. Copy
@@ -85,9 +101,11 @@ Claude Code can also install the in-repo plugin:
 /plugin install copper-pilot
 ```
 
-That plugin starts `copper-pilot mcp` and adds `@copper-pilot` plus
-`/copper-pilot-review`. Setup for Cursor, Codex, and approvals:
-[docs/harness.md](docs/harness.md).
+That plugin starts `copper-pilot mcp` (tools `status`, `ask`, `plan`, `run`,
+`resume`, `threads_list`, `validate`) and adds `@copper-pilot` plus
+`/copper-pilot-review`. Editors that speak the Agent Client Protocol, such as
+Zed, can run `copper-pilot acp` after `pip install "copper-pilot-cli[acp]"`.
+Setup for Cursor, Codex, Zed, and approvals: [docs/harness.md](docs/harness.md).
 
 ## Configuration
 
@@ -146,7 +164,8 @@ normalizes hosted tool names, approval decisions, and result envelopes.
 Computer use, model/provider selection, local model execution, LangSmith
 tracing, content telemetry, MCP **host**/plugin-runtime controls, and server
 implementation code are not part of this package. A thin MCP **server**
-(`copper-pilot mcp`) that delegates to the hosted agent is.
+(`copper-pilot mcp`) and an ACP **server** (`copper-pilot acp`) that delegate
+to the hosted agent are.
 
 See [UPSTREAM.md](UPSTREAM.md) and [NOTICE](NOTICE) for the retained Textual
 client attribution.

copper_pilot_cli-0.1.10/VERSION

@@ -0,0 +1 @@
+0.1.10

{copper_pilot_cli-0.1.8 → copper_pilot_cli-0.1.10}/docs/cli.md

@@ -7,6 +7,8 @@ copper-pilot --help
 copper-pilot auth --help
 copper-pilot threads --help
 copper-pilot mcp --help
+copper-pilot acp --help
+copper-pilot validate --help
 ```
 
 Python 3.11 or newer is required. Install with `pip install copper-pilot-cli`.
@@ -49,6 +51,39 @@ Headless mode is also used when `--message` is set and stdout is not a TTY.
 With `--json --no-stream`, the document includes `thread_id` so a later run can
 pass `--resume`.
 
+## Validate
+
+```console
+copper-pilot validate [workspace] [--profile dev|release] [--gate stage|full|strict]
+                      [--until STAGE] [--only ID,...] [--skip ID,...] [--json] [--junit PATH]
+copper-pilot validate list|graph [workspace]
+copper-pilot validate explain CHECK_ID [workspace]
+```
+
+Runs a stage-gated graph of read-only reviewers: `kicad-cli` checks (ERC,
+DRC, parity, rules, Gerbers) and hosted Agent-mode reviewers scoped to one
+concern each, in the order a hardware engineer reviews (intake, architecture,
+parts, schematic, netlist-to-layout, placement, routing, DFM/DFA, release).
+It never modifies design files. Outputs land in `.copperpilot/validate/latest/`:
+`report.json`, `REPORT.md`, and `next_actions.json` (only the earliest failing
+stage, worst first). Uses the stored credential; never opens a browser.
+
+| Code | Meaning |
+|------|---------|
+| 0 | PASS: every selected check is PASS or WARN |
+| 1 | FAIL: at least one blocking FAIL or ERROR |
+| 2 | Usage or config error: bad flags, invalid YAML, a dependency cycle |
+| 3 | INCOMPLETE: no failures, but checks were SKIPPED because of `--gate`, `--until` or `--only` |
+| 4 | Environment: not logged in, or a usage-limit block |
+
+```console
+copper-pilot validate ./my-board --json --gate stage
+copper-pilot validate ./my-board --until S3 --emit-fix-prompt
+copper-pilot validate ./my-board --profile release --gate full --junit validate.xml
+```
+
+Flags, config, the default graph and the fix loop: [validate.md](validate.md).
+
 ## MCP
 
 ```console
@@ -67,10 +102,50 @@ write to stdout; the protocol owns it.
 | `run` | `--mode agent`. Optional `effort`; `approval` is `auto` (default) or `yolo`. |
 | `resume` | Continue `thread_id`. Optional `mode`, `effort`, and the same approval as `run`. |
 | `threads_list` | List threads for this workspace (`limit`, `all_workspaces`). |
+| `validate` | Read-only stage-gated review; returns `verdict`, `exit_code`, `report_path`, `next_actions`. |
 
 Workspace is the tool argument, else `CLAUDE_PROJECT_DIR`, else the process
 current directory. Manual approval is TUI-only. See [harness.md](harness.md).
 
+## ACP
+
+```console
+pip install "copper-pilot-cli[acp]"
+copper-pilot acp
+```
+
+Serves the Agent Client Protocol over stdio for editors such as Zed. The
+`acp` extra is optional; without it the command prints an install hint and
+exits with status 2. `copper-pilot acp auth login` is accepted as an alias for
+`copper-pilot auth login`, because some ACP clients (T3 Code) run the
+advertised login method by appending its arguments to the agent command. One ACP session is one CopperPilot thread, and the
+session `cwd` is the workspace. Uses the stored device-login credential and
+advertises a terminal auth method that runs `copper-pilot auth login`.
+
+| ACP feature | CopperPilot behavior |
+|-------------|----------------------|
+| Session modes | `ask`, `plan`, `agent` (default `agent`) |
+| Config options | `mode` and `effort` (`balanced` default, `intelligence` paid) |
+| `session/load` | Resumes an existing thread id and replays its history |
+| `session/request_permission` | Auto approval; non-routine writes and shell prompt the editor |
+| `elicitation/create` | Clarifying questions (options or free text) when the client advertises form elicitation |
+| `session/cancel` | Cancels the hosted turn and local tools |
+| `usage_update` | Prompt tokens of the latest hosted turn; window size is unknown (0) |
+| `plan` | Hosted todo list events and `.copperpilot/plans/*.plan.md` todos |
+| `available_commands_update` | `/effort balanced\|intelligence`, answered locally |
+
+"Allow all for this session" switches that session to YOLO until the server
+exits; it is never saved. Clarifying questions use ACP form elicitation when
+the client supports it (T3 Code does): options become an enum, free text a
+string field. Without form elicitation, option questions are shown as
+permission choices plus Skip and free-text questions are declined with a
+message to continue in the TUI. A question nobody answers within 100 seconds
+is skipped with a note asking the model to repeat it in its reply, because the
+hosted service drops a turn whose tool result takes longer than two minutes.
+Intelligence survey workers appear as `think` tool calls named
+`Survey: <task>` whose status and output track the worker.
+See [harness.md](harness.md).
+
 ## Effort and Intelligence
 
 Balanced is the default. Intelligence is available on paid plans and lets the
@@ -138,6 +213,38 @@ searches run freely. Writes, edits, deletes, and shell commands are gated:
 
 `--yolo` wins over `--auto-approve`. Saved preferences never enable YOLO.
 
+## Turn durability
+
+Every front-end (TUI, headless, MCP, ACP) runs a hosted turn through the same
+checkpointed graph node, which mirrors the desktop client's chat manager:
+
+- A stream that drops before the final frame (socket close, timeout, 5xx, 429)
+  is retried up to three times with 5 s, 10 s, and 20 s backoff. The retry
+  re-prompts the hosted agent with the partial transcript and
+  `Resume where we left off: <original message>` so it continues rather than
+  restarting. Deterministic failures (4xx other than 429, invalid or oversized
+  requests, plan refusals, auth) fail immediately.
+- Retry progress is visible: the TUI status bar and a notification, a yellow
+  line in headless text mode, MCP progress, and ACP agent thoughts
+  (`Retrying (1/2) in 5s: …`). `--json` emits `copper.retry` events.
+- The websocket close code and reason are carried into the error message
+  (`close code 1011 received: …`) and the log file.
+- Whatever a failed turn produced before the error (assistant text, tool calls
+  and results) is still checkpointed with a hidden
+  `[Turn interrupted before completion: …]` note, so a later "continue" has the
+  prior work in context.
+- There is no idle timeout between frames once a turn is streaming; websocket
+  keepalive still detects dead peers, and long hosted reasoning or subagent
+  runs no longer trip a client-side limit. The first frame must still arrive
+  within 60 s.
+- Shell commands run in the foreground for the requested timeout (default
+  25 s) and then move to the background unless the request sets
+  `kill_on_timeout` or `background: false`. After the final frame the client
+  resumes the agent with their output. Commands still running are awaited
+  first. Commands that already exited while the model was still working are
+  delivered too, so a search that finishes mid-turn is not dropped. Output is
+  capped at 5 MB and the whole process tree is killed on cancel.
+
 ## Usage limits
 
 The hosted service owns weekly and window usage. The CLI does not show raw