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-v0-10-0-s-changelog-describes-the-lts-fix-and-test-limits-not-most-of-what-the-tag-ships

v0.10.0’s changelog describes the LTS fix and test limits, not most of what the tag ships; cost, license and lineup unchanged. The profile credited v0.9.0 with legible receipts. v0.10.0 keeps a dated heading, but its entry is a qualification memo. A reader of the changelog would not learn that cod changed model, that acfs swarm launch and plugin installs arrived, or that a token-logging bug and a nightly settings rewrite were fixed. The README at the tag still offers v0.9.0 as its pinned example and says “Tagged releases are tested and stable,” while the release body declines to claim a full install. Budget, license and the default agent lineup did not move.

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

Operator consequence: Before upgrading, read the compare (173 commits), not the changelog. Cost: nothing to report; the $440-$656/month figure is still the project’s own example stack, not market pricing. The license rider and the three-agent default stand unchanged.

Receipt

Finding metadata

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

Finding ID: 2026-10-13-agent-flywheel-v0-10-0-s-changelog-describes-the-lts-fix-and-test-limits-not-most-of-what-the-tag-ships

Profile citations

Source links

Primary links, including exact changelog lines when available.

Versioned source: run artifact