npm - @dev.sail.money/sailor - Versions diffs - 0.0.2-20 → 0.0.2-22 - Mend

@dev.sail.money/sailor 0.0.2-20 → 0.0.2-22

This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.

Files changed (122) hide show

package/packages/ui/dist/assets/{walletconnect-CfkgbqAq.js → walletconnect-Glte9ia7.js} RENAMED Viewed

@@ -1,4 +1,4 @@
-import{F as l}from"./core-BN9UnMip.js";import"./index-DJQDBPts.js";import"./events-DrkgavVp.js";import"./index.es-D6UPoR2j.js";import"./fallback-Y8-BiCNG.js";const o=l`<svg fill="none" viewBox="0 0 96 67">
+import{F as l}from"./core-B_rvnvkC.js";import"./index-Dc9_WV0G.js";import"./events-CkyJn32_.js";import"./index.es-CvyDIsY4.js";import"./fallback-BL3U4ZRT.js";const o=l`<svg fill="none" viewBox="0 0 96 67">
   <path
     fill="currentColor"
     d="M25.32 18.8a32.56 32.56 0 0 1 45.36 0l1.5 1.47c.63.62.63 1.61 0 2.22l-5.15 5.05c-.31.3-.82.3-1.14 0l-2.07-2.03a22.71 22.71 0 0 0-31.64 0l-2.22 2.18c-.31.3-.82.3-1.14 0l-5.15-5.05a1.55 1.55 0 0 1 0-2.22l1.65-1.62Zm56.02 10.44 4.59 4.5c.63.6.63 1.6 0 2.21l-20.7 20.26c-.62.61-1.63.61-2.26 0L48.28 41.83a.4.4 0 0 0-.56 0L33.03 56.21c-.63.61-1.64.61-2.27 0L10.07 35.95a1.55 1.55 0 0 1 0-2.22l4.59-4.5a1.63 1.63 0 0 1 2.27 0L31.6 43.63a.4.4 0 0 0 .57 0l14.69-14.38a1.63 1.63 0 0 1 2.26 0l14.69 14.38a.4.4 0 0 0 .57 0l14.68-14.38a1.63 1.63 0 0 1 2.27 0Z"

package/packages/ui/dist/assets/{warning-circle-BfOqu3HN.js → warning-circle-j-3V4KTo.js} RENAMED Viewed

@@ -1,4 +1,4 @@
-import{F as r}from"./core-BN9UnMip.js";import"./index-DJQDBPts.js";import"./events-DrkgavVp.js";import"./index.es-D6UPoR2j.js";import"./fallback-Y8-BiCNG.js";const a=r`<svg fill="none" viewBox="0 0 20 20">
+import{F as r}from"./core-B_rvnvkC.js";import"./index-Dc9_WV0G.js";import"./events-CkyJn32_.js";import"./index.es-CvyDIsY4.js";import"./fallback-BL3U4ZRT.js";const a=r`<svg fill="none" viewBox="0 0 20 20">
   <path
     fill="currentColor"
     d="M11 6.67a1 1 0 1 0-2 0v2.66a1 1 0 0 0 2 0V6.67ZM10 14.5a1.25 1.25 0 1 0 0-2.5 1.25 1.25 0 0 0 0 2.5Z"

package/packages/ui/dist/assets/{x-CxAcJv-O.js → x-Bcc52c_T.js} RENAMED Viewed

@@ -1,4 +1,4 @@
-import{F as l}from"./core-BN9UnMip.js";import"./index-DJQDBPts.js";import"./events-DrkgavVp.js";import"./index.es-D6UPoR2j.js";import"./fallback-Y8-BiCNG.js";const a=l`<svg fill="none" viewBox="0 0 41 40">
+import{F as l}from"./core-B_rvnvkC.js";import"./index-Dc9_WV0G.js";import"./events-CkyJn32_.js";import"./index.es-CvyDIsY4.js";import"./fallback-BL3U4ZRT.js";const a=l`<svg fill="none" viewBox="0 0 41 40">
   <g clip-path="url(#a)">
     <path fill="#000" d="M.8 0h40v40H.8z" />
     <path

package/packages/ui/dist/index.html CHANGED Viewed

