Skip to content

fix(app): diagnose startup failures before exiting - #99

Merged
nick2781 merged 3 commits into
fix/application-drain-lifecyclefrom
fix/startup-failure-diagnostics
Oct 20, 2026
Merged

nick2781 merged 3 commits into
fix/application-drain-lifecyclefrom
fix/startup-failure-diagnostics

Conversation

@nick2781

@nick2781 nick2781 commented Oct 20, 2026 •

Copy link
Copy Markdown
Member

Startup failures could abort abruptly or lose the plugin/module and lifecycle phase that failed. Report missing libraries, missing plugin entry points, false startup hooks and standard/nonstandard exceptions with their owning plugin/module and phase, then exit with status 1 before later startup callbacks.

Extend real-process TOML and XML acceptance cases across all four startup stages and loader failures. Integrate the shutdown safeguards from #95, including the Windows C++ exception boundary; normal accepted work still drains before teardown.

Validation at 13cc8cb499f34bae784815f645a3fca6b2da84fe: macOS Debug complete check-core passed, including 24 startup processes and inherited drain regressions; 71 CI policy tests, whole-project clang-format 18 and Nimbus documentation checks passed (123 HTML pages, 217 internal references).

Windows and the complete merge-candidate matrix remain required hosted acceptance. Partial-start resource rollback, plugin hot replacement and general shared-library unloading safety remain separate work. #95 is the parent change and should merge first.

@nick2781
nick2781 marked this pull request as ready for review October 20, 2026 03:26
@nick2781
nick2781 merged commit 54be9e0 into fix/application-drain-lifecycle Oct 20, 2026
@nick2781
nick2781 deleted the fix/startup-failure-diagnostics branch October 20, 2026 03:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant