feat: wire BuildPulse to Appwrite-backed persistence

docs/DECISIONS.md

@@ -30,7 +30,8 @@ Reason:
 This allows future autonomous agents to emit the same event shape without a major data model rewrite.
 
 Consequences:
-- Pulse schema includes future-friendly fields such as `agent_id`, `trace_id`, `confidence_score`, `structured_payload`, and `evidence_refs`.
+- Pulse schema includes future-friendly fields such as `agent_id`, `trace_id`, `confidence_score`, and `evidence_refs`.
+- Richer Agent Pulse fields such as `structured_payload` are intentionally parked until later versions.
 - v0.1 UI may not use all fields deeply.
 
 ## Decision 003 — Single Project in v0.1
@@ -79,21 +80,21 @@ Consequences:
 - Session view may come later.
 - Trace IDs allow grouping session-related pulses later.
 
-## Decision 006 — Local-First Storage
+## Decision 006 — Appwrite Canonical Storage with Local Cache Fallback
 
 Date:
 2026-05-06
 
 Decision:
-BuildPulse v0.1 uses local-first storage.
+BuildPulse v0.1 stores canonical state in Appwrite on the Unraid server, with a local cache fallback in the browser.
 
 Reason:
-This keeps the first version simple, fast, private, and easy to run.
+This keeps the first version durable across sessions while still feeling fast and forgiving in the browser.
 
 Consequences:
-- No database.
-- No auth.
+- No custom auth.
 - Export/import is important to avoid lock-in.
+- The browser cache is a fallback, not the source of truth.
 
 ## Decision 007 — Export Is a Core Feature