chore: sync generated content from apify-plugins

[apify-service-account]

Automated PR opened by the apify-plugins CI pipeline.

Source commit: apify/apify-plugins-internal@0bf81f12
Trigger: push to main
Workflow run: #35

This PR updates generated content (skills, rules, MCP config, manifests) with the latest build output. Files not produced by the build are left untouched.

⚠️ Overlay sync — files removed from the source build are not deleted here. If a generated file was renamed or removed upstream, please delete the orphaned copy manually before merging.

Please review the diff before merging.

[github-actions]

૮ >ﻌ< ა ci review

_{ran on d4d6493 — chore: sync generated content from apify-plugins (0bf81f12)}

❌ Job failures

Check contributors / check-attribution · View job

Job Check contributors / check-attribution failed.

---

⚠️ Action required

Unmapped contributor email(s) · View job

New contributor email(s) are not in AUTHOR_MAP.

apify-plugins-bot@users.noreply.github.com (apify-plugins-bot)

How to fix:

Run from the PR branch:

python3 scripts/audit_pr_attribution.py --fix
git add contributors && git commit -m "chore: map contributor emails" && git push

Or map one email manually (do NOT edit AUTHOR_MAP in release.py):

python3 scripts/add_contributor.py <email> <github-username>

To find the GitHub username for an email:

gh api 'search/users?q=EMAIL+in:email' --jq '.items[0].login'

---

⚠️ Warnings

OSV vulnerability scan · View job

76 known vulnerabilities found in pinned dependencies.

• CVE-2026-83608 in package-lock.json
• CVE-2026-83608 in package-lock.json
• CVE-2026-84375 in package-lock.json
• CVE-2026-84375 in website/package-lock.json
• CVE-2026-67213 in website/package-lock.json
• CVE-2026-85062 in package-lock.json
• CVE-2026-85062 in website/package-lock.json
• CVE-2026-83609 in package-lock.json
• CVE-2026-82417 in scripts/whatsapp-bridge/package-lock.json
• CVE-2026-82417 in website/package-lock.json
• CVE-2026-84369 in website/package-lock.json
• CVE-2026-83605 in package-lock.json
• CVE-2026-83605 in package-lock.json
• CVE-2026-75931 in package-lock.json
• CVE-2026-75931 in website/package-lock.json
• CVE-2026-83610 in package-lock.json
• CVE-2026-83610 in package-lock.json
• CVE-2026-83611 in package-lock.json
• CVE-2026-83611 in package-lock.json
• CVE-2026-71554 in uv.lock

How to fix:

Review the findings in the Security tab. Update the affected dependencies if a patched version is available.

---

debug info

CI timings

CI timings · View report · View job

Wall time 1440m23s vs 1440m17s (+0.0%). 10 job(s) slower, 2 faster, 3 unchanged.

• Docs Site / docs-site-checks: +68.0s
• OSV scan / Emit review status: +64.0s
• Python lints / Windows footguns (blocking): +24.0s
• OS-specific tests / macOS-only tests: +7.0s
• Detect affected areas: +6.0s