wao 0.41.0 → 0.41.1

package/cjs/aoconnect-base.js

@@ -868,8 +868,11 @@ var _default = exports["default"] = function _default() {
             case 10:
               evalFrom = _context6.v;
             case 11:
-              // Cranked messages use MU addr as From for AOS trust
-              if (_opt !== null && _opt !== void 0 && _opt["for"]) evalFrom = mu.addr;
+              // Cranked messages historically used MU addr as From. But AOS's
+              // msg.reply targets msg.From, so overwriting From to mu.addr
+              // breaks the X-Reference round-trip for Send().receive(). Only
+              // override when no explicit from is supplied by the caller.
+              if (_opt !== null && _opt !== void 0 && _opt["for"] && !(_opt !== null && _opt !== void 0 && _opt.from)) evalFrom = mu.addr;
               _context6.n = 12;
               return fetch("".concat(p._cu_url, "/cu/evaluate"), {
                 method: "POST",
@@ -1034,9 +1037,13 @@ var _default = exports["default"] = function _default() {
             case 34:
               from = _context6.v;
             case 35:
-              // Cranked messages (inter-process) use MU addr as From for AOS trust
-              // From-Process tag still tracks the originating process
-              if (_opt["for"]) from = mu.addr;
+              // Cranked messages (inter-process) historically used MU addr as
+              // From for AOS trust. But AOS's msg.reply uses msg.From as Target,
+              // so overwriting From to mu.addr breaks the X-Reference round-trip
+              // needed for Send().receive() coroutine resumption. Preserve the
+              // originating process (passed via _opt.from = opt.process from the
+              // outbox-dispatch loop) so replies land back on it.
+              if (_opt["for"] && !_opt.from) from = mu.addr;
               // check: is owner=mu.addr right?
               _owner = (_opt$message_item = opt.message_item) !== null && _opt$message_item !== void 0 && _opt$message_item.owner ? (0, _utils.toAddr)(opt.message_item.owner) : mu.addr;
               _context6.n = 36;

package/esm/aoconnect-base.js

@@ -380,8 +380,11 @@ export default ({ AR, scheduler, mu, su, cu, acc, AoLoader, ArMem } = {}) => {
               })
             }
           }
-          // Cranked messages use MU addr as From for AOS trust
-          if (_opt?.for) evalFrom = mu.addr
+          // Cranked messages historically used MU addr as From. But AOS's
+          // msg.reply targets msg.From, so overwriting From to mu.addr
+          // breaks the X-Reference round-trip for Send().receive(). Only
+          // override when no explicit from is supplied by the caller.
+          if (_opt?.for && !_opt?.from) evalFrom = mu.addr
           const cuResult = await fetch(`${p._cu_url}/cu/evaluate`, {
             method: "POST",
             headers: { "Content-Type": "application/json" },
@@ -465,9 +468,13 @@ export default ({ AR, scheduler, mu, su, cu, acc, AoLoader, ArMem } = {}) => {
             })
           }
         }
-        // Cranked messages (inter-process) use MU addr as From for AOS trust
-        // From-Process tag still tracks the originating process
-        if (_opt.for) from = mu.addr
+        // Cranked messages (inter-process) historically used MU addr as
+        // From for AOS trust. But AOS's msg.reply uses msg.From as Target,
+        // so overwriting From to mu.addr breaks the X-Reference round-trip
+        // needed for Send().receive() coroutine resumption. Preserve the
+        // originating process (passed via _opt.from = opt.process from the
+        // outbox-dispatch loop) so replies land back on it.
+        if (_opt.for && !_opt.from) from = mu.addr
         // check: is owner=mu.addr right?
         const _owner = opt.message_item?.owner
           ? toAddr(opt.message_item.owner)

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "wao",
-  "version": "0.41.0",
+  "version": "0.41.1",
   "bin": {
     "wao": "./cjs/cli.js",
     "wao-esm": "./esm/cli.js"