Composio powers 1000+ toolkits, tool search, context management, authentication, and a sandboxed workbench to help you build AI agents that turn intent into action.
test(cli-e2e): gate mutate --strict on check-too-weak steps only (#5419)
This PR: - builds on https://github.com/ComposioHQ/composio/pull/5418 — base is `test/agent-journey-grader-guards` - makes `mutate.ts --strict` fail on `check-too-weak` steps alone, instead of failing on any step that is not `needed` - moves the exit reason into `failuresOf()` in `src/mutation.ts`, so `--strict` names the journey, step and command it rejects on stderr instead of exiting silently - keeps `unused` in the report and the README table, where the seven listed steps are expected: reads, a `--help`, and commands that fail on purpose - updates `HILLCLIMB.md` and the agent-journeys README to say what the gate now means ## Context `--strict` was defined as "every step is load-bearing", which no journey can satisfy. A read or a `cat` of a skill reference changes no state, so no outcome check can depend on it and it is always `unused`; dropping those steps to make the flag green would delete the exploration the hand-authored paths exist to document. The defect signal is the other verdict: `check-too-weak` means a run ended somewhere else and every check still passed. With that split, `--strict` is green on the current tree and means something: | veredict | what it says | `--strict` | | --- | --- | --- | | `needed` | a check noticed the step is gone | pass | | `unused` | no check noticed, and the run ended the same way | pass | | `check-too-weak` | no check noticed, but the run ended somewhere else | fail | Wiring it into CI is left out on purpose: it is 22 containers, 1m41s locally, and it only changes meaning when the journeys, the checks or the fake backend change — a path-filtered job is the follow-up, not a step on every PR. ## Verification - `bun run mutate.ts --strict` on all five journeys: exit 0, `17 step(s): 10 needed, 7 unused, 0 check-too-weak`, 1m41s - `bun test ./mutation.test.ts`: 28 pass, 0 fail — including `--strict` passing with `unused` steps and failing with `check-too-weak`, and the failure message it prints - `bun run typecheck`: clean; `oxlint`, antislop and prettier on the changed files: clean - `bun test e2e.test.ts` is unchanged by this PR (no harness file is touched), so it is not re-run here