Orchestrators echo/log audit pass

Status conclusions, clean-cycle summaries, skipped-feature lines, and phase
completion results → echo across all nine orchestrator scripts. Per-share,
per-job, and per-script detail lines inside loops remain log. README-Orchestrators:
added Output Tiers section.

Orchestrators/README-Orchestrators.md

@@ -142,6 +142,26 @@ Single notification  → one bell per run, not one per job
 
 ---
 
+## ━━━ OUTPUT TIERS ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
+
+All scripts use a two-tier output model: `echo` lines are always visible; `log`
+lines only appear when `--log` is passed.
+
+**One-shot orchestrators** (`array_started.sh`, `array_stopping.sh`, `sunday_morning_coffee_report.sh`):
+without `--log`, section headers, per-phase results, and the final summary are
+visible. Per-item detail suppressed.
+
+**Periodic orchestrators** (`critical_sync_maintenance.sh`, `daily_sync_maintenance.sh`,
+`intermediate_sync_maintenance.sh`, `weekly_sync_maintenance.sh`): without `--log`,
+phase headers, per-phase completion status, and the final summary are visible. Per-share
+and per-job detail suppressed.
+
+**Daemon orchestrators** (`watchdog_orchestrator.sh`, `transcode_management.sh`): silent
+during clean cycles. Only state transitions, errors, and startup-grace expiry shown
+without `--log`.
+
+---
+
 ## ━━━ SCRIPTS AT A GLANCE ━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━━
 
 | Script | What It Orchestrates | Schedule |