GloriousFlywheel Npm Publish Family Hosted Archive Policy 2026-04-18

GloriousFlywheel Npm Publish Family Hosted Archive Policy 2026-04-18

Snapshot date: 2026-04-18

Purpose

Resolve the remaining ambiguity around the hosted npm-publish.yml family in Queue B.

The question is not whether these repos use ci-templates. The question is whether they are still a live enrollment surface that deserves self-hosted migration energy.

Live Findings

The current package repos are:

  • tinyland-inc/vite-plugin-a11y
  • tinyland-inc/tinyland-rate-limit
  • tinyland-inc/tinyland-physics
  • tinyland-inc/tinyland-color-utils
  • tinyland-inc/tinyland-a11y-engine

Live repo metadata:

  • all five repos are archived
  • all five still default to main

Live workflow evidence on main:

  • each repo still uses:
    • tinyland-inc/ci-templates/.github/workflows/npm-publish.yml@main

Live reusable workflow evidence:

  • tinyland-inc/ci-templates/.github/workflows/npm-publish.yml runs all inspected jobs on ubuntu-latest
    • build-and-test
    • publish-gpr
    • publish-npm

Decision

This repo family should be treated as:

  • hosted template consumers
  • archived package repos
  • out of the active runner-enrollment migration queue

These repos still matter for reporting honesty, because raw template usage could still overcount enrollment.

But they do not currently deserve the same migration energy as active repos.

What Changes

Reporting

Count this whole family in:

  • hosted template consumers

Do not count this family in:

  • real runner enrollment
  • active runner migration candidates

Queueing

Move this family from “active Queue B migration surface” to:

  • hosted-by-policy archive surface

The active Queue B work should stay focused on:

  • template mode reporting
  • ci-templates capability boundaries
  • active repos where template mode still affects the current platform claim

Recommendation

Use this wording in PM and status surfaces:

  • the npm-publish.yml package family remains hosted by current policy and is archived
  • it still belongs in the hosted template consumer count
  • it does not currently belong in the active migration queue

Exit Condition

This note can retire once:

  • the archived family is no longer discussed as an active migration target
  • hosted template consumer reporting already makes this family visible by default

GloriousFlywheel