Docs drift - updates needed for the next Maintainerr release #189

📚 Docs drift report

Comparing origin/main → HEAD against Maintainerr_docs. Informational only - maintainers decide what needs doc updates before release.

Rule glossary parity

• Code rule keys (rules.constants.ts): 225
• Documented keys (docs/Glossary.md): 225

Glossary is in sync with the code.

New migrations on this branch

No new migrations.

Rule constants

No changes to rules.constants.ts.

Public contracts (@maintainerr/contracts)

No contract changes.

New HTTP controllers

No new controllers.

feat: commits on this branch

• fd5ab8d5 feat(download-client): remove downloads that seeded 14 days at any ratio (#4066)
• ef5396b1 feat(rules): show media server ID and path in *arr not-tracked warnings (#4065)
• ddb7a8d0 feat(i18n): add Russian and Traditional Chinese (#4064)

Behavioral fixes worth reviewing

• e0002e47 fix(plex): revoke the token at plex.tv when clearing credentials (#4038)
  • touched: apps/server/src/modules/api/lib/plextvApi.spec.ts, apps/server/src/modules/api/lib/plextvApi.ts, apps/server/src/modules/api/plex-api/plex-api.service.spec.ts, apps/server/src/modules/api/plex-api/plex-api.service.ts, apps/server/src/modules/settings/settings-operations.service.spec.ts, apps/server/src/modules/settings/settings-operations.service.ts
• c65dd120 fix(plex): apply saved connection settings without a restart (#4069)
  • touched: apps/server/src/modules/api/plex-api/plex-api.service.spec.ts, apps/server/src/modules/api/plex-api/plex-api.service.ts, apps/server/src/modules/rules/rule-users.service.spec.ts, apps/server/src/modules/rules/rule-users.service.ts, apps/server/src/modules/settings/media-server-switch.service.ts, apps/server/src/modules/settings/settings-operations.service.spec.ts, apps/server/src/modules/settings/settings-operations.service.ts
• 5b5dbd1d fix(emby): show the size of show and season collections (#4067)
  • touched: apps/server/src/modules/api/media-server/emby/emby-adapter.service.spec.ts, apps/server/src/modules/api/media-server/emby/emby-adapter.service.ts
• c4346709 fix(storage-metrics): count a ZFS pool's free space once (#4068)
  • touched: apps/server/src/modules/storage-metrics/storage-metrics.service.spec.ts, apps/server/src/modules/storage-metrics/storage-metrics.service.ts

fix: commits that touched a doc-worthy surface - the UI, any server module except internal-only events/logging, any controller, or the README. Worth scanning to decide whether observable behavior changed enough to warrant a docs note.

Documentation-labeled issues & PRs

No open issues or in-range merged PRs carry the documentation label.

🤖 Guidance for Copilot opening the docs PR

Open a PR on Maintainerr_docs that addresses this drift report, following these rules:

• Always work from local clones, not github.com web views (they can be cached or truncated).
  Clone Maintainerr/Maintainerr and Maintainerr/Maintainerr_docs before anything else.
• Read complete files, not excerpts or partial reads. Coverage you would otherwise miss often
  sits past the first screenful - read each doc file and each commit diff end-to-end.
• Source of truth: the upstream Maintainerr commits and file diffs listed above.
  Use the prose summary as guidance, but always confirm against the local clone
  (git show <sha>) before editing.
• Skip what's already documented: read the current main branch of Maintainerr_docs
  and the most recent merged docs PRs first. If something is already covered, do not
  re-document it.
• Minimal edits only: make only the doc updates that are still missing for the Next
  release. No speculative additions, no broad rewrites.
• Doc-only changes: restrict edits to files under docs/ and static/openapi-spec/.
  Do not touch sidebars, config, or unrelated assets unless strictly required by a doc edit.
• PR description structure:
  1. What was added - one short bullet per doc edit, citing the upstream commit or PR.
  2. Already covered by prior PRs - list anything from this drift that earlier merged
     docs PRs already documented, so reviewers can confirm it's intentionally skipped.
• Keep the PR focused and tied to the actual code diff rather than the issue summary alone.