pi-crew 0.10.3 → 0.10.5

package/AGENTS.md

@@ -69,7 +69,8 @@ npm test
 
 - `src/extension/team-tool.ts` — main tool actions
 - `src/runtime/team-runner.ts` — workflow scheduler
-- `src/runtime/task-runner.ts` — task execution and artifacts
+- `src/runtime/task-runner.ts` + `src/runtime/task-runner/` — task execution and artifacts (thin entry + phase modules: pre-execution, child-executor, post-execution, …)
+- `src/runtime/child-pi/` — child Pi process runtime (spawn/streams/kill/steering/timers/transcript modules)
 - `src/state/` — durable state/event/artifact store
 - `src/worktree/` — worktree creation and cleanup
 - `agents/`, `teams/`, `workflows/` — builtin resources

package/CHANGELOG.md

@@ -2,6 +2,46 @@
 
 > **Note:** `atomic-write-v2.ts` / `AtomicWriter` mentioned in historical entries below was consolidated into `atomic-write.ts` as of v0.9.42. This changelog is preserved as historical record — the migration was completed (the v2 class was never adopted; v1 won on simplicity + symlink-safety + link+unlink atomicity). See `docs/migration/atomic-write-v2-migration.md` for the decision rationale.
 
+## [0.10.5] — user-scope runs: waitForRun + background diagnostics (2026-09-11)
+
+### fix: RUN/WAIT instantly errored "Run not found" for user-scope runs (#54)
+
+`waitForRun`'s slow-path attempt-0 probe joined `projectCrewRoot(cwd)`
+(`<cwd>/.crew/state/runs/…`) to test run-directory existence. But runs created in
+a **markerless (non-git) cwd** are routed to **user scope**
+(`userCrewRoot()` = `~/.pi/agent/extensions/pi-crew/`) by `createRunPaths` →
+`scopeBaseRoot` — the exact scope resolution `loadRunManifestById` uses when
+reading. Result: the run executed fine (STATUS/STEER/SUMMARY all worked), while
+`team action=run` and every `team action=wait` **instantly** threw
+`Run not found` — so the agent believed the crew had failed and duplicated the
+work itself while it kept running in the background. Reproduced from the #54
+transcript (artifact paths under `~/.pi/agent/extensions/pi-crew/artifacts/…`).
+
+- The probe now resolves through the exported, pure `createRunPaths(cwd,
+  runId).stateRoot` — the same scope-aware resolver used at run creation, so
+  project scope (incl. the `.pi/teams/` fallback, issue #29) and user scope
+  both resolve correctly.
+- Regression test: user-scope run in a markerless cwd (isolated
+  `PI_TEAMS_HOME`) — the waiter must poll through the user-scope dir and
+  resolve on terminal status instead of throwing.
+- Same-family fix (#55, also in this release): `background-runner.ts` computed
+  `background.log` + `exit-code.txt` paths via `projectCrewRoot` too, so those
+  diagnostics silently went missing for user-scope runs — degrading exactly
+  the crash evidence needed to diagnose them. Both sites now resolve via the
+  exported `backgroundLogPath()` / `backgroundExitCodePath()` helpers built on
+  `createRunPaths` (scope-aware; runId boundary hardening preserved). Ships as
+  source — no dist rebuild needed for this half.
+
+### test: macOS ENOTEMPTY teardown race — shared `teardownCwd` helper
+
+Third and fourth occurrence of the class (CI runs 34557602253 / 34558219451:
+`resume-checkpoint`, `wait-request-broker`): a run's last artifact writes race
+the recursive `rmSync` in test teardown — `rimrafSync` throws ENOTEMPTY when a
+file lands between its unlink pass and a directory rmdir. Extracted the
+5×200ms sleepSync retry (previously copy-pasted in resume-cancel `8197f054`
+and role-tools-integration `6a271822`) into `test/fixtures/teardown-cwd.ts`
+and switched both affected files to it.
+
 ## [0.10.3] — MuxSurface: workers in real panes + per-team-run tabs (2026-09-01)
 
 128 commits since v0.10.2. The headline feature is **MuxSurface A1** (spec

package/README.md

@@ -698,7 +698,11 @@ the `goal` action's completion-guarantee loop to builtin workflows.
 
 | Key path | Type | Default | Description |
 |----------|------|---------|-------------|
-| `ui.widgetPlacement` | `aboveEditor \| belowEditor` | `aboveEditor` | Where the status widget renders. |
+| `ui.widgetPlacement` | `aboveEditor \| belowEditor \| bottom` | `bottom` | Where the status widget renders. `bottom` docks inside the crew-vibes footer (very bottom of the screen), falling back to `belowEditor` when no footer sink exists. |
+| `ui.widgetRowStyle` | `compact \| detailed` | `compact` | Per-agent row layout in the widget (`compact` = one width-budgeted line per agent; `detailed` = two-line tree). |
+| `ui.inlinePanel` | `boolean` | `true` | Keyboard-navigable agent rows under the prompt (`↓` from an empty prompt). Yields to any extension that owns the editor component. |
+| `ui.refreshMs` | `number` | `1000` | Internal UI refresh cadence default (not a user-settable `ui.*` schema key — kept here for completeness). |
+| `ui.widgetDefaultFrameMs` | `number` | `1000` | Internal widget frame-budget default (not a user-settable `ui.*` schema key — kept here for completeness). |
 | `ui.widgetMaxLines` | `number` | `8` | Max lines shown by the widget. |
 | `ui.powerbar` | `boolean` | `true` | Show the power bar. |
 | `ui.dashboardPlacement` | `center \| right` | `center` | Dashboard screen position. |