[Gastown] GitHub token expiry escalations repeat without resolution path in UI

[markijbema]

What happened?

The Mayor keeps receiving repeated medium escalations for "GitHub token expired — cannot push branch" from rig 1c19c055-603a-4e48-8d4d-c14831ce034e. The escalations repeat every few minutes even after the Mayor has acknowledged and explained the issue. There is no way for the Mayor to resolve this (it requires user action to refresh credentials), but the escalation system keeps firing it repeatedly with no mechanism to snooze/dismiss/acknowledge it from the Mayor side. This creates noise and fills the conversation with repeated identical escalation messages. A resolution path or acknowledgement mechanism should exist so the Mayor can suppress repeat escalations for the same root cause until the underlying issue is fixed.

Area

Mayor / Chat

Context

• Town ID: 80803a9a-f944-40ee-990a-8a09603b019e
• Agent: Mayor (9b5bc803-53c5-4564-93a0-2600bfce4eef)
• Rig ID: 1c19c055-603a-4e48-8d4d-c14831ce034e

Recent Errors

GitHub token expired — cannot push branch gt/toast/c5df4379 (repeated 4+ times in same session)

Filed automatically by the Mayor via gt_report_bug.

[jrf0110]

Mayor debug sweep diagnostic note (2026-04-05 UTC)

Per-issue checklist

• Symptom: mayor UI repeatedly receives identical GitHub token expiry escalations without any mayor-side dismiss/snooze path
• Subsystem: escalation dedup + mayor incident surfacing (gt:core + gt:mayor)
• Expected evidence: active unresolved escalation source or a debug trace showing why the same root-cause continues to emit

Documentation / access findings

• Attempted to retrieve cloudflare-gastown/docs branch gastown-staging directly during this sweep.
• git clone --branch gastown-staging --single-branch https://github.com/cloudflare-gastown/docs /tmp/cloudflare-gastown-docs failed with fatal: could not read Username for 'https://github.com': No such device or address.
• gh repo view cloudflare-gastown/docs and gh api repos/cloudflare-gastown/docs/contents?ref=gastown-staging both returned repository-not-found / 404.
• Because the docs repo is inaccessible from this environment, the exact endpoint documentation and request format could not be re-verified live in this run.

Diagnostics attempted from this environment

• No staging debug endpoint calls could be executed in this run because the required doc/source-of-truth for endpoint paths and auth contract was inaccessible.
• Blocking step recorded exactly as encountered above; no payload beyond the repository access attempts was available.

Conclusion

• Confirmed vs unconfirmed: Unconfirmed in this run due to blocked access to staging debug documentation.
• Likely fault domain: gt:core (dedup/escalation lifecycle) with mayor/UI surfacing impact in gt:mayor.
• Immediate next engineering action: restore access to cloudflare-gastown/docs gastown-staging for the debug sweep runner, then re-run the staging endpoint probes and capture source/correlation IDs for the repeated token-expiry escalation emitter.