docs: update all references with local pipe mode features

- CHANGELOG.md: add [Unreleased] section with all local mode additions
- README.md: add pipe deploy, history, replay, and target commands
- PIPING.md: update architecture diagram, templates vs instances, API table
- DAG_PIPES_DEVELOPER_MANUAL.md: add local mode callout to guide overview
- DAG_PIPES_PART2_WEB_EDITOR.md: note local mode CLI alternative
- STACKER_YML_REFERENCE.md: document pipe mode implications of deploy.target

Co-authored-by: Copilot <223556219+Copilot@users.noreply.github.com>

Author: vsilent

CHANGELOG.md

@@ -4,6 +4,18 @@ All notable changes to this project will be documented in this file.
 
 ## [Unreleased]
 
+### Added — Local Pipe Mode
+
+- **`stacker target [local|cloud|server]`** — switch deployment target mode; persists in `.stacker/active-target`
+- **Local pipe creation** — `stacker pipe create` works without a cloud deployment (`deployment_hash` is now optional, `is_local` flag on PipeInstance/PipeExecution)
+- **Local scanning** — `stacker pipe scan` discovers containers via `docker ps` in local mode
+- **Local triggering** — `stacker pipe trigger` executes via `docker exec` / HTTP against local containers
+- **`stacker pipe deploy <id> --deployment <hash>`** — promote a local pipe to a remote deployment (clones config to new remote instance)
+- **`GET /api/v1/pipes/instances/local`** — list local pipe instances for the authenticated user
+- **`POST /api/v1/pipes/instances/{id}/deploy`** — deploy (promote) local pipe to remote
+- **`stacker init --target local`** — initialize project in local mode directly
+- Database migration: `deployment_hash` nullable, `is_local BOOLEAN DEFAULT FALSE`, partial index on local instances
+
 ## [0.2.7] — 2026-04-10
 
 ### Security — IDOR Hardening & Test Coverage

README.md

@@ -166,6 +166,10 @@ The end-user tool. No server required for local deploys.
 | `stacker pipe activate <id>` | Activate a pipe (start listening for triggers) |
 | `stacker pipe deactivate <id>` | Pause an active pipe |
 | `stacker pipe trigger <id>` | One-shot pipe execution with optional input data |
+| `stacker pipe deploy <id>` | Promote a local pipe to a remote deployment |
+| `stacker pipe history <id>` | View execution history for a pipe |
+| `stacker pipe replay <exec-id>` | Re-run a previous pipe execution |
+| `stacker target [local\|cloud\|server]` | Switch deployment target mode (affects all pipe commands) |
 | `stacker submit` | Package current stack and submit to marketplace for review |
 | `stacker marketplace status` | Check submission status for your marketplace templates |
 | `stacker marketplace logs <name>` | Show review comments and history for a submission |

docs/DAG_PIPES_DEVELOPER_MANUAL.md

@@ -6,10 +6,12 @@ Build and run data pipelines that connect your deployed services. Route contact
 
 | Part | For | What you'll learn |
 |------|-----|------------------|
-| **[Part 1: CLI Guide](./DAG_PIPES_PART1_CLI_GUIDE.md)** | Getting started | Create and run pipes using `stacker pipe` commands |
+| **[Part 1: CLI Guide](./DAG_PIPES_PART1_CLI_GUIDE.md)** | Getting started | Create and run pipes using `stacker pipe` commands (includes local mode) |
 | **[Part 2: Visual Editor](./DAG_PIPES_PART2_WEB_EDITOR.md)** | Visual builders | Drag-and-drop pipeline builder in your browser |
 | **[Part 3: REST API Deep Dive](./DAG_PIPES_PART3_API_DEEP_DIVE.md)** | Automation & scripting | Full API reference, curl scripts, gRPC streaming |
 
