Skip to content

fix(timer): preserve the original retry intent - #4664

Merged
hellofrequencylab merged 5 commits into
mainfrom
codex/timer-retry-intent-20261104
Nov 4, 2026
Merged

hellofrequencylab merged 5 commits into
mainfrom
codex/timer-retry-intent-20261104

Conversation

@hellofrequencylab

Copy link
Copy Markdown
Owner

What

Mindless retries now replay the original practice, movement mode, partial-session resume and queue leg after a load failure. Be Still history retries retain the original attended flag alongside their original timing and practice arguments.

Why

“Try again” previously opened a generic sit, so retrying a failed queue leg could restart the queue or lose the chosen practice. A partial Be Still finish originally sent with attended=false could retry using the default true.

Risk

Small client-state repair. Existing close and stale-load guards remain; the functional state update does not reopen a closed overlay. The movement engine already retained its finish options and is unchanged. No server timer, duration, reward or WAM rules change. TIMER-RETRY-INTENT remains open for release verification. Daniel specifically approved the exact four-test provider regression patch.

How to verify

Normal main merge to 2d5b549; exact integrated head 906a34e.

  • 79 tests in nine focused timer/action/live-session suites pass, including four approved retry regressions.
  • Focused lint, whitespace, static backlog and one-list checks pass. Current open-PR file listings show no shared timer or ledger-row conflict.
  • Temporary proof covers the actual Be Still saved-argument/retry seams with attended=false. Pristine-base controls reproduce the original losses while persisted movement recovery still passes. This is bounded source-seam proof, not a rendered full Be Still finish flow.
  • Full TypeScript was not rerun alongside the shared full-tree check; required CI, exact READY preview and browser/mobile lifecycle checks remain necessary. No real session was completed and no production data was changed locally.

Root owns the merge sequence. Auto-merge is off.

@vercel

vercel Bot commented Nov 4, 2026 •

Copy link
Copy Markdown

The latest updates on your projects. Learn more about Vercel for GitHub.

Project Deployment Actions Updated
frequency-web Ready Ready Preview Nov 4, 2026 8:17pm UTC

Request Review

@hellofrequencylab
hellofrequencylab merged commit a6ad4cd into main Nov 4, 2026
17 checks passed

This branch was successfully deployed

1 active deployment
Preview — 1c0e38be Deployed Nov 4, 2026 by vercel[bot]
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants