Repository navigation
fix: restore opt-in HTTP policy and align Kernel cache diagnostics - #31
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
1 participant
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 1.2.0–1.2.2 implicitly blocks outbound WordPress HTTP in production/staging, breaking payment, mail, licence and other existing API integrations. Restore the compatible 1.x default: blocking is opt-in, and explicit host allowlists remain authoritative. Doctor validates the selected HTTP policy and reports hardening configuration separately from unverified application hook activation.
Align read-only diagnostics and cache maintenance with Kernel 1.1.5's JSON metadata contract; the optional Kernel floor is 1.1.5. Keep legacy PHP metadata retirement safe without executing it. The published 1.2.2 baseline already contains the process-fingerprint removal; regression checks prove cache/dump do not expose dictionary-testable process values.
Validation: canonical strict package QA (1,425 tests /10,349 assertions, no skips or warnings), documentation checks (96 files), real WordPress HTTP opt-in/default tests, plus focused JSON metadata/selection/retirement and classic-webroot/cold-read-only fallback tests against the published Kernel archive. Read-only diagnostics validate the same private temporary generation, ownership and protected ancestors, without adopting unsafe legacy caches. Release guide documents regenerating existing managed configuration and updating the Kernel/Runtime pair. Release: 1.2.3.