schedule: correct the never-fires comment — the zero time is in the past, not now
Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
1 file changed,
+3
−2
internal/schedule/converge.go+3 −2
diff --git a/internal/schedule/converge.go b/internal/schedule/converge.go| index 5fb9d0051..fbe383b81 100644 |
| --- a/internal/schedule/converge.go |
| +++ b/internal/schedule/converge.go |
| @@ -220,8 +220,9 @@ func (c *Converger) convergeHost(rt registry.Route, decl Declaration, fireName s |
| if wouldChange { |
| // Schedule.Validate refuses a spec whose first Next is zero at |
| // `set` time; one written some other way must not become a row |
| - // due at the zero time's unix value (-62135596800, i.e. now). |
| - // It is parked at next_at=0 and told why, below. |
| + // due at the zero time's unix value (-62135596800 — in the past, |
| + // so due on the very next tick, forever). It is parked at |
| + // next_at=0 and told why, below. |
| if n := sp.Next(now); !n.IsZero() { |
| next = n.Unix() |
| } else { |