poe-code 3.0.127 → 3.0.129

package/dist/sdk/pipeline.d.ts

@@ -1,5 +1,5 @@
 import { type PipelineRunOptions, type PipelineRunResult } from "@poe-code/pipeline";
-export type { AgentRunUsage, AgentRunInput, AgentRunResult, PipelineConfig, PipelineMetrics, PipelinePlan, PipelineStatus, PipelineTask, ResolvedStepDefinitions, StepDefinition, StepMode, TaskProgress, PlanSummary } from "@poe-code/pipeline";
+export type { AgentRunUsage, AgentRunInput, AgentRunResult, PipelineConfig, PipelineMetrics, PipelinePlan, PipelineStatus, PipelineTask, ResolvedStepDefinitions, ResolvedStepsConfig, StepDefinition, StepMode, TaskProgress, PlanSummary } from "@poe-code/pipeline";
 export { resolvePlanDirectory } from "@poe-code/pipeline";
 export type { PipelineRunOptions, PipelineRunResult };
 export declare function runPipeline(options: PipelineRunOptions): Promise<PipelineRunResult>;

package/dist/sdk/pipeline.js.map

@@ -1 +1 @@
-{"version":3,"file":"pipeline.js","sourceRoot":"","sources":["../../src/sdk/pipeline.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,WAAW,IAAI,oBAAoB,EAGpC,MAAM,oBAAoB,CAAC;AAC5B,OAAO,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AACxD,OAAO,EAAE,KAAK,IAAI,QAAQ,EAAE,MAAM,YAAY,CAAC;AAiB/C,OAAO,EAAE,oBAAoB,EAAE,MAAM,oBAAoB,CAAC;AAG1D,MAAM,CAAC,KAAK,UAAU,WAAW,CAC/B,OAA2B;IAE3B,OAAO,oBAAoB,CAAC;QAC1B,GAAG,OAAO;QACV,QAAQ,EAAE,KAAK,EAAE,KAAiE,EAAE,EAAE;YACpF,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,GAAG,QAAQ,CAAC,KAAK,CAAC,KAAK,EAAE;gBAC/C,MAAM,EAAE,KAAK,CAAC,MAAM;gBACpB,GAAG,EAAE,KAAK,CAAC,GAAG;gBACd,MAAM,EAAE,KAAK,CAAC,MAAM;gBACpB,KAAK,EAAE,KAAK,CAAC,KAAK;gBAClB,IAAI,EAAE,KAAK,CAAC,IAAI;gBAChB,GAAG,CAAC,KAAK,CAAC,UAAU,CAAC,CAAC,CAAC,EAAE,UAAU,EAAE,KAAK,CAAC,UAAU,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;aAC9D,CAAC,CAAC;YACH,MAAM,eAAe,CAAC,MAAM,CAAC,CAAC;YAC9B,OAAO,MAAM,MAAM,CAAC;QACtB,CAAC;KACF,CAAC,CAAC;AACL,CAAC"}
+{"version":3,"file":"pipeline.js","sourceRoot":"","sources":["../../src/sdk/pipeline.ts"],"names":[],"mappings":"AAAA,OAAO,EACL,WAAW,IAAI,oBAAoB,EAGpC,MAAM,oBAAoB,CAAC;AAC5B,OAAO,EAAE,eAAe,EAAE,MAAM,uBAAuB,CAAC;AACxD,OAAO,EAAE,KAAK,IAAI,QAAQ,EAAE,MAAM,YAAY,CAAC;AAkB/C,OAAO,EAAE,oBAAoB,EAAE,MAAM,oBAAoB,CAAC;AAG1D,MAAM,CAAC,KAAK,UAAU,WAAW,CAC/B,OAA2B;IAE3B,OAAO,oBAAoB,CAAC;QAC1B,GAAG,OAAO;QACV,QAAQ,EAAE,KAAK,EAAE,KAAiE,EAAE,EAAE;YACpF,MAAM,EAAE,MAAM,EAAE,MAAM,EAAE,GAAG,QAAQ,CAAC,KAAK,CAAC,KAAK,EAAE;gBAC/C,MAAM,EAAE,KAAK,CAAC,MAAM;gBACpB,GAAG,EAAE,KAAK,CAAC,GAAG;gBACd,MAAM,EAAE,KAAK,CAAC,MAAM;gBACpB,KAAK,EAAE,KAAK,CAAC,KAAK;gBAClB,IAAI,EAAE,KAAK,CAAC,IAAI;gBAChB,GAAG,CAAC,KAAK,CAAC,UAAU,CAAC,CAAC,CAAC,EAAE,UAAU,EAAE,KAAK,CAAC,UAAU,EAAE,CAAC,CAAC,CAAC,EAAE,CAAC;aAC9D,CAAC,CAAC;YACH,MAAM,eAAe,CAAC,MAAM,CAAC,CAAC;YAC9B,OAAO,MAAM,MAAM,CAAC;QACtB,CAAC;KACF,CAAC,CAAC;AACL,CAAC"}

package/dist/templates/pipeline/SKILL_plan.md

@@ -13,7 +13,8 @@ Write a YAML pipeline plan. Before writing, determine where to place it:
 
 1. Run `poe-code pipeline plan-path` to get the plans directory.
 2. Write the plan to `<plan-path>/plan-<name>.yaml`. If the plan path is under the global `~/.poe-code` directory, prefix the filename with the project name: `plan-<project>-<name>.yaml`.
-3. Check if a `steps.yaml` exists next to the plans directory (i.e. `<plan-path>/../steps.yaml`). If it does, read it to determine available steps. If not, use stepless tasks.
+3. Check if a `steps.yaml` exists next to the plans directory (i.e. `<plan-path>/../steps.yaml`). If it does, read it to determine available steps and note any `setup`/`teardown` hooks defined there. If not, use stepless tasks.
+4. If the user has an existing Markdown plan document (e.g. in `docs/plans/`), link it via `vars` so it is available in every prompt without repeating the path.
 
 ## Rules
 
@@ -24,32 +25,47 @@ Write a YAML pipeline plan. Before writing, determine where to place it:
 - The available steps come from the `steps.yaml` file you found (project or global). Use the current step names instead of inventing hardcoded ones.
 - If no step configuration is present, use stepless tasks with scalar `status: open`.
 - If step configuration is present, start every configured step status at `open`.
+- `setup` and `teardown` defined in `steps.yaml` are inherited automatically.
+- To disable an inherited hook for a specific plan, set `setup: false` or `teardown: false`.
+- To override an inherited hook, define the full block with an `prompt` field.
+- If the user has an existing Markdown plan document, add a `vars` block with a `plan_doc` key pointing to the file path. The pipeline runtime reads the file and makes its contents available as a named placeholder in every prompt.
+- `vars` values are plain strings. Use the `file` include syntax inside a value to load a file at runtime (path relative to project root): write `var_name: "` followed by the file include tag and a closing `"`.
+- Each var name becomes a double-curly-brace placeholder usable in any task, step, setup, or teardown prompt.
 
 ## Output Format
 
-Stepless tasks:
-
 ```yaml
-tasks:
-  - id: auth-hardening
-    title: Harden auth flow
-    prompt: |
-      Improve auth validation and session handling.
-    status: open
-```
-
-Stepped tasks when `.poe-code/pipeline/steps.yaml` defines steps:
+# vars: optional. Define named values available as double-curly-brace placeholders in every prompt.
+# Each value is a plain string. To load a file at runtime, write the value using the
+# file include syntax: double-curly-brace file followed by a quoted path.
+# Omit this block if there are no shared values to inject.
+#
+# vars:
+#   plan_doc: "(file include for docs/plans/my-feature.md)"  # loaded at runtime
+#   env: production                                           # literal string
+
+# setup/teardown are inherited from steps.yaml automatically.
+# Include them only to disable or override:
+#
+# setup: false              # disable the inherited setup hook
+# teardown: false           # disable the inherited teardown hook
+# setup:                    # override with a different prompt
+#   prompt: Custom setup
+#   mode: yolo
 
-```yaml
 tasks:
   - id: auth-hardening
     title: Harden auth flow
     prompt: |
       Improve auth validation and session handling.
-    status:
-      implement: open
-      test: open
-      review: open
+      # If vars defines plan_doc, reference it here using the double-curly-brace placeholder syntax.
+    # scalar when no steps.yaml steps are defined:
+    status: open
+    # stepped when steps.yaml defines steps:
+    # status:
+    #   implement: open
+    #   test: open
+    #   commit: open
 ```
 
 ## After Writing

package/dist/templates/pipeline/steps.yaml.hbs

@@ -3,10 +3,22 @@
 # Uncomment and change the example below when you want stepped tasks.
 # Add `mode` only when you want to override the default `yolo`.
 # Add `agent` and/or `model` to override the pipeline-level defaults per step.
+# Use {{file 'path'}} in any prompt to inline the contents of a Markdown file (relative to project root).
+#
+# Optional: setup runs once before any tasks, teardown runs once after all complete.
+# These can also be defined in plan.yaml to override the defaults below.
+#
+# setup:
+#   prompt: Prepare the workspace
+#   # mode: yolo
+#
+# teardown:
+#   prompt: Run final checks and clean up
+#   # mode: read
 #
 # steps:
 #   implement:
-#     instruction: |
+#     prompt: |
 #       {{id}}: {{title}}
 #
 #       Implement
@@ -15,7 +27,7 @@
 #     # model: o3
 #
 #   refactor:
-#     instruction: |
+#     prompt: |
 #       {{id}}: {{title}}
 #       Original task:
 #       {{prompt}}
@@ -23,7 +35,7 @@
 #       Refactor and improve the code
 #
 #   test:
-#     instruction: |
+#     prompt: |
 #       {{id}}: {{title}}
 #       Original task:
 #       {{prompt}}
@@ -31,7 +43,7 @@
 #       Be a user and test all edge cases, fix bugs
 #
 #   commit:
-#     instruction: |
+#     prompt: |
 #       {{id}}: {{title}}
 #       Original task:
 #       {{prompt}}

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "poe-code",
-  "version": "3.0.127",
+  "version": "3.0.129",
   "description": "CLI tool to configure Poe API for developer workflows.",
   "type": "module",
   "main": "./dist/index.js",
@@ -27,10 +27,15 @@
     "screenshot": "tsx scripts/screenshot.ts",
     "screenshot-poe-code": "tsx scripts/screenshot.ts --poe-code",
     "generate:design-docs": "turbo run generate:docs --filter=@poe-code/design-system",
+    "generate:design-docs:all": "npm run generate:design-docs:all -w @poe-code/design-system",
     "format": "prettier --check .",
     "format:write": "prettier --write .",
     "watch:diff": "tsx local_scripts/watch-diff.ts",
     "test:integration": "vitest run tests/integration/",
+    "test:workflows": "bats .github/workflows/test/workflows.bats",
+    "test:workflows:fast": "bats --filter 'dry-run' .github/workflows/test/workflows.bats",
+    "test:workflows:all": "bash scripts/test-workflows.sh",
+    "test:workflows:ci": "ACT_FULL=1 bash scripts/test-workflows.sh",
     "test:record": "POE_SNAPSHOT_MODE=record npm run test:integration",
     "test-generate": "tsx scripts/test-generate.ts",
     "snapshots": "tsx scripts/snapshots.ts",
@@ -88,36 +93,39 @@
   "devDependencies": {
     "@eslint/js": "^9.0.0",
     "@modelcontextprotocol/sdk": "^1.26.0",
-    "auth-store": "*",
-    "poe-oauth": "*",
     "@poe-code/agent-spawn": "*",
+    "@poe-code/cmdkit": "*",
+    "@poe-code/github-workflows": "*",
     "@poe-code/config-mutations": "*",
     "@poe-code/design-system": "*",
     "@poe-code/e2e-docker-test-runner": "*",
-    "@poe-code/freeze-cli": "*",
+    "@poe-code/experiment-loop": "*",
     "@poe-code/pipeline": "*",
     "@poe-code/poe-acp-client": "*",
     "@poe-code/poe-code-config": "*",
+    "@poe-code/process-launcher": "*",
+    "@poe-code/process-runner": "*",
     "@poe-code/ralph": "*",
     "@types/mustache": "^4.2.6",
     "@types/node": "^25.2.2",
     "@types/semver": "^7.7.1",
+    "auth-store": "*",
+    "bats": "^1.13.0",
     "eslint": "^9.0.0",
     "eslint-config-prettier": "^10.1.8",
     "globals": "^17.3.0",
     "husky": "^9.1.7",
     "memfs": "^4.56.10",
+    "poe-oauth": "*",
     "prettier": "^3.8.1",
+    "terminal-png": "*",
     "tiny-stdio-mcp-server": "*",
     "tiny-stdio-mcp-test-server": "*",
     "tsx": ">=4.21.0",
     "turbo": "^2.8.3",
     "typescript": "^5.9.3",
     "typescript-eslint": "^8.54.0",
-    "vitest": "^4.0.18",
-    "@poe-code/experiment-loop": "*",
-    "@poe-code/process-launcher": "*",
-    "@poe-code/process-runner": "*"
+    "vitest": "^4.0.18"
   },
   "repository": {
     "type": "git",