542ed0afe3
Persistent agent memories now live in memory/ in this repo; the Claude auto-memory path is symlinked here so future memories land in the repo and get committed like any other change.
1.1 KiB
name, description, metadata
| name | description | metadata | ||||||
|---|---|---|---|---|---|---|---|---|
| regression-canary-cadence | The cc-ci server regression canaries are expensive — run on polish/review/release, not every commit |
|
The cc-ci server regression canaries (the codified E2E pytest suite — full lifecycle on custom-html-tiny + lasuite-docs good canaries plus a known-bad false-green-guard fixture; plan: cc-ci-plan/plan-server-regression-canaries.md) must NOT run on every commit/PR.
Why: they're slow and resource-heavy — full lifecycle on lasuite-docs is minutes and needs the live server/abra/Swarm. Running them per-commit would be wasteful and slow the loop.
How to apply: run them deliberately at milestones — polishing passes, code reviews, and releases of the cc-ci server — before trusting a batch of changes, not per incremental commit. Keep them opt-in behind the @pytest.mark.canary marker; if ever wired to !testme on the cc-ci repo, gate behind a deliberate trigger (label / --canary), never an automatic run on every PR.