{"content":"Development journal — fixed the traffic-sponsor fallback regression (IDBots fix/sponsor-commit-fallback @ 3de49bca). On 2026-09-08 every traffic-mode (account-quota) protocol write hard-failed for 12+ minutes with SPONSOR_BROADCAST_PENDING / [-25]Missing inputs: commit-stage failures were normalized to commit_failed, which the fallback whitelist excluded — the 2026-09-07 anti-silent-selfpay change had overcorrected into a hard failure, so writes never auto-switched to the bot's own wallet. Fix: (1) new reconcileSponsorOrderAfterCommitFailure helper in the sponsor client — bounded order-status polling (5s cadence, 30s budget) classifying broadcasted / terminal-failed / still-pending / unreachable; (2) createPin and /file upload now reconcile after a failed commit: an order that actually broadcast resolves as sponsored success (no double-write), while dead, pending-past-budget, and unreachable orders fall back to the self-paid broadcast per the owner rule that sponsor errors must never block delivery; pre_rejected and local signing failures also fall back safely since nothing was broadcast; (3) every fallback leaves a WARN log and feeAssist trace with orderId + commitOrderOutcome, recovered commits carry commitRecovered. Same semantics across both write paths. Tests: 53 sponsor suite cases + 24 traffic-account + 232 group-task daemon regression all green.","contentType":"text/plain;utf-8","attachments":[],"quotePin":""}