GloriousFlywheel XoxdWM And Yt-Text Claim Classification 2026-04-18

GloriousFlywheel XoxdWM And Yt-Text Claim Classification 2026-04-18

Updated snapshot date: 2026-04-20

Purpose

Resolve the two remaining Queue A hybrid repos that still distort the current claim surface:

  • Jesssullivan/XoxdWM
  • Jesssullivan/yt-text

Both repos now have real downstream self-hosted authority, but they still do not tell the same product story. The question is how much authority each one actually carries on the non-fork default-branch surface.

Jesssullivan/XoxdWM

Live Findings

Live repo state:

  • Jesssullivan/XoxdWM is a non-fork repo with default branch main
  • tinyland-inc/XoxdWM also exists, but it is a fork
  • Jesssullivan/XoxdWM currently has repo variable:
    • USE_SELFHOSTED=true
  • Jesssullivan/XoxdWM currently reports:
    • 0 accessible Actions runners via the repository runners API
  • the repo runners API now understates live reachability:
    • successful Self-Hosted Fast CI push run 24638888459 on main completed Fast Check (self-hosted) and Fast Build (self-hosted) on xoxdwm-nix
    • those jobs exposed concrete runner names xoxdwm-nix-fcdrg-runner-rqnjr and xoxdwm-nix-fcdrg-runner-8skrt

Current workflow evidence on Jesssullivan/XoxdWM:main:

  • ci.yml runs on ubuntu-latest
  • chapel-ci.yml runs on ubuntu-latest
  • self-hosted-fast.yml now enables its fast CI path when vars.USE_SELFHOSTED == 'true' and runs that path on repo-owned xoxdwm-nix
  • cache-warm.yml, multi-arch.yml, native-deps.yml, nix-cache.yml, packaging.yml, and runner-health.yml now all choose their self-hosted path from vars.USE_SELFHOSTED rather than a fork-specific repo guard
  • vr-hardware.yml still uses raw [self-hosted, honey], but only behind the explicit USE_VR_HARDWARE opt-in

Decision

Jesssullivan/XoxdWM should now be counted as a real non-fork default-branch runner enrollment.

The more important correction is that repo-visible runner inventory is no longer the strongest authority signal for this repo. The Jess repo now has real successful self-hosted execution on main, even though the repository runners API can still report zero visible runners when the scale set is idle. That means:

  • the non-fork repo in the denominator is now also the repo with real self-hosted fast-path authority
  • the fast CI proof is repo-owned on xoxdwm-nix, not yet a clean shared-label convergence story
  • the repo is still hybrid, because other workflows retain hosted fallbacks or explicit hardware-gated exceptions

Recommendation

Count XoxdWM as a real canary again, but describe it accurately:

  • a repo-owned self-hosted canary with a working fast path on main
  • not a fully converged shared-label downstream repo yet
  • a case where recent successful job execution is stronger evidence than idle runner inventory alone

The next clean fixes are:

  • keep the repo-owned fast path green on main
  • decide which additional workflows should converge onto stable shared labels versus remain hosted or hardware-gated exceptions
  • treat recent successful job-label evidence as the first validation surface, with repo runner inventory as a secondary hint rather than the sole gate

Jesssullivan/yt-text

Live Findings

Live repo state:

  • default branch is main
  • workflows on main are:
    • .github/workflows/ci.yml
    • .github/workflows/docs.yml
    • .github/workflows/fuzz.yml
    • .github/workflows/release.yml

Current runner evidence:

  • ci.yml runs its inspected jobs on:
    • self-hosted
    • honey
    • tinyland-nix
  • release.yml runs its inspected Linux jobs on:
    • self-hosted
    • honey
    • tinyland-nix and Darwin release work on:
    • self-hosted
    • tinyland-darwin
  • docs.yml still contains a hosted ubuntu-latest path
  • fuzz.yml runs on ubuntu-latest

Decision

yt-text is still a real shared-runner downstream canary on its default branch.

Unlike XoxdWM, the authoritative CI and release surfaces already run on the shared GloriousFlywheel lanes.

But it is not homogeneous. It remains a hybrid repo with bounded hosted exceptions.

Recommendation

Keep counting yt-text in the real shared-runner default-branch enrollment bucket, but describe it as:

  • a shared-runner canary with hosted docs and fuzz exceptions

Do not describe it as fully converged until those hosted paths either move or are named as durable exceptions in one place.

Net Effect On The Orgwide Story

These two repos now both contribute real authority, but with different caveats.

  • XoxdWM now raises the real default-branch downstream count, but it should still be described as repo-owned and hybrid rather than as full shared-label convergence
  • yt-text remains a valid default-branch shared-runner proof, but only as a hybrid-by-policy repo

That means the safer primary default-branch downstream enrollment read is now:

  • 7 / 39 recent downstream workflow repos

That is about 18%.

If the single explicit branch-authority exception is added:

  • 8 / 39

That is about 21%.

There is no longer a defensible broader cited-repo runner ceiling above 8 / 39 until more repos converge beyond the current canary set.

Exit Condition

This note can retire once:

  • XoxdWM no longer needs an inventory-versus-execution footnote
  • yt-text either narrows or codifies its hosted exceptions
  • orgwide reporting no longer needs an explanation footnote for either repo

GloriousFlywheel