feat: adopt typed yt-dlp broker and reproducible CI

[mpiton]

Summary

• migrate all yt-dlp calls to the typed run_ytdlp host contract
• remove plugin-controlled binaries, arguments and timeout values
• add full WASM ABI smoke coverage and pinned reproducible CI
• use upstream Extism 1.30.0 and stop tracking the generated WASM binary

Validation

• 106 unit tests and 3 WASM smokes pass
• native and WASM Clippy pass with warnings denied
• release WASM build and cargo audit pass

Linear: MAT-129, MAT-131

---

Summary by cubic

Migrates all yt-dlp calls to the typed run_ytdlp broker to harden security and make behavior consistent across hosts. Adds WASM ABI smoke tests and reproducible, pinned CI (repinned reusable workflows); updates extism to 1.30.0; stops tracking the built WASM; and restricts releases to the repo owner. Linear: MAT-129, MAT-131.

• New Features

  • Switched to the typed run_ytdlp host API; the host now owns the binary, args, timeouts, env, and cwd.
  • Added WASM ABI smoke tests and reproducible CI with a pinned Rust toolchain; split verification and release workflows, pinned canonical reusable workflows by SHA (repinned), and limited tag releases to the repository owner.
  • Updated to extism 1.30.0 and removed the tracked vortex_mod_youtube.wasm.

• Migration

  • Requires Vortex host >= 0.2.0 (min_vortex_version updated).
  • Host must provide run_ytdlp and manage yt-dlp; install yt-dlp in a host-approved path.
  • Plugin install path updated to ~/.local/share/dev.vortex.app/plugins/... as shown in the README.

^{Written for commit 316dd53. Summary will update on new commits.}

[qodo-code-review]

Qodo reviews are paused for this user.

Troubleshooting steps vary by plan Learn more →

On a Teams plan?
Reviews resume once this user has a paid seat and their Git account is linked in Qodo.
Link Git account →

Using GitHub Enterprise Server, GitLab Self-Managed, or Bitbucket Data Center?
These require an Enterprise plan - Contact us
Contact us →

[coderabbitai]

Warning

Review limit reached

You’ve reached a temporary PR review limit under our Fair Usage Limits Policy.

Your recent review volume is higher than typical usage, so adaptive limits are currently applied.

Next review available in: 20 minutes

Enable usage-based reviews in Billing to review now. Otherwise, wait until the next included review is available.
You're only billed for reviews past your plan's rate limits ($0.25/file).

How can I continue?

After more reviews become available, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

To avoid repeated limits, reduce automatic review volume by pausing incremental auto-reviews earlier, using label-based review opt-in, excluding WIP or generated PR titles, or requesting reviews manually when the PR is ready. If your team needs uninterrupted high-volume reviews, an organization admin can enable usage-based reviews.

How do review limits work?

CodeRabbit enforces per-developer PR review limits for each organization. Most developers receive the normal plan review availability.

For paid Pro and Pro+ PR reviews, CodeRabbit uses adaptive limits for sustained high-volume activity. When a developer's recent PR review activity reaches the 95th percentile or higher among CodeRabbit users, additional reviews become available more gradually as earlier reviews age out of the rolling window.

Please refer docs for additional details.

Review details

⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 08d644b7-43dc-4eb3-856d-69d44f83a87b

📥 Commits

Reviewing files that changed from the base of the PR and between 4c53e7d and 316dd53.

⛔ Files ignored due to path filters (2)

• Cargo.lock is excluded by !**/*.lock
• vortex_mod_youtube.wasm is excluded by !**/*.wasm

📒 Files selected for processing (11)

• .github/workflows/plugin-ci.yml
• .gitignore
• CHANGELOG.md
• Cargo.toml
• README.md
• plugin.toml
• rust-toolchain.toml
• src/extractor.rs
• src/plugin_api.rs
• src/url_matcher.rs
• tests/wasm_smoke.rs

---

_{Comment @coderabbitai help to get the list of available commands.}

[socket-security]

Review the following changes in direct dependencies. Learn more about Socket for GitHub.

Diff	Package	Supply Chain Security	Vulnerability	Quality	Maintenance	License
	extism@​1.30.0

View full report

[socket-security]

Warning

Review the following alerts detected in dependencies.

According to your organization's Security Policy, it is recommended to resolve "Warn" alerts. Learn more about Socket for GitHub.

Action	Severity	Alert  (click "▶" to expand/collapse)
Warn		Obfuscated code: cargo im-rc is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/extism@1.30.0 → cargo/im-rc@15.1.0 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/im-rc@15.1.0. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: cargo libc is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/extism@1.30.0 → cargo/libc@0.2.186 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/libc@0.2.186. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: cargo writeable is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/extism@1.30.0 → cargo/writeable@0.6.3 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/writeable@0.6.3. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.
Warn		Obfuscated code: cargo zerocopy is 90.0% likely obfuscated Confidence: 0.90 Location: Package overview From: ? → cargo/extism@1.30.0 → cargo/zerocopy@0.8.54 ℹ Read more on: This package | This alert | What is obfuscated code? Next steps: Take a moment to review the security alert above. Review the linked package source code to understand the potential risk. Ensure the package is not malicious before proceeding. If you're unsure how to proceed, reach out to your security team or ask the Socket team for help at support@socket.dev. Suggestion: Packages should not obfuscate their code. Consider not using packages with obfuscated code. Mark the package as acceptable risk. To ignore this alert only in this pull request, reply with the comment @SocketSecurity ignore cargo/zerocopy@0.8.54. You can also ignore all packages with @SocketSecurity ignore-all. To ignore an alert for all future pull requests, use Socket's Dashboard to change the triage state of this alert.

View full report

[cubic-dev-ai]

No issues found across 13 files

_{Re-trigger cubic}