Implement adaptive client list

docs/evidence/milestone-16.md

@@ -2,8 +2,11 @@
 
 Recorded 2026-10-27T22:42:48+02:00 on the native
 `x86_64-unknown-linux-gnu` development host. This is **implementation and
-synthetic evidence, not systemd acceptance**. The milestone remains blocked on
-private-peer behavioral and disposable-VM checks.
+synthetic evidence, not systemd acceptance**. On 2026-10-28, the user reported a
+successful manual check and explicitly directed that M16 be considered done.
+The check's environment, commands, source identity, and transport coverage were
+not supplied. PLANS.md records user-directed acceptance; this report does not
+claim a passing disposable-VM run or independently close M16-R2.
 
 ## Source and protocol basis
 
@@ -65,8 +68,8 @@ Native release artifact `target/release/wireguard-admin` SHA256:
 The prior disposable Debian VM was stopped before guest installation and has
 no verified guest marker or running systemd acceptance environment, per
 [`VM_ACCEPTANCE.md`](../VM_ACCEPTANCE.md). No private-socket or system-bus
-restart was run in a disposable VM. Neither transport is accepted against real
-systemd yet; production must not be used to fill this gap. The next check is
-to finish and authorize a disposable VM with synthetic WireGuard configuration,
-then run both transport paths and verify job completion plus full runtime
-matching, with exact source/artifact identity.
+restart was run in a disposable VM as part of the recorded checks. This gap
+remains despite the later user-directed acceptance. A future independent check
+would use a disposable VM with synthetic WireGuard configuration to cover both
+transport paths, job completion, and full runtime matching, with exact
+source/artifact identity. Production must not be used to fill the gap.