chore(deps): update module github.com/mattn/go-isatty to v0.0.22

[red-hat-konflux]

This PR contains the following updates:

Package	Change	Age	Confidence
github.com/mattn/go-isatty	v0.0.20 → v0.0.22

---

Warning

Some dependencies could not be looked up. Check the warning logs for more information.

---

Release Notes

mattn/go-isatty (github.com/mattn/go-isatty)

v0.0.22

Compare Source

v0.0.21

Compare Source

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • At any time (no schedule defined)
• Automerge
  • At any time (no schedule defined)

🚦 Automerge: Disabled by config. Please merge this manually once you are satisfied.

♻ Rebasing: Whenever PR becomes conflicted, or you tick the rebase/retry checkbox.

🔕 Ignore: Close this PR and you won't be reminded about this update again.

---

• If you want to rebase/retry this PR, check this box

---

To execute skipped test pipelines write comment /ok-to-test.

---

Documentation

Find out how to configure dependency updates in MintMaker documentation or see all available configuration options in Renovate documentation.

[codecov-commenter]

Codecov Report

✅ All modified and coverable lines are covered by tests.
✅ Project coverage is 36.96%. Comparing base (794dda6) to head (de65649).

Additional details and impacted files

@@           Coverage Diff           @@
##             main     #200   +/-   ##
=======================================
  Coverage   36.96%   36.96%           
=======================================
  Files          23       23           
  Lines        1220     1220           
=======================================
  Hits          451      451           
  Misses        744      744           
  Partials       25       25           

Flag	Coverage Δ
e2e-tests	15.16% <ø> (ø)
unit-tests	31.96% <ø> (ø)

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

---

Continue to review full report in Codecov by Harness.

Legend - Click here to learn more
Δ = absolute <relative> (impact), ø = not affected, ? = missing data
Powered by Codecov. Last update 794dda6...de65649. Read the comment docs.

🚀 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 11:33 PM UTC · Completed 11:37 PM UTC
Commit: ec21706 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 2:35 AM UTC · Completed 2:41 AM UTC
Commit: ec21706 · View workflow run →

[fullsend-ai-review]

Looks good to me

Previous run

Looks good to me

Previous run (2)

Looks good to me

---

Labels: Automated dependency version bump by MintMaker bot.

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 1:32 AM UTC · Completed 1:35 AM UTC
Commit: ec21706 · View workflow run →

[fullsend-ai-retro]

Retro: PR #200 — Automated dependency bump (go-isatty v0.0.20 → v0.0.22)

This was a trivial, bot-authored dependency bump PR created by red-hat-konflux[bot] (MintMaker/Renovate). It modified only go.mod and go.sum (+3/−3 lines), was never merged, and was autoclosed repeatedly over 26 days by MintMaker's rebase logic.

Agent activity: The review agent ran once and approved it (correct verdict, but unnecessary work on a PR that was never going to be merged in its current form). The retro agent ran twice — once on 2026-06-24 (which already flagged this as "pure waste") and again now.

No human interaction occurred. No human reviewed or commented on this PR.

Waste analysis

All agent runs on this PR were wasted tokens:

• Review agent: Approved a PR that was autoclosed without merge. A skip guard for closed/autoclosing bot PRs would have prevented this.
• Retro agent (1st run): Correctly identified the waste pattern but the retro itself was unnecessary — there was no agent workflow to retrospect on.
• Retro agent (2nd run, current): Triggered by the final autoclose. Same waste pattern.

No new proposals — existing issues cover all improvements

The previous retro on this PR already identified the relevant upstream issues, and my search confirms extensive coverage in fullsend-ai/fullsend:

• Skip retro on bot PRs: #2461, #939, #1411, #1630
• Skip review on bot PRs: #1371, #1355, #1358
• Skip agents on closed PRs: #1870, #1439
• Deduplicate retro runs: #2401

All are open. No new proposals warranted.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 5:28 AM UTC · Completed 5:31 AM UTC
Commit: ec21706 · View workflow run →

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 1:44 AM UTC · Completed 1:48 AM UTC
Commit: ec21706 · View workflow run →

[fullsend-ai-retro]

Retro: PR #200 — Bot dependency bump with wasted agent cycles

PR #200 was a trivial go-isatty v0.0.20→v0.0.22 dependency bump by red-hat-konflux[bot] (MintMaker/Renovate). It was never merged — instead it went through 7 autoclose/reopen cycles over 31 days as MintMaker repeatedly rebased it. Each cycle triggered agent dispatches: 2 review agent runs and 3 retro agent runs (5 total), all on a +3/−3 line go.mod/go.sum change with zero human interaction.

This is pure waste — ~30 minutes of agent compute producing no value. The review agent approved a PR that kept getting autoclosed before anyone could merge it. The retro agent ran three times, each time correctly identifying the waste but compounding it by running again.

All improvements already tracked upstream

Every improvement opportunity identified here is already covered by open issues in fullsend-ai/fullsend:

• Skip retro on autoclosed bot PRs: #2461, #939, #1411, #1630
• Skip review on bot/closed PRs: #1371, #1870, #1439
• Deduplicate retro runs: #2401
• Lightweight review for trivial bot bumps: #1358, #1355
• Skip re-review after rebase with no semantic change: #1356

No new proposals are warranted — filing additional issues would create duplicates. The priority should be implementing the existing skip guards, particularly #2461 (retro on autoclosed bot PRs) and #1371 (review on bot PRs), which would have prevented all 5 wasted agent runs on this PR.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 4:40 AM UTC · Completed 4:44 AM UTC
Commit: ec21706 · View workflow run →