openclaw - ✅(Solved) Fix parity gate fails when speech-core runtime public surface cannot be resolved [1 pull requests, 1 participants]

Official PRs (…)
ON THIS PAGE

Recommended Tools

×6

Utilities matched from this issue’s tags and category — try them while you read without losing context.

GitHub issue graph ai analysis

Paste a GitHub issue URL. We fetch that issue, discover linked issues from bodies/comments/timeline, collect linked pull requests, and produce a structured English report.

The report is written in English Markdown for sharing and archival.

Helpful · Quick feedback

Loading…
GitHub stats
openclaw/openclaw#67887Fetched 2026-04-17 08:29:04
View on GitHub
Comments
0
Participants
1
Timeline
1
Reactions
0
Participants
Timeline (top)
cross-referenced ×1

The GPT-5.4 / Opus 4.6 parity gate can fail for unrelated PRs because the qa-lab parity run aborts with:

Error: Unable to resolve bundled plugin public surface speech-core/runtime-api.js

This shows up as a red CI check even when the PR diff does not touch speech-core or parity-gate code.

Error Message

Error: Unable to resolve bundled plugin public surface speech-core/runtime-api.js

  • agent.wait returned error: Error: Unable to resolve bundled plugin public surface speech-core/runtime-api.js

Root Cause

This makes the parity gate noisy on unrelated PRs and can block or confuse review by reporting a red check that is not caused by the branch under test.

Fix Action

Fixed

PR fix notes

PR #67904: fix facade activation for manifestless runtime packages

Description (problem / solution / changelog)

Summary

  • treat bundled runtime support packages without openclaw.plugin.json as valid bundled facades when they expose an @openclaw/<dir> package.json
  • derive the facade plugin id from package.json for runtime-core packages like speech-core
  • keep facade activation checks working for normal manifest-backed plugins

Testing

  • pnpm vitest run src/plugin-sdk/facade-runtime.test.ts src/plugins/bundled-plugin-metadata.test.ts test/scripts/bundled-plugin-build-entries.test.ts

Why

The parity gate failure behind #67887 was blowing up while resolving . That runtime surface is intentionally shipped, but the activation check path only recognized bundled plugins with , so manifestless runtime-core packages could be treated as missing instead of valid bundled facades.

Changed files

  • extensions/image-generation-core/package.json (modified, +3/-0)
  • extensions/media-understanding-core/package.json (modified, +3/-0)
  • extensions/speech-core/package.json (modified, +3/-0)
  • src/gateway/server-close.test.ts (modified, +3/-1)
  • src/plugin-sdk/facade-activation-check.runtime.ts (modified, +56/-27)
  • src/plugin-sdk/facade-runtime.test.ts (modified, +33/-0)
  • test/extension-test-boundary.test.ts (modified, +1/-2)
RAW_BUFFERClick to expand / collapse

Summary

The GPT-5.4 / Opus 4.6 parity gate can fail for unrelated PRs because the qa-lab parity run aborts with:

Error: Unable to resolve bundled plugin public surface speech-core/runtime-api.js

This shows up as a red CI check even when the PR diff does not touch speech-core or parity-gate code.

Evidence

Observed on PR #66685 in the failing check:

  • Run the GPT-5.4 / Opus 4.6 parity gate against the qa-lab mock

The uploaded parity artifact (parity-gate-66685) contains parity/qa-agentic-parity-report.md, which reports:

  • QA parity verdict: fail
  • every required scenario failing in both lanes with:
    • agent.wait returned error: Error: Unable to resolve bundled plugin public surface speech-core/runtime-api.js

Examples from the report include:

  • Approval turn tool followthrough
  • Model switch with tool continuity
  • Source and docs discovery report
  • Image understanding from attachment
  • Subagent handoff
  • Config restart capability flip

Both candidate and baseline fail identically, which suggests a repo/runtime setup problem rather than a model-parity regression.

Why this matters

This makes the parity gate noisy on unrelated PRs and can block or confuse review by reporting a red check that is not caused by the branch under test.

Likely area to inspect

  • bundled plugin public-surface resolution for speech-core/runtime-api.js
  • qa-lab / parity-gate environment expectations around bundled plugin artifacts
  • whether parity-gate jobs need an explicit build/staging step for bundled plugin public surfaces before running scenarios

extent analysis

TL;DR

The parity gate failure is likely due to an issue with resolving the bundled plugin public surface speech-core/runtime-api.js, and verifying the qa-lab environment expectations and parity-gate job configuration may help resolve the issue.

Guidance

  • Verify that the speech-core/runtime-api.js file is correctly bundled and available in the qa-lab environment.
  • Check the parity-gate job configuration to ensure that it includes an explicit build or staging step for bundled plugin public surfaces before running scenarios.
  • Inspect the environment expectations around bundled plugin artifacts in the qa-lab and parity-gate environments to identify any potential mismatches.
  • Review the parity-gate-66685 artifact and the parity/qa-agentic-parity-report.md report to confirm that the failure is consistent across all scenarios and lanes.

Example

No code snippet is provided as the issue does not imply a specific code change.

Notes

The issue suggests that the problem is not related to the model-parity regression, but rather a repo/runtime setup issue. The fact that both candidate and baseline fail identically supports this theory.

Recommendation

Apply a workaround by verifying and updating the qa-lab environment expectations and parity-gate job configuration to ensure correct resolution of bundled plugin public surfaces. This is recommended because the issue appears to be related to the environment setup rather than a code change.

Vote matrix · Quick signals

Works
Did the solution work? Tap to confirm.
Easy Fix
Was it a quick fix?
Time Saver
Did it save you time?
Blocking
Was it severely blocking?
Common Issue
Are others likely hitting this too?
Flaky / Intermittent
Is it intermittent?
Verified / Reproducible
Can you reproduce it reliably?
Loading…

Still need to ship something?

×6

Another batch ranked right after the header list — different links, same matching logic.

Back to top recommendations

TRENDING

openclaw - ✅(Solved) Fix parity gate fails when speech-core runtime public surface cannot be resolved [1 pull requests, 1 participants]