Non-Blocking Review Concern: TR_TORRENT_FILES format varies across pipeline layers without consolidated documentation
Source: claude (automated reviewer)
Location: app-setup/templates/transmission-done.sh (header area)
PR: #113 — fix(transmission-filebot): replace find(1) with NFS-safe alternatives (#113)
Date: 2026-04-05
What was flagged
TR_TORRENT_FILES carries three distinct formats across the pipeline: pipe-separated relative paths in the trigger file, newline-separated absolute paths from the watcher, and the done script consumes the newline form. Each hop is commented individually but a single consolidated note in transmission-done.sh's header would help future maintainers avoid tracing all three files.
Context
This issue was automatically created from a non-blocking concern identified
during pre-merge review of PR #113. It was safe to merge but worth tracking.
Created by lib-review-issues.sh
Non-Blocking Review Concern: TR_TORRENT_FILES format varies across pipeline layers without consolidated documentation
Source: claude (automated reviewer)
Location:
app-setup/templates/transmission-done.sh (header area)PR: #113 — fix(transmission-filebot): replace find(1) with NFS-safe alternatives (#113)
Date: 2026-04-05
What was flagged
TR_TORRENT_FILES carries three distinct formats across the pipeline: pipe-separated relative paths in the trigger file, newline-separated absolute paths from the watcher, and the done script consumes the newline form. Each hop is commented individually but a single consolidated note in
transmission-done.sh's header would help future maintainers avoid tracing all three files.Context
This issue was automatically created from a non-blocking concern identified
during pre-merge review of PR #113. It was safe to merge but worth tracking.
Created by lib-review-issues.sh