c4fe2c1d · zzmq.dev@gmail.com/zz
Commit
c4fe2c1d599f4b051468d11d21e3050cc996ca38
Move Ladder storage to git notes, via isomorphic-git A rung is an annotation on a real git object, not a standalone coordination record, so it belongs in a git note attached to that object (data-format.md's argument against notes holds for Lanes/ Roles/Decisions, not for this). One note per anchor (file blob, directory/repo tree, or the commit an issue/release is tied to), holding that rung plus everything embedded under it inline, so reading one file's local Ladder is one note read. Separate note refs per commit-anchored kind (issue/pr/release) after a real collision surfaced in testing: two unrelated rungs anchoring to the same commit silently clobbered each other under one shared ref. Used isomorphic-git instead of shelling out to the real git binary or a native binding (es-git): it's pure JS, the only one of the three that can actually run in Cloudflare Workers, the real target deployment, which has no child_process and no native addon loading. Caught and fixed a real cross-compatibility bug in the process: short commit SHAs round-trip fine through isomorphic-git's own API but are invisible to the real `git notes` CLI, since git's notes tree indexes by full SHA; fixed by expanding every commit ref before anchoring. Verified the real `git notes` CLI can list and show every note this build writes. Removed the superseded one-file-per-rung storage. Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
Troy Howard <thoward37@gmail.com> -- 2026-10-07T12:28:50.000Z