Repository navigation
Speed up delivery with selective checks and safe offline reuse - #2
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.
SStack previously ran its full suite for README edits and repeated separate lint, coverage and review handoffs. This change gives README-only work a documentation gate and runs registered affected checks through one command, with bounded parallel execution for explicitly safe checks. Skills, runtime, configuration, unknown coverage and declared live acceptance retain their gates.
Successful offline reports can be reused only with identical revision/input/command/runtime bindings, intact logs and an explicit environment key; custom checks require reuse_safe opt-in. Live/UI proof and independent review are never cached. Delivery can consume embedded coverage from the same report, avoiding duplicate evidence files.
The skills now default to one independent verifier/reviewer, overlapping review with safe checks on a stable head. CI uses the same selection, caches dependencies and cancels superseded PR runs while retaining the existing check name.
Validation: selection, serial-barrier/concurrency, stale/corrupt-cache and delivery regressions; integrated suite with 111 passing tests; a fresh clone README-only gate selected exactly docs and passed in 0.19 seconds, with subsequent explicit reuse returning the original report. That timing measures local verification, not full feature-delivery speed. Independent review and current-head CI are required before merge.