Regenerate configuration.leaf, which is the page people actually read

Scripts/check-doc-pages.py failed the PR: configuration.leaf is generated from
docs/CONFIGURATION.md and hashed against it, so documenting a variable without
rebuilding the page leaves the served page saying something older.

Build with FLAMENET_E2E_DIR pointed at the engine AT THE PIN in .e2e-ref. With
a sibling checkout on the engine's main instead, spec.leaf and engine.leaf
regenerate from unpinned content and the check fails on two more pages.

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>

Resources/Views/configuration.leaf

@@ -3,7 +3,7 @@
 <!-- GENERATED by Scripts/build-doc-pages.sh from docs/CONFIGURATION.md.
      Edits made HERE are deleted the next time that script runs.
      Change the markdown source and re-run it.
-     source-sha256: 990bef688fcc2b5c -->
+     source-sha256: 7c9841556ca1f5eb -->
 <article class="band doc doc-generated">
   <div class="wrap wrap-narrow">
 <h1 id="configuring-a-relay">Configuring a relay</h1>
@@ -1325,6 +1325,17 @@ naming somebody else.</td>
 mailboxes.</td>
 </tr>
 <tr>
+<td><code>FN_FUNDING_MANIFESTS</code></td>
+<td>unset</td>
+<td>The <code>funding.json</code> manifests this domain vouches for,
+whitespace or comma separated, served at
+<code>/.well-known/funding-manifest-urls</code>. Anything not starting
+with <code>https://</code> is dropped. Unset, that path is a 404: the
+manifest carries an operator's legal name, contact address and bank
+details, so a relay somebody else runs must not tell a funder that
+donations for it reach us.</td>
+</tr>
+<tr>
 <td><code>FN_ANDROID_VERSION_CODE</code>,
 <code>FN_ANDROID_VERSION_NAME</code></td>
 <td>unset</td>