recipe-maintainers/cc-ci-orchestrator
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

memory: move agent memory into repo (memory/), note in AGENTS.md

Browse Source 
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.
This commit is contained in:
autonomic-bot
2026-06-09 19:25:20 +00:00
parent 330378d30d
commit 542ed0afe3
11 changed files with 194 additions and 0 deletions
Download Patch File Download Diff File Expand all files Collapse all files
memory/regression-canary-cadence.md
+14
View File
@@ -0,0 +1,14 @@
---
name: regression-canary-cadence
description: "The cc-ci server regression canaries are expensive — run on polish/review/release, not every commit"
metadata:
node_type: memory
type: feedback
originSessionId: 7b5366a6-263c-421b-be7d-9f888067336b
---
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.