A planned project finishes with its runs' known gaps dropped #270

Closed
opened 2026-10-28 11:54:57 -04:00 by cmoriarty · 1 comment
Owner

What happens
Each run's summary lists what it left Not done. Re-planning folded those into the next item in runs 125 and 126, then stopped doing it:

  • run 127: the bigger ball never checked by eye
  • run 128: an end-to-end spec never run
  • run 129: post-catch thresholds never tuned
  • run 130: nobody listened to the new sounds
  • run 131: touch never tried on a touch device; a panel covers text on phones

The project then reported "every item of the plan is done".

Fix

  • Re-planning carries every Not done bullet into the plan: an item, or a list for a person to check.
  • The project page shows that list when the plan is done.

Done when
A finished project shows every gap its runs reported, and none is silently dropped.

From the #260 re-run's transcripts.

**What happens** Each run's summary lists what it left **Not done**. Re-planning folded those into the next item in runs 125 and 126, then stopped doing it: - run 127: the bigger ball never checked by eye - run 128: an end-to-end spec never run - run 129: post-catch thresholds never tuned - run 130: nobody listened to the new sounds - run 131: touch never tried on a touch device; a panel covers text on phones The project then reported "every item of the plan is done". **Fix** - Re-planning carries every Not done bullet into the plan: an item, or a list for a person to check. - The project page shows that list when the plan is done. **Done when** A finished project shows every gap its runs reported, and none is silently dropped. _From the #260 re-run's transcripts._
Author
Owner

Shipped in #301 (5355515, deployed). It's part of planned-projects-finish-right, archived once the change's other issues are verified.

Seen on production in run 139 (the first item of cmoriarty/breakout-planned):

  • Tick: run 139's summary ended with a Not done bullet: touch was checked in a headless browser, not on a real phone. script.update-plan carried it into PLAN.md's new ## To check, naming the run's change (breakout-game), in the tick commit.
  • Replan: the replan was shown the list and the rule. It reworded the next item (add-game-sounds) around the sound hooks this run built, and kept the gap, which only a person can check. check-replan passed.
  • Project page: a "To check" section lists the gap. When the plan is done, the same list comes first, as "Left for you to check"; that ordering is covered by the browser journey, and the finished project will show it at the end.
Shipped in #301 (5355515, deployed). It's part of `planned-projects-finish-right`, archived once the change's other issues are verified. Seen on production in run 139 (the first item of cmoriarty/breakout-planned): - **Tick:** run 139's summary ended with a **Not done** bullet: touch was checked in a headless browser, not on a real phone. `script.update-plan` carried it into `PLAN.md`'s new `## To check`, naming the run's change (`breakout-game`), in the tick commit. - **Replan:** the replan was shown the list and the rule. It reworded the next item (`add-game-sounds`) around the sound hooks this run built, and kept the gap, which only a person can check. `check-replan` passed. - **Project page:** a "To check" section lists the gap. When the plan is done, the same list comes first, as "Left for you to check"; that ordering is covered by the browser journey, and the finished project will show it at the end.
Sign in to join this conversation.
No labels
No milestone
No project
No assignees
1 participant
Notifications
Due date
The due date is invalid or out of range. Please use the format "yyyy-mm-dd".

No due date set.

Dependencies

No dependencies set

Reference
cmoriarty/braid#270
No description provided.