Align README with MCP trace replay artifacts

[ProfRandom92]

Motivation

• Reflect the repository state after recent MCP trace replay and replay semantic integrity artifacts were added and keep the top-level positioning deterministic and fixture-bound.
• Make the README reviewer-facing and precise about the new mcp_trace_replay fixture family and related committed artifacts without changing any code or artifacts.

Description

• Update the top tagline to: Deterministic replay-integrity validation for compressed MCP-style operational traces.
• Replace the opening positioning sentence with: CompText V7 validates whether compressed operational commitments survive deterministic replay reconstruction in MCP-style agent workflows.
• Add an "Operational commitments" section listing evidence, constraints, blockers, dependencies, recovery paths, tool order, capability boundaries, and governance/policy gates, and add the mcp_trace_replay description with registered contracts tool_call_order_preserved, validation_before_unsafe_action, dependency_chain_preserved, recovery_path_available, and capability_boundary_respected.
• Increase the manifest-registered fixture count wording to "Four manifest-registered operational fixture families", add mcp_trace_replay to the benchmark family list and diagram, and update the Proof artifacts table to include artifacts/mcp_trace_replay_results.json and artifacts/replay_semantic_integrity_results.json while keeping conservative deterministic descriptions.
• Changed files: README.md only.

Testing

• Ran npm run check, which exercised layout, typecheck, validation, build, and the test suite; the command completed successfully.
• Automated tests passed: the test run shows 237 passed and npm run check succeeded.
• Scope note: README-only change; no artifact changes, no fixture changes, no source-code changes, and no workflow or package changes.

---

Codex Task

[gemini-code-assist]

Code Review

This pull request updates the README.md to incorporate the new mcp_trace_replay fixture family, bringing the total number of manifest-registered operational fixture families to four. The changes include updated project descriptions focusing on MCP-style operational traces, a new 'Operational commitments' section, and additions to the artifacts table and Mermaid flowchart. There were no review comments provided, so I have no feedback to offer.