[clstaudt]

Relates to #502 and #597. Builds on the idea in #598 (configurable contract-end and overdue reminders).

What

• Rules make the tasks. The Tasks view gets a Tasks | Rules switch. A rule is either on a date (once or repeating) or when something happens to a contract, project, invoice or financial goal: before, on or after one of its dates, or when its status changes. The trigger reads as one sentence, and a live preview shows the tasks the rule makes today and the next one.
• Events come from the records. tuttle/app/tasks/rules.py lists each record's dates and the statuses Tuttle already shows (project board stage, contract and invoice status); the 20 events derive from that.
• Statuses. Open ones (overdue, lead, offer, agreed) include records already in them. Final ones (paid, cancelled, completed, reached) only count records that reach them after the rule is made, so a "thank them for paying" rule doesn't make a task for every old payment. A status change has no date, so the rule notes the day it first sees one (TaskRuleNotice).
• No floods. A repeating rule makes one task, for its latest day. Contract and project dates before the rule was made are left alone. A task closes itself when it's no longer worth doing (invoice paid, contract completed).
• Built-in rules. The overdue-invoice task and a heads-up 30 days before a contract ends are now ordinary rules every user starts with, to edit, pause or delete. The migration moves existing overdue tasks over with their status. Getting-started tasks stay built in.
• Tasks show their date, link to their record and to the rule that made them. The sidebar counts pending tasks. Harry's demo data has rules of each kind.
• Speed. Task generation loads each kind of record once per pass: 3.2 s → 0.2 s with 56 rules on the demo data.

Screenshots

Tasks made by rules

Rules

New rule: when something happens

On a date	Light and dark

Open status: overdue invoices already out count	Final status: from today

Checks

1090 tests pass, 196 of them new: the rule engine; the composer's RPC calls with the UI's exact payloads on the demo database; and a simulation that runs a rule for every event over two years of days, checking that no task comes early, twice, or back after it was done, and that a second pass on the same day changes nothing. tsc passes. Drove the app with Playwright on a scratch demo install: creating, editing, pausing and deleting rules, every preview, links to records, dark mode and a narrow window, with no console errors. Upgraded a copy of an existing dev database.

🤖 Generated with Claude Code