Spec Kitty CLI 3.2.6

3.2.6 is the stabilization release that makes Spec Kitty tell the truth — it closes a long list of "reported success while the thing was actually broken" defects — and pairs that with one substantial new capability: driving a Mission's entire design pipeline from an external host.

Highlights

• orchestrator-api contract 1.4.0 — drive the whole design pipeline from outside the host CLI. 11 new verbs let a CI pipeline, custom dashboard, or native driver run specify → plan → tasks → analyze → decision resolution — including resolving a spec-kitty next decision moment with full event/lifecycle parity. Purely additive; all 21 commands coexist. (#3837)
• Status surfaces are now honest. Auth and sync diagnostics are derived from evidence through one HealthVerdict authority — a probe that can't verify says unknown, never a false ok (#3723). spec-kitty next no longer restarts a merged Mission or stalls on a canceled work package (#2947, #3780).
• spec-kitty merge honors a Mission's declared retention policy instead of silently deleting branches and worktrees it asked to keep (#3131).
• charter is now the canonical governing term. The doctrine code package relocated to charter.offering; every spec-kitty doctrine surface keeps working with a one-time deprecation warning (#3664). charter synthesize is non-destructive by default (#3270).
• --owned-checkout works across the whole single-branch lifecycle, so an agent can run a Mission end-to-end from a task-owned Git worktree (#3843).
• CLI quality-of-life: the startup crash on typer 0.27.2 is fixed (#3782), plus shell autocompletion, a -h alias, a single copyable --version line, and a durable per-project .kitty.env operator config.

⚠️ Breaking — action required

• Sync is now off by default. A bare install spawns no daemon and emits no events. Existing sync users must set SPEC_KITTY_ENABLE_SAAS_SYNC=1 to keep the daemon and event emission. (#3799)
• Built-in doctrine content moved to packs/built-in/ (no shim). Repoint any reference to the old src/doctrine/<kind>/built-in/ path — drop the inner built-in/ segment.
• Org packs are stricter. An unrecognised agent-profile/DRG key, a bare cross-pack reference, or a dangling edge endpoint now fails to load or validate. Run spec-kitty doctor doctrine --json and check skipped_profiles before upgrading.
• Local beads/fp tracker sync requires a recorded egress decision. A binding with no recorded consent stops syncing until you set tracker.egress: permitted or run spec-kitty sync opt-in. (#3108)
• The rtk-search-tooling toolguide is removed — the spec-kitty upgrade migration strips it automatically.
• Legacy {"mission": …}-only Missions stop resolving their type. Run spec-kitty migrate backfill-mission-type before upgrading such a project. (#3598)
• API/automation consumers: primary_feature_dir_for_mission is removed (use placement_seam(...).read_dir(<kind>)); seven types no longer re-export from specify_cli.dossier (import from spec_kitty_events); setup-plan returns exit 0 + warnings[] for an unauthenticated host; charter context --json bumps context_schema_version. See the full notes for each.

The complete, exhaustive breaking-changes list (with the exact upgrade action for every item) is in the release notes.

Install / upgrade

# New install:
pipx install spec-kitty-cli        # or: pip install spec-kitty-cli

# Existing project:
spec-kitty upgrade

All 3.2.6 migrations run automatically on spec-kitty upgrade and are safe to re-run.

Full details

• Release notes: docs/changelog/release-notes-3.2.6.md
• Line-by-line changelog: the [3.2.6rc1], [3.2.6rc2], and [Unreleased] (3.2.6rc4) sections of docs/changelog/CHANGELOG.md

🤖 Generated with Claude Code