[bakerboy448]

TLDR

• New "TRaSH Sync Requirements" section on the client After Install page: apps and versions, schedule, timer vs manual runs, where results show.
• Sonarr page: TRaSH sync on Sonarr v5 needs the unstable client for now (0.9.8 uses /api/v5).
• Starr Proxy page: the key needs write methods, including the v5 bulk PUT /api/v5/qualitydefinition and PUT /api/v5/settings/naming. A GET-only key returns 405 on every write.

Limits

• Client screenshots follow in a second commit.
• Avoids trash.md and commands.md, open in docs: add Sportarr, Tracearr, and Watchsync pages; fix four pages against source #72 and docs(client): add Shield remote and Linux ops command examples #71.

Sources

• Sonarr v3 CF skip: website classes/traits/trash/customFormats.php:329
• Lidarr trigger 501: client pkg/triggers/handler.go:130
• Sync time written every run: website sync.php:241-246
• Discord-only failures behind toggles: website sync.php:472,720, customFormats.php:664
• Sonarr v5 on unstable 0.9.8: client-triggered rpsync read both Sonarrs over /api/v5 and PUT /api/v5/qualitydefinition returned 200 (beta test, 2026-10-29)
• Proxy template methods: starrproxy templates/sonarr/notifiarr.json, v5 PUT fix in fix: allow notifiarr PUT on Sonarr v5 qualitydefinition and settings/naming starrproxy#128

🤖 Generated with Claude Code