fix: remove bind-propagation=shared from mount instructions

runc v1.3.5 (Docker 29.x / Unraid 7.3+) rejects bind-propagation=shared
on symlink sources with: open /proc/self/mountinfo: no such file or directory.
The ramdisk tmpfs is already MS_SHARED at the kernel level — propagation is
inherited automatically and does not need to be specified in Docker.

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

user_script_plug-in.sh

@@ -209,8 +209,9 @@
 #   Show active Emby sessions with play method. Write daily stats to TRANSCODE_DAILY_LOG.
 #
 # NOTE: Emby Extra Parameters MUST include:
-#   --mount type=bind,source=/mnt/ram-transcode,target=/ext-ram-transcode,bind-propagation=shared
-#   Without shared propagation, symlink flips are silently ignored after the first flip.
+#   --mount type=bind,source=/mnt/ram-transcode,target=/ext-ram-transcode
+#   Do NOT add bind-propagation=shared — runc v1.3.5+ (Docker 29.x, Unraid 7.3+) rejects it.
+#   The ramdisk mount is already shared at the kernel level (MS_SHARED) — propagation is automatic.
 #
 # bash /boot/config/plugins/varaverk/Orchestrators/transcode_management.sh
 
@@ -1058,8 +1059,9 @@
 #   TRANSCODE_LINK symlink → RAMDISK_PATH (always reset to ramdisk at array start)
 #
 # IMPORTANT: Emby Extra Parameters must include:
-#   --mount type=bind,source=/mnt/ram-transcode,target=/ext-ram-transcode,bind-propagation=shared
-#   Without shared propagation: symlink flips silently ignored after first flip (rprivate locks inode).
+#   --mount type=bind,source=/mnt/ram-transcode,target=/ext-ram-transcode
+#   Do NOT add bind-propagation=shared — runc v1.3.5+ (Docker 29.x, Unraid 7.3+) rejects it.
+#   The ramdisk mount is already shared at the kernel level (MS_SHARED) — propagation is automatic.
 #
 # Verify setup:
 #   mountpoint /mnt/ramdisk_transcodes     should say "is a mountpoint"