chore: release 1.1.1

Patch rather than minor: the error surface is unchanged and no public
signature moved. What downstream must notice is timing, not types — the
worst-case call duration rises to roughly max_attempts * timeout_s now
that the retry budget actually applies.

Pre-release review caught an overreaching promise in the changelog entry:
the 429 bound holds only when the stall verdict can fire at all, i.e. when
the whole scope has no progress. The verdict is a conjunction, so a call
does not die while other calls in the scope are still producing — by
design — which leaves no hard per-call ceiling in that case. That property
predates this fix and is now stated with its precondition instead of as an
unconditional guarantee.

The wiki sync in the release checklist is a no-op again: the doc site has
been down since 2026-08-02 and its landing page names CHANGELOG.md as the
version source of truth, which this commit updates.

src/polygateway/__init__.py

@@ -32,7 +32,7 @@ from polygateway.types import (
     SourceConfig,
 )
 
-__version__ = "1.1.0"
+__version__ = "1.1.1"
 
 __all__ = [
     "DEFAULT_PROFILES",

src/polygateway/middleware/retry.py

@@ -355,6 +355,8 @@ class RetryMW:
             await self._settle_and_release(permit, 0)
         return None, gate_rejections
 
+    # —— 背压与 stall 判死(CHS governance.py:270-285)——
+
     async def _stalled(self, clock: StallClock) -> bool:
         """双条件 stall 判死(CHS governance.py:270-281): 本地累计等待与全局
         无进展**同时**超窗才判死——本地 monotonic 与后端时钟刻意不混用。