Souta d1f47952b4 docs: plugin compatibility matrix skeleton (Tier 1-B(2)) ... Living doc covering each plugin the user actually runs (Dataview, Templater, Kanban, Excalidraw, Thino, Commander, Emoji Shortcodes, Heatmap Calendar, Meta Bind, Omnisearch, QuickLatex). Most rows are "expected to work" based on architectural read of how the plugin accesses the vault — the ✅ "verified" status is reserved for plugins that have been smoke-tested in the dev vault. Each row's status legend, per-plugin smoke-test checklist, and a "known footguns" section covering the patterns that trip plugins across the board: - direct app.vault.adapter.basePath joins (worker-thread escapes, raw fs reads) - worker-thread JS contexts that don't see our patched adapter - Node fs.watch against basePath - manually-built app://local/<path> URLs The doc explicitly says it's maintained by hand from manual smoke testing; there's no auto-verification. README.md already references docs/plugin-compatibility.md. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>		2026-04-26 22:14:11 +09:00
..
plugin-compatibility.md	docs: plugin compatibility matrix skeleton (Tier 1-B(2))	2026-04-26 22:14:11 +09:00