Skip to content

fix(release): carry the Z.AI API Platform waiver#110243

Merged
RomneyDa merged 2 commits into
extended-stable/2026.6.33from
dev/extended-stable-2026.6.33-v6.11-repair6
Jul 17, 2026
Merged

fix(release): carry the Z.AI API Platform waiver#110243
RomneyDa merged 2 commits into
extended-stable/2026.6.33from
dev/extended-stable-2026.6.33-v6.11-repair6

Conversation

@RomneyDa

@RomneyDa RomneyDa commented Jul 17, 2026

Copy link
Copy Markdown
Member

What Problem This Solves

Canonical Full Release Validation 29620608973 correctly used candidate-owned workflows, but Release Checks child 29620688377 still ran the known-broken Z.AI API Platform probes. Job 88015298867 reproduced the existing account outage: both global endpoint probes returned zero assistant content while 68 sibling live tests passed.

The maintainer-approved temporary waiver from #109246 and its shard companion #109272 had been merged only into main for the discarded temporary-harness design. Candidate-owned validation therefore needs the same release machinery frozen on extended-stable/2026.6.33.

Why This Change Was Made

Two dependency-ordered commits:

  1. Cherry-pick test(ci): temporarily omit Z.AI API Platform validation #109246 / 954c77d4ef9d4e0f587344032eda90f694149d16:
    • omit Z.AI API Platform from the Docker model matrix;
    • omit the native Z.AI gateway profile;
    • keep the combined advisory lane as xAI-only;
    • record the temporary omission in workflow summaries.
  2. Adapt only the Z.AI shard portion of fix(release): repair frozen validation compatibility #109272 / c4b2183db66f0f8f8b60edaf09f9c33b2f349a03:
    • exclude src/agents/zai.live.test.ts from the broad agents shard;
    • retain it exactly in the dedicated Z.AI Coding Plan shard.

No Android compatibility change is imported because the candidate-owned v6.11 CI does not need it.

User Impact

No product behavior change. Z.AI API Platform validation remains temporarily waived while its CI account is unavailable; Z.AI Coding Plan validation remains required. No provider runtime, credential, native, package, version, npm inventory, or publication code changes. The release remains npm-only.

The waiver must be reverted after the replacement API Platform credential passes a real completion probe.

Evidence

After merge, npm preflight and all-groups Full Release Validation will run from the new exact canonical SHA. No tag or publication has occurred.

