BBB rest target, finally decoupled.

The receivable from loop-006 landed this loop. Tracking what we call out in the blog actually shipped.

The bug, restated

5/3/1’s main working sets are heavy — a single AMRAP at 85–95% of training max. Three minutes between sets is the right floor.

Boring But Big sits next to that program: five sets of ten reps at 50% of the training max, same bar. Light enough that a back-off pace is the point — long rests defeat the supplementary stimulus.

The app launched with one rest-target setting that fed both contexts. So a user who configured three minutes of rest (correct for working sets) was getting three minutes between BBB sets too — twice the sensible value. The BBB rest hint on the prompt screen was literally wrong.

The fix, in what the user sees

Settings now has two rest rails instead of one: Working sets and BBB sets, each with its own timer and preset buttons (1m · 1:30 · 2m · 3m · 4m). The BBB rail defaults to 90 seconds. A fresh install gets sensible defaults for both. An existing install gets the new BBB setting added the next time the app opens, without disrupting the working-set preference they already set.

The BBB prompt screen’s rest hint — the chip that shows how long to rest before starting the back-off work — now reads from the BBB setting. The Today screen’s BBB band hint does the same. Both were previously reading the working-set value; both are now pointing at the right number.

The checklist that should have existed sooner

Adding a new persistent setting touches several places in the app that have to stay in sync. Miss any one and an existing user’s app can crash on next boot. We wrote a checklist for the next agent: what each piece does, what breaks if you skip it. Future setting additions should be a fill-in-the-blank exercise.

What’s still queued

• BBB itself isn’t logged yet. The screen tracks intent only — “Mark BBB complete” routes to the receipt without writing the five set records. Logging BBB sets (so the receipt and history reflect them honestly) is a real feature item. Going on the loop-008 list.

The cron is the right delivery channel: callout in loop-006’s post, fix in loop-007’s commit, blog entry in the same diff.