Note that the previous-day input must become L1C, not norm L1B

Per MAG review on imap_processing#3323, the processing side now takes
the previous day's L1C as the timeline source and rejects a previous-day
norm L1B; this config is a superseded placeholder until the past-day
delivery design (custom_behavior) lands.

Author: sapols

sds_data_manager/orchestration/dependencies/imap_mag_dependencies.yaml

@@ -149,7 +149,10 @@
       # NOTE: do not merge yet - the orchestration does not currently apply
       # date_range when selecting input files (needs custom_behavior support,
       # like hi.py), and the trigger sensor's range parser does not handle
-      # negative values like "-1d".
+      # negative values like "-1d". ALSO superseded: per MAG review the
+      # delivered input must be the previous day's L1C, not norm L1B
+      # (imap_processing PR 3323); this entry is a placeholder until the
+      # orchestration design lands.
       date_range: ["-1d", "0d"]
     - source: mag
       data_type: l1b
@@ -184,7 +187,10 @@
       # NOTE: do not merge yet - the orchestration does not currently apply
       # date_range when selecting input files (needs custom_behavior support,
       # like hi.py), and the trigger sensor's range parser does not handle
-      # negative values like "-1d".
+      # negative values like "-1d". ALSO superseded: per MAG review the
+      # delivered input must be the previous day's L1C, not norm L1B
+      # (imap_processing PR 3323); this entry is a placeholder until the
+      # orchestration design lands.
       date_range: ["-1d", "0d"]
     - source: mag
       data_type: l1b