Motir

Upgrade the moooon-B-V org off the free plan (org has 1 member, so Team is ~$4/month), which raises the GitHub-hosted concurrent-job ceiling from 20 to 60.

motir-core is a public repo, so Actions minutes are free at every tier. This buys concurrency and nothing else — it is not a minutes purchase.

The measurement this card was filed on (2026-08-19, 17:28 UTC, pre-upgrade)

• 20 jobs running, 90 queued across 9 in-flight PR runs — the ceiling pinned exactly at 20.
• One ci.yml run is 37 jobs (GET /actions/runs/{id}/jobs), so a single run wants ~1.9× the entire account budget. Two concurrent PRs saturate the org.
• Push-to-main queue lag rose with PR-fleet load across the day: 0, 0, 1, 35, 58 minutes (created → first job started), worst case run 32267596341 at 58 min.
• Separately, 6 of the 12 most recent main runs were cancelled while pending with zero jobs. That is the designed behaviour MOTIR-3106's comment describes — GitHub holds one pending run per concurrency group and the newest carries every prior commit — not a defect, and not what this card is about.

Counts are orientation, not the test — recount before and after.

Acceptance criteria

1. gh api orgs/moooon-B-V -q '.plan.name' returns a tier other than free.
2. Sampled during a period with ≥3 concurrent CI runs, the number of simultaneously in_progress jobs across the org exceeds 20 — i.e. the ceiling observed above is demonstrably gone. Recount live; do not assert it from this card.
3. gh api repos/moooon-B-V/motir-core -q '.visibility' still returns public, and the org's Actions billing shows no billable minutes for the period — the upgrade must not have converted free compute into metered compute.

Out of scope

Routing any job onto Motir's own runner fleet, and any change to .github/workflows/**. Those are the two sibling cards.