chore(deps): update dependency eslint-plugin-svelte to v3.22.0

[renovate-fullsend]

This PR contains the following updates:

Package	Change	Age	Confidence
eslint-plugin-svelte (source)	3.20.0 → 3.22.0

---

Warning

Some dependencies could not be looked up. Check the Dependency Dashboard for more information.

---

Release Notes

sveltejs/eslint-plugin-svelte (eslint-plugin-svelte)

v3.22.0

Compare Source

Minor Changes

• #​1563 cdad05a Thanks @​baseballyama! - feat: add no-conflicting-module-names rule

v3.21.0

Compare Source

Minor Changes

• #​1559 4138a57 Thanks @​knrdl! - feat: add no-bind-value-on-checkable-inputs rule

---

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 is behind base branch, 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

---

This PR has been generated by Mend Renovate.

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 4:21 AM UTC · Completed 4:26 AM UTC
Commit: d262c1b · View workflow run →

[github-actions]

Site preview

Preview: https://cd39c6eb-site.fullsend-ai.workers.dev

Commit: 762494bf7fae98013d73c3a515a4dc0c4942585b

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-review]

Looks good to me

Previous run

Looks good to me

---

Labels: Renovate bot dependency update modifying only package-lock.json

Previous run (2)

Looks good to me

Previous run (3)

Looks good to me

Previous run (4)

Looks good to me

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:38 PM UTC · Completed 3:44 PM UTC
Commit: 9dc7e93 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 4:22 AM UTC · Completed 4:29 AM UTC
Commit: 426dc58 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 3:38 PM UTC · Completed 3:44 PM UTC
Commit: 0a79203 · View workflow run →

[fullsend-ai-review]

🤖 Finished Review · ✅ Success · Started 4:25 AM UTC · Completed 4:31 AM UTC
Commit: 762494b · View workflow run →

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 8:20 AM UTC · Completed 8:35 AM UTC
Commit: 762494b · View workflow run →

[fullsend-ai-retro]

Retro: PR #5809 — Renovate lockfile bump reviewed 5 times

PR #5809 is a trivial Renovate bot dependency update bumping eslint-plugin-svelte from 3.20.0 to 3.22.0 in package-lock.json only (3 additions, 3 deletions, 1 file changed). Renovate rebased the branch 4 times over 2.5 days to stay current with main, and each rebase triggered a full review dispatch — 5 review runs total, each taking ~5–7 minutes and reaching the same "Looks good to me" verdict. Human reviewer rh-hemartin approved without comments and merged on 2026-08-03.

Workflow timeline

1. 2026-08-01 04:21 — Renovate opens PR. Review run 1 (~5m 36s) correctly classifies the change as "mechanical / value-only," skips 4 of 6 sub-agents, constrains the remaining 2 to trivial scope. Approves and labels ready-for-merge.
2. 2026-08-01 15:37 — Rebase docs: Add agent-compatible code problem document #1. Review run 2 (~6m 49s). Same verdict.
3. 2026-08-02 04:22 — Rebase Add problem areas: Tekton pipeline review, migration path, multi-tenancy #2. Review run 3. Same verdict.
4. 2026-08-02 15:38 — Rebase docs: Add codebase context problem document and trim CLAUDE.md #3. Review run 4. Same verdict.
5. 2026-08-03 04:24 — Rebase Use AI to help formalise intent after rapid local prototyping #4. Review run 5 (~6m 57s). Finds prior review context but the re-review override forces correctness sub-agent to full scope despite the change being trivially identical. Same verdict.
6. 2026-08-03 08:10 — Human approves and merges. Retro dispatched.

Assessment

The review agent's per-run behavior was reasonable — it correctly identified the change as mechanical and minimized sub-agent dispatch. The waste comes from the dispatch layer: every Renovate rebase triggers a full review pipeline with no diff-equivalence check, and the re-review override paradoxically increases effort on subsequent runs of unchanged content.

Total waste: ~4 redundant review runs (~25 minutes compute). This retro itself is also arguably unnecessary for a lockfile-only bot PR.

Evidence for existing issues (no new proposals)

All improvement opportunities are covered by existing open issues. This PR adds another data point:

• Review agent should avoid full re-reviews when Renovate rebases without content changes #4596, Review agent should detect rebase-only force-pushes and skip re-review when the effective diff is unchanged #4401, Skip redundant re-reviews when Renovate rebases a dependency PR without changing the diff #4652 (skip re-review on unchanged rebases): 4 redundant re-reviews on rebase-only force-pushes where the effective diff was identical each time.
• Skip review and retro stages for bot-authored dependency update PRs #5360, Consider fast-path for review agent on single-file bot dependency PRs #3347, Add lightweight review path for trivial bot dependency bumps #1358, pr-review skill: reduce sub-agent dispatch for mechanical/value-only changes like dependency bumps #4060 (skip/fast-path reviews for bot dependency PRs): The review agent's internal triage was efficient (skipped 4/6 sub-agents, trivial scope), but the dispatch layer still spun up a full runner, checked out the repo, minted tokens, and ran the harness for each of 5 runs.
• Skip retro agent for automated bot dependency PRs #3833, Skip retro stage for automated dependency PRs (Renovate, Dependabot, MintMaker) #4006 (skip retro for bot dependency PRs): This retro run is itself an example of unnecessary compute on a trivial bot PR.
• Consolidate 22+ overlapping "skip retro/agent dispatch" issues into a single design issue #5817 (consolidation meta-issue): Notes 22+ overlapping issues in this space. This PR is further evidence that the consolidation and implementation should be prioritized.

The workflow went well within the constraints of the current system. No new proposals are warranted — the existing issue backlog comprehensively covers every improvement opportunity identified.