fix: correct drifted org name across SPEC plans and specs

plans/SPEC-1-core-engine-todo-sync.md

@@ -153,7 +153,7 @@ The package `exports` entry (`./src/index.ts`) is the **stable public surface**
 
 - [ ] **Step 4: Run test to verify it passes**
 
-Run: `cd ~/local-dev/getpither/armory-todo && pnpm test:run test/public-api.test.ts`
+Run: `cd ~/local-dev/getpipher/armory-todo && pnpm test:run test/public-api.test.ts`
 Expected: PASS.
 
 - [ ] **Step 5: Full suite + typecheck**

plans/SPEC-2-deep-armory-integration.md

@@ -17,7 +17,7 @@
 - **Single-writer discipline:** `noExtensions: true` on the child loader (no host extension hooks fire in the child); `excludeTools: ["todo"]` (hardened guard).
 - **No AI attribution** in commits/PRs/files.
 - **One commit per task**; conventional branch `feat/spec-2-deep-armory-integration`.
-- **getpither conventions:** EditorTheme gotcha — `ctx.ui.custom` receives full `Theme` (import from `@earendil-works/pi-coding-agent`); `ctx.ui.setEditorComponent` receives `EditorTheme`. Thread `() => ctx.ui.theme` for real colors.
+- **getpipher conventions:** EditorTheme gotcha — `ctx.ui.custom` receives full `Theme` (import from `@earendil-works/pi-coding-agent`); `ctx.ui.setEditorComponent` receives `EditorTheme`. Thread `() => ctx.ui.theme` for real colors.
 - **Companion PRs land first** (Tasks 1–2) so fleet's `pnpm install` against `file:../armory-memory` + `file:../vision` resolves the new `exports`.
 
 ---

plans/SPEC-5a-operational-runtime.md

@@ -2,7 +2,7 @@
 
 > **For agentic workers:** REQUIRED SUB-SKILL: Use superpowers:subagent-driven-development (recommended) or superpowers:executing-plans to implement this plan task-by-task. Steps use checkbox (`- [ ]`) syntax for tracking.
 
-**Goal:** Make the fleet operational — async/background runs on isolated git worktrees (per-lifecycle, foreground unchanged), cron/interval/one-shot scheduling (session-scoped, PID-locked, in-process), a JSONL run journal + auto-resume after crash, worktree-diff artifact discovery (replaces the prompt-baked `Artifacts:` block for isolated runs), a results inbox + `fleet.results()` auto-delivery, and a `/fleet` Scheduled tab + bg row status. Targets `@getpither/armory-fleet@0.5.0`.
+**Goal:** Make the fleet operational — async/background runs on isolated git worktrees (per-lifecycle, foreground unchanged), cron/interval/one-shot scheduling (session-scoped, PID-locked, in-process), a JSONL run journal + auto-resume after crash, worktree-diff artifact discovery (replaces the prompt-baked `Artifacts:` block for isolated runs), a results inbox + `fleet.results()` auto-delivery, and a `/fleet` Scheduled tab + bg row status. Targets `@getpipher/armory-fleet@0.5.0`.
 
 **Architecture:** A layer **above** the unchanged SPEC-1..4 engine seam. Three new modules: `src/worktree/` (greenfield `WorktreeService` + `DiffService` — git shell-outs), `src/runtime/` (async runner + JSONL journal + N-slot concurrency pool + results inbox + resume), `src/scheduling/` (expressions + PID-lock + scheduler). One vendored module: `src/vendor/cron-parser/` (MIT, frozen). The async runner calls the **unchanged** `runLifecycle`/`spawnSubagent` with a worktree cwd + a journal hook; the phase loop, backend registry, and spawn path are untouched. Foreground sync `subagent` (v0.1..0.4) is unchanged — zero breaking change.
 

specs/SPEC-2-deep-armory-integration.md

@@ -169,7 +169,7 @@ The PRD says "scoped per project/local/user" without defining the terms. SPEC-2
 | Scope | Means | Memory dir | Delivered by |
 |---|---|---|---|
 | **project** | the cwd the child works in | `~/.pi/agent/memory/<cwd-slug>/` (armory-memory's existing dir) | armory-memory as-is |
-| **local** | the **immediate parent directory** of the project cwd (the workspace/org level — e.g. for cwd `~/local-dev/getpither/armory-fleet`, `local` = `~/local-dev/getpither`) | `~/.pi/agent/memory/<parent-slug>/` | fleet calls `renderMemoryBlock(dirname(projectCwd))` |
+| **local** | the **immediate parent directory** of the project cwd (the workspace/org level — e.g. for cwd `~/local-dev/getpipher/armory-fleet`, `local` = `~/local-dev/getpipher`) | `~/.pi/agent/memory/<parent-slug>/` | fleet calls `renderMemoryBlock(dirname(projectCwd))` |
 | **user** | global, cross-project user memory | a fixed pseudo-cwd dir (e.g. `~/.pi/agent/memory/_user/`) | fleet calls `renderMemoryBlock(USER_PSEUDO_CWD)` |
 
 `USER_PSEUDO_CWD` is a fleet-defined constant (e.g. `"/__armory-fleet-user__"`) whose slug resolves to a stable global memory dir. The value is a fleet concern, not an armory-memory concern.
@@ -405,5 +405,5 @@ Nothing is silently dropped; every deferral is recorded with its landing SPEC. T
 - pi SDK doc: `…/pi-coding-agent/docs/sdk.md` (`createAgentSession`, `tools`/`excludeTools`/`customTools`, `DefaultResourceLoader`, `systemPromptOverride`)
 - pi extensions doc: `…/pi-coding-agent/docs/extensions.md` (`before_agent_start`, `setActiveTools`)
 - Sibling sources: `~/local-dev/getpipher/armory-memory/src/memory-store.ts` (`renderMemoryBlock`), `~/local-dev/getpipher/vision/lib/{capability,delegate,config}.ts`
-- getpither conventions + EditorTheme gotcha: `~/local-dev/getpipher/AGENTS.md`
+- getpipher conventions + EditorTheme gotcha: `~/local-dev/getpipher/AGENTS.md`
 - SPEC-1 companion PRs (the pattern): armory-todo #12 (`exports` + `index.ts`) + #13 (`index.d.ts` + dual-condition exports)

specs/SPEC-4-superpowers-native-lifecycle.md

@@ -402,7 +402,7 @@ lifecycle is marked `failed` (§9).
 
 ## 9. The `/fleet` panel — Lifecycle view
 
-Per the getpither interactive-first convention, the Lifecycle capability lands as a **new
+Per the getpipher interactive-first convention, the Lifecycle capability lands as a **new
 tab in the `/fleet` panel** first (human surface); the model-callable surface is the
 `subagent({ task, lifecycle })` param (§2.3). The `/fleet-implement <task>` slash is the
 thin text mirror / done-bar shortcut.