docs: publish Obsidian and Logseq synonym search examples

[AlexMikhalev]

The tutorial now includes ready-to-open Obsidian and Logseq examples. Each keeps synonyms:: Risk, Concern in the Risk concept note, with a separate community garden brief and saved results. Readers can search for “concern” and retrieve three decisions written using “risk”. Search targets only the project notes, so neither synonym definitions nor saved results can supply a literal query hit.

The Logseq example includes native alias:: Concern, linked blocks, an embedded project brief, and instructions verified through Logseq 2.0.2’s File to DB graph import. Both examples reuse the unchanged graph exported from Terraphim Editor. Their screenshots show actual installed applications; CLI results are clearly described as saved output. The additional Logseq graph-view screenshot shows the garden brief’s native page links to Risk, Start here and Concern search. Its caption distinguishes page links from the supplied Terraphim synonym graph.

The public page uses practical reader steps and download links. Detailed build provenance remains in downloadable records. Jason Fried’s original video receives inspiration credit.

Validation at 6626de7016e96580af9b41b2360fb0ac55f83cb7:

• All 25 site tests and both required CI checks pass: https://github.com/terraphim/terraphim.ai/actions/runs/38263837636
• Preview deployment passed: https://github.com/terraphim/terraphim.ai/actions/runs/38263863101
• Verified preview: https://2b15b9a2.terraphim-ai.pages.dev/how-tos/synonym-search/#try-it-with-a-logseq-graph
• All 48 deployed downloads match tested bytes. Fresh extraction of both downloaded ZIPs followed by released terraphim-grep 1.21.19 reproduces zero baseline passages and three exact saved source passages.
• Native Logseq import and browser rendering verified; independent review found no blocking issues. The graph-view follow-up was independently reviewed with no findings; the 16-file Logseq ZIP was extracted and rerun with the released CLI.
• Obsidian ZIP SHA-256: acd2ec71aa2af50791c1689314c10b1edc6962081f80ed81d912abe0b3077ca4.
• Logseq ZIP SHA-256: f150c1f2190fdbd21f5d34ae92a8667e7611baa81ddca8042082220cbe45427c.

Production deployment uses the main-branch Cloudflare workflow after review and merge. The prepared DEV, Discourse and GitHub updates are held until production downloads are verified. LinkedIn stays in draft.