feat: wire BuildPulse to Appwrite-backed persistence

docs/DATA_SCHEMA.md

@@ -27,7 +27,7 @@ Current schema version:
 {
   "id": "project_buildpulse",
   "name": "BuildPulse",
-  "one_line_pitch": "A local-first planning cockpit for AI-assisted product building.",
+  "one_line_pitch": "A calm planning cockpit for AI-assisted product building.",
   "description": "BuildPulse helps capture features, park distracting ideas, log progress as Pulse events, and export clean context for AI coding agents.",
   "current_goal": "Ship v0.1 with Feature Plan, Parking Lot, Pulse Log, and Export.",
   "notes": "",
@@ -113,6 +113,7 @@ Allowed `risk_level` values:
 ## Pulse Event
 
 Pulse events are append-friendly and future-compatible with Agent Pulse.
+In v0.1, Pulse events are intentionally simple and human-readable.
 
 ```json
 {
@@ -124,7 +125,6 @@ Pulse events are append-friendly and future-compatible with Agent Pulse.
   "agent_id": "jimmi",
   "pulse_type": "INTENT",
   "message": "Start implementing the Feature Plan screen.",
-  "structured_payload": {},
   "confidence_score": 0.9,
   "evidence_refs": [],
   "trace_id": "session_001"
@@ -186,6 +186,19 @@ Later form may become:
 ]
 ```
 
+## Future Agent Pulse Fields
+
+The full Agent Pulse framework may later add:
+- `structured_payload`
+- `event_version`
+- `parent_event_id`
+- `agent_capability`
+- `tool_call_refs`
+- `artifact_refs`
+- `safety_classification`
+
+These are intentionally out of scope for v0.1.
+
 ## Settings
 
 Minimal v0.1 settings: