++

Author: subtleGradient

.tasks/backlog/TASK-207-reenable-ci-for-release.md

@@ -5,8 +5,8 @@ Re-enable GitHub Actions CI when approaching public release.
 
 ## Status
 - State: backlog
-- Priority: LOW (blocked until release decision)
-- Blocked by: `.wishes/blocked-on-tom/release-readiness-decision.md`
+- Priority: LOW (requires execution; decision made)
+- Blocked by: (none)
 - Created: 2025-12-25
 
 ## Context
@@ -16,25 +16,26 @@ CI was disabled (TASK-206) because:
 3. macOS GitHub Actions has transient nix install issues
 
 Before re-enabling, we need to:
-1. Decide if WASM support is required for release
+1. Implement WASM build (required for release)
 2. Set up oracle binaries in CI (or skip oracle-dependent tests)
 3. Fix any remaining platform-specific issues
 
 ## Files to Modify
 - `.github/workflows/zig-tests.yaml` — Re-enable and fix
 
 ## Acceptance Criteria
-1. [ ] Release readiness decision made (see blocked-on-tom wish)
+1. [x] Release readiness decision made (see blocked-on-tom wish)
 2. [ ] CI passes on Linux (ubuntu-latest)
 3. [ ] CI passes on macOS (macos-latest)
-4. [ ] WASM build passes OR is explicitly removed from scope
+4. [ ] WASM build passes
 
 ## Parent Docs / Cross-links
 - Disabling task: `.tasks/done/TASK-206-disable-ci-temporarily.md` (after completion)
 - Release decision: `.wishes/blocked-on-tom/release-readiness-decision.md`
 
 ## Progress Log
 - 2025-12-25: Created, blocked on release decision.
+- 2025-12-25: Tom decided: scope = Native + WASM + Browser; version = `0.16.300-preview`; distribution = npm (effect-native) + GitHub Releases + nix tags; docs = none for preview.
 
 ## Completion Notes
 (Empty until done.)

.tasks/triage/TASK-208-zig-composite-pk-sync.md

@@ -77,7 +77,7 @@ rm -rf "$TMPDIR"
 ## Parent Docs / Cross-links
 
 - Related: `.tasks/done/TASK-202-fix-crsql-changes-insert-failure.md` (single PK fix)
-- Related: `.tasks/active/TASK-205-fix-inventory-app-test.md` (documents xfail)
+- Related: `.tasks/done/TASK-205-fix-inventory-app-test.md` (documents xfail)
 - Test: `zig/harness/test-app-inventory.sh`
 
 ## Progress Log

.wishes/blocked-on-tom/implementation-agnostic-spec-suite.md

@@ -99,12 +99,7 @@ Try expressing the two hardest current tests as specs *without* embedding runner
 If either one forces bespoke runner code (“special-case this test”), the approach is suspect.
 
 ## Questions Tom needs to decide
-1) Does “any CR-SQLite implementation” mean:
-   - only loadable SQLite extensions (C/Zig), or
-   - also WASM + mobile runtimes?
-2) Should the spec suite assert:
-   - only public SQL surface behavior (preferred), or
-   - internal tables/triggers/layout too?
+Deferred until after first public release `0.16.300-preview`.
 
 ## Pointers
 - Zig harness runner: `zig/harness/test-parity.sh`

.wishes/blocked-on-tom/release-readiness-decision.md

@@ -50,4 +50,12 @@ When are we ready for our first public release of the Zig cr-sqlite implementati
 - `.tasks/backlog/TASK-207-reenable-ci-for-release.md`
 
 ## Tom's Decision
-(Pending)
+
+- Release scope: **Native + WASM + Browser**
+- Versioning: `0.16.300-preview`
+  - Rationale: upstream `cr-sqlite` abandoned around `v0.16.3`; this preview line targets full backwards compatibility with that surface, but remains preview until validated in multiple real products.
+- Distribution:
+  - npm (OIDC) via the `effect-native` repo
+  - native binaries via GitHub Releases
+  - nix via GitHub tags
+- Documentation requirement: none for first preview release