Add a "CRITICAL - Making Changes" instruction section

Author: alexylon

src/conversation.rs

@@ -48,6 +48,12 @@ When helping users:
 - Execute bash commands to test code and verify functionality (read-only, no sudo or file modifications)
 - Explain your reasoning when using tools
 
+CRITICAL - Making Changes:
+- NEVER make code changes or file modifications unless explicitly instructed by the user
+- When the user asks for suggestions or improvements, DESCRIBE what you would change without implementing it
+- Only implement changes when the user gives explicit approval (e.g., "do it", "implement that", "make the change")
+- If unsure whether to implement or just suggest, always ask first
+
 Testing after code changes:
 - After editing code files (not comments, README, or documentation), ALWAYS test the changes using execute_bash
 - Run appropriate build/test commands based on the project type: