chore(deps): update dependency svelte-check to v4.7.3

[renovate-fullsend]

This PR contains the following updates:

Package	Change	Age	Confidence
svelte-check	4.7.2 → 4.7.3

---

Release Notes

sveltejs/language-tools (svelte-check)

v4.7.3

Compare Source

Patch Changes

• feat: zero-config +error.svelte props (#​3076)

---

Configuration

📅 Schedule: (UTC)

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

🚦 Automerge: Enabled.

♻ 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.

[github-actions]

Site preview

Preview: https://68a8bff8-site.fullsend-ai.workers.dev

Commit: 68e754fb4f70f21ff9d15f6e12d7bb6c254aedcd

[codecov]

Codecov Report

✅ All modified and coverable lines are covered by tests.

📢 Thoughts on this report? Let us know!

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 6:29 AM UTC · Completed 6:40 AM UTC
Commit: 68e754f · View workflow run →

[fullsend-ai-retro]

Retro: PR #5204 — Renovate lockfile bump (svelte-check v4.7.3)

Verdict: No novel improvements to propose. All identified waste is already extensively tracked.

What happened

PR #5204 was a trivial Renovate bot lockfile-only dependency update (svelte-check → v4.7.3). Only package-lock.json changed — the ^4.0.0 range in package.json already satisfied the new version.

Agent involvement: none

No triage, code, review, or fix agents were dispatched. The fullsend dispatch workflow ran 4 times across the PR lifecycle:

Run	Event	Outcome	Reason
1 (opened)	pull_request_target	Skipped	renovate-fullsend[bot] failed has_write_permission() — bot identities don't resolve via the collaborator API
2 (synchronize)	pull_request_target	Skipped	Same authorization failure
3 (review submitted)	pull_request_review	Skipped	Human approval (approved), not changes_requested — no fix agent trigger
4 (closed)	pull_request_target	Retro dispatched	closed action unconditionally routes to retro stage

A human reviewer (rh-hemartin) approved and merged the PR.

Waste analysis

This retro run (Opus model, 30-min timeout, subagent delegation) is analyzing a PR with zero agent involvement and no substantive code changes. There are no workflow interactions, no review findings, no rework cycles, and no autonomy gaps to assess. The entire retro compute is waste.

Why no proposals

The core issue — retro dispatched unconditionally on bot-authored PRs with no agent involvement — is already tracked across 10+ open issues:

• Skip retro agent for bot-authored trivial PRs with no agent interaction #3226, Skip or use lightweight retro analysis for bot-authored PRs #3317, Skip or fast-path retro stage for automerged bot dependency PRs #3647, Skip retro agent for automated bot dependency PRs #3833, Skip or early-exit retro for automated dependency update PRs #3951, Skip retro stage for automated dependency PRs (Renovate, Dependabot, MintMaker) #4006, Skip fullsend agent dispatch for bot-authored PRs #4154, Skip agent stages for auto-merge bot PRs to reduce wasted compute #4975, Skip fullsend agent pipeline for auto-merged bot dependency PRs #4989, Skip fullsend agent dispatch for bot dependency PRs #5067, Extend bot PR retro skip to use user.type detection instead of hardcoded bot list #5185, Evidence for fullsend#5185: retro dispatched on zero-agent-involvement bot digest PR #5220

Related issues also cover:

• Bot permission check failures in dispatch: Review agent skipped on bot-authored PRs due to collaborator permission check failing for GitHub App accounts #5188 (with fix PR fix(dispatch): distinguish permission-check failures from unauthorized skips #5219 in progress)
• Retro agent lacking valid GitHub API access: Retro agent receives invalid GH_TOKEN, cannot access GitHub API #5160, Retro agent sandbox blocks GitHub API access, preventing workflow analysis #5186, Retro agent sandbox lacks GitHub API access (proxy blocks api.github.com) #5037, Retro agent lacks GitHub API access and sufficient git history #4763

Filing new proposals would add to the existing duplicate pile without providing new signal. The priority action is implementing the bot-PR skip already proposed in the existing issues.