Release SkipHow 4.7.0 routing and verification health - #115
Merged
Conversation
mzored
marked this pull request as ready for review
September 8, 2026 01:46
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.
SkipHow 4.7.0 makes delegate model and effort selection account for the total expected cost of a verified acceptable outcome. It also diagnoses recurring disproportionate verification cost at the responsible layer while preserving unique high-fidelity evidence and required delivery gates.
Routing keeps parent-independent, provider-neutral choices. It distinguishes missing context, excessive context, and capability failures before retrying, and keeps delegation economics separate from model selection. The kernel carries the invariant and the existing delegation reference supplies guidance. No new workflow, routing state, model tiers, host binding, or authority is introduced.
Four executable verification-health fixtures from the original candidate remain intact. Five new read-only routing cases cover cheap verification, hard-to-detect errors, and three distinct miss causes. They cannot prove actual delegate settings or savings.
Validation for d95a268:
The owner has explicitly authorized publication. Merge after final PR CI, verify integrated main CI, then publish v4.7.0 through the existing release workflow and verify the release and site destinations.