Krzysztof kuhy Rudnicki f8f81ecac0 Cap artifact growth instead of recommending a future prune ... The prune commit's evidence noted that "a recurring prune or a hard cap would be the durable fix if this recurs" - which is advice, not a fix. The tree would have regrown at one artifact per commit and been noticed months later, exactly as it was this time. check_repo_size.sh now caps evidence/ and contracts/ at 60 files each: the headroom the prune bought, against 21 today. main accumulates failures rather than returning on the first, so tripping both the source ceiling and the artifact cap reports both. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com> Claude-Session: https://claude.ai/code/session_01PJrqKERAo5QUeEHWS5Asgp		2026-08-23 19:33:53 +02:00
..
contracts	Prune 655 superpowers evidence and contract artifacts	2026-08-23 19:28:49 +02:00
evidence	Cap artifact growth instead of recommending a future prune	2026-08-23 19:33:53 +02:00
memory	style(prettier): apply markdown/json formatting updates	2026-05-07 22:08:00 +02:00
plans	feat(phone-focus): add recovery workflow, automation scripts, and docs	2026-05-01 19:07:27 +02:00
sessions	chore(agent): add governance checks and artifact workflow scaffolding	2026-05-07 22:03:43 +02:00
specs	Bring every markdown file under the cap	2026-08-16 19:25:59 +02:00
workflows	chore(agent): add governance checks and artifact workflow scaffolding	2026-05-07 22:03:43 +02:00