chore(deps): update dependency mermaid to v11.16.1

[renovate-fullsend]

This PR contains the following updates:

Package	Change	Age	Confidence
mermaid	11.16.0 → 11.16.1

---

Warning

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

---

Release Notes

mermaid-js/mermaid (mermaid)

v11.16.1

Compare Source

Patch Changes

• #​8022 12d472c Thanks @​aloisklink! - fix: handle CSS sibling combinators in compileCSS

• #​8022 2cd6dcf Thanks @​aloisklink! - fix: increase protections against prototype pollution

  User-controlled input already has protections against prototype pollution.

  Fixes: GHSA-c4c3-pg64-4m4v

• #​8022 99af3fc Thanks @​aloisklink! - fix(architecture): use Maps and Sets to store groups/services

  Services are now rendered in the order they are defined and more service IDs
  are now supported.

• #​8022 2cd6dcf Thanks @​aloisklink! - deprecate: Deprecate the mermaidAPI.setConfig() function

  Calling this function has no observable effect, as the next time a
  render() or parse() is called, the currentConfig is cleared.

• #​8022 630aa7e Thanks @​aloisklink! - fix(xychart): support zero-width x-axis ranges

• #​8022 59b22fa Thanks @​aloisklink! - fix(radar): limit number of ticks to 32

  Setting a ticks value higher than this would only show 32 ticks.

---

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 these updates 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:19 AM UTC · Completed 4:25 AM UTC
Commit: c078111 · View workflow run →

[github-actions]

Site preview

Preview: https://3b8b5f51-site.fullsend-ai.workers.dev

Commit: c078111bc88db9c8aa84b8e3bb5fe318dcb0384b

[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

[fullsend-ai-retro]

🤖 Finished Retro · ✅ Success · Started 8:01 AM UTC · Completed 8:14 AM UTC
Commit: c078111 · View workflow run →

[fullsend-ai-retro]

Retro: PR #5963 — Renovate mermaid 11.16.0 → 11.16.1 lockfile update

This was a routine Renovate bot lockfile-only patch update (2 files, 7+/7−). The workflow completed without rework:

1. 04:18 UTC — Renovate opened PR, auto-merge enabled
2. 04:25 UTC — Review agent approved in ~7 min ($1.16, Opus-tier correctness sub-agent). Correctly classified as mechanical/value-only, applied trivial scope, zero findings.
3. 04:25 UTC — CI passed, ready-for-merge label applied
4. 04:25–07:52 UTC — 3h 27m idle, waiting for human CODEOWNERS approval (* @fullsend-ai/core wildcard requires team member review the bot can't satisfy)
5. 07:52 UTC — Human reviewer approved (no comments)
6. 07:59 UTC — Merged via merge queue

Assessment

Review quality: Appropriate. The agent correctly triaged the lockfile-only change, dispatched only correctness + style-conventions sub-agents at trivial scope, and approved quickly.

Rework rate: Zero iterations — ideal.

Time to resolution: The 3h 27m human-review wait was the sole bottleneck. The review agent, CI, and Renovate auto-merge were all ready within 7 minutes of PR creation.

Token cost: $1.16 for reviewing a lockfile-only patch is non-trivial. The correctness sub-agent ran at Opus tier. Additionally, this retro itself is consuming compute on a trivially-handled bot PR.

Autonomy readiness: The human reviewer's approval aligned with the agent's verdict. This is consistent with the pattern documented in 28+ existing autonomy-readiness tracking issues.

No new proposals — existing issues cover all improvement areas

Every improvement opportunity identified is already tracked:

• Consider auto-merge for low-risk Renovate patch/minor devDependency updates where CI passes #3016, Support approving dependency update PRs to enable renovate auto-merge with merge queues #691, Dependency bot PR triage and merge automation #336 — Auto-merge for low-risk Renovate patches blocked by CODEOWNERS/branch protection. This PR is another data point: a lockfile-only patch waited 3.5 hours for a human approval that added no delta to the agent's review.
• Review agent: use cheaper model for trivial bot-authored PRs #2842, Review model routing should use diff complexity, not just author type #5777 — Using a cheaper model for trivial bot PRs. The $1.16 cost (Opus-tier correctness sub-agent) on a lockfile-only change is evidence these optimizations would yield savings.
• agents Review bot extraneous messages and minimal usefulness #649, Collect OpenShell sandbox logs into the run output directory #276, fix: add contents:read to dispatch token for private .fullsend repos #349 — Pre-retro early-exit for trivially-handled bot PRs. None are implemented; pre-retro.sh currently only validates input format. This retro run is itself evidence of the cost described in those issues.
• Skip agent stages for auto-merge bot PRs to reduce wasted compute #4975, Skip review and retro stages for bot-authored dependency update PRs #5360, Skip fullsend agent dispatch for bot dependency PRs #5067 — Skipping the full agent pipeline for bot dependency PRs. This PR's minimal review footprint (zero findings, trivial scope) supports the case.
• pr-review skill: reduce sub-agent dispatch for mechanical/value-only changes like dependency bumps #4060 — Reducing sub-agent dispatch for mechanical/value-only changes in the pr-review skill.