Upstream dependency incident

Failed commit and CI evidence

• Placebo case upstream-formatter-release: Chalk 5 is ESM-only and cannot be required. Tavily grounding names the release fact before the repair.
• Failing command: vitest run
• Error excerpt:  Duration  208ms (transform 21ms, setup 0ms, import 37ms, tests 4ms, environment 0ms) $ vitest run ⎯⎯⎯⎯⎯⎯⎯ Failed Tests 1 ⎯⎯⎯⎯⎯⎯⎯  FAIL  case.test.js > loads the pinned CommonJS release TypeError: chalk.green is not a function  ❯ Object.exports.renderStatus app.cjs:2:36  1| const chalk = require('chalk');  2| exports.renderStatus = () => chalk.green('ready');  | ^  3|  ❯ case.test.js:4:60 ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯[1/1]⎯ [ELIFECYCLE] Test failed. See above for more details.
• Repository local/fixture · run local-fixture · runtime node
• Recorded workflow run

Nano diagnosis and confidence

Failure class

infra

Confidence

49%

Signals

• TypeError: chalk.green is not a function
• mechanical:infra
• llm:test-bug
• llm-command-mismatch
• llm-excerpt-ungrounded
• llm-class-ungrounded

Diagnosis recovery

• Initial diagnosis retained: infra. Recovery: not-run — no-supported-recovery-signal.
• Observed command: vitest run
• Executed command: if [ -f pnpm-lock.yaml ]; then corepack pnpm exec sh -c 'vitest run'; elif [ -f yarn.lock ]; then corepack yarn exec sh -c 'vitest run'; else PATH="./node_modules/.bin:$PATH" sh -c 'vitest run'; fi
• These bounded observations do not measure live repair quality.

Clean audit branch and Ultra verdict

Not run. No candidate survived for adversarial audit.

Final outcome

Gave up Recorded live result

Sutura never merges a generated repair. A gave up result still needs human review.

Check a patch this page did not produce

This run did not record an exact failing commit and policy commit, so both are shown as placeholders. Verification is always tied to exact commits. A patch cannot ask for a more permissive policy by carrying one, and no green log is accepted in place of execution.

sutura verify \
  --case-dir <checkout> \
  --source-sha <failing commit> \
  --policy-base-sha <trusted policy commit> \
  --candidate-diff <patch file> \
  --failing-command diagnosed \
  --format json

The same route runs as a GitHub Action and needs no repository write access. Uploading a patch stays a command-line and Action route; this page never runs one.