docs(wiki): reflect Step 5.7 stance change — accepted as future work

projects-meta-skills.md "Bootstrap trigger" section + log decision entry
now show Step 5.7 (projects-meta-mcp dependency detector) as accepted
future work rather than a deliberate non-decision. Tracked as ⚪ Ready
task [bootstrap-recommend-projects-meta].

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

.tasks/STATUS.md

@@ -93,6 +93,15 @@ _Updated: 2026-04-30_
 **Next action:** when triggered (skill count crosses threshold), evaluate variant B (grouped by family) vs variant C (flat + manifest) from the original brainstorm in `.wiki/concepts/repo-layout.md`
 **Branch:** (not started)
 
+---
+
+## ⚪ [bootstrap-recommend-projects-meta] — Step 5.7 in project-bootstrap: recommend `setup-projects-meta` if MCP tools missing
+**Status:** ready
+**Where I stopped:** (not started) — opened as follow-up to `[bootstrap-projects-meta-trigger]` (commit b120397). The `check across all projects` trigger is now in every CLAUDE.md template, but on a fresh machine without `projects-meta-mcp` registered the trigger is silently no-op until the user verbally asks for cross-project work
+**Next action:** mirror Step 5.6 (superpowers plugin check). Detect missing `mcp__projects-meta__*` tools — possible signals: parse `~/.claude.json` for `mcpServers.projects-meta` key, or check for `~/.local/projects-meta-mcp/dist/server.js`. If absent, print one-shot recommendation block in chat with `setup-projects-meta` invocation hint. Hard rule: never auto-install. Bump project-bootstrap 1.2.0 → 1.3.0
+**Branch:** (not started)
+**Blocker:** waits on observing a real fresh-machine bootstrap that silently misses the dependency — defer until we see the failure mode in practice
+
 ## 🟢 [using-projects-meta-freshness-gate] — добавить Step 0 freshness check в using-projects-meta
 
 **Status:** done

.wiki/concepts/projects-meta-skills.md

@@ -97,4 +97,6 @@ This loads `using-projects-meta` automatically in every bootstrapped repo so cro
 
 The phrase is a verbatim quote from `using-projects-meta`'s `description:` triggers — guaranteed match against the harness's keyword index, no fuzzy matching required.
 
-The trigger is a **no-op** when `mcp__projects-meta__*` tools aren't registered in the session. On a fresh machine, `setup-projects-meta` provides the install path; `using-projects-meta`'s Prerequisites already redirects there. We deliberately did **not** add a Step 5.7 mirror of Step 5.6 (the `superpowers` plugin recommendation) for `projects-meta` — the wiring is already self-correcting via the Prerequisites pointer, and bootstrap shouldn't grow a recommendation block per skill. If fresh-machine bootstraps start silently failing the dependency check, revisit.
+The trigger is a **no-op** when `mcp__projects-meta__*` tools aren't registered in the session. On a fresh machine, `setup-projects-meta` provides the install path; `using-projects-meta`'s Prerequisites already redirects there.
+
+A Step 5.7 mirror of Step 5.6 (the `superpowers` plugin recommendation) for `projects-meta` is **accepted as future work** — tracked as `[bootstrap-recommend-projects-meta]` (⚪ Ready). Deferred until we observe a real fresh-machine bootstrap silently miss the dependency, so the detector design is informed by the actual failure mode (`~/.claude.json` `mcpServers.projects-meta` key absence vs. `~/.local/projects-meta-mcp/dist/server.js` absence vs. both). Until then, the Prerequisites pointer in `using-projects-meta` is the self-correcting fallback.

.wiki/log.md

@@ -35,3 +35,4 @@ Parseable: `grep "^## \[" .wiki/log.md | tail -20`.
 ## [2026-04-28] doc | README.md + README.ru.md — new "Using skills in projects" / "Использование в проектах" section after install quick-start; describes project-bootstrap workflow (git, .gitignore, README, .wiki/, .tasks/, CLAUDE.md, manifest, superpowers-plugin check) and the init/upgrade modes
 ## [2026-04-30] refactor | project-bootstrap re-run on this repo (upgrade mode) — setup-wiki noop, setup-tasks noop, CLAUDE.md unchanged (matches template), bootstrap-manifest.md written: project-bootstrap@1.1.0 / setup-wiki@1.0.0 / setup-tasks@1.0.0
 ## [2026-04-30] decision | project-bootstrap@1.2.0 — CLAUDE.md template gains `check across all projects` (verbatim trigger from using-projects-meta description); installs auto-load cross-project tasks + shared-wiki access in every bootstrapped repo; no Step 5.7 dependency-check mirror — Prerequisites pointer in using-projects-meta is self-correcting; local CLAUDE.md, both READMEs, dist/.skill, projects-meta-skills concept page synced
+## [2026-04-30] decision | Step 5.7 mirror of Step 5.6 (projects-meta-mcp dependency detector / `setup-projects-meta` recommendation) accepted as future work; tracked as ⚪ Ready task `[bootstrap-recommend-projects-meta]`; deferred until first observed fresh-machine miss so detector signal is informed by real failure mode; concept page `projects-meta-skills.md` updated to reflect new stance