Lattice

Added

• Added optional lifecycle failure context on LifecycleException, including runtime id, phase, failed operation, and module id when available.
• Added structured startup report entries while keeping the existing string-based startup event list.
• Added optional config failure context on ConfigException, including config path and operation when Lattice can identify them.
• Added lifecycle diagnostics details for failed runtime operations, including event count, failed operation, module id, and failure message.

Changed

• Module lifecycle callback failures now preserve module id and operation context across load, enable, ready, and disable paths.
• YAML config load, parse, render, defaults, deserialize, validate, migrate, serialize, save, and update validation failures now use context-aware ConfigException reporting.
• Public diagnostics and getting-started docs now describe how plugin-owned logging and diagnostics commands can surface lifecycle and config context.

Fixed

• Lifecycle diagnostics no longer report a failure finding for a fresh runtime that has not started.
• Lifecycle diagnostics now keep an error status when a failed lifecycle entry remains after a later phase transition.
• Disable failures now use lifecycle-neutral diagnostic wording instead of startup-specific wording.

Compatibility

• Existing LifecycleException and ConfigException constructors remain supported.
• Existing StartupReport#events() callers continue to receive the legacy string event list.
• Structured startup report write helpers remain runtime-owned and are not exposed as stable plugin authoring API.