Follow the sibling project's rename to dev-updater

It is no longer "local" -- it serves over WireGuard rather than the LAN --
and it is specifically for developing new apps. Renaming the references
here at the same time keeps one name to search for across both repos.

Also drops the last references to gen-dev-cert.sh, which the in-process
certificate generation replaced: the build script and the Gradle task now
say to start the server once, and test-wg-tunnel.sh reads the
certificates from the XDG directory rather than the repo.

Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_017xn8nHw1tw1R6PtiY1eEtw

AGENTS.md

@@ -22,11 +22,11 @@ session-type branch in shared code (routes, transcript, app screens).
 
 ## Layout
 
-Mirrors `../local-updater` deliberately — same stack (axum 0.8 +
+Mirrors `../dev-updater` deliberately — same stack (axum 0.8 +
 axum-server/rustls, tokio, clap; Kotlin 2.4.x + Compose Multiplatform,
 single `:androidApp` module), same cert scheme, same registry pattern (every
 session mutation funnels through the manager so in-memory and on-disk state
-can't come apart). Read local-updater's `README.md` and `AGENTS.md` for the
+can't come apart). Read dev-updater's `README.md` and `AGENTS.md` for the
 conventions before diverging from them; module-by-module intent for this
 repo is in PLAN.md's "Backend layout" section.
 
@@ -62,7 +62,7 @@ real-phone/WireGuard bring-up, which is operational rather than code.
   from `server/` — the build stays warning-clean, keep it that way.
 - App: from `app/`, `. ./android-env.sh && ./gradlew :androidApp:compileDebugKotlin`
   to typecheck; `./build-apk.sh` to produce the APK to install on a phone
-  (through Local Updater); `./run-android.sh` to build, install, and launch
+  (through Dev Updater); `./run-android.sh` to build, install, and launch
   on the emulator.
 - **The APK pins the CA of the machine that builds it**, read at build time
   from `$XDG_CONFIG_HOME/ai-app/certs/ca.pem` (`AI_APP_CA` overrides) and
@@ -83,7 +83,7 @@ real-phone/WireGuard bring-up, which is operational rather than code.
 Established 2026-08-25, and it decides more than it looks like:
 
 - **The host (192.168.1.168) is the backend machine.** It runs
-  local-updater's server today and is where `ai-server` belongs in
+  dev-updater's server today and is where `ai-server` belongs in
   production: it has the LAN address the phone can reach, and it's where
   WireGuard terminates. `wg-setup-host.sh` sets that up (keys, `wg0.conf`,
   the phone's QR); run it there with `sudo WG_ENDPOINT=<ddns name>`.
@@ -157,10 +157,10 @@ Established 2026-08-25, and it decides more than it looks like:
   SourceDirectory(task, Task::outputDir) }`, which also carries the task
   dependency.
 
-## Environment notes (this machine, learned in local-updater)
+## Environment notes (this machine, learned in dev-updater)
 
 - Android SDK is at `~/Android/Sdk`, not the root-owned `/opt/android-sdk`
-  the ambient `$ANDROID_HOME` may point at; copy local-updater's
+  the ambient `$ANDROID_HOME` may point at; copy dev-updater's
   `android-env.sh` override pattern.
 - Each agent command runs in a fresh shell — exported environment does not
   carry over. Chain: `cd app && . ./android-env.sh && ./gradlew …`. Never
@@ -171,5 +171,5 @@ Established 2026-08-25, and it decides more than it looks like:
   (`setsid nohup … & disown -h`, verify `PPID 1`), and every
   `pgrep -f`/`pkill -f` pattern needs its first character bracketed
   (`[a]i-server`) in **every** occurrence in the command, or the pattern
-  matches the shell running it. Full explanation in local-updater's
+  matches the shell running it. Full explanation in dev-updater's
   `AGENTS.md` — it bites exactly the same way here.