ResiliReplay v0.4.0 — Adopt: configuration to recovery CI

[aliengineering-byte]

ResiliReplay v0.4.0 — Adopt is now public. The release tests a narrow hypothesis: MCP maintainers need a shorter path from an existing Inspector-compatible configuration to reviewed deterministic recovery CI.

npx --yes resilireplay@0.4.0 demo
npx --yes resilireplay@0.4.0 adopt --config ./mcp.json --dry-run
npx --yes resilireplay@0.4.0 adopt --config ./mcp.json

The zero-configuration public-package demo completed in 239 ms in final verification. A real local stdio adoption completed in 783 ms, generated 14 commit-ready artifacts, executed its regression, and passed clean, recovered tool-error, timeout-negative, and safety-negative campaign scenarios.

Generated CI uses the immutable Action reference:

- uses: aliengineering-byte/resilireplay@v0.4.0

The external Ubuntu/Windows × Node 22/24 matrix is green. Adoption dry-run starts no process, opens no network connection, calls no tool, and writes no project file. Real adoption still requires explicit target, tool/argument, and duplicate-retry safety review; tool annotations are treated as untrusted hints.

• Release and evidence
• Adoption guide
• Public package

ResiliReplay is defensive test software, not an OS sandbox, vulnerability claim, or security certification. Audit only local or user-owned targets.

If you maintain an MCP server, which bounded failure boundary would make the most useful first repository-owned recovery fixture?