GloriousFlywheel XoxdWM Authority Convergence Plan 2026-04-18

GloriousFlywheel XoxdWM Authority Convergence Plan 2026-04-18

Snapshot date: 2026-04-18

Purpose

Turn the XoxdWM activation-mismatch finding into an execution plan.

The problem is no longer “is this repo hybrid?” The problem is:

  • which repo surface should count as authority
  • how to repair the live self-hosted toggle without creating a fake adoption claim

Live Findings

Repo Topology

  • Jesssullivan/XoxdWM is the non-fork repo in the downstream denominator
  • tinyland-inc/XoxdWM also exists, but it is a fork
  • both repos currently report 0 accessible Actions runners via the repository runners API

Workflow Contract Split

On Jesssullivan/XoxdWM:main:

  • ci.yml and chapel-ci.yml run on ubuntu-latest
  • self-hosted-fast.yml, packaging.yml, nix-cache.yml, multi-arch.yml, and vr-hardware.yml only use self-hosted paths when the repository is tinyland-inc/XoxdWM

On tinyland-inc/XoxdWM:main:

  • the same workflow family uses:
    • vars.USE_SELFHOSTED == 'true'
    • tinyland-nix
    • raw [self-hosted, honey] hardware lanes
    • setup-flywheel

Variable And Runner Availability

  • Jesssullivan/XoxdWM currently has repo variable:
    • USE_SELFHOSTED=true
  • the Jess repo currently reports 0 accessible runners
  • the tinyland fork currently also reports 0 accessible runners

Divergence Matters

Live compare state for Jesssullivan/XoxdWM:main vs tinyland-inc/XoxdWM:main:

  • status: diverged
  • fork ahead by: 1
  • fork behind by: 42

That means the fork is not just a clean canonical downstream home. It is materially behind the non-fork repo surface that the orgwide scan would normally count.

What This Means

There are three theoretical fixes, but they are not equally good.

Option 1: Count The Fork As Canonical Authority

Meaning:

  • treat tinyland-inc/XoxdWM as the true self-hosted authority surface
  • keep Jesssullivan/XoxdWM as the public or upstream repo in practice

Problem:

  • this keeps the claim dependent on a fork exception
  • the fork is 42 commits behind, so it is not a clean authority surface
  • the fork also currently reports 0 accessible runners
  • the non-fork repo still stays mostly hosted

Conclusion:

  • not a good primary fix

Option 2: Converge Authority Back Onto Jesssullivan/XoxdWM

Meaning:

  • keep Jesssullivan/XoxdWM as the counted authority surface
  • restore accessible shared runners to that repo
  • remove the github.repository == 'tinyland-inc/XoxdWM' gates from the shared fast-path workflows

Benefits:

  • fixes the denominator and the claim at the same time
  • removes the broken activation mismatch from the main metric
  • does not require repo migration or fork promotion first

Cost:

  • requires real runner availability before the workflow cleanup can merge
  • may require turning USE_SELFHOSTED back off temporarily if runner access cannot be restored immediately
  • hardware jobs still need to be treated as explicit exceptions

Conclusion:

  • best near-term fix

Option 3: Move Canonical Ownership To tinyland-inc/XoxdWM

Meaning:

  • make the fork the real primary repo
  • stop treating the Jess repo as the authority surface

Benefits:

  • aligns the self-hosted path with org ownership

Problem:

  • the fork is currently behind
  • this requires a real repo-authority migration, not just a metric change
  • until convergence happens, the main claim stays muddied

Conclusion:

  • viable only as a later ownership move after branch and content convergence

Phase 1: Fix The Counted Surface

Target:

  • Jesssullivan/XoxdWM

Actions:

  • confirm or restore accessible tinyland-nix runner inventory for Jesssullivan/XoxdWM
  • if that cannot be done immediately, set USE_SELFHOSTED=false again until it can
  • remove repo-name gates that currently restrict self-hosted fast paths to the tinyland fork
  • keep tinyland-nix as the shared fast lane
  • keep VR and raw honey hardware jobs explicit as hardware exceptions, not as generic runner proof

Success condition:

  • the non-fork repo in the downstream denominator actually exercises the shared self-hosted path on main without queueing on nonexistent runners

Phase 2: Reclassify Hardware And Hosted Escapes

Actions:

  • classify raw [self-hosted, honey] jobs as hardware-bound exceptions
  • classify any remaining ubuntu-latest jobs as hosted exceptions or migrate them case by case

Success condition:

  • XoxdWM can be described as a shared-runner repo with named exceptions rather than a broken activation surface

Phase 3: Decide Ownership Later

Only after Phase 1 and Phase 2:

  • decide whether canonical ownership should remain under Jesssullivan
  • or move to tinyland-inc/XoxdWM after real repo convergence

This keeps ownership strategy separate from runner-truth repair.

Recommendation

Do not make the metric depend on the fork.

Near-term, GloriousFlywheel should repair XoxdWM by making Jesssullivan/XoxdWM itself the shared-runner authority surface.

That is the shortest path to:

  • cleaner enrollment reporting
  • less activation-mismatch hand-waving
  • a repo that can actually stay in the downstream denominator honestly

Exit Condition

This note can retire once:

  • Jesssullivan/XoxdWM has the self-hosted toggle and active fast path on main
  • fork-specific repository gates are gone from the shared fast-path workflows
  • orgwide reporting no longer needs the XoxdWM activation-mismatch footnote

GloriousFlywheel