@gotgenes/pi-subagents 1.0.1 → 2.0.0

package/CHANGELOG.md

@@ -5,6 +5,35 @@ All notable changes to this project will be documented in this file.
 The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
 and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
 
+## [2.0.0](https://github.com/gotgenes/pi-packages/compare/pi-subagents-v1.0.2...pi-subagents-v2.0.0) (2026-05-17)
+
+
+### ⚠ BREAKING CHANGES
+
+* the `schedule` parameter is removed from the Agent tool. The `subagents:scheduled` and `subagents:scheduler_ready` events are no longer emitted. The `/agents → Settings → Scheduling` toggle is removed.
+* the `schedule` parameter is removed from the Agent tool and the `subagents:scheduled` / `subagents:scheduler_ready` events are no longer emitted. System cron (or launchd) invoking `pi` directly is the recommended replacement for recurring/delayed agent tasks.
+
+### Features
+
+* remove scheduled subagents source and tests ([860a03f](https://github.com/gotgenes/pi-packages/commit/860a03f08a6dbd418b437a72c2fd05ea416abacb))
+* remove scheduler wiring, types, and settings ([d5184e8](https://github.com/gotgenes/pi-packages/commit/d5184e88b181e60809b7fecc6a0971a18723bb9d))
+
+
+### Documentation
+
+* correct Module-Level Changes table in plan [#52](https://github.com/gotgenes/pi-packages/issues/52) (AGENTS.md → SKILL.md) ([93337e2](https://github.com/gotgenes/pi-packages/commit/93337e2a6b0424dc64e0adaf7a5c6ae6913c5991))
+* plan remove in-process scheduled subagents ([#52](https://github.com/gotgenes/pi-packages/issues/52)) ([bc548a4](https://github.com/gotgenes/pi-packages/commit/bc548a4dc6be4c5f810e9e33abcc76bc0d84f0da))
+* remove scheduling from README, architecture doc, and skill ([b2f16f2](https://github.com/gotgenes/pi-packages/commit/b2f16f2a53674a6a2675024dfc038c4243edd299))
+* **retro:** add retro notes for issue [#51](https://github.com/gotgenes/pi-packages/issues/51) ([0f741de](https://github.com/gotgenes/pi-packages/commit/0f741dedbe4a8e26fd1e39098fb153e4511082b9))
+
+## [1.0.2](https://github.com/gotgenes/pi-packages/compare/pi-subagents-v1.0.1...pi-subagents-v1.0.2) (2026-05-17)
+
+
+### Documentation
+
+* plan update ADR 0001 to reflect hard-fork decision ([#51](https://github.com/gotgenes/pi-packages/issues/51)) ([bd4899a](https://github.com/gotgenes/pi-packages/commit/bd4899a0d7e72c43b80c3c07c07ccc32dc0df8ed))
+* update ADR 0001 to reflect hard-fork decision ([#51](https://github.com/gotgenes/pi-packages/issues/51)) ([387e0ad](https://github.com/gotgenes/pi-packages/commit/387e0ad06ec1cf015c1d3d1d9852a1be015fc283))
+
 ## [1.0.1](https://github.com/gotgenes/pi-packages/compare/pi-subagents-v1.0.0...pi-subagents-v1.0.1) (2026-05-17)
 
 

package/README.md

@@ -34,7 +34,6 @@ https://github.com/user-attachments/assets/8685261b-9338-4fea-8dfe-1c590d5df543
 - **Styled completion notifications** — background agent results render as themed, compact notification boxes (icon, stats, result preview) instead of raw XML. Expandable to show full output. Group completions render each agent individually
 - **Event bus** — lifecycle events (`subagents:created`, `started`, `completed`, `failed`, `steered`, `compacted`) emitted via `pi.events`, enabling other extensions to react to sub-agent activity
 - **Cross-extension RPC** — other pi extensions can spawn and stop subagents via the `pi.events` event bus (`subagents:rpc:ping`, `subagents:rpc:spawn`, `subagents:rpc:stop`). Standardized reply envelopes with protocol versioning. Emits `subagents:ready` on load
-- **Schedule subagents** — pass `schedule` to the `Agent` tool to fire on cron / interval / one-shot. Session-scoped jobs with PID-locked persistence; results land via the same `subagent-notification` followUp path as manual background completions; manage via `/agents → Scheduled jobs`
 
 ## Install
 
@@ -63,38 +62,6 @@ Agent({
 
 Foreground agents block until complete and return results inline. Background agents return an ID immediately and notify you on completion.
 
-### Scheduling
-
-Add a `schedule` field to register the agent to fire later instead of running now:
-
-```
-Agent({
-  subagent_type: "Explore",
-  prompt: "Look at recent commits and summarize what changed since last week",
-  description: "Weekly commit review",
-  schedule: "0 0 9 * * 1",   // 9am every Monday (6-field cron)
-})
-```
-
-Schedule formats:
-
-- **Cron** — 6-field (`second minute hour day-of-month month day-of-week`), e.g. `"0 0 9 * * 1"` for 9am every Monday, `"0 */15 * * * *"` for every 15 minutes.
-- **Interval** — `"5m"`, `"1h"`, `"30s"`, `"2d"`. Fires repeatedly at that interval.
-- **One-shot relative** — `"+10m"`, `"+2h"`, `"+1d"`. Fires once at that future time.
-- **One-shot absolute** — full ISO timestamp, e.g. `"2026-12-25T09:00:00.000Z"`.
-
-When a schedule fires, the spawn runs in background and its completion notification arrives in the conversation through the same `subagent-notification` followUp path as a manually-spawned background agent — your parent agent reasons about the result the same way.
-
-Schedules are **session-scoped**: they reset on `/new` and restore on `/resume`. List and cancel via `/agents → Scheduled jobs` (creation is the `Agent` tool's job — there is no parallel manual-create wizard). Storage at `<cwd>/.pi/subagent-schedules/<sessionId>.json` with PID-based file locking for cross-instance safety.
-
-**Disable the feature entirely**: `/agents → Settings → Scheduling → disabled` removes `schedule` from the `Agent` tool spec (no LLM-context cost), hides the menu entry, and stops any active scheduler. The schema-level removal takes effect on the next pi session; the runtime kill is immediate. Re-enable from the same menu.
-
-Restrictions:
-- `schedule` cannot be combined with `inherit_context` (no parent conversation exists at fire time) or `resume` (schedules create fresh agents).
-- `run_in_background` is forced to `true`.
-- Scheduled fires bypass the `maxConcurrent` queue so a 5-minute interval cannot be deferred behind long-running manual agents.
-- **Headless `pi -p` doesn't wait for scheduled subagents.**
-
 ## UI
 
 The extension renders a persistent widget above the editor showing all active agents:
@@ -351,8 +318,6 @@ Agent lifecycle events are emitted via `pi.events.emit()` so other extensions ca
 | `subagents:failed` | Agent errored, stopped, or aborted | same as completed + `error`, `status` |
 | `subagents:steered` | Steering message sent | `id`, `message` |
 | `subagents:compacted` | Agent's session successfully compacted | `id`, `type`, `description`, `reason` (`"manual"` / `"threshold"` / `"overflow"`), `tokensBefore`, `compactionCount` |
-| `subagents:scheduled` | Schedule lifecycle change | `{ type: "added" \| "removed" \| "updated" \| "fired" \| "error", … }` (job/agentId/error fields per type) |
-| `subagents:scheduler_ready` | Scheduler bound to session, enabled jobs armed | `sessionId`, `jobCount` |
 | `subagents:ready` | Extension loaded and RPC handlers registered | — |
 | `subagents:settings_loaded` | Persisted settings applied at extension init | `settings` (merged global + project) |
 | `subagents:settings_changed` | `/agents` → Settings mutation was applied | `settings`, `persisted` (`boolean` — `false` on write failure) |

package/docs/architecture/architecture.md

@@ -48,14 +48,11 @@ invocation-config.ts  — merge tool params with agent config
 output-file.ts        — JSONL transcript streaming
 settings.ts           — persistent operational settings
 
-schedule.ts           — cron/interval/one-shot job dispatch  ← removing
-schedule-store.ts     — file-backed schedule persistence     ← removing
 cross-extension-rpc.ts — RPC over pi.events                  ← replacing
 group-join.ts         — batch completion notifications
 
 ui/agent-widget.ts       — above-editor live status widget
 ui/conversation-viewer.ts — scrollable session overlay
-ui/schedule-menu.ts      — /agents schedule submenu          ← removing
 ```
 
 ### Coupling today
@@ -63,8 +60,7 @@ ui/schedule-menu.ts      — /agents schedule submenu          ← removing
 The widget reads agent state by holding a direct reference to
 `AgentManager` and polling a shared mutable `Map<string, AgentActivity>`
 every 80 ms. The conversation viewer subscribes directly to `AgentSession`
-objects. The scheduler holds a direct `AgentManager` reference and calls
-`manager.spawn()`.
+objects.
 
 Cross-extension consumers use an ad-hoc RPC layer over `pi.events`
 (`subagents:rpc:spawn`, `subagents:rpc:stop`, `subagents:rpc:ping`) with
@@ -342,10 +338,10 @@ Add the `SubagentsAPI` interface, serializable types, and `Symbol.for()`
 accessor functions as public exports of this package. No behavioral
 changes to the core yet.
 
-### Phase 2: Remove scheduling
+### Phase 2: Remove scheduling ✓ (done — issue #52)
 
-Delete `schedule.ts`, `schedule-store.ts`, `ui/schedule-menu.ts`. Remove
-the `schedule` parameter from the `Agent` tool schema. Remove scheduler
+Deleted `schedule.ts`, `schedule-store.ts`, `ui/schedule-menu.ts`. Removed
+the `schedule` parameter from the `Agent` tool schema. Removed scheduler
 setup and lifecycle hooks from `index.ts`.
 
 ### Phase 3: Remove group-join, output-file, ad-hoc RPC

package/docs/decisions/0001-deferred-patches.md

@@ -1,5 +1,5 @@
 ---
-status: accepted
+status: superseded
 date: 2026-05-11
 ---
 
@@ -7,7 +7,8 @@ date: 2026-05-11
 
 ## Status
 
-Accepted
+Superseded by [`docs/architecture/architecture.md`](../architecture/architecture.md), which commits to a hard fork with material scope reduction (scheduling removal, `SubagentsAPI` boundary, `index.ts` decomposition).
+The original rationale below remains useful context.
 
 ## Context
 
@@ -51,7 +52,8 @@ All three divergences now have upstream PRs, opened after production validation
 2. **Post-bind re-filter** — [tintinweb/pi-subagents#72](https://github.com/tintinweb/pi-subagents/pull/72) (`fix(agent-runner): re-filter active tools after bindExtensions so extension tools land in child`)
 3. **Active-agent tag** — [tintinweb/pi-subagents#73](https://github.com/tintinweb/pi-subagents/pull/73) (`feat(prompts): inject <active_agent name="..."/> tag for permission resolution`)
 
-Once these land upstream, the fork's divergence reduces to package naming and tooling.
+If these land upstream, upstream gains the peer-dep fix and the two RepOne patches.
+However, the fork now diverges intentionally beyond those patches — see [`docs/architecture/architecture.md`](../architecture/architecture.md) for the full scope of planned changes.
 
 ## Consequences
 
@@ -67,5 +69,6 @@ Once these land upstream, the fork's divergence reduces to package naming and to
 
 ### Operational
 
-- Upstream PRs are open and linked above. Once merged, the fork's behavioral divergence is eliminated.
+- Upstream PRs are open and linked above. If merged, upstream gains the three patches, but the fork continues independently with broader architectural changes per [`docs/architecture/architecture.md`](../architecture/architecture.md).
+- The architecture document governs the fork's direction going forward; this ADR's original "thin-patch" framing no longer describes the fork's trajectory.
 - When Patch 1 is eventually added, it should be a separate ADR in `docs/decisions/` with its own follow-up.

package/docs/plans/0051-update-adr-0001-hard-fork.md

@@ -0,0 +1,74 @@
+---
+issue: 51
+issue_title: "docs: update ADR 0001 to reflect hard-fork decision"
+---
+
+# Update ADR 0001 to reflect hard-fork decision
+
+## Problem Statement
+
+ADR 0001 (`docs/decisions/0001-deferred-patches.md`) was written when the fork was a thin-patch layer over `tintinweb/pi-subagents`.
+The new architecture document (`docs/architecture/architecture.md`) commits to a hard fork with material scope reduction — scheduling removal, a `SubagentsAPI` boundary, `index.ts` decomposition, and more.
+
+Several claims in ADR 0001 are now outdated:
+
+1. The status is "accepted" but the decision has been superseded by the architecture doc.
+2. The Upstream PRs section states "the fork's divergence reduces to package naming and tooling," which is no longer true.
+3. The Consequences → Operational section implies that merging the upstream PRs eliminates behavioral divergence, which no longer holds.
+
+## Goals
+
+- Add a supersession note to ADR 0001 pointing to `docs/architecture/architecture.md`.
+- Update the "Upstream PRs are open" subsection so the "divergence reduces to…" claim reflects reality.
+- Update the Consequences → Operational section to note intentional divergence per the architecture document.
+- Preserve all existing rationale — no information is removed.
+
+## Non-Goals
+
+- Rewriting the ADR from scratch — the original context is still useful.
+- Updating the architecture document itself.
+- Any code changes.
+
+## Background
+
+ADR 0001 has YAML frontmatter (`status: accepted`, `date: 2026-05-11`) and follows a standard ADR structure: Status, Context, Decision, Consequences.
+
+The architecture document (`docs/architecture/architecture.md`) describes a six-phase plan that materially diverges from upstream: scheduling removal, ad-hoc RPC replacement, group-join and output-file removal, a typed `SubagentsAPI` boundary, and `index.ts` decomposition.
+
+The three upstream PRs (#71, #72, #73) are still open and factually accurate — that section just needs the concluding sentence revised.
+
+## Design Overview
+
+The update touches three areas of the ADR:
+
+1. **Frontmatter + Status section** — change `status: accepted` to `status: superseded` in frontmatter, and update the Status section body to read "Superseded" with a pointer to `docs/architecture/architecture.md`.
+2. **"Upstream PRs are open" subsection** — keep the PR list and factual statements intact; revise the final sentence ("Once these land upstream, the fork's divergence reduces to package naming and tooling.") to note that the fork now diverges intentionally beyond those patches, per the architecture document.
+3. **Consequences → Operational** — add a sentence noting that the fork diverges intentionally beyond patches, and that the architecture document governs the fork's direction going forward. Keep the existing bullet about upstream PRs.
+
+No structural changes (new sections, removed sections, reordered content).
+
+## Module-Level Changes
+
+| File                                      | Change                                                                                                                                                                                    |
+| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `docs/decisions/0001-deferred-patches.md` | Update frontmatter `status` from `accepted` to `superseded`; revise Status section; revise closing sentence in "Upstream PRs are open"; add divergence note to Consequences → Operational |
+
+## Test Impact Analysis
+
+No tests are affected — this is a docs-only change.
+
+## TDD Order
+
+1. Update ADR 0001 with all four edits described above.
+   Commit: `docs: update ADR 0001 to reflect hard-fork decision (#51)`
+
+## Risks and Mitigations
+
+| Risk                                           | Mitigation                                                                                                           |
+| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
+| Supersession note makes the ADR look stale     | Keep all original rationale intact; the note clarifies evolution, not obsolescence                                   |
+| Wording drift between ADR and architecture doc | Use a direct pointer (`docs/architecture/architecture.md`) rather than paraphrasing the architecture doc's decisions |
+
+## Open Questions
+
+None — the issue's acceptance criteria are unambiguous.

package/docs/plans/0052-remove-scheduled-subagents.md

@@ -0,0 +1,131 @@
+---
+issue: 52
+issue_title: "feat: remove in-process scheduled subagents"
+---
+
+# Remove in-process scheduled subagents
+
+## Problem Statement
+
+The scheduling subsystem reimplements OS-level cron inside a process that is not designed to be a long-lived daemon.
+System cron (or launchd) invoking `pi` directly is strictly superior: it survives crashes and reboots, is inspectable via `crontab -l`, and adds zero lines of code to this extension.
+The current implementation weighs ~610 source lines plus ~820 test lines, a `croner` dependency, PID-locked file persistence, and scheduler lifecycle wiring scattered across `index.ts`.
+
+## Goals
+
+- Delete the three scheduling source files (`schedule.ts`, `schedule-store.ts`, `ui/schedule-menu.ts`).
+- Delete the three scheduling test files (`schedule.test.ts`, `schedule-store.test.ts`, `schedule-e2e.test.ts`).
+- Remove all scheduler wiring from `index.ts` (~200 lines of imports, lifecycle hooks, tool-schema gates, and menu routing).
+- Remove `ScheduledSubagent` and `ScheduleStoreData` interfaces from `types.ts`.
+- Remove `schedulingEnabled` from `SubagentsSettings`, `SettingsAppliers`, and related sanitize/apply logic in `settings.ts`.
+- Remove the `croner` dependency from `package.json`.
+- Update `README.md` (remove "Scheduling" section and events-table rows) and package `AGENTS.md` (remove scheduling modules from architecture diagram and tables).
+- This is a **breaking change** (`feat!:`) — the `schedule` parameter is removed from the `Agent` tool, and the `subagents:scheduled` / `subagents:scheduler_ready` events are no longer emitted.
+
+## Non-Goals
+
+- Removing `bypassQueue` from `SpawnOptions` in `agent-manager.ts` — it remains useful for cross-extension RPC callers.
+- Removing other subsystems slated for removal in the architecture doc (output-file, cross-extension-rpc, group-join) — those are separate issues.
+- Providing a migration path or compatibility shim — no known consumers depend on the scheduling events.
+
+## Background
+
+The architecture doc (`docs/architecture/architecture.md`) already marks `schedule.ts`, `schedule-store.ts`, and `ui/schedule-menu.ts` as `← removing`.
+This issue executes that plan.
+
+The scheduling code touches `index.ts` in several distinct regions:
+
+1. Imports (lines 27–28, 46)
+2. Scheduler instance creation and `startScheduler()` helper (lines 445–462)
+3. Lifecycle hooks: `session_start`, `session_before_switch`, `session_shutdown` (lines 470–496)
+4. The `schedule` tool-schema param shape, conditional inclusion, and guideline string (lines 621–640, 666, 719)
+5. Schedule execution path in the Agent tool handler (lines 880–918)
+6. `/agents` menu: "Scheduled jobs" entry and routing (lines 1297–1327)
+7. `/agents → Settings → Scheduling` toggle (lines 1855–1867)
+
+The `settings.ts` module has `schedulingEnabled` woven into `SubagentsSettings`, `SettingsAppliers`, `sanitize()`, and `applySettings()`.
+
+`types.ts` carries `ScheduledSubagent` (30 lines) and `ScheduleStoreData` (5 lines) — both are only consumed by the scheduling subsystem.
+
+## Design Overview
+
+This is a pure deletion change with no new abstractions.
+The approach is inside-out: delete leaf modules first (no dependents), then remove references from the wiring layer (`index.ts`, `settings.ts`, `types.ts`), then clean up docs.
+
+The `bypassQueue` option on `SpawnOptions` stays — its JSDoc comment mentioning "scheduler" should be updated to a generic description since the scheduler is the only current user but the option is architecturally useful for any caller that needs to skip the concurrency queue.
+
+## Module-Level Changes
+
+### Delete
+
+| File                          | Lines |
+| ----------------------------- | ----- |
+| `src/schedule.ts`             | 365   |
+| `src/schedule-store.ts`       | 143   |
+| `src/ui/schedule-menu.ts`     | 104   |
+| `test/schedule.test.ts`       | 429   |
+| `test/schedule-store.test.ts` | 154   |
+| `test/schedule-e2e.test.ts`   | 237   |
+
+### Modify
+
+| File                                       | Change                                                                                                                                                                                                                                                                       |
+| ------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
+| `src/index.ts`                             | Remove scheduler imports, instance creation, `startScheduler()`, lifecycle hooks, `scheduleParamShape`/`scheduleParam`/`scheduleGuideline`, schedule execution path in Agent handler, "Scheduled jobs" menu entry + routing, "Scheduling" settings toggle.                   |
+| `src/types.ts`                             | Remove `ScheduledSubagent` interface and `ScheduleStoreData` interface.                                                                                                                                                                                                      |
+| `src/settings.ts`                          | Remove `schedulingEnabled` from `SubagentsSettings` and `SettingsAppliers`. Remove sanitize clause and `applySettings` clause for `schedulingEnabled`.                                                                                                                       |
+| `src/agent-manager.ts`                     | Update `bypassQueue` JSDoc to remove scheduler-specific language.                                                                                                                                                                                                            |
+| `package.json`                             | Remove `"croner": "^10.0.1"` from dependencies.                                                                                                                                                                                                                              |
+| `README.md`                                | Remove "Scheduling" feature bullet, "Scheduling" subsection (lines 66–96), and `subagents:scheduled` / `subagents:scheduler_ready` rows from the events table.                                                                                                               |
+| `.pi/skills/package-pi-subagents/SKILL.md` | Remove `schedule.ts`, `schedule-store.ts`, `ui/schedule-menu.ts` from the architecture diagram and module tables. Update `index.ts` description to drop scheduler mention. (`packages/pi-subagents/AGENTS.md` is a stub — the architecture content lives in the skill file.) |
+
+## Test Impact Analysis
+
+1. No new unit tests are needed — this is pure deletion.
+2. All three scheduling test files (`schedule.test.ts`, `schedule-store.test.ts`, `schedule-e2e.test.ts`) become entirely redundant and are deleted.
+3. Existing tests for `agent-manager`, `agent-runner`, `settings`, and other modules stay as-is. The `settings.test.ts` file (if it exists) may need minor updates to remove `schedulingEnabled` from fixture data.
+
+## TDD Order
+
+Since this is a removal (not a feature), the order is deletion-first with a single validation pass.
+
+1. **Delete scheduling source files.**
+   Delete `src/schedule.ts`, `src/schedule-store.ts`, `src/ui/schedule-menu.ts`.
+   Delete `test/schedule.test.ts`, `test/schedule-store.test.ts`, `test/schedule-e2e.test.ts`.
+   Commit: `feat!: remove scheduled subagents source and tests`
+
+2. **Remove scheduler wiring from `index.ts`.**
+   Remove imports, scheduler instance, `startScheduler()`, lifecycle hooks, schedule-related tool schema params and guideline, schedule execution path in Agent handler, "Scheduled jobs" menu entry/routing, and "Scheduling" settings toggle.
+   Commit: `feat!: remove scheduler wiring from index.ts`
+
+3. **Clean up types and settings.**
+   Remove `ScheduledSubagent` and `ScheduleStoreData` from `types.ts`.
+   Remove `schedulingEnabled` from `SubagentsSettings`, `SettingsAppliers`, `sanitize()`, and `applySettings()` in `settings.ts`.
+   Update `bypassQueue` JSDoc in `agent-manager.ts`.
+   Commit: `feat!: remove scheduling types and settings`
+
+4. **Remove `croner` dependency.**
+   Remove from `package.json`, run `pnpm install` to update lockfile.
+   Commit: `build: remove croner dependency`
+
+5. **Verify all tests pass.**
+   Run `pnpm vitest run` in the package. Fix any test fixtures that reference `schedulingEnabled` or scheduling types.
+   Commit (if fixes needed): `test: remove scheduling references from test fixtures`
+
+6. **Update documentation.**
+   Update `README.md`: remove scheduling feature bullet, "Scheduling" subsection, and event-table rows.
+   Update package `AGENTS.md`: remove scheduling modules from architecture diagram and module tables, update `index.ts` description.
+   Commit: `docs: remove scheduling from README and AGENTS`
+
+## Risks and Mitigations
+
+| Risk                                             | Mitigation                                                                                                                         |
+| ------------------------------------------------ | ---------------------------------------------------------------------------------------------------------------------------------- |
+| Missed scheduling reference causes compile error | `grep -rn 'schedule\|Schedule\|croner' src/` after each step to catch stragglers. TypeScript `noEmit` check catches import errors. |
+| Test fixtures reference `schedulingEnabled`      | Step 5 explicitly scans for and fixes these.                                                                                       |
+| `bypassQueue` removal mistakenly included        | Explicitly excluded in Non-Goals; plan preserves the option and only updates its JSDoc.                                            |
+| Breaking change not communicated                 | `feat!:` commit prefix triggers a major version bump via release-please.                                                           |
+
+## Open Questions
+
+None — the issue scope is fully specified and the architecture doc already ratified this removal.

package/docs/retro/0051-update-adr-0001-hard-fork.md

@@ -0,0 +1,33 @@
+---
+issue: 51
+issue_title: "docs: update ADR 0001 to reflect hard-fork decision"
+---
+
+# Retro: #51 — docs: update ADR 0001 to reflect hard-fork decision
+
+## Final Retrospective (2026-05-16)
+
+### Session summary
+
+Updated ADR 0001 (`docs/decisions/0001-deferred-patches.md`) to reflect the hard-fork decision documented in `docs/architecture/architecture.md`.
+The change was planned, implemented, shipped, and released as `pi-subagents-v1.0.2` in a single clean pass with no rework.
+
+### Observations
+
+#### What went well
+
+- The entire plan→build→ship pipeline completed with zero corrections, zero CI failures, and zero user interventions.
+- Parallel context gathering (issue body, `AGENTS.md`, ADR file, architecture doc, two skill files) in one tool call made the planning phase efficient.
+- The 4-edit approach (`Edit` with a single call containing four `edits[]` entries) was well-matched to the task — each edit was small, unique, and non-overlapping.
+
+#### What caused friction (agent side)
+
+- No friction observed. The task was unambiguous and the tooling well-suited.
+
+#### What caused friction (user side)
+
+- No friction observed. The session required no user input beyond invoking the three slash commands.
+
+### Follow-ups identified
+
+- The `package-pi-subagents` skill (`.pi/skills/package-pi-subagents/SKILL.md`) still frames the fork as "a friendly fork… carrying a small number of patches" with priorities like "stays as close to upstream as possible." This framing is now stale given the hard-fork commitment. A separate issue should update the skill to reflect the architecture document's posture.

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@gotgenes/pi-subagents",
-  "version": "1.0.1",
+  "version": "2.0.0",
   "description": "A pi extension that brings Claude Code-style autonomous sub-agents to pi. Friendly fork of @tintinweb/pi-subagents.",
   "author": {
     "name": "Chris Lasher"
@@ -33,7 +33,6 @@
   },
   "dependencies": {
     "@sinclair/typebox": "^0.34.49",
-    "croner": "^10.0.1",
     "nanoid": "^5.0.0"
   },
   "engines": {

package/src/agent-manager.ts

@@ -40,8 +40,8 @@ interface SpawnOptions {
   isBackground?: boolean;
   /**
    * Skip the maxConcurrent queue check for this spawn — start immediately even
-   * if the configured concurrency limit would otherwise queue it. Used by the
-   * scheduler so a fired job can't be deferred past its trigger window.
+   * if the configured concurrency limit would otherwise queue it. Useful for
+   * callers (e.g. cross-extension RPC) that must not be deferred by the queue.
    */
   bypassQueue?: boolean;
   /** Isolation mode — "worktree" creates a temp git worktree for the agent. */