Repository navigation
feat(runtime): production checks and safe deployment maintenance - #10
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.
Runtime now supports production checks and repeatable deployment maintenance: setup drift detection, a strict production doctor, source-aware environment caches, mounted secrets, URL download pins, crash recovery and protected pruning. Temporary-file fallback can no longer expose environment secrets outside the intended directory.
The native profile gains Composer-managed update protection; legacy profiles retain their contracts. Generated modes support 0600/0640, database table scans require an explicit native maintenance command, and bootstrap bundling is optional. The guides, option schema and ADRs document defaults and limits. Changes remain Unreleased; existing 0.1.0 tags and consumer pins are unchanged.
Validation:
Boundaries: drift requires a successful baseline and reports custom side effects as unknown. Production checks report opaque PHP, unverified ACLs and web-server protection as unknown rather than certifying them. TOFU does not independently authenticate the first download. Existing unowned backups are retained.