5 Commits

Include renames

Author	SHA1	Message	Date
clawbot	7e9e441d42	Describe code in its own terms, not by an earlier build's data (closes #522) ... Several comments justified code by what an earlier build would have left in a database or on disk. Each now says what the code does: reserveSQLiteFile sets the mode on every open whoever created the file, and expired treats a session lacking a deadline's timestamp as expired. The comments on retention, resubmitted events, archive pruning, target headers, the redactor and the delivery result view drop their mentions of older rows. parseMaxRetries loses its paragraph on targets saved before the ceiling existed, and neither BeforeSave nor retentionCutoff cites a migration. Comments only. Model: opus-5-5	2026-10-13 06:53:38 +00:00
clawbot	45bd7e9b94	Pin the close before the reopen in the archive sweep (closes #103) ... The archive sweep closes a target's archive connection before it reopens the file, and no test noticed if that close was removed, which would leak one SQLite connection per target per sweep. A test now keeps the connection from before a sweep that reopens the archive and requires it closed afterwards. The sweeper's query for database targets takes the sweep's context; a sweep whose context is done returns without an error line, so stopping is not logged as a failure, and a test pins that. The comment on the sweeper's cancel function gives the true reason it needs no lock: fx calls the stop hook only after the start hook has returned. Model: opus-5-5	2026-10-02 18:16:31 +02:00
clawbot	fd036774f9	Name each database target's archive for its webhook and target (closes #376) ... Each database target now writes its own archive file, archive-WEBHOOKNAME-TARGETNAME-TARGETID.db, named by delivery.ArchiveFileName, in place of one archive per webhook keyed on its UUID. Renaming a webhook or a target renames its archive files (with any -wal and -shm) before the new name is saved, never over an existing file, and moves every one back if a rename or the save fails. The webhook edit, the target edit and target creation share one lock so no two interleave. Deleting a webhook or target leaves its files on disk. Nothing looks for the old archive-WEBHOOKID.db files. The README gives the naming and the recovery steps. Model: opus-5-5	2026-10-02 13:28:49 +02:00
clawbot	2ee720a9af	Bound shutdown hooks by their stop context (closes #102)	2026-08-14 06:18:33 +02:00
clawbot	3e261d2f01	Evict archive writers on deletion and sweep idle archives (closes #89) (#95) ... Per-webhook archive writers are now evicted when the webhook or its last database target is deleted, and a background sweeper prunes expired rows from idle archives that no longer receive writes. Archive files themselves are never deleted.	2026-08-10 15:52:20 +02:00