* feat(managed-agent): add an admin launcher for the maintenance entry points
The server has twelve offline maintenance entry points, but the reference
distribution only shipped a launcher for operator recovery. The docs ran
the rest from a module build, sometimes through a classified jar the
distribution does not ship.
bin/qwen-managed-agent-admin <command> now runs each entry point by a
short name from the server jar, through PropertiesLauncher, since every
classified jar is the same application with another main class. It lists
its commands without starting Java, exits 2 on an unknown command, and
loads config/application.yml as the other launchers do. Packaging fails
when a mapped class is missing or has no main method.
The deployment guide gains a maintenance-commands section that names the
W1_JDBC_* and K2_JDBC_* credentials the commands read. The server and K2
READMEs show the distribution form first, and the K2 module-build commands
use the plain server jar.
* docs(managed-agent): name the admin commands that read the Spring datasource
operator-recovery and resident-retirement start the server's Spring
configuration and take its datasource, so they read SPRING_DATASOURCE_*
and the other control-plane settings, not W1_JDBC_* or K2_JDBC_*. The
deployment guide and the design said every database command read its
own credentials; they now name the two exceptions, say to run them with
server.env loaded, and note that csi-protection opens no database.
The config template's list of launchers that default
SPRING_CONFIG_ADDITIONAL_LOCATION now includes the admin launcher, which
shares the server launcher's preamble instead of a copy of it. A test
now also fails when a class with a main method has no admin command.
Shaojin Wen
6ef3eaa2f2