6 Commits

Include renames

Author	SHA1	Message	Date
archvillainetteandClaude Opus 5	12b4713b95	docs(agents): tea api needs a token, not a different verb ... Corrects the bullet added in the previous commit. It read "tea api can read but not write", which described the symptom rather than the rule. `tea api` sends only the login's `token:` field and never signs requests with the SSH key, so on an SSH-only login every authenticated call fails with `{"message":"token is required"}` — writes and authenticated reads alike. Anonymous reads against these public repos still succeed, which is why it looked like a read/write split. Adding a token to the login makes the raw endpoints work in both directions, confirmed by a POST to the issue labels endpoint that applied and read back. The `tea issues` / `tea pr` subcommands authenticate over SSH and keep working with no token at all. That asymmetry is the confusing part, so it is now stated outright. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-05 17:57:57 +02:00
archvillainetteandClaude Opus 5	335680889b	docs(agents): tea 0.15 applies org labels; tea api still cannot write ... Mirrors ShadowsOverWestgate/sow-topdata@8c5f4d8 into this repo's copy of the shared agent docs. nixpkgs now ships tea 0.15.1, so `tea issues edit --add-labels` applies `Kind/*` and the rest of the org set. The 0.14 ceiling stays documented as history for anyone on a pinned older tea. Two things outlived the bump. `tea api` cannot write at all — any `--method POST`/`PATCH` returns `{"message":"token is required"}`, while GETs succeed anonymously because these repos are public. Both files prescribed a `tea api` labels endpoint for labelling an existing issue; that recipe has never worked. It now points at `tea issues edit`. The read-back rule stays, with its reasoning corrected. The note had grown a claim that `tea issues ls` returns stale labels for several seconds after a successful edit, and warned against concluding failure from an immediate read. That was the 0.14 silent no-op misread as replication lag — the read-back was accurate both before and after the bump, and waiting it out would convert a real failure into an assumed success. Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>	2026-08-05 17:46:34 +02:00
archvillainette	a02e06d644	docs(agents): record that tea 0.14 cannot apply org-level labels (#98) ... `tea issues edit --add-labels` and `--remove-labels` resolve label names against the repository's own label set only. Every `Kind/*`, `Priority/*`, `Reviewed/*` and `Status/*` label lives at the org level, so none of them match: the command exits 0, prints the issue, and applies nothing. Repo-local labels (`wayfinder:*`, `ready-for-agent`) work normally, which makes the failure look intermittent instead of categorical. Upstream tea fixed this in v0.15 — `modules/task/labels.go` now queries `ListOrgLabels` alongside the repo labels. nixpkgs pins 0.14.0, so this note expires when tea is bumped. `tea labels` has the same repo-only limitation and will not show the org set; `tea api orgs/ShadowsOverWestgate/labels` will. The second bullet is the more durable half: re-read a label change before believing it. An earlier version of this branch confidently documented the opposite cause, because a label that a human had applied by hand was read back as proof that the CLI had applied it. `tea issues ls -o json` exposes a `labels` field; a zero exit code does not. Identical addition in all seven repos carrying `docs/agents/issue-tracker.md`.Reviewed-on: #98 Co-authored-by: vickydotbat <vickydotbat@tutamail.com>	2026-08-05 11:38:35 +00:00
archvillainette	f395d86db5	Replace the stale triage label vocabulary with the org label taxonomy (#97) ... `docs/agents/triage-labels.md` named five labels that do not exist in the tracker (`needs-triage`, `needs-info`, `ready-for-human`, `wontfix`). Meanwhile the org has an 18-label taxonomy at https://git.westgate.pw/org/ShadowsOverWestgate/settings/labels that agents never touched, because no doc pointed at it — `Kind/Bug` had been used twice across every repo. This replaces the doc with the real taxonomy and makes one `Kind/*` label required on every issue and PR at creation time. `AGENTS.md` gets the short version. Enforcement lands separately in `sow-platform` (`ops/policy/labels.yml` + a nightly `ops/checks/check-labels.sh` drift check). Identical doc change in every `sow-*` repo.Reviewed-on: #97 Co-authored-by: vickydotbat <vickydotbat@tutamail.com>	2026-08-04 21:55:47 +00:00
archvillainette	00f467b932	docs(agents): note that tea reads stdin and hangs without </dev/null (#68) ... `tea comment` reads stdin to EOF and appends whatever it finds to the comment body. In a non-interactive shell — which is every agent — stdin is an open pipe that never sends EOF, so the call hangs forever instead of posting. Verified on tea 0.14.0: with `</dev/null` it posts instantly; with an open pipe it blocks until killed; with `echo "x" | tea comment N "y"` it posts `y` followed by `x`. Documents the redirect in the tracker guide, and applies it to the wayfinder resolve step. Same trap exists on `tea issues create --description` and `tea pr create`. 🤖 Generated with [Claude Code](https://claude.com/claude-code)Reviewed-on: #68 Co-authored-by: vickydotbat <vickydotbat@tutamail.com>	2026-07-28 13:18:38 +00:00
archvillainette	ed6945d308	Adopt workspace-wide agent standards; retire sow-docs (#51) ... Part of the workspace-wide standards rollout. Establishes where work lives (issues vs ADRs vs standing law), scaffolds `docs/agents/` for the engineering skills, and adopts ADR-0001 locally. See `sow-platform` ADR-0021 for the `sow-docs` retirement.Reviewed-on: #51 Reviewed-by: xtul <mpiasecki720@protonmail.com> Co-authored-by: vickydotbat <vickydotbat@tutamail.com>	2026-07-24 18:43:31 +00:00