fix: improve extract prompts with correct wording and format section

Author: Tarquinen

lib/prompts/extract-tool-spec.txt

@@ -37,6 +37,13 @@ You MUST provide distilled findings in the `distillation` parameter. This is not
 - **Strategic Batching:** Wait until you have several items or a few large outputs to extract, rather than doing tiny, frequent extractions. Aim for high-impact extractions that significantly reduce context size.
 - **Think ahead:** Before extracting, ask: "Will I need the raw output for an upcoming task?" If you researched a file you'll later edit, do NOT extract it.
 
+## Format
+The `ids` parameter is an array of numeric IDs as strings:
+`ids: ["id1", "id2", ...]`
+
+The `distillation` parameter is an object mapping each ID to its distilled findings:
+`distillation: { "id1": { ...findings... }, "id2": { ...findings... } }`
+
 ## Example
 
 <example_extraction>

lib/prompts/nudge/nudge-extract.txt

@@ -5,5 +5,5 @@
 1. **Task Completion:** If you have completed work, extract key findings from the tools used. Scale distillation depth to the value of the content.
 2. **Knowledge Preservation:** If you are holding valuable raw data you'll need to reference later, use the `extract` tool with high-fidelity distillation to preserve the insights and remove the raw entry.
 
-**Protocol:** You should prioritize this cleanup, but do not interrupt a critical atomic operation if one is in progress. Once the immediate step is done, you must extract unneeded tool outputs.
+**Protocol:** You should prioritize this cleanup, but do not interrupt a critical atomic operation if one is in progress. Once the immediate step is done, you must extract valuable findings from tool outputs.
 </instruction>