feat: reach the rest of Gitea with kettle api, and drop tea

The plugin required `tea`, Gitea's own CLI, for everything that is not an
issue: releases, pull requests, milestones, branches, actions, webhooks. That
put a second binary, a second set of logins nothing here could see, and 400
lines documenting somebody else's flags outside anything this repository can
test. One command over the transport that already existed removes all three.

Transport: `post` — the hand-rolled request the SDK cannot express, written for
the dependency endpoint — is generalized to an exported `Do`, and `post` is
three lines on top of it. Same http.Client, so the same RoundTripper files the
body under .kettle/payload/, the same `token …` header authenticates it, and a
non-2xx is the same *APIError. It does not paginate, does not reformat the
answer, and names no domain concept, so the layering test is untouched.

The endpoint rule is `tea api`'s, so an endpoint table written for that tool
still works — with one restriction it did not have: a full URL must be on this
instance. Every request carries the project's token in a header, and a URL on
another host would hand the token to whatever was typed.

Command: `kettle api <endpoint>` in a new `api` group, so the generator writes
plugins/kettle/skills/api/SKILL.md — group, directory and /kettle:api are one
word. No --repo and no --login, for the reason no sync command has them: a
cross-repository address is an address, and another instance is KETTLE_URL.
`-X DELETE` needs `--yes`; a flag typed on purpose is an operator's decision.

Scopes: a token minted for issues carries write:issue and answers 403 on the
first request outside issues, naming no scope. Gitea cannot be asked what a
token may do — its own token listing needs a password — so `auth add --scopes`
records it, `auth list` and `config` show it, and a 403 says which category it
is likely to be. Documentation only; nothing is checked against it.

skills/use — the tea reference, 239 lines of it — becomes skills/api: what to
ask for, which endpoints paginate, and how to write a body. Every mention of
`tea` as a requirement is gone from the manifests, the READMEs, the runner and
the four other skills; what survives is the back-compat with the old plugin,
which is a decision and not a debt.

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

plugins/kettle/skills/auth/SKILL.md

@@ -85,9 +85,33 @@ repo      claude-skills/marketplace
 | `401` / `403` from a sync command | report it verbatim. Do **not** try another login, and do not edit or remove one to route around it — that is somebody's identity, not a setting |
 | `token none` in `kettle config` | a name is pinned but no credential answers to it |
 
-**`tea` does not read any of this.** The `tea` CLI keeps its own configuration
-under `$XDG_CONFIG_HOME/tea` and its own logins (`tea logins list`), and
-configuring one tool configures nothing in the other — see `/kettle:use`.
+## Scopes: what the token is allowed to do
+
+Gitea mints a token with scopes, spelled `<read|write>:<category>`. A token made
+for issues carries `write:issue` — and that is enough for everything
+`/kettle:issue` and `/kettle:sync` do, and **not** enough for anything
+`/kettle:api` reaches: releases, pull requests, branches, tags and actions all
+sit under `repository`.
+
+| doing | needs |
+|---|---|
+| pull, push, comment, close, evict | `write:issue` |
+| `kettle labels` | `write:issue` |
+| `kettle api` on releases, PRs, tags, branches, actions | `write:repository` too |
+| reading any of those without writing | the `read:` half is enough |
+
+`kettle auth add --scopes write:issue,write:repository` writes that down beside
+the login. **It is a note and nothing else** — nothing is checked against it and
+nothing is refused because of it. It is worth writing down because the instance
+will not answer the question: Gitea's own token listing needs a password rather
+than a token, so a token cannot be asked what it may do. `kettle auth list` and
+`kettle config` show what was recorded; `(not recorded)` means nobody wrote it
+down, never "none".
+
+A **403** from a sync command or from `kettle api` is usually this and says so.
+Minting a new token is the operator's job in the web UI — the same flow as step
+2 above, with both scopes ticked this time. Never remove or re-point a login to
+route around a 403.
 
 **No `kettle` on PATH?** `command not found: kettle` is the whole story. Stop and
 tell the operator to install it: `cd cli && go build -o ~/.local/bin/kettle