September 2: main converges onto the active 3.2.6 development line

**On Wednesday, September 2, `main` becomes the converged 3.2.6 line.**

For the last two weeks the active development of spec-kitty has been happening on a working fork, [spec-kitty/EXPERIMENTAL-spec-kitty](https://github.com/spec-kitty/EXPERIMENTAL-spec-kitty). On **2026-09-02** we converge: `main` here will be fast-forwarded to a merge commit that preserves both histories (this repo's line and the working line as its two parents) with the working line's tree as the result.

**What this means for you:**

- **Your merged work is not lost.** Post-fork commits from this repo are being ported onto the converged line commit-by-commit with original authorship preserved (`cherry-pick -x`), tracked publicly. The 3.2.6 P0/P1 fixes that landed here in the last weeks are already ported or in review.
- **Removed in 3.2.6:** the local sync transport (the `spec-kitty sync` command family and its daemon), the delivery/event-journal stack, and the `websockets` dependency. Mission status is now ephemeral by design and team artifacts render server-side. The changelog will carry a full Removed/Breaking block, and an architectural gate keeps these subsystems from silently returning.
- **PRs stay welcome here.** Open PRs and new PRs on this repo are imported onto the converged line with attribution. Open issues keep their milestones — 3.2.6 items are being closed on the converged line; longer-horizon items moved to the new 3.2.7 milestone.
- **Releases:** `v3.2.6rc5` and then `v3.2.6` will be cut from the converged line through the normal release pipeline to PyPI.
- The docs site may lag for a short window around the cutover while the docs workflow moves across.

Questions and concerns → right here in this thread.