fix(config): address review findings in docs and reference.conf

- Remove incorrect DnsConfig Javadoc referencing nonexistent PublishConfig
- Move deprecated activeConnectFactor/connectFactor to end of node block
  in reference.conf with clearer deprecation comment
- Fix double backtick typo in configuration.md (Args.logConfig())
- Fix capitalisation inconsistency in configuration.md table
- Add missing trailing newline to configuration.md
- Clarify nesting depth in configuration-conventions.md: CI gate hard
  ceiling is 5 (historical max); new keys must stay within 3 levels

Co-Authored-By: Claude Sonnet 4.6 <noreply@anthropic.com>

Author: 317787106

common/src/main/java/org/tron/core/config/args/NodeConfig.java

@@ -267,9 +267,6 @@ public static class DynamicConfigSection {
     private long checkInterval = 600;
   }
 
-  /**
-   * All default parameters come from PublishConfig
-   */
   @Getter
   @Setter
   public static class DnsConfig {

common/src/main/resources/reference.conf

@@ -195,11 +195,6 @@ node {
   maxHttpConnectNumber = 50
   minParticipationRate = 0
 
-  # Deprecate, don't use
-  activeConnectFactor = 0.1
-  # Deprecate, don't use
-  connectFactor = 0.6
-
   # WARNING: Some shielded transaction APIs require sending private keys as parameters.
   # Calling these APIs on untrusted or remote nodes may leak your private keys.
   # It is recommended to invoke them locally for development and testing.
@@ -397,6 +392,11 @@ node {
   # Open history query APIs on lite FullNode (may return null for some queries)
   openHistoryQueryWhenLiteFN = false
 
+  # Deprecated: these fields were used by the old connection-factor algorithm.
+  # They are still accepted from user config for backward compatibility but have no effect.
+  activeConnectFactor = 0.1
+  connectFactor = 0.6
+
   jsonrpc {
     # Note: Before release_4.8.1, if you turn on jsonrpc and run it for a while and then turn it off,
     # you will not be able to get the data from eth_getLogs for that period of time. Default: false

docs/configuration-conventions.md

@@ -81,16 +81,17 @@ A HOCON key named `isOpenFullTcpDisconnect` produces the setter `setIsOpenFullTc
 
 ## Nesting Depth
 
-Keep nesting to **at most 3 levels** from the top-level section. Deeper nesting creates long key paths that are hard to override in `config.conf` and require more boilerplate inner bean classes.
+The CI gate enforces a hard ceiling of **5 levels** (the historical maximum in `reference.conf`). New parameters must stay within **3 levels** from the top-level section. The gap between 3 and 5 is reserved for legacy paths that already exist — it is not a license to add new deep keys.
 
 ```
 level 1:  node { ... }
 level 2:  node { rpc { ... } }
-level 3:  node { rpc { flowControl { ... } } }   ← maximum
-level 4+: node { rpc { flowControl { window { ... } } } }   ← avoid
+level 3:  node { rpc { flowControl { ... } } }   ← limit for new keys
+level 4+: node { rpc { flowControl { window { ... } } } }   ← legacy only; do not add new keys here
+level 6+: rejected by CI gate unconditionally
 ```
 
-Each level of nesting requires a corresponding inner static bean class. If you find yourself going 4 levels deep, consider flattening by moving the leaf keys up one level or using a longer camelCase key at level 2.
+Each level of nesting requires a corresponding inner static bean class. If you find yourself going beyond 3 levels deep, consider flattening by moving the leaf keys up one level or using a longer camelCase key at level 2.
 
 ## Adding a New Parameter: Checklist
 
@@ -190,7 +191,7 @@ nc.shutdownBlockTime = section.hasPath("shutdown.BlockTime")
 | Standard camelCase | `maxConnections` | `MaxConnections`, `max_connections`, `max-connections` |
 | No `is` prefix | `openFullTcpDisconnect` | `isOpenFullTcpDisconnect` |
 | No all-caps acronym prefix | `pbftExpireNum`, `pBFTPort`* | `PBFTExpireNum` |
-| Nesting ≤ 3 levels | `node.rpc.maxMessageSize` | `node.rpc.limits.size.max` |
+| New keys: nesting ≤ 3 levels | `node.rpc.maxMessageSize` | `node.rpc.limits.size.max` |
 | Java field name matches HOCON key exactly | field `maxConnections` ↔ key `maxConnections` | field `maxConns` ↔ key `maxConnections` |
 
 \* `PBFTEnable` / `PBFTPort` are legacy exceptions; do not model new keys after them.

docs/configuration.md

@@ -9,7 +9,7 @@ java-tron uses [Typesafe Config](https://github.com/lightbend/config) and applie
 | File | Location | Purpose |
 |------|----------|---------|
 | `reference.conf` | Bundled inside the jar (`common` module) | Declares every parameter with its default value |
-| `config.conf` | bundled template and optionally edited & passed via -c | Overrides only the values that differ from defaults |
+| `config.conf` | Bundled template, optionally edited & passed via -c | Overrides only the values that differ from defaults |
 
 **Loading priority:** values in `config.conf` always win. Any parameter that your `config.conf` omits is automatically filled in from `reference.conf`. You never need to copy the entire `reference.conf` into your own file — only include the parameters you actually want to change.
 
@@ -242,7 +242,7 @@ Not all parameters support hot-reload. Parameters that affect node identity, gen
 
 ## Viewing Effective Configuration
 
-At startup, the node unconditionally logs a summary of key parameters under `Net config`, `Backup config`, `Code version`, `DB config`, and `shutDown config` headers (see `Args.logConfig()`` for the exact fields). For parameters not in this summary, you must inspect runtime behavior or consult `reference.conf` directly — the full merged configuration is never dumped.
+At startup, the node unconditionally logs a summary of key parameters under `Net config`, `Backup config`, `Code version`, `DB config`, and `shutDown config` headers (see `Args.logConfig()` for the exact fields). For parameters not in this summary, you must inspect runtime behavior or consult `reference.conf` directly — the full merged configuration is never dumped.
 
 Note: `node.openPrintLog` is a separate flag that controls runtime verbosity of P2P/inventory/pending-tx logs, not startup config logging.
 
@@ -254,4 +254,4 @@ Every parameter with its default value and an inline comment is documented in:
 common/src/main/resources/reference.conf
 ```
 
-When you need the authoritative default for a parameter or want to understand what a key does, consult that file directly.
+When you need the authoritative default for a parameter or want to understand what a key does, consult that file directly.