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/project/SKILL.md

@@ -19,7 +19,7 @@ nothing on its own, which is what makes it safe inside a working tree.
 `KETTLE_URL` and `KETTLE_TOKEN` each override the file they shadow.
 
 **No `kettle` on PATH?** `command not found: kettle` is the whole story — no
-script and no `tea` invocation substitutes for it. Stop and tell the operator to
+script and no other CLI substitutes for it. Stop and tell the operator to
 install it: `cd cli && go build -o ~/.local/bin/kettle ./cmd/kettle` in the
 marketplace repository (go.mod requires **go 1.26**), or
 `go install git.noodles.cam/claude-skills/marketplace/cli/cmd/kettle@latest`.
@@ -47,9 +47,19 @@ argument is in the shell history the moment it is typed:
 
 `list` never prints a token. There is no flag to make it.
 
+--scopes RECORDS WHAT THE TOKEN WAS MINTED WITH, and records is all it does:
+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, not a token, so a token cannot be asked what it
+may do. Gitea spells them <read|write>:<category>; issues need `write:issue`,
+and everything `kettle api` reaches outside issues — releases, pull requests,
+branches, tags, actions — is `repository`. A token minted for issues alone
+answers 403 there, and the 403 names no scope.
+
 | flag | default | what it does |
 | --- | --- | --- |
 | `--name` | — | login name (add) |
+| `--scopes` | — | what the token was minted with, comma separated, e.g. write:issue,write:repository; documentation only (add) |
 | `--token` | — | token, if you would rather not use stdin (add) |
 | `--url` | — | instance URL, e.g. https://git.example.com (add) |
 | `--user` | — | account this token belongs to; documentation only (add) |
@@ -57,6 +67,7 @@ argument is in the shell history the moment it is typed:
 ```bash
 kettle auth list            # what this machine holds
 pass show gitea | kettle auth add --name noodles --url https://git.example.com  # add one, token on stdin
+kettle auth add --name noodles --url https://git.example.com --scopes write:issue,write:repository < t.txt  # and write down what it can do
 kettle auth remove noodles  # forget it
 ```