refactor!: drop the wiki and page layers

The plugin is issues and nothing else now. `skills/page` (the page-tree
domain) and `skills/wiki` (its bridge to a Gitea wiki) are gone, and
with them the issue domain's `wiki:` field — page titles were the only
thing that tied the two domains together, and a field the tracker has
no column for never came back from a pull anyway.

What is left is the shape AGENTS.md already claimed for the rest of the
repo: one domain, one bridge, one transport. The docs, the plugin
manifest, and tea-runner's skill table now say so too, and
test_payload_root walks the one script directory that remains.

Also removes openspec/config.yaml; nothing in the repo referenced it.

378 tests pass.

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

README.md

@@ -9,34 +9,28 @@ A Claude Code plugin that gives Claude a reference for the `tea` CLI and enforce
 | `/tea:auth` skill | Prompts you to pick a Gitea login and pins it to the project |
 | `/tea:issue` skill | Issues as units of work — create, read, grep, validate, walk the dependency graph. Entirely offline |
 | `/tea:sync` skill | Moves issues between the local store and Gitea — pull, push, comment, close, evict |
-| `/tea:page` skill | A discussion's artifacts as a named, ordered tree of pages — import, title, index. Entirely offline |
-| `/tea:wiki` skill | Moves page trees between a local space and a Gitea wiki — fetch a subtree, publish one |
 | `/tea:use` skill | Tea CLI reference for everything that is not an issue — loads command docs on demand |
 | `tea-runner` agent | Subagent on Haiku that runs the scripts and reports back a receipt — the mechanical half, off your main context |
 | `tea-guard` hook | PreToolUse hook that blocks or rewrites every `tea` invocation |
 
 ## The layering
 
-An issue is a unit of work first and a Gitea row second. A page tree is a
-discussion's artifacts first and a wiki second. Each is two layers, and
-knowledge flows one way:
+An issue is a unit of work first and a Gitea row second. That is two layers,
+and knowledge flows one way:
 
 ```
 skills/issue    DOMAIN     what an issue is: format, validation, dependency graph
-skills/page     DOMAIN     what a page tree is: title <-> path, order, the index
       ▲                    offline — no tracker, no network, stdlib only
       │ imports
 skills/sync     BRIDGE     md <-> Gitea issue JSON, then over the wire
-skills/wiki     BRIDGE     md <-> Gitea wiki JSON; transport is sync's _gitea.py
       ▲
       │ calls
 tea-runner      EXECUTION  runs the scripts, reports a receipt — no opinions
 ```
 
-Delete `skills/sync` and the issue domain keeps working; delete `skills/wiki`
-and page trees keep working. Work that lives only on your machine is
-first-class, not a draft waiting to be uploaded. That is the point of the
-split: you can plan, write, validate, and organize without a tracker, and
+Delete `skills/sync` and the issue domain keeps working. Work that lives only
+on your machine is first-class, not a draft waiting to be uploaded. That is the
+point of the split: you can plan, write, and validate without a tracker, and
 publish only what you choose to.
 
 ## Prerequisites
@@ -159,22 +153,6 @@ skills/
       close.py                   the state field, both ways
       evict.py                   refresh state: from Gitea, then evict
       labels.py                  put the canonical label set into a repository
-  page/                      /tea:page — the page-tree domain, offline
-    SKILL.md
-    references/pages.md        canonical page-tree format
-    scripts/                   Python 3, stdlib only, no network:
-      page.py                    domain module: title <-> path, ordering,
-                                 the manifest, importing, the index
-      page_import.py             copy a directory of markdown into a space
-      page_index.py              write the table-of-contents page
-      page_ls.py                 the tree, the titles, one state tag per page
-  wiki/                      /tea:wiki — the bridge to a Gitea wiki
-    SKILL.md
-    scripts/
-      wikimap.py                 md <-> Gitea wiki JSON, pure, no I/O
-      wiki_ls.py                 what the wiki holds
-      wiki_pull.py               wiki -> tmp/wiki/<space>/
-      wiki_push.py               tmp/wiki/<space>/ -> wiki (additive)
   use/                       /tea:use — tea CLI reference (non-issue entities)
     SKILL.md
     references/tea/            command docs