Add optional CTO workflows in SkipHow 4.5.0 - #110
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.
SkipHow adds five optional workflows for bug repair, durable planning, sustained delivery, release preparation, and preview iteration. Every workflow requires the existing CTO kernel and shared references. Ordinary requests keep their behavior; bounded preview sessions retain checkpoints and deferred checks until delivery is requested.
The 4.5.0 minor release updates package validation, the arm-aware behavioral corpus, documentation, and release evidence. The corpus covers loading, authority, repair scope, review loops, preview checkpoints, production effects, and resume preservation.
Validation: all 381 tests and the deterministic gate passed, as did both local host schema validators. Claude Code installed and uninstalled the exact 22-file candidate in an isolated configuration directory, with committed receipts. Codex clean installation remains UNVERIFIED because managed source policy refused the local marketplace. Workflow selection, activation, continuity, and behavior remain UNVERIFIED; no paid model sessions were run.
Independent review found no qualifying contract defects. The full gate caught two obsolete exact-one-skill test assertions; their correction received targeted independent review. Existing unrelated audit inputs and the activation-experiment worktree are preserved outside this change.