morning: recite the day the store actually holds

Four defects in the plan, all of them in what it reads or how it prints
it. The checklist line was keyed on Status.Active, which Evaluate reports
only inside the window, so a morning routine skipped and asked about at
14:00 said nothing. Outstanding answers the question the plan asks, "what
did today still not get done", and the line stays placed at the nudge
time so it sorts to the top of the day. Nothing before the window opens
counts, so 06:00 is not a complaint.

The event text kept the "@ 14:00-14:30" tail FactValue writes, next to a
line that prints the hour itself, so every event said its time twice.
Reminders came off ListReminders, which orders by creation, so the 500
row cap dropped a reminder stated long ago for today and kept one stated
this morning for next year. PendingReminders bounds by fire time instead.
The pending filter used a string literal, one typo from matching nothing.

After now marks the plan it trimmed. "что дальше?" past the last item
answered "на 03.08.2026 ничего не запланировано", which denies a day he
just lived through.

The surface the plan belongs on is still open, tracked as Vikunja #431;
the comment in actions_query.go points at it.
Found in review of #58.

internal/store/reminders.go

@@ -26,6 +26,15 @@ type Reminder struct {
 	Collapsed []Reminder
 }
 
+// Reminder lifecycle states. Named for the same reason DigestStatus is: a
+// caller filtering on the string literal "pending" is one typo away from a
+// filter that silently matches nothing.
+const (
+	ReminderPending   = "pending"
+	ReminderFired     = "fired"
+	ReminderCancelled = "cancelled"
+)
+
 var (
 	ErrReminderNotFound = errors.New("store: reminder not found")
 	ErrReminderState    = errors.New("store: reminder not in a mutable state")
@@ -93,6 +102,36 @@ func (s *Store) DueReminders(ctx context.Context, now time.Time) ([]Reminder, er
 	return out, rows.Err()
 }
 
+// PendingReminders returns the pending reminders whose next fire time falls in
+// [from, to), earliest first.
+//
+// The day plan used to take the newest 500 rows out of ListReminders, which
+// orders by creation, and then filter them by day. A reminder stated long ago
+// for today fell off the end of that scan while a reminder stated this morning
+// for next year stayed on it. Bounding by fire time drops what is out of range
+// instead of what is old.
+func (s *Store) PendingReminders(ctx context.Context, from, to time.Time) ([]Reminder, error) {
+	rows, err := s.db.QueryContext(ctx, `
+		SELECT id, created_ts, fire_ts, next_fire_ts, payload, status, cron
+		  FROM reminders
+		 WHERE status = ? AND next_fire_ts >= ? AND next_fire_ts < ?
+		 ORDER BY next_fire_ts ASC, id ASC`,
+		ReminderPending, from.UnixMilli(), to.UnixMilli())
+	if err != nil {
+		return nil, fmt.Errorf("pending reminders: %w", err)
+	}
+	defer rows.Close()
+	var out []Reminder
+	for rows.Next() {
+		r, err := scanReminder(rows)
+		if err != nil {
+			return nil, err
+		}
+		out = append(out, r)
+	}
+	return out, rows.Err()
+}
+
 // MarkReminder sets a reminder's status. Only valid transitions: pending→fired,
 // pending→cancelled. Anything else is a programming error.
 func (s *Store) MarkReminder(ctx context.Context, id int64, status string) error {