cleanup: remove completed mesh tasks from backlog, update AGENTS.md + wishes

- Remove TASK-048/049/050 (completed in round 32, now in done/)
- Update AGENTS.md with adversarial collaboration loop docs
- Update start-here.md to point to handoff log
- Add Tom blocker wishes for browser spec naming + upstream scope

Author: subtleGradient

.tasks/DELEGATE_WORK_HANDOFF.md

@@ -257,7 +257,8 @@ Root cause: Multi-table crsql_changes vtab rowid slab assignment not implemented
 - `.tasks/done/TASK-052-web-browser-test-triage.md`
 
 **Commits**
-- Pending — changes made by subagent in `zig/src/changes_vtab.zig`
+- `3fc49dbe` — delegate round 34: fix zig rowid slab cache invalidation (TASK-051, 052)
+- `e466ae2c` — cleanup: remove completed mesh tasks from backlog, update AGENTS.md + wishes
 
 **Modified files**
 - `zig/src/changes_vtab.zig` (schema cache invalidation fix)
@@ -327,4 +328,3 @@ Running 18 tests using 2 workers
 **Known gaps / unverified claims**
 - TypeScript packages have type errors (visible in project diagnostics) — these are pre-existing from Round 32, not introduced by this round
 - No coverage captured
-- Commit not yet created (will be done after handoff update)

.tasks/backlog/TASK-048-crsql-mesh-protocol-schema-reuse.md

@@ -0,0 +1,29 @@
+# Tom blocker: pick browser runtime spec + package boundary
+
+## What’s blocked
+All browser multi-tab work is spec-gated and currently blocked on a naming/boundary decision:
+- `.tasks/backlog/TASK-056-tom-browser-spec-naming.md`
+
+Downstream tasks blocked by this:
+- `.tasks/backlog/TASK-053-spec-browser-runtime-phase1.md` (Phase 1 instructions)
+- `.tasks/backlog/TASK-054-spec-browser-runtime-phase2.md` (Phase 2 requirements)
+- `.tasks/backlog/TASK-031-web-service-worker-fallback.md` (implementation)
+- `.tasks/backlog/TASK-032-web-reactive-subscriptions.md` (implementation)
+
+## What Tom needs to decide
+Please reply by updating `.tasks/backlog/TASK-056-tom-browser-spec-naming.md` with:
+- Spec directory name under `effect-native/.specs/`
+  - Example options: `crsqlite-web-multitab`, `crsql-mesh-runtime-web`, `crsqlite-browser-runtime`
+- Intended npm package name(s)
+  - One package vs split (coordinator / client / provider)
+- One sentence boundary per package
+
+## Why this matters
+If we guess the package boundaries, we’ll write the wrong spec tree and waste a round.
+
+## Where to look for context
+- Proposal: `research/zig-cr/96-proposal-multitab-wasm-sqlite-crsqlite.md`
+- Spec workflow rules: `effect-native/.specs/AGENTS.md`
+
+## Added
+- 2025-12-15

.tasks/backlog/TASK-049-crsql-mesh-engine-phase4.md

@@ -0,0 +1,19 @@
+# Tom blocker: scope zig-sqlite upstream feedback capture
+
+## What’s blocked
+Upstream feedback capture is blocked on scope:
+- `.tasks/backlog/TASK-055-tom-scope-upstream-feedback.md`
+- `.tasks/backlog/TASK-037-zig-sqlite-upstream-feedback-blocked.md`
+
+## What Tom needs to decide
+Please reply by updating `.tasks/backlog/TASK-037-zig-sqlite-upstream-feedback-blocked.md` (or completing `.tasks/backlog/TASK-055-tom-scope-upstream-feedback.md`) with:
+- How many upstream idea cards you want (3 / 5 / 10)
+- Whether cards may reference `.refs/zig-sqlite` directly
+- Whether we’re allowed to patch `.refs/zig-sqlite` locally for experiments (no upstream PR)
+- Any “must include” topics
+
+## Why this matters
+Without scope we either under-deliver (too few / wrong topics) or create noise.
+
+## Added
+- 2025-12-15

.tasks/backlog/TASK-050-crsql-mesh-runtime-node-phase4.md

@@ -11,15 +11,13 @@ If you’re asking “what’s left?” start here:
 
 ## Next parallel work (curated)
 
-- Global mesh (TS, Phase 4 implementation gaps):
-  - `.tasks/backlog/TASK-048-crsql-mesh-protocol-schema-reuse.md`
-  - `.tasks/backlog/TASK-049-crsql-mesh-engine-phase4.md`
-  - `.tasks/backlog/TASK-050-crsql-mesh-runtime-node-phase4.md`
 - Web phase 2 (TS, spec-gated):
   - `.tasks/backlog/TASK-031-web-service-worker-fallback.md`
   - `.tasks/backlog/TASK-032-web-reactive-subscriptions.md`
 - Upstream feedback capture (blocked): `.tasks/backlog/TASK-037-zig-sqlite-upstream-feedback-blocked.md`
 
+(For what just happened in the last delegate round, start at `.tasks/DELEGATE_WORK_HANDOFF.md` and then confirm against `effect-native/.specs/` and `effect-native/packages-native/`.)
+
 ## Rules of the game (thing-golf)
 
 Prefer fewer, sharper “Things”:

.wishes/blocked-on-tom/tom-browser-spec-naming.md

@@ -46,7 +46,17 @@ Workflow:
 
 Meaning: reconcile intended docs/specs vs built reality, then refresh `.tasks/`.
 
+"Delegate work" and "Update tasks" are an adversarial collaboration loop:
+- Delegate phase writes **claims + evidence** into `.tasks/DELEGATE_WORK_HANDOFF.md`.
+- Update phase tries to **invalidate** those claims by reconciling specs vs implementation.
+- Gap backlog (`research/zig-cr/92-gap-backlog.md`) is the opposite evergreen handoff (update→delegate).
+
 Do this, in order:
+0. Read the delegate evidence first:
+   - `.tasks/DELEGATE_WORK_HANDOFF.md`
+   - Treat it as *claims to falsify*.
+   - Prefer using the captured test output + coverage notes to avoid rerunning expensive tests.
+   - If evidence is missing (no commands, no output, no repro steps), assume the claim is unproven.
 1. Snapshot the inbox + queue:
    - `.wishes/*.md`
    - `.tasks/{active,backlog,done}/`