chore(deps): update stripe/agent-toolkit digest to ea6997c

[renovate]

This PR contains the following updates:

Package	Update	Change
stripe/agent-toolkit	digest	da4991b → ea6997c

---

Configuration

📅 Schedule: (UTC)

• Branch creation
  • Between 12:00 AM and 03:59 AM, only on Monday (* 0-3 * * 1)
• 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

---

This PR was generated by Mend Renovate. View the repository job log.

[toolhive-release-app]

🛡️ Skill Security Scan Results

❌ stripe-best-practices

• Status: Failed
• Findings: 3
• Blocking: 1

Blocking issues:

• [LLM_PROMPT_INJECTION] (HIGH) The Billing reference instructs the agent to retrieve and read a remote SKILL.md from docs.stripe.com when the local metronome skill is not installed, then continue implementation. A remotely fetched skill manifest is untrusted external content and may contain instruction-like text. Treating it as authoritative creates an indirect prompt-injection path if the remote resource is compromised, modified, redirected, or otherwise serves malicious instructions. (references/billing.md)

✅ stripe-projects

• Status: Passed
• Findings: 6

✅ upgrade-stripe

• Status: Passed
• Findings: 3
• Allowed (not blocking): 1
  • MANIFEST_MISSING_LICENSE (Allowed: stripe/agent-toolkit is licensed MIT at the repository root; upstream does not embed an SPDX license identifier in per-skill SKILL.md frontmatter.)

---

Summary: Completed 3 of 3 skill scan(s), found 1 blocking issue(s).

⚠️ Action Required: Review the failed scan jobs and any blocking findings. Add a justified entry to the skill's security.allowed_issues[] only when a finding is a confirmed false positive.

[renovate]

Edited/Blocked Notification

Renovate will not automatically rebase this PR, because it does not recognize the last commit author and assumes somebody else may have edited the PR.

You can manually request rebase by checking the rebase/retry box above.

⚠️ Warning: custom changes will be lost.