refactor(spa): stop asking a node what version it is

`MNP_MIN_SUPPORTED` is the version this build speaks, so `check_version`
refuses everything below it at the handshake. Every capability the client was
gating on the node's version is therefore true of every peer it can reach:

  * `supportsSealedUpload` — an upload is sealed or it is not sent;
  * `supportsAppOps` — one `app_directories` op, and no `setVideoRoot` /
    `setAudioRoot` / `setPhotoRoots` wrappers behind it;
  * `supportsTransferSlots` and `Lease._skip()` — a lease is always real, so
    there is no branch where a transfer runs without one;
  * `legacyNode`, the read-only shared-directories table, and the two hints
    telling an operator their node is too old to configure an app.

The version the node declares is still recorded, for diagnostics. Nothing
branches on it, and the comment says so, because a field kept "just in case" is
how the branches came back last time.

`test_mnp_1_0_node_compat.py` goes with them: it existed to hold the fallbacks
in place, and holding a fallback that cannot execute is how a suite starts
lying. The two locale strings for those hints are removed from all ten
catalogues.

Hub suite 872 passed (test_sticky_header deselected — failing before this).

Co-Authored-By: Claude Opus 5 <noreply@anthropic.com>
Claude-Session: https://claude.ai/code/session_01AsoWC3GmhNdwVFomW3QjH3

1 files changed, 0 insertions, 6 deletions

diff --git a/packages/meshbay-hub/src/meshbay_hub/static/group-page.js b/packages/meshbay-hub/src/meshbay_hub/static/group-page.js
index 0f442cf..341d37e 100644
--- a/packages/meshbay-hub/src/meshbay_hub/static/group-page.js
+++ b/packages/meshbay-hub/src/meshbay_hub/static/group-page.js
@@ -145,10 +145,6 @@ function GroupPage({ groupId, group, token, username, userId, userPrefs,
   // destination rather than a set of folders it reads.
   const [chatDirectory, setChatDirectory] = useState('');
   const [chatLinkPreview, setChatLinkPreview] = useState(true);
-  // Whether this node speaks the operations MNP 1.1 added. False for one that
-  // predates them, and the Settings page then offers what that node can
-  // actually do rather than controls whose messages it drops unanswered.
-  const [nodeSupportsAppOps, setNodeSupportsAppOps] = useState(false);
   // MusicBrainz on/off (per-group) — docs/musicbay.md §3.2.
   const [musicbrainzConfig, setMusicbrainzConfig] = useState(null);
   const onPlayQueue = useCallback((tracks, startIndex) => {
@@ -365,7 +361,6 @@ function GroupPage({ groupId, group, token, username, userId, userPrefs,
             || (ack.audio_root ? [ack.audio_root] : []),
           photo: ack.photo_directories || ack.photo_roots || [],
         });
-        setNodeSupportsAppOps(transport.supportsAppOps);
         setChatDirectory(ack.chat_directory || '');
         setChatLinkPreview(ack.chat_link_preview !== false);
         setMusicbrainzConfig({
@@ -827,7 +822,6 @@ function GroupPage({ groupId, group, token, username, userId, userPrefs,
             onScanSettings=${(s) => setScanSettings(s)}
             entries=${entries} nodeDirs=${nodeDirs}
             appSettings=${appSettings}
-            nodeSupportsAppOps=${nodeSupportsAppOps}
             ${/* The saving pane already knows what it asked for; this is so
                   the page's own copy moves at the same time, rather than
                   waiting for the ack it will not be handed (transport.js