[2026-05-23] taiga sync: family/logs/vault-sync-2026-05-22.md wiki/SCHEMA.md wiki/concepts/vault-agent-integration.md wiki/htpc-bazzite-proton.md wiki/index.md

2026-05-23 00:00:49 +00:00
parent 6dc4b89d49
commit 3a44a55ee0
19 changed files with 44 additions and 791 deletions
@@ -1,34 +0,0 @@
---
-title: Media Pipeline Pitfalls
-created: '2026-05-23'
-updated: '2026-05-23'
-type: tech
-namespace: family
-tags: [media-pipeline, pitfalls, torrents, infra]
-related: "[[arr-stack-kraken]]"
---
-
-# Media Pipeline Pitfalls
-
-## Torrents — Do Not Rename Files
-
-Never rename torrent source files or folders while a torrent is active.
-Transmission tracks files by path. Renaming breaks the association and
-causes re-download or stalled seeding.
-
-## torrent-set-location Updates downloadDir
-
-`torrent-set-location` in the Transmission RPC updates `downloadDir` in
-the torrent metadata. Use this when moving completed files, not a manual
-rename. Sequence:
-
-1. Move files to new location on disk
-2. Call `torrent-set-location` with the new path + `move=false`
-3. Verify torrent goes back to seeding state
-
-## General Rules
-
- Never touch source files/folders (media-pipeline USER.md rule)
- `resolve-manual` is emergency-only
- NFO files: do not create manually; let the pipeline handle them
- Never delete test files from the pipeline project