docs: publish headers match the wired reality - #22
Merged
Merged
Conversation
- the monoliths' consumer path is the per-package shard (the resolver's primary index form); the cited tebako-pkg verb does not exist — a consumer that wants the monolith shape derives it from the shards (tebako-packages/metanorma's stage_spawned_mirror is the reference) - the source-pin dispatch chain IS wired (tamatebako/python's release-src -> repository_dispatch -> bump-source-pin.yml) - the org PAT's repository selection covers this repo (the receiver's dry run exercised it); the audit job keeps the runner token by choice
ronaldtse
enabled auto-merge (squash)
September 14, 2026 01:56
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
2 participants
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/comments only — no behavior change. Three header inaccuracies corrected:
Phantom verb removed. The publish header cited
`tebako-pkg release-index`as the monolith derivation path — that subcommand does not exist. The accurate statement: the per-package<stem>.manifest.jsonshard IS the release-index entry (the resolver's primary index form); a consumer that wants the monolith shape derives it from the shards locally — tebako-packages/metanorma'stools/stage_spawned_mirroris the reference derivation.The source-pin dispatch chain IS wired. The header claimed "No repository_dispatch trigger yet" — tamatebako/python's
release-srcevent dispatches tobump-source-pin.ymland the chain is live.The PAT's repository selection covers this repo. The
tebako-runtime-python#5deviation notes (PAT 404s, "owner action") are stale — the issue is closed and aworkflow_dispatchno-op dry run against the current pin exercised the auth path end to end. The audit job keeps the runnerGITHUB_TOKENby choice (it mutates only this repo's own release), now documented as such.Verification
ruby -ryamlparses all three workflows.