mcp-arcade 0.2.0

Eight waves after the 0.1.0 floor. The sentence on the tin still holds: the oracle is the JSON-RPC wire plus the sandbox, and nothing added here grades anything else. The seat is a policy, not a judge; dataset labels come from the wire; the tape is an allowlisted type with no score field. Still 0.x.

• Wave 1 — the harness survives a real server: --framing auto|ndjson|content-length, protocolVersion negotiation, --task / --args, --wrap, --timeout, server requests rejected. Decisions: docs/wave-1.md.
• Wave 2 — Docker is the sandbox: --target docker, one fresh container per atom, image id pinned and drift-checked, /sandbox snapshotted from inside, no host binds by default. Decisions: docs/wave-2.md.
• Wave 3 — mcp-arcade dataset: one JSONL row per atom, labels from the wire, split: proof never trains. Decisions: docs/wave-3.md.
• Wave 4 — the agent seat: --agent ollama:<model>, frozen template hashed onto the receipt, model text dropped before the receipt, no-call is a utility SKIP. Decisions: docs/wave-4.md.
• Wave 5 — protocol.unlisted_call, The Ghost on the Menu: the server answers a name it never listed. Holdout atom. Decisions: docs/wave-5.md.
• Wave 6 — the tape: receipt --timeline, one row per wire event, an allowlisted Tape with no score fields. Three.js unscheduled. Decisions: docs/wave-6.md.
• Wave 7 — the live-fire packet: --wrap-target, --seat-allow, receipts against a real server, a repository test that greps every committed proof for a host path. docs/live-fire.md.
• Wave 8 — mcp-arcade tape: the allowlisted export the cabinets play. The tape can be played as Ghost on the Menu; the game never touches the score.

pip install mcp-arcade==0.2.0. PyPI 1.0.0 remains yanked history; do not use it.

v0.1.0

First public version. A brand-new repo.

Three atoms, a wire oracle, fail-closed --allow-live.
Not 1.0.0.