v3.2.3

## Spec Kitty 3.2.3

**3.2.3 is a stabilization-and-foundations release.** It hardens behavior under non-trivial branch topologies, smooths the day-to-day planning and implementation loop, and lands a governed documentation and doctrine foundation for the upcoming 3.3.x developer-experience focus.

- **Improved branch topology support** — coordination-topology missions now read and write every artifact from the correct surface (planning artifacts on the primary branch, status on the coordination worktree) through a single kind-aware resolution seam, backed by single-authority resolution gates. The orchestrator, the accept gate, merge/lane logic, and `spec-kitty next` no longer stall, mis-route, or report phantom early state on coordination missions.
- **Usability upgrades** — a batch of mission-lifecycle tooling-loop friction fixes, clearer global-install guidance, `SPEC_KITTY_HOME` isolating *all* local state, `--json` output safe to capture with `2>&1`, safer worktree discard (no sibling data loss), and a stale tool environment that can no longer brick the CLI.
- **Doctrine additions** — the Common Docs governed documentation foundation (a documentation directive, a styleguide, and curation / scaffold / write / find tactics wired into the doctrine graph) plus the structural move to a 13-section Divio `docs/` tree: 117 architecture decision records converted to metadata-in-file records under `docs/adr/`, redirect coverage for every moved page, and documentation rulers promoted to blocking gates.
- **Doctrine/charter extension improvements** — charter activation now gates org-pack agent availability across dispatch, context, and projection; the generated charter interpolates the project documentation policy; and `spec-kitty doctor` reports unsanctioned built-in doctrine-graph overrides.

We are continuing our efforts to remediate the usability issues introduced in `3.2.0`, though there is good progress, not everything was addressed yet. As mentioned in the `3.2.2` release: expect quick iterations to remediate these issues further in the coming days. We are committed to ensure your Spec Kitty experience is as fluent and enjoyable as possible.

Full details in the [CHANGELOG](https://github.com/Priivacy-ai/spec-kitty/blob/main/CHANGELOG.md).