@@ -5,7 +5,7 @@
     <meta name="viewport" content="width=device-width, initial-scale=1.0" />
     <meta name="theme-color" content="#040b16" />
     <title>Sail - Unlocking Personalized Money</title>
-    <script type="module" crossorigin src="/assets/index-DJQDBPts.js"></script>
+    <script type="module" crossorigin src="/assets/index-Dc9_WV0G.js"></script>
     <link rel="stylesheet" crossorigin href="/assets/index-DDKDa0s2.css">
   </head>
   <body>

package/templates/default/AGENTS.md CHANGED Viewed

@@ -40,6 +40,10 @@ If the user's first message is an npm install command, run it, then present the
 In the browser. Run `sailor ui start`, open the printed URL, connect your owner wallet, choose your network, and deploy your SMA. Then create your agent wallet — a separate signing key I use to submit transactions on your behalf. You need gas in both: the owner wallet to deploy and sign the mandate; the agent wallet to submit transactions once the agent is running. The owner key never leaves the browser.
+**Deterministic address (salt):** every SMA deployment uses a CREATE2 salt. The CLI defaults to salt `0`, giving you a predictable address you can verify before spending gas: `sailor account predict --owner <your-wallet> --manager <agent-wallet>`. The kernel binds the salt to your owner wallet, agent (manager) wallet, and fee policy — create your agent wallet first, then predict. The salt is saved in `.sail/account.json` automatically. All supported chains (Ethereum, Base, Arbitrum, Unichain, plus testnets) share the same protocol addresses via CREATE2, so the same owner, manager, and salt produce the **same SMA address on every chain**.
+**Multi-chain deployment:** once your SMA is live on one chain, deploy it at the same address on any other supported chain with `sailor account deploy-chain --chain <id>` (e.g. `--chain 42161` for Arbitrum). The owner approves the deployment in the browser; no new salt or agent wallet needed. Run `sailor account predict` first to confirm the address matches.
 ## Stage 2 — Define your strategy
 Tell me what you want your agent to do. I'll ask the right questions, establish the on-chain bounds with you (tokens, amounts, slippage, venues), and set up your RPC endpoint once you've chosen your chain. Blank slate — you define the strategy.
@@ -54,7 +58,22 @@ Permission contracts live in `mandates/`. The user authors, reviews, and owns th
 ```bash
 forge build
-sailor mandate deploy --contract <Name> --attach --sma <SMA>
+sailor mandate deploy --contract <Name> --sma <SMA>   # deploy only — do NOT --attach yet
+```
+Before AUTHORIZING (attaching) the permission, BACK the plain-English claims with an actual on-chain probe. `evaluate()` lives on the deployed contract, so deploy first, then — before the irreversible authorization — generate sample calls from the user's stated strategy (ones the permission MUST accept and ones it MUST reject) and run them through `sailor mandate simulate`. This is an off-chain `eth_call` (no gas, no signing) that reports what the permission's `evaluate()` returns for each call, and flags any target with no contract code (a wrong or wrong-chain address):
+```bash
+# one call inline, or a batch via JSON
+sailor mandate simulate --address <PermissionOrName> --sma <SMA> \
+  --target <addr> --calldata <hex> --expect pass
+sailor mandate simulate --address <PermissionOrName> --sma <SMA> --calls calls.json
+```
+`calls.json` is an array of `{ target, calldata, value?, expect: "pass"|"fail", label }`. A mismatch between `expect` and the actual result exits non-zero — do not authorize until every sample matches. Simulate proves what the permission DOES; it does not guarantee it is correct.
+```bash
+sailor mandate attach --address <PermissionOrName> --sma <SMA>   # authorize, once simulate is clean
 ```
 Registration requires the owner to sign in the browser. If the wrong wallet is connected, the CLI rejects it.

package/packages/ui/dist/assets/cursor-BWdjWDLC.js DELETED Viewed

@@ -1,3 +0,0 @@
-import{F as o}from"./core-BN9UnMip.js";import"./index-DJQDBPts.js";import"./events-DrkgavVp.js";import"./index.es-D6UPoR2j.js";import"./fallback-Y8-BiCNG.js";const l=o` <svg fill="none" viewBox="0 0 13 4">
-  <path fill="currentColor" d="M.5 0h12L8.9 3.13a3.76 3.76 0 0 1-4.8 0L.5 0Z" />
-</svg>`;export{l as cursorSvg};