[mfederowicz]

Trakt's contract added an optional personalized query param to movies/:id/related and shows/:id/related (trakt/trakt-api 090d333): VIP accounts get the related titles re-ordered toward their taste, everyone else is ignored.

Added

• movies -a related and shows -a related take -personalized, sent as personalized=true; without the flag nothing extra is sent.
• Library: uri.ListOptions.Personalized and str.Options.Personalized (new fields, non-breaking; service signatures unchanged).
• Docs examples in docs/movies.md and docs/shows.md.

Tests

• Service: both related routes send personalized=true when set.
• Handlers: the param is sent only with the flag.
• Commands: the flag reaches the options in both modules and stays false when not given.

Live check (2026-11-04, non-VIP account)

• movies -a related -i tron-legacy-2010: 45 items, same order with and without the flag.
• shows -a related -i the-sopranos: 50 items, same order with and without the flag.
• Trakt accepts the param and ignores it for non-VIP, as documented; the VIP re-ordering is mock-tested only.

AI (Claude Code) wrote the change, tests, docs, CHANGELOG entry and the live-check script; I ran the live check.