Skip to content

Recover legacy notification transport backoff - #189

Merged
ael-dev3 merged 1 commit into
mainfrom
codex/notification-transport-recovery
Aug 4, 2026
Merged

Recover legacy notification transport backoff#189
ael-dev3 merged 1 commit into
mainfrom
codex/notification-transport-recovery

Conversation

@ael-dev3

@ael-dev3 ael-dev3 commented Aug 4, 2026

Copy link
Copy Markdown
Owner

Summary

  • recognize the exact legacy broad-transport diagnostics written by the affected Cloudflare deployment
  • let an authenticated operator bring only that generation’s persisted fifth retry forward after the 30-second Farcaster floor
  • preserve the stable notification ID, current admission resolver check, stored backoff lifetime, and six-attempt ceiling
  • keep current classified failures on their normal backoff

No SpacetimeDB schema, frontend, game state, secret, or notification token changes are included.

Verification

  • pnpm --dir services/auth-bridge run check
    • 310 unit tests
    • 12 Workerd tests
    • both TypeScript checks
  • git diff --check
  • exact CI gitleaks history scan: no leaks

@ael-dev3
ael-dev3 merged commit 044759d into main Aug 4, 2026
5 checks passed
@ael-dev3
ael-dev3 deleted the codex/notification-transport-recovery branch August 4, 2026 00:50
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.

1 participant