Reconcile final maintenance security state - #218
Merged
ashfame merged 2 commits intoJul 28, 2026
Merged
Conversation
ashfame
merged commit Jul 28, 2026
6b4a517
into
agent/maintenance-security-and-hygiene
5 checks passed
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.
Change
Reconcile every baseline alert against the final integration lock, record current residual causal paths and audit-only advisories, close stale child/branch status records, and add the automated and manual handoff checklist.
Root cause
Child-stage alert wording no longer reflected later compatible lock refreshes, while GitHub continues to show default-branch alerts until the draft integration PR reaches trunk. A final range-, scope-, and path-aware reconciliation was required to distinguish real lock resolution from residual or scanner-hidden risk.
Affected alerts
All 124 baseline rows are revalidated. The final integration lock resolves 84 rows and retains 40 affected rows: 26 WPS, five React Router, three Concurrently plus WPS, two block-library, two Babel plus WPS, one web-ext, and one web-ext plus WPS. Alert 171 is lock-resolved but retains the documented Playground bundled-source blocker. Seven current npm-audit GHSAs are also recorded without inventing GitHub alert numbers.
Impact
This documentation-only child changes no manifest, lockfile, application source, configuration, generated schema, public API, stored data, behavior, or license metadata. It makes clear that functional automation passes but security acceptance remains blocked by 40 baseline rows, seven audit-only advisories, and the hidden Playground source risk.
Checks
The integration PR remains draft and unmerged for manual testing and explicit residual-risk decisions.