fix(ci): make Admin CI refresh failures self-throttling

[lopugit]

What changed

• preserve the last-known Admin CI snapshot while automatic refreshes fail
• coalesce overlapping 5s/30s dashboard polls and exponentially back off failures from 30s to a five-minute cap; manual refresh remains immediate
• classify MongoDB sort-memory code 292 as a private, retryable 503 with Retry-After
• emit stable route/error-code telemetry without query, namespace, document, or credential details
• patch the api.admin-ci-control capability to 1.0.2 and document the new failure contract
• retain the repository-scoped compound index/query fix already merged in fix(auth): recover passkeys and CI dashboard #511

Evidence

• npm --prefix remix run test:ci-control — 41 passed
• npm --prefix remix run test:collections — 16 passed
• capability manifest tests — 2 passed
• targeted ESLint — clean
• npm --prefix remix run build — Vite + Nitro + Vercel output verification passed
• live authenticated Admin CI page: cached failure state remained usable; full desktop and 390px mobile top-to-bottom checks had no horizontal overflow
• Graphify refreshed after rebasing onto current main; hooks and union merge driver verified

Manual checklist

• TESTING.md Admin CI control-plane cached-state/index/failure-path checklist reviewed and extended for MongoDB code 292, retry headers, single-flight polling, exponential backoff, and safe telemetry.

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated (UTC)
thingtime	Ready	Preview	Aug 31, 2026 11:26am

[github-actions]

🤖 Lopu live PR update

Status: ✅ Lopu finished — this PR is closed or merged

Current phase: The resolver branch work is complete

Estimated completion: Done — no further active-work ETA.

Time conversion (UTC source)

Moment	UTC	Los Angeles	Melbourne
Updated	2026-08-31 11:37 UTC (UTC+00:00)	2026-08-31 04:37 PDT (UTC-07:00)	2026-08-31 21:37 AEST (UTC+10:00)

Los Angeles and Melbourne use their real IANA time zones, so PDT/PST and AEST/AEDT offsets change automatically.

Lopu queue and PR pulse

Scope	Metric	Count
Repository	Open PRs	35
Repository	Conflicting	28
Repository	Out-of-date with target	0
Repository	GitHub state unknown	0
Repository	Part of an open stack	0
Repository	Touch files changed by another open PR	36
Repository	Target a non-root branch without an open parent PR	0
This resolver batch	Admitted snapshots	2
This resolver batch	Currently resolving	0
This resolver batch	Waiting	0
This resolver batch	Finished	2

Related PR context

• Stack: No open parent or child PR currently links to this branch.
• Target: main is a repository root/integration branch.
• Changed-file overlap: 5 changed files are also touched by #54, #57, #68, #74, #79, #92, #93, #101, #105, #107, #116, #122, +13 more.

Exact branch pair: main → codex/fix-admin-ci-sort-memory.

Timeline

• 10:52 UTC — Detected that main needs to be merged into codex/fix-admin-ci-sort-memory; assigning the exact snapshot to the resolver queue.
• 10:53 UTC — Still safely queued behind earlier admitted Lopu work; no duplicate resolver was spawned.
• 11:04 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 11:14 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 11:24 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 11:35 UTC — 10-minute check-in: still working — Waiting in Lopu's serialized PR-management lane.
• 11:37 UTC — The resolver worker completed successfully and the PR is no longer open.

Technical run details — optional; this comment is the human-facing source of truth.

[lopugit]

Final merge evidence:

• Full local unit suite: PASS
• Focused Admin CI suite: 41/41 PASS
• MongoDB collection suite: 16/16 PASS
• Capability-manifest suite: 2/2 PASS
• Targeted ESLint: PASS
• Full Vite + Nitro + Vercel output build: PASS
• CodeQL: PASS
• Vercel preview deployment and smoke checks: PASS

The only non-green context is Classify Web CI scope, which was cancelled twice while actions/checkout@v4 was still running at the reusable workflow’s fixed 2-minute job timeout. The advisory checkout of the same PR completed in 1m56s. This is a control-plane timeout before classification, not a product test failure; the protected github-actions workflow is outside this PR’s main-branch scope.

[github-actions]

Lopu repository review

Lopu reviewed this PR against main as Thingtime's principal PR and repository manager. Using Claude Opus 5.

The PR head moved during review, so Lopu preserved the newer branch and did not overwrite it.

The model did not leave a detailed report; inspect this workflow run for the Lopu session log.

View Lopu workflow run

[github-actions]

🤖 Lopu detected an out-of-date PR branch

Status: Work detected — Lopu is taking ownership.

Current phase: Entering Lopu's serialized PR-resolution queue.

Estimated completion: around 11:38 UTC (~20 minutes; this adjusts as the queue moves).

Next automatic check-in: within 10 minutes while work remains active. You can stay on this PR; there is no need to find the Actions run.

Time conversion (UTC source)

Moment	UTC	Los Angeles	Melbourne
Updated	2026-08-31 11:18 UTC (UTC+00:00)	2026-08-31 04:18 PDT (UTC-07:00)	2026-08-31 21:18 AEST (UTC+10:00)
Estimated finish	2026-08-31 11:38 UTC (UTC+00:00)	2026-08-31 04:38 PDT (UTC-07:00)	2026-08-31 21:38 AEST (UTC+10:00)

Los Angeles and Melbourne use their real IANA time zones, so PDT/PST and AEST/AEDT offsets change automatically.

Lopu queue and PR pulse

Scope	Metric	Count
Repository	Open PRs	36
Repository	Conflicting	28
Repository	Out-of-date with target	1
Repository	GitHub state unknown	0
Repository	Part of an open stack	0
Repository	Touch files changed by another open PR	36
Repository	Target a non-root branch without an open parent PR	0
This resolver batch	Admitted snapshots	2
This resolver batch	Currently resolving	0
This resolver batch	Waiting	2
This resolver batch	Finished	0

Related PR context

• Stack: No open parent or child PR currently links to this branch.
• Target: main is a repository root/integration branch.
• Changed-file overlap: 5 changed files are also touched by #54, #57, #68, #74, #79, #92, #93, #101, #105, #107, #116, #122, +13 more.

Exact branch pair: main → codex/fix-admin-ci-sort-memory.

Timeline

• 11:18 UTC — Detected that main needs to be merged into codex/fix-admin-ci-sort-memory; assigning the exact snapshot to the resolver queue.