Repository navigation
v0.5.6
Summary
Config Phase 3 landing (issue #226) — canonical env-key rename + start.sh registry self-check.
Breaking changes
FUSION_API_KEYis renamed toFUSION_CLIENT_KEY(canonical client credential for any endpoint;FUSION_AUTH_TOKENremains an equivalent alias). No in-repo alias chain is kept — alias compatibility is fusion-core's job.- The engine-local env aliases
FUSION_MLX_API_KEY/MLX_API_KEYare no longer read. Engine-side key fallback is~/.fusion-mlx/settings.jsonauth.api_key. Gateway-side deprecated aliases (FUSION_GATEWAY_API_KEY/GATEWAY_API_KEY) still work with a once-per-session warning.
start.sh: register-then-start self-check
start.sh start now refuses to start when its port is not declared in architecture/port-registry.yaml. FUSION_SKIP_REGISTRY_CHECK=1 bypasses; a missing registry file warns and continues.
Acceptance
python scripts/check-env.py --root fusion-code reports 0 errors / 0 warns (clean under --strict too). All four start.sh paths verified live. Gates: tsc 0 / unit 1232 / integration 345 / lint / layers / flags 88=88 / build 3793 modules.
🤖 Generated with Claude Code