v0.2.0 wrongly said the dedicated meta-host shares the project's name. Per
meta-out-of-repo design the convention is meta-<project> (e.g.
OpeItcLoc03/meta-yt-tools), so the bare <project> name stays free for a code
mirror. Fixed resolve step, example, and bootstrap instruction.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
Resolve order now prefers a dedicated same-name Gitea meta-host (e.g.
OpeItcLoc03/yt-tools) over a shared host (.common). Adds Bootstrapping a
new meta-host section incl. the git add -f gotcha (global core.excludesFile
ignores .wiki/.tasks in fresh clones). yt-tools relocated to its own host
2026-05-27.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
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>
