fix(bot): productivity and backlog optimizations (#26236)

tools/gemini-cli-bot/brain/critique.md

@@ -92,7 +92,12 @@ above:
     logic and the goals of the prior investigation. Do not invent new workflows;
     just ensure the existing ones are implemented robustly according to this
     checklist.
-4.  Re-stage the file with `git add`. **CRITICAL: You MUST use `git add` to
+4.  **Strict Scope Constraint**: You are STRICTLY FORBIDDEN from modifying or
+    staging any file that was not already staged by the investigation phase. You
+    must ONLY critique and fix the files explicitly included in
+    `git diff --staged`. Do not attempt to complete pending tasks from the
+    memory ledger or introduce unrelated refactoring to unstaged files.
+5.  Re-stage the file with `git add`. **CRITICAL: You MUST use `git add` to
     stage your fixes.**
 
 ## Final Verdict & Logging

tools/gemini-cli-bot/brain/interactive.md

@@ -24,7 +24,11 @@ Before beginning your analysis, you MUST perform the following research:
 
 1.  **Read Memory**: Read `tools/gemini-cli-bot/lessons-learned.md` to
     understand the current state.
-2.  **Verify Request Context**: Use the GitHub CLI to verify the current state
+2.  **Ignore Pending Tasks**: You are in interactive mode. You MUST explicitly
+    ignore any FAILED, STUCK, or pending tasks listed in the
+    `lessons-learned.md` Task Ledger. Do not attempt to complete or resume them.
+    Your ONLY goal is to address the user's specific comment.
+3.  **Verify Request Context**: Use the GitHub CLI to verify the current state
     of the issue/PR you were mentioned in. If the user's request is already
     addressed or obsolete, inform them via `issue-comment.md`.
 
@@ -46,6 +50,10 @@ If your investigation confirms that a code or configuration change is required:
 
 - **Surgical Changes**: Apply the minimal set of changes needed to address the
   issue correctly and safely.
+- **Strict Scope**: You MUST strictly limit your changes to addressing the
+  user's specific request. You are STRICTLY FORBIDDEN from including any
+  unrelated updates (such as metrics updates, backlog triage changes, or
+  background housekeeping) when operating in interactive mode.
 - **Acknowledgment**: Write a brief acknowledgement to `issue-comment.md` (e.g.,
   "I've investigated the request and implemented a fix. A PR will be created
   shortly.").