docs(nano): drop the promise of a felis setup --nano that should not exist

nano.go's package comment told the reader that `felis setup --nano` installs the
multiplexer as a service. No such flag has ever existed -- `felis setup` defines
only -config and -dev -- so anyone following the comment gets "flag provided but
not defined: -nano" and exit 2.

Adding the flag was the obvious reading, and it is the wrong one. setup does not
install anything selectively: it re-images the host by running the full bootstrap
TUI, and no install-mode parameter is threaded anywhere -- nothing in Go reads or
writes FELIS_INSTALL_MODE, which is a shell variable bootstrap.sh consumes on its
own. So `--nano` could only mean one of two things. Re-run the installer in nano
mode, which is what pointing at the installer already does. Or convert a
provisioned full host into a nano one, which means tearing down k3s, Postgres and
the proxy -- an uninstall, not a flag.

setup's --dev already settled this shape once. It looked like a channel selector,
silently installed release, and the fix was to refuse it and name the installer
rather than pretend to choose. The same answer applies here, so the comment now
names the real entry point -- the installer's `[2] Felis-nano` prompt, or
FELIS_INSTALL_MODE=nano -- and records why there is no flag, so the next reader
does not reopen it.

No refusing --nano flag is added: --dev exists because it used to be a silent
no-op that people passed, and nothing has ever accepted --nano, so flag's own
"not defined" error is already the correct and clearer failure.

cmd/felis/nano.go

@@ -13,8 +13,16 @@ package main
 // off-loopback with -listen; see the flag below for why that is an explicit opt-in.
 //
 // This is the no-database delivery of the identical brain `felis api` mounts through its
-// route table (internal/api.HasJoinedHandler). `felis setup --nano` / the bootstrap nano
-// choice install this as the runtime service; here it just serves.
+// route table (internal/api.HasJoinedHandler). The bootstrap installer's nano choice — its
+// `[2] Felis-nano` prompt, or FELIS_INSTALL_MODE=nano — installs this as the
+// felis-nano.service unit; here it just serves.
+//
+// There is deliberately no `felis setup --nano`. setup re-images the host through the full
+// bootstrap TUI and carries no install-mode parameter anywhere (nothing in Go reads or sets
+// FELIS_INSTALL_MODE), so such a flag would either re-run the installer — which is what
+// pointing at the installer already does — or tear a full install down into a nano one,
+// which is an uninstall, not a flag. This is the same reasoning that makes setup's --dev
+// refuse and name the installer rather than pretend to choose a channel.
 
 import (
 	"context"