docs(mappers): time no longer dates detection

Eight mappers (Cortex XDR, CrowdStrike, Rapid7) still called the OCSF
`time` field "the MTTD anchor" that Riposte reads to stamp detected_at.
Riposte retired MTTD in migration 0256 and stamps detection at
ingestion for every alert; the mappings stay, as the alert's own record
of when the source saw the event. Comments only: no mapping changes.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

integrations/cortex-xdr/mappers/get_alerts.yaml

@@ -23,11 +23,12 @@ ocsf:
   - { source_path: "alert_category",       ocsf_field: "finding_info.analytic.category" }
   - { source_path: "alert_name",           ocsf_field: "finding_info.analytic.name" }
   - { source_path: "matching_service_rule_id", ocsf_field: "finding_info.analytic.uid" }
-  # ── Detection time: the MTTD anchor ───────────────────────────────
-  # `time` is what Riposte measures detection-to-ingestion against. The grid
-  # exposes when the tenant took the alert in (source_insert_ts); a sensor-side
-  # detection timestamp, when the tenant sends one, is the better anchor and
-  # comes last so it wins.
+  # ── Event time (OCSF `time`) ───────────────────────────────────────
+  # Riposte no longer reads it to date detection (MTTD retired, migration 0256):
+  # it is the alert's own record of when the source saw the event.
+  # The grid exposes when the tenant took the alert in (source_insert_ts); a
+  # sensor-side detection timestamp, when the tenant sends one, is closer to the
+  # event and comes last so it wins.
   - { source_path: "source_insert_ts",     ocsf_field: "time" }
   - { source_path: "detection_timestamp",  ocsf_field: "time" }
   # ── Alert state ───────────────────────────────────────────────────

integrations/cortex-xdr/mappers/get_incidents.yaml

@@ -18,8 +18,10 @@ ocsf:
   - { source_path: "modification_time",  ocsf_field: "finding_info.modified_time" }
   - { source_path: "xdr_url",            ocsf_field: "finding_info.src_url" }
   - { source_path: "status",             ocsf_field: "status" }
-  # `time` is the MTTD anchor — when XDR opened the incident, as opposed to when
-  # Riposte ingested it. Without it the detection delay column stays empty.
+  # `time` is the OCSF event time — when XDR opened the incident, as opposed to
+  # when Riposte ingested it.
+  # Riposte no longer reads it to date detection (MTTD retired, migration 0256):
+  # it is the alert's own record of when the source saw the event.
   - { source_path: "creation_time",      ocsf_field: "time" }
   - { source_path: "alert_count",        ocsf_field: "count" }
   # ── MITRE ATT&CK (first aggregated tactic/technique) ──────────────

integrations/cortex-xdr/mappers/get_incidents_full.yaml

@@ -35,7 +35,9 @@ ocsf:
   # The detection that opened the incident, so an analyst reading the aggregate
   # can still pivot to the single alert in the XDR console.
   - { source_path: "alerts[0].alert_id",  ocsf_field: "finding_info.uid_alt" }
-  # ── Detection time: the MTTD anchor ───────────────────────────────
+  # ── Event time (OCSF `time`) ───────────────────────────────────────
+  # Riposte no longer reads it to date detection (MTTD retired, migration 0256):
+  # it is the alert's own record of when the source saw the event.
   # Weakest first, strongest last. detection_time is often null on an XDR
   # incident, and then the first alert's own detection timestamp is the honest
   # anchor; incident creation is the last resort.