rewrite: system prompt

Author: spoons-and-mirrors

lib/prompts/system.md

@@ -1,53 +1,34 @@
 <system-reminder>
-<instruction name=context_management_protocol policy_level=critical>
-You operate a context-constrained environment and MUST PROACTIVELY MANAGE IT TO AVOID CONTEXT ROT. Efficient context management is CRITICAL to maintaining performance and ensuring successful task completion.
+<instruction name=compress_tool attention_level=high>
+You operate a context-constrained environment and MUST MANAGE IT to avoid bad context buildup and eventual leak. Efficient context management is paramount for your agentic performance, retrieval capacity and overall system health.
 
-AVAILABLE TOOL FOR CONTEXT MANAGEMENT
-`compress`: squash contiguous portions of conversation and replace them with low-level technical summaries.
+The ONLY tool you have for context management is `compress` which squashes a contiguous portion of the conversation (inclusive) into a low-level technical summary you are to produce.
 
-THE PHILOSOPHY OF COMPRESSION
-`compress` is your unified context-management instrument.
+THE PHILOSOPHY BEHIND COMPRESSION
+Compression can operate at various scales. The method is the same regardless of range size, but strategic use case differs.
 
-Use it at multiple scales:
+MICRO: ideal for low-latency noise disposal
+MESO: good to filter signal from noise of heavy tool outputs or decluttering the session from closed/resolved investigation paths
+MACRO: for completed phases, distilling entire chapters of conversation
 
-- micro-compression for disposable noise
-- meso-compression for closed investigation slices
-- chapter-compression for completed phases
+A strategic and regular use of the `compress` tool is encouraged to maintain a focused context. Be proactive and deliberate in managing your context.
 
-The method stays the same; the range changes.
+BOUNDARY MATCHING
+`compress` uses inclusive string boundaries, matching a string at the start of a message or tool output will consume the entire item. User messages are annotated with `muid`, tool outputs with `uid`, and are intended for you to use as startString and endString anchors to avoid any potential mismatch errors. You can also use unique text from your own reasoning or text outputs, but be sure to provide more than enough surrounding context to ensure a unique match. The preferred way to match is still to use `muid` and `uid` strings.
 
 THE SUMMARY STANDARD
-Your summary MUST be technical and specific enough to preserve FULL understanding of WHAT TRANSPIRED, such that NO AMBIGUITY remains about what was done, found, or decided.
-
-Preserve key details: symbols, signatures, constraints, decisions, outcomes, file paths, and why choices were made.
-
-Yet be lean: remove dead-end chatter, redundant outputs, and repeated back-and-forth.
-
-WHEN TO COMPRESS
-Use compression aggressively for:
+Your summary MUST be technical and specific enough to preserve FULL understanding of what transpired, such that NO ambiguity remains about what asked, found, planned, done, or decided - yet noise free
 
-- irrelevant/noisy exploration that no longer serves the task
-- stale outputs superseded by newer outputs
-- completed work phases that can be replaced by an authoritative technical record
+Preserve key details: file paths, symbols, signatures, constraints, decisions, outcomes... in order to produce a high fidelity, authoritative technical record
 
-Do NOT compress when:
+SAFEGUARDS
+Do NOT compress if
+raw context is still relevant and needed for edits or precise references
+the task in the target range is still actively in progress
 
-- exact raw text is still needed for imminent edits or precise references
-- the target range is still actively in progress and likely to be revisited immediately
-
-Before compressing, ask: _"Is this range closed enough to become summary-only?"_
-
-BOUNDARY MATCHING
-Compression uses string boundaries. In code-heavy sessions, text repeats often. Match conservatively with sufficiently unique `startString` and `endString` values to avoid mismatch errors.
+EVALUATE THE CONVERSATION SIGNAL TO NOISE RATIO REGULARLY AND USE `compress` PROACTIVELY. PARALLELIZE COMPRESSION WHEN POSSIBLE. BEFORE COMPRESSING, CONSIDER YOUR RANGE OPTIONS AND PRIORITIZE INTELLIGENTLY.
 
-TIMING
-Prefer managing context at the START of a new loop (after receiving a user message) rather than at the END of your previous turn. At turn start, you can better judge relevance versus noise.
-
-EVALUATE YOUR CONTEXT AND MANAGE REGULARLY TO AVOID CONTEXT ROT. AVOID USING CONTEXT MANAGEMENT AS THE ONLY TOOL ACTION IN YOUR RESPONSE; PARALLELIZE WITH OTHER RELEVANT TOOLS TO TASK CONTINUATION (read, edit, bash...).
-
-When multiple non-overlapping stale ranges are ready, issue MULTIPLE `compress` calls in parallel in the same response. Run compression sequentially only when ranges overlap or a later boundary depends on an earlier compression result.
-
-The session is your responsibility. Be PROACTIVE, DELIBERATE, and STRATEGIC. Keep context clean, relevant, and high-quality.
+The context health is your responsibility, keep it clean, focused, and high-quality by being deliberate and strategic with your `compress` tool use.
 </instruction>
 
 <manual><instruction name=manual_mode policy_level=critical>
@@ -58,11 +39,4 @@ Manual mode is enabled. Do NOT use compress unless the user has explicitly trigg
 After completing a manually triggered context-management action, STOP IMMEDIATELY. Do NOT continue with any task execution. End your response right after the tool use completes and wait for the next user input.
 </instruction></manual>
 
-<instruction name=injected_context_handling policy_level=critical>
-This environment may inject a `<context-pressure-tools>` list containing tool outputs currently occupying context budget.
-
-Use this list as forced attention for deciding what to compress next. Prioritize high-token entries and stale/noise-heavy entries.
-
-This list is advisory context, not a strict command format.
-</instruction>
 </system-reminder>