We traced the core:compile failure to a pre-existing TypeScript error (TS2430) in webmcp-bridge.provider.ts, which is WebMCP infrastructure introduced by the dependency PR #4458 — not by changes in this PR. The same error was confirmed to exist in branch 4458, so this needs to be resolved there first before this PR can compile cleanly.
Merge 1f4018e728927ea1f29e943d94f5807b2f2ce25f into d5fde759fa43116a9b1bf6e7cba7827e30ef58fe
445901988f5Open on GitHubSelf-Healing CI
An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.
The failure was classified as environment_state rather than code_change for the following reasons:
The
coreproject was not touched by this PR. Thetouched_projectslist is empty, meaning none of the files changed in this PR belong to thecorepackage where the compile error originates.The failing file is not part of this PR's changes. The error is in
packages/@o3r/core/src/core/webmcp/webmcp-bridge.provider.ts, which is WebMCP infrastructure code introduced by PR #4458 — the dependency this PR explicitly builds on top of.The identical error exists in branch 4458. The similar-task-failure-detector confirmed that branch 4458 has the exact same
TS2430compile error on the same file and line. This means the failure pre-dates this PR and is not a regression introduced here.The root cause is a type incompatibility in the dependency branch.
ModelContextis missing theregisterToolandontoolchangeproperties required byModelContextCore. This is a structural issue in the WebMCP bridge infrastructure that must be resolved in PR #4458 before this PR can compile cleanly.