Roadmap and spec status reconciliation

ROADMAP.md

@@ -1,16 +1,39 @@
 # mockworld — Roadmap
 
-## v0.1
-- Shared engine + 5 built-in mocks (payments, email, exchange, crm, files)
-- One-command run; reset/seed for determinism; fault injection
-- Ships alongside stampede's first finance demos
-
-## v0.2 ✅ (implemented)
-- ✅ Registry + `mockworld add`/`search`/`pack` — index-as-repo, checksum + safety gate
-- ✅ Record-mode — scaffold a runnable mock from an OpenAPI spec
+Released on PyPI as [`mockworld-mcp`](https://pypi.org/project/mockworld-mcp/)
+(0.3.1). See [`CHANGELOG.md`](./CHANGELOG.md) for the full history.
+
+## v0.1 ✅ — engine + built-in mocks
+
+- ✅ Deterministic, LLM-free engine: one-command run, reset/seed, fault injection, per-session isolation
+- ✅ Built-in mocks: `payments`, `crm`, `exchange`, `email`, `files` (+ `hello` example)
+- ✅ MCP over stdio and Streamable HTTP; out-of-band control plane
+
+## v0.2 ✅ — the moat
+
+- ✅ Registry + `mockworld add`/`search`/`pack` — index-as-repo, checksum + safety gate. Public
+  registry live at [swarmproof/mockworld-registry](https://github.com/swarmproof/mockworld-registry)
+  (`weather`, `slack`, `twilio`, `github`, `calendar`)
+- ✅ Record-mode — scaffold a runnable mock from an OpenAPI spec **or** a HAR capture
 - ✅ Mock composition — a "world" = several mocks with a shared identity namespace
 
-## v0.3 ✅ (implemented)
-- ✅ stampede `Target` protocol + a deterministic swarm harness producing an Agent Readiness Report (misuse map)
+## v0.3 ✅ — the ecosystem
+
+- ✅ stampede `Target` protocol + a deterministic swarm harness → an Agent Readiness Report (misuse map)
 - ✅ Scenario snapshots — portable `.mw.json` artifacts (seed + versions + state) with cross-version migration
 - ✅ Contract-verify — `mockworld verify --against <openapi>` for fidelity-drift governance
+
+## Shipped beyond the original roadmap
+
+- ✅ Runtime sandbox for untrusted registry handlers (hardened subprocess isolation)
+- ✅ OTLP trace export; read-only `mockworld://` MCP resources; ambiguous-description variants
+- ✅ `mockworld` pytest fixture; `mockworld new` authoring scaffold; automated PyPI release pipeline
+
+## Open (needs the sibling projects)
+
+- **Deep stampede integration** — `stampede.yaml`-driven runs against a mockworld world, and the joint
+  launch demo. stampede now ships a `TargetAdapter` ABC and hand-coded `crm`/`payments` worlds; a
+  mockworld-backed target would replace those with the whole mock library. Unblocked as of stampede's
+  public release.
+- **Shared trace package** — swap mockworld's trace shim for the shared
+  `agent_reliability_core.trace` schema (the `swarmproof.*` attribute registry stampede publishes).

SPEC.md

@@ -2,6 +2,11 @@
 ### A synthetic internet for agents
 *Companion to stampede · v1.0 spec*
 
+> **Status:** this is the original design spec; it has been implemented and
+> released as [`mockworld-mcp`](https://pypi.org/project/mockworld-mcp/). For
+> current state see [`ROADMAP.md`](./ROADMAP.md) and [`CHANGELOG.md`](./CHANGELOG.md).
+> The roadmap in §3 below describes the original plan (v0.1–v0.3), all now shipped.
+
 > **mockworld** — the localhost for the agent economy. Spin up high-fidelity fake services — a fake Stripe, a fake Gmail, a fake exchange, a fake CRM — as instant MCP servers, so you can build and test agents without touching production, leaking data, or paying for real API calls.
 
 ---

docs/PRD.md

@@ -3,6 +3,11 @@
 *Vision, goals, personas, functional & non-functional requirements, feature tiers, mock-library scope, success metrics.*
 *Companion to `SPEC.md` and `docs/RESEARCH.md`. Author: mockworld architect. Last updated: 2026-07-13.*
 
+> **Status:** the P0/P1 requirements below are implemented and released as
+> `mockworld-mcp`; several P2/P3 items (registry, record-mode, snapshots, sandbox)
+> shipped too. `../ROADMAP.md` and `../CHANGELOG.md` track current state; REQ-IDs
+> remain the stable reference used across the docs.
+
 > **⊕ Beyond original spec** marks requirements that extend the v1.0 `SPEC.md`.
 > Requirement IDs are stable and referenced by `ARCHITECTURE.md`, `DELIVERY-PLAN.md`, and `TEST-PLAN.md`.