clad2 37e31ffd85 fix(labels): refuse an unset API root, name transport failures, update the docs ... Three corrections from @codex-reviewer-andresmgsl's review of 935a813. 1. `api="${GITHUB_API_URL:-https://api.github.com}"` guessed GitHub when the variable was absent — driven with a recording curl, it reported success after POSTing to api.github.com from this forge. That is the "Never 'probably github'" rule, and the same unset-environment refusal #201 just established for docs-sync. It now refuses before any request, and the test asserts zero calls were made: refusing after a POST is not refusing. 2. The "never silenced with || true" invariant was still asserted by grepping the gh line this port removed, so it passed on any REST implementation including one that swallows a failed POST. It is rebound behaviourally: a curl that dies at the transport must fail the step. Doing that revealed the step failed with a bare exit 7 and no sentence, so it now names the failure — owning the diagnostic is the whole point of the surrounding code. 3. docs/CONSUMERS.md and both caller comments still described `gh workflow run` as the mechanism. They describe the REST dispatch now, and the manual bootstrap command carries a forge-neutral curl form beside the gh one: a cross-forge runbook that sends this forge to a missing binary is wrong even where the prose around it is right. Refs #205		2026-08-05 17:16:30 +00:00
..
.gitkeep	ci: scaffold test and lint workspace	2026-07-22 16:56:25 +00:00
CONSUMERS.md	fix(labels): refuse an unset API root, name transport failures, update the docs	2026-08-05 17:16:30 +00:00
UPSTREAM-SYNC.md	docs(upstream-sync): the inventory names docs-sync, which #201 makes forge-deciding (#200)	2026-08-05 15:15:35 +00:00
VENDORED.txt	docs: correct release gate mechanics	2026-08-03 18:26:58 +00:00