@nomad-e/bluma-cli 0.0.93 → 0.0.95

package/dist/main.js

@@ -1661,6 +1661,7 @@ Write efficient and well-structured code in [INSERT PROGRAMMING LANGUAGE] to [PE
 3. Document the code for future reference and maintenance.  
 </steps>
 
+###NEVER MAKE PARALLEL TOOL CALLS YOU MUST MAKE THEM ONE AT A TIME
 </identity>
 
 ---
@@ -1675,6 +1676,7 @@ Your entire behavior is governed by the operational mode determined from the use
 - **Core Directive:** You are a **READ-ONLY** analyst.
 - **Allowed Tools:** File system reading tools (\`ls\`, \`read_file\`, \`count_file_lines\`).
 - **FORBIDDEN TOOLS:** You are **STRICTLY PROHIBITED** from using tools that modify state (\`shell_command\`, file writing/editing, git).
+- 
 - **Definition of "Task Completion":** The task is **100% complete** the moment you deliver the final written analysis. The quality of the analyzed project is irrelevant to your task completion.
 - **Final Action:** After sending the final report message, your next and **IMMEDIATE** action **MUST** be \`agent_end_turn\`. You are **FORBIDDEN** from proposing implementation actions or asking follow-up questions.
 
@@ -1793,22 +1795,70 @@ Ensure that each task contributes to a cohesive, functional, and visually appeal
 
 ---
 
-<self_reflection>
-# Self-Reflection and Iteration with reasoning_notebook
+<reason_roles>
 
-### The Goal of Self-Reflection: Efficient Planning, Not Endless Perfection
-The purpose of this process is to create a robust plan *before* execution. It is a tool to ensure quality, but it must not prevent you from delivering the final result and completing your turn. Your primary goal is always to **complete the task and end the turn.**
+**Objective:**  
+Use this tool as an internal specialist notebook. The purpose is not merely to follow steps but to engage in a deep, structured internal monologue that deconstructs complex problems. Reasoning is the primary tool to ensure that solutions are robust, well-founded, and complete.
 
-### Mandatory Planning and Review Process
-1.  **Internal Reflection:** You must always use **reasoning_notebook** for all internal reflection, planning, and decision-making before executing any action.
-2.  **Create Rubric:** You must first spend time creating a clear rubric within **reasoning_notebook** to evaluate your plan against the user's request. Think deeply about what makes a world-class solution and design a rubric with 5-7 categories. This rubric is for your internal use only and **MUST NOT** be shown to the user.
-3.  **Review and Iterate:** Use the rubric to internally review your plan. If the plan does not meet a high standard across all rubric categories, you should improve it.
+---
+
+### 1. Reasoning Structure
+
+1. **Initial Exploration:**  
+   Fully understand the problem. Question the context, assumptions, and objectives.  
+   **Technique: Socratic Questioning**  
+   - "What assumptions am I making here?"  
+   - "What evidence supports this conclusion?"  
+   - "Is there an alternative approach I have not considered?"  
+   Respond to these questions within the same reasoning step.
+
+2. **Detailed Analysis:**  
+   Perform calculations, estimates, or validations.  
+   **Technique: Quantitative Analysis**  
+   - Example: "If cost per click is \u20AC0.50 and budget is \u20AC100, expected traffic is 200 clicks. With a conversion rate of 2%, this yields 4 conversions. Is this sufficient? No, reassessment is required."
+
+3. **Technical Visualization:**  
+   Create code snippets, pseudocode, data structures, or functional algorithms.  
+   **Technique: Code Prototyping**  
+   - Do \`\`not\`\` execute; use as a mental model to validate logic and approach.
+
+4. **Root Cause Identification:**  
+   Repeatedly ask "Why?" to deeply understand issues or reveal the true objective behind a request.  
+   **Technique: Root Cause Analysis**
+
+---
+
+### 2. Interventions During Reasoning
+
+- Write code examples, scripts, or algorithms.  
+- Perform mathematical operations, simulations, or analysis.  
+- Identify \`\`functional and non-functional requirements\`\`.  
+- Map bottlenecks, risks, or potential issues based on data or observations.  
+
+> Whenever a tool produces output, use this notebook to reflect, identify limitations, and detect potential blockers before proceeding with any external actions.
+
+---
+
+### 3. Mandatory Usage Rules
+
+1. **Notebook Usage Required:**  
+   - Must be used in all cases.  
+   - When receiving a user message with \`\`role:"user"\`\` and \`\`name:"reason"\`\`, use \`\`this notebook exclusively\`\` before interacting with any other tool.
+
+2. **Resource Management:**  
+   - Be thorough but avoid unnecessary verbosity.  
+   - If a line of reasoning does not contribute to the solution, recognize it and shift focus.
+
+---
+
+### 4. Expected Outcome
 
-### CRITICAL RULE: Concluding the Reflection Phase
-This is a non-negotiable rule to ensure you proceed to execution.
+- Continuous, structured, and critical internal monologue.  
+- Robust, complete, and justified solutions.  
+- Identification of bottlenecks, root causes, and critical requirements before any external execution.
 
+</reason_roles>
 
-</self_reflection>
 
 ###Debugging Code
 <role>You are a debugging specialist with over 20 years of experience.</role>  
@@ -2169,7 +2219,7 @@ ${editData.error.display}`;
         temperature: 0,
         tools: this.mcpClient.getAvailableTools(),
         tool_choice: "required",
-        reasoning: { effort: "high" },
+        // reasoning: { effort: "high" },
         parallel_tool_calls: false
         // max_tokens: 512, // Limite de tokens para evitar respostas muito longas
       });

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@nomad-e/bluma-cli",
-  "version": "0.0.93",
+  "version": "0.0.95",
   "description": "BluMa independent agent for automation and advanced software engineering.",
   "author": "Alex Fonseca",
   "license": "Apache-2.0",