devcouncil 0.2.0 → 0.2.2

package/README.md

@@ -1,346 +1,182 @@
-# DevCouncil: The Gated AI Orchestrator
+# DevCouncil
 
-<p align="center">
-  <img src="https://raw.githubusercontent.com/bharathvbcr/DevCouncil/main/src/devcouncil/assets/devcouncil_logo_premium.png" alt="DevCouncil Logo" width="300">
-</p>
+Code intelligence and verification components for AI development.
 
+[![Website](https://img.shields.io/badge/website-devcouncil.vbcr.dev-10B981?style=flat&logo=safari&logoColor=white)](https://devcouncil.vbcr.dev/)
+[![CI](https://github.com/bharathvbcr/DevCouncil/actions/workflows/ci.yml/badge.svg)](https://github.com/bharathvbcr/DevCouncil/actions/workflows/ci.yml)
+[![npm version](https://img.shields.io/npm/v/devcouncil)](https://www.npmjs.com/package/devcouncil)
 [![License](https://img.shields.io/badge/License-Apache_2.0-blue.svg)](LICENSE)
-[![Python 3.12+](https://img.shields.io/badge/python-3.12+-blue.svg)](https://www.python.org/downloads/)
-[![uv](https://img.shields.io/badge/managed%20by-uv-purple.svg)](https://github.com/astral-sh/uv)
-
-**"DevCouncil should not merely generate code. It should make AI-generated work prove that it satisfied the original intent."**
-
-DevCouncil is a high-integrity command-line orchestration platform for AI-assisted software development. It turns AI implementation from a black-box generation task into a gated engineering workflow where every change is authorized, verified, and traceable back to a requirement.
-
-DevCouncil does not replace coding agents. It sits beside tools like Codex CLI, Gemini CLI, Claude Code, OpenCode, Google Antigravity CLI, Warp/Oz, Cursor, Aider, and bring-your-own prompt-taking CLIs, then owns the plan, task scope, verification loop, repair prompts, and evidence trail.
-
-## Documentation
-
-- [Quickstart](docs/quickstart.md): shortest install-to-first-task path.
-- [Daily workflow](docs/workflow.md): manual sidecar loop, verification, repair, and rollback.
-- [Coding CLI integration](docs/coding-cli-integration.md): Codex, Gemini, Claude Code, OpenCode, Antigravity, Cursor, Aider, MCP, hooks, and automated executors.
-- [Integration tiers](docs/integration-tiers.md): headless executor vs MCP-only vs sidecar definitions.
-- [CLI command reference](docs/cli-reference.md): available `dev` commands.
-- [Architecture](docs/architecture.md): components, artifact graph, state machine, and gated execution.
-- [Executor adapters](docs/executor-adapters.md): manual, coding CLI, native-preview, Mini-SWE, and OpenHands execution paths.
-- [Live review](docs/live-review.md): `dev watch` session review, cards, signals, and blocking behavior.
-- [Model routing](docs/model-routing.md): provider selection, role models, OpenRouter, Vertex AI, Doubleword, and Ollama (local) setup.
-- [Security model](docs/security.md): redaction, permissions, allowlists, and local state.
-- [Project status](docs/project-status.md): current maturity by subsystem.
-- [Roadmap](docs/roadmap.md): planned work.
-
-## Why DevCouncil Exists
-
-Standard AI coding agents are good at producing the happy path, but they often fail in expensive ways when complexity grows:
-
-- **Requirement omission:** agents lose track of original product or PRD constraints across chat turns.
-- **Architecture drift:** agents add dependencies or change design patterns without explicit authorization.
-- **Unverified success:** agents claim tests passed without proving that the new logic was exercised.
-- **Hidden assumptions:** important decisions stay buried in transient chat history instead of durable project artifacts.
-
-**DevCouncil makes evidence, not model confidence, the final authority.**
-
-It creates a persistent **Requirement -> Task -> Diff -> Evidence** graph, blocks completion when evidence is missing, detects unauthorized changes, and produces a final report that can be reviewed like an engineering artifact.
-
-## Quickstart
-
-Run DevCouncil commands in a normal terminal from the root of the repository you want DevCouncil to manage. Do not run these commands inside a coding CLI chat.
 
-Install `uv` first if it is missing:
-
-```powershell
-powershell -ExecutionPolicy ByPass -c "irm https://astral.sh/uv/install.ps1 | iex"
-```
-
-On macOS or Linux:
-
-```bash
-curl -LsSf https://astral.sh/uv/install.sh | sh
-```
-
-Install DevCouncil from npm:
-
-```bash
-npm install -g devcouncil
-devcouncil --help
-dev --help
-```
+<p align="center">
+  <a href="https://devcouncil.vbcr.dev/"><strong>Explore the Interactive Architecture &amp; Code Graph Showcase (devcouncil.vbcr.dev) &rarr;</strong></a>
+</p>
 
-Start the first gated workflow from your target repository:
+> **"DevCouncil should not merely generate code. It should make AI-generated work prove that it satisfied the original intent."**  
+> *Evidence, not model confidence, is the final authority.*
 
-```bash
-cd path/to/your/project
-dev setup
-dev plan "Describe the implementation goal"
-dev tasks
-dev run TASK-001 --executor manual
-dev prompt TASK-001
-dev verify TASK-001
-```
+DevCouncil is **components and modules** for AI-assisted software development. It ships independently installable binaries and libraries — code intelligence (`devmap`), task and lease state (`dcstore`), deterministic verification (`dcverify`), ignore-aware search (`dcgrep`), and a Go host (`devcouncil` / `dev`) — so a harness or an app can take only the pieces it needs and update them one at a time.
 
-On a fresh interactive setup, DevCouncil can configure supported coding CLI integrations immediately; pass `--skip-integrations` if you want to defer that step.
+See [repository input and verification boundaries](docs/SECURITY_BOUNDARIES.md)
+for executable selection, filesystem protections, resource limits, and the
+difference between unavailable evidence and a passing check.
 
-### Run locally on macOS (Apple Silicon + Ollama)
+**Manvi wraps these components** into a coding-agent harness (turn loop, providers, policy, TUI, `manvi serve`). **GitPulse** uses Manvi for policy, workbench, and agent hosting, and DevCouncil components for code intelligence and related analysis. DevCouncil does not replace coding agents; it sits beside Claude Code, Codex, Cursor, and others as selectable modules.
 
-DevCouncil runs fully offline against [Ollama](https://ollama.com) — no API key, no per-token cost. It is Apple-Silicon-aware: `dev setup --provider ollama` sizes the default local model to your Mac's unified memory, and `dev doctor` reports the chip/RAM, pings the Ollama server, and flags a too-small context window.
+---
 
-```bash
-brew install ollama && ollama serve
-ollama pull qwen2.5-coder:32b     # use the size `dev doctor` recommends for your RAM
-export OLLAMA_NUM_CTX=16384       # large planning prompts need a raised context window
-dev setup --provider ollama      # auto-selects the model for your RAM
-```
+## Architecture & Components
 
-See [Model routing → macOS / Apple Silicon](docs/model-routing.md) for the RAM-to-model table.
+DevCouncil's core runtime is a set of standalone, compiled native modules. Each binary is useful on its own, sits on `PATH`, and can be spawned or linked by a host that wants that one job:
 
-Paste only the output from `dev prompt TASK-001` into Codex, Gemini, Claude Code, OpenCode, Antigravity, Warp, Cursor, Aider, or another coding tool. Keep `dev setup`, `dev plan`, `dev run`, and `dev verify` in the terminal at the repository root.
+| Binary | Language | Role & Ownership |
+|--------|----------|------------------|
+| `devcouncil` / `dev` | **Go** | Host orchestrator: Stdio MCP server (`mcp`), multi-host agent integration (`integrate`), engineering skills distribution (`skills`), task verification (`verify`), and devmap forwarding (`map`, `graph`, `ast`). |
+| `devmap` | **Rust** | Code intelligence engine: Language-aware tree-sitter extraction and explicit fallback/coverage reporting, symbol resolution, blast-radius calculation, dead-code analysis, workspace guides (`AGENTS.md`), and DevMap MCP server (`devmap mcp`). |
+| `dcstore` | **Rust** | State & lease store: SQLite-backed task repository, mutual-exclusion leases for concurrent agent building, evidence records, and gap tracking. |
+| `dcverify` | **Rust** | Deterministic verification: Unified-diff parsing, planned file scope classification, anti-laziness/stub gates, test coverage evaluation, and typed `next_actions` repair signals. |
+| `dcgrep` | **Rust** | Code search: Ripgrep-powered ignore-aware search engine with optional trigram indexing (`tgrep-core`). |
 
-For an automated end-to-end run with a supported coding CLI installed:
+### How hosts consume the modules
 
-```bash
-dev e2e "Describe the implementation goal" --executor codex
-dev e2e "Describe the implementation goal" --executor antigravity
-dev e2e "Describe the implementation goal" --executor warp
-dev go "Describe the implementation goal" --executor codex
-```
+- **Manvi** wraps the components: it drives the agent loop, provider routing, policy ladder, and TUI, and reaches each binary over JSON on stdio. A host that wants a harness embeds Manvi rather than reimplementing it.
+- **GitPulse** uses both for their respective jobs: Manvi (`manvi serve`) for policy, workbench, and agent hosting; selected DevCouncil crates and the `devmap` CLI for in-process code intelligence. It does not have to take every module.
+- **Other apps** pick the same way — `devmap` alone, `dcverify` alone, the Go host MCP, or the full set. Updating one module does not require shipping the rest.
 
-`dev e2e` is the explicit one-command integration target for coding agents. It initializes local DevCouncil state if needed, plans the goal, runs each approved task through the selected executor, verifies the resulting diff, and prints the final report. If `--executor` is omitted, DevCouncil uses `execution.default_executor` from `.devcouncil/config.yaml`. `dev go` is kept as a shorter alias for the same flow.
+> [!NOTE]
+> DevCouncil is built entirely as native compiled Go and Rust binaries; legacy Python orchestration has been retired (see [docs/PHASE7_LONG_TAIL.md](docs/PHASE7_LONG_TAIL.md)).
 
-For machine-readable agent handoff, write the final report to a stable file:
+---
 
-```bash
-dev e2e "Describe the implementation goal" --executor codex --agent
-dev e2e "Describe the implementation goal" --executor codex --json --report-file .devcouncil/reports/latest.json
-```
+## Benchmarks: DevMap vs Graphify, Gortex, GitNexus, CodeGraph, and codebase-memory-mcp
+
+Six code-graph tools plus a ripgrep text baseline, measured on **four
+repositories** (595 to 4,335 files, mixing Rust, Go, TypeScript, Python and
+Swift) on one Apple M5 Pro. Every timing is a minimum or median from a
+reproducible run with the raw evidence committed beside it — not a marketing
+estimate. Head-to-head breakdown:
+**[DevMap vs GitNexus, CodeGraph, Graphify, Gortex, and codebase-memory-mcp](docs/devmap/comparison.md)**.
+Full method, caveats, and raw output:
+**[benchmark report](benchmarks/results/competition/20260914-v0.2.2/REPORT.md)**.
+
+**DevMap 0.2.2 was fastest on most of what was measured:** cold indexing and
+unchanged refresh on **all four repositories**, the lowest median in **all six
+symbol-query cells**, and **5/5** source-inspected caller pairs — matched only
+by codebase-memory-mcp.
+
+Detailed table on the 1,098-file DevCouncil corpus, where the correctness and
+query campaign also ran:
+
+| Tool | Cold index | Unchanged refresh | Single-file edit | Definition lookup | Peak RSS | Caller pairs found |
+|---|---:|---:|---:|---:|---:|---:|
+| **DevMap 0.2.2** | **2.012 s** | **0.089 s** | 0.816 s | **9.7 ms** | **678 MiB** | **5/5** |
+| CodeGraph 1.6.0 | 3.294 s | 0.235 s | **0.512 s** | 101–106 ms | 2430 MiB | 3/5 |
+| codebase-memory-mcp 0.10.8 | 9.357 s | 5.726 s | 8.894 s | ~3.94 s | — | **5/5** |
+| Graphify 0.9.59 | 14.989 s | 5.080 s | 4.883 s | 557–572 ms | 3417 MiB | 3/5 |
+| GitNexus 1.6.9 | 33.689 s | 0.699 s | 31.841 s | 792–808 ms | 3355 MiB | 3/5 |
+| Gortex 0.64.3 | 16.5 s to query-ready | — | — | 92–104 ms | — | 4/5 |
+
+**Where DevMap won.** Fastest cold index on all four corpora (**1.6–21×** the
+competitors' time) and fastest unchanged refresh on all four (**2.2–107×**).
+Lowest median in all six query cells — definition lookups at 9.7 ms, **~10×
+faster than CodeGraph** and **~82× faster than GitNexus**. Lowest sampled peak
+memory on three of four corpora. All five source-inspected caller pairs, and a
+clean result on both index-staleness probes.
+
+**Where DevMap lost.** CodeGraph re-indexes a single edited file faster **on
+every corpus** — DevMap takes 1.08× its time on the smallest and **3.61×** on
+GitPulse. That is the one stage where a competitor is consistently ahead.
+DevMap's store is 1.6–2.0× CodeGraph's and 2.8–4.7× Graphify's, and Graphify
+used **less memory than DevMap on the largest repository** (1,458 MB vs
+1,725 MB). Against v0.2.1, unchanged refresh regressed ~12% on the smallest
+corpus.
+
+**What these numbers are not.** Four repositories, one machine, three-to-five
+repetitions, three symbols, and five inspected caller pairs. They do not
+establish general graph accuracy, persistent-MCP latency, or coding-agent task
+success. Tool output scopes differ, so equal latency is not equal analysis.
+DevMap itself reports 106,217 unexplained call-attribution sites on this corpus.
+The report states every limit explicitly and keeps the failures in — including
+GitNexus serving a deleted symbol through two ordinary refreshes until a forced
+rebuild.
 
-`--agent` enables JSON output and writes `.devcouncil/reports/latest.json`. Fresh projects default to manual sidecar mode, so pass an automated executor or set `execution.default_executor` before using `dev e2e` without `--executor`.
+---
 
-See the full [quickstart](docs/quickstart.md) for installation variants, API-key setup, and first-run guidance.
+## Get started
 
-OpenCode and Google Antigravity CLI are built-in executors and MCP integrations:
+Build just DevMap from source, then map a project:
 
 ```bash
-dev integrate opencode --apply
-dev run TASK-001 --executor opencode
-dev agents run TASK-001 --agent opencode --profile default
-dev integrate antigravity --apply
-dev run TASK-001 --executor antigravity
-dev agents run TASK-001 --agent agy --profile default
+git clone https://github.com/bharathvbcr/DevCouncil.git
+cd DevCouncil
+bash scripts/install.sh --only=devmap
+export PATH="$HOME/.local/bin:$PATH"
+
+cd /path/to/your/project
+devmap build --manifest --guides
+devmap paths --json
+devmap status --json
+devmap explore MyFunction --json
 ```
 
-Register any other local CLI that accepts prompts. `dev agents` is the first-class agent hub; `dev integrate cli-agent` remains available for older scripts:
+Git and Rust/Cargo are required. To include the Go host and full analysis suite,
+run `bash scripts/install.sh`; the host needs the toolchain declared in
+[`go.mod`](backend/go_orchestrator/go.mod), currently Go 1.26.6. On Windows use
+`.\scripts\install.ps1 -Components devmap`, or omit `-Components` for the suite.
+The npm package is a lightweight launcher for native binaries, not a bundled
+runtime. [Complete installation guide](docs/quickstart.md).
 
-```bash
-dev agents add myagent --command myagent --arg run --input-mode prompt-file --prompt-arg=--prompt-file --supports-mcp
-dev agents
-dev agents doctor
-dev agents run TASK-001 --agent myagent --profile default
-```
+Use the paths returned by `devmap paths`: new repositories default to `.devmap`,
+existing `.devcouncil` layouts remain supported, and explicit configuration can
+override either. `--guides` requests managed workspace guides separately from
+the map export. Check freshness, coverage gaps and result truncation before
+using graph answers as evidence. If first-time guide creation leaves status
+stale, run `devmap build --manifest` once more to index the new guides.
 
-GEPA prompt-profile optimization is available for the agent hub:
+## Connect an agent
 
 ```bash
-dev agents optimize --agent codex --profile yolo --evals .devcouncil/evals/agent-profile.jsonl --dry-run
-dev agents optimize --agent codex --profile yolo --evals .devcouncil/evals/agent-profile.jsonl --apply
-```
-
-## Feature Set
-
-DevCouncil is an application layer around coding agents. It does not just emit prompts; it owns the workflow state, validates task scope, records evidence, and produces release-style reports.
-
-### Workflow Features
-
-- **Repository onboarding:** `dev setup` initializes `.devcouncil/`, generates the repo map + `AGENTS.md`/`CLAUDE.md` guides, scaffolds applicable engineering skills, runs environment checks, offers integration setup, and prints the next useful commands. Use `--skip-map` / `--skip-skills` to opt out, or `--scaffold-ci` to also write a starter GitHub Actions workflow.
-- **Repository mapping:** `dev map` writes `.devcouncil/repo_map.json`, identifies important files and subsystems, filters generated/temp files, and keeps managed `AGENTS.md` / `CLAUDE.md` workspace guides synchronized. Subsystems, entry points, neighbors, and important surfaces are now inferred generically for **any** repository — grouped from the directory tree and ranked by an import-graph in-degree — so the map (and the structural context it feeds into prompts) is meaningful outside DevCouncil's own tree, not just within it. The map records the git HEAD and tracked-file fingerprint it was built from; when prompts reuse a map that has fallen behind the current code, they flag it as stale (run `dev map` to refresh) rather than silently feeding wrong structure. The map is also generated automatically on first init.
-- **Engineering skills:** `dev skills` lists the bundled skills and shows which apply to the repository; `dev skills scaffold` writes them into `.claude/skills/<name>/SKILL.md`. A merged always-on `core-engineering` skill (think-before-coding, simplicity, surgical changes, goal-driven execution, evidence-grounded communication) plus domain skills (Android, iOS, Windows, web, AI training) that brief the agent on current SDKs, deprecations, and tooling before coding. Applicable skills are also embedded into `dev prompt` output.
-- **CI scaffolding:** `dev scaffold-ci` writes a starter `.github/workflows/devcouncil.yml` derived from the configured test/lint/typecheck commands, filtered to the detected language stack; it never overwrites existing CI unless `--force`.
-- **Planning council:** `dev plan` turns a goal into requirements, acceptance criteria, assumptions, critique findings, and executable tasks.
-- **Task graph:** `dev tasks` and `dev show TASK-001` expose requirement links, acceptance-criterion links, planned files, expected tests, allowed commands, forbidden changes, dependencies, and status. Tasks can declare `depends_on`; the plan gate rejects unknown dependencies and cycles, and `dev go`/`dev e2e` run tasks in topological order and skip a task whose prerequisites didn't complete (rather than letting it fail spuriously and burn its repair budget).
-- **Scoped task prompts:** `dev prompt TASK-001` creates a constrained implementation prompt for sidecar agents, including file scope, verification expectations, and forbidden changes. The prompt now embeds the current (secret-redacted) contents of each planned file with a top-level symbol outline, structural orientation (from the code-review graph when available, otherwise the generated `repo_map.json`), and a **dependents (blast-radius) list** — the files that import each file being changed, from the map's precomputed reverse-import index — so the agent edits in place and keeps call sites working instead of starting blind. A central prompt budget keeps the core (goal/scope/instructions) always present and fits the optional context sections in priority order (file contents > structural > dependents > skills), dropping the lowest-priority ones with an explicit marker rather than overflowing silently.
-- **Execution:** `dev run TASK-001` supports manual sidecar mode, built-in coding CLI executors, external executors, and registered custom CLI agents.
-- **One-command flow:** `dev e2e "goal"` and `dev go "goal"` can initialize state, plan, run approved tasks, verify the diff, and generate a report. With an automated executor the run is now a **closed loop**: a task that fails verification is re-driven through a bounded self-repair loop (a correction manifest is written and the executor re-run) until it verifies or the `execution.max_repair_attempts` budget is spent, with no-progress detection that stops early when the same blocking gaps reappear.
-- **Verification:** `dev verify TASK-001` captures the diff, runs expected evidence commands, checks planned-file compliance, detects orphan changes, flags unplanned dependency edits, scans for secrets, and links evidence to acceptance criteria. An **empty diff can no longer pass** a task that declares files to create or modify (work that committed earlier is still recognized via the task checkpoint), and the result reports the rigor it ran at (`verification_mode` compiled vs coarse, `diff_empty`, `coverage_measured`/`coverage_skipped_reason`) plus a distinct `advisory_actions` list so an agent never mistakes "passed" for "proven." `dev verify` exits non-zero when a task is blocked so shell-driven agents can gate on `$?`.
-- **Repair:** `dev repair` converts blocking gaps into focused follow-up work instead of leaving failures as vague test output.
-- **Rollback:** `dev rollback TASK-001` uses task checkpoints to revert scoped work when a task needs to be backed out.
-- **Reporting:** `dev report` emits a requirements coverage table, evidence summary, blocking gaps, and live-review blockers; JSON and PR-comment paths are available for automation.
-
-### App Surfaces
-
-- **CLI:** `dev` and `devcouncil` expose the same Typer command surface for local terminal workflows.
-- **Agent hub:** `dev agents` lists built-in and custom agents, `dev agents add` registers prompt-taking CLIs, `dev agents doctor` checks wiring, `dev agents run` executes a task through a named agent/profile, and `dev agents optimize` uses GEPA to tune profile preambles from offline eval examples.
-- **Integration hub:** `dev integrate all --apply` configures supported coding CLI and MCP integrations; targeted setup exists for Codex, Gemini, Claude Code, OpenCode, Antigravity, Cursor, Warp/Oz, hooks, and custom CLI agents. `dev integrate check` now reports each client's **enforcement posture** — `pre-action` (a native hook blocks unauthorized writes before they happen) vs `verify-only` (forbidden changes are caught only after the fact by verification) — so the containment guarantee isn't overstated for clients without a pre-action gate.
-- **MCP server:** `dev mcp-server` exposes DevCouncil context and workflow tools over stdio for MCP-capable clients. `devcouncil_verify_task` now runs DevCouncil's strong compiled per-criterion checks when a provider key is configured (falling back to a clearly-labeled `coarse` mode otherwise), refuses to pass on an empty diff, and returns `verification_mode`, `diff_empty`, `coverage_measured`/`coverage_skipped_reason`, and an `advisory_actions` array alongside the blocking `next_actions`. Cheap, re-verify-free read tools — `devcouncil_get_gaps` and `devcouncil_get_next_actions` — let a reconnecting agent resume outstanding work from persisted gaps (which now carry `file`/`line`/`suggested_command`/`acceptance_criterion_id`). Task leases expire on a config-driven TTL so a crashed agent's task frees itself, with `devcouncil_renew_lease` and `devcouncil_list_leases` for long runs and fleet supervision; a partial-unique DB index enforces a single active lease per task, so concurrent checkouts can't both win the writer slot. A pure-MCP agent can now make the change itself through lease-gated write tools — `devcouncil_write_file` and `devcouncil_apply_patch` — which policy-check every target path *before* it lands (out-of-scope, protected, or escaping paths are rejected; a patch with any out-of-scope target is rejected whole, never partially applied), write atomically, and record a `FileChangeEvent` for provenance. The corpus is also browsable as MCP **resources** (`devcouncil://report`, `devcouncil://tasks`, `devcouncil://gaps`, `devcouncil://cards`, `devcouncil://task/{id}`) so a host can read project state without a tool call. `devcouncil_get_task_provenance` then exposes that audit trail — gated file changes, verification runs, diff-coverage evidence, and the latest correction manifest — so what happened on disk is inspectable. The diff↔coverage proof is now also retained across graph reloads (it was previously dropped), so reports and `dev status` reflect whether the changed lines were actually exercised.
-- **Live review:** `dev watch` tracks review cards, signals, blocking feedback, and repair guidance while a session is active.
-- **Trace viewer:** `dev trace tail --follow` streams local DevCouncil trace events for execution, verification, and agent handoff.
-- **Dashboard:** `dev dashboard --open` serves a local status dashboard and opens it in the default browser for project state and live workflow visibility.
-- **Agent-consumable CLI:** machine output for shell-driven agents — `dev prompt --json` (`{ok, task_id, prompt}`), `dev handoff --json` (`{ok, manifest_path, run_id, next_command}` to chain `dev run`), `dev verify` exits non-zero when blocked, and `dev status`/`dev report` accept `--fail-on-blocking` to exit non-zero on outstanding blocking gaps so a loop can gate on `$?`.
-- **Config editor:** `dev config` and `dev config models` inspect/update provider, model, executor, and command configuration.
-- **Artifact tools:** `dev artifacts validate` checks stored graph integrity.
-- **Code intelligence:** `dev lsp inspect` checks optional language-server readiness, and `dev ast match` searches code structurally.
-- **Doctor:** `dev doctor` validates local dependencies, commands, and environment prerequisites before a workflow fails deeper in execution.
-
-### Agent And Executor Support
-
-DevCouncil works with human-in-the-loop sidecar sessions and automated prompt handoff:
-
-- **Manual sidecar:** paste `dev prompt TASK-001` into any agent, then run `dev verify TASK-001`.
-- **Built-in coding CLI adapters:** `codex`, `gemini`, `claude`, `opencode`, `antigravity`, `warp`, `cursor`, `aider`, and aliases such as `codex-cli`, `gemini-cli`, `claude-code`, `opencode-cli`, `antigravity-cli`, `agy`, `agy-cli`, `warp-cli`, `oz`, `cursor-agent`, and `cursor-cli`.
-- **Custom CLI agents:** register any prompt-taking command with stdin, argument, or prompt-file handoff.
-- **Execution profiles:** custom agents can use profiles such as `default`, `yolo`, and `prod` to adjust prompt constraints while DevCouncil still verifies the final diff.
-- **External automated adapters:** `mini`, `openhands`, `native-preview`, and `native` are available when the corresponding local executor is configured.
-- **Hook-aware clients:** `dev integrate hooks --apply` installs write/shell hooks for Codex, Gemini, Claude, Cursor, and OpenCode so DevCouncil policy can block unauthorized actions before verification. The post-task hook can run deterministic verification of the active task and record gaps (enable `execution.verify_on_post_task`; off by default to keep hooks fast). File-write policy uses one shared path normalizer across the hook and task-policy paths that resolves every target and **denies anything outside the project root** (so the path that's checked is the path that's enforced), and the pre-tool-use hook is fail-closed: an unparseable or error payload is surfaced (and blocked under `--strict`/`DEVCOUNCIL_HOOK_STRICT`) rather than silently allowed.
-
-### Gates And Evidence
-
-DevCouncil blocks completion on concrete gaps rather than model confidence:
-
-- **Plan approval gates:** requirements must have acceptance criteria, acceptance criteria need verification methods, tasks must map to known requirements and acceptance criteria, high-impact assumptions must be resolved, and high/critical critique findings must be closed.
-- **Task readiness gates:** the working tree must be clean for the task, planned files must be declared, and each task needs allowed commands plus expected verification evidence.
-- **Diff gates:** verification detects files changed outside the planned task scope, dependency-file edits made without authorization, deleted/added files, and untracked file diffs.
-- **Evidence gates:** passing evidence commands are linked back to acceptance criteria; missing passing evidence becomes a blocking gap.
-- **Security gates:** secret scanning runs over captured diffs, and command output is redacted before it is written to logs.
-- **Live-review gates:** unresolved critical review cards can block task verification and appear in reports.
-
-### Providers, Models, And Cost Tracking
-
-- **Providers:** OpenRouter, Vertex AI, Doubleword, and Ollama (local, no key) are supported through local configuration and secrets.
-- **Role models:** planner, critic, arbiter, reviewer, and repair roles can share one model or use per-role overrides.
-- **Structured repair:** model routing includes JSON repair paths for structured planning and review outputs.
-- **Model defaults:** packaged YAML defaults ship with the tool so installed CLI environments do not depend on source-tree-only files.
-- **Telemetry:** local trace and cost data feed `dev status`, reports, and dashboard surfaces.
-
-### Reports And Automation Outputs
-
-- **Markdown reports:** include verdict, coverage summary, requirement/task mapping, blocking gaps, and live-review status.
-- **JSON reports:** `--json` and `--report-file` support machine-readable handoff to other automation.
-- **Agent preset:** `--agent` writes `.devcouncil/reports/latest.json` for stable downstream consumption.
-- **PR comments:** `dev report --github-pr-comment` and `dev report --gitlab-pr-comment` can publish verification summaries to pull/merge requests.
-- **GitHub checks:** preview GitHub report/check surfaces are available for repository automation.
-
-### Local State And Files
-
-DevCouncil stores local workflow state in the target repository:
-
-- `.devcouncil/config.yaml`: provider, executor, command, integration, and workflow settings.
-- `.devcouncil/secrets.env`: local provider secrets such as API keys or Vertex AI project/location values. Git-ignored; copy `.devcouncil/secrets.env.example` and fill in real values. Environment variables take precedence over this file.
-- `.devcouncil/repo_map.json`: generated repository map and subsystem navigation index.
-- `.devcouncil/state.sqlite`: SQLite state for requirements, assumptions, tasks, evidence, gaps, critique findings, and project phase history.
-- `.devcouncil/checkpoints/`: task snapshots used by verification and rollback.
-- `.devcouncil/logs/`: redacted stdout/stderr from verification commands.
-- `.devcouncil/runs/<run-id>/agent-run.json`: prompt, executor, profile, exit status, and run metadata for automated agent executions.
-- `.devcouncil/reports/latest.json`: optional machine-readable report generated by `dev e2e --agent`.
-- `.devcouncil/integrations/` and `.agents/`: generated integration files such as Warp/Oz MCP JSON and Antigravity MCP config.
-
-### Maturity
-
-The stable daily workflow is planning, manual sidecar execution, verification, repair, rollback, and reporting. Coding CLI executors, MCP, live review, dashboard, PR comments, LSP/AST tools, and GitHub check surfaces are preview features. Native autonomous execution is experimental and still requires DevCouncil verification before work is considered complete.
-
-## Core Flow
-
-DevCouncil's recommended default is **Manual Sidecar Mode**:
-
-1. DevCouncil plans the work and creates a task graph.
-2. You ask DevCouncil for one constrained task prompt.
-3. You paste that prompt into your coding CLI or agent.
-4. The agent edits the repository.
-5. DevCouncil verifies the resulting diff against task constraints.
-6. If verification fails, DevCouncil creates a focused repair loop.
-
-The detailed task-by-task workflow lives in [docs/workflow.md](docs/workflow.md).
-
-## How The Repo Runs
-
-```mermaid
-flowchart TD
-    user["User runs dev/devcouncil"] --> cli["Typer CLI\nsrc/devcouncil/cli/main.py"]
-    cli --> config["Config + secrets\n.devcouncil/config.yaml\n.devcouncil/secrets.env"]
-    cli --> map["Repo map\nsrc/devcouncil/indexing/repo_mapper.py"]
-    cli --> planning["Planning commands\ndev plan / dev prompt / dev tasks"]
-
-    config --> providers["Model providers\nOpenRouter, Vertex AI, Doubleword, or Ollama"]
-    providers --> router["ModelRouter\nrole models, cache, telemetry, structured JSON repair"]
-    router --> planning
-
-    planning --> storage["SQLite + repositories\nrequirements, tasks, gaps, evidence, state"]
-    storage --> artifactGraph["Artifact graph\nRequirement -> Task -> Diff -> Evidence"]
-    artifactGraph --> gates["Gate policy\nplanned files, commands, secret checks"]
-
-    gates --> manual["Manual sidecar\ndev prompt + user agent edits"]
-    gates --> coding["Coding CLI executor\nCodex, Gemini, Claude, OpenCode, Antigravity, Warp, custom CLIs"]
-    gates --> native["Native preview executor\nLLM router + TaskRunner"]
-    gates --> external["Mini-SWE / OpenHands adapters"]
-
-    coding --> runlog["Run artifacts\nprompt file, redacted logs, manifest, trace events"]
-    native --> runlog
-    external --> runlog
-    manual --> diff["Repository diff"]
-    runlog --> diff
-
-    diff --> verify["Verifier\ndev verify / automatic post-run verification"]
-    verify --> evidence["Evidence + gaps"]
-    evidence --> storage
-    evidence --> repair["Repair loop\ndev repair / dev watch repair"]
-    evidence --> report["Reports\ndev report, JSON, GitHub/GitLab comments"]
-
-    cli --> mcp["MCP server\ndev mcp-server"]
-    mcp --> storage
-    mcp --> artifactGraph
-    mcp --> repair
-
-    cli --> live["Live review\ndev watch"]
-    live --> cards["Cards + signals\nblocking review feedback"]
-    cards --> report
+devmap integrate cursor --dry-run
+devmap integrate cursor
+devmap integrate cursor --check
 ```
 
-## Install From Source
+Substitute `claude`, `codex`, `antigravity`, `opencode` or `warp` for `cursor`.
+Integration can update user-level MCP settings as well as project assets.
+Inspect the receipt and complete host reload/trust steps. For task tooling,
+add the Go-host integration described in
+[coding CLI integration](docs/coding-cli-integration.md).
 
-For local development inside this checkout:
-
-```bash
-uv sync
-uv run dev --help
-```
+## Verification is opt-in
 
-For a global install from this repository:
+For an existing task in an initialized `.devcouncil/state.sqlite`:
 
 ```bash
-uv tool install --force .
-dev --help
-devcouncil --help
+devcouncil verify TASK-001 --mode enforce --json
 ```
 
-## Project Shape
-
-DevCouncil implements a 7-phase software-team workflow:
-
-1. Goal analysis and repository mapping.
-2. Requirements drafting.
-3. Council debate and task arbitration.
-4. Gated execution with scoped files and commands.
-5. Deterministic verification.
-6. Repair-loop generation.
-7. Evidence reporting.
-
-Read [docs/architecture.md](docs/architecture.md) for the artifact graph, gating state machine, and component layout.
+Read gate mode, skipped reasons and coverage metadata. The Go host invokes
+`dcverify` for rigor checks; changed-line coverage requires a profile supplied
+through `--coverage PATH`. The default gate mode is `off`. Task leases and MCP
+policy results coordinate participating clients; retired lifecycle hooks do
+not intercept arbitrary shell commands or editor writes. The sandbox selector
+does not implement Docker/Nix isolation. See the
+[task loop contract](docs/hero-loop.md).
 
-## Contributions
-
-Project ideas and execution patterns come from the open-source ecosystem:
-
-- [Sage](https://github.com/usetig/sage): peer-review-first model for planning and critique.
-- [karpathy/llm-council](https://github.com/karpathy/llm-council): for the multi-LLM peer-review pattern.
-- [GPT Pilot](https://github.com/Pythagora-io/gpt-pilot): for role-based software-team concept.
-- [astral-sh/uv](https://github.com/astral-sh/uv): for reproducible Python package/runtime workflows.
-- [OpenHands](https://github.com/All-Hands-AI/OpenHands): for workspace-aware agent execution patterns.
-- [mini-SWE-agent](https://github.com/SWE-agent/mini-swe-agent): for lightweight execution loop inspiration.
-- [SWE-agent](https://github.com/SWE-agent/SWE-agent): for full-spectrum autonomous SWE-style tasking patterns.
-- [GitNexus](https://github.com/abhigyanpatwari/GitNexus): for structural codebase awareness.
-- [graphify](https://github.com/safishamsi/graphify): for knowledge-graph-based coordination concepts.
-
-## License
-
-Licensed under the **Apache License, Version 2.0**. See [LICENSE](LICENSE) for details.
-
----
+## Documentation
 
-**"Trust the model, but verify the graph."**
+Start at the **[documentation index](docs/README.md)**.
+
+| Topic | Guide |
+|---|---|
+| Installation and first query | [Quickstart](docs/quickstart.md) |
+| Components and state ownership | [Architecture](docs/architecture.md) |
+| Symbols, impact and evidence limits | [Code graph](docs/code-graph.md) |
+| Editor setup and hooks | [Integration](docs/coding-cli-integration.md) |
+| Commands and flags | [CLI reference](docs/cli-reference.md) |
+| Task workflow | [Workflow](docs/workflow.md) and [MCP loop](docs/hero-loop.md) |
+| Implementation and migration limits | [Project status](docs/project-status.md) |
+| Native development | [Rust workspace](rust/README.md) |
+
+[Apache 2.0](LICENSE). The Python CLI, its release lineage and its historical
+workflow certifications are retired; current native source and installed
+binary identities must be checked separately.