Your source. A real browser. The same test twice.
The website is a recorded-evidence viewer with a live reproduction. Actual repair execution runs locally, where it can change your source safely.
The demonstrated repair used a web-assisted Gemini re-prompt. Automatic Gemini CLI repair is implemented but has not yet been validated end to end with an authenticated Gemini CLI in this build environment. Missing authentication stops the run; there is no hardcoded repair fallback.
Local setup
Use the source repository with Node 22, Git and Google Chrome on Linux. No hosted execution account or paid model API is required.
npm ci npm test npx kane-cli login --oauth npx kane-cli whoami npx gemini npm start
Sign into your own free Gemini Code Assist account and a TestMu account with available Kane credits. Never put credentials into source files. Open the loopback address printed by the server.
What Run Full Repair does
- Restores the deliberately broken controlled fixture.
- Runs the immutable Kane acceptance objective.
- Collects five DOM hit tests and stacking ancestor evidence.
- Requests a CSS-only proposal from Gemini CLI.
- Rejects changes outside the overlay CSS rules and checks the active loading state.
- Runs the unchanged Kane objective again. Only an actual passed completion with exit 0 is success.
Limits
One same-origin overlay fixture, not arbitrary website repair. The local runner binds to loopback and must not be exposed to the internet. The static viewer has no model keys, account credentials or execution server.