refactor(gitea): deep modules — split flat dispatch skill into 6 domain skills + orchestrator + agent (#67)

plugins/gitea/skills/gitea-issues/references/search.md

@@ -0,0 +1,39 @@
+---
+topic: search
+source_keys:
+  - gitea-mcp-repo
+  - gitea-mcp-slim-go
+---
+
+# `search_issues`
+
+Call signature verified live against the deployed `gitea-mcp` server via `ToolSearch` at authoring
+time (see `references/sources.md`) — confirmed to match `api-reference.md`.
+
+**Parameters:**
+- `query` (string, required) — the only hard-required parameter
+- `state` (string, enum `"open"` | `"closed"` | `"all"`, optional)
+- `type` (string, enum `"issues"` | `"pulls"`, optional) — **this tool has a working type filter**,
+  unlike `list_issues` (see `references/issues.md`)
+- `labels` (string, optional) — comma-separated label **names** — a plain string, not the array form
+  `list_issues` uses
+- `owner` (string, optional) — restrict results to one owner
+- `page` (number, optional, default `1`)
+- `per_page` (number, optional, default `30`)
+
+**Call:**
+```
+search_issues query: <text>
+```
+
+**Narrowing the search:**
+```
+search_issues query: <text> owner: <owner> state: "open" type: "pulls" labels: "bug,urgent"
+```
+
+This is a cross-repository search (unlike `list_issues`, which is scoped to one `owner`/`repo`) —
+useful when the caller doesn't know which repo an issue lives in, or wants results across an
+organization. Pass `owner` to narrow scope if the caller does know it.
+
+Paginate the same way as `list_issues`: iterate `page` until the returned count is less than
+`per_page`.