jason
2ddf199850
- 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>
1.7 KiB
description
| description |
|---|
| Load CHORUS memory — cold-start context read (profile, scope, latest session, today, inbox) |
Use the chorus-memory skill to load memory now. Run the cold-start Loading procedure from SKILL.md: the eight orientation reads (marker, group profile, your preferences/context/heartbeat, today's shared daily note, your inbox, the group inbox) in one call, then do the load-time reconcile (inbox-depth + scope-drift) and surface it in a single line.
CHORUS="${CLAUDE_PLUGIN_ROOT}/skills/chorus-memory/scripts/chorus.py"
[ -f "$CHORUS" ] || CHORUS=$(ls /sessions/*/mnt/.remote-plugins/*/skills/chorus-memory/scripts/chorus.py 2>/dev/null | head -1) # CoWork sandbox fallback
python3 "$CHORUS" load
# add --all-members for a group-wide view (every member's scope + last session)
# Windows: use `python` or `py -3` if `python3` is not on PATH.
load prints all eight sections (and self-onboards your member namespace on a first visit) (404s on today's note / inbox are shown as absent, not errors) and flags an un-bootstrapped vault. Follow up with chorus.py scope show if you need the sessions-since-switch count, and a project search if a specific project is in play.
If load prints NOT CONFIGURED (exit 78), this machine has no usable key file yet. Don't proceed with memory — follow First run in SKILL.md: tell the operator CHORUS isn't configured, ask for their chorus-memory config file (group/member/endpoint/key), install it with chorus.py config import <path> (or config set), then re-run load.
Do not narrate the reads. End with a one-line orientation: who/what/where the active scope is, and any reconcile prompt.