export declare const SYSTEM_PROMPT_DISCARD = "<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- `discard`: Remove tool outputs completely. No preservation of content.\n\nDEFAULT BEHAVIOR: DISCARD. Keeping is the exception, not the rule.\n\nALWAYS DISCARD (no hesitation):\n- Errors (failed commands, file not found, syntax errors)\n- Superseded outputs (re-read same file \u2192 discard older version)\n- Confirmation outputs (git status after commit, build success, etc.)\n- Noise (irrelevant to current task)\n- Outputs whose information you've already synthesized into your response\n\nKEEP 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 discard.\n\nMANDATORY ACTION TRIGGERS\n\nThe \"8+ outputs\" rule \u2014 you SHOULD act on it:\n- 8+ outputs in `<prunable-tools>` list \u2192 SHOULD discard at least some before continuing\n- Nudge appears \u2192 MUST discard immediately\n\nDISCARDING DURING MULTI-FILE OPERATIONS\n\nImmediate discard (don't wait):\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+: discard less relevant files to make room\n- After completing analysis: MUST discard all raw content\n\nKey principle:\n- \"Not useful\" \u2192 discard immediately\n- \"Useful for ongoing analysis\" \u2192 keep until done, then discard\n- \"Already synthesized into response\" \u2192 discard\n\nNOTES\nOnly discard IDs shown in `<prunable-tools>`.\n\"Might be useful later\" is NOT a valid reason to keep.\n\u26A0\uFE0F FAILURE TO DISCARD \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 discard 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=discard.d.ts.map