81: Control Nenjim process construction and ordered startup through NenjimHub.conf

README.md

@@ -17,7 +17,7 @@ Every application-owned, human-maintained runtime configuration file starts
 with an explicit format version:
 
 ```text
-FORMAT_VERSION=1
+FORMAT_VERSION=<version supported by that file's loader>
 ```
 
 Blank lines and full-line comments may precede the declaration, but it must be
@@ -33,6 +33,7 @@ configuration files. Compatible additions do not require a version increment.
 
 This policy currently applies to:
 
+- `NenjimHub.conf` (mandatory version 2 with ordered `[AUTO_START]`)
 - `alarms.conf`
 - `alarmaction_Console.conf`
 - `alarmaction_Pushover.conf`
@@ -44,6 +45,10 @@ This policy currently applies to:
 Third-party configuration formats such as Log4j's XML configuration are
 versioned by their owning library and do not use this declaration.
 
+Nenjim Hub reads only `conf/NenjimHub.conf`; copy
+`conf/NenjimHub.conf.example` before first use and edit the ordered process
+list for the deployment role. The example is never loaded as runtime input.
+
 ## Release log:
 | Date             |   Version      | Description          |
 |:-----------------|:--------------:|----------------------|