docs(cron): record the due-only occurrence identity in the missed-occurrence contract

Also map the two salvaged contributor emails (kleros109, fangliquanflq).
This commit is contained in:
teknium1
2026-09-14 18:17:42 -07:00
committed by Teknium
parent 7cecc9eb3d
commit e89605b4e6
2 changed files with 9 additions and 1 deletions
+1
View File
@@ -0,0 +1 @@
kleros109
@@ -140,7 +140,14 @@ dropped silently. The mechanics, in the order the due scan applies them
3. **Already fired → never twice.** `completed_occurrence()` consults the
executions ledger for a `completed` row with that exact `scheduled_instant`
before anything is due; a slot that ran before the restart advances without
firing. `failed` / `unknown` rows do not count as completion.
firing. `failed` / `unknown` rows do not count as completion, and neither
does a `completed` row whose `finished_at` (else `claimed_at`) precedes the
instant it is stamped with — a run cannot prove an occurrence that had not
happened yet. Rows without a comparable timestamp keep counting.
An occurrence identity is only claimable once it is due: `claim_job_for_fire`
drops a `scheduled_instant` that is still in the future, so an off-tick fire
(dashboard trigger, webhook, lease reclaim, misfire backstop) runs
occurrence-free instead of consuming the next slot.
4. **Late within grace → fire late.** Grace = half the period clamped to
`[120 s, 2 h]` (`_compute_grace_seconds`); the dispatch is stamped
`last_dispatch.kind = late`.