chore(runbooks): log merge-guard v4.4.51-batch post-install live-probe — 29/29 PASS on installed v4.4.52#1090
Merged
Conversation
…e — 29/29 PASS on installed v4.4.52
There was a problem hiding this comment.
Pull request overview
Adds an append-only runbook log entry documenting a post-install live-probe of the merge-guard batch fixes against the installed v4.4.52 plugin, discharging the gated-closure confirmation for the previously-merged v4.4.51 work.
Changes:
- Appends a new dated section to
RUNBOOK_RUN_DATES.mdrecording a 29/29 PASS post-install probe. - Documents byte-identity confirmation (installed hooks vs
origin/main), corpus provenance, and outcome breakdown (ALLOW/DENY/REFUSE/AUTHORIZE expectations).
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
This was referenced Jul 2, 2026
Closed
michael-wojcik
added a commit
that referenced
this pull request
Jul 3, 2026
… runbook (keep both probe sections chronologically: #1090 post-install, then cross-leg fix-level)
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.
Summary
Logs the post-install live-probe of the merge-guard against the installed v4.4.52 plugin — the final gate held open since PR #1085 (v4.4.51) merged. 29/29 PASS, zero installed-vs-source divergence, no HALT.
Runbook-log-only: +6 lines, append-only new section in
pact-plugin/tests/runbooks/RUNBOOK_RUN_DATES.md. No code changes, no version bump (runbook-log precedent: the #1063/v4.4.50 log PR).What the probe did
diff -rof the installed v4.4.52 hooks tree vs source at60f14796— byte-identical (excl.__pycache__), covering both hook mains + everyshared/module transitively.merge_guard_pre.py/merge_guard_post.pymains as real subprocesses (hooks.jsonpython3 <hook>.pyshape, macOS system python3 3.9.6), per-probe isolatedCLAUDE_CONFIG_DIR+HOME, zero~/.claudecontamination.Issue closure
This row discharges the post-install gate for #1064, #1077, #1078, #1082, #1083 (gated-closure discipline from PR #1085). The five issues will be closed manually after this PR merges, citing the merged row. Not using auto-close keywords.
Not-certified perimeter (mirrored from the row, review M1): NOT probed — #1087 (multi-close ambiguity laundering, open, pre-existing, tracked); #1079 closed won't-fix 2026-07-01.