sisyphi 1.1.23 → 1.1.25

package/dist/deploy/shared/cloud-init.yaml.tpl

@@ -73,9 +73,12 @@ runcmd:
   - curl -fsSL https://deb.nodesource.com/setup_22.x | bash -
   - DEBIAN_FRONTEND=noninteractive apt-get install -y nodejs
 
-  # 3. Tailscale. --ssh enables Tailscale SSH on top of system SSH.
+  # 3. Tailscale. We deliberately do NOT pass --ssh: Tailscale SSH would
+  # intercept port 22 on the tailscale0 interface and require a browser-
+  # based check (per the user's tailnet ACL), blocking key-based access.
+  # System OpenSSH on tailscale0 with the user's pubkey is simpler.
   - curl -fsSL https://tailscale.com/install.sh | sh
-  - tailscale up --authkey='${ts_authkey}' --hostname='${hostname}' --ssh
+  - tailscale up --authkey='${ts_authkey}' --hostname='${hostname}'
 
   # 4. Firewall. Public 22 stays denied; tailscale0 fully open.
   - ufw default deny incoming
@@ -116,4 +119,4 @@ runcmd:
 %{ endif ~}
 
   # Done — marker for `sisyphus deploy <provider> up` polling loop.
-  - echo "sisyphus-cloud-init: done" >> /var/log/cloud-init-output.log
+  - echo "sisyphus cloud-init done" >> /var/log/cloud-init-output.log

package/dist/templates/agent-plugin/skills/humanloop/SKILL.md

@@ -142,6 +142,7 @@ EOF
 ## Submission notes
 
 - The deck is validated at submit (precise errors — trust them).
-- `bodyPath` lets an interaction point at a markdown file (e.g. a completion summary) instead of inlining the markdown in JSON.
+- `kind` is an enum: `notify` | `validation` | `decision` | `context` | `error`. No other values accepted (see the table above for which to pick).
+- `bodyPath` points at a markdown file instead of inlining the body in JSON. The path is resolved **relative to the deck JSON's directory** and must stay inside it (no `..`, no symlinks out, no absolute paths pointing elsewhere). Practical pattern: write the deck JSON next to its body file — e.g. both inside `$SISYPHUS_SESSION_DIR/context/` — and use a basename like `"completion-summary.md"`. Mutually exclusive with `body`.
 - On completion, stdout is one line of JSON: `{responses, completedAt}`. Parse `responses[]` and dispatch on each interaction's `id`.
 - See `sisyphus ask -h` for the full CLI surface.

package/dist/templates/orchestrator-plugin/skills/humanloop/SKILL.md

@@ -144,6 +144,7 @@ EOF
 ## Submission notes
 
 - The deck is validated at submit (precise errors — trust them).
-- `bodyPath` lets an interaction point at a markdown file (e.g. a completion summary) instead of inlining the markdown in JSON.
+- `kind` is an enum: `notify` | `validation` | `decision` | `context` | `error`. No other values accepted (see the table above for which to pick).
+- `bodyPath` points at a markdown file instead of inlining the body in JSON. The path is resolved **relative to the deck JSON's directory** and must stay inside it (no `..`, no symlinks out, no absolute paths pointing elsewhere). Practical pattern: write the deck JSON next to its body file — e.g. both inside `$SISYPHUS_SESSION_DIR/context/` — and use a basename like `"completion-summary.md"`. Mutually exclusive with `body`.
 - On completion, stdout is one line of JSON: `{responses, completedAt}`. Parse `responses[]` and dispatch on each interaction's `id`.
 - See `sisyphus ask -h` for the full CLI surface.