fix: treat HttpStatus.UNKNOWN as retryable

[crleona]

Summary

Implements the suggestion from issue #69 to treat HttpStatus.UNKNOWN responses as retriable, similar to TIMEOUT and FAILED statuses. This enhances the SDK's resilience by preventing immediate event loss for unrecognized server responses.

• ResponseProcessor now pushes events back to storage for retry on HttpStatus.UNKNOWN.
• Updated test_worker.py to assert retry behavior for UNKNOWN responses.
• Added a new unit test in test_processor.py to specifically cover UNKNOWN status retry logic.

Checklist

• Does your PR title have the correct title format?
• Does your PR have a breaking change?: No

---

 

[cursor]

Cursor Agent can help with this pull request. Just @cursor in comments and I'll start working on changes in this branch.
_{Learn more about Cursor Agents}

[macroscopeapp]

Route UNKNOWN HTTP responses to immediate retry in ResponseProcessor.process_response with push_to_storage(events, 0, res) per Issue 69 suggestion

Extend failure handling to treat HttpStatus.UNKNOWN like TIMEOUT and FAILED in processor.py; add unit tests covering unknown status retry in test_processor.py and worker behavior in test_worker.py.

📍Where to Start

Start with the conditional in ResponseProcessor.process_response in processor.py.

---

Macroscope summarized 62998b3. (Automatic summaries will resume when PR exits draft mode or review begins).