@gotgenes/pi-subagents 1.0.1 → 1.0.2
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
package/CHANGELOG.md
CHANGED
|
@@ -5,6 +5,14 @@ All notable changes to this project will be documented in this file.
|
|
|
5
5
|
The format is based on [Keep a Changelog](https://keepachangelog.com/en/1.0.0/),
|
|
6
6
|
and this project adheres to [Semantic Versioning](https://semver.org/spec/v2.0.0.html).
|
|
7
7
|
|
|
8
|
+
## [1.0.2](https://github.com/gotgenes/pi-packages/compare/pi-subagents-v1.0.1...pi-subagents-v1.0.2) (2026-05-17)
|
|
9
|
+
|
|
10
|
+
|
|
11
|
+
### Documentation
|
|
12
|
+
|
|
13
|
+
* 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))
|
|
14
|
+
* 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))
|
|
15
|
+
|
|
8
16
|
## [1.0.1](https://github.com/gotgenes/pi-packages/compare/pi-subagents-v1.0.0...pi-subagents-v1.0.1) (2026-05-17)
|
|
9
17
|
|
|
10
18
|
|
|
@@ -1,5 +1,5 @@
|
|
|
1
1
|
---
|
|
2
|
-
status:
|
|
2
|
+
status: superseded
|
|
3
3
|
date: 2026-05-11
|
|
4
4
|
---
|
|
5
5
|
|
|
@@ -7,7 +7,8 @@ date: 2026-05-11
|
|
|
7
7
|
|
|
8
8
|
## Status
|
|
9
9
|
|
|
10
|
-
|
|
10
|
+
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).
|
|
11
|
+
The original rationale below remains useful context.
|
|
11
12
|
|
|
12
13
|
## Context
|
|
13
14
|
|
|
@@ -51,7 +52,8 @@ All three divergences now have upstream PRs, opened after production validation
|
|
|
51
52
|
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`)
|
|
52
53
|
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`)
|
|
53
54
|
|
|
54
|
-
|
|
55
|
+
If these land upstream, upstream gains the peer-dep fix and the two RepOne patches.
|
|
56
|
+
However, the fork now diverges intentionally beyond those patches — see [`docs/architecture/architecture.md`](../architecture/architecture.md) for the full scope of planned changes.
|
|
55
57
|
|
|
56
58
|
## Consequences
|
|
57
59
|
|
|
@@ -67,5 +69,6 @@ Once these land upstream, the fork's divergence reduces to package naming and to
|
|
|
67
69
|
|
|
68
70
|
### Operational
|
|
69
71
|
|
|
70
|
-
- Upstream PRs are open and linked above.
|
|
72
|
+
- 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).
|
|
73
|
+
- The architecture document governs the fork's direction going forward; this ADR's original "thin-patch" framing no longer describes the fork's trajectory.
|
|
71
74
|
- When Patch 1 is eventually added, it should be a separate ADR in `docs/decisions/` with its own follow-up.
|
|
@@ -0,0 +1,74 @@
|
|
|
1
|
+
---
|
|
2
|
+
issue: 51
|
|
3
|
+
issue_title: "docs: update ADR 0001 to reflect hard-fork decision"
|
|
4
|
+
---
|
|
5
|
+
|
|
6
|
+
# Update ADR 0001 to reflect hard-fork decision
|
|
7
|
+
|
|
8
|
+
## Problem Statement
|
|
9
|
+
|
|
10
|
+
ADR 0001 (`docs/decisions/0001-deferred-patches.md`) was written when the fork was a thin-patch layer over `tintinweb/pi-subagents`.
|
|
11
|
+
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.
|
|
12
|
+
|
|
13
|
+
Several claims in ADR 0001 are now outdated:
|
|
14
|
+
|
|
15
|
+
1. The status is "accepted" but the decision has been superseded by the architecture doc.
|
|
16
|
+
2. The Upstream PRs section states "the fork's divergence reduces to package naming and tooling," which is no longer true.
|
|
17
|
+
3. The Consequences → Operational section implies that merging the upstream PRs eliminates behavioral divergence, which no longer holds.
|
|
18
|
+
|
|
19
|
+
## Goals
|
|
20
|
+
|
|
21
|
+
- Add a supersession note to ADR 0001 pointing to `docs/architecture/architecture.md`.
|
|
22
|
+
- Update the "Upstream PRs are open" subsection so the "divergence reduces to…" claim reflects reality.
|
|
23
|
+
- Update the Consequences → Operational section to note intentional divergence per the architecture document.
|
|
24
|
+
- Preserve all existing rationale — no information is removed.
|
|
25
|
+
|
|
26
|
+
## Non-Goals
|
|
27
|
+
|
|
28
|
+
- Rewriting the ADR from scratch — the original context is still useful.
|
|
29
|
+
- Updating the architecture document itself.
|
|
30
|
+
- Any code changes.
|
|
31
|
+
|
|
32
|
+
## Background
|
|
33
|
+
|
|
34
|
+
ADR 0001 has YAML frontmatter (`status: accepted`, `date: 2026-05-11`) and follows a standard ADR structure: Status, Context, Decision, Consequences.
|
|
35
|
+
|
|
36
|
+
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.
|
|
37
|
+
|
|
38
|
+
The three upstream PRs (#71, #72, #73) are still open and factually accurate — that section just needs the concluding sentence revised.
|
|
39
|
+
|
|
40
|
+
## Design Overview
|
|
41
|
+
|
|
42
|
+
The update touches three areas of the ADR:
|
|
43
|
+
|
|
44
|
+
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`.
|
|
45
|
+
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.
|
|
46
|
+
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.
|
|
47
|
+
|
|
48
|
+
No structural changes (new sections, removed sections, reordered content).
|
|
49
|
+
|
|
50
|
+
## Module-Level Changes
|
|
51
|
+
|
|
52
|
+
| File | Change |
|
|
53
|
+
| ----------------------------------------- | ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
|
|
54
|
+
| `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 |
|
|
55
|
+
|
|
56
|
+
## Test Impact Analysis
|
|
57
|
+
|
|
58
|
+
No tests are affected — this is a docs-only change.
|
|
59
|
+
|
|
60
|
+
## TDD Order
|
|
61
|
+
|
|
62
|
+
1. Update ADR 0001 with all four edits described above.
|
|
63
|
+
Commit: `docs: update ADR 0001 to reflect hard-fork decision (#51)`
|
|
64
|
+
|
|
65
|
+
## Risks and Mitigations
|
|
66
|
+
|
|
67
|
+
| Risk | Mitigation |
|
|
68
|
+
| ---------------------------------------------- | -------------------------------------------------------------------------------------------------------------------- |
|
|
69
|
+
| Supersession note makes the ADR look stale | Keep all original rationale intact; the note clarifies evolution, not obsolescence |
|
|
70
|
+
| Wording drift between ADR and architecture doc | Use a direct pointer (`docs/architecture/architecture.md`) rather than paraphrasing the architecture doc's decisions |
|
|
71
|
+
|
|
72
|
+
## Open Questions
|
|
73
|
+
|
|
74
|
+
None — the issue's acceptance criteria are unambiguous.
|
package/package.json
CHANGED