feat(skills): update setup-projects-meta paths for .common/lib/

- Replace ~/.local/projects-meta-mcp → ~/projects/.common/lib/projects-meta-mcp
- Update setup-projects-meta and using-projects-meta skills
- Rebuild dist/ with new paths

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

skills/using-projects-meta/README.md

@@ -59,7 +59,7 @@ Before **any** `tasks_*` or `knowledge_*` call:
 
 1. `mcp__projects-meta__meta_status` — probe cache age + errors.
 2. If `cache_age_minutes` > 10 OR `errors_count` > 0 →
-   `node ~/.local/projects-meta-mcp/dist/sync.js`.
+   `node ~/projects/.common/lib/projects-meta-mcp/dist/sync.js`.
 3. For shared-wiki **writes** (`knowledge_ingest`, `knowledge_promote`) →
    **also** `git -C ~/projects/projects-wiki pull --ff-only`. Unconditional.
    The MCP server uses sha-based optimistic locking on the wiki repo;
@@ -134,7 +134,7 @@ from `auth.toml`).
   two different stores. `using-wiki` operates on the local one;
   `using-projects-meta` queries / ingests the shared one.
 - **Acting on stale `tasks_aggregate`.** If `meta_status.age_seconds` > 3600,
-  either run `node dist/sync.js` (in `~/.local/projects-meta-mcp`) or warn the
+  either run `node dist/sync.js` (in `~/projects/.common/lib/projects-meta-mcp`) or warn the
   user about staleness.
 - **Vague `knowledge_search` queries.** "auth" returns noise. Multi-word,
   specific queries return targeted snippets.

skills/using-projects-meta/SKILL.md

@@ -65,8 +65,8 @@ Use MCP only for **other** projects, **other** machines, or **shared** wiki cont
 
 2. Branch on cache freshness:
    • If cache_age_minutes > 10 OR errors_count > 0:
-       run `node ~/.local/projects-meta-mcp/dist/sync.js`
-       (or `npm run sync` from ~/.local/projects-meta-mcp).
+       run `node ~/projects/.common/lib/projects-meta-mcp/dist/sync.js`
+       (or `npm run sync` from ~/projects/.common/lib/projects-meta-mcp).
    • Else: cache is fresh enough — skip sync, no need to hit the network.
 
 3. For shared-wiki WRITES (knowledge_ingest, knowledge_promote):
@@ -221,7 +221,7 @@ User: "close `[projects-meta-skills]` in claude-skills"
 | Reading current project's tasks via `tasks_get` instead of disk | Read `.tasks/STATUS.md` directly. MCP is for *other* projects. |
 | Inlining `confirm: true` on the first mutation call | Always preview first; show user; only then `confirm: true`. |
 | Using `knowledge_search` for the project's own wiki | The shared wiki is a separate Gitea repo. Local `.wiki/` is in cwd. |
-| Acting on a stale `tasks_aggregate` without checking `meta_status` | Step 0 — Freshness gate is mandatory. If `cache_age_minutes` > 10 (or errors > 0), run `node ~/.local/projects-meta-mcp/dist/sync.js` first. |
+| Acting on a stale `tasks_aggregate` without checking `meta_status` | Step 0 — Freshness gate is mandatory. If `cache_age_minutes` > 10 (or errors > 0), run `node ~/projects/.common/lib/projects-meta-mcp/dist/sync.js` first. |
 | Skipping `git -C ~/projects/projects-wiki pull` before `knowledge_ingest` / `knowledge_promote` | sha-based optimistic lock will reject the commit (422) and the failure is opaque. Pull is unconditional for shared-wiki writes — fast-forward is a no-op when current. |
 | Treating sync 401/403 as "MCP is fine, the page just doesn't exist yet" | 401/403 means the Gitea token is dead. Stop, tell the user to rotate `gitea_token` in `~/.config/projects-mcp/auth.toml`. Never guess on stale data. |
 | Calling `knowledge_ingest` with the wrong `type` | `type` must be one of `entities` / `concepts` / `packages` / `sources` / `raw`. Mis-typed pages land in the wrong section and break `index.md`. |