Unblock browser runtime and web tasks after Phase 2 spec completion

Author: subtleGradient

.tasks/backlog/TASK-031-web-service-worker-fallback.md

@@ -4,7 +4,7 @@
 - [x] Planned
 - [ ] Assigned
 - [ ] In Progress
-- [x] Blocked (reason: TS work must follow spec-first in `effect-native/`)
+- [ ] Blocked (reason: TS work must follow spec-first in `effect-native/`)
 - [ ] Complete
 
 ## Priority
@@ -18,16 +18,17 @@ subagent (general)
 - Gap backlog: `research/zig-cr/92-gap-backlog.md` (Multi-tab Web Architecture)
 - TS workflow rules: `effect-native/.specs/AGENTS.md`
 - Browser spec tasks (unblock):
-  - `.tasks/backlog/TASK-056-tom-browser-spec-naming.md`
-  - `.tasks/backlog/TASK-053-spec-browser-runtime-phase1.md`
-  - `.tasks/backlog/TASK-054-spec-browser-runtime-phase2.md`
+  - ✅ `.tasks/done/TASK-056-tom-browser-spec-naming.md` (concept name + boundary deferral)
+  - ✅ `effect-native/.specs/crsql-mesh/requirements.md` (contains Phase 2 EARS for browser multi-tab)
+  - ✅ `effect-native/.specs/crsql-mesh/design.md` (contains browser multi-tab design sketch)
+  - ✅ `effect-native/.specs/crsql-mesh/plan.md` (contains RGRTDD slices)
 
 ## Constraint
 This work is TypeScript-heavy.
 
 Per `AGENTS.md` (TypeScript Work Rule): **all TypeScript work happens in the `effect-native/` submodule** and must follow the spec-first workflow in `effect-native/.specs/AGENTS.md`.
 
-This task stays blocked until Phase 2 requirements exist for the browser/runtime surface under `effect-native/.specs/AGENTS.md`.
+This task is unblocked: Phase 2 requirements now exist in `effect-native/.specs/crsql-mesh/requirements.md` (browser multi-tab section).
 
 ## Description
 Add a Service Worker fallback for environments where SharedWorker is unavailable.

.tasks/backlog/TASK-032-web-reactive-subscriptions.md

@@ -4,7 +4,7 @@
 - [x] Planned
 - [ ] Assigned
 - [ ] In Progress
-- [x] Blocked (reason: TS work must follow spec-first in `effect-native/`)
+- [ ] Blocked (reason: TS work must follow spec-first in `effect-native/`)
 - [ ] Complete
 
 ## Priority
@@ -18,16 +18,17 @@ subagent (general)
 - Gap backlog: `research/zig-cr/92-gap-backlog.md` (Multi-tab Web Architecture)
 - TS workflow rules: `effect-native/.specs/AGENTS.md`
 - Browser spec tasks (unblock):
-  - `.tasks/backlog/TASK-056-tom-browser-spec-naming.md`
-  - `.tasks/backlog/TASK-053-spec-browser-runtime-phase1.md`
-  - `.tasks/backlog/TASK-054-spec-browser-runtime-phase2.md`
+  - ✅ `.tasks/done/TASK-056-tom-browser-spec-naming.md` (concept name + boundary deferral)
+  - ✅ `effect-native/.specs/crsql-mesh/requirements.md` (contains Phase 2 EARS for browser multi-tab)
+  - ✅ `effect-native/.specs/crsql-mesh/design.md` (contains browser multi-tab design sketch)
+  - ✅ `effect-native/.specs/crsql-mesh/plan.md` (contains RGRTDD slices)
 
 ## Constraint
 This work is TypeScript-heavy.
 
 Per `AGENTS.md` (TypeScript Work Rule): **all TypeScript work happens in the `effect-native/` submodule** and must follow the spec-first workflow in `effect-native/.specs/AGENTS.md`.
 
-This task stays blocked until Phase 2 requirements exist for the browser/runtime surface under `effect-native/.specs/AGENTS.md`.
+This task is unblocked: Phase 2 requirements now exist in `effect-native/.specs/crsql-mesh/requirements.md` (browser multi-tab section).
 
 ## Description
 Provide a narrow notification/subscription surface so tab B can react when tab A writes.

.tasks/backlog/TASK-053-spec-browser-runtime-phase1.md

@@ -4,7 +4,7 @@
 - [x] Planned
 - [ ] Assigned
 - [ ] In Progress
-- [x] Blocked (reason: requires Phase-approval workflow in `effect-native/.specs/AGENTS.md`)
+- [ ] Blocked (reason: requires Phase-approval workflow in `effect-native/.specs/AGENTS.md`)
 - [ ] Complete
 
 ## Priority
@@ -35,16 +35,16 @@ Per Tom (2025-12-16), defer package boundaries and npm names until they block pr
 - `research/zig-cr/92-gap-backlog.md` (link to spec)
 
 ## Acceptance Criteria
-- [ ] New Phase 1 spec exists with:
+- [x] Unified Phase 1 spec exists in `effect-native/.specs/crsql-mesh/instructions.md` with:
   - Context
   - User Story
   - High-Level Goals
   - Out of Scope
-- [ ] The spec explicitly references the constraints from `research/zig-cr/96-proposal-multitab-wasm-sqlite-crsqlite.md`:
+- [x] The spec explicitly references the constraints from `research/zig-cr/96-proposal-multitab-wasm-sqlite-crsqlite.md`:
   - SharedWorker preferred, Service Worker fallback
   - No COOP/COEP requirement
   - Provider-tab dedicated worker owns OPFS
-- [ ] The spec calls out the minimal “notification/subscription” goal (db_version advanced events) needed by `.tasks/backlog/TASK-032-web-reactive-subscriptions.md`.
+- [x] The spec calls out the minimal “notification/subscription” goal (db_version advanced events) needed by `.tasks/backlog/TASK-032-web-reactive-subscriptions.md`.
 
 ## Progress Log
 ### 2025-12-15

.tasks/backlog/TASK-054-spec-browser-runtime-phase2.md

@@ -4,7 +4,7 @@
 - [x] Planned
 - [ ] Assigned
 - [ ] In Progress
-- [x] Blocked (reason: depends on Phase 1 instructions approval)
+- [ ] Blocked (reason: depends on Phase 1 instructions approval)
 - [ ] Complete
 
 ## Priority
@@ -37,10 +37,10 @@ Per Tom (2025-12-16), package boundaries and npm names are deferred until they b
 - `research/zig-cr/92-gap-backlog.md` (link to spec)
 
 ## Acceptance Criteria
-- [ ] Requirements use EARS notation per `effect-native/.specs/AGENTS.md`.
-- [ ] Service Worker fallback behavior is specified precisely enough to implement `.tasks/backlog/TASK-031-web-service-worker-fallback.md`.
-- [ ] Subscription/notification behavior is specified precisely enough to implement `.tasks/backlog/TASK-032-web-reactive-subscriptions.md`.
-- [ ] Requirements define clear failure modes (e.g., provider death / re-election semantics at MVP level).
+- [x] Requirements use EARS notation per `effect-native/.specs/AGENTS.md`.
+- [x] Service Worker fallback behavior is specified precisely enough to implement `.tasks/backlog/TASK-031-web-service-worker-fallback.md`.
+- [x] Subscription/notification behavior is specified precisely enough to implement `.tasks/backlog/TASK-032-web-reactive-subscriptions.md`.
+- [x] Requirements define clear failure modes (e.g., provider death / re-election semantics at MVP level).
 
 ## Progress Log
 ### 2025-12-15