@reefclaw/connect 0.1.35 → 0.1.36

package/assets/plugin/tools/hl-provision-agent-wallet.js

@@ -96,22 +96,40 @@ export async function hlProvisionAgentWalletTool(args, deps) {
         const derived = await deriveAddressFromPrivateKey(existingKey);
         if (derived.ok) {
             const masterMatches = existingMaster != null && existingMaster.toLowerCase() === walletAddress.toLowerCase();
-            // ★ Honour a CHANGED network on the resume path. The same keypair is
-            // valid on both Hyperliquid networks, so switching mainnet<->testnet
-            // must not require regenerating the wallet — but the stored flag has to
-            // follow, or the box boots against the network the operator did NOT
-            // pick. Before this, unticking "Use Hyperliquid testnet" after
-            // provisioning silently kept testnet:true, and the approval was signed
-            // for Testnet while the operator believed they were on mainnet
-            // (observed live 2026-08-03).
-            if (masterMatches && existingTestnet !== testnet) {
+            // ★ Re-ACTIVATE the venue on resume (E2E audit 2026-08-11 #6) and honour
+            // a CHANGED network in the same write.
+            //
+            // Venue: the resume path used to write NOTHING unless the network flag
+            // moved — so a box whose active venue was still binance (HL provisioned
+            // earlier and switched back, or a live-Binance box that just clicked
+            // through the confirm-switch dialog above) kept `venue:'binance'` on
+            // disk. hl_agent_wallet_status only reports configured when
+            // `exchange.venue==='hyperliquid'`, so the guided flow dead-ended
+            // polling configured:false forever, and the confirm dialog "switched"
+            // nothing. By this point the venue-switch confirm gate has already run,
+            // so the activation write is authorized. buildVenueExchangeConfig with
+            // empty fields activates the venue while keeping BOTH venues'
+            // credentials (the merge contract).
+            //
+            // Network: the same keypair is valid on both Hyperliquid networks, so
+            // mainnet<->testnet must not require regenerating — but the stored flag
+            // has to follow, or the box boots against the network the operator did
+            // NOT pick (observed live 2026-08-03: approval signed for Testnet while
+            // the operator believed mainnet).
+            const needsVenueActivation = fromVenue !== 'hyperliquid';
+            if (masterMatches && (needsVenueActivation || existingTestnet !== testnet)) {
                 try {
                     updatePluginConfig({ exchange: buildVenueExchangeConfig(existingExchange, 'hyperliquid', {}, testnet) }, deps.configPath);
+                    if (needsVenueActivation) {
+                        logger.info(TAG, 'venue re-activated: hyperliquid (existing agent wallet resumed)');
+                    }
+                    if (existingTestnet !== testnet) {
+                        logger.info(TAG, `network switched to ${testnet ? 'TESTNET' : 'MAINNET'} (same agent wallet)`);
+                    }
                     existingTestnet = testnet;
-                    logger.info(TAG, `network switched to ${testnet ? 'TESTNET' : 'MAINNET'} (same agent wallet)`);
                 }
                 catch (err) {
-                    logger.warn(TAG, `could not persist network change: ${err instanceof Error ? err.message : String(err)}`);
+                    logger.warn(TAG, `could not persist venue/network change: ${err instanceof Error ? err.message : String(err)}`);
                 }
             }
             return {

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@reefclaw/connect",
-  "version": "0.1.35",
+  "version": "0.1.36",
   "description": "One-command installer that connects your OpenClaw agent to ReefClaw (paper trading, no exchange keys).",
   "type": "module",
   "bin": {