Implement notion-md v-next sync surface

Author: schickling-assistant

CHANGELOG.md

@@ -16,6 +16,8 @@ All notable changes to this project will be documented in this file.
 
 - **CI / Nix packages**: Refresh the stale `genie`, `megarepo`, `notion-md`, and `tui-stories` pnpm fixed-output hashes after the schema-first OTEL contract change updated the workspace dependency closure.
 
+- **@overeng/notion-md**: Move the v-next public CLI to `track` / `status` / `sync`: `track` is now the only page-id bootstrap command, `sync`/`status` operate on local self-describing files, write-capable paths support `--dry-run`, and `sync --watch` routes through the same source-aware reconcile engine as one-shot sync.
+
 - **CI / Nix packages**: Refresh the stale `workflow-report` pnpm fixed-output hash so the Storybook preview reporting step can build `#workflow-report` again after the branch rebase updated the workspace dependency closure.
 
 - **@overeng/restate-effect**: Made `Restate.run`'s type HONEST. A durable `ctx.run` step carries NO catchable typed failure: the inner effect runs via `Runtime.runPromise` inside `ctx.run`, so a typed `Effect.fail` only REJECTS the step (Restate retries; a give-up maps to a `RestateError` DEFECT) and never reaches the outer failure channel — the old `run<A, E, R>(…): Effect<A, E, …>` advertised a typed `E` that `catchTag`/`catchAll` would typecheck against but that could never fire. `run` is now `run<A, R>(name, effect: Effect<A, never, R>, options?): Effect<A, never, …>`, and `runExit` is `runExit<A, R>(…): Effect<Exit<A>, never, …>` — the honest OBSERVATION form, whose failure channel is `never` (an observed failure is a defect/interrupt `Cause`, not a phantom typed `E`). Domain errors now belong in the HANDLER body (classify the step's result there) or are encoded as VALUES inside the step; to force a durable retry, DIE inside the step. A passed typed-`E` inner effect is now a COMPILE error (negative-type assertion in `capability-inference.types.ts`). Callers reconciled: the saga integration test's failing `pay` step `Effect.die`s (was `Effect.fail`), and `examples/12-self-reschedule.ts`'s `pollComposedSource` returns a tagged VALUE with `E = never` (classified in the cycle body, unchanged). `examples/14-http-error-classification.ts` already used the die-the-step / classify-in-body strategies; only its prose was corrected. VRS: decision 0003 (#4 — corrects the earlier "keep the inner `E` flowing through `run`"), 03-effect-runtime / 04-error-boundary specs, the guide handbook, and a DEFERRED typed-failure-transport `run` note (an encoded `fail(E)` journaled via an error schema). No dependency changes.

packages/@overeng/notion-datasource-sync/docs/vrs/capability-gaps.md

@@ -89,9 +89,9 @@ public `INSERT INTO changes` is not part of the current e2e acceptance surface.
 
 ### G. Multi-data-source databases
 
-| Operation                                                                | Support     | Guard if blocked             | Promotion criteria (if fail-closed)                                             |
-| ------------------------------------------------------------------------ | ----------- | ---------------------------- | ------------------------------------------------------------------------------- |
-| `sync --from-notion` against a database with multiple child data sources | FAIL-CLOSED | `MultiDataSourceUnsupported` | Per-data-source file naming scheme + cross-DS query/relation semantics modeled. |
+| Operation                                                   | Support     | Guard if blocked             | Promotion criteria (if fail-closed)                                             |
+| ----------------------------------------------------------- | ----------- | ---------------------------- | ------------------------------------------------------------------------------- |
+| `track` against a database with multiple child data sources | FAIL-CLOSED | `MultiDataSourceUnsupported` | Per-data-source file naming scheme + cross-DS query/relation semantics modeled. |
 
 ## Current Fail-Closed Boundaries
 

packages/@overeng/notion-datasource-sync/docs/vrs/decisions/0004-track-is-the-adoption-verb.md

@@ -0,0 +1,23 @@
+# Track is the adoption verb
+
+Initial adoption of an existing Notion data source into a local SQLite workspace
+uses `notion db track <data-source-id-or-database-url> <workspace-root>`.
+Established reconciliation uses `notion db sync <workspace-root>`.
+
+## Status
+
+accepted
+
+## Considered Options
+
+- `sync --from-notion`: fewer top-level verbs, but makes `sync` accept both
+  remote identities and established local workspace roots.
+- `establish`: precise, but uncommon as a CLI verb and inconsistent with
+  NotionMD.
+- `track`: names the durable relationship, keeps adoption separate from
+  established reconciliation, and aligns with NotionMD.
+
+## Consequences
+
+`track` is remote-to-local only and never mutates Notion. `sync` operates only on
+established local workspaces and preserves the local-capture-first invariant.

packages/@overeng/notion-datasource-sync/docs/vrs/decisions/0005-init-pull-push-are-internal-phases.md

@@ -0,0 +1,23 @@
+# Init, pull, and push are internal phases
+
+Datasource sync exposes adoption (`track`), inspection (`status`), reconciliation
+(`sync` / `sync --watch`), export, conflict resolution, forget, restore, and
+doctor commands. Init, pull, and push remain implementation phases inside the
+reconcile engine, not public commands.
+
+## Status
+
+accepted
+
+## Considered Options
+
+- Public `init`/`pull`/`push`: exposes mechanical phases, but asks users to pick
+  a direction and makes partial bindings/product states easier to create.
+- Public `sync` only for established reconciliation: keeps the normal workflow on
+  the guarded local-capture-first loop.
+
+## Consequences
+
+Public writes flow through `sync`, `sync --watch`, conflict resolution, forget,
+restore, or adoption. Phase-level behavior stays observable through progress,
+structured output, spans, and dry-run plans.

packages/@overeng/notion-datasource-sync/docs/vrs/decisions/0006-authority-is-surface-and-event-based.md

@@ -0,0 +1,26 @@
+# Authority is surface and event based
+
+Datasource sync does not use NotionMD's `source: local | remote | shared`
+frontmatter model. Its authority model is per surface and event based: Notion is
+fresh observed remote state, the SQLite event log is durable local authority for
+accepted intents/outbox/conflicts/tombstones, and public replica tables are
+intent-entry and projection surfaces.
+
+## Status
+
+accepted
+
+## Considered Options
+
+- Import NotionMD Mirror/Shared terminology: consistent naming across packages,
+  but incorrectly suggests single-source overwrite modes for a bidirectional
+  SQLite control plane.
+- Keep datasource-specific authority vocabulary: matches the event log, outbox,
+  guarded materialization, and no-silent-LWW requirements.
+
+## Consequences
+
+The CLI can share verbs such as `track`, `status`, `sync`, and `sync --watch`
+with NotionMD, but datasource-sync keeps its own authority vocabulary. Public
+docs must explain authority through surfaces, observations, intents, events,
+outbox commands, and guarded materialization rather than source modes.

packages/@overeng/notion-datasource-sync/docs/vrs/glossary.md

@@ -27,6 +27,14 @@ row-membership or deletion authority; projected read-only as `debug_*`.
 
 ## Sync surfaces and identity
 
+**Authority model**:
+The cross-cutting rule for where each fact's authority lives. Datasource-sync
+authority is per surface and event based, not a file-level source mode. Notion is
+fresh observed remote state; the SQLite event log is durable local authority for
+accepted local facts; public replica tables are intent-entry/projection surfaces;
+materialization is guarded output.
+_Avoid_: importing NotionMD `source: local | remote | shared` semantics.
+
 **Surface**:
 The smallest independently-hashed unit a write targets — a single property value,
 a page body, or the schema. Conflicts and base hashes are per-surface.

packages/@overeng/notion-datasource-sync/docs/vrs/intuition.md

@@ -24,7 +24,7 @@ decision.
 Notion database
   shared human workspace
         |
-        | notion db sync --from-notion
+        | notion db track
         v
 <database-id>.sqlite
   local working copy
@@ -147,7 +147,7 @@ unit of local state for one Notion database.
 Start by establishing the local replica:
 
 ```sh
-notion db sync --from-notion <database-url-or-data-source-id> ./notion-workspace
+notion db track <database-url-or-data-source-id> ./notion-workspace
 ```
 
 Inspect the data: