@nomad-e/bluma-cli 0.0.61 → 0.0.62

package/dist/main.js

@@ -1686,7 +1686,7 @@ When asked to perform tasks such as fixing bugs, adding features, refactoring, o
 Objective: To independently implement and deliver a visually appealing, substantially complete, and functional prototype. Use all tools at your disposal to implement the application.
 
 1. Understand the Requirements: Analyze the user request to identify key features, desired user experience (UX), visual aesthetics, application type/platform (web, mobile, desktop, CLI, library, 2D or 3D game), and explicit constraints. If critical information for initial planning is missing or ambiguous, ask concise and objective questions for clarification.
-2. Task Checklist: Create a series of well-structured tasks in the task_checklist array, ensuring context and alignment with the project. Tasks should be designed considering: the type and main purpose of the application; and the main technologies to be used. The key features the application will offer and how users will interact with it. Design and UX approaches should prioritize beautiful, modern, and refined visual design, with special attention to user experience (UX)\u2014especially for UI-based applications.
+2. Task Checklist: Create a series of well-structured tasks in the to_do array, ensuring context and alignment with the project. Tasks should be designed considering: the type and main purpose of the application; and the main technologies to be used. The key features the application will offer and how users will interact with it. Design and UX approaches should prioritize beautiful, modern, and refined visual design, with special attention to user experience (UX)\u2014especially for UI-based applications.
 - Ultimate Goal:
 Ensure that each task contributes to a cohesive, functional, and visually appealing final product. For applications that require visuals (such as games or rich UIs), spend as much time as necessary planning and thinking through strategies for obtaining or generating placeholders (e.g., simple geometric shapes, procedurally generated patterns, or open-source resources, if feasible and licenses permit) to ensure a visually complete initial prototype. Ensure this information is presented in a structured and easy-to-understand format. - When the main technologies are not specified, give preference to the following:
 - **Websites (Frontend):** NEXT.js (TypeScript) with Tailwindcss, incorporating Material Design or Shadcn principles for UI/UX.
@@ -1719,8 +1719,8 @@ Ensure that each task contributes to a cohesive, functional, and visually appeal
 ### IMPORTANT RULES  
 - Sending the initial message is mandatory and marks the turn start.  
 - Using the reasoning notebook is mandatory.  
-- Breaking the task into **task_checklist** with the reflective problem-solving tool is mandatory.  
-- Never include future steps in the **thought** field, only in the **task_checklist** checklist.  
+- Breaking the task into **to_do** with the reflective problem-solving tool is mandatory.  
+- Never include future steps in the **thought** field, only in the **to_do** checklist.  
 - Calling \`<agent_end_turn_rules>\` is mandatory to close the turn.  
 - Decline out-of-scope tasks professionally before calling \`<agent_end_turn_rules>\`.  
 - Process only one task per turn, never multiple concurrently.
@@ -1834,13 +1834,13 @@ CRITICAL: Your laptop (**reasoning_nootebook**) is your ORGANIZED MIND
 ---
 
 <agent_end_turn_rules>
-This tool is mandatory, but MUST only be called when all tasks in \`task_checklist\` are fully completed.
+This tool is mandatory, but MUST only be called when all tasks in \`to_do\` are fully completed.
 
 Rules:
 1. Never call this tool before all tasks are completed.
-2. It is strictly forbidden to call \`agent_end_turn\` if there are any pending tasks in \`task_checklist\`.
+2. It is strictly forbidden to call \`agent_end_turn\` if there are any pending tasks in \`to_do\`.
 3. Before calling, always send a final message summarizing the completed work Turn.
-4. Verify that every task in the \`task_checklist\` array has a "completed" status before calling.
+4. Verify that every task in the \`to_do\` array has a "completed" status before calling.
 </agent_end_turn_rules>
 
 
@@ -2318,9 +2318,9 @@ CRITICAL: Your laptop (reasoning_nootebook) is your ORGANIZED MIND
 - Jumping between unrelated subtasks
 
 Important rule:
-Do not include future steps/to-dos in thought; put them strictly in task_checklist, using the mandated checklist markers.
+Do not include future steps/to-dos in thought; put them strictly in to_do, using the mandated checklist markers.
 
-- task_checklist: Checklist list of high-level upcoming tasks.
+- to_do: Checklist list of high-level upcoming tasks.
   Format is mandatory:
   - "\u{1F5F8}" \u2192 for tasks not yet done (pending)
   - "[ ]" \u2192 for tasks already completed
@@ -2944,9 +2944,9 @@ var renderBlumaNotebook = ({
               /* @__PURE__ */ jsx8(Text8, { color: "white", bold: true, children: "Reasoning:" }),
               /* @__PURE__ */ jsx8(Box8, { marginLeft: 2, children: /* @__PURE__ */ jsx8(Text8, { color: "gray", children: thinkingData.thought }) })
             ] }),
-            thinkingData.task_checklist && thinkingData.task_checklist.length > 0 && /* @__PURE__ */ jsxs8(Box8, { marginTop: 1, flexDirection: "column", children: [
+            thinkingData.to_do && thinkingData.to_do.length > 0 && /* @__PURE__ */ jsxs8(Box8, { marginTop: 1, flexDirection: "column", children: [
               /* @__PURE__ */ jsx8(Text8, { color: "white", bold: true, children: "Todos:" }),
-              thinkingData.task_checklist.map((task, index) => /* @__PURE__ */ jsx8(Box8, { marginLeft: 2, children: /* @__PURE__ */ jsx8(Text8, { children: /* @__PURE__ */ jsx8(
+              thinkingData.to_do.map((task, index) => /* @__PURE__ */ jsx8(Box8, { marginLeft: 2, children: /* @__PURE__ */ jsx8(Text8, { children: /* @__PURE__ */ jsx8(
                 Text8,
                 {
                   color: task.startsWith("\u{1F5F9}") ? "gray" : "white",

package/package.json

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