T-PMCI-waypost-publish-chain-launch
State: planning/proposed · Impact: high · Complexity: medium
Publish @sksizer/detect-runners and @sksizer/waypost to npm. The in-repo
wiring is complete; nothing outside the repository exists yet.
The ordered launch sequence already lives in
N-PFDK-waypost-launch (docs/planning/notes/N-PFDK-waypost-launch.md) and is checkbox-ready.
This task is the registry’s handle on it and deliberately does not restate the
steps — two homes for one sequence drift.
State verified 2026-08-31:
| Location | Role today |
|---|---|
publish-libs.json | Both packages are roster entries with the right needs chain. Complete. |
packages/ts/detect-runners/.github/workflows/release.yml | Mirror-side publish pipeline, shipped inside the snapshot. Complete. |
packages/ts/waypost/.github/workflows/release.yml | Same, plus site.yml for Pages. Complete. |
docs/planning/notes/N-PFDK-waypost-launch.md | The ordered sequence. Nothing in it has been run. |
Neither package is on npm, and no mirror repository exists for command-seam,
detect-runners or waypost. OSS_PUBLISH_TOKEN exists on sksizer/dev
dated 2026-07-18, predating all three mirrors, so it almost certainly does not
cover them — and publish-lib.yml skips the push with a message rather than
failing, so a PAT that is silently too narrow looks like success.
Proposed
Section titled “Proposed”Both packages installable from npm with provenance, and the docs site served from the waypost mirror’s Pages.
Approach
Section titled “Approach”Follow docs/planning/notes/N-PFDK-waypost-launch.md. Publish order is
command-seam, then detect-runners, then waypost — not a preference:
each snapshot builds standalone and resolves its dependency from the registry,
so an out-of-order publish fails in the mirror’s own CI.
- Preconditions: create the three mirror repositories, widen or reissue
OSS_PUBLISH_TOKENto cover them, and confirm the names are still free. - Publish
command-seam, which is not on this package’s roster but blocks both of these. - Rehearse with
gh workflow run publish-lib -f lib=...before any tag. - Release
detect-runners, thenwaypost. - Enable Pages on the waypost mirror.
Most of this needs account access rather than repository access: creating repositories, scoping a fine-grained PAT, and configuring npm trusted publishing.
| Location | Kind | Change |
|---|---|---|
docs/planning/notes/N-PFDK-waypost-launch.md | modify | Tick its boxes as the sequence is run. |
No source change is expected. If one turns out to be needed, the snapshot build was not actually standalone, which is its own finding.
Acceptance criteria
Section titled “Acceptance criteria”- AC-1:
bun add -g @sksizer/waypostin an empty directory, thenwayin a real repository, lists tasks. - AC-2:
bunx @sksizer/detect-runners --jsonemits a valid catalog. - AC-3: Both npm package pages show provenance.
- AC-4: The site loads at its Pages URL and its install snippet works as written.
Out of scope
Section titled “Out of scope”- The Cloudflare Pages mirror. Optional, and the runbook marks it later.
Dependencies
Section titled “Dependencies”command-seammust be published first and is not on this package’s roster.
Discovery context
Section titled “Discovery context”Drafted as WP-0001 under docs/packages/ts/waypost/planning/tasks in
#1616; moved here so the launch is
visible to the registry rather than only to the package.