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

server/src/certs.rs

@@ -111,7 +111,7 @@ fn generate_leaf(
     params.distinguished_name.push(DnType::OrganizationName, "ai-app dev");
     params.distinguished_name.push(
         DnType::CommonName,
-        addresses.first().map(|a| a.to_string()).unwrap_or_else(|| "local-updater".to_string()),
+        addresses.first().map(|a| a.to_string()).unwrap_or_else(|| "dev-updater".to_string()),
     );
     params.subject_alt_names = addresses.iter().map(|a| SanType::IpAddress(*a)).collect();
     params.is_ca = IsCa::ExplicitNoCa;

server/src/main.rs

@@ -193,7 +193,7 @@ async fn main() -> Result<()> {
         tracing::warn!(
             "a new CA was generated in {} -- any installed app pins the previous one and can no \
              longer reach this server. Rebuild it with app/build-apk.sh, which embeds this CA, \
-             and reinstall through Local Updater.",
+             and reinstall through Dev Updater.",
             certs_dir.display(),
         );
     }

server/src/session/mod.rs

@@ -1,7 +1,7 @@
 //! The live session registry. Every session mutation -- spawn, delete,
 //! token changes -- funnels through [`SessionManager`] under one lock, so
 //! in-memory state and `config.json` can't come apart (the same pattern as
-//! local-updater's `registry.rs`).
+//! dev-updater's `registry.rs`).
 //!
 //! A live session is a driver plus one event pump: the driver reports
 //! [`Event`]s into an mpsc channel; the pump assigns each a sequence