refactor!: rewire the plugin onto the kettle binary, and rename it

BREAKING: the plugin is `kettle`, not `tea`, and its commands are `/kettle:*`.
It also now needs a binary on PATH that it did not need before; the README and
every skill say how to get one and what a missing one looks like.

The plugin was 3800 lines of Python doing what a compiled binary does better,
and the name pointed at a tool that no longer takes part: `tea` is Gitea's CLI,
and since the transport moved into the binary nothing here shells out to it for
issues at all. A plugin named after it was going to keep suggesting otherwise.

Deleted: 19 scripts, the 14-file unittest suite, and the tea-guard hook. The
guard blocked any `tea` invocation that would run under a login the model picked
instead of the operator; the binary holds its own credentials and reads the
pinned login out of the project's own config, so that failure is no longer
expressible and there is nothing left to police. agents-sync stays — it is about
AGENTS.md symlinks and has nothing to do with any of this.

What the plugin keeps is what only a plugin can carry: the rules an operator
states and a binary cannot enforce. `init` still refuses to run inside a linked
worktree and still may not be model-invoked, because which directory is the
project is a statement a person makes. The issue format reference stays here and
stays the source of truth. The runner subagent is still for batches and still
may not decide what an issue says.

The command reference in the issue, sync and project skills is GENERATED from
the binary's own command registry, between markers, so a flag that changed
cannot ship with a skill that recommends the old one. `kettle gen skills
--check` exits non-zero when they drift. The generator owns the region and
nothing outside it: the frontmatter description, which is what decides whether a
skill loads at all, stays hand-written.

`use` survives and is the one place `tea` is still named — for releases,
webhooks and actions, which kettle does not cover. Its instruction to write
`--login "$GITEA_LOGIN"` and let the hook substitute the pin was true until this
commit and is now rewritten: `tea` keeps its own configuration, kettle keeps
its own, and configuring one configures nothing in the other.

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

README.md

@@ -1,8 +1,9 @@
 # claude-skills — a Claude Code plugin marketplace
 
-One repository, one marketplace, several plugins. Register it once and install
-whichever pieces you want; each plugin is independent and carries its own
-manifest, docs, and tests.
+One repository, one marketplace, several plugins, and the `kettle` binary the
+issue plugin is built on. Register the marketplace once and install whichever
+pieces you want; each plugin is independent and carries its own manifest and
+docs.
 
 ## Installation
 
@@ -19,17 +20,29 @@ Working from a local clone? Point at the directory instead:
 Then install what you need:
 
 ```
-/plugin install tea@claude-skills
+/plugin install kettle@claude-skills
 /plugin install tdl@claude-skills
 ```
 
 Use `/plugin` to enable, disable, or update them later.
 
+**`kettle` also needs its binary**, which no plugin can install for you. Build it
+from this repository (`cli/go.mod` requires **Go 1.26**; `vendor/` is committed,
+so the build needs no network):
+
+```bash
+cd cli && go build -o ~/.local/bin/kettle ./cmd/kettle
+go install git.noodles.cam/claude-skills/marketplace/cli/cmd/kettle@latest
+```
+
+Put the target directory on your `PATH` and check with `kettle help`. A skill
+that answers `command not found: kettle` is telling you exactly this.
+
 ## What ships here
 
 | Plugin | Commands | What it does |
 |---|---|---|
-| [`tea`](plugins/tea) | `/tea:auth` `/tea:issue` `/tea:sync` `/tea:use` | Gitea issues as local markdown, cleanly layered. Issues are units of work offline first and tracker rows second; a PreToolUse hook blocks any `tea` command that would run under a login Claude picked instead of the operator |
+| [`kettle`](plugins/kettle) | `/kettle:init` `/kettle:auth` `/kettle:issue` `/kettle:sync` `/kettle:use` `/kettle:project` | Issues as local markdown, cleanly layered. Issues are units of work offline first and tracker rows second; the `kettle` binary does the work, and each skill's command reference is generated from the binary's own command registry so it cannot drift |
 | [`tdl`](plugins/tdl) | `/tdl:audit` | Three Dots Labs Go conventions as an enforceable rule set — audits a Go project against 63 CQRS/DDD/Clean-Architecture rules by severity, or scaffolds services, handlers, entities, repositories and Watermill adapters from templates that already follow them |
 
 ## Layout
@@ -38,10 +51,12 @@ Use `/plugin` to enable, disable, or update them later.
 .claude-plugin/
   marketplace.json           the catalog — one entry per plugin, source is a
                              path into plugins/
+cli/                         the kettle binary: cmd/kettle + internal/*, its
+                             own AGENTS.md, its own tests, vendored deps
 plugins/
-  tea/
+  kettle/
     .claude-plugin/plugin.json
-    agents/ hooks/ skills/ tests/
+    agents/ hooks/ skills/
     README.md  AGENTS.md
   tdl/
     .claude-plugin/plugin.json
@@ -53,11 +68,21 @@ resolves inside it and every path a plugin uses stays relative to itself.
 Adding a plugin means adding a directory here plus one entry in
 `marketplace.json` — nothing else in the repo needs to know about it.
 
+`cli/` is deliberately not inside a plugin: a binary is installed on a machine,
+while a plugin is a directory Claude Code loads, and collapsing the two is what
+put an earlier version's issue store inside a versioned plugin cache.
+
 ## Development
 
-`tea` has a test suite; run it from its own directory so the tests resolve
-their root correctly:
+```bash
+cd cli && go test ./...                                     # the binary's suite
+cd cli && go build -o /tmp/kettle ./cmd/kettle
+/tmp/kettle gen skills --out plugins/kettle/skills --check   # docs vs binary
+```
 
-```
-cd plugins/tea && python3 -m unittest discover -s tests
-```
+The second one is the invariant that keeps the plugin honest: everything a
+SKILL.md says about a `kettle` command — its usage line, its flags, its
+examples — is generated from the registry the binary is built from, between
+`<!-- kettle:gen -->` markers. `--check` exits 1 when any of it is out of date;
+run `gen skills` without it to regenerate. Prose outside the markers is never
+touched.