v2: 7-persona virtual team + headless MCP + paste-install UX

[2233admin]

What's in v2

v2 pivots from "MCP plumbing" to "6-persona virtual team". Your markdown vault becomes a set of /vault-* skills any MCP agent (Claude Code, Codex, OpenCode, Gemini) drives directly.

Install in 30 seconds

git clone --depth 1 https://github.com/2233admin/obsidian-llm-wiki.git ~/obsidian-llm-wiki-src
cd ~/obsidian-llm-wiki-src && ./setup

PowerShell:

git clone --depth 1 https://github.com/2233admin/obsidian-llm-wiki.git "$HOME\obsidian-llm-wiki-src"
cd "$HOME\obsidian-llm-wiki-src"; .\setup.ps1

Headline changes

• 7 vault- personas*: librarian, architect, curator, teacher, historian, janitor, gardener
• Headless-first MCP: filesystem adapter always available; Obsidian / memU / GitNexus are optional adapters
• 38 MCP tools across vault / query / compile / recipe / agent namespaces; auto-generated reference at docs/mcp-tools-reference.md with a drift guard test
• Recipe framework: voile, feishu, x-to-vault collectors ship in-tree
• Setup UX: single paste-install works across Claude Code / Codex / OpenCode / Gemini (--host <name>)
• Brand: display flipped to "LLM Wiki Bridge"; slug obsidian-llm-wiki unchanged (npm scope, repo URL, clone paths, serverInfo.name)
• 88 tests green on this head

Verification

• npm run build -- clean (tsc 0 errors)
• npm test -- 88/88 pass
• npm run generate-tools-doc -- doc is deterministic, drift test enforces freshness
• Tag v2.0.0-rc1 already pushed on this head

Review notes

• 16 code commits + 1 rebrand commit on top of main
• Slug/brand split rationale: see project_obsidian_llm_wiki_branding and feedback_rebrand_workflow (short form: npm scope was registered first, slug has to stay canonical across npm/URL/path for GEO + install consistency)

Ready for merge review. Release notes live on the Releases tab.

[gemini-code-assist]

Code Review

This pull request transitions the project to 'LLM Wiki Bridge v2', introducing a persona-based architecture with six specialized virtual team roles for AI agents. Key changes include a pre-bundled MCP server for easier installation, refactored Python compiler logic for robust markdown parsing, a synthetic demo vault, and a static graph viewer. Feedback was provided regarding the vault.searchByFrontmatter implementation in the MCP server, where a call to statSync lacks error handling, potentially leading to execution failures if files are deleted or inaccessible during the vault walk.

[gemini-code-assist]

statSync is called without error handling inside the pushWithMtime helper. If a file is deleted or becomes inaccessible between the vault walk and this call, the entire tool execution will fail. It is safer to wrap this in a try-catch block to skip files that cannot be accessed.

        const pushWithMtime = (relPath: string, v: unknown): void => {
          try {
            const st = statSync(this.resolve(relPath));
            results.push({ path: relPath, value: v, mtime: st.mtimeMs });
          } catch {
            // Skip files that disappeared or are inaccessible
          }
        };