diff --git a/CHANGELOG.md b/CHANGELOG.md index 7048d5b..268f0f0 100644 --- a/CHANGELOG.md +++ b/CHANGELOG.md @@ -11,6 +11,24 @@ For each entry, **Upgrade impact** classifies the change against the [three-buck ## Unreleased +## v1.3.0 — 2026-10-06 — Every task goes through `/dispatch` + +A minor release for teams with the `parallel-agents` module +([#37](https://github.com/Aplyca/AgenticDevelopmentFramework/pull/37), decision 0020). The session in +the main checkout now takes every task and hands it to a new session in a worktree of its own, by the +route the project's `worktree.conf` gives. The plugin now carries `/dispatch`. Nothing changes for a +project without the module. + +**Upgrading from v1.2.x:** `/aplyca-adf:upgrade` moves the pin to `v1.3.0`. In a project with the +module it also: +- overwrites `/dispatch` and merges `docs/PARALLEL-AGENTS.md`. A committed project also overwrites the + hooks and `/spec-workflow` it commits; +- in a packaged project, deletes the committed `.claude/skills/dispatch/` where it's unchanged since the + baseline. Type `/aplyca-adf:dispatch` from then on. + +A project whose worktrees need a port or setup now takes every task through the scripts. Ask for a +chip for a task that won't run the app. + ### Every task goes through `/dispatch` in the main checkout ([0020](docs/decisions/0020-every-task-through-dispatch.md), amending [0008](docs/decisions/0008-dispatcher-and-worker-worktrees.md) and [0015](docs/decisions/0015-tool-worktrees-are-workers.md)) diff --git a/README.md b/README.md index 2efbbc9..beaab97 100644 --- a/README.md +++ b/README.md @@ -141,8 +141,10 @@ Updates are deliberate: `/aplyca-adf:upgrade` moves a project from one release t pull request and keeps its customizations. Read the **Upgrade impact** of each release in [CHANGELOG.md](CHANGELOG.md) first. From v1.0.0, releases follow semantic versioning ([decision 0017](docs/decisions/0017-semantic-versioning.md)), so a major release asks something of your team. -The latest, **v1.2.1** (2026-10-05), fixes drift in the instruction files. **v1.2.0** moved the -framework's reference docs out of packaged projects and into the plugin. +The latest, **v1.3.0** (2026-10-06), takes every task in the main checkout through `/dispatch`, for +teams with the `parallel-agents` module, and the plugin carries `/dispatch`. **v1.2.1** fixed drift +in the instruction files, and **v1.2.0** moved the framework's reference docs out of packaged +projects and into the plugin. **v1.0.0** (2026-10-02) renamed the plugin `aplyca-adf` and opens with the order to upgrade in. A baseline older than `7383422` takes that release's order first, and one older than `3eb7777` takes its three fixes before that — they affect every adopted repository. diff --git a/docs/decisions/0017-semantic-versioning.md b/docs/decisions/0017-semantic-versioning.md index e787370..12a9e39 100644 --- a/docs/decisions/0017-semantic-versioning.md +++ b/docs/decisions/0017-semantic-versioning.md @@ -34,6 +34,10 @@ From v1.0.0, each release is `vMAJOR.MINOR.PATCH`: - **MINOR** — new capabilities that are additive or opt-in: a skill, a module, an install mode. - **PATCH** — fixes that change no workflow. +*Clarified 2026-10-06:* "has to act" means something stops working until the team acts, as with the +plugin's rename. A migration step that `/aplyca-adf:upgrade` carries out, or a changed rule in an +opt-in module, makes a minor release: v1.2.0 and v1.3.0 shipped both that way. + Where it shows: - **The changelog heading:** `## v1.0.0 — 2026-10-02 —