Follow-ups to the v0.6.0 knowledge base that were parked as unscheduled work: two heading-anchor defects, derived related-note suggestions, templates and daily notes, and shared graph nodes in the concept editor.

v0.11.0 - Knowledge Base Follow-ups

Done	Area	Item
⬜	WIKI	A heading whose text also appears in the body can land the preview on the body line - MarkdownView.scroll_to_heading searches the rendered text for the heading’s line (that is what makes source lines and rendered lines agree), so a paragraph that says exactly the same thing and appears first wins the search. Found while closing the fragment item (2026-10-18); the renderer emits no anchors, so text matching was the chosen approach. Display-only - a wrong scroll inside the right note, never a wrong note. Fix direction only if it is noticed in use: have GptyMarkdown.render track each heading’s plain-text offset while emitting events and map that offset with get_character_line, or emit an invisible marker the view can find.
⬜	WIKI	Setext headings have no anchor - MarkdownAnchors recognizes ATX (#) headings only, so [[note#Title]] does not land on a Title over === heading, and a source line under one derives no anchor (it lands at the nearest ATX heading above, or the top). The preview renders setext headings (pulldown-cmark does), so the gap is navigation, not display. Found while closing the fragment item (2026-10-18); rare in Obsidian-shaped notes, which is why it was scoped out. Fix direction: add the two-line ===/--- form to the scanner - carefully, because a leading --- is frontmatter and a thematic break is not a heading.
⬜	WIKI	Suggested related notes from the FTS index - score a note’s own top terms against the rest of the vault (notes_fts already holds them, porter-stemmed) and surface the neighbours as suggestions: fully derived, no store, no authoring, no trust question, display-only like everything else in the graph. This is the middle layer between measured mention counts and declared weights (v0.6.0), and it answers “what else is about this” without an LLM; queue it once the link layer has settled.
⬜	WIKI	Templates - a designated folder whose contents are inserted into the open note with a closed token table ({{date}}, {{time}}, {{title}}, {{vault}}) expanded in Rust and inserted as an edit, so the user still saves and templates open no second write path into the vault. Parked off-release by the owner’s call (2026-10) because nothing depends on it; scheduled here by the roadmap restructure, and it still adds no trust surface. The scripting half of this on the Obsidian side is its Templater plugin - the ecosystem this project stays out of. Daily notes are a cron-job on a template (open or create <folder>/<pattern>.md for today, then apply one) and can ride along when this is built, reusing the create-note verb; they are not worth an item of their own.
⬜	CONCEPT	Shared graph nodes (free DAG) - the visual editor’s rules are chains because a compiled entry’s identity is the trigger’s name: one trigger = one rule, and a shared condition or action would compile two entries under one name. Fan-in/fan-out needs OR’d triggers (triggers: [regex…]) and a rule id independent of the trigger name in the vocabulary. Deferred from v0.5.4 - revisit with demand evidence, not before.