T05-05-TASK-01 Separate persistence failures from network failures #516

New issue

Copy link

New issue

Copy link

Closed

#520

Closed

T05-05-TASK-01 Separate persistence failures from network failures#516

#520

Copy link

Description

edithatogo

opened on Aug 10, 2026

Issue body actions

Track: T05-05nParent: #479n`nImplement a distinct rate-limit persistence boundary so persistence failures cannot be misclassified as fetch failures or replay HTTP requests.

Activity

1. edithatogo

   added a parent issue on Aug 10, 2026

   • Distinguish rate-limit state persistence failures from network failures #479
2. edithatogo

   closed this as completedin a302481on Aug 10, 2026
3. github-project-automation

   added this to Substack CLI frontier-mainline maturity programme to 1.0on Aug 10, 2026
4. github-project-automation

   moved this to Done in Substack CLI frontier-mainline maturity programme to 1.0on Aug 10, 2026

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

Labels

No labels

No labels

Projects

• Substack CLI frontier-mainline maturity programme to 1.0

  Status

  Done

  Show more project fields

Milestone

No milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions

• Open in GitHub Copilot app