+> **💡 Local mode**: You can build and test pipes against local Docker containers without a cloud deployment. See the [Local Mode section in Part 1](./DAG_PIPES_PART1_CLI_GUIDE.md#local-mode-experimental) for setup and workflow.
+
 ## Examples in All Three Guides
 
 Each guide walks through the same practical examples:

docs/DAG_PIPES_PART2_WEB_EDITOR.md

@@ -179,6 +179,8 @@ Click **"Execute"** to run the pipeline with test data.
 
 Demo mode is great for learning the interface. Sign in to actually run pipelines.
 
+> **💡 Local mode (CLI)**: For local experimentation with _real_ execution, use `stacker target local` and the CLI pipe commands (see [Part 1: Local Mode](./DAG_PIPES_PART1_CLI_GUIDE.md#local-mode-experimental)). Local pipes can later be promoted to remote via `stacker pipe deploy`.
+
 ---
 
 ## What's Next?

docs/PIPING.md

@@ -12,7 +12,16 @@ Data piping connects containerized apps in a deployment, routing data from one s
 |  pipe create     |       |  validate params  |       |  curl endpoints  |
 |  pipe trigger    |       |  store results    |       |  capture samples |
 |  pipe history    |       |  persist history  |       |  execute pipes   |
+|  pipe deploy     |       |  promote local→   |       |                  |
 +------------------+       +------------------+       +------------------+
+        |
+        | (local mode — no agent needed)
+        v
++------------------+
+|  Local Docker    |
+|  docker ps       |
+|  docker exec     |
++------------------+
 ```
 
 **Three components work together:**
@@ -21,6 +30,8 @@ Data piping connects containerized apps in a deployment, routing data from one s
 2. **Server** (`/api/v1/pipes`) - REST API, validation, persistence
 3. **Agent** (status-panel) - runs on the deployment, probes containers, executes pipe triggers
 
+> **Local mode**: When `stacker target local` is active, scan uses `docker ps` and trigger uses `docker exec` — no agent required. Pipes are stored with `is_local=true` and no `deployment_hash`.
+
 ## Quick Start
 
 ### 1. Scan for connectable endpoints
@@ -138,7 +149,9 @@ stacker pipe deactivate <pipe-id>
 ### Templates vs Instances
 
 - **Template** - reusable pipe definition: source app type, target app type, endpoint paths, field mapping. Can be shared publicly.
-- **Instance** - deployment-specific activation of a template: ties to a `deployment_hash`, tracks status, trigger counts, errors.
+- **Instance** - activation of a template tied to a deployment or local context:
+  - **Remote instance** — bound to a `deployment_hash`, executed via the status agent on the cloud server.
+  - **Local instance** — no `deployment_hash`, `is_local=true`, executed via `docker exec` against local containers. Created when `stacker target local` is active.
 
 ### Field Mapping
 
@@ -257,10 +270,12 @@ All endpoints require authentication. Pipe instance access is verified through d
 
 | Method | Path | Description |
 |--------|------|-------------|
-| POST | `/api/v1/pipes/instances` | Create instance |
+| POST | `/api/v1/pipes/instances` | Create instance (`deployment_hash` optional for local) |
 | GET | `/api/v1/pipes/instances/{deployment_hash}` | List instances for deployment |
+| GET | `/api/v1/pipes/instances/local` | List local instances for current user |
 | GET | `/api/v1/pipes/instances/detail/{id}` | Get instance |
 | PUT | `/api/v1/pipes/instances/{id}/status` | Update status (draft/active/paused/error) |
+| POST | `/api/v1/pipes/instances/{id}/deploy` | Promote local instance to remote deployment |
 | DELETE | `/api/v1/pipes/instances/{id}` | Delete instance |
 
 ### Executions

docs/STACKER_YML_REFERENCE.md

@@ -501,6 +501,8 @@ deploy:
   target: local
 ```
 
+> **Pipe mode**: The `deploy.target` value also affects how `stacker pipe` commands behave. When target is `local`, pipes are created without a `deployment_hash` and execute against local Docker containers (`docker exec`). Use `stacker target` to switch modes at runtime without editing `stacker.yml`. See the [DAG Pipes CLI Guide — Local Mode](./DAG_PIPES_PART1_CLI_GUIDE.md#local-mode-experimental) for details.
+
 ### `deploy.compose_file`
 
 *Optional* · `string` (path) · Default: none