3 Commits

Include renames

Author	SHA1	Message	Date
sneak	433fdceee2	Say max_retries is the total attempt count, not a retry count (closes #316) ... The delivery core makes max_retries attempts in total: a fresh delivery starts at attempt one and gives up once the attempt number reaches max_retries, so 3 is three attempts, not four, and 0 is special-cased to a single fire-and-forget attempt with no retries and no circuit breaker. The create and edit target forms called it "Max retries" with no total, and the README data-model row called it "maximum retry attempts", so an operator wanting "try, then retry twice" would enter the wrong number. Both forms and the README rows now state the number is the total number of delivery attempts, with the 0 case spelled out. The delivery arithmetic is unchanged. A UI copy test renders both forms and pins the shared wording so it cannot drift back to a retry count. Model: opus-4-8	2026-09-21 07:55:07 +00:00
clawbot	687405993e	Harden operator-set target headers (closes #233) (#242)	2026-08-20 10:54:43 +02:00
clawbot	aba02bc509	Add a target edit form with headers and timeout fields (closes #127) (#229)	2026-08-20 07:24:12 +02:00