docs(releasing): document roadmap tracking pipeline + clarify label canonicity#138
Merged
Conversation
…anonicity Three small changes wrapping up the roadmap-pipeline arc that shipped 2026-05-27 → 2026-05-29: 1. docs/RELEASING.md — new §11 "Roadmap tracking pipeline" walking through the six-step chain end-to-end. Covers skill triggers, skip conditions, auto-discovery details, server-side dependencies, and an operator quick-reference table for the common "release shipped, what now?" failure modes. 2. docs/RELEASING.md §6.2 — `roadmap_item_slug` added to the workflow_dispatch inputs table. Was a real input on promote.yml but not previously documented. Cross-references §11 for the auto-discovery mechanism that usually obviates needing it. 3. .claude/skills/pr-roadmap-link/SKILL.md — explicit "the label is canonical, the trailer is human-readable" note in the lede. Was implicit in the code (release-promote reads labels only) but wasn't documented anywhere outside PR descriptions; future-readers reconstructing the pipeline have a one-line answer now. No code changes. Pure docs + skill prose. The roadmap chain is already live in tray-v1.8.11 / v1.8.12; this just makes the chain self-documenting for the next operator who arrives without having been through this session. Memory entry [[roadmap-pipeline-chain]] saved in the same arc.
ntatschner
force-pushed
the
docs/roadmap-pipeline-chain
branch
from
93cc5ff to
587a987
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
docs/RELEASING.md§11 (new) — End-to-end walkthrough of the roadmap tracking pipeline shipped across PRs feat(roadmap): handle issues webhook for fast label propagation #112/feat(roadmap): operator tooling — drafts publisher, project normalizer, auto-publish, tracking skill #113/feat(roadmap): promote rc to a first-class channel #125/fix(roadmap-emit): soft-fail 400 unknown-channel like 404 unknown-slug #126/feat(roadmap): HMAC-keyed bulk-publish endpoint + CI script #128/feat(.claude): pr-roadmap-link skill — lock slug at PR-create time #129/feat(release-promote): auto-discover slug from merged PR roadmap labels #130/fix(auto-publish): compose URL from STARSTATS_API_URL instead of a separate secret #133.docs/RELEASING.md§6.2 —roadmap_item_slugadded to the workflow_dispatch inputs table (was a real input but undocumented)..claude/skills/pr-roadmap-link/SKILL.md— One-paragraph clarification that theroadmap/<slug>label is the canonical signal; the trailer is human-readable only.Why
Across the recent arc, the roadmap pipeline became fully self-sufficient: feature-start skill → PR-create skill → auto-discovery at promote-time → HMAC publish at release-time, with zero operator typing in the middle. But the chain wasn't documented anywhere outside PR descriptions. Future operators arriving cold would have to reconstruct it from
git log+ reading multiple PR bodies.This PR makes the chain self-documenting. New §11 explains the six steps + cross-references the relevant scripts/skills/endpoints. §6.2 closes a small doc gap where
roadmap_item_slugwas a real workflow input but absent from the inputs table. The skill clarification preempts the foot-gun where someone manually edits a PR body trailer but forgets the label (only the label drives discovery).What does NOT change
tray-v1.8.11+v1.8.12.release-promote.mjsauto-discovery code itself is unchanged from PR feat(release-promote): auto-discover slug from merged PR roadmap labels #130.pr-roadmap-linkskill's flow steps are unchanged; only the lede was updated to emphasize label canonicity.Test plan
name:+description:) unchanged → auto-trigger behavior preserved.claude/skills/discovery onmainDocs-only PR — should ramp through the channels cleanly with no behavior to validate. Path filter on
promote.ymlmay or may not auto-trigger an alpha bump (docs/is in the skip list, but.claude/skills/is not, so it'll likely tag the tray track).