Johannes Millan 89066aca51 docs(sync): mark subtask orphan detection as false positive ... Re-evaluated the "missing subtask cascade in tag deletion" issue. The current behavior is correct: - A subtask with a surviving parent is NOT orphaned - it's accessible through the parent in the UI - If a parent is orphaned, its subtasks ARE correctly deleted - Subtasks always have parentId, so they're never directly orphaned This is intentional behavior, not a bug.		2025-12-12 20:47:48 +01:00
..
hybrid-manifest-architecture.md	docs: update operation log architecture paths	2025-12-12 20:46:26 +01:00
operation-log-best-practises2.md	docs: clean up execution plan by removing completed tasks and focusing on future enhancements	2025-12-12 20:46:25 +01:00
operation-log-implementation-review.md	docs(sync): mark subtask orphan detection as false positive	2025-12-12 20:47:48 +01:00
operation-log-integration-testing-plan.md	test(oplog): add integration tests for multi-client sync and state consistency	2025-12-12 20:46:27 +01:00
operation-log-sync-best-practices.md	feat(sync-server): implement operation log sync API	2025-12-12 20:46:12 +01:00
pfapi-sync-persistence-architecture.md	docs: plan operation logs again 6	2025-12-12 20:46:05 +01:00
replace-pfapi-with-oplog-plan.md	docs(sync): replace PFAPI with operation log sync for all providers	2025-12-12 20:47:47 +01:00
server-sync-architecture.md	feat(sync-server): implement operation log sync API	2025-12-12 20:46:12 +01:00
supersync-e2e-test-plan.md	feat(e2e): add SuperSync E2E test infrastructure for multi-client sync	2025-12-12 20:47:41 +01:00
synthesized-delta-sync-analysis.md	docs: analysis of delta sync 2	2025-12-12 20:46:05 +01:00
synthesized-delta-vs-oplog.md	docs: analysis of delta sync 3	2025-12-12 20:46:05 +01:00