Add obsidian-wiki as a local workspace

[Ar9av]

Summary

Add obsidian-wiki as a core Local Workspace for building an agent-maintained, Obsidian-compatible second brain.

This PR:

• adds a full solution profile using the repository template
• wires the project into all five lifecycle decision paths and the Local Workspaces snapshot
• adds it to the solution layer and capability matrix
• adds focused comparisons for setup burden, agent access, local/cloud deployment, and personal/team fit

Why it belongs

obsidian-wiki provides a shipped, multi-agent knowledge lifecycle rather than a bare note app or generic RAG bridge: source and agent-history ingest, merge-in-place organization, provenance and delta tracking, graph-aware queries, linting, deduplication, cross-linking, synthesis, export, rebuild/restore, and scheduled maintenance. The source of truth remains a local Markdown vault.

Sources and verification

Claims were reviewed against primary project sources on 2026-07-11:

• https://github.com/Ar9av/obsidian-wiki
• https://github.com/Ar9av/obsidian-wiki/tree/main/.skills
• https://github.com/Ar9av/obsidian-wiki/blob/main/pyproject.toml
• https://github.com/Ar9av/obsidian-wiki/blob/main/LICENSE
• https://pypi.org/project/obsidian-wiki/

Local validation performed:

• git diff --check
• checked all relative Markdown links in README.md, solutions/, and comparisons/ resolve

Known limitations

• knowledge quality and write-back behavior depend on the agent executing each skill
• no built-in SaaS connector platform, dedicated memory API, or MCP server
• evolution is invoked or scheduled, not a continuously managed consolidation service
• team sync, permissions, concurrent edits, and approval workflows are external
• local vault ownership does not imply that the chosen model, sync, browser, or optional indexing provider is local or private