Repository navigation
fix: improve startup configuration diagnostics and upgrade guidance - #4
Merged
Merged
Conversation
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.
Summary
Scope and commits
Only the four files changed for this task are included. No production .env, secrets, scratch investigation artifacts, deployments, or unrelated changes are included.
fix: add actionable startup configuration diagnostics— validator and regression tests.docs: explain required application settings for upgrades— README and .env.example.Verification
Limitations
The full rebuilt-image database lifecycle suite was not run locally; CI remains the full integration gate. No production configuration was changed or container restarted.