@pipod/cli 0.1.15 → 0.1.16

package/docs/workspace-seeding.md

@@ -74,6 +74,12 @@ starts at once; the server also opens the gate on its own after a timeout, so a
 dies mid-seed never strands the pod. Configured projects keep their post-start copy and do not
 arm the gate.
 
+A seed only ever fills an empty workdir. When init scripts (or the image) have already
+populated it by the time provisioning finishes, as a template whose init clones its
+repositories does, the server records the seed as `skipped` and starts Pi with the pod. The
+client then sends nothing: no clone request, no archive. Older servers leave the gate armed,
+and the client sends the seed for the routes to refuse.
+
 ## Older servers
 
 A server with a strict launch schema rejects the `workspaceSeed` flag; the client retries the
@@ -106,6 +112,7 @@ on the sandbox backend:
 8. **Nested pod launch** — from inside a pod, launch a child from a source-less directory;
    symlinks are skipped with a warning, files arrive.
 9. **Template/init-script collision** — `--template <one whose init script clones>`; expect
-   `workspace already populated … leaving it in place`.
+   `workspace already populated … nothing sent`, no archive build or upload, and the
+   pod's `workspaceSeed` reported `skipped`.
 10. **`--no-seed`, `--dry-run`, `fork`, `--on`** — none create a transfer; `--dry-run` prints
     the decision and creates no pod.

package/man/pipod-config.5

@@ -1,4 +1,4 @@
-.TH "PIPOD\-CONFIG" "5" "October 2026" "0.1.15"
+.TH "PIPOD\-CONFIG" "5" "October 2026" "0.1.16"
 .SH "NAME"
 \fBpipod-config\fR \- pi pod configuration files
 .SH SYNOPSIS

package/man/pipod.1

@@ -1,4 +1,4 @@
-.TH "PIPOD" "1" "October 2026" "0.1.15"
+.TH "PIPOD" "1" "October 2026" "0.1.16"
 .SH "NAME"
 \fBpipod\fR \- run pi coding\-agent sessions in server\-managed pods
 .SH SYNOPSIS
@@ -277,7 +277,8 @@ or \.pi\-pod/env\. Private\-remote
 credentials are forwarded only after a prompt (\fB\-\-yes\fP approves it) and are never stored\.
 \fB\-\-dry\-run\fP prints the decision without prompting or creating a pod\. Forks, reused pods,
 \fB\-\-on\fP co\-location, and \fB\-\-no\-seed\fP never seed\. A project with a \.pi\-pod/config\.json gets its
-workspace from its init scripts instead\.
+workspace from its init scripts instead\. When a template's init scripts have already
+populated the workspace, nothing is sent\.
 .P
 Arguments after \fB\-\-\fP go to pi: prompt words start the session, and \fB\-\-model\fP, \fB\-\-thinking\fP,
 and \fB\-\-tui\-mode\fP apply to this launch\. Per\-launch Pi resources (\fB\-\-extension\fP, \fB\-\-skill\fP,

package/man/pipod.1.md

@@ -266,7 +266,8 @@ or .pi-pod/env. Private-remote
 credentials are forwarded only after a prompt (`--yes` approves it) and are never stored.
 `--dry-run` prints the decision without prompting or creating a pod. Forks, reused pods,
 `--on` co-location, and `--no-seed` never seed. A project with a .pi-pod/config.json gets its
-workspace from its init scripts instead.
+workspace from its init scripts instead. When a template's init scripts have already
+populated the workspace, nothing is sent.
 
 Arguments after `--` go to pi: prompt words start the session, and `--model`, `--thinking`,
 and `--tui-mode` apply to this launch. Per-launch Pi resources (`--extension`, `--skill`,

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@pipod/cli",
-  "version": "0.1.15",
+  "version": "0.1.16",
   "description": "Run pi coding-agent sessions in server-managed pods",
   "type": "module",
   "license": "AGPL-3.0-only",