feat(skills): add meta-host-routing v0.1.0

Resolve where a project's meta lives before tasks_create/knowledge_ingest/
promotion. Github-hosted projects (or any 'not in cache' in projects-meta)
keep .tasks/.wiki in a sibling Gitea host repo (meta-out-of-repo design),
not in the github tree. Route MCP calls to the host, never guess.

Codified after an agent started writing yt-tools tasks into the github repo
instead of recalling yt-tools meta lives in .common.

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

skills/meta-host-routing/SKILL.md

@@ -0,0 +1,73 @@
+---
+name: meta-host-routing
+version: 0.1.0
+description: >
+  Use before any tasks_create / knowledge_ingest / brainstorm-promotion against
+  a project — resolve WHERE that project's meta lives before writing. A
+  github-hosted project (or any project projects-meta reports "not in cache")
+  does NOT carry .tasks/.wiki in its own repo (meta-out-of-repo design: they'd
+  leak on push/PR). Its meta lives in a sibling Gitea-tracked host repo — route
+  MCP calls there, never into the github working tree, never guess. Triggers:
+  "project not in cache" from projects-meta, promoting/creating tasks for a
+  project with a github remote, "заведи таски в <github-проект>", "промоутни
+  <github-проект>". Skip for a normal Gitea project already known to
+  projects-meta — there the route is direct.
+---
+
+# meta-host-routing
+
+> A project's code repo is not always where its meta lives. Before writing tasks or wiki, resolve the **meta-host**. Github-hosted projects keep their `.tasks/`/`.wiki/` in a sibling Gitea repo — never in the github tree. Never guess the target.
+
+## When this runs
+
+Before any `mcp__projects-meta__tasks_create`, `mcp__projects-meta__knowledge_ingest`, or brainstorm promotion, when **either**:
+
+- the target project's local clone has a **github remote**, OR
+- `projects-meta` returns **"project not in cache"** for the target.
+
+Both are signals that the project follows the **meta-out-of-repo** design: its meta is intentionally absent from its own repo.
+
+**Skip** when the target is a normal Gitea project already known to `projects-meta` (`meta_status` lists it / a `tasks_create` dry-run succeeds) — there the route is direct, no resolution needed.
+
+## Why meta is out of the repo
+
+Per the `meta-out-of-repo` design: `.tasks/`, `.wiki/`, `.claude/` must not be committed into a repo that gets pushed to a public / shared / forked-upstream remote — the "kitchen" (notes, tasks, local skills, agent instructions) would leak. A global `core.excludesFile` ignores those paths, so github-hosted projects carry **no** meta in-tree by design. The meta still exists — it lives in a Gitea-tracked **host** repo and syncs through `projects-meta`.
+
+## Steps
+
+1. **Detect.** Check the target's local remote (`git remote -v`) and/or a `projects-meta` dry-run. Github remote OR "not in cache" → meta-out-of-repo project; continue. Otherwise → direct Gitea route, this skill does not apply.
+
+2. **Resolve the meta-host.** Find the Gitea repo that already tracks this project's meta. Grep sibling Gitea repos — **start with `.common`** (`~/projects/.common/`) — for the project name across `.tasks/STATUS.md` and `.wiki/`:
+   ```
+   grep -ril "<project-name>" ~/projects/.common/.tasks/ ~/projects/.common/.wiki/
+   ```
+   The host is whichever Gitea repo already holds that project's tasks/wiki. Canonical example: code `github.com/OpeItcLoc03/yt-tools` → meta-host `.common` (`OpeItcLoc03/common`), because yt-tools was born in `.common/lib/yt-tools/` and the code was extracted while the meta stayed.
+
+3. **Route there.** Send every `tasks_create` / `knowledge_ingest` to the host's qualified `<owner>/<repo>` (e.g. `OpeItcLoc03/common`). Namespace entries with a `<project>-` slug prefix so they're distinguishable on the shared host board (`yt-meta-impl`, `yt-comments-impl`, …).
+
+4. **Never** write `.tasks/`/`.wiki/` files into the github working tree, and **never** invent a target when resolution is ambiguous (Failure modes below).
+
+## Failure modes
+
+- **No Gitea repo tracks this project** → STOP. Ask the user where the meta should live (likely `.common`, or a new host). Do **not** default to writing into the github repo — that reintroduces the leak meta-out-of-repo exists to prevent.
+- **Multiple Gitea repos reference the project** → STOP, ask which is canonical. Don't pick by guess.
+- **projects-meta cache stale** ("not in cache" could be staleness, not meta-out-of-repo) → run a sync / `meta_status` freshness check first (see `using-projects-meta` Step 0) before concluding the project is github-only.
+
+## Interaction with workshop-promote-brainstorm
+
+`workshop-promote-brainstorm`'s domain branch currently **aborts** on "project not in cache". With this skill active, that abort becomes a resolve step: find the meta-host, then promote into it. This skill is the routing primitive; promote-brainstorm (and ad-hoc `tasks_create`) consult it.
+
+## What NOT to do
+
+- Don't write meta into a github working tree "because the project is right there" — that's the exact path-of-least-resistance leak meta-out-of-repo prevents.
+- Don't treat "project not in cache" as "project doesn't exist" — it means "meta is hosted elsewhere," resolve it.
+- Don't guess the meta-host when grep is ambiguous — ask.
+- Don't apply this to normal Gitea projects already in `projects-meta` — adds a pointless resolution step.
+
+## Cross-agent note
+
+References Claude Code MCP tool names (`mcp__projects-meta__*`). On non-CC platforms substitute the projects-meta equivalents; the routing logic is platform-independent.
+
+## Why this exists
+
+Codified 2026-05-27 after an agent, asked to promote a yt-tools feature, found yt-tools "not in cache" and started writing tasks directly into the github repo — instead of recalling that yt-tools' meta lives in `.common`. The `meta-out-of-repo` design existed only as an archived workshop concept doc (never triggers). This skill makes the routing rule fire at the moment of action.