@pilotspace/add 1.7.3 → 1.8.0
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 +37 -0
- package/package.json +1 -1
- package/tooling/add.py +853 -145
package/CHANGELOG.md
CHANGED
|
@@ -4,6 +4,43 @@ All notable changes to the ADD method (`@pilotspace/add` on npm,
|
|
|
4
4
|
`pilotspace-add` on PyPI) are documented here. The format follows
|
|
5
5
|
[Keep a Changelog](https://keepachangelog.com/); versions follow semver.
|
|
6
6
|
|
|
7
|
+
## [1.8.0] — 2026-06-23
|
|
8
|
+
|
|
9
|
+
Team collaboration: ADD becomes git-native and multi-user, with N
|
|
10
|
+
parallel-active milestones, plus a polish pass on the delta-resolution
|
|
11
|
+
machinery. Additive and backward-compatible — `add.py` ships a one-way state
|
|
12
|
+
migration (single-active → multi-active), and the non-interactive byte stream
|
|
13
|
+
for existing single-user flows is preserved. Bundles six closed milestones.
|
|
14
|
+
|
|
15
|
+
### Added
|
|
16
|
+
- **Multi-active milestones (`team-collaboration`)** — work N milestones in
|
|
17
|
+
parallel: `add.py activate` / `deactivate` manage an active working SET,
|
|
18
|
+
`add.py mine` is a my-work lens over owned tasks, the `streams:` block shows a
|
|
19
|
+
per-stream owner, and waves can span all active milestones.
|
|
20
|
+
- **Git-native user identity** — `add.py whoami` resolves the actor from git
|
|
21
|
+
config; tasks carry an owner.
|
|
22
|
+
- **Ownership & assignment** — `add.py assign` / `unassign` attach a task to an
|
|
23
|
+
owner; ownership renders across status and reports.
|
|
24
|
+
- **Git-merge safety** — merge-base enforcement guards a stale worker base; the
|
|
25
|
+
drift vectors a parallel-wave merge can introduce are pinned suite fixtures.
|
|
26
|
+
- **Multi-file commit primitive** — `_atomic_write_many` is now true
|
|
27
|
+
all-or-nothing: stage every temp → fsync → rename-aside → rename-all, with
|
|
28
|
+
rollback-on-any-failure restoring prior bytes. `fold`, `release`, and the
|
|
29
|
+
delta seed all route through it, closing the prior mid-rename residual window.
|
|
30
|
+
- **`--match <substr>` selector** — `add.py new-task --from-delta` and
|
|
31
|
+
`add.py drop-delta` accept `--match` to target ONE open SPEC delta among
|
|
32
|
+
several; a 0-match or ambiguous match is a named reject. First-open behavior
|
|
33
|
+
is byte-identical when `--match` is absent.
|
|
34
|
+
- **`compact --force`** — `add.py compact --force` overrides the project-wide
|
|
35
|
+
`open_spec_deltas_unresolved` block ONLY (never a structural guard) so an
|
|
36
|
+
urgent compaction is not blocked by an UNRELATED open SPEC delta; the bypass
|
|
37
|
+
is warned and recorded as `force_bypassed_spec_deltas`.
|
|
38
|
+
|
|
39
|
+
### Notes
|
|
40
|
+
- One version tag publishes both channels: `@pilotspace/add` (npm) and
|
|
41
|
+
`pilotspace-add` (PyPI). The engine (`add.py`) is mirrored byte-identical
|
|
42
|
+
across all three trees with `ENGINE_MD5` re-pinned.
|
|
43
|
+
|
|
7
44
|
## [1.7.3] — 2026-06-18
|
|
8
45
|
|
|
9
46
|
Multi-agent installer reach (`multi-agent-installer`). Additive; no breaking
|
package/package.json
CHANGED
|
@@ -1,6 +1,6 @@
|
|
|
1
1
|
{
|
|
2
2
|
"name": "@pilotspace/add",
|
|
3
|
-
"version": "1.
|
|
3
|
+
"version": "1.8.0",
|
|
4
4
|
"description": "ADD (AI-Driven Development). One skill. Eight steps. Five disciplines. Every feature ships through the loop — a minimal, state-tracked Claude Code skill that ships the AIDD book as its trust layer.",
|
|
5
5
|
"bin": {
|
|
6
6
|
"add": "bin/cli.js"
|