feat: queue telegram requests with rate limits (#54)

2026-01-05 12:00:37 +04:00
parent c64913ed6d
commit 2d8fbc8a5a
9 changed files with 898 additions and 152 deletions
@@ -247,7 +247,7 @@ The bridge MUST:
 * Resolve resume token (per §3.4)
 * Schedule runs per thread (per §6.2)
 * Start runner execution with cancellation support
-* Maintain a progress message with rate-limited edits
+* Maintain a progress message while avoiding excessive edits
 * Publish a final message containing status, answer, and resume line (when known)
 * Support `/cancel` for in-flight runs

@@ -280,7 +280,7 @@ Runs that start as new threads:
 ### 6.3 Progress message behavior

 * The bridge SHOULD send an initial progress message quickly (e.g., “Running…”).
-* The bridge SHOULD edit the progress message no more frequently than every **2 seconds**.
+* The bridge SHOULD avoid excessive edits and respect transport constraints (implementation-defined).
 * The bridge SHOULD skip edits when rendered content is unchanged.
 * Once `started` is observed, the progress view SHOULD include the canonical ResumeLine.