Check resolved file configuration before diagnosing a missing cron schedule

When diagnosing a scheduled service, distinguish service-level settings, configuration resolved from its deployed repository file, and actual execution evidence. A null service-level cronSchedule or nextCronRunAt does not by itself establish that the deployed schedule was removed. Inspect resolvedFileConfig and its deployment identity, then correlate container starts/exits with application completion heartbeats. This applies to platforms that merge configuration sources; an intact manifest still does not prove that the scheduler dispatched a run. Keep missing dispatch, a stuck execution, and failed business work as separate hypotheses.