GloriousFlywheel Yt-Text Hybrid Exception Plan 2026-04-18

GloriousFlywheel Yt-Text Hybrid Exception Plan 2026-04-18

Snapshot date: 2026-04-18

Purpose

Turn the yt-text hybrid classification into a concrete exception plan.

Unlike XoxdWM, yt-text already has real shared-runner authority on its default branch. The remaining work is to separate:

  • durable hosted exceptions
  • hosted paths that still deserve migration review

Live Findings

Authoritative Shared-Runner Surface

On Jesssullivan/yt-text:main:

  • ci.yml runs its inspected jobs on:
    • self-hosted
    • honey
    • tinyland-nix
    • nix
  • release.yml runs:
    • Linux release builds on self-hosted, honey, tinyland-nix, nix
    • Darwin release builds on self-hosted, tinyland-darwin
    • release creation and npm publish on the shared self-hosted Linux lane

That means the repo’s real CI and release authority is already on GloriousFlywheel-backed runners.

Hosted Docs Deploy Split

docs.yml is mixed:

  • build runs on the shared self-hosted Linux and Nix lane
  • deploy runs on ubuntu-latest

The workflow itself documents why:

  • actions/deploy-pages@v5 depends on GitHub OIDC and the current self-hosted Tinyland routing does not make that endpoint reliable

This is not random drift. It is a bounded GitHub Pages deploy exception.

Hosted Fuzz Split

fuzz.yml runs entirely on ubuntu-latest:

  • nightly toolchain setup
  • cargo-fuzz
  • crash artifact upload

Unlike the docs deploy case, the workflow does not currently document a platform reason that this must remain hosted.

So this is a real hosted escape, not yet a clearly durable hosted exception.

Decision

yt-text should stay counted as a real shared-runner downstream canary on default branch.

But its two hosted paths should be treated differently.

Durable Hosted Exception

  • GitHub Pages deploy in docs.yml

Why:

  • the build already dogfoods the self-hosted lane
  • the remaining hosted step is GitHub-native deploy authority
  • the workflow contains an explicit technical reason

Reviewable Hosted Escape

  • fuzz.yml

Why:

  • it is still fully hosted
  • it does not yet carry an explicit platform exception rationale
  • it may be a valid hosted choice, but that choice is not yet codified

Phase 1: Codify The Durable Exception

Actions:

  • keep the Pages deploy job hosted
  • explicitly refer to it as a GitHub-native publication exception in the enrollment and exception docs

Success condition:

  • the docs deploy path stops being cited as evidence that yt-text is unresolved or unclear

Phase 2: Decide The Fuzz Path Intentionally

Options:

  • keep fuzz hosted and document why
  • or migrate fuzz onto a shared lane if nightly toolchain and runtime requirements make sense on tinyland-nix

Recommendation:

  • do not force migration just for metric purity
  • require an explicit keep-hosted or migrate decision instead

Success condition:

  • fuzz.yml is no longer an unexplained hosted escape

Use this wording:

  • yt-text is a real shared-runner canary with a durable GitHub Pages deploy exception and one remaining hosted fuzz decision

That is more honest than:

  • calling it fully converged
  • or treating it as if all hosted paths are equally problematic

Exit Condition

This note can retire once:

  • the Pages deploy exception is codified everywhere it needs to be
  • the fuzz workflow is either migrated or explicitly kept hosted by policy
  • yt-text can be described as hybrid-by-policy without extra explanation

GloriousFlywheel