Keep the Handoff Outside the Summary

After a long debugging session, the next turn remembers the proposed fix but loses the failing input. That is enough to make a plausible continuation go wrong.

/compact focus on the API changes can guide a summary. Guidance does not guarantee that every decision, file or test result survives. Treat compaction as a lossy handoff.

Before the handoff, save the current requirement, changed paths, exact failing case, commands already run and unresolved decisions in the project record. On resumption, compare that record with Git status and the actual files. Re-run the checks whose results depend on changes made since they last ran.

The context-management guidance offers controls for what stays in the conversation. The durable record gives you something to verify when the summary is incomplete.