@codyswann/lisa 2.330.0 → 2.331.0

package/plugins/src/base/skills/lisa-setup-remote-env/scripts/toolchain.mjs

@@ -334,6 +334,26 @@ export function assertPinned(tool) {
     }
     return;
   }
+  // A tree carries the same checksum obligation and one more: which file inside
+  // it is the entry point. There is no sane default — the archive root is a
+  // directory, so guessing would install a directory as a binary.
+  if (tool.install === "release-tree") {
+    if (!tool.url || !tool.sha256) {
+      throw new Error(
+        `${tool.name}: a release-tree install needs both url and sha256.\n` +
+          `A version bump must move the checksum in the same reviewed commit.`
+      );
+    }
+    if (!tool.binary) {
+      throw new Error(
+        `${tool.name}: a release-tree install needs "binary" — the path to the ` +
+          `entry point INSIDE the archive, such as "maestro/bin/maestro".\n` +
+          `Unlike the single-file kinds there is nothing to fall back to: the ` +
+          `archive root is a directory.`
+      );
+    }
+    return;
+  }
   if (tool.install === "npm-global") {
     if (!tool.package)
       throw new Error(`${tool.name}: npm-global install needs a package`);
@@ -341,6 +361,6 @@ export function assertPinned(tool) {
   }
   throw new Error(
     `${tool.name}: unknown install method "${tool.install}".\n` +
-      `Supported: release-zip, release-tar, npm-global.`
+      `Supported: release-zip, release-tar, release-tree, npm-global.`
   );
 }

package/plugins/src/base/skills/lisa-setup-workstation/SKILL.md

@@ -25,15 +25,36 @@ repository, and nothing here duplicates that manifest.
 
 ## Usage
 
+**Start here — this is the entry point that presumes nothing:**
+
+```sh
+npx -y @codyswann/lisa@latest workstation             # report what is present and missing
+npx -y @codyswann/lisa@latest workstation --install   # install what is missing
+```
+
+That form needs only Node. No checkout, no agent, no Lisa install — npx resolves
+the package into its own cache.
+
+**Why it matters:** this skill exists to prepare a machine with *no coding agent*
+and *no checkout*. But a skill can only be invoked by typing a slash command into
+an agent, and Lisa ships as a devDependency, so it does not exist until a repo is
+cloned and its dependencies installed. Both are exactly the state this is meant to
+create — so as a skill alone, the bootstrap was unreachable in the one scenario it
+was designed for. The CLI is the way in; the skill is the surface for people who
+already have an agent.
+
+Every flag is the same either way:
+
 ```sh
-node scripts/cli.mjs                              # report what is present and missing
-node scripts/cli.mjs --install                    # install what is missing
-node scripts/cli.mjs --install --agents=claude,codex   # only these agents
-node scripts/cli.mjs --provider=bitwarden         # credential manager (asked if a TTY)
-node scripts/cli.mjs --json                       # machine-readable plan
-node scripts/cli.mjs --print-dockerfile           # an image that runs this same script
+lisa workstation --install --agents=claude,codex   # only these agents
+lisa workstation --provider=bitwarden              # credential manager (asked if a TTY)
+lisa workstation --json                            # machine-readable plan
+lisa workstation --print-dockerfile                # an image that runs this same script
 ```
 
+Inside an agent, `/lisa:setup:workstation` runs the identical script; and the
+script itself is directly runnable as `node scripts/cli.mjs …`.
+
 Nothing is installed or written without `--install`. Exit status is non-zero when a required
 tool is absent or an install fails, so this is usable as a gate.