The documented consult-label command applies nothing, because the label is not called consult #881

New issue

Closed

opened 2026-08-17 03:02:37 +00:00 by coilyco-ops · 0 comments

coilyco-ops commented

2026-08-17 03:02:37 +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.

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.

coilyco-ops referenced this issue from a commit

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

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

coilyco-ops referenced this issue from a pull request that will close it,

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

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