@pipod/cli 0.1.11 → 0.1.12

package/docs/workspace-seeding.md

@@ -23,20 +23,23 @@ from a subdirectory seeds the whole repository and prints the subdirectory so it
 
 ## Clone or archive
 
-A clone is chosen only when it reproduces the host checkout exactly. Every check below fails
-closed into an archive with a human-readable reason (`pipod --dry-run` prints it):
+A clone is preferred when the pod can fetch the host's exact **committed HEAD**. Local
+staged, unstaged, and untracked changes do not prevent cloning and are **not copied** by a
+successful clone. The local checkout is left untouched. Every check below fails closed into
+an archive with a human-readable reason (`pipod --dry-run` prints it):
 
 1. inside a git work tree
 2. `origin` exists and rewrites to an `https://` URL (`git@host:x/y.git` and `ssh://` are rewritten; local paths cannot be cloned by a pod)
 3. HEAD is on a branch
-4. no modified, staged, or untracked non-ignored files
-5. the branch has an upstream with no unpushed commits
-6. no initialized submodules, no Git LFS attributes
-7. the pod's egress policy admits the remote host
-8. a live `git ls-remote` shows the remote branch at exactly the local HEAD commit
+4. the branch has an upstream with no unpushed commits
+5. no initialized submodules, no Git LFS attributes
+6. the pod's egress policy admits the remote host
+7. a live `git ls-remote` shows the remote branch at exactly the local HEAD commit
 
 The server clones that exact commit into the empty workdir. If the clone fails for any
-reason, the launch automatically falls back to an archive of the local tree.
+reason, the launch automatically falls back to an archive of the local working tree,
+**including uncommitted changes**. The committed-only behavior applies to successful clones,
+not archive or configured-project copy transports.
 
 An **archive** is a gzip-compressed POSIX tar stream written to a temporary file and streamed
 to `PUT /v1/pods/:id/workspace/archive`. It contains tracked and untracked non-ignored files,
@@ -91,10 +94,12 @@ on the sandbox backend:
    the forwarding prompt; approve; `!git remote -v` inside the pod shows the https URL with no
    token, and `!cat .git/config` holds no token.
 3. **Declined forwarding** — answer `n`; expect an archive, and the pod still holds the tree.
-4. **Dirty repository archive** — edit a file, launch; expect `will be archived … (uncommitted
-   changes would be lost by a clone)` and `!git status` in the pod shows the same edit.
+4. **Dirty repository clone** — in a pushed, cloneable repository, stage a change, edit it
+   again, and add an untracked file. Launch; expect `will clone … (local uncommitted changes
+   are not copied)`. Inside the pod, `!git status` is clean, tracked content matches HEAD,
+   and the untracked file is absent. The host's staged, unstaged and untracked changes remain.
 5. **Non-git archive** — a plain directory of files; expect the files without a `.git`.
-6. **100+ MiB streaming archive** — a repository with a large untracked binary; watch the
+6. **100+ MiB streaming archive** — a repository without `origin`, with a large untracked binary; watch the
    `upload 25% …` lines; verify the file's checksum in the pod.
 7. **Interrupted upload** — Ctrl-C during upload; expect the pod deleted and no
    `pi-pod-seed-*.tar.gz` left in the temp directory.

package/man/pipod-config.5

@@ -1,4 +1,4 @@
-.TH "PIPOD\-CONFIG" "5" "October 2026" "0.1.11"
+.TH "PIPOD\-CONFIG" "5" "October 2026" "0.1.12"
 .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.11"
+.TH "PIPOD" "1" "October 2026" "0.1.12"
 .SH "NAME"
 \fBpipod\fR \- run pi coding\-agent sessions in server\-managed pods
 .SH SYNOPSIS
@@ -265,10 +265,13 @@ The launch uses the template named by \fB\-\-template\fP, or else the one pinned
 first launch offers to create a template from the project and pin it\.
 .P
 Workspace seeding: launching from a directory with no \.pi\-pod/config\.json seeds the new pod
-from that directory (its git repository root when inside one)\. A clean, pushed checkout whose
-remote tip matches HEAD is cloned at that exact commit; anything else (dirty trees, unpushed
-commits, private remotes without usable credentials, plain directories) is streamed in as a
-tar archive, without git\-ignored paths, node_modules, or \.pi\-pod/env\. Private\-remote
+from that directory (its git repository root when inside one)\. A pushed checkout whose
+remote tip matches HEAD is cloned at that exact committed HEAD, even with local uncommitted
+changes\. A successful clone does not copy staged, unstaged, or untracked changes and leaves
+the local checkout untouched\. When cloning is unavailable or fails (unpushed commits, private
+remotes without usable credentials, plain directories), the local working tree, including
+uncommitted changes, is streamed in as a tar archive, without git\-ignored paths, node_modules,
+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

package/man/pipod.1.md

@@ -254,10 +254,13 @@ The launch uses the template named by `--template`, or else the one pinned in th
 first launch offers to create a template from the project and pin it.
 
 Workspace seeding: launching from a directory with no .pi-pod/config.json seeds the new pod
-from that directory (its git repository root when inside one). A clean, pushed checkout whose
-remote tip matches HEAD is cloned at that exact commit; anything else (dirty trees, unpushed
-commits, private remotes without usable credentials, plain directories) is streamed in as a
-tar archive, without git-ignored paths, node_modules, or .pi-pod/env. Private-remote
+from that directory (its git repository root when inside one). A pushed checkout whose
+remote tip matches HEAD is cloned at that exact committed HEAD, even with local uncommitted
+changes. A successful clone does not copy staged, unstaged, or untracked changes and leaves
+the local checkout untouched. When cloning is unavailable or fails (unpushed commits, private
+remotes without usable credentials, plain directories), the local working tree, including
+uncommitted changes, is streamed in as a tar archive, without git-ignored paths, node_modules,
+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

package/package.json

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