Stop pinning Sway output mode in dev config

Removes the hardcoded `output * mode 1920x1080` from the development Sway config and updates related docs to match. Dev sessions now rely on each output’s preferred mode at scale `1`, which better follows current display size (including VMware autofit behavior), while still documenting how to set a mode manually when needed.

compositor/README.md

@@ -50,11 +50,10 @@ NEBULA_SHELL_AUTOSTART=0 sh compositor/sway/dev/run-sway-vm.sh
 
 ### Output / resolution
 
-The development config uses scale `1` and requests `1920x1080` when that mode is advertised. If it is not, Sway keeps the preferred mode. This is a VM convenience, not a production requirement.
+The development config uses scale `1` and does not pin a resolution. Sway uses the output's preferred mode, which follows the current display size (including VMware Autofit Guest).
 
 ```bash
 swaymsg -t get_outputs
-swaymsg output <name> mode 1920x1080
 swaymsg output <name> scale 1
 ```
 

compositor/sway/nebula-sway.conf

@@ -9,15 +9,13 @@ set $term foot
 # -----------------------------------------------------------------------------
 # Output / resolution
 # -----------------------------------------------------------------------------
-# Development default: 1:1 scale, fill the current VMware display.
-# Request 1920x1080 when the output advertises that mode. If the mode is not
-# available, Sway keeps the output's preferred mode instead of failing.
+# Development default: 1:1 scale, fill the current display.
+# No mode is pinned, so Sway uses the output's preferred mode (typically the
+# native or current size). VMware Autofit Guest can then follow the host window.
 #
-# This is a development convenience, not a production architecture requirement.
 # Inspect modes:  swaymsg -t get_outputs
 # Force another mode (example):  swaymsg output <name> mode 1600x900
 output * scale 1
-output * mode 1920x1080
 output * bg #000000 solid_color
 
 # -----------------------------------------------------------------------------