start

Author: subtleGradient

…ASK-144-cross-platform-compat-no-skip.md …ASK-144-cross-platform-compat-no-skip.md.tasks/triage/TASK-144-cross-platform-compat-no-skip.md renamed to .tasks/active/TASK-144-cross-platform-compat-no-skip.md .tasks/triage/TASK-144-cross-platform-compat-no-skip.md renamed to .tasks/active/TASK-144-cross-platform-compat-no-skip.md

@@ -6,7 +6,7 @@ Ensure the cross-platform compatibility harness is a reliable invalidation tool
 Currently `zig/harness/test-cross-platform-compat.sh` can SKIP entirely when it cannot find the Rust/C extension.
 
 ## Status
-- State: triage
+- State: active
 - Priority: medium
 
 ## Problem Statement

…schema-evolution-no-acceptable-errors.md …schema-evolution-no-acceptable-errors.md.tasks/triage/TASK-145-schema-evolution-no-acceptable-errors.md renamed to .tasks/active/TASK-145-schema-evolution-no-acceptable-errors.md .tasks/triage/TASK-145-schema-evolution-no-acceptable-errors.md renamed to .tasks/active/TASK-145-schema-evolution-no-acceptable-errors.md

@@ -4,7 +4,7 @@
 Turn the "acceptable error" paths in `zig/harness/test-schema-evolution.sh` into explicit, stable behavior assertions, so schema-evolution sync does not silently mask real compatibility issues.
 
 ## Status
-- State: triage
+- State: active
 - Priority: medium
 
 ## Problem Statement

…ss-open-modification-interoperability.md …ss-open-modification-interoperability.md.tasks/triage/TASK-147-cross-open-modification-interoperability.md renamed to .tasks/active/TASK-147-cross-open-modification-interoperability.md .tasks/triage/TASK-147-cross-open-modification-interoperability.md renamed to .tasks/active/TASK-147-cross-open-modification-interoperability.md

@@ -6,7 +6,7 @@ Change the Zig implementation to match the Rust/C implementation such that a dat
 This is a hard requirement.
 
 ## Status
-- State: triage
+- State: active
 - Priority: highest
 
 ## Problem Statement

…SK-143-cross-open-modification-compat.md …SK-143-cross-open-modification-compat.md.tasks/triage/TASK-143-cross-open-modification-compat.md renamed to .tasks/done/TASK-143-cross-open-modification-compat.md .tasks/triage/TASK-143-cross-open-modification-compat.md renamed to .tasks/done/TASK-143-cross-open-modification-compat.md

@@ -6,7 +6,7 @@ Enable a database created by one CR-SQLite implementation (Zig vs Rust/C) to be
 This gap is currently explicitly marked as "known limitation" in `zig/harness/test-cross-open-parity.sh` (XO-003, XO-004, XO-006).
 
 ## Status
-- State: triage
+- State: done (superseded by TASK-147)
 - Priority: high
 
 ## Problem Statement
@@ -59,4 +59,4 @@ When an implementation opens a DB created by the other and attempts INSERT/UPDAT
 - 2025-12-21: Created task from known-fail cross-open modification tests.
 
 ## Completion Notes
-(Empty until done.)
+- 2025-12-21: Superseded by TASK-147 which has a more specific implementation plan (unify on Rust/C trigger schema).