docs: v1 checklist ticks, DID in the Request-URI

The outside install, restores, the week on the owner's server, Portainer
updates and both registries are done. The mobile app is after v1.

docs/spec/06-voipms.md

@@ -54,8 +54,9 @@ voip.ms Asterisk PJSIP wiki: registration + auth + aor + endpoint + identify,
   which means the **Request-URI user is the 10-digit DID** (no leading 1).
 - The dialplan (03 §6.4) normalizes it to 11 digits and checks `sp-did-exists`. If that fails,
   it falls back to the user part of the `To:` header. That covers either behavior.
-- **M3 acceptance check (verify):** run `pjsip set logger on`, call the DID from a
-  mobile phone, and confirm which header carries the DID. Record the finding here.
+- **Checked (owner, 2026-10-21):** a mobile → DID call came in with the DID as the Request-URI
+  user, and the dialplan routed it to the digital receptionist. The `To:` fallback stays for
+  other providers.
 - Inbound caller ID arrives as 10 digits for North American callers. The dialplan normalizes it to 11.
 
 ## 4. Outbound calls

docs/v1-checklist.md

@@ -14,7 +14,7 @@ Tick a box only with proof: a date and what was seen.
 - [x] The trunk shows **Registered** in the UI (2026-10-21: green, voip.ms, the sub-account at
       its POP).
 - [x] A mobile → DID call rings a phone. 2026-10-21: DID → digital receptionist → browser
-      phone; the DID came in the Request-URI. Still to do: write that down in 06 §3.
+      phone; the DID came in the Request-URI (written down in 06 §3).
 - [x] An outbound call shows the DID as caller ID on the mobile (2026-10-21, owner).
 - [ ] Write down in 06 §4 whether per-call caller ID (Remote-Party-ID) is honored.
 
@@ -31,18 +31,14 @@ On hold until the owner has the phones (2026-10-21).
 
 ## Someone else installs it (M11)
 
-- [ ] An outside tester follows only the admin guide and gets inbound and outbound calls working
-      on a fresh VM.
-- [ ] A backup restores on a second VM.
-
-On hold (2026-10-21).
+- [x] An outside tester follows only the admin guide and gets inbound and outbound calls working
+      on a fresh VM (2026-10-28, owner).
+- [x] A backup restores on a second VM (2026-10-28, owner).
 
 ## A week on the owner's server
 
-- [ ] 7 days handling real calls with no crash or restart of the api or Asterisk.
-- [ ] Nightly backups restore cleanly.
-
-In progress on the owner's server (v0.0.2, from 2026-10-21).
+- [x] 7 days handling real calls with no crash or restart of the api or Asterisk (2026-10-28, owner).
+- [x] Nightly backups restore cleanly (2026-10-28, owner).
 
 ## Updating
 
@@ -57,7 +53,8 @@ Docker only, never bare metal (owner, 2026-10-21).
       restarts, and the script went back to v0.0.3 with that backup restored.
 - [ ] A real compose install with the bundled Caddy updated with `scripts/update.sh`, with calls
       and backups.
-- [ ] The owner's Portainer stack updated to a release that changes the database.
+- [x] The owner's Portainer stack updated to a release that changes the database, several times
+      (2026-10-28, owner).
 
 ## Security leftovers (08 §6)
 
@@ -73,10 +70,9 @@ Owner's decision (2026-10-21): fix all of them. Each is in 08 §6 with its test.
 ## The release
 
 - [ ] Version 1.0.0 in every `package.json`, and a v1.0.0 entry in the [changelog](../CHANGELOG.md).
-- [ ] The release builds and pushes images to both the Gitea registry and ghcr.io. (Gitea works.
-      ghcr.io: the api image pushes; the asterisk package exists, empty, and refuses the push.)
+- [x] The release builds and pushes images to both the Gitea registry and ghcr.io (2026-10-28, owner).
 
 ## Not needed for v1
 
-More SIP providers (Telnyx, Flowroute, Twilio), SMS, push notifications for phone apps, and the
-M12 list in the roadmap.
+The mobile app (owner, 2026-10-28), more SIP providers (Telnyx, Flowroute, Twilio), SMS, push
+notifications for phone apps, and the M12 list in the roadmap.