Interactive · Sheet 05

SIMULATOR

This is how hyperfixer behaves on a real project: gates run in cost order, fail-fast blocks later groups, cached gates return instantly, autofix clears the fixable noise, and every outcome maps to one exit code. Inject problems and run.

Inject problems lint error, autofixable type error failing test hanging gate, timeout Pipeline options warm cache max-cost 100

$ hyperfixer run

verdict.json

run the pipeline first

FIX simulates hyperfixer fix: fixCommands (eslint --fix, biome --write) clear the autofixable lint error, then the pipeline verifies. The hanging gate shows the infrastructure path: status error, exit 3, the agent must not edit code for it.