f6bc47b347
Previous JSONL fallback called `store.addNode(defaultParentId, root)` and reported `status: 'applied'` regardless of outcome. But `addNode` returns void and silently no-ops via `insertNodeInTree` when the parent id can't be resolved (stale `defaultParentId`, empty doc, etc). The caller would then count the dispatch as a successful insert even though the doc was unchanged. Verify each root via `getNodeById(root.id)` immediately after addNode. Outcomes now: - All roots land → `applied`, message lists count. - Some land, some don't → `applied` with partial-failure note in message; only the live roots are returned in `insertedNodes`. - No roots land → `failed` with diagnostic naming the parent id and the first few failed root ids — caller surfaces this to the orchestrator retry path instead of silently absorbing the loss. |
||
|---|---|---|
| .. | ||
| cli | ||
| desktop | ||
| web | ||