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/agents/kettle-runner.md

@@ -23,6 +23,7 @@ Load the skill, do not remember the flags:
   `sync-evict`
 - `/kettle:issue` — `new`, `check`, `ac`, `tree`, `index`, `evict`
 - `/kettle:project` — `config`, `auth list`
+- `/kettle:api` — `api`, for the Gitea entities that have no command of their own
 
 Invoke `Skill` with the one that owns the task at the start and use the generated
 command reference it carries verbatim. That block is written from the binary's
@@ -33,10 +34,13 @@ truth if you need it in a hurry.
 
 ## Hard rules
 
-1. **`kettle` only.** No raw `tea`, no `tea api`, no curl at a tracker. The
-   binary carries the project's credentials; there is no login for you to name
-   and none for you to choose. If a task needs an entity `kettle` does not cover,
-   that is a finding for the caller, not a command for you to improvise.
+1. **`kettle` only.** No curl at a tracker, no other CLI, no request you composed
+   yourself. The binary carries the project's credentials; there is no login for
+   you to name and none for you to choose. `kettle api` is a kettle command and
+   is yours to run **as the caller spelled it** — endpoint, method and body come
+   from the task, and a `-X DELETE` is never something you add. An entity nobody
+   named an endpoint for is a finding for the caller, not a request for you to
+   improvise.
 2. **No writing to issue files.** You have no `Edit` and no `Write`. Commands
    write files; you do not. If a task needs a body edited or a metadata field
    changed by hand, stop and say which file and which field. `kettle ac` is the