Add integration tests based on VM

README.md

@@ -48,6 +48,12 @@ absolute. Settings validation checks syntax and values only; it does not
 require the referenced files, directories, or service to exist and does not
 perform DNS lookups.
 
+For installation, backup custody, restart failure handling and manual recovery,
+see [`docs/OPERATIONS.md`](docs/OPERATIONS.md). The qualified evidence and the
+current host release-candidate assessment are in
+[`docs/RELEASE_READINESS.md`](docs/RELEASE_READINESS.md); those records do not
+claim a completed systemd VM run or real IPv6 qualification.
+
 ## Terminal workflows
 
 The client list supports arrow-key selection, Enter for details, `?` for help,
@@ -98,9 +104,10 @@ let bytes_to_review = updated.render(); // no persistence or VPN operation
 ```
 
 Runtime and restart behavior has synthetic fixture and fake-adapter coverage;
-it has not been accepted against a real WireGuard interface or systemd service.
-Real WireGuard integration is deferred to the isolated Alpine milestone, and
-real systemd/D-Bus acceptance requires the disposable VM milestone.
+the accepted Alpine milestone also exercised real IPv4 WireGuard traffic and
+the Rustix reader. The Alpine fixture did not use systemd/D-Bus, and the
+disposable systemd VM milestone has not been run. Real IPv6 capability and
+traffic remain unverified.
 
 ## Saved state, Commit, and backups
 
@@ -189,4 +196,6 @@ It checks an 80×24 to 40×8 to 80×24 resize sequence and terminal cleanup afte
 `q`. The workflow also checks that Esc clears a returned QR disclosure; the
 focused renderer test checks complete quiet-zone fit. Do not use the development
 host's settings or VPN as a substitute.
+M1–M8 qualification evidence and the remaining M9 limitations are summarized
+in [`docs/RELEASE_READINESS.md`](docs/RELEASE_READINESS.md).