docs: release 7383422 — parallel agents, test first in every lane, and adoption per project

[mauricios]

What changed and why

Turns ## Unreleased into the 7383422 release (2026-10-01, aplyca-framework 0.2.4), so adopted repositories can stamp it and /upgrade knows which entries apply. It covers:

• #13 — parallel agents with portable defaults, environment info, and /handoff;
• #14 — test first in every lane, and the hub enforced;
• #15 — /upgrade offers the missing modules, the plugin installs per project, and adoption works from one prompt and in a new project.

The release opens with the order to upgrade from 3eb7777:

1. Get the plugin into the project at 0.2.4, using the README's install prompt, --scope project.
2. Run /upgrade, from a worktree in a hub project. By hand: each part's Upgrade impact, newest first.
3. Re-stamp CLAUDE.md with 7383422 and the modules.

A baseline older than 3eb7777 applies that release's three fixes first.

Also:

• README.md § Update a project names the latest release.
• docs/UPGRADING.md gets a scenario, "We adopted before the 7383422 release": plugin first, then /upgrade, from a worktree in a hub.
• The adopt eval report adds run 3, from the published GitHub address now that ADOPT.md is on main. The repository is private, so the address and the README's raw link return 404 to anything not signed in. Both models recovered with the developer's GitHub access: Sonnet through gh api, and Opus with a clone kept outside the project. Both passed every invariant, for $0.39.

Upgrade impact

None by itself: it's the changelog heading, docs, and an eval report. The entries it releases carry their own.

How to verify

1. ./evals/run-evals.sh.
2. Read CHANGELOG.md from the top: an empty Unreleased, then the 7383422 heading and its upgrade order.

Verified / not verified

• Verified: static suites 131, 61, 43, and 9 pass.
• Not verified: an /upgrade of a real project to 7383422 — that's the pilot, next.

🤖 Generated with Claude Code