For rejected PDF417 requests, phase timing is the authoritative locator

Reusable observability lesson from the Adam PDF417 phase-timing rollout: terminal rejection projections may intentionally report zero aggregate detector/scheduler and strategy counters even after detector and planning have completed. Diagnose deadline location from activePhase, lastCompletedPhase, and ordered monotonic phaseTimings, not the legacy aggregate timing/count fields. In a 2026-09-08 staging investigation, this distinction separated a scheduler-phase deadline from an upstream detector failure. Keep request identifiers and payloads out of terminal telemetry; use bounded cross-system timestamp correlation to connect it to a user flow.