Files

Scott Idem 4711f41c34 Expanded Recovery Meeting sort options and refined development SOP.

Implemented 'Meeting Name (A-Z)' and 'Meeting Name (Z-A)' sorting for Recovery Meetings, including UI dropdown updates and client-side re-sorting logic.

Updated documentation/GUIDE__DEVELOPMENT.md to v1.1 with clarified verification steps and inter-agent coordination protocols.

Minor label cleanup in Journal editor.

2026-02-16 15:58:17 -05:00

2.1 KiB

Raw Blame History

Aether Development SOP (Frontend)

Version: 1.1 (2026-02-16) 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

Svelte Integrity: npx svelte-check
Type Safety: Ensure interfaces in src/lib/types/ae_types.ts match backend schemas.
Reactivity Check: Verify Svelte 5 runes ($state, $derived) are not creating race conditions with Dexie liveQuery.
Build Check: For major changes, run npm run build:staging 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: IGNORE THIS FOR NOW: ~~Update your shared Journal in ~/agents_sync/aether/journals/ after significant milestones.~~
**Stuck in Loop or Insufficient Information: ** If you find yourself in a loop or lacking information, ask Scott and or use the message tool to ask for clarification or assistance from the Backend Agent.

Tool: Use the message tool to communicate with the Backend Agent or Scott's other agents.

🧠 Continuity

Before starting work:

Read ~/agents_sync/README.md to understand the fleet status and cross-agent tasks.
Check README.md in the project root for technical specs.
Review your local documentation/AGENT_TODO.md for active tasks.
Be sure to describe the plan before you start making code changes to one or more files.

2.1 KiB Raw Blame History