notion db track fails closed on packaged runtime (breaks sqlite demo + demo-env replica)

Summary

notion db track no longer establishes a local SQLite replica on the current packaged/flake notion runtime (notion 0.1.0+unknown, committed 2026-07-07). It fails closed.

Impact

• Breaks demo/sqlite/reset.sh (uses notion db track <ds> . --mode local).
• demo/env/demo-env new degrades loudly for the sqlite demo: the Notion DB + rows are still created and usable, but the local .sqlite replica is not; manifest records sqlite.tracked: false.

Root cause (two layers)

1. Wrapper routing omits track. The flake notion bin routes only init|pull|push|sync|export|status|conflicts|forget|restore|doctor to notion-db-runtime; track is missing, so notion db track falls through to the Bun-unsupported unwrapped binary (… imports node:sqlite …). The routing list also has stale verbs (init/pull/push) not in the actual CLI.
2. Runtime fails closed even when invoked directly. notion-db-runtime track <ds> . --mode local --no-materialize-bodies exits non-zero with no diagnostic output, writing only .notion/v1/state.sqlite. Also: the new runtime creates <workspace>/<database-id>.sqlite and rejects --sqlite for track.

Repro (inside devenv shell)

cd $(mktemp -d)
RT=$(grep -oE '/nix/store/[^ ]*notion-db-runtime[^ ]*/bin/notion-db-runtime' $(command -v notion) | head -1)
"$RT" track <data-source-id> . --mode local --no-materialize-bodies; echo exit=$?  # exit=1, no output

Asks

• Add track to the wrapper's routed-verb list (drop stale init/pull/push).
• Make the runtime emit an error on track failure instead of a silent non-zero exit.

Filed as out-of-scope follow-up from the demo/env (demo-env CLI) work.

Start with the flake notion wrapper's routed-verb list and the notion-db-runtime entry point; run the provided packaged-runtime reproduction in a temporary directory. Done means track is routed through the runtime and failures produce diagnostics instead of a silent non-zero exit, while the SQLite demo can establish its local replica.