RomneyDa added 2 commits July 17, 2026 16:36
@RomneyDa
test(ci): temporarily omit Z.AI API Platform validation (#109246)
fe3014f 
* test(ci): temporarily omit Z.AI API Platform validation

* test(ci): align disabled provider count

(cherry picked from commit 954c77d)
@RomneyDa
fix(release): keep waived Z.AI probe out of broad shard
4f745b7 
Adapt the Z.AI shard portion of upstream c4b2183 (#109272). Exclude the waived API Platform file from the broad agents shard while retaining the dedicated Coding Plan proof.

(cherry picked from commit c4b2183)
@openclaw-barnacle openclaw-barnacle Bot added scripts Repository scripts size: S maintainer Maintainer-authored PR labels Jul 17, 2026
@clawsweeper clawsweeper Bot added rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR. P2 Normal backlog priority with limited blast radius. merge-risk: 🚨 automation 🚨 May affect CI, automerge, proof capture, label sync, or maintainer automation. labels Jul 17, 2026
@clawsweeper

clawsweeper Bot commented Jul 17, 2026

Copy link
Copy Markdown
Contributor

Codex review: needs maintainer review before merge. Reviewed July 17, 2026, 7:43 PM ET / 23:43 UTC.

Summary
This PR backports the temporary Z.AI API Platform release-validation waiver and preserves the dedicated Z.AI Coding Plan shard on extended-stable/2026.6.33.

PR surface: Tests -1, Config +3, Other 0. Total +2 across 6 files.

Reproducibility: yes. from the provided release-validation diagnostic: the cited Release Checks job reproduces the failed Z.AI API Platform probes, and the changed workflow/shard paths directly encode the failing selection behavior. This review did not execute the credentialed live probes.

Review metrics: 1 noteworthy metric.

  • Temporary provider coverage change: 1 API Platform provider omitted; 1 dedicated Coding Plan shard retained. The branch remains protected against the known unavailable endpoint while preserving the healthy Z.AI validation path.

Merge readiness
Overall: 🐚 platinum hermit
Proof: 🐚 platinum hermit
Patch quality: 🐚 platinum hermit
Result: ready for maintainer review.

Overall follows the weaker of proof and patch quality, so missing proof can cap an otherwise strong patch.

Rank-up moves:

  • [P2] Obtain release-owner acceptance of the temporary coverage reduction before merge.
  • Complete the candidate-owned full release validation at the exact merged SHA.

Risk before merge

  • [P1] Merging intentionally omits Z.AI API Platform from default frozen-candidate release validation until a replacement credential passes a real completion probe; a release owner must accept that temporary coverage gap and ensure the waiver is later removed.

Maintainer options:

  1. Approve with release-waiver ownership (recommended)
    Merge after the release owner explicitly accepts the temporary omitted API Platform coverage and confirms the dedicated Coding Plan shard remains required.
  2. Pause for restored credential coverage
    Hold this release-branch change until a replacement API Platform credential can demonstrate a real completion probe and restore normal validation.

Next step before merge

  • The PR is a protected, member-authored release-branch change whose remaining blocker is release-owner acceptance of the intentional temporary validation waiver.

Maintainer decision needed

  • Question: Should the extended-stable/2026.6.33 release candidate proceed with Z.AI API Platform validation temporarily omitted while the dedicated Z.AI Coding Plan shard remains required?
  • Rationale: The patch is mechanically aligned with two already-merged main-branch fixes, but accepting a temporarily reduced provider-validation matrix for a release candidate is a release-risk decision rather than a code-correctness determination.
  • Likely owner: RomneyDa — This person authored the original merged waiver and the release-branch carry, so they are the strongest available routing candidate for the release-validation context.
  • Options:
    • Approve the temporary waiver (recommended): Merge this backport, complete the candidate-owned release validation, and remove the waiver once the replacement API Platform credential produces a real completion.
    • Hold the release candidate: Keep the branch unmerged until the replacement Z.AI API Platform credential is available and the normal probes can run again.

Security
Cleared: The patch changes only existing in-repository workflow planning, shard selection, and matching tests; it adds no dependency, permission, secret, artifact-download, or new code-execution path.

Review details

Best possible solution:

Land the narrow frozen-branch backport only with release-owner acceptance of the temporary coverage waiver, keep the Coding Plan shard required, and remove the omission after a replacement API Platform credential passes a real completion probe.

Do we have a high-confidence way to reproduce the issue?

Yes, from the provided release-validation diagnostic: the cited Release Checks job reproduces the failed Z.AI API Platform probes, and the changed workflow/shard paths directly encode the failing selection behavior. This review did not execute the credentialed live probes.

Is this the best way to solve the issue?

Yes for the frozen release branch: it selectively carries the two already-merged main fixes, avoids the unrelated Android compatibility change, and preserves the healthy Z.AI Coding Plan proof rather than disabling Z.AI coverage wholesale.

AGENTS.md: found and applied where relevant.

Codex review notes: model internal, reasoning high; reviewed against 82fa956d5a22.

Label changes

Label changes:

  • add P2: This is a bounded release-validation workflow change with no stated product-runtime behavior change.
  • add merge-risk: 🚨 automation: The PR changes the release workflow matrix and live-test shard selection used to qualify a frozen release candidate.
  • add rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • add status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This is a member-authored release-workflow PR, so the external-contributor proof gate does not apply; the body provides a concrete failing release job and focused contract-test evidence.

Label justifications:

  • P2: This is a bounded release-validation workflow change with no stated product-runtime behavior change.
  • merge-risk: 🚨 automation: The PR changes the release workflow matrix and live-test shard selection used to qualify a frozen release candidate.
  • rating: 🐚 platinum hermit: Overall readiness is 🐚 platinum hermit; proof is 🐚 platinum hermit and patch quality is 🐚 platinum hermit.
  • status: 👀 ready for maintainer look: ClawSweeper has no concrete contributor-facing blocker left for this PR. Not applicable: This is a member-authored release-workflow PR, so the external-contributor proof gate does not apply; the body provides a concrete failing release job and focused contract-test evidence.
Evidence reviewed

PR surface:

Tests -1, Config +3, Other 0. Total +2 across 6 files.

View PR surface stats
Area Files Added Removed Net
Source 0 0 0 0
Tests 3 10 11 -1
Docs 0 0 0 0
Config 1 15 12 +3
Generated 0 0 0 0
Other 2 7 7 0
Total 6 32 30 +2

What I checked:

Likely related people:

  • RomneyDa: Authored the merged main-branch waiver and shard-repair commits that this PR selectively carries to the frozen release branch. (role: introduced and carried the waiver; confidence: high; commits: 954c77d4ef9d, c4b2183db66f, 4f745b7d3849; files: .github/workflows/openclaw-live-and-e2e-checks-reusable.yml, scripts/plan-release-workflow-matrix.mjs, scripts/test-live-shard.mjs)
What the crustacean ranks mean
  • 🦀 challenger crab: rare, exceptional readiness with strong proof, clean implementation, and convincing validation.
  • 🦞 diamond lobster: very strong readiness with only minor maintainer review expected.
  • 🐚 platinum hermit: good normal PR, likely mergeable with ordinary maintainer review.
  • 🦐 gold shrimp: useful signal, but proof or patch confidence is still limited.
  • 🦪 silver shellfish: thin signal; proof, validation, or implementation needs work.
  • 🧂 unranked krab: not merge-ready because proof is missing/unusable or there are serious correctness or safety concerns.
  • 🌊 off-meta tidepool: rating does not apply to this item.

Shiny media proof means a screenshot, video, or linked artifact directly shows the changed behavior. Runtime, network, CSP, and security claims still need visible diagnostics.

How this review workflow works
  • ClawSweeper keeps one durable marker-backed review comment per issue or PR.
  • Re-runs edit this comment so the latest verdict, findings, and automation markers stay together instead of adding duplicate bot comments.
  • A fresh review can be triggered by eligible @clawsweeper re-review comments, exact-item GitHub events, scheduled/background review runs, or manual workflow dispatch.
  • PR/issue authors and users with repository write access can comment @clawsweeper re-review or @clawsweeper re-run on an open PR or issue to request a fresh review only.
  • Maintainers can also comment @clawsweeper review to request a fresh review only.
  • Fresh-review commands do not start repair, autofix, rebase, CI repair, or automerge.
  • Maintainer-only repair and merge flows require explicit commands such as @clawsweeper autofix, @clawsweeper automerge, @clawsweeper fix ci, or @clawsweeper address review.
  • Maintainers can comment @clawsweeper explain to ask for more context, or @clawsweeper stop to stop active automation.

@RomneyDa

RomneyDa commented Jul 17, 2026

Copy link
Copy Markdown
Member Author

Land-ready proof at exact PR head 4f745b7d3849906d56673794a7c5840685b7436c:

  • All relevant hosted PR checks passed; GitHub reports the PR cleanly mergeable.
  • Focused exact-head Z.AI Coding Plan workflow 29621285373 passed a real provider completion while API Platform remained omitted.
  • Structural selection proof reports broadHasZai=false; the dedicated Coding Plan shard selects exactly src/agents/zai.live.test.ts.
  • Actionlint passed.
  • Focused workflow/planner/shard suites passed 78/78.
  • Oxfmt and git diff --check passed.
  • This is release machinery only: no provider runtime, credential, Android, native, package, version, npm inventory, or publication code changed.

The waiver remains temporary and must be reverted after the replacement API Platform credential passes a real completion probe. After merge, prior preflight/validation evidence is superseded and both required canonical runs will be repeated at the new exact SHA. No tag or publication has occurred.

@RomneyDa
RomneyDa merged commit 30bde93 into extended-stable/2026.6.33 Jul 17, 2026
179 of 184 checks passed
@RomneyDa
RomneyDa deleted the dev/extended-stable-2026.6.33-v6.11-repair6 branch July 17, 2026 23:48
@RomneyDa RomneyDa mentioned this pull request Jul 21, 2026
Merged
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Reviewers

No reviews

Assignees

No one assigned

Labels

maintainer Maintainer-authored PR merge-risk: 🚨 automation 🚨 May affect CI, automerge, proof capture, label sync, or maintainer automation. P2 Normal backlog priority with limited blast radius. rating: 🐚 platinum hermit Good normal PR readiness with ordinary maintainer review expected. scripts Repository scripts size: S status: 👀 ready for maintainer look ClawSweeper has no concrete contributor-facing blocker left for this PR.

Projects

None yet

Milestone

No milestone

Development

Successfully merging this pull request may close these issues.

1 participant

@RomneyDa