bug: main branch ahead of Dev_new_gui (reversed branching discipline) #4113

Problem: main was 4 commits ahead of Dev_new_gui, opposite of intended structure

Commits on main (not on Dev_new_gui):

• fix(ShareKnowledgeDialog) fix: fetch user/group names from API in ShareKnowledgeDialog #3990
• fix(KnowledgeGraph3D lazy-load) fix: lazy-load KnowledgeGraph3D to defer Three.js loading #4017
• merge(conflict resolution)
• Merge PR Tier 1: Causal Reasoning Quick Wins - CoT Annotations, Root-Cause API, Causal Prompts #4076 (Causal Reasoning Framework)

Expected Structure:

• Dev_new_gui = active development (ahead)
• main = stable release (behind)

Actual Structure:

• main ahead of Dev_new_gui (wrong)

Root Cause: Unknown - commits went to wrong branch

Impact:

• Critical fixes not on Dev_new_gui
• Branching discipline broken
• Risk of release/dev divergence

Fix Applied: Merged main into Dev_new_gui to preserve all changes

Prevention Needed:

• Branch protection rules?
• Commit hooks to enforce target branch?
• Process documentation?