context-mode 1.0.131 → 1.0.133

package/skills/context-mode/SKILL.md

@@ -283,6 +283,7 @@ Subagents automatically receive context-mode tool routing via a PreToolUse hook.
 - Using `cat large-file.json` via Bash → entire file in context. Use `ctx_execute_file` instead.
 - Using `gh pr list` via Bash → raw JSON in context. Use `ctx_execute` with `--jq` filter instead.
 - Piping Bash output through `| head -20` → you lose the rest. Use `ctx_execute` to analyze ALL data and print summary.
+- Narrowing `ctx_execute` output upstream of capture → `ctx_execute` captures, `ctx_search` filters; merging the layers drops data that the index never sees. See `references/anti-patterns.md` §8.
 - Running `npm test` via Bash → full test output in context. Use `ctx_execute` to capture and summarize.
 - Calling `browser_snapshot()` WITHOUT `filename` parameter → 135K tokens flood context. **Always** use `browser_snapshot(filename: "/tmp/snap.md")`.
 - Calling `browser_console_messages()` or `browser_network_requests()` WITHOUT `filename` → entire output floods context. **Always** use the `filename` parameter.

package/skills/context-mode/references/anti-patterns.md

@@ -244,6 +244,32 @@ GOOD — specific and actionable:
 
 ---
 
+## 8. `ctx_execute` Captures, `ctx_search` Filters — Don't Merge the Layers
+
+`ctx_execute` and `ctx_search` are two layers, not one. `ctx_execute` exists to **capture** full output into the index. `ctx_search` exists to **filter** what was captured. When you narrow the output *inside* `ctx_execute` — at the shell layer, in script logic, anywhere upstream of capture — the dropped lines never reach the index. `ctx_search` cannot recover what was never written. You've spent the capture budget and lost the data you'd want to query later, for no context-window benefit: large stdout is already auto-indexed, not returned inline.
+
+The mental model:
+
+```
+┌──────────────────────┐      ┌──────────────────────┐
+│   ctx_execute        │ ───▶ │   ctx_search         │
+│   (capture layer)    │      │   (filter layer)     │
+│                      │      │                      │
+│   produces full      │      │   queries the        │
+│   output into index  │      │   captured index     │
+└──────────────────────┘      └──────────────────────┘
+        ▲                              ▲
+        │                              │
+   Job: capture                   Job: narrow
+   Do NOT narrow here.            Do all narrowing here.
+```
+
+**Rule:** Treat `ctx_execute`'s output as write-once to the index. Run the command in full and let it index. Do every narrowing step downstream, via `ctx_search`. If you find yourself trimming inside `ctx_execute`, you are doing the filter layer's job in the capture layer — stop and move the narrowing to a `ctx_search` call.
+
+**Why the layer separation matters:** the index is what survives across calls and across sessions. Anything you discard before the index is gone permanently from this session's queryable surface. Anything you keep is queryable, repeatedly, with different questions, at zero re-execution cost.
+
+---
+
 ## Summary Checklist
 
 Before using `execute`, verify: