Correct verifier_version constant in acceptance verification schema

[MerverliPy]

Problem

The accepted v0.2.6 package preserves this constant in schemas/acceptance-verification.schema.json:

"verifier_version": {"const": "0.2.5"}

The v0.2.6 runtime emits verifier_version: "0.2.6" because repo_agent_team.acceptance uses repo_agent_team.__version__.

Impact

The runtime verifier does not load this JSON Schema, so accepted run 20260720T114528Z-97b68fc7, its 27/27 deterministic checks, and its receipt verification are unaffected. However, verifier output from v0.2.6 does not validate against the published acceptance-verification schema as written.

Required fix

1. Update the schema constant to 0.2.6 in a new patch release or explicitly version the schema independently.
2. Add a regression test that validates representative verify_run output against the public schema.
3. Update release notes and MANIFEST.sha256.
4. Run the full 79-test suite, compilation, schema checks, and manifest verification.

Publication boundary

The v0.2.6 public repository preserves the accepted package schema byte-for-byte and documents this mismatch rather than silently changing an accepted artifact.