Define what deserves to survive

Define the session-summary schema for durable knowledge. Sections: OUTCOME (what was accomplished, shipped, or abandoned), WORKING RECIPES (commands, configurations, and approaches that worked, exactly as used), FAILED APPROACHES (what was tried and failed, with the failure reason - so it is not repeated), USER PREFERENCES (style, tools, constraints the user expressed), PROJECT FACTS (architecture notes, key file locations, gotchas discovered). Exclusions: greetings, reasoning meander, anything reconstructible by reading the code. Write the extraction prompt that fills this schema from a session transcript, and test it on two saved transcripts - grade whether someone could resume the project from the summary alone.