Repository navigation
Preserve reviewed scope through decision refresh and commit cleanup - #40
Merged
Merged
Conversation
dkropachev
force-pushed
the
fix/30-preserve-reviewed-scope
branch
from
October 26, 2026 22:17
320546b to
ee6b222
Compare
Use the registry revision when a native manifest omits its version, while keeping explicit version mismatches and resource tampering blocking. Exclude transient root host leases from new package snapshots and retain historical sealed inventories exactly. Keep the retention and descriptor regressions with their compatibility changes so host metadata refreshes preserve reviewed provider identity.
Cross-check incomplete CLI repository names against authoritative REST identity, IDs, refs, SHAs and fork status before choosing ownership. Share the resolver across configuration, review context, Decisions code links and live series evidence. Keep read-only support for deleted forks with positive fork evidence, while ownership-sensitive operations remain strict. Cover same-repository and fork identities, inconsistent evidence and actual caller behavior. Fixes #39
Compare refreshed preparation directly with original review evidence. Require source-verified mappings for discussion restatements and assess operational wording without weakening strict inputs, legacy provenance or persisted negative judgments. Bind regroup publication to immutable candidate and lease prechecks. Keep final preparation, reconciliation, engineering verification and exact-head CI separate, with structured diagnostics and recovery state. Keep regression fixtures aligned with preparation lineage and native exporters. Document retained-run recovery and release plugin 1.2.1. Fixes #30
dkropachev
force-pushed
the
fix/30-preserve-reviewed-scope
branch
from
October 27, 2026 02:24
282e801 to
550ddb2
Compare
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.
Issue
Required replies can add discussion Decisions that restate an already reviewed contract. Refreshing preparation then loses review coverage, leaving identical-tree cleanup blocked after the fifth cycle. GitHub CLI responses with an empty
headRepository.nameWithOwneralso block accessible PRs during configuration and cleanup (#30, #39).Fixes #30
Fixes #39
Fix
Add version-2 attestations that compare refreshed preparation directly with the original review. Every added discussion Decision needs a source-verified mapping to an original decision or prepared boundary. Operational wording and exact Decisions-backed choice evidence can retain coverage when engineering meaning is unchanged; material or ambiguous changes remain blocking. Original hashes, review artifacts, reviewer packages and cycle budgets stay intact, and version-1 attestations keep their original restrictions.
Require an immutable prepublication receipt for regroup pushes and no-op assessments, binding the candidate, lease and guard state to both preparations and the original review. Revalidate before publication and preserve uncertain-push recovery. Prechecks establish review and cleanup readiness separately from completion; final-head preparation, reconciliation, engineering verification and exact-head CI remain required.
Use one shared repository identity resolver across configuration, preflight, cleanup, completion, review context and Decisions code links. When the CLI omits the full head name, cross-check the REST pull-request identity, repositories, IDs, refs, SHAs and fork status before proceeding.
Document recovery into the repaired runtime while preserving the active run and its exhausted budget. Bump both plugin manifests, the Claude marketplace entry and README to 1.2.1. Recovery is covered by representative fixtures; this change does not operate on the external PR #150 run.