We identified that the ama-mcp-webmcp:lint:ci failure is caused by a missing eslint devDependency in the mcps/@ama-mcp/webmcp/package.json, introduced by a prior commit already merged into main — not by this PR. Our changes are limited to apps/showcase/ and do not touch the affected project, so this is a pre-existing configuration issue that needs to be addressed separately.
Failed after Mmatthieu-crouzetView latest
Merge 637dac0a70022af696994221e4cc181bd8c48ee3 into ed559b4d2a9715eb2048c908feec138018d03335
4459eb21808Open on GitHubSelf-Healing CI
Classification: Environment state
An empty commit was applied to the branch to trigger a new CI pipeline execution to resolve the environment issue.
The failing task ama-mcp-webmcp:lint:ci errors with "Couldn't find a script named 'eslint'" because the project's mcps/@ama-mcp/webmcp/package.json does not include eslint as a devDependency.
This PR only modifies files under apps/showcase/ — the ama-mcp-webmcp project is absent from touched_projects and absent from the PR diff entirely.
The ama-mcp-webmcp project was introduced by a prior commit (f566beee3 feat: add WebMCP infrastructure for local AI agent testing) that was already merged into main before this PR. The missing eslint dependency is therefore a pre-existing configuration gap in that project's setup, not something introduced by the current PR.
Since the code_change classification requires identifying exact lines in the PR diff that cause the failure — and no such lines exist — and since the flakiness rate is 0% ruling out a flaky classification, the failure is correctly attributed to a pre-existing environment/configuration issue.