@code-partner/codepipe 0.1.137-dev.59.g4039549 → 0.1.137-dev.61.g5455e63

package/README.md

@@ -199,6 +199,7 @@ codepipe daemon           headless daemon (launchd/systemd; --profile for multi-
 codepipe sync             clone/fetch the project repos per project.yaml
 codepipe login            set/replace the Claude token (--shared for machine-wide)
 codepipe clone <id>       reconstruct the workspace on another machine
+codepipe project move …   repoint an initialised project at another HUB
 codepipe worker …         run the agent worker separately (see below)
 ```
 
@@ -272,4 +273,30 @@ mkdir ~/Projects/acme && cd ~/Projects/acme
 codepipe clone acme    # re-clone the workspace; re-enter your tokens
 ```
 
+## Moving a project to another HUB
+
+When a project graduates from a shared HUB to an enterprise one (or you want to
+try it on a dev stand), `project move` re-registers it on the target HUB without
+the full `init` wizard. Your Context Repo, project config and stored
+credentials are reused as-is; only a fresh account sign-in on the target HUB is
+needed.
+
+```bash
+codepipe project move --from-profile acme --hub https://hub.enterprise.example
+```
+
+That repoints the `acme` profile in place. To keep the old binding and add a
+second one — e.g. a dev stand alongside prod — write a separate profile:
+
+```bash
+codepipe project move --from-profile acme --to-profile acme-dev \
+  --hub https://hub.dev.example --project acme-dev
+```
+
+The move is non-destructive: the project's registration on the old HUB stays.
+Task history is not copied — the project starts clean on the target HUB — and
+the source HUB must be reachable so the current definition can be read.
+`--account <email>` targets a specific account on the new HUB (defaults to the
+source account); `--yes` skips the confirmation.
+
 See the platform docs for architecture and the pipeline state machine.