docs(agents): record that tea 0.14 cannot apply org-level labels #98

Merged

archvillainette merged 1 commits from docs/tea-label-readback-trap into main

2026-08-05 11:38:36 +00:00

Author	SHA1	Message	Date
archvillainetteandClaude Opus 5	27005622e4	docs(agents): record that tea 0.14 cannot apply org-level labels ci / ci (pull_request) Successful in 3m38s Details `tea issues edit --add-labels` and `--remove-labels` resolve names against the repo's own label set only, so `Kind/`, `Priority/` and the rest of the org set match nothing. The command exits 0, prints the issue and changes nothing — no error to notice. Repo-local labels work, which makes the failure look intermittent rather than categorical. Upstream fixed this in v0.15 (`modules/task/labels.go` also queries `ListOrgLabels`); nixpkgs pins 0.14.0, so the note expires on a bump. Also states the general rule the miss came from: re-read a label change before believing it. Exit 0 is not evidence. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-05 12:58:01 +02:00

Author

SHA1

Message

Date

archvillainetteandClaude Opus 5

27005622e4

docs(agents): record that tea 0.14 cannot apply org-level labels

ci / ci (pull_request) Successful in 3m38s

Details

`tea issues edit --add-labels` and `--remove-labels` resolve names against
the repo's own label set only, so `Kind/*`, `Priority/*` and the rest of
the org set match nothing. The command exits 0, prints the issue and
changes nothing — no error to notice. Repo-local labels work, which makes
the failure look intermittent rather than categorical.

Upstream fixed this in v0.15 (`modules/task/labels.go` also queries
`ListOrgLabels`); nixpkgs pins 0.14.0, so the note expires on a bump.

Also states the general rule the miss came from: re-read a label change
before believing it. Exit 0 is not evidence.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-05 12:58:01 +02:00