Add .wishes/ inbox for async product owner communication

Author: subtleGradient

.wishes/README.md

@@ -0,0 +1,72 @@
+# Wishes Inbox
+
+This folder is for **Tom (Product Owner)** to asynchronously communicate wishes to AI agents.
+
+## How to Use
+
+1. **Drop a markdown file** in this folder with your wish
+2. **Name it descriptively**: `priority-description.md` (e.g., `high-add-fuzzing-tests.md`)
+3. **Agent will process** on next OODA loop iteration
+4. **File moves to `.wishes/done/`** when processed
+
+## File Format
+
+```markdown
+# [Title of Wish]
+
+## Priority
+high | medium | low
+
+## Description
+What you want to happen.
+
+## Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+
+## Notes (optional)
+Any context, links, or constraints.
+```
+
+## Example
+
+```markdown
+# Add Performance Benchmarks
+
+## Priority
+medium
+
+## Description
+I want to see how the Zig implementation compares to the Rust/C implementation in terms of:
+- Sync throughput (changes/second)
+- Memory usage during large syncs
+- Cold start time
+
+## Acceptance Criteria
+- [ ] Benchmark script exists at `zig/harness/bench-*.sh`
+- [ ] Results documented in `research/zig-cr/`
+- [ ] Can reproduce on CI
+
+## Notes
+Look at how hyperfine does benchmarking.
+```
+
+## Folder Structure
+
+```
+.wishes/
+├── README.md           # This file
+├── done/               # Processed wishes (moved here after completion)
+├── blocked/            # Wishes that can't be done yet (with reason in file)
+└── *.md                # Active wishes (inbox)
+```
+
+## For Agents
+
+When processing wishes:
+1. Read all `.md` files in `.wishes/` (not subdirs)
+2. Sort by priority (high > medium > low)
+3. Incorporate into current round planning
+4. Move to `.wishes/done/` when complete (append completion notes)
+5. Move to `.wishes/blocked/` if blocked (append reason)
+6. Update `research/zig-cr/92-gap-backlog.md` with relevant items

AGENTS.md

@@ -4,22 +4,70 @@ This file provides guidance to AI coding agents when working with code in this r
 
 ---
 
+## Product Owner Wishes System
+
+Tom (Product Owner) can asynchronously express wishes by dropping markdown files into `.wishes/`.
+
+### How It Works
+
+```
+.wishes/
+├── README.md           # Instructions for Tom
+├── done/               # Completed wishes (moved here with completion notes)
+├── blocked/            # Blocked wishes (moved here with reason)
+└── *.md                # Active wishes (inbox) - PROCESS THESE
+```
+
+### Agent Workflow for Wishes
+
+At the start of each OODA loop iteration:
+
+1. **Check `.wishes/` for new files** (not in subdirs)
+2. **Parse priority** from filename or content (`high-`, `medium-`, `low-` prefix or `## Priority` section)
+3. **Incorporate high-priority wishes** into current round planning
+4. **After completing a wish**:
+   - Move file to `.wishes/done/`
+   - Append completion notes (date, what was done, commit hash)
+5. **If wish is blocked**:
+   - Move file to `.wishes/blocked/`
+   - Append reason why it's blocked
+6. **Update `research/zig-cr/92-gap-backlog.md`** with relevant items from wishes
+
+### Wish File Format
+
+```markdown
+# [Title]
+
+## Priority
+high | medium | low
+
+## Description
+What to do.
+
+## Acceptance Criteria
+- [ ] Criterion 1
+- [ ] Criterion 2
+```
+
+---
+
 ## Zig CR-SQLite Rewrite: Orchestration Workflow
 
 This project is undergoing a major rewrite from C/Rust to Zig. The following workflow governs how work proceeds.
 
 ### Continuous Integration Loop
 
 ```
-1. Review the evergreen end state spec
-2. Compare it to the current WIP implementation
-3. Identify gaps
-4. Ensure each gap is captured and all status documents are updated in git
-5. Brainstorm the optimal divide-and-conquer strategy to keep many subagents busy without stepping on each other's toes
-6. Ensure the current subagent tasklist properly reflects that strategy
-7. Assign tasks to subagents and direct them to update their task card once done
-8. Ensure everything is in git
-9. While not yet done, goto step 1
+1. Check .wishes/ for new product owner requests
+2. Review the evergreen end state spec
+3. Compare it to the current WIP implementation
+4. Identify gaps
+5. Ensure each gap is captured and all status documents are updated in git
+6. Brainstorm the optimal divide-and-conquer strategy to keep many subagents busy without stepping on each other's toes
+7. Ensure the current subagent tasklist properly reflects that strategy
+8. Assign tasks to subagents and direct them to update their task card once done
+9. Ensure everything is in git
+10. While not yet done, goto step 1
 ```
 
 ### Document Organization

research/zig-cr/101-proposal-universal-crsqlite-mt-js.md

@@ -25,6 +25,10 @@ See node multi-process proposal:
 
 - [`100-proposal-node-multiprocess-crsqlite-mesh.md`](./100-proposal-node-multiprocess-crsqlite-mesh.md)
 
+See global mesh target:
+
+- [`102-proposal-crsqlite-global-mesh.md`](./102-proposal-crsqlite-global-mesh.md)
+
 ---
 
 ## Proposal: `@libcrsql/crsqlite-mt` (universal JS package)