feat(progress): the buffer before a turn narrates is five seconds #392

Merged
coilysiren merged 4 commits from feat/five-second-buffer into main 2026-08-13 12:22:37 +00:00
Member

Kai asked for the progress threshold to move from three seconds to about five.
One constant changes, because 354 made the other two derive from it.

The cascade is the point rather than a side effect, and the resulting numbers
are worth stating: the edit grid goes 6s to 10s and the long-reply window that
gates thread creation goes 15s to 25s. Both follow from the derivation Kai chose
on 354. That 25s is flagged on the issue, since this ticket asked about the
buffer and quietly decides the window too.

Three tests failed on the value change, which is 359's design working: it pinned
the values separately from the relationships so a base change reports what it
moved instead of moving three things quietly. All three are updated to the new
values and the relationship test needed no change.

The docs did not have the same property. Eight places across two files wrote
3, 6, 9 and 15 out as prose, so "one number to move" was true in Go and false in
Markdown. Those are corrected here, including a cadence table whose rows are the
grid in order.

closes #375

Co-authored-by: Kai Siren coilysiren@gmail.com
Co-authored-by: Claude noreply@anthropic.com

Kai asked for the progress threshold to move from three seconds to about five. One constant changes, because 354 made the other two derive from it. The cascade is the point rather than a side effect, and the resulting numbers are worth stating: the edit grid goes 6s to 10s and the long-reply window that gates thread creation goes 15s to 25s. Both follow from the derivation Kai chose on 354. That 25s is flagged on the issue, since this ticket asked about the buffer and quietly decides the window too. Three tests failed on the value change, which is 359's design working: it pinned the values separately from the relationships so a base change reports what it moved instead of moving three things quietly. All three are updated to the new values and the relationship test needed no change. The docs did not have the same property. Eight places across two files wrote 3, 6, 9 and 15 out as prose, so "one number to move" was true in Go and false in Markdown. Those are corrected here, including a cadence table whose rows are the grid in order. closes #375 Co-authored-by: Kai Siren <coilysiren@gmail.com> Co-authored-by: Claude <noreply@anthropic.com>
feat(progress): the buffer before a turn narrates is five seconds
All checks were successful
ci / test (pull_request) Successful in 30s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
ci / image-build (pull_request) Successful in 19s
4b3d28e8e1
Kai asked for the progress threshold to move from three seconds to about five.
One constant changes, because 354 made the other two derive from it.

The cascade is the point rather than a side effect, and the resulting numbers
are worth stating: the edit grid goes 6s to 10s and the long-reply window that
gates thread creation goes 15s to 25s. Both follow from the derivation Kai chose
on 354. That 25s is flagged on the issue, since this ticket asked about the
buffer and quietly decides the window too.

Three tests failed on the value change, which is 359's design working: it pinned
the values separately from the relationships so a base change reports what it
moved instead of moving three things quietly. All three are updated to the new
values and the relationship test needed no change.

The docs did not have the same property. Eight places across two files wrote
3, 6, 9 and 15 out as prose, so "one number to move" was true in Go and false in
Markdown. Those are corrected here, including a cadence table whose rows are the
grid in order.

closes #375

Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>
Merge branch 'main' into feat/five-second-buffer
All checks were successful
ci / test (pull_request) Successful in 30s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
ci / image-build (pull_request) Successful in 22s
8b0ecd8d88
Merge branch 'main' into feat/five-second-buffer
All checks were successful
ci / test (pull_request) Successful in 33s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
ci / image-build (pull_request) Successful in 18s
7e9b4dffad
Merge branch 'main' into feat/five-second-buffer
All checks were successful
ci / test (pull_request) Successful in 29s
ci / publish-echo-image (pull_request) Has been skipped
ci / publish-observed (pull_request) Has been skipped
ci / image-build (pull_request) Successful in 18s
837bc067b8
Sign in to join this conversation.
No reviewers
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
coilyco-gaming/sirens-echo!392
No description provided.