Skip to content

Release SkipHow 4.7.0 routing and verification health - #115

Merged
mzored merged 4 commits into
mainfrom
release/470-verification-health
Sep 8, 2026
Merged

Release SkipHow 4.7.0 routing and verification health#115
mzored merged 4 commits into
mainfrom
release/470-verification-health

Conversation

@mzored

@mzored mzored commented Sep 8, 2026

Copy link
Copy Markdown
Owner

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:

  • Full local python scripts/check.py passed with pinned dependencies on Python 3.14.7. A final grammar correction in the decision ledger was followed by the focused package/document check, which passed.
  • Corpus checks passed, 48 tests. Final git diff --check passed.
  • Local Codex and Claude strict schema validators both passed.
  • Independent read-only review found no qualifying defects against the supplied spec or outcome contract. The prior verification-health fixture defect remains resolved.
  • No paid model sessions or clean-install smoke were run. Package structure and host bindings are unchanged. Routing, verification-health behavior, effective delegate settings, and savings remain UNVERIFIED.

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.

@mzored mzored changed the title Prepare SkipHow 4.7.0 verification-health guidance Release SkipHow 4.7.0 routing and verification health Sep 8, 2026
@mzored
mzored marked this pull request as ready for review September 8, 2026 01:46
@mzored
mzored merged commit 11446ad into main Sep 8, 2026
1 check passed
@mzored
mzored deleted the release/470-verification-health branch September 8, 2026 01:46
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant