Web UI: zone naming and reverse zones, ACL suggestions, record form

- New zone dialog: choose Domain or Reverse zone. Reverse zones are
  created from a network and their name is generated; both kinds show the
  exact zone name and flag likely mistakes (addresses or URLs as names,
  host-like names, duplicates in the view, parent/child zones, networks
  off the octet/nibble boundaries) before anything is submitted.
- Record form: clears every field but the type after an add; shows the
  record exactly as it will be stored and warns about unqualified names.
  In reverse zones it takes an address, defaults to PTR, suggests host
  names of A/AAAA records with that address and warns about a second PTR;
  the record list shows addresses.
- Address match lists (options, view match lists, ACL elements) offer the
  existing ACLs, TSIG keys and built-ins as one-click suggestions and
  flag unknown names.
- Server: in reverse zones a record can be named by its address, and a
  PTR target like nas.example.com without the final dot is read as the
  full host name (a bare label is refused). Warnings noticed while parsing
  record data reach the result again.
- Fixes: brand link hover underline, the dashboard's "New zone" link
  opening the dialog twice.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>

CHANGELOG.md

@@ -10,6 +10,11 @@ The first version, to be released as 0.1.0.
 
 ### Added
 
+- Web UI: wherever an address match list is entered (server, view and zone
+  options such as allow-query or allow-transfer, view match lists, ACL
+  elements) the existing ACLs, TSIG keys and built-in names are offered as
+  one-click suggestions, and names that don't exist are flagged as you type.
+
 - **Query statistics** (off by default; `stats` in jarl.yaml, docs/stats.md).
   When enabled, Jarl adds a loopback statistics channel and a response log to
   named's configuration (merged into existing `logging` and
@@ -101,12 +106,38 @@ The first version, to be released as 0.1.0.
 
 ### Changed
 
+- Web UI, new zone dialog: choose **Domain** or **Reverse zone**. For a
+  reverse zone you give the network (10.10.0.0/24, 2001:db8:1::/48) and the
+  zone name is generated. Either way the dialog shows the exact zone name it
+  will create and explains problems before submitting: an address or URL
+  instead of a name, a host-like name such as www.example.com, a zone that
+  already exists in the view, a child or parent of an existing zone, and
+  networks that don't follow the octet or nibble boundaries.
+- Web UI, record form: after adding a record every field is cleared except
+  the type, and the cursor returns to the name. A "Will add:" line shows the
+  record exactly as it will be stored, with warnings for unqualified names
+  (e.g. a CNAME to readthedocs.io without the final dot). In reverse zones
+  the form asks for the address, defaults to PTR, offers the host names of
+  A/AAAA records with that address, warns about a second PTR for an
+  address, and the record list shows each record's address.
+- Reverse zones: a record name can be given as an address (10.10.0.20) in
+  the API and CLI too, and a PTR target without a final dot that contains a
+  dot (nas.adbraun.lol) is read as the full host name (with a warning); a
+  bare label is refused.
+
 - `jarl resync` / `jarld resync` refuse to overwrite files that were changed
   outside Jarl unless `--force` is given, as documented. Before, they always
   overwrote them.
 
 ### Fixed
 
+- Web UI: the "Jarl 0.1.0" brand link no longer underlines the gap between
+  the name and the version on hover.
+- Web UI: creating a zone from the dashboard's "New zone" link no longer
+  opens the dialog a second time.
+- Warnings noticed while parsing record data (a name read as absolute) were
+  lost before reaching the result; they are shown again.
+
 - The negative-caching warning now uses the effective negative TTL, which
   is the smaller of the SOA minimum and the zone's default TTL (RFC 2308).
   It explains the real effect (new names can stay invisible to resolvers