Priivacy-ai/spec-kitty v3.2.0rc29

on GitHub

3.2.0rc29 rerolls the coordination branch atomic event-log candidate after
PR review and publishes the launch-readiness hardening merged after the yanked
3.2.0rc28 candidate.

Added

• Added mission coordination branches, sparse coordination worktrees,
  BookkeepingTransaction, and WorkflowMutationPolicy so mission status
  mutations are staged, audited, and committed away from protected target
  branches.
• Added regression, integration, stress, and architectural coverage for
  coordination worktree creation, safe-commit branch assertions, legacy mission
  fallback, workflow rollback, post-merge indexing, and concurrent status
  emission.
• Added mission close --discard and doctor diagnostics for coordination
  workspace health, restart-daemon timing, command/skill manifest drift, and
  upgrade remediation provenance.
• Added external-orchestrator install and compatibility documentation, including
  PyPI installation paths, orchestrator API JSON-error guidance, host-surface
  governance docs, and environment-variable references.

Changed

• BREAKING (CLI): spec-kitty safe-commit now requires
  --to-branch <ref>. The temporary SPEC_KITTY_INFER_DESTINATION_REF=1
  compatibility path lets the CLI resolve and pass the destination explicitly
  during rollout; the helper itself never infers it.
• BREAKING (internal): safe_commit() now requires keyword-only
  worktree_root, destination_ref, and paths, and structurally verifies
  that the worktree HEAD matches the declared destination before staging.
• Removed Spec Kitty internal protected-branch commit exceptions for planning
  artifacts and merged-WP done records. Remaining exceptions are limited to
  documented non-Spec-Kitty upgrade/release workflows.
• Hardened release CI ownership by deduplicating release-readiness checks,
  adding installed-entrypoint smoke coverage, and preserving clean-install
  latency evidence.

Fixed

• Migrated remaining production safe_commit() call sites to the
  destination-ref-aware API so agent task, mission, merge, upgrade, and
  orchestrator paths no longer crash on the removed legacy signature.
• Fixed protected-branch leakage from agent action implement by routing
  planning artifacts and workflow status writes through coordination-owned
  commit paths instead of target-branch bypasses.
• Serialized first-time coordination worktree creation under the feature
  status lock to prevent concurrent emitters from racing on git worktree add.
• Fixed idempotent squash-merge retry behavior, finalize-tasks dependency
  source precedence, safe-commit recovery reporting, workflow path mirroring,
  configured command execution on Windows, charter JSON error envelopes, and
  command/skill manifest repair drift.
• Restored upgrade-readiness preference preservation and compatibility hints,
  including uv-tool pytest remediation provenance fallbacks.
• Restored compatibility for older unit-test fakes that do not expose the new
  coordination branch or commit-result fields.