moneybtn2, week 32: three merges and a numbering collision

Thu, 06 Aug 2026 00:00:00 +0000

A merge-heavy week: three branches that had been open for a while all landed.

What shipped. Candle storage and the charts that read from it; event overlays on those charts; and a detail popup in the ops view. Each of those had been sitting on its own branch long enough that merging them was most of the work.

One thing worth writing down came out of the chart work: the two data sources feeding the chart are independent of each other. That sounds obvious stated plainly, and it was not obvious from the code — it’s exactly the sort of fact that gets rediscovered painfully in six months, so it’s a decision record now.

And the comedy. Two branches both created decision record 0089. Fine, renumber: 0107 and 0108. Except 0089 had also been claimed on main while those branches were open, so the third one became 0109 — followed by a commit to index it and fix a stale reference to its old number that had survived the first two renames.

Three commits of pure bookkeeping to land one document about something unrelated. Sequentially-numbered append-only records are a good convention until you have parallel branches, and I don’t have a real fix yet. Allocating the number at merge time rather than at write time would work, but it means the filename changes late, which is its own annoyance.

Also: the deploy script does not do two of the steps required to actually deploy, and now says so out loud in the docs rather than living in my head.

Where this came from

Work between 3 and 6 August 2026 in the moneybtn2 repository: pull requests #122, #126 and #127, and decision records 0107–0109. The repository is private.

The two undocumented deploy steps are described as documented, not as automated — they are still manual.

process — toothywalrus

moneybtn2, week 32: three merges and a numbering collision

Where this came from