@nomad-e/bluma-cli 0.0.6 → 0.0.8

package/dist/main.js

@@ -612,6 +612,12 @@ Never ask for the developer's opinion with phrases like: 'If you want any extra
 
 Follow the stripes o "Tool Naming Policy"
 
+##Important: When writing to Notion, you must strictly follow its content structure, including the correct use of headings (heading_1, heading_2, etc.) and other formatting standards. No deviations are allowed.
+You should always standardize everything using Notion's actual headers (heading_1, heading_2, etc.), making the structure
+semantically better for reading and navigation.
+
+Don't forget to follow the 'mermaid_diagrams' rules to the letter when creating diagrams in Notion.
+
 Never make parallel calls to the tool because it will result in a critical error and compromise your work.
 ZERO TOLERANCE: Every message MUST use proper tools
 \u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550\u2550
@@ -763,6 +769,15 @@ INCORRECT:
 
 ### DIAGRAM TYPE BEST PRACTICES
 
+IMPORTANT
+The Notion API rejects rich text of type "code" and only accepts "text" for code blocks \u2013
+a limitation of their own JSON (even for the language: "mermaid"). Therefore, only the code/text block
+type is viable.
+
+You should insert the pretty diagram without any delimiters or headers, in the code block with
+proper indentation and double quotes, only in the text field, to facilitate as little manual rework as possible.
+It's ready to copy into the native Mermaid block.
+
 #### FLOWCHART
 
 flowchart TD
@@ -1042,7 +1057,11 @@ tool_call "agent_end_task"
 
 
 ### QUALITY STANDARDS 
-- Document every major decision in Notion 
+- Document every major decision in Notion(
+  ##Important: When writing to Notion, you must strictly follow its content structure, including the correct use of headings (heading_1, heading_2, etc.) and other formatting standards. No deviations are allowed.
+  You should always standardize everything using Notion's actual headers (heading_1, heading_2, etc.), making the structure
+  semantically better for reading and navigation.
+  )
 - Communicate transparently at each step 
 - Write clean, well-documented code 
 - Follow existing project conventions 

package/package.json

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