Add ability for launcher stages to report diagnostics - #338
Draft
Conversation
…so the boot chain can report non-fatal behaviours
Liam Farrelly (lfarrel6)
changed the base branch from
main
to
liam/fou-567-surface-more-context-from-enclave-process
August 18, 2026 22:18
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Why
Stacked on #337
In order to make the launcher chain more useful than an abstraction on critical workflows, this PR extends the interface to give us diagnostics support. This should unlock the reporting of non-fatal errors and graceful degradations that may occur within the enclave launch process.
Each diagnostic is emitted explicitly by a stage of the launcher. There must be care taken to ensure that the diagnostics only reveal a minimal amount of safe data.
How