docs: move regen instructions to DEVELOPMENT.md, fix orphaned contrast sentence

The "regenerate this table via make docs" note is a maintainer instruction,
not something a node operator needs to see, and referenced a Makefile
target that no longer exists (it's cli-docs). Dropped it from the two
operator-facing options pages and folded the instruction into
DEVELOPMENT.md's existing regeneration section instead.

Also fixed a sentence in the legacy did:nuts client-authentication section
that only made sense next to the did:x509 section it used to sit beside
in certificates.rst before this PR split them into separate pages ("Nuts-
node versions before v6 only use..." read as an orphaned historical claim
once the did:x509 contrast it was set up against moved elsewhere).

Assisted by AI
Claude-Session: https://claude.ai/code/session_01VJiY69SPaAf1mxERAWK1SG

Author: reinkrul

DEVELOPMENT.md

@@ -63,7 +63,9 @@ All files to be included can be generated using:
 make cli-docs
 ```
 
-This regenerates the config-option and CLI reference tables from code.
+This regenerates the config-option and CLI reference tables from code, and the root `README.rst` from `README_template.rst`.
+Whenever you add, remove, or change a config flag or CLI command, run this and commit the regenerated files —
+don't hand-edit `docs/pages/configuration/server_options*.rst` or `docs/pages/operations/cli-reference.rst`.
 
 If needed, you can also build the documentation locally in `/docs/_build` using Docker; see [docs/README.md](docs/README.md).
 

README.rst

@@ -307,13 +307,6 @@ The following options can be configured on the server:
       -
       - Base URL of the AuthZen PDP endpoint. Required when any credential profile uses scope_policy 'dynamic'; the node refuses to start if such a profile is configured but this flag is empty.
 
-This table is automatically generated using the configuration flags in the core and engines. When they're changed
-the options table must be regenerated using the Makefile:
-
-.. code-block:: shell
-
-    $ make docs
-
 If your use case still uses ``did:nuts`` DIDs and/or the gRPC network, there's an additional (deprecated) options
 table in :ref:`Legacy did:nuts configuration <legacy-did-nuts-configuration>`.
 

docs/pages/configuration/legacy-did-nuts.rst

@@ -13,18 +13,11 @@ The following table contains additional (deprecated) options that are relevant f
 
 .. include:: server_options_didnuts.rst
 
-This table is automatically generated using the configuration flags in the core and engines. When they're changed
-the options table must be regenerated using the Makefile:
-
-.. code-block:: shell
-
-    $ make docs
-
 Client authentication
 **********************
 
-Nuts-node versions before v6 only use TLS certificates for client authentication on the ``/n2n`` endpoints and in the ``gRPC Nuts network``.
-The Nuts-node also validates the client certificates used by its peers on the ``gRPC network`` when a new connection is established, and periodically after that as long as the connection exists.
+The ``/n2n`` endpoints and the ``gRPC Nuts network`` use TLS certificates for client authentication.
+The Nuts-node validates the client certificates used by its peers on the ``gRPC network`` when a new connection is established, and periodically after that as long as the connection exists.
 To do this, all trusted certificate chains must be configured in ``tls.truststorefile``.
 See :ref:`Certificate revocation handling <certificate-revocation-handling>` for how CRL checks and soft-fail behavior work for these certificates.
 The ``gRPC Nuts network`` and ``/n2n`` endpoints are deprecated and will be removed in the future.

docs/pages/configuration/options.rst

@@ -50,13 +50,6 @@ The following options can be configured on the server:
 
 .. include:: server_options.rst
 
-This table is automatically generated using the configuration flags in the core and engines. When they're changed
-the options table must be regenerated using the Makefile:
-
-.. code-block:: shell
-
-    $ make docs
-
 If your use case still uses ``did:nuts`` DIDs and/or the gRPC network, there's an additional (deprecated) options
 table in :ref:`Legacy did:nuts configuration <legacy-did-nuts-configuration>`.