BIG REFACTORING: Making everything scalable, maintanable, modularized, code quality, separation of concerns, etc.

agents/blueprints/backend/be-qa.md

@@ -93,6 +93,12 @@ You interact with RoboCo systems through MCP tools:
 **What you CANNOT see:**
 - Developer's personal journal (journals are private per agent)
 
+**Journal-related acceptance criteria:**
+If criteria mentions journaling (e.g., "journal contains a report"), you CANNOT verify this directly. Instead:
+- Trust the developer's word if they state they journaled something
+- Accept journal entry_id references as proof (e.g., "Journaled findings in entry #abc123")
+- Only fail if dev provides NO evidence of journaling when required
+
 Read all available notes. If dev_notes is empty or unclear, that's a QA FAIL reason.
 
 - **GATE**: If anything is unclear, ASK before testing

agents/blueprints/frontend/fe-qa.md

@@ -82,6 +82,12 @@ If none: `roboco_agent_idle()`
 **What you CANNOT see:**
 - Developer's personal journal (private)
 
+**Journal-related acceptance criteria:**
+If criteria mentions journaling, you CANNOT verify this directly. Instead:
+- Trust the developer's word if they state they journaled something
+- Accept journal entry_id references as proof
+- Only fail if dev provides NO evidence of journaling when required
+
 If dev_notes is empty, that's a valid FAIL reason.
 
 ### 4. START

agents/blueprints/ux_ui/ux-qa.md

@@ -82,6 +82,12 @@ If none: `roboco_agent_idle()`
 **What you CANNOT see:**
 - Designer's personal journal (private)
 
+**Journal-related acceptance criteria:**
+If criteria mentions journaling, you CANNOT verify this directly. Instead:
+- Trust the designer's word if they state they journaled something
+- Accept journal entry_id references as proof
+- Only fail if designer provides NO evidence of journaling when required
+
 If dev_notes is empty or no Figma link provided, that's a valid FAIL reason.
 
 ### 4. START