docs(labels): name the consult label, because `consult` applies nothing #882

Merged

coilysiren merged 1 commit from aos/claude/hs68-consult-label-name into main

2026-08-17 03:09:37 +00:00

coilyco-ops commented

2026-08-17 03:03:07 +00:00

Member

Found by walking into it. AGENTS.md and docs/sirens-echo-consult-gate.md both call the dispatch gate consult, and the file that warns about silent label failures ends with:

Both exit zero. Use --labels consult.

consult is not a label. Not in this repository, not in the coilyco-gaming org. The real name is autonomy/async-consult (id 332), one of an exclusive autonomy/* set alongside autonomy/headless, autonomy/live-collab, and autonomy/epic.

Why this is the same bug that section documents

Running the documented command:

aosguard ops forgejo issue-label add coilyco-gaming sirens-echo 838 --labels consult

Exit code 0. Labels unchanged. The API discards a name that does not exist, exactly as it discards a quoted numeral. The section warns "an ID goes over as "332" and Forgejo reads a quoted numeral as a label name. add then applies nothing" - and then hands you a name that also applies nothing, for the same reason, in the same call.

I only caught it because that section also says to read after the write. Without that habit the issue would have carried a claim of being labelled while sitting unlabelled, which is the fail-closed-and-invisible pair docs/sirens-echo-consult-gate.md calls the worst outcome.

The fix, and the part that is not just a typo

Both spellings corrected, plus one behaviour that neither file mentions and an author should know before running it: the autonomy/* labels are exclusive, so adding autonomy/async-consult removes autonomy/headless rather than sitting beside it.

That is the right outcome - an issue is one or the other - but it is a bigger move than "adds a label" implies, and someone adding consult to a headless issue should know they are taking it out of the headless queue.

Verified on #838 and #576: both went from autonomy/headless to autonomy/async-consult in a single add, with no remove call.

Related - agentic-os#1047, the numeric-label bug this is a sibling of.

This PR is the correction. Both spellings fixed, and both files now state the exclusivity behaviour neither mentioned.

just gate passes.

closes #881

Found by walking into it. `AGENTS.md` and `docs/sirens-echo-consult-gate.md` both call the dispatch gate `consult`, and the file that warns about silent label failures ends with: > Both exit zero. Use `--labels consult`. **`consult` is not a label.** Not in this repository, not in the `coilyco-gaming` org. The real name is `autonomy/async-consult` (id 332), one of an exclusive `autonomy/*` set alongside `autonomy/headless`, `autonomy/live-collab`, and `autonomy/epic`. ## Why this is the same bug that section documents Running the documented command: ``` aosguard ops forgejo issue-label add coilyco-gaming sirens-echo 838 --labels consult ``` **Exit code 0. Labels unchanged.** The API discards a name that does not exist, exactly as it discards a quoted numeral. The section warns "an ID goes over as `"332"` and Forgejo reads a quoted numeral as a label name. `add` then applies nothing" - and then hands you a name that also applies nothing, for the same reason, in the same call. I only caught it because that section also says to read after the write. Without that habit the issue would have carried a claim of being labelled while sitting unlabelled, which is the fail-closed-and-invisible pair `docs/sirens-echo-consult-gate.md` calls the worst outcome. ## The fix, and the part that is not just a typo Both spellings corrected, plus one behaviour that neither file mentions and an author should know before running it: **the `autonomy/*` labels are exclusive**, so adding `autonomy/async-consult` *removes* `autonomy/headless` rather than sitting beside it. That is the right outcome - an issue is one or the other - but it is a bigger move than "adds a label" implies, and someone adding consult to a headless issue should know they are taking it out of the headless queue. Verified on #838 and #576: both went from `autonomy/headless` to `autonomy/async-consult` in a single `add`, with no `remove` call. **Related** - agentic-os#1047, the numeric-label bug this is a sibling of. --- **This PR is the correction.** Both spellings fixed, and both files now state the exclusivity behaviour neither mentioned. `just gate` passes. closes #881

coilyco-ops added 1 commit

2026-08-17 03:03:07 +00:00

docs(labels): name the consult label, because consult applies nothing

ci / image-build (pull_request) Successful in 25s

Details

ci / test (pull_request) Successful in 52s

Details

ci / publish-echo-image (pull_request) Has been skipped

Details

ci / publish-observed (pull_request) Has been skipped

Details

0c2681849b

AGENTS.md's own warning about labels that exit zero having done nothing ends
with `Use --labels consult`. There is no `consult` label in this repository or
its org. The name is `autonomy/async-consult`, and the documented command is
discarded exactly as silently as the quoted numeral the same section warns
about.

Both spellings corrected, in AGENTS.md and the consult-gate page, and both now
say the thing neither did: `autonomy/*` is an exclusive set, so adding consult
removes `autonomy/headless` rather than joining it. That is the intended
outcome and it is a bigger move than "adds a label" reads.

Verified against issues 838 and 576, which each moved from headless to
async-consult in a single add with no remove call.

closes #881

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
Co-authored-by: Kai Siren <coilysiren@gmail.com>
Co-authored-by: Claude <noreply@anthropic.com>

coilyco-ops requested review from coilysiren

2026-08-17 03:03:07 +00:00