[griffinmc22]

Success responses with no extracted elements now expose results: {}. Repeated waits return copies of retained results for up to one hour within the existing buffer cap. README examples use .get() for optional elements. Millisecond receivedAt values (>= 100,000,000,000) raise local InvalidRequestError, matching Node's guard; this restriction requires the 0.2.0 minor bump.

The monotonic poll gate rechecks every wake and now measures the gap from request completion so dispatch delays cannot shorten it (3 seconds, or 1 second after a full page). Sent polls still finish independently of departing waiters. New tests confirm existing HTTP error handling preserves normal error types, status and Retry-After for HTML, empty, invalid UTF-8 and non-object JSON bodies, including create retry policy. Main already had the correct Mailman > Settings > Tasks API path; verified the actual arrow-separated path in the built wheel README.

Validation:

• Full unittest suite: 50 passing tests each on Python 3.12 and 3.13; seven new regression tests.
• CI's python -m mypy mailman_tasks: success, four source files.
• python -m build and python -m twine check dist/mailman_tasks-0.2.0*: wheel and sdist pass.
• Python 3.8 syntax parsing, wheel metadata/README checks, and git diff --check pass.
• Python 3.8/3.10 runtimes unavailable locally; GitHub CI covers the full 3.8/3.10/3.12/3.13 matrix.
• No production API calls, other-repository changes, merges or publishing.

Owner steps after merging:

1. Confirm all CI jobs pass and check out merged main in a clean release environment.
2. Install build/twine, then run python -m build and python -m twine check dist/mailman_tasks-0.2.0*.
3. Publish only the 0.2.0 wheel and sdist with python -m twine upload dist/mailman_tasks-0.2.0*, using the owner's PyPI credentials or approved publishing workflow.
4. Verify PyPI version 0.2.0 and its README/settings path. This SDK-only PR needs no application/server deploy.

Nothing has been merged, tagged, released or published.

---

^{Need help on this PR? Tag @codesmith-bot with what you need.}