update(prompts): refine compress and nudge prompt wording

Author: Tarquinen

lib/prompts/compress-message.ts

@@ -8,6 +8,7 @@ When a selected message contains user intent, preserve that intent with extra ca
 Directly quote short user instructions when that best preserves exact meaning.
 
 Yet be LEAN. Strip away the noise: failed attempts that led nowhere, verbose tool output, and repetition. What remains should be pure signal - golden nuggets of detail that preserve full understanding with zero ambiguity.
+If a message contains no significant technical decisions, code changes, or user requirements, produce a minimal one-line summary rather than a detailed one.
 
 MESSAGE IDS
 You specify individual raw messages by ID using the injected IDs visible in the conversation:
@@ -17,27 +18,18 @@ You specify individual raw messages by ID using the injected IDs visible in the
 Each message has an ID inside XML metadata tags like \`<dcp-message-id priority="high">m0007</dcp-message-id>\`.
 The ID tag appears at the end of the message it belongs to — each ID covers all the content above it back to the previous ID.
 Treat these tags as message metadata only, not as content to summarize. Use only the inner \`mNNNN\` value as the \`messageId\`.
-The \`priority\` attribute indicates relative context cost. Prefer higher-priority closed messages before lower-priority ones.
+The \`priority\` attribute indicates relative context cost. When using the compress tool, if there are high-priority messages they MUST be compressed if all of their information is not vital to the task at hand.
+If there are previous messages with compress tool results, these MUST be compressed with a minimal summary.
 Messages marked as \`<dcp-message-id>BLOCKED</dcp-message-id>\` cannot be compressed.
 
 Rules:
 
 - Pick each \`messageId\` directly from injected IDs visible in context.
 - Only use raw message IDs of the form \`mNNNN\`.
 - Ignore XML attributes such as \`priority\` when copying the ID; use only the inner \`mNNNN\` value.
-- Do NOT use compressed block IDs like \`bN\`.
 - Do not invent IDs. Use only IDs that are present in context.
-- Do not target prior compressed blocks or block summaries.
 
 BATCHING
 Select MANY messages in a single tool call when they are independently safe to compress.
 Each entry should summarize exactly one message, and the tool can receive as many entries as needed in one batch.
-When several messages are equally safe to compress, prefer higher-priority messages first.
-
-Because each message is compressed independently:
-
-- Do not describe ranges
-- Do not use start/end boundaries
-- Do not use compressed block placeholders
-- Do not reference prior compressed blocks with \`(bN)\`
 `

lib/prompts/context-limit-nudge.ts

@@ -7,18 +7,12 @@ You MUST use the \`compress\` tool now. Do not continue normal exploration until
 
 If you are in the middle of a critical atomic operation, finish that atomic step first, then compress immediately.
 
-RANGE STRATEGY (MANDATORY)
-Prioritize one large, closed, high-yield compression range first.
-This overrides the normal preference for many small compressions.
-Only split into multiple compressions if one large range would reduce summary quality or make boundary selection unsafe.
-
-RANGE SELECTION
+SELECTION PROCESS
 Start from older, resolved history and capture as much stale context as safely possible in one pass.
-Avoid the newest active working slice unless it is clearly closed.
-Use visible injected boundary IDs for compression (\`mNNNN\` for messages, \`bN\` for compressed blocks), and ensure \`startId\` appears before \`endId\`.
+Avoid the newest active working messages unless it is clearly closed.
 
 SUMMARY REQUIREMENTS
-Your summary must cover all essential details from the selected range so work can continue without reopening raw messages.
+Your summary MUST cover all essential details from the selected messages so work can continue.
 If the compressed range includes user messages, preserve user intent exactly. Prefer direct quotes for short user messages to avoid semantic drift.
 </dcp-system-reminder>
 `

lib/prompts/iteration-nudge.ts

@@ -2,7 +2,5 @@ export const ITERATION_NUDGE = `<dcp-system-reminder>
 You've been iterating for a while after the last user message.
 
 If there is a closed portion that is unlikely to be referenced immediately (for example, finished research before implementation), use the compress tool on it now.
-
-Prefer multiple short, closed ranges over one large range when several independent slices are ready.
 </dcp-system-reminder>
 `

lib/prompts/system.ts

@@ -10,19 +10,6 @@ THE PHILOSOPHY OF COMPRESS
 
 Think of compression as phase transitions: raw exploration becomes refined understanding. The original context served its purpose; your summary now carries that understanding forward.
 
-OPERATING STANCE
-Prefer short, closed, summary-safe compressions.
-When multiple independent stale sections exist, prefer several focused compressions (in parallel when possible) over one broad compression.
-
-Use \`compress\` as steady housekeeping while you work.
-
-CADENCE, SIGNALS, AND LATENCY
-
-- No fixed threshold mandates compression
-- Prioritize closedness and independence over raw size
-- Prefer smaller, regular compressions over infrequent massive compressions for better latency and summary quality
-- When multiple independent stale sections are ready, batch compressions in parallel
-
 COMPRESS WHEN
 
 A section is genuinely closed and the raw conversation has served its purpose:

lib/prompts/turn-nudge.ts

@@ -1,10 +1,9 @@
 export const TURN_NUDGE = `<dcp-system-reminder>
 Evaluate the conversation for compressible ranges.
 
-If any range is cleanly closed and unlikely to be needed again, use the compress tool on it.
+If any messages are cleanly closed and unlikely to be needed again, use the compress tool on them.
 If direction has shifted, compress earlier ranges that are now less relevant.
 
-Prefer small, closed-range compressions over one broad compression.
 The goal is to filter noise and distill key information so context accumulation stays under control.
 Keep active context uncompressed.
 </dcp-system-reminder>