Evidence record / agent-flywheel

A dated record of one change, kept so the writing that cites it can be checked. Compiled from the sources listed below by the research run, not written for reading. The judgment lives in the issues that cite it, below.

2026-10-13-agent-flywheel-a-failed-dcg-install-now-fails-the-install-on-v0-9-0-it-could-finish-green-with-exit

A failed DCG install now fails the install; on v0.9.0 it could finish green with exit 0. The commit records the old failure mode. Nine tools the manifest marks required (br, bv, cass, cm, caam, dcg, ru, ubs, ms) could fail in the legacy stack phase, which is what a plain curl | bash runs, and still be listed under an Optional heading below a green Installation Complete! banner with exit 0. v0.10.0 counts them as failures and exits non-zero, which is why the v0.10.0 factory run reported exit 1 when the dcg checksum was refused (#427). The guard’s binary is now required. Registering its Claude Code hook in the finalize step is still logged as optional, and the Antigravity hook still allows commands when dcg cannot run.

Channel: tagged-release. Half: defect. Date: 2026-10-03.

Operator consequence: On hosts built with v0.9.0, confirm that dcg is installed and its hook registered: a green install was not evidence of either. On v0.10.0, treat a non-zero installer exit as real, read the failure list, and still check the hook-registration line in the log. The install-time verdict got honest; the runtime posture, allow when the guard is missing, did not change.

Receipt

Finding metadata

Run: 2026-10-13-profile-refresh-2026-09-21_2026-10-13-frontier-v0

Finding ID: 2026-10-13-agent-flywheel-a-failed-dcg-install-now-fails-the-install-on-v0-9-0-it-could-finish-green-with-exit

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact