[aaronspring]

TL;DR

Freelancers forget contract deadlines and overdue invoices because Tuttle only created a task once an invoice was already overdue with no advance warning. This adds configurable reminder lead times so users get tasks before contracts end and at custom intervals after invoices go overdue, with a new Tasks tab in Settings to configure them.

Closes #597

Changes

• Contract-end task generation: creates tasks N days before a contract's end_date (default: 30 days and on the day). Skips open-ended and completed contracts.
• Configurable overdue lead days: the existing overdue-invoice task now respects a user-defined list of days-after-due (default: 0, same as before).
• Settings backend: two new key-value settings (tasks.contract_end_lead_days, tasks.invoice_overdue_lead_days) with get_task_reminders / save_task_reminders RPC endpoints.
• Tasks tab in Settings UI: new tab with comma-separated day inputs for both reminder types, with inline help text.
• Tests: 8 new test cases covering contract-end tasks (lead window, completed contract, open-ended, idempotency, custom lead days, today's end date) plus unit tests for _parse_lead_days. All 22 task tests pass; full suite 901 passed.

Screenshots: could not capture automatically (Chrome extension not connected). Please add screenshots of the Tasks settings tab before merging.

intent revealed by prompt history

Started from issue #502 comment asking for contract-end notifications alongside invoice-overdue reminders. Scope was refined through four clarification questions: global-only settings (not per-contract), new Tasks tab in Settings, comma-separated days input, and auto-resolve on contract completion.

1 prompt, 4 decisions

1. "implement Automation triggers for common workflows #502 comment. first create issue about contract end notification. add in settings tasks about when to raise a new task: invoice overdue set to once overdue as current, new contract ends when contract ends and 1 month before. those reminders can have multiple dates and are user defined ranging from days to months. first ask clarification questions, then create the issue, then create branch and test locally, then /open-pr"
2. ↳ Scope — Claude asked "Should the reminder lead times be global settings or per-contract overrides?"
   → Global only (Recommended)
3. ↳ UI placement — Claude asked "Where should the task reminder settings live in the Settings UI?"
   → New 'Tasks' tab (Recommended)
4. ↳ Input format — Claude asked "How should the user specify reminder lead times?"
   → Comma-separated days
5. ↳ Auto-resolve — Claude asked "Should contract-end tasks auto-resolve when the contract is marked completed?"
   → Yes (Recommended)

🤖 Generated with Claude Code

[aaronspring]

[clstaudt]

@aaronspring Thanks but I am not sure about this one.

Why not go all the way? Have a look at #601

[aaronspring]

mine was a small addition. I prefer your #601