feat: wire BuildPulse to Appwrite-backed persistence

docs/SCOPE.md

@@ -94,16 +94,16 @@ Markdown exports:
 - PULSE_LOG.md
 - CLAUDE_CONTEXT.md
 
-### 6. Local Persistence
+### 6. Appwrite Persistence
 
-The app persists data locally.
-Acceptable v0.1 storage:
-- LocalStorage
-- IndexedDB
+The app stores its canonical state in Appwrite on the Unraid server.
+It may also keep a local cache for fast reloads and temporary offline/failure fallback.
+
+Required v0.1 behavior:
+- Appwrite-backed read/write persistence
+- Local cache fallback if the backend is temporarily unavailable
 - JSON file export/import
 
-No database required.
-
 ## Out of Scope for v0.1
 
 Do not implement:
@@ -119,7 +119,6 @@ Do not implement:
 - GitHub/Gitea integration
 - WebSockets
 - Backend authentication
-- Database
 - Multi-user collaboration
 - Notifications
 - Advanced analytics
@@ -143,7 +142,7 @@ BuildPulse v0.1 is done when:
 6. The user can manually add Pulse events.
 7. Pulse events can be linked to features.
 8. Pulse events display in chronological order.
-9. The app persists data locally after refresh.
+9. The app persists data through Appwrite after refresh, with local cache fallback if Appwrite is temporarily unavailable.
 10. The user can export JSON.
 11. The user can export Pulse events as JSONL.
 12. The user can export Markdown context.