feat: update tests and docs

Author: rober-m

CLAUDE.md

@@ -6,7 +6,7 @@ This file provides guidance to Claude Code (claude.ai/code) when working with co
 
 `cardano-init` is a Rust CLI tool that scaffolds Cardano protocol projects. Users select tools for each functional role (on-chain, off-chain, infrastructure, devnet, formal-methods) and the CLI generates a working monorepo. The authoritative docs live in `docs/`: read `docs/PRD.md` (product), `docs/ARCHITECTURE.md` (system design), and `docs/TECH_SPEC.md` (contracts, schemas, edge cases) before making any significant changes; `docs/ADDING_A_TOOL.md` is the contributor guide and `docs/ROADMAP.md` is the milestone plan.
 
-It's an early prototype: several capabilities (the dependency `doctor`, `list` / `--format json`, a hosted web builder) are **planned, not yet implemented**. `docs/ROADMAP.md` tracks what's real vs. upcoming.
+It's an early prototype: the dependency `doctor`, `list`, and `--format json` are implemented, while a few capabilities (a *hosted* web builder, WASM live preview, min-version checks) remain **planned, not yet implemented**. `docs/ROADMAP.md` tracks what's real vs. upcoming.
 
 ## Commands
 
@@ -36,7 +36,7 @@ The codebase is a single Rust crate. The module structure is as follows (see `do
 - `src/registry/`: deserializes embedded TOML tool definitions into typed structs. The `Role` enum (5 roles) is the sole source of truth for the role vocabulary; the registry only *references* roles.
 - `src/scaffold/`: four-phase pipeline: context building → planning → rendering → writing.
 - `src/web/`: impure edge: hand-rolled local web builder server.
-- `src/doctor/`: **(planned)** dependency detection + install advice.
+- `src/doctor/`: dependency detection + install advice.
 - `src/contract.rs`: constants for the interface contract (canonical paths, env var names, role dirs).
 
 **Key invariant:** `registry/`, `scaffold/`, `contract`, and the pure part of `doctor/` have zero dependency on `cli/` or `web/` (the impure edges). They are pure logic over data.
@@ -50,7 +50,7 @@ The codebase is a single Rust crate. The module structure is as follows (see `do
 
 ### Registry and templates
 
-Tool definitions live in `registry/tools/<tool>.toml`. Templates live in `templates/<tool>/<role>/` with a `manifest.toml` listing files. Both are embedded into the binary at compile time via **rust-embed** (`#[folder = "…"]`). There is **no `build.rs`**. (Dependency install recipes will live in `registry/deps.toml`, consumed by the planned `doctor`, see `docs/TECH_SPEC.md` §9.)
+Tool definitions live in `registry/tools/<tool>.toml`. Templates live in `templates/<tool>/<role>/` with a `manifest.toml` listing files. Both are embedded into the binary at compile time via **rust-embed** (`#[folder = "…"]`). There is **no `build.rs`**. (Dependency install recipes live in `registry/deps.toml`, consumed by `doctor`, see `docs/TECH_SPEC.md` §9.)
 
 The **interface contract** (`contract.rs`) is what enables any on-chain tool to compose with any off-chain tool without per-pair logic:
 - On-chain templates must produce `blueprint/plutus.json` during `build`.

README.md

@@ -95,7 +95,7 @@ Early prototype. Tools currently in the registry (✅ available · ⬜ planned).
 | **`cardano-up`** | Provisions & runs Cardano infrastructure (node, indexers, devnets) | Ongoing, per environment |
 
 
-These sit at different layers: `cardano-init` decides *what tools your project uses and how they compose*, while `aikup` / `cardano-up` install and manage *the toolchains and infrastructure those tools need*. The two meet at the (planned) dependency [`doctor`](docs/ROADMAP.md): when toolchains are missing, `cardano-init` advises the right installer (`aikup` for Aiken, `cardano-up` for the infrastructure role) rather than reinventing them.
+These sit at different layers: `cardano-init` decides *what tools your project uses and how they compose*, while `aikup` / `cardano-up` install and manage *the toolchains and infrastructure those tools need*. The two meet at the dependency [`doctor`](docs/ROADMAP.md): when toolchains are missing, `cardano-init` advises the right installer (`aikup` for Aiken, `cardano-up` for the infrastructure role) rather than reinventing them.
 
 By design, `cardano-init` is **not** a package or version manager: it does not pin or upgrade tool versions, manage dependencies after generation, or migrate existing projects. There is no `cardano-init update`.
 

docs/ROADMAP.md

@@ -39,8 +39,8 @@ Deliverables below are tracked as checklists (`[ ]` = not yet done).
 
 **Feature surface:**
 - [ ] Interactive CLI and one-shot CLI (polish; deterministic output).
-- [ ] `list` subcommand + global `--format human|json` presenter + machine-readable error codes (agent surface, PRD FR-13/14/15).
-- [ ] **`cardano-init doctor`** standalone command + check-and-advise during scaffolding (deps/installer graph, `registry/deps.toml`). *(Pulled earlier than the docs' original deferral.)*
+- [x] `list` subcommand + global `--format human|json` presenter + machine-readable error codes (agent surface, PRD FR-13/14/15).
+- [x] **`cardano-init doctor`** standalone command + check-and-advise during scaffolding (deps/installer graph, `registry/deps.toml`). *(Pulled earlier than the docs' original deferral.)*
 - [ ] Local web builder (`cardano-init web`), `--dry-run`, optional Nix flake.
 - [ ] Determinism canonicalization (planner) + snapshot tests + contract-compliance tests per template.
 

src/cli/oneshot.rs

@@ -250,14 +250,12 @@ mod tests {
     }
 
     #[test]
-    #[ignore = "no infrastructure tool in the registry to exercise infra dedup; \
-                re-enable (and swap the tool id) once one is added"]
     fn duplicate_infra_is_deduplicated() {
         let sel = build_selection(
             "test",
             None,
             None,
-            &["yaci".to_string(), "yaci".to_string()],
+            &["kupo".to_string(), "kupo".to_string()],
             None,
             None,
             "preview",