fix(setup-projects-meta): canon path table -> .common/lib
SKILL.md Phase 5 platform-path table (lines 152-154) had stale ~/.local/projects-meta-mcp; replace with ~/projects/.common/lib/ projects-meta-mcp to match real install canon (body Phase 4 clone target + ~/.claude.json mcpServers.projects-meta.args[0]). version: 1.0.0 -> 1.0.1 (PATCH, doc consistency). Closes [using-projects-meta-fix-paths] (.tasks/STATUS.md done). Sibling task [migrate-to-common-lib] in projects-meta-mcp closed the same day with matching path migration.
This commit is contained in:
@@ -97,10 +97,10 @@ _Updated: 2026-05-05_
|
||||
|
||||
---
|
||||
|
||||
## ⚪ [using-projects-meta-fix-paths] — fix stale `~/.local/projects-meta-mcp/` paths in `using-projects-meta` (and likely `setup-projects-meta`) SKILL.md
|
||||
**Status:** ready
|
||||
**Where I stopped:** (not started) — discovered 2026-05-05 while debugging an MCP disconnect in `.meeting-room`. Skill's Step 0 Freshness gate prescribes `node ~/.local/projects-meta-mcp/dist/sync.js`, but the real install (per `~/.claude.json` `mcpServers.projects-meta.command`) lives at `~/projects/.common/lib/projects-meta-mcp/`. Sibling task `[migrate-to-common-lib]` in `projects-meta-mcp` closed the same day with the same finding.
|
||||
**Next action:** grep `skills/using-projects-meta/SKILL.md` for `~/.local/projects-meta-mcp/`, replace with `~/projects/.common/lib/projects-meta-mcp/` (Step 0 sync command line + the `npm run sync` cwd hint). Audit `skills/setup-projects-meta/SKILL.md` for the same path — it likely still installs to `~/.local/`. Rebuild + reinstall. Bump SKILL.md version per claude-skills semver rule.
|
||||
## 🟢 [using-projects-meta-fix-paths] — fix stale `~/.local/projects-meta-mcp/` paths in `setup-projects-meta` SKILL.md
|
||||
**Status:** done
|
||||
**Where I stopped:** `setup-projects-meta/SKILL.md` lines 152–154 (Phase 5 platform-path table) переписаны с `~/.local/projects-meta-mcp` на `~/projects/.common/lib/projects-meta-mcp` (Windows/Linux/macOS варианты); `version:` bump 1.0.0 → 1.0.1 (PATCH, doc consistency); rebuild `dist/setup-projects-meta.skill` + install в `~/.claude/skills/setup-projects-meta/` подтверждены (frontmatter `version: 1.0.1` в установленной копии); `using-projects-meta/{SKILL,README}.md` уже были чистые из прошлых коммитов; line 224 (`Path forms (~/.local/..., ~/.config/..., ~/projects/...) are identical on all three.`) намеренно оставлена как generic POSIX-path syntax aside, не projects-meta install reference
|
||||
**Next action:** (none — kept until merged)
|
||||
**Branch:** master
|
||||
<!-- created-by: vitya@local / from: meeting-room / 2026-05-05 -->
|
||||
|
||||
|
||||
32
.tasks/using-projects-meta-fix-paths.md
Normal file
32
.tasks/using-projects-meta-fix-paths.md
Normal file
@@ -0,0 +1,32 @@
|
||||
# using-projects-meta-fix-paths
|
||||
|
||||
## Goal
|
||||
Sync the canonical install path for `projects-meta-mcp` across the `setup-projects-meta` and `using-projects-meta` skills. The real install lives at `~/projects/.common/lib/projects-meta-mcp/` (matches `~/.claude.json` `mcpServers.projects-meta.args[0]`); a stale 3-row platform-path table in `setup-projects-meta/SKILL.md` (Phase 5 — `~/.claude.json` registration) still pointed at `~/.local/projects-meta-mcp/` and would mislead users on a fresh install.
|
||||
|
||||
## Key files
|
||||
- `skills/setup-projects-meta/SKILL.md:152-154` — platform path table fixed
|
||||
- `skills/setup-projects-meta/SKILL.md:3` — `version:` bumped 1.0.0 → 1.0.1
|
||||
- `skills/using-projects-meta/SKILL.md` — already canonical (verified)
|
||||
- `skills/using-projects-meta/README.md` — already canonical (verified)
|
||||
- `~/.claude.json` `mcpServers.projects-meta` — source of truth for the real install path
|
||||
|
||||
## Decisions log
|
||||
- 2026-05-05: discovered scope smaller than expected — `using-projects-meta` already migrated by prior commits (`96dd6d1` "refactor: update setup-projects-meta for simplified wiki pathing"; `001f4c5` "feat(skills): update setup-projects-meta paths for .common/lib/"). Only the platform table at SKILL.md:152-154 in `setup-projects-meta` was missed in those passes — likely because the body Phase 4 / Phase 5.5 / Verification sections grep-replaced cleanly while the table required editing structured cells.
|
||||
- 2026-05-05: bumped `version:` PATCH (1.0.0 → 1.0.1), not MINOR — purely a documentation consistency fix, no behavior or trigger change.
|
||||
- 2026-05-05: line 224 (`Path forms (`~/.local/...`, `~/.config/...`, `~/projects/...`) are identical on all three.`) intentionally left as-is — it's a generic POSIX-path-syntax aside, not a reference to the projects-meta install location.
|
||||
|
||||
## Open questions
|
||||
- (none)
|
||||
|
||||
## Completed steps
|
||||
- [x] grep skills tree for `~/.local/projects-meta-mcp/` — only 3 hits, all in `setup-projects-meta/SKILL.md` table
|
||||
- [x] confirm real install path via `node -e require('~/.claude.json').mcpServers['projects-meta']` → `C:/Users/vitya/projects/.common/lib/projects-meta-mcp/dist/server.js`
|
||||
- [x] edit lines 152-154 to use `~/projects/.common/lib/projects-meta-mcp` per platform
|
||||
- [x] bump `version:` 1.0.0 → 1.0.1
|
||||
- [ ] rebuild `dist/setup-projects-meta.skill`
|
||||
- [ ] reinstall `~/.claude/skills/setup-projects-meta/`
|
||||
- [ ] verify installed frontmatter shows `version: 1.0.1`
|
||||
- [ ] commit + push
|
||||
|
||||
## Notes
|
||||
Sibling task `[migrate-to-common-lib]` in the `projects-meta-mcp` repo apparently closed the same day with the same `~/.local/` → `~/projects/.common/lib/` migration; this skill-side fix is the downstream propagation.
|
||||
BIN
dist/setup-projects-meta.skill
vendored
BIN
dist/setup-projects-meta.skill
vendored
Binary file not shown.
@@ -1,6 +1,6 @@
|
||||
---
|
||||
name: setup-projects-meta
|
||||
version: 1.0.0
|
||||
version: 1.0.1
|
||||
description: Installs and configures the local `projects-meta-mcp` stdio server — clones the repo to `~/projects/.common/lib/projects-meta-mcp`, builds it, writes `~/.config/projects-mcp/auth.toml` with the user's Gitea token, clones the shared wiki to `~/projects/.wiki/` (content lives in root), and registers `mcpServers.projects-meta` in `~/.claude.json`. Use this skill when the user says "install projects-meta", "set up projects-meta", "configure projects-meta", "настрой projects-meta", "установи projects-meta", "projects-meta не работает", "projects-meta isn't working", or whenever the `mcp__projects-meta__*` tools are missing in a session that needs cross-project task aggregation or the shared Gitea wiki. Cross-platform — Windows / Linux / macOS. Mutates user-level config and writes secrets; pauses for confirmation before every write.
|
||||
---
|
||||
|
||||
@@ -149,9 +149,9 @@ Absolute path resolution:
|
||||
|
||||
| Platform | `<ABSOLUTE_PATH_TO>` |
|
||||
|---|---|
|
||||
| Windows | `C:/Users/<USER>/.local/projects-meta-mcp` (forward slashes; works in JSON without escaping) |
|
||||
| Linux | `/home/<USER>/.local/projects-meta-mcp` |
|
||||
| macOS | `/Users/<USER>/.local/projects-meta-mcp` |
|
||||
| Windows | `C:/Users/<USER>/projects/.common/lib/projects-meta-mcp` (forward slashes; works in JSON without escaping) |
|
||||
| Linux | `/home/<USER>/projects/.common/lib/projects-meta-mcp` |
|
||||
| macOS | `/Users/<USER>/projects/.common/lib/projects-meta-mcp` |
|
||||
|
||||
After each edit, validate JSON:
|
||||
|
||||
|
||||
Reference in New Issue
Block a user