@leing2021/super-pi 0.23.8 → 0.23.9

package/README.md

@@ -118,6 +118,7 @@ Super Pi is not a fork or wrapper. It extracts useful methods from the projects
 |---------|------------------------|
 | [addyosmani/agent-skills](https://github.com/addyosmani/agent-skills) | "Use when" skill trigger conditions, source-driven verification, stop-the-line hard gate, anti-rationalization, and the five-axis review baseline. Adopted as embedded micro-patterns only — no new skills, tools, commands, or agents. |
 | [everything-claude-code](https://github.com/affaan-m/everything-claude-code) | Parallel subagent orchestration, checkpoint resume, continuous learning loops, and token-conscious agent workflow design. |
+| [humanlayer/12-factor-agents](https://github.com/humanlayer/12-factor-agents) | Context window ownership, compacting resolved errors, retry caps, and pre-fetching obvious prerequisites. Adopted as lightweight context hygiene rules inside the existing Phase 1 pipeline. |
 | [superpowers](https://github.com/obra/superpowers) | Strict TDD gates, design checklists, review discipline, and the idea that agents need hard gates instead of gentle suggestions. |
 | [compound-engineering-plugin](https://github.com/EveryInc/compound-engineering-plugin) | The five-step think → plan → build → review → learn loop and the knowledge-compounding backbone. |
 | [gstack](https://github.com/garrytan/gstack) | YC-style forcing questions, CEO Review cognitive frameworks, browser QA patterns, failure maps, and evidence-first validation. |

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@leing2021/super-pi",
-  "version": "0.23.8",
+  "version": "0.23.9",
   "private": false,
   "type": "module",
   "description": "Pi-native Compound Engineering package for iterative development workflows",

package/skills/03-work/SKILL.md

@@ -58,6 +58,17 @@ Anti-rationalization — when a gate fails or evidence is missing:
 
 This is a hard gate — do not push past a failing test or broken build to continue implementation. Errors compound.
 
+## Error compaction after recovery
+
+After a stop-the-line failure is diagnosed, fixed, and verified:
+
+1. Replace full traces in handoff/context with `ERROR(resolved): <root cause>`
+2. Keep only the final repro, root cause, fix summary, and verification result
+3. Remove intermediate debug output and failed exploratory runs that are no longer relevant
+4. Update `session_checkpoint` with the compacted state only
+
+If the same tool, command, or implementation unit fails 3 consecutive times, stop retrying and ask the user for direction with a concise evidence summary.
+
 ## Workflow
 
 1. **Load context**: consume latest handoff before any broad file reads — `context_handoff load` or read `.context/compound-engineering/handoffs/latest.md`. If found, use `activeFiles`, `blocker`, `verification`, `activeRules` as starting point. If not found, proceed normally.

package/skills/references/pipeline-config.md

@@ -29,6 +29,15 @@ Before reading any project files or running repository-wide scans, load the most
 
 Core principle: **consume handoff before broad project file reads** — a single handoff read (~500 tokens) avoids 5-10 project file scans (~5K-10K tokens).
 
+## Context hygiene rules
+
+Applies to all Phase 1 skills when preparing context or saving handoff.
+
+1. **Compact resolved errors** — Once an error is diagnosed, fixed, and verified, do not carry the full trace forward. Replace it with `ERROR(resolved): <root cause>` and keep repro/verification only if still relevant.
+2. **Fetch obvious prerequisites** — If the next step has an obvious deterministic prerequisite, fetch it before reasoning further instead of spending an LLM round trip asking for it.
+3. **Cap repeated failures** — After 3 consecutive failures on the same tool, command, or implementation unit, stop retrying. Summarize evidence and ask the user for direction.
+4. **Prune before handoff** — Before saving handoff, keep only what the next stage needs. Move broad history to artifact paths; remove intermediate debug output that is no longer relevant.
+
 ## End of skill: save handoff + status + context
 
 Every Phase 1 skill (02-plan through 05-learn) must save context handoff at completion: