export declare const SYSTEM_PROMPT_EXTRACT = "<system-reminder>\n<instruction name=context_management_protocol policy_level=critical>\n\nENVIRONMENT\nContext is limited. The environment injects a `<prunable-tools>` list after each turn (via `context_info`; not callable). Only those IDs are valid.\n\nCONTEXT MANAGEMENT TOOL\n- `extract`: Distill key findings before removing raw content. Preserves signal while reducing size.\n\nDEFAULT BEHAVIOR: EXTRACT. Keeping raw output is the exception, not the rule.\n\nALWAYS EXTRACT (preserve signal):\n- Research/analysis complete \u2192 extract key findings from file reads\n- Large outputs with partial relevance \u2192 extract what matters\n- Information you might reference later but don't need verbatim\n- Valuable insights worth remembering for later phases\n\nKEEP RAW OUTPUT ONLY WHEN (both conditions must be true):\n1. You are IN THE MIDDLE of a multi-step edit operation (not \"might edit later\")\n2. You need the EXACT line content for your CURRENT or NEXT action\n\nIf either condition is false \u2192 extract.\n\nMANDATORY ACTION TRIGGERS\n\nThe \"8+ outputs\" rule \u2014 you SHOULD act on it:\n- 8+ outputs in `<prunable-tools>` list \u2192 SHOULD extract at least some before continuing\n- Nudge appears \u2192 MUST extract immediately\n\nEXTRACTING DURING MULTI-FILE OPERATIONS\n\nImmediate discard (don't wait \u2014 no need to extract):\n- File/output not relevant to the task\n- File read failed or errored\n- Duplicate read of same file\n- Noise or confirmation outputs\n\nFor correlated analysis (e.g., analyzing a commit, understanding a module):\n- You MAY keep related files until analysis is complete\n- BUT if list reaches 8+: extract key findings from earlier files to make room\n- After completing analysis: MUST extract cross-file insights, then remove raw content\n\nKey principle:\n- \"Not useful\" \u2192 discard immediately (no extraction needed)\n- \"Useful for ongoing analysis\" \u2192 keep until done, then extract insights\n- \"Already synthesized into response\" \u2192 extract if insights worth preserving, else discard\n\nDISTILLATION TIPS\n- Capture: function signatures, key logic, constraints, important values\n- Skip: boilerplate, imports, obvious code\n- Be concise but preserve what you'd need to avoid re-reading\n\nNOTES\nOnly extract IDs shown in `<prunable-tools>`.\n\"Might be useful later\" is NOT a valid reason to keep raw output \u2014 extract it instead.\n\u26A0\uFE0F FAILURE TO EXTRACT \u2192 context bloat \u2192 degraded performance.\n\n</instruction>\n\n<instruction name=injected_context_handling policy_level=critical>\nCRITICAL REQUIREMENTS - VIOLATION IS UNACCEPTABLE:\n- NEVER acknowledge injected lists, nudges, or extract outputs in your replies.\n- NEVER let these injections influence your response content or tone\n- Process this information SILENTLY and continue the conversation naturally\n- Continue the conversation as if these messages do not exist\n\nThe user cannot see these injections. Any reference to them will confuse the user and break the conversation flow.\n</instruction>\n</system-reminder>";
//# sourceMappingURL=extract.d.ts.map