Skip to content
FSS Knowledge Base

Verify and install Phase 2 of the Obsidian-native upgrade set

Section titled “Verify and install Phase 2 of the Obsidian-native upgrade set”

Background

Section titled “Background”

Spun out of Obsidian-Guide-KB-OS-Upgrades.md (Phase 1 verdict: piecemeal upgrade, not the paid Obsidian Starter Kit — full reasoning + 4 rounds of evidence in that task’s history). Phase 1 evaluated the buy-vs-piecemeal question and produced a scored candidate list in KB-OS/UPGRADES.md and Focus/UPGRADES.md. This task executes the concrete next steps that Phase 1 could not finish inside a CLI-only session — GUI plugin installs and in-app visual verification.

Four candidates are teed up, all Talbot-approved for install where a plugin is involved:

  1. Related-Tasks.base / Related-Notes.base — already built at Core/Processes/Projects/KB-OS/Bases/, native Obsidian Bases (no plugin), adapted from the “No Plugins, No AI” clipping’s two-tag discovery pattern to KB-OS’s actual task/note schema. Not yet visually verified — built and committed sight-unseen because this CLI session cannot render Obsidian’s UI.
  2. Kanban Action Planner (plugin, MIT license, free, approved) — its WBS view renders parent/child hierarchy as a collapsible tree with rollup calculations. This is the load-bearing test for whether ecco-replacement-research’s “no candidate handles nested hierarchy” verdict (2026-08-20) still holds.
  3. Dataview Serializer (plugin, approved, revertible) — materializes query output as durable Markdown between comment markers. Candidate fix for ecco-view.js’s render-only output being invisible to grep/AI.
  4. Obsidian CLI (official, free, not yet installed) — the actual verification mechanism for #1-#3. Its obsidian eval (run JS inside the running app) and screenshot commands are the precedented path for an AI agent to confirm an Obsidian UI change actually rendered correctly, without a human’s eyes — see the obsidian-live-preview-stale-render memory precedent from a past task. Worth installing specifically so future KB-OS/Focus sessions can self-verify Obsidian-side changes instead of always asking Talbot to eyeball it.

Tasks

Section titled “Tasks”
  • Talbot, GUI steps (Claude cannot do these — no Windows GUI/computer-use access in this environment, confirmed 2026-08-25):
    • Install Kanban Action Planner via Settings → Community plugins → Browse.
    • Install Dataview Serializer via the same path.
    • Install the official Obsidian CLI (help.obsidian.md/cli) — one-time setup, needed for #4 below.
    • Open Related-Tasks.base and Related-Notes.base in Obsidian; confirm they render without error.
  • Claude, once Obsidian CLI is installed and Obsidian is running: attempt obsidian eval/screenshot commands from this WSL session to programmatically verify the two .base files render correctly and to check Kanban Action Planner’s WBS view against a real multi-level task tree from ecco-notepads-build — replacing “ask Talbot to eyeball it” with a self-verified result where the CLI’s reach from WSL to a Windows-side running Obsidian instance allows it. If the CLI can’t be reached from WSL (likely, since it talks to a local Obsidian instance and WSL/Windows networking may not bridge it), say so plainly and fall back to Talbot’s visual confirmation — don’t claim verification that didn’t happen.
  • Report Kanban Action Planner’s hierarchy test result back into ecco-notepads-build.md (the Ecco-replacement thread), not just here — that’s the file tracking the actual replacement decision.
  • Report Dataview Serializer’s fit against ecco-view.js output back into Focus/UPGRADES.md / ecco-notepads-build.md — keep or revert.
  • Update KB-OS/UPGRADES.md and Focus/UPGRADES.md to mark each tested candidate resolved (adopted / rejected / reverted) once results are in.

Success Criteria

Section titled “Success Criteria”

Done when: both Bases files are confirmed rendering correctly in Obsidian (or fixed if not), Kanban Action Planner’s hierarchy test has a clear yes/no answer recorded in ecco-notepads-build, Dataview Serializer has a keep/revert decision recorded, and the Obsidian CLI is either installed-and-usable-from-WSL or documented as not reachable from this environment. Does not require solving the Ecco-replacement question itself — only recording whether Kanban Action Planner clears the specific hierarchy bar ecco-replacement-research set.