GloriousFlywheel Queue C Migration Candidate Truthing 2026-04-18

Snapshot date: 2026-04-18

Purpose

Resolve the current truth of the three Queue C repos from live workflow files:

• tinyland-inc/betterkvm
• Jesssullivan/tinyclaw
• Jesssullivan/remote-juggler

The goal is not to argue that they are good future candidates. The goal is to classify what they actually are today.

Live Findings

tinyland-inc/betterkvm

Live repo state:

• default branch is sid/initial-scaffold
• current workflow files on that branch are:
  • .github/workflows/ci.yml
  • .github/workflows/release.yml
  • .github/workflows/secrets-scan.yml

Current runner evidence:

• ci.yml declares:
  • NIX_RUNNER: ubuntu-latest
  • comment: Switch to tinyland-nix when ARC runners are deployed
• the inspected jobs in ci.yml all run on ubuntu-latest
• release.yml also runs on ubuntu-latest

Decision:

• betterkvm is hosted-only on its current default branch
• it is not current runner enrollment
• it remains a migration candidate, but only after default-branch and branch intent stabilize

Jesssullivan/tinyclaw

Live repo state:

• default branch is main
• current workflow files on main include:
  • .github/workflows/build.yml
  • .github/workflows/pr.yml
  • .github/workflows/release.yml
  • .github/workflows/ghcr.yml
  • .github/workflows/upstream-sync.yml

Current runner evidence:

• build.yml runs on ubuntu-latest
• pr.yml runs all inspected jobs on ubuntu-latest
• release.yml runs on ubuntu-latest
• ghcr.yml runs on ubuntu-latest

Decision:

• tinyclaw is fully hosted on main
• it should stay outside current runner-adoption claims
• it should only return to the migration queue if there is an explicit product reason to move one authoritative path onto ARC

Jesssullivan/remote-juggler

Live repo state:

• default branch is main
• current workflow files on main include:
  • .github/workflows/ci.yml
  • .github/workflows/nix-ci.yml
  • .github/workflows/containers.yml
  • .github/workflows/release.yml
  • .github/workflows/tofu-apply.yml
  • .github/workflows/gtk-gui.yml
  • additional hosted utility workflows
• tinyland-inc/remote-juggler also exists, but it is a fork and should not be counted as a separate enrollment surface

Current runner evidence:

• ci.yml runs on ubuntu-latest, ubuntu-24.04-arm, macos-latest, and macos-15
• nix-ci.yml uses Attic, but its inspected Linux jobs still run on ubuntu-latest and its Darwin jobs on macos-15
• containers.yml, release.yml, tofu-apply.yml, and gtk-gui.yml all use hosted runners in the inspected paths

Decision:

• remote-juggler is not a runner-enrolled repo today
• it is a hosted CI repo with Nix and Attic acceleration
• it should be declassified from the current runner story and treated as cache-acceleration or build-acceleration adjacent work unless a specific authoritative lane is intentionally moved to tinyland-nix

Updated Queue C Read

The three Queue C repos do not deserve the same treatment.

Keep As Later Migration Candidate

• tinyland-inc/betterkvm
  • only after default-branch normalization and explicit branch intent

Remove From Current Runner Story

• Jesssullivan/tinyclaw
• Jesssullivan/remote-juggler

These are not “almost enrolled.” They are hosted repos today.

Recommendation

Update the enrollment queue so that:

• betterkvm remains the only active Queue C runner candidate
• tinyclaw moves to hosted-by-current-policy unless product priorities change
• remote-juggler moves out of runner-enrollment reporting and into cache-acceleration or later migration discussion

Exit Condition

This note can retire once:

• betterkvm either migrates or is declassified
• tinyclaw has an explicit keep-hosted or migrate decision
• remote-juggler moves one authoritative lane onto ARC or is permanently treated as hosted plus cache acceleration