Create a Typed Startup Preflight and Configuration Compatibility Layer for Every Runtime Mode

[Inkman007]

Problem

Configuration is spread across settings, YAML, CLI flags, Helm values, Compose, workflows, and subsystem-specific modules. Invalid combinations are often discovered only when a code path executes, while renamed/deprecated values can drift silently between deployment surfaces.

Scope

• Define a canonical typed configuration schema with source precedence and runtime-mode profiles.
• Validate cross-field invariants for API, streamer, batch scoring, training, webhook worker, federation, and contract publishing.
• Add ledgerlens config validate and config explain commands that show effective non-secret values and provenance.
• Generate or validate .env.example, Helm values/schema, and Compose variables against the canonical schema.
• Add explicit deprecation windows and compatibility errors.
• Check external prerequisites (database extensions/schema, model compatibility, writable paths, certificates, endpoints) in a bounded preflight.

Acceptance criteria

• Every executable mode runs preflight before accepting work.
• Unknown, deprecated, unsafe, or contradictory settings fail with actionable messages.
• Secret values are always redacted.
• CI detects drift between code, environment example, Helm schema, and docs.
• Tests cover precedence and supported configuration matrices.
• Preflight supports offline validation and distinguishes warnings from fatal errors.