GloriousFlywheel yt-text Dogfood Playbook 2026-04-16

GloriousFlywheel yt-text Dogfood Playbook 2026-04-16

Snapshot date: 2026-04-16

Purpose

Capture the first concrete yt-text readout under the downstream adoption lane so runner-health facts do not stay trapped in terminal output.

GitHub owner: #210

Why yt-text Matters

Jesssullivan/yt-text is one of the clearest live user-repo consumers of the shared tinyland-nix lane:

  • it is private but directly uses the honey / tinyland-nix shared runner set
  • it runs real Rust, docs, and release-flavored workflows instead of a synthetic platform smoke test
  • it is a better signal for organic adoption health than the platform repo alone

Observed Workflow Reality

From direct workflow and run inspection on 2026-04-16:

  • .github/workflows/ci.yml and .github/workflows/docs.yml both target: runs-on: [self-hosted, linux, x64, honey, tinyland-nix, nix]
  • the live CI run used GloriousFlywheel runners successfully:
    • Check + Clippy + Fmt ran on honey-yt-text
    • Tests ran on honey-yt-text-3
    • Check po-token feature ran on honey-yt-text
    • Docs ran on honey-yt-text-2
    • Nix Build ran on honey-yt-text-4
  • this confirms runner auto-pickup is working for Jesssullivan/yt-text
  • the workflow uses raw nix commands today rather than the canonical GloriousFlywheel nix-job or explicit Nix bootstrap pattern

Current Problem Shape

The main issue is not runner matching.

The main issues are workflow shape and capacity efficiency:

  • self-hosted Nix bootstrap is still implicit in the workflow
  • the docs deploy path was consuming tinyland-nix capacity even though the Pages publish step does not need a scarce Nix runner

Local Optimization Patch

Prepared locally on 2026-04-16 in /tmp/yt-text:

  • add DeterminateSystems/determinate-nix-action@v3 to self-hosted tinyland-nix jobs in:
    • ci.yml
    • docs.yml
    • release.yml
  • move the Pages deploy job in docs.yml to ubuntu-latest
  • keep the actual docs build on tinyland-nix
  • move the combined Check + Clippy + Fmt job in ci.yml from tinyland-nix to tinyland-nix-heavy so the first real heavy Rust/Nix dogfood proof stays scoped to the job that actually exercises the higher memory envelope

Verification for the local patch:

  • git -C /tmp/yt-text diff --check passes
  • the patched workflow YAML parses cleanly
  • draft PR opened: Jesssullivan/yt-text#67

yt-text is now the cleanest immediate heavy-Nix dogfood target because:

  • it already uses explicit workflow-owned Nix bootstrap
  • its Rust clippy lane is a real organic workload rather than a synthetic benchmark
  • the patch can move only the heavy check/clippy/fmt lane to tinyland-nix-heavy while leaving tests, docs, and general Nix build paths on the baseline tinyland-nix lane

Acceptance Criteria

  • yt-text is recorded as a healthy live shared-runner consumer
  • the platform story distinguishes runner pickup health from workflow-shape inefficiency
  • the repo is available as a tranche-2 user-repo canary for Nix bootstrap and runner-capacity optimization work

GloriousFlywheel