Algophony v0.4.0 — spec v1.2: located, directed listening

Algophony v0.4.0 — Spec v1.2: located, directed listening

2026-07-11. Integration release; the frozen corpus is untouched.

Akousma spec v1.2 (Earworm v0.3)

The shared store's records may now carry two optional consent-scoped blocks,
and the record is open at the top level (unknown fields are preserved by
stores, never rejected):

• location — where the sound was heard: lat/lon, accuracy_m,
  altitude_m, human label, source (gps/network/manual/config/inferred),
  captured_at. The akousmata navigator plots these on its new listening
  map and strips them from every open-research export.
• capture — how the listening was triggered: direction (past =
  the ring-buffer seconds before the trigger; future = the window recorded
  after it; live = open-ended), window seconds, trigger surface,
  armed_at, triggered_at. Oída's floating listener and new remote ear
  write it on every capture.

workers/akousmata_source.py carries both blocks through
akousma_to_prompt_record(...) — as location, capture, and the
convenience capture_direction — so evaluation and organization runs can
group by place or temporal direction. A record without akousma_id now
raises a clear KeyError instead of an anonymous one.

CI

The worker unit tests (provider contracts, Oída gateway contract, the
AKOÚŌ drift guards, and the akousmata batch surface) now run in CI. The
cross-repo drift assertions self-skip where the sibling checkouts are
absent and run fully in local development.

Compatibility

• The Oída gateway contract pin stays oida/gateway/v0.2; every gateway
  addition in Oída 0.3.0 is optional and additive.
• The AKOÚŌ contract pin stays akouo/v0.6.
• Records without location/capture (spec v1.0/v1.1) read exactly as
  before.