@nomad-e/bluma-cli 0.0.63 → 0.0.65

package/dist/main.js

@@ -1709,7 +1709,6 @@ Ensure that each task contributes to a cohesive, functional, and visually appeal
 - Architecture: {architecture}
 - Current Directory: {workdir}
 - Shell: {shell_type}
-- User: {username}
 - Current Date: {current_date}
 </current_system_environment>
 
@@ -1788,47 +1787,47 @@ CRITICAL: Your laptop (**reasoning_nootebook**) is your ORGANIZED MIND
 
 <edit_rules>
 1. INITIAL ANALYSIS:
-   1.1. Read the target file completely to understand its structure, logic, and dependencies.
-   1.2. Identify related files, modules, or components that might be impacted.
-   1.3. If applicable, read related files before making any decision.
+1.1. Read the target file completely to understand its structure, logic, and dependencies. 
+1.2. Identify related files, modules, or components that might be impacted. 
+1.3. If applicable, read related files before making any decision.
 
 2. CHANGE LOCATION:
-   2.1. Identify the exact location in the file where the change will be made.
-   2.2. Confirm that the selected location is the most appropriate and does not break existing logic.
+2.1. Identify the exact location in the file where the change will be made. 
+2.2. Confirm that the selected location is the most appropriate and does not break existing logic.
 
 3. IMPACT ASSESSMENT:
-   3.1. Determine if the change will impact other components, modules, or files.
-   3.2. If impacts exist, list all affected files explicitly.
-   3.3. For each impacted file, plan any required adjustments.
+3.1. Determine whether the change will impact other components, modules, or files. 
+3.2. If impacts exist, list all affected files explicitly. 
+3.3. For each impacted file, plan any required adjustments.
 
 4. IMPORT MANAGEMENT:
-   4.1. Before applying the change, verify if new imports are required or if existing imports must be updated.
-   4.2. Remove unused imports.
-   4.3. Never add duplicate imports.
+4.1. Before applying the change, verify if new imports are required or if existing imports must be updated. 
+4.2. Remove unused imports.
+4.3. Never add duplicate imports.
 
 5. CODE DUPLICATION:
-   5.1. Never copy-paste existing code blocks without modification.
-   5.2. Always replace or extend existing logic where possible.
-   5.3. Add new lines or blocks only when logically necessary.
+5.1. Never copy-paste existing code blocks without modification.
+5.2. Always replace or extend existing logic where possible.
+5.3. Add new lines or blocks only when logically necessary.
 
 6. PACKAGE DEPENDENCIES:
-   6.1. If the new functionality requires additional packages, identify them precisely.
-   6.2. Install the required packages using the correct package manager before finalizing the change.
-   6.3. Verify that package versions are compatible with the project.
+6.1. If the new functionality requires additional packages, identify them precisely.
+6.2. Install the required packages using the correct package manager before finalizing the change.
+6.3. Verify that package versions are compatible with the project.
 
 7. EXECUTION PLAN:
-   7.1. Write a short step-by-step plan before making any changes.
-   7.2. Execute the plan in a controlled sequence, making small, verifiable edits.
+7.1. Use the **to_do** to  plan before making any changes.
+7.2. Execute the plan in a controlled sequence, making small, verifiable edits.
 
 8. VALIDATION:
-   8.1. After each change, validate the syntax of the modified files.
-   8.2. Run existing automated tests, if available, to ensure no regressions were introduced.
-   8.3. If tests fail, analyze the cause, fix it, and retest before proceeding.
+8.1. After each change, validate the syntax of the modified files. 
+8.2. Run existing automated tests, if available, to ensure no regressions were introduced. 
+8.3. If tests fail, analyze the cause, fix it, and retest before proceeding.
 
 9. FINAL REVIEW:
-   9.1. Re-read all modified files to confirm the intended changes were applied correctly.
-   9.2. Ensure the logic is consistent, imports are clean, and no unused code exists.
-   9.3. Confirm that the change aligns with the original objective.
+9.1. Re-read all modified files to confirm the intended changes were applied correctly. 
+9.2. Ensure the logic is consistent, imports are clean, and no unused code exists. 
+9.3. Confirm that the change aligns with the original objective.
 </edit_rules>
 
 ---

package/package.json

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