Bug type

Behavior bug (incorrect output/state without crash)

Beta release blocker

No

Summary

The v2026.7.1-beta.3 candidate cannot produce publish-ready Full Release Validation evidence. The candidate pins an outdated Codex app-server package, carries stale Telegram QA and SwiftFormat configuration, and generates a release section larger than GitHub's release-body limit. The trusted performance harness also needs the report-publication and Kova corrections tracked in #103125 and #103126.

Steps to reproduce

1. Run Full Release Validation against release/2026.7.1@245e99f28b3993cb38a3e82ac97e72599455c465.
2. Observe the all-publishable plugin check reject @openclaw/codex: the candidate uses @openai/[email protected], while the current required release version is 0.144.0.
3. Observe macos-swift reject the candidate with SwiftFormat 0.62 and the Telegram canonical scenario expect silence after the runtime intentionally returns an authorization denial.
4. Regenerate the complete 2026.7.1 contribution record from v2026.7.1-beta.2; the release section is approximately 193.6k characters, above GitHub's 125,000-character release-body limit.

Expected behavior

Full Release Validation should validate the exact candidate with current required dependencies and target-owned QA configuration. Release preparation should reject oversized notes before any registry or GitHub release mutation.

Actual behavior

The candidate fails dependency freshness, macOS formatting, and Telegram QA. Its generated release notes would also fail late during GitHub release creation after earlier publish-side mutations.

OpenClaw version

245e99f28b3993cb38a3e82ac97e72599455c465

Operating system

Ubuntu 24.04 and macOS GitHub Actions runners

Install method

Repository checkout in GitHub Actions

Model

N/A for metadata validation; mock provider for the performance release lane

Provider / routing chain

Full Release Validation -> candidate CI + plugin metadata validation + performance evidence + GitHub Release preparation

Logs

@openclaw/[email protected]: @openai/codex must match npm latest for release; found "0.143.0", latest is "0.144.0".

Screenshots, recordings, and evidence

• Full validation: https://github.com/openclaw/openclaw/actions/runs/29050334044
• Codex freshness failure: https://github.com/openclaw/openclaw/actions/runs/29050334530/job/86229104827
• Candidate CI: https://github.com/openclaw/openclaw/actions/runs/29050510594
• Release checks: https://github.com/openclaw/openclaw/actions/runs/29050511761
• Performance failure: https://github.com/openclaw/openclaw/actions/runs/29050511549/job/86229720522
• Corrected Kova release lineage: fix: attribute gateway snapshots to resource gates Kova#10
• Trusted harness repair: fix: fail release performance when reports do not publish #103126

Impact and severity

• Affected: release maintainers and beta consumers.
• Severity: Release blocker.
• Frequency: Deterministic for this candidate.
• Consequence: beta.3 cannot receive complete, trustworthy release proof; attempting publication risks a late partial-publish failure.

Additional information

The candidate-specific repair needs the Codex 0.144 update, the already-landed Telegram assertion and SwiftFormat configuration backports, and compact lossless release-note generation with an early size gate. The performance harness repair remains independently tracked by #103125 and #103126.