Use one name for each thing the UI shows (closes #399)

The database target type is called an archive on its badge, in the add target form's type list and on its edit page, and its settings read "Archive expiry" and "Archive rotation" everywhere, the new webhook page included. The retry field is labelled "Delivery attempts", with its help text and error messages to match, on both target forms and in the target list. The navbar says "Sign out" and the sign-in page "Sign in". The resubmit notice says "webhook". The stored values (`database`, `max_retries`) and their meaning are unchanged.

Model: opus-5-5

README.md

@@ -1617,10 +1617,11 @@ event routing.
 The new webhook form can also give the webhook its first targets: an
 optional HTTP target URL creates an `http` target named `HTTP`, and the
 archive checkbox creates a `database` target named `Archive` whose
-`expiry` is the pruning chosen beside it (never, 1h, 12h, 24h, 30d, 90d
-or 365d) and whose `rotation` is the rotation chosen below that (none,
-monthly, daily or hourly). Both are validated as on the add target form,
-and the webhook and its targets are created together or not at all.
+`expiry` is the archive expiry chosen beside it (never, 1h, 12h, 24h,
+30d, 90d or 365d) and whose `rotation` is the rotation chosen below that
+(none, monthly, daily or hourly). Both are validated as on the add
+target form, and the webhook and its targets are created together or
+not at all.
 
 | Field            | Type    | Description |
 | ---------------- | ------- | ----------- |
@@ -1707,7 +1708,7 @@ events should be forwarded.
 | `type`           | TargetType | One of: `http`, `slack`, `database`, `log` |
 | `active`         | boolean    | Whether deliveries are enabled (default: true) |
 | `config`         | JSON text  | Type-specific configuration |
-| `max_retries`    | integer    | Total delivery attempts for `http` and `slack` targets, not retries on top of the first: 0 is a single fire-and-forget attempt with no retries and no circuit breaker, and a value of N makes N attempts in all, with exponential backoff and a per-target circuit breaker. Ignored by `database` and `log` targets |
+| `max_retries`    | integer    | Total delivery attempts for `http` and `slack` targets, not retries on top of the first: 0 is a single fire-and-forget attempt with no retries and no circuit breaker, and a value of N makes N attempts in all, with exponential backoff and a per-target circuit breaker. Ignored by `database` and `log` targets. The web UI labels it Delivery attempts |
 
 **Relations:** Belongs to Webhook. Has many Deliveries.
 
@@ -1736,7 +1737,9 @@ events should be forwarded.
   expiry in plain units, such as "30 days", and the rotation. No external
   delivery and no retries; an archive write failure fails the delivery.
   See the database target section under "Per-Webhook Event Databases"
-  for the full semantics.
+  for the full semantics. The web UI calls this type an archive: its
+  badge, the add target form's type list and the target edit page say
+  so, and its settings are labelled Archive expiry and Archive rotation.
 - **`log`** — Write the event to the application log (stdout). Useful
   for debugging.
 
@@ -3081,9 +3084,9 @@ abuse limit later; they are tracked as future work.
 
 | Method | Path            | Description |
 | ------ | --------------- | ----------- |
-| `GET`  | `/pages/login`  | Login page (not rate limited). Its `next` parameter names the page to return to after login; anything but a path on this site is replaced with `/` |
-| `POST` | `/pages/login`  | Login form submission. On success, redirects to the form's `next` when it is a path on this site, otherwise to `/`. Credentials are verified before any limit is consulted, so a correct password is never throttled; 5 FAILED attempts per minute per bucket per submitted username, then `429`. `503` if no verification slot frees up within 5s, or immediately if 16 requests are already queued for one (see [Rate Limiting](#rate-limiting)) |
-| `POST` | `/pages/logout` | Logout (destroys session) |
+| `GET`  | `/pages/login`  | Sign-in page (not rate limited). Its `next` parameter names the page to return to after signing in; anything but a path on this site is replaced with `/` |
+| `POST` | `/pages/login`  | Sign-in form submission. On success, redirects to the form's `next` when it is a path on this site, otherwise to `/`. Credentials are verified before any limit is consulted, so a correct password is never throttled; 5 FAILED attempts per minute per bucket per submitted username, then `429`. `503` if no verification slot frees up within 5s, or immediately if 16 requests are already queued for one (see [Rate Limiting](#rate-limiting)) |
+| `POST` | `/pages/logout` | Sign out (destroys session) |
 
 #### Authenticated Endpoints