context-mode 1.0.66 → 1.0.67

package/openclaw.plugin.json

@@ -3,7 +3,7 @@
   "name": "Context Mode",
   "kind": "tool",
   "description": "OpenClaw plugin that saves 98% of your context window. Sandboxed code execution in 11 languages, FTS5 knowledge base with BM25 ranking, and intent-driven search.",
-  "version": "1.0.66",
+  "version": "1.0.67",
   "sandbox": {
     "mode": "permissive",
     "filesystem_access": "full",

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "context-mode",
-  "version": "1.0.66",
+  "version": "1.0.67",
   "type": "module",
   "description": "MCP plugin that saves 98% of your context window. Works with Claude Code, Gemini CLI, VS Code Copilot, OpenCode, and Codex CLI. Sandboxed code execution, FTS5 knowledge base, and intent-driven search.",
   "author": "Mert Koseoğlu",

package/skills/context-mode-ops/SKILL.md

@@ -44,6 +44,24 @@ One untested change breaks everything. TDD is not optional, it is the gate.
 4. **Architects**: REJECT any change without tests. No exceptions, no "trivial change" excuse.
 5. **QA Engineer**: Run full suite after EVERY change. Report failures immediately.
 
+## Grill-Me Review: BLOCKING GATE
+
+<grill_me_enforcement>
+STOP. Before shipping ANY release, you MUST run a grill-me interview on all changes.
+No exceptions. No "this is a small patch." No "we already tested it."
+Every release gets grilled. If the grill reveals an unresolved question, the release is BLOCKED.
+</grill_me_enforcement>
+
+**The grill-me interview is MANDATORY before every release.** Summary:
+
+1. Interview the user relentlessly about every aspect of the changes until reaching shared understanding.
+2. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one.
+3. For each question, provide your recommended answer.
+4. Ask questions one at a time.
+5. If a question can be answered by exploring the codebase, explore the codebase instead of asking.
+6. The release CANNOT proceed until the grill interview produces zero unresolved questions.
+7. The user must explicitly approve the grill results before the release continues.
+
 ## You Are the Engineering Manager
 
 <delegation_enforcement>

package/skills/context-mode-ops/release.md

@@ -34,6 +34,21 @@ Spawn these agents simultaneously:
 
 All must report PASS before proceeding.
 
+### 1b. Grill-Me Review — MANDATORY BLOCKING GATE
+
+**Before ANY version bump, the EM MUST run a grill-me interview on all changes in this release.**
+
+This is not optional. This is not skippable. Every release gets grilled.
+
+Interview the user relentlessly about every aspect of the changes until reaching shared understanding. Walk down each branch of the design tree, resolving dependencies between decisions one-by-one. For each question, provide your recommended answer. Ask questions one at a time. If a question can be answered by exploring the codebase, explore the codebase instead of asking.
+
+**The release is BLOCKED until:**
+- [ ] All branches of the design tree are resolved
+- [ ] Zero unresolved questions remain
+- [ ] User explicitly approves the grill results
+
+Only after grill-me approval: proceed to version bump.
+
 ### 2. Version Bump — MANDATORY
 
 <version_bump_enforcement>