chorus

Files

T

jason 2ddf199850 Phase 4: shared-write hardening + group lenses

- vault_lock gains bounded retry/backoff (CHORUS_LOCK_RETRIES=4,
  CHORUS_LOCK_BACKOFF=0.5s); atomic_index_update and recall-index upkeep
  retry acquisition — unlocked fallback only after exhausted retries,
  loudly, so an already-written note is never stranded unindexed.
- Duplicate-gate candidates carry the existing note's author; STOP
  message says whose entity the capture collided with.
- recall --author <member> filters hits + linked context to one member's
  notes; recall briefs and --json surface the author: stamp.
- load --all-members appends a group-wide view (every member's scope +
  last-session heartbeat); roster parsing accepts folders as
  trailing-slash file entries (the REST API's actual shape).
- operating-contract.md concurrency section rewritten for N members.
- Two-member e2e suite committed as eval/test_multimember.py (26 checks
  incl. all four Phase-4 behaviors).
- Manifest -> 2.0.0-alpha.4; rebuilt chorus-memory.plugin.

Verified: 25/25 unit, scaffold, routing-sync, 5 mock e2e suites (incl.
new multimember), run_eval metrics unchanged.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>

2026-07-21 15:29:55 -05:00

chorus-doctor.md

Phase 1: mechanical echo→chorus rename with back-compat shims

2026-07-21 13:35:51 -05:00

chorus-health.md

Phase 1: mechanical echo→chorus rename with back-compat shims

2026-07-21 13:35:51 -05:00

chorus-load.md

Phase 4: shared-write hardening + group lenses

2026-07-21 15:29:55 -05:00

chorus-recall.md

Phase 4: shared-write hardening + group lenses