oída 0.3.0 — the remote ear and directed listening

• The remote ear (/remote): phone records (PCM in the page, WAV on-device), attaches its GPS fix when granted, posts to POST /remote/listen; the server runs the full pipeline, keeps the WAV, writes the akousma — the sound + its listening file, with spec v1.2 location and capture — into the shared store, and returns the listening event to the remote UI. Served over the operator's private network (Tailscale); remote_ear_url reported by oida integrate remote.
• Future / past listening: past slices the ring buffer that was already listening when the trigger fired; future records the window after it. Direction pill (⟲/⟳) in the floating listener, default in Settings, native mic ring 30s→120s with real bufferedSeconds, on-phone ring buffer in the remote ear (overwrites itself — nothing accumulates), capture_direction/capture_seconds/capture_trigger on /listen-event.
• Geolocated listening: optional consent-scoped location on /listen-event, /gateway/listen, the germ handoff, and oida_listen (MCP) — plotted by the akousmata listening map at /library/.
• MCP: oida_live gains capture (the past direction made callable); oida_listen gains location.
• Contracts: components move to earworm/v0.3 + akousmata/v0.3; the gateway contract stays oida/gateway/v0.2 — everything is additive. 150 tests.