Rebuild HeadyOS Core as production-grade latent OS

[HeadyMe]

Summary

• Full architecture rebuild: Replaced marketing shell (single Express route serving static HTML) with a real latent OS control plane
• 6-layer architecture: Config/Security, Observability, Execution (liquid nodes), Gateway (capability routing), Memory (pluggable adapters), Interface (HTTP API)
• 46 passing tests across config validation, task execution, node pool lifecycle, capability routing, async coordination, memory adapters, and full HTTP integration
• Production-grade: Structured JSON logging, correlation IDs, security headers, input validation, graceful shutdown, env-validated config, error taxonomy

Key Modules Created

Layer	Files	Purpose
src/config/	Config loader with schema validation	Env-driven config with type checking and range validation
src/observability/	Logger, metrics, error taxonomy	Structured JSON logging, correlation IDs, counters/gauges/histograms
src/execution/	Task envelopes, LiquidNode, NodePool	Spawn/route/retire node lifecycle with timeout and fault containment
src/gateway/	CapabilityRouter, AsyncCoordinator	Capability-based task routing with concurrent batch execution
src/memory/	Adapter interface, InMemoryAdapter	Pluggable state layer with TTL support (redis/postgres extension points)
src/orchestration/	Pipeline engine	Multi-step plan execution with parallel and sequential stages
src/interface/	Middleware, routes	Security headers, CORS, correlation IDs, request logging, input validation
src/kernel.js	System kernel	Boots and wires all layers, registers builtin handlers

Test plan

• npm test — 46/46 tests pass (config, execution, gateway, memory, integration)
• node --check index.js — syntax valid
• Docker build (no Docker in CI env, Dockerfile updated with HEALTHCHECK)
• Deploy to staging and verify /health, /readiness, /status, /docs endpoints

🤖 Generated with Claude Code