Bootstrap image remediation without closing the parent backlog #2425

Parent and implementation

Parent security ledger: #2396
Current implementation PR: #2409 at head 1d9f72d7c40bff34aa43b8107cb817ad01e8efd5

This child tracks the bounded patchable-dependency and enforcement-bootstrap slice only. It must not close #2396, because the exact current image still reports 259 HIGH/CRITICAL occurrences.

Verified current state

• The exact current image has 15 fewer HIGH/CRITICAL occurrences than the prior image.
• Application-level findings for Next.js, sharp, proxy-addr, source-map-js, devalue, ip-address, pacote, picomatch, sigstore, jaraco.context, and wheel are absent from the retained current-head SARIF.
• The new lowercase trivy job fails as configured on remaining findings.
• The PR also fails Dependency Review on NumPy 2.5.4's composite license expression.
• No review approval exists and the PR remains draft.

Bootstrap deadlock to resolve

The PR combines partial remediation with a strict zero-HIGH/CRITICAL gate. Because 259 findings remain—including 251 OS occurrences without fixed versions in the retained report—the new gate intentionally fails and prevents the same remediation PR from satisfying merge gates.

Acceptance criteria

• Preserve Triage image findings despite successful Trivy job #2396 as the parent backlog until a clean re-fetched image or separately reviewed applicability/VEX evidence accounts for every remaining finding.
• Choose and document a mergeable bootstrap path:
  • split the already-verified dependency repairs from final strict enforcement; or
  • implement a reviewable baseline-delta gate that blocks new/regressed findings without erasing the existing backlog.
• Retain exact source commit, image identity, SARIF, counts, and package paths.
• Resolve the NumPy composite-license result without silently relaxing license policy.
• Re-run CI, security, dependency review, E2E, coverage, CodeQL, secret scan, and applicable review checks against one exact head.
• Keep the PR draft while intentional required checks fail.
• Do not deploy or merge without the applicable approval and exact-head gates.

Owner: UVAI Loop/Codex. This issue is a reversible planning/control correction, not a clean-image or production-remediation claim.