feat: publish versioned capability contract

[felirami]

Summary

• publish a generated, versioned capability contract for v0.11.2 in Markdown and JSON
• add dated platform and release evidence and link the public contract from the root README
• derive contract versioning from the current release and add drift regression coverage

Exact reviewed state

• Base: fc306b381cb8483ef7a2160af24b42fc1981f24b
• Head: 6e9de0febd002e76c69e80649367a81a8fe13c1d
• Tree: 7fc812985f03982e37cd7ec776692291899bc4e9
• Branch: agent/p2-versioned-capability-contract

Both commits and the required Co-authored-by / Signed-off-by trailers were reconstructed byte-for-byte from independently verified immutable carriers. The remote branch was read after push and resolved to the exact head above.

Verification

• Full Node suite: 423/423 passed
• Full TUI suite with Bun 1.2.21 and OPENTUI_LIBC=musl: 91/91 passed
• Capability contract tests: 5/5 passed
• capabilities:check: passed
• Two generate → check parity cycles: passed with stable generated hashes
• Canonical package: clawfix@0.11.2, 21/21 allowlisted files
• Remediation contracts: 7/7 passed
• Repair validation: 50 scripts, 0 blockers (34 ShellCheck advisories)
• npm audit --omit=dev: 0 vulnerabilities
• git diff --check, exact SHA/tree, scope, trailers, and clean-state checks: passed

An independent safe version-drift probe confirmed the README regression fails with the exact expected v0.11.3 link when release inputs advance.

Residual boundary

Release, platform, and outcome evidence is a dated manual snapshot and must be refreshed for future releases. The version-derived README regression makes stale public discoverability fail closed.

Coordination

• Originating Buzz channel: 4144552c-c494-4754-ab7f-c71be5535de6
• Originating thread: b1d0d8d45c0a1439c8dfe59587b2ad01820fb9ac8ba59b6f481c72b4fef24a68