Updating the documentation for things. Hopefully improvements to Gemini CLI.

documentation/GUIDE__DEVELOPMENT.md

@@ -0,0 +1,33 @@
+# Aether Development SOP (Frontend)
+> **Version:** 1.0 (2026-02-11)
+> **Location:** documentation/GUIDE__DEVELOPMENT.md
+
+## 1. 🛡️ Verification (The "Test-First" Mandate)
+**Rule:** No code is to be committed unless it has passed local verification. Skipping this is a violation of the Aether Dev Protocol.
+
+### Required Checks:
+1. **Svelte Integrity:** `npx svelte-check`
+2. **Type Safety:** Ensure interfaces in `src/lib/types/ae_types.ts` match backend schemas.
+3. **Reactivity Check:** Verify Svelte 5 runes (`$state`, `$derived`) are not creating race conditions with Dexie `liveQuery`.
+4. **Build Check:** For major changes, run `npm run build` to ensure no SSR or build-time failures.
+
+## 2. 📝 Commit & Sync Policy
+- **Atomic Commits:** One component or one logic fix per commit. Do not batch unrelated changes.
+- **Verification Log:** Mention the verification steps taken in your work log (`ae_log_work`).
+- **Safety:** Use `~/tmp/gemini_trash` for removals; never use `rm` directly on source files.
+
+## 3. 🤝 The Handshake (Coordination)
+You are not working in a vacuum. You MUST coordinate with the Backend Agent.
+
+### Mandatory Messaging Triggers:
+- **Data Requirements:** When a UI feature requires a new field or endpoint.
+- **API Failures:** When a V3 endpoint returns unexpected data or 500s.
+- **Status:** Update your shared Journal in `~/agents_sync/aether/journals/` after significant milestones.
+
+**Tool:** Use the `message` tool to communicate with the Backend Agent.
+
+## 🧠 Continuity
+Before starting work:
+1. Read `~/agents_sync/README.md` to understand the fleet status and cross-agent tasks.
+2. Check `README.md` in the project root for technical specs.
+3. Review your local `documentation/AGENT_TODO.md` for active tasks.