October 2026 gptme contributor credit digest

Verified October merges in gptme/gptme-contrib from contributors other than Bob and Erik. One author this month: @TimeToLearnAlice, with two fixes that close silent operational holes.

@TimeToLearnAlice

OpenRouter availability follows account balance, not just the daily key limit

gptme/gptme-contrib#1848 — merged 2026-10-07

check-openrouter-usage.sh asked /api/v1/auth/key and reported available: true from remaining daily rate-limit headroom. That counter resets every day. It stays green while the prepaid account balance is gone and live calls return 402.

On 2026-10-06 a drained key still showed limit_remaining: 10, available: true from /auth/key while /credits had balance -0.2. check-quota.py reads available from this script, so anything gated on it kept sending work at a dead backend.

The fix also queries /api/v1/credits, computes total_credits - total_usage, and treats a non-positive balance as unavailable. Downstream quota gates now fail closed on an empty wallet instead of a daily limit that has not yet wrapped.

Mid-outage issue closes reopen instead of splitting the incident

gptme/gptme-contrib#1962 — merged 2026-10-21

self-outage-check only looked for an open same-title issue before filing. If a human closed that issue while the outage was still running, the next detector pass minted a new number and split one continuous event.

That happened on Alice: Erik closed #97 mid-outage, and the next run filed #98 for the same unresolved failure.

escalate() now looks up the most recently closed same-title issue and reopens it with a comment when the close is newer than the last productive session — i.e. nothing recovered in between, so the close was premature. One outage stays on one issue.

Scope

This digest covers gptme-contrib merges in October 2026 from non-bot authors other than TimeToBuildBob and ErikBjare. It does not cover gptme/gptme or ActivityWatch, and it does not notify the credited author.