Canonicalize GödelOS Runtime: Unify Server Entrypoint, WebSocket Manager, and Consciousness State

[Steake]

Our momentum has shifted GödelOS into a “working but fragmented” integration program. To enable the next phase of roadmap work, we must now:

1. Declare a single runtime entrypoint: All system startup (including scripts, CI, cloud hosting, and local dev) must flow through backend/unified_server.py as the canonical “kernel”.
2. Unify the WebSocket/event manager: Remove duplicate or experimental managers. Use the EnhancedWebSocketManager (or the agreed successor) everywhere. Contract-test all outbound event schemas.
3. Singularize the consciousness state computation: All API/dashboards/etc. must reference one state-of-the-art computation for φ, workspace, etc. Deprecate/removal historical/legacy “phenomenal experience” and consciousness modules.
4. Pipeline integration enforcement: All integration modules (including godelos_integration.py) must wire through the single cognitive pipeline (godelOS/cognitive_pipeline.py), removing fallbacks or degraded paths except as stubs for testability.
5. Eliminate legacy duplication: Clean up alternate modules/branches, log all remaining technical debt for future tracking.

Acceptance Criteria:

• Only one backend server start path exists.
• WebSocket broadcasting/events are routed through a singular manager/class.
• All system and dashboard reads for consciousness state are wired through one contract.
• No duplicate “phenomenal experience”, event, or state modules persist.
• CI and merge policies updated to enforce single-path runtime logic.