forked from jason/echo
jason
f2bfd70dd4
The final phase of CHORUS-PLAN.md. Code- and doc-complete for group use; rc pends live deployment at chorusapi.mpm.to. - Repo README rewritten for CHORUS: group model (schema 5), concurrency posture, configuration, baked-build onboarding, layout, testing, 2.0 version history (ECHO history referenced at the fork tag). - Operator→member voice sweep across SKILL.md (incl. the trigger description, now group-aware), all references, 8 command docs, plugin README; member preferences / semantic layer / triage guidance describe the group model. - docs/ONBOARDING.md: member runbook — vault stand-up, per-member config, bake, deliver, self-onboarding first load, norms, offboarding. - docs/USAGE.md rewritten as the member usage guide. - New icon: chorus-icon.svg + 1024/512/64 PNGs (three voices, one center). - Removed ECHO-era assets (icons, spec PDF, perf briefs); ECHO planning docs retired to docs/history/. All preserved at echo-fork-point. - eval/README documents test_multimember.py. Manifest -> 2.0.0-rc.1; rebuilt chorus-memory.plugin. Verified: routing-sync, 25/25 unit, scaffold, 5 mock e2e suites, run_eval metrics green. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1.2 KiB
1.2 KiB
description, allowed-tools
| description | allowed-tools |
|---|---|
| Run the CHORUS vault-health linter and summarize any invariant violations | Bash(python3 *vault_lint.py*), Bash(python *vault_lint.py*), Bash(ls /sessions/*), Bash(dirname *) |
Run the bundled, read-only vault linter and report findings. Pass the conversation's current date (CHORUS_TODAY) so stale/aging math uses the same clock the agent writes with:
SDIR="${CLAUDE_PLUGIN_ROOT}/skills/chorus-memory/scripts"
[ -d "$SDIR" ] || SDIR=$(dirname "$(ls /sessions/*/mnt/.remote-plugins/*/skills/chorus-memory/scripts/vault_lint.py 2>/dev/null | head -1)") # CoWork sandbox fallback
CHORUS_TODAY=<currentDate> python3 "$SDIR/vault_lint.py"
# Windows: use `python` or `py -3` if `python3` is not on PATH.
Exit codes: 0 clean · 1 violations (printed, grouped by check) · 2 vault unreachable · 3 vault not bootstrapped (run bootstrap.py).
Summarize the violations grouped by category and propose fixes, but do not auto-fix without the member's go-ahead. If this is the first substantive session of a calendar month, offer to write the findings to _agent/health/YYYY-MM-vault-health.md (per the skill's Vault Health section).