Commit 69878888f621

@@ -17,7 +17,7 @@ Fedora CSB (base OS, IT-managed)
 From another machine with SSH access to aomi:
 
 ```bash
-ssh vincent@192.168.1.39 'bash -s' < imperative/aomi/bootstrap.sh
+ssh vdemeest@192.168.1.23 'bash -s' < imperative/aomi/bootstrap.sh
 ```
 
 Or on aomi directly:
@@ -34,8 +34,8 @@ cd ~/src/home
 # System-manager (WireGuard, Syncthing)
 nix build .#systemConfigs.aomi && sudo ./result/bin/activate
 
-# Home-manager (dev tools, shell) — TODO: not yet configured
-# nix run home-manager -- switch --flake .#vincent@aomi
+# Home-manager (dev tools, shell)
+home-manager switch --flake .#vdemeest@aomi
 ```
 
 ## WireGuard
@@ -48,10 +48,11 @@ placeholder for the private key. After first activation:
 sudo cp /path/to/backup/private.key /etc/wireguard/
 sudo chmod 600 /etc/wireguard/private.key
 
-# Option 2: Generate new keypair (update globals.nix with new pubkey)
+# Option 2: Generate a new keypair, then update globals.nix
 wg genkey | sudo tee /etc/wireguard/private.key
 sudo cat /etc/wireguard/private.key | wg pubkey
 # → update globals.nix machines.aomi.net.vpn.pubkey
+#   (current: Pmu/0CjRaClmz+v25OV3SLd/V6Il8YLLavbtu8cYSGY=, VPN IP 10.100.0.17)
 
 sudo systemctl restart wireguard-wg0
 ```
@@ -59,10 +60,11 @@ sudo systemctl restart wireguard-wg0
 ## Syncthing
 
 After activation, Syncthing runs as a system service under the
-`vincent` user. It will generate a new device ID — update
-`globals.nix` and accept the device on other nodes.
+`vdemeest` user. The device ID is already registered in `globals.nix`
+(`S6UM56N-...`). If the ID changes, update `globals.nix` and re-accept
+the device on other nodes.
 
 ```bash
-# Get new device ID
+# Get the current device ID
 curl -s http://localhost:8384/rest/system/status | jq -r .myID
 ```

@@ -1,16 +1,20 @@
 # Nagoya Configuration
 
-> ⚠️ **DEPRECATED:** This imperative setup is now deprecated in favor of the declarative system-manager configuration at `~/src/home/systems/nagoya/system.nix`.
+> 🚧 **Needs rework:** Nagoya is managed with Nix `system-manager`
+> (`~/src/home/systems/nagoya/system.nix`, exposed as `systemConfigs.nagoya`
+> in `flake.nix`). The imperative `apply.sh` below predates that and is kept
+> only as a bootstrap fallback; it still needs to be reconciled with the
+> system-manager config.
 >
-> The imperative scripts are kept as a backup fallback only.
->
-> To use system-manager, see the deployment instructions in `CLAUDE.md`.
+> For deployment, see `AGENTS.md` at the repo root.
 
-Configuration scripts for the Nagoya system, a Debian-based server.
+Configuration for the Nagoya host, a Debian-based aarch64 server.
 
 ## Overview
 
-This directory contains idempotent configuration scripts for the Nagoya host, which runs Debian and is not managed by NixOS.
+This directory contains the legacy idempotent `apply.sh` script for the Nagoya
+host. The current source of truth is the Nix `system-manager` configuration in
+`systems/nagoya/`.
 
 ### System Information