chore(deps): Update ubi-minimal base image (release-v0.8)

[st3penta]

Update ubi-minimal base image to latest digest.

Old digest: sha256:8ebe2ad8fdf3cab3e5a53c1edc69194c98209cfadab24b884f4ad9ebcf7bbbfc
New digest: sha256:beeada7dd17903dfb69fd5f6916c054720bf28a52daaa2f7a1910a1394244bd2

RPM changes

- libxml2-2.9.13-14.el9_8.4
+ libxml2-2.9.13-14.el9_8.5

Co-Authored-By: gpt-6-luna noreply@openai.com

[coderabbitai]

Important

Review skipped

Auto reviews are disabled on base/target branches other than the default branch.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Enterprise

Run ID: acae5d63-36bd-4c42-895d-dcf9c1c46825

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.

Use the checkbox below for a quick retry:

• 🔍 Trigger review

---

_{Comment @coderabbitai help to get the list of available commands.}

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 10:55 AM UTC · Completed 11:03 AM UTC

Commit: 1d0cff6 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $2.75

[fullsend-ai-review]

Risk Assessment: moderate (2/5)

Details

Routine UBI minimal base image digest update (libxml2 security patch) with a 4-line XS diff from an established contributor; CI-influencing files and 2 protected-path matches keep the score at moderate rather than low, while zero fix/revert history contains the risk.

[fullsend-ai-review]

Review

Findings

High

• [protected-path] Dockerfile and Dockerfile.dist — Both changed files match a governance-protected path prefix (Dockerfile) in the review configuration, and the PR is not linked to a tracking issue. The PR body explains the change (routine ubi-minimal digest bump for the RHSA-2026-71585 / libxml2 errata), but under the protected-path policy the description alone is not sufficient authorization: a linked issue or ADR is required so that infrastructure changes remain auditable.
  Remediation: Link this PR to a tracking issue (or a standing errata/base-image-bump policy issue) that explicitly authorizes routine RHSA-driven digest bumps to Dockerfile and Dockerfile.dist. Alternatively, if these routine bumps should not require per-PR authorization, narrow REVIEW_PROTECTED_PATHS to exclude Dockerfile (or move the entries under a directory prefix that does not match root-level Dockerfiles). Either way, human review is still required for protected-path modifications.

Notes

• Change scope: pure value-only base image digest bump on release-v0.8; both files receive the identical new digest (sha256:beeada7d...44bd2).
• Composite risk: moderate (2/5) — routine mechanical maintenance from an established contributor; the score is anchored by protected-path count (2) and CI-influencing files, tempered by zero fix/revert history on the touched files.
• Correctness, security, and style-conventions sub-agents returned no findings; both digests are well-formed 64-hex sha256: values and follow the surrounding pinning pattern exactly.

---

Next steps:

• /fs-fix — agent addresses review findings automatically
• /fs-fix <your instruction> — agent fixes with your specific guidance
• Push commits directly — review re-runs automatically on push
• /fs-fix-stop — disable automatic fix runs for this PR

[fullsend-ai-review]

See the review comment for full details.

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

Flag	Coverage Δ
acceptance	54.86% <ø> (ø)
generative	18.14% <ø> (ø)
integration	26.99% <ø> (ø)
unit	68.66% <ø> (ø)

Flags with carried forward coverage won't be shown. Click here to find out more.

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 1:35 PM UTC · Completed 1:39 PM UTC

Commit: 1d0cff6 · View workflow run →

Runtime: claude · Model: opus → claude-opus-4-7 · Effort: high · Cost: $1.21

[fullsend-ai-retro]

Retro summary — PR fullsend-ai/fullsend#3589 (release-v0.8 ubi-minimal digest bump)

Outcome: Merged cleanly in ~2h 41m with zero rework. Two human contributors (dheerajodha, cuipinghuo) approved the 4-line pure-value digest bump without comment; the review agent's Correctness / Security / Style sub-agents returned no findings. Codecov confirmed all modified/coverable lines are covered.

Only friction: The review agent surfaced a High-severity [protected-path] finding on Dockerfile and Dockerfile.dist, asking for a linked authorizing issue despite the PR body citing the Red Hat errata (sha256:beeada7d..., libxml2-2.9.13-14.el9_8.4 → .5). Humans merged without addressing it. This is a consistent pattern — the three simultaneous sibling PRs from the same RHSA event were flagged identically: #3587 (main, High), #3588 (release-v0.7, Medium), #3590 (release-v0.9, Medium). Every one merged without remediation. Earlier bump cohorts (#3578-#3581, fullsend-ai/fullsend#3568-#3571) show the same shape going back weeks.

No proposals filed — the theme is already tracked. The retro-analysis skill's "Before proposing" check surfaced extensive prior work on exactly this finding class:

• Open, directly on-point: fullsend-ai/fullsend#3675 (FROM-line Dockerfile digest-pinning agent-approval), #3061 (digest-only trusted-bot severity), #3239 (change-type-aware exemptions), #7611, #3164, #2588, #5370, #1551 (human-authored severity).
• Open in agents repo (closer to the actual finding text): fullsend-ai/agents#741 (semantic-significance assessment), #718 (external tracker references as authorization — matches this PR's RHSA-2026-71585 citation), #735 (PR body rationale as authorization context).
• Repo-side companion already open: conforma/cli#3502 (AGENTS.md guidance for UBI bumps) — note maintainer skepticism in the discussion that repo-side documentation is the right layer for this fix.
• Closed not-planned in the last 90d: fullsend-ai/fullsend#4387, #3910 — blanket bot digest-bump exemptions were explicitly rejected, which constrains the design space for any new proposal.

New evidence this run adds to the existing tracker cluster (for anyone triaging fullsend-ai/fullsend#3675 / fullsend-ai/fullsend#718 / fullsend-ai/fullsend#735): the finding recurs on human-authored PRs too, not just Renovate/bot cases. PR fullsend-ai/fullsend#3589's author is a human contributor with a Codex co-author; the PR body includes both the RHSA reference and the RPM-level diff, yet the agent still fires High severity for lack of a linked issue. Any exemption design that keys on "trusted bot author" alone would miss this recurring class.

Autonomy-readiness signal (already tracked): across at least 6 recent PRs in this cohort, the review agent's non-governance sub-agents matched human review (both returned zero substantive findings and humans approved without comment). This is the same 100%-match pattern captured by fullsend-ai/fullsend#4962 and #4817; no new autonomy-readiness proposal filed here to avoid duplication.

Cost note (not proposal-worthy on its own): the review ran at opus / high effort for $2.75 on a 4-line pure-value diff, and the RHSA event triggered four near-identical reviews (~$11 combined). If any of the open protected-path calibration issues land, effort routing for verified-mechanical bumps should benefit automatically; no separate action needed.

Agents repo discovered from run log: fullsend-ai/agents@main (SHA a526fa38). Localization guidance applied when scanning for prior issues.