chore(submodules): promote PMOVES-Jellyfin gitlink to upstream-synced HEAD

[POWERFULMOVES]

Why

Completes the Jellyfin fork-staleness fix (PMOVES.AI #8). PMOVES-Jellyfin#3 synced PMOVES.AI-Edition-Hardened from 1258 commits behind jellyfin/jellyfin:master to current — conflict-free, with the additive PMOVES hardening overlay preserved (build + tests on macOS/Ubuntu/Windows green; structural ABI-Difference/Base Artifact reds are inherent to syncing a stale base and self-heal now that the base is current).

What

Promote the PMOVES-Jellyfin submodule gitlink: ecdfad9e → 6933bb39.

• Clean fast-forward: gh api .../compare/ecdfad9e...6933bb39 → status: ahead, 1260 ahead / 0 behind.
• Single-file gitlink change; .gitmodules unchanged (still tracks PMOVES.AI-Edition-Hardened).
• CI gate: submodule-gitlink-gate / submodule-smoke.

Effect

Puts the Jellyfin media stack on a current, CVE-patched base and unblocks the Jellyfin secret rotation (JELLYFIN_API_KEY) + media-over-Tailscale lane.

Follow-ups (separate, non-blocking)

• Operator: enable the fork's Security policy (Dependabot/secret-scanning).
• Fork-CI hygiene: OpenAPI - HEAD upload-path mismatch in upstream's inherited workflow (artifact path; not a code defect — build/tests pass).

🤖 Generated with Claude Code

[coderabbitai]

Warning

Review limit reached

@POWERFULMOVES, we couldn't start this review because you've reached your PR review rate limit.

More reviews will be available in 29 minutes and 8 seconds. Learn how PR review limits work.

Your organization has used up its prepaid credits, and credit purchases are no longer available. Enable the review add-on in the billing tab to keep reviews running — you're only billed for reviews past your plan's rate limits ($0.25/file).

⌛ How to resolve this issue?

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

🚦 How do rate limits work?

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

For paid Pro and Pro+ PR reviews, CodeRabbit uses rolling per-developer review limits. Reviews become available again as older review attempts age out of the rolling limit window.

Please see our Fair Usage Limits Policy for further information.

ℹ️ Review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Pro

Run ID: 3bc260be-2e10-463b-b42f-60addd4d1061

📥 Commits

Reviewing files that changed from the base of the PR and between 8668e96 and 86122e9.

📒 Files selected for processing (1)

• PMOVES-Jellyfin

✨ Finishing Touches

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Commit unit tests in branch chore/promote-jellyfin-gitlink

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

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