@dev.sail.money/sailor 1.3.0-210 → 1.3.0-95

package/packages/sdk/dist/intelligence.d.ts

@@ -5,7 +5,7 @@
  * Do not edit manually — run `pnpm build` to regenerate.
  *
  * Spec version : 1.2.0
- * Generated at : 2026-06-25T14:29:20.609Z
+ * Generated at : 2026-06-26T09:46:27.970Z
  */
 export declare const SAIL_INTELLIGENCE_BASE_URL = "https://api.sail.money";
 export declare const SAIL_INTELLIGENCE_DOCS_URL = "https://api.sail.money/docs";

package/packages/sdk/dist/intelligence.js

@@ -5,7 +5,7 @@
  * Do not edit manually — run `pnpm build` to regenerate.
  *
  * Spec version : 1.2.0
- * Generated at : 2026-06-25T14:29:20.609Z
+ * Generated at : 2026-06-26T09:46:27.970Z
  */
 export const SAIL_INTELLIGENCE_BASE_URL = "https://api.sail.money";
 export const SAIL_INTELLIGENCE_DOCS_URL = "https://api.sail.money/docs";

package/scripts/pack.mjs

@@ -0,0 +1,21 @@
+// Build the publishable npm package as a .tgz archive — the npm analog of `docker build`.
+// Packs under the canonical published name (@sail.money/sailor) so the artifact installs and
+// resolves exactly like the registry package; CI applies the same rename at publish time.
+// ponytail: .tgz is npm's native archive (install offline with `npm i ./<file>.tgz`). For a
+// literal .zip, unpack the tgz and re-zip — not added until something actually needs it.
+import { execSync } from "node:child_process";
+import { readFileSync, writeFileSync } from "node:fs";
+
+const PKG = "package.json";
+const CANONICAL = "@sail.money/sailor";
+
+const original = readFileSync(PKG, "utf8");
+try {
+  const manifest = JSON.parse(original);
+  if (manifest.name !== CANONICAL) {
+    writeFileSync(PKG, `${JSON.stringify({ ...manifest, name: CANONICAL }, null, 2)}\n`);
+  }
+  execSync("npm pack", { stdio: "inherit" }); // emits sail.money-sailor-<version>.tgz
+} finally {
+  writeFileSync(PKG, original); // restore the working manifest verbatim
+}

package/templates/default/.agents/skills/sail-servers/SKILL.md

@@ -13,11 +13,13 @@ Two distinct local servers. Both are per-project, both write state under `.sail/
 sailor ui start    # spawns a detached Express server, prints the URL, returns immediately
 sailor ui status   # ● running  http://localhost:<port>  (pid N)
 sailor ui stop     # SIGTERM via the pid file
+sailor ui start --expose tailscale   # also serve it on the tailnet over HTTPS (opt-in)
 ```
 
-- Port: deterministic per project — `3333 + (hash(projectPath) % 667)`, i.e. somewhere in 3333–3999, bumped to the next free port if taken. **Do not assume 3333** — always use the URL the command prints or read `.sail/runtime/ui.json` (`{ pid, port, startedAt }`).
+- Port: deterministic per project — `3333 + (hash(projectPath) % 667)`, i.e. somewhere in 3333–3999, bumped to the next free port if taken. **Do not assume 3333** — always use the URL the command prints or read `.sail/runtime/ui.json` (`{ pid, port, startedAt, exposed }`).
 - The server serves the pre-built React app (`SERVE_DIST=1`) and a local `/api` that reads `.sail/` state (`SAIL_DIR` env).
 - `ui start` does not block — no `&` needed.
+- `--expose tailscale` (optional): proxies the dashboard onto the operator's tailnet over HTTPS via `tailscale serve` (tailnet-private, never `funnel`). Requires `tailscale` installed + logged in, and Serve + HTTPS enabled for the tailnet (else the command prints the enable link). `ui stop` tears the proxy down. To allow extra browser origins, set `SAILOR_CORS_ORIGINS` (comma-separated; the local origin is always allowed).
 
 ## Signing station — `sailor station`