feat(node): per-file upload ceiling is an operator setting, default 8 GB

Was a 4 GB constant in webrtc_server.py, the same on a small board and on
a machine holding a library. Now max_upload_gb in node.toml, on the Node
page and via `meshbay-node transfers max-size`, read from the transport
context per chunk so a change reaches an upload already running.

MESHBAY_DESIGN.md §6.4; §15.3 records a defect found beside it.

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

1 files changed, 8 insertions, 0 deletions

diff --git a/packages/meshbay-hub/src/meshbay_hub/static/node-page.js b/packages/meshbay-hub/src/meshbay_hub/static/node-page.js
index 0f75edc..2edcbab 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/node-page.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/node-page.js
@@ -1068,6 +1068,14 @@ export function NodePage({ groups, token, username }) {
               </div>
             </label>
             <label class="node-setting">
+              <span class="node-setting-label">${t('node.setting_max_upload')}</span>
+              <div class="node-setting-input">
+                <input type="number" min="0.1" step="0.5" value=${editSettings.max_upload_gb}
+                  onInput=${e => setEditSettings(s => ({...s, max_upload_gb: parseFloat(e.target.value) || 0.1}))} />
+                <span class="node-setting-unit">${t('node.setting_unit_gb')}</span>
+              </div>
+            </label>
+            <label class="node-setting">
               <span class="node-setting-label">${t('node.setting_transcode')}</span>
               <div class="node-setting-input">
                 <input type="checkbox" checked=${editSettings.transcode_incompatible_video}