2 Commits

Include renames

Author	SHA1	Message	Date
rmancinasandClaude Opus 5	89611da202	feat(notificaciones): global send flags + editable schedules ... The "Flags del envío" panel lived inside the Servicios tab and only governed the four bulk jobs. The pólizas half had no debug at all, so there was no way to test a renewal notice without mailing a real customer. The panel now lives in the /notificaciones shell above the tabs and both halves read it. `debug` on the renewal path diverts to the same override inbox as the servicios jobs and deliberately does NOT write the `RenewalNotice` row or advance the sweep's `lastSuccessfulAt` — the customer was not notified, so nothing may gate the letter they are still owed. `ignoreDayRestriction` and `useEmailLimit` stay estado-de-cuenta-only and are labelled as such. Both automatic sweeps are now operator-editable. The renewal cadence was a `@Cron("0 6 * * *")` literal and servicios had no automatic run at all; both now resolve through `NotificationScheduleService`, which stores the cadence in `app_settings` and reinstalls the cron job on save — no redeploy, no restart. Defaults preserve current behaviour: pólizas 06:00 daily, servicios off. A scheduled run never inherits the UI flags; it always sends for real. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-02 12:23:19 -07:00
rmancinasandClaude Opus 5	a491ef3eed	feat(notificaciones): edit summary recipients in the UI ... NOTIFICATION_ADMIN_EMAILS made "add Beto to the summaries" a redeploy — the wrong unit of work for a list that changes when office staff change. Adds `app_settings`, a key/value table for the configuration staff must be able to change without a deploy, and `SettingsService`, which resolves every key db -> env -> default and reports which of the three a value came from. That ladder is what makes the move safe: a deployment behaves exactly as before until somebody saves in the UI, and the screen can say "this is still coming from the deployment" rather than implying somebody chose it. - new ability `setting:manage` (ADMIN) — deliberately above `notification:send`, since redirecting the audit summaries is how someone would quietly stop them being read - GET/PUT /notifications/settings/admin-emails; read is open to any logged-in user so the UI can display the list, write is gated - resolved per job, not cached at boot, or we would reintroduce exactly the restart-to-apply behaviour being removed - a saved empty list means "nobody" and does NOT fall through to the env, or clearing the field would keep mailing the people just removed Credentials stay in env — see the model doc for where the line is drawn. Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>	2026-08-02 11:58:42 -07:00