Fix duplicate consciousness bootstrap calls and refactor demo imports

[Copilot]

Addresses code review feedback from PR #44. The system was calling bootstrap_consciousness() twice on startup (lines 442 and 492 in unified_server.py), potentially creating duplicate goals and inconsistent state. Demo file had imports scattered inside functions.

Duplicate Bootstrap Prevention

• Extract is_consciousness_bootstrap_complete() helper that checks phenomenal_experience.bootstrap_complete flag
• Apply check at both bootstrap locations (cognitive_manager init and unified_consciousness_engine init)
• Add null safety for consciousness_engine and cognitive_state_injector

def is_consciousness_bootstrap_complete(cognitive_manager) -> bool:
    if not cognitive_manager or not hasattr(cognitive_manager, 'consciousness_engine'):
        return False
    ce = cognitive_manager.consciousness_engine
    if not ce or not hasattr(ce, "current_state") or not hasattr(ce.current_state, "phenomenal_experience"):
        return False
    return ce.current_state.phenomenal_experience.get("bootstrap_complete", False)

Bug Fix

• Correct attribute name: consciousness_state_injector → cognitive_state_injector (the former doesn't exist in UnifiedConsciousnessEngine)

Code Quality

• Move inline imports to top of demo_consciousness.py (6 imports consolidated)
• Extract state_injector to local variable to avoid repeated property access

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.