<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/changelog/release-notes-3.2.6/">
  <id>https://docs.spec-kitty.ai/changelog/release-notes-3.2.6/</id>
  <title>Release notes — 3.2.6</title>
  <updated>2026-09-03T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/changelog/release-notes-3.2.6/"/>
  <summary>Consolidated 3.2.6 release notes: the stabilization release hardening fail-loud honesty across the workflow, plus orchestrator-api 1.4.0 for external-host design pipelines.</summary>
  <content type="html">&lt;span id=&quot;release-notes--326&quot;&gt;&lt;/span&gt;
&lt;p&gt;&lt;em&gt;For the Spec Kitty operator or maintainer upgrading an existing project from &lt;code dir=&quot;auto&quot;&gt;v3.2.5&lt;/code&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;3.2.6 is the stabilization release that makes Spec Kitty tell the truth.&lt;/strong&gt; It closes a long list of “reported success while the thing was actually broken” defects — silent status greens, phantom mission restarts, retention policies quietly ignored, timestamps mislabelled, a startup-crashing dependency — and pairs that reliability push with one substantial new capability: &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; contract 1.4.0&lt;/strong&gt;, which lets an external host (a CI pipeline, a custom dashboard, a native driver) run a Mission’s entire design pipeline — &lt;code dir=&quot;auto&quot;&gt;specify → plan → tasks → analyze → decision resolution&lt;/code&gt; — without ever crossing into host-CLI territory. Alongside those, &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; becomes the canonical governing term, sync ships &lt;strong&gt;off by default&lt;/strong&gt; on a bare install, and the CLI gains explicit worktree-owned lifecycle commands, shell autocompletion, and a durable operator-config file.&lt;/p&gt;
&lt;p&gt;The previous stable release was &lt;strong&gt;v3.2.5&lt;/strong&gt; (2026-07-08). This is the finalized &lt;code dir=&quot;auto&quot;&gt;3.2.6&lt;/code&gt;; it supersedes the per-candidate notes for &lt;code dir=&quot;auto&quot;&gt;3.2.6rc1&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;3.2.6rc2&lt;/code&gt;.&lt;/p&gt;
&lt;h2 id=&quot;install--upgrade&quot;&gt;Install / upgrade&lt;/h2&gt;
&lt;div class=&quot;expressive-code&quot;&gt;&lt;figure class=&quot;frame is-terminal not-content&quot;&gt;&lt;figcaption class=&quot;header&quot;&gt;&lt;span class=&quot;title&quot;&gt;&lt;/span&gt;&lt;span class=&quot;sr-only&quot;&gt;Terminal window&lt;/span&gt;&lt;/figcaption&gt;&lt;pre data-language=&quot;bash&quot;&gt;&lt;code&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# New install:&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;pipx&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;install&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;spec-kitty-cli&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;        &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# or: pip install spec-kitty-cli&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;
&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# Existing project:&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;div class=&quot;ec-line&quot;&gt;&lt;div class=&quot;code&quot;&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;spec-kitty&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#3B61B0&quot;&gt;upgrade&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; runs every 3.2.6 migration automatically; each is idempotent and safe to re-run. Read the &lt;strong&gt;Breaking changes&lt;/strong&gt; section below before upgrading — several items need a one-time action, and a few need one command run &lt;em&gt;before&lt;/em&gt; the upgrade reaches the project.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-breaking-changes&quot;&gt;💥 Breaking changes&lt;/h2&gt;
&lt;p&gt;This section is exhaustive. Each item states what breaks and the exact action to take. Read it in full before you upgrade.&lt;/p&gt;
&lt;h3 id=&quot;governance-charter--doctrine-packs&quot;&gt;Governance, charter &amp;#x26; doctrine packs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Built-in doctrine content moved to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; with no compatibility shim&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;relocate-builtin-doctrine-packs&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; any reference to the old &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&amp;#x3C;kind&gt;/built-in/&amp;#x3C;file&gt;&lt;/code&gt; path. &lt;em&gt;Action:&lt;/em&gt; repoint each reference to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&amp;#x3C;kind&gt;/&amp;#x3C;file&gt;&lt;/code&gt; — drop the inner &lt;code dir=&quot;auto&quot;&gt;built-in/&lt;/code&gt; segment. Doctrine &lt;code dir=&quot;auto&quot;&gt;.py&lt;/code&gt; code, &lt;code dir=&quot;auto&quot;&gt;schemas/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;templates/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;skills/&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;missions/&lt;/code&gt; did &lt;strong&gt;not&lt;/strong&gt; move.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An org pack with an unrecognised agent-profile or DRG key now fails to load&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-silence-guards&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a pack carrying a typo’d or retired key that earlier releases silently dropped. &lt;em&gt;Action:&lt;/em&gt; before upgrading, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine --json&lt;/code&gt; and check the &lt;code dir=&quot;auto&quot;&gt;skipped_profiles&lt;/code&gt; list; fix any invalid profile. A pack with an invalid profile is reported unhealthy rather than passing as healthy.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The redundant &lt;code dir=&quot;auto&quot;&gt;context-sources.*&lt;/code&gt; agent-profile block is removed from the schema&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3629&lt;/code&gt;; mission &lt;code dir=&quot;auto&quot;&gt;doctrine-drg-silent-drop-boundary&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a custom profile that still authors &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;directives&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tactics&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;toolguides&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;styleguides&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;doctrine-layers&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;additional&lt;/code&gt;) now fails to load loudly instead of dropping the block in silence. &lt;em&gt;Action:&lt;/em&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; — the &lt;code dir=&quot;auto&quot;&gt;3_3_1_context_sources_consolidation&lt;/code&gt; migration set-merges every reference id onto the canonical &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt; fields. Author references solely on &lt;code dir=&quot;auto&quot;&gt;directive-references&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;tactic-references&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;toolguide-references&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;styleguide-references&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Cross-pack references in an org pack must now be written in full&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-silence-guards&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a bare id in a &lt;code dir=&quot;auto&quot;&gt;drg/&lt;/code&gt; fragment no longer resolves against a &lt;em&gt;different&lt;/em&gt; pack in the same merge — it now raises an &lt;code dir=&quot;auto&quot;&gt;unresolved_edge_endpoint&lt;/code&gt; conflict at merge time. &lt;em&gt;Action:&lt;/em&gt; write each edge endpoint as &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;kind&gt;:&amp;#x3C;id&gt;&lt;/code&gt; (for example &lt;code dir=&quot;auto&quot;&gt;styleguide:acme-sty-001&lt;/code&gt;), or as a bare id declared in that same fragment’s own &lt;code dir=&quot;auto&quot;&gt;nodes:&lt;/code&gt; block.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;pack validate&lt;/code&gt; (and &lt;code dir=&quot;auto&quot;&gt;doctrine org validate&lt;/code&gt;) now fail (exit 1) for three previously-passing org-pack shapes&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3387&lt;/code&gt;; mission &lt;code dir=&quot;auto&quot;&gt;org-pack-authoring-diagnostics&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a merge-time-skipped agent profile (now &lt;code dir=&quot;auto&quot;&gt;profile_skipped&lt;/code&gt;), a nested &lt;code dir=&quot;auto&quot;&gt;assets/&amp;#x3C;pack&gt;/x.asset.yaml&lt;/code&gt; with a schema violation (now scanned recursively), and DRG content living only under &lt;code dir=&quot;auto&quot;&gt;drg/*.graph.yaml&lt;/code&gt; fragments with no pack-root &lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; (now &lt;code dir=&quot;auto&quot;&gt;drg_root_graph_missing&lt;/code&gt;). &lt;em&gt;Action:&lt;/em&gt; if you maintain an org pack, run &lt;code dir=&quot;auto&quot;&gt;pack validate&lt;/code&gt; and fix all three shapes before adopting the pack.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine&lt;/code&gt; now exits non-zero when an org pack declares an edge endpoint that resolves to nothing&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-silence-guards&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; CI that treated &lt;code dir=&quot;auto&quot;&gt;doctor doctrine&lt;/code&gt; as a green gate over a pack with dangling endpoints. &lt;em&gt;Action:&lt;/em&gt; resolve the dangling endpoints the report names. &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; reports the same problems in its &lt;code dir=&quot;auto&quot;&gt;errors&lt;/code&gt; array but deliberately keeps exit code 0, so scripts keying on &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt;’s exit code are unaffected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;rtk-search-tooling&lt;/code&gt; toolguide is removed&lt;/strong&gt;, including from the default charter pack (&lt;code dir=&quot;auto&quot;&gt;3.2.6_retire_rtk_search_tooling&lt;/code&gt; migration). &lt;em&gt;What breaks:&lt;/em&gt; a project still holding the stale &lt;code dir=&quot;auto&quot;&gt;activated_toolguides&lt;/code&gt; entry would hard-fail its next charter compile with &lt;code dir=&quot;auto&quot;&gt;UnknownArtifactIdError&lt;/code&gt;. &lt;em&gt;Action:&lt;/em&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; — the migration strips the entry from &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt;, does nothing on a project that never had it, and is safe to re-run. If you want RTK guidance, keep it in your own org pack.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;sync-tracker--auth&quot;&gt;Sync, tracker &amp;#x26; auth&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The legacy local-sync surface is now deactivated by default; opt in with &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC=1&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3799&lt;/code&gt;; mission &lt;code dir=&quot;auto&quot;&gt;sync-deactivate-by-default&lt;/code&gt;; folds &lt;code dir=&quot;auto&quot;&gt;#3470&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#2801&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#2809&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a bare install now spawns &lt;strong&gt;no&lt;/strong&gt; sync daemon and emits &lt;strong&gt;no&lt;/strong&gt; events — zero background processes and zero network egress on the default path. &lt;em&gt;Action:&lt;/em&gt; existing sync users must set &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC=1&lt;/code&gt; (a per-shell &lt;code dir=&quot;auto&quot;&gt;export&lt;/code&gt;, a per-repo &lt;code dir=&quot;auto&quot;&gt;.kittify/.kitty.env&lt;/code&gt; entry, or per-invocation) to retain the daemon and event emission. Deactivation does not kill a daemon a prior opted-in session left running — &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync doctor&lt;/code&gt; surfaces an advisory and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor restart-daemon&lt;/code&gt; retires it. Arming stays strictly upstream of the per-project egress &lt;em&gt;consent&lt;/em&gt; gate; it never replaces or weakens consent. The pre-review regression gate is cut off the shared sync toggles onto its own &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PRE_REVIEW_GATE_DISABLE&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Local tracker providers (&lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;) now require a recorded egress decision&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;tracker-egress-refusal-3108&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a &lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt; binding that never recorded hosted-sync consent and has no &lt;code dir=&quot;auto&quot;&gt;tracker.egress&lt;/code&gt; key stops syncing on upgrade (only &lt;code dir=&quot;auto&quot;&gt;sync pull&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;push&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;run&lt;/code&gt; are gated; &lt;code dir=&quot;auto&quot;&gt;bind&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;unbind&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;map add&lt;/code&gt; stay available). &lt;em&gt;Action:&lt;/em&gt; record &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; to keep local sync without consenting to hosted sync at all, &lt;strong&gt;or&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt; / set &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt; to consent to hosted sync. Absence at both channels denies by design.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Hosted-sync consent is now per-project, and the shared-store &lt;code dir=&quot;auto&quot;&gt;sync migrate&lt;/code&gt; is retired&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3262&lt;/code&gt;; mission &lt;code dir=&quot;auto&quot;&gt;per-project-sync-consent-ledgers&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; the old shared-store &lt;code dir=&quot;auto&quot;&gt;sync migrate&lt;/code&gt; now refuses with guidance, and &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC&lt;/code&gt; is strictly deny-only as a consent signal (arming it grants nothing on its own). &lt;em&gt;Action:&lt;/em&gt; each project keeps its own isolated consent ledger; &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt; is the sole local grant. Use the copy-only, resumable cutover commands (&lt;code dir=&quot;auto&quot;&gt;sync project-store-preview&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;-migrate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;-status&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;-quarantine&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;-history&lt;/code&gt;) to move existing history. See &lt;code dir=&quot;auto&quot;&gt;docs/guides/project-sync-consent.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;missions-gates--lifecycle&quot;&gt;Missions, gates &amp;#x26; lifecycle&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A legacy &lt;code dir=&quot;auto&quot;&gt;{&quot;mission&quot;: …}&lt;/code&gt;-only Mission now stops resolving its type&lt;/strong&gt; and goes neutral/typeless (&lt;code dir=&quot;auto&quot;&gt;#3598&lt;/code&gt;; epic &lt;code dir=&quot;auto&quot;&gt;#3410&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; the canonical reader drops the legacy &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt; field and the silent &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; default, and this &lt;strong&gt;compounds&lt;/strong&gt; with the per-type hard-fail — a legacy Mission that used to mask as &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; can go type-unresolvable. &lt;em&gt;Action (program-ordered):&lt;/em&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-mission-type&lt;/code&gt; against the project &lt;strong&gt;before&lt;/strong&gt; this change reaches it (it mints a profile-resolving &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; into every legacy Mission and never fabricates an unresolvable type), then gate with &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-type --fail-on legacy-key-only,typeless,error&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; now block on requirements written as bare prose&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3396&lt;/code&gt;; mission &lt;code dir=&quot;auto&quot;&gt;bare-prose-requirements-uncounted&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a spec whose requirements are bare sentences (no &lt;code dir=&quot;auto&quot;&gt;FR/NFR/C&lt;/code&gt; id) used to pass the coverage gate as covered. &lt;em&gt;Action:&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; now refuses to advance past the tasks boundary and &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; exits non-zero, listing the uncounted requirement ids — give each requirement a first-class id.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A custom mission family that ships its own &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt; now genuinely blocks on unmet &lt;code dir=&quot;auto&quot;&gt;blocking: true&lt;/code&gt; requirements&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3704&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; an in-flight custom Mission previously advancing silently past a step whose declared, &lt;code dir=&quot;auto&quot;&gt;blocking: true&lt;/code&gt; artifact was never produced may now correctly &lt;strong&gt;block&lt;/strong&gt; on its next evaluation. &lt;em&gt;Action:&lt;/em&gt; produce the declared artifact (or fix the manifest). The four built-in families are byte-identical; an unregistered family with no manifest still runs to completion as before. In-flight Missions are not retroactively re-evaluated.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt; with an unknown or typo’d key now fails loud&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3413&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3542&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a misspelled key used to be silently discarded, so the requirement vanished. &lt;em&gt;Action:&lt;/em&gt; the loader now raises &lt;code dir=&quot;auto&quot;&gt;ManifestSchemaError&lt;/code&gt; naming the file (across &lt;code dir=&quot;auto&quot;&gt;reconcile&lt;/code&gt;, background dossier sync, and version resolution, including org-authored manifests) — fix the key to the schema.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Review rejections now require a rationale&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3307&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3444&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a rejection travels to the hosted dashboard as &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;, so an empty rationale is refused. &lt;em&gt;Action:&lt;/em&gt; pass &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; when rejecting a work package; the backward review move now correctly carries &lt;code dir=&quot;auto&quot;&gt;force=True&lt;/code&gt; and the rationale on the wire.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The event log is the single authority for a work package’s review verdict&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;; mission &lt;code dir=&quot;auto&quot;&gt;verdict-seam-write-unification&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; automation that read the &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;verdict&lt;/code&gt; field as truth. &lt;em&gt;Action:&lt;/em&gt; read the &lt;code dir=&quot;auto&quot;&gt;review_result&lt;/code&gt; event in &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;; the Markdown render is now best-effort and non-authoritative. An &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; migration backfills stranded terminal &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt; verdicts.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission-mutating &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; now fail closed when run from a foreign checkout&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3128&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3129&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; a command run from a linked lane worktree that used to silently act on the primary checkout. &lt;em&gt;Action:&lt;/em&gt; run mission-mutating commands from the owned checkout (reads and planning are unaffected); a foreign checkout now raises a &lt;code dir=&quot;auto&quot;&gt;CheckoutIdentityError&lt;/code&gt; naming the target checkout.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-apis--automation-contracts&quot;&gt;Internal APIs &amp;#x26; automation contracts&lt;/h3&gt;
&lt;p&gt;These affect only callers scripting against Spec Kitty internals, parsing its JSON, or importing its modules.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt; is removed; importing it raises &lt;code dir=&quot;auto&quot;&gt;ImportError&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#2886&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3014&lt;/code&gt;). &lt;em&gt;Action:&lt;/em&gt; replace the call with &lt;code dir=&quot;auto&quot;&gt;placement_seam(root, slug).read_dir(&amp;#x3C;kind&gt;)&lt;/code&gt; for the artifact kind you need.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Seven &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt; types are no longer re-exported from &lt;code dir=&quot;auto&quot;&gt;specify_cli.dossier&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3677&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;from specify_cli.dossier import ArtifactIdentity&lt;/code&gt; (and the six other moved types) now raises &lt;code dir=&quot;auto&quot;&gt;ImportError&lt;/code&gt;. &lt;em&gt;Action:&lt;/em&gt; import these types directly from &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt;. The four &lt;code dir=&quot;auto&quot;&gt;emit_*&lt;/code&gt; re-exports are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The two exported event emitters take a metadata object, not tail kwargs&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3317&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; out-of-tree callers of &lt;code dir=&quot;auto&quot;&gt;emit_wp_status_changed&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;emit_token_usage_recorded&lt;/code&gt; (re-exported from the &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; facade) that passed &lt;code dir=&quot;auto&quot;&gt;causation_id&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;force&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;evidence&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;run_id&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;provider&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt; as individual kwargs. &lt;em&gt;Action:&lt;/em&gt; pass a &lt;code dir=&quot;auto&quot;&gt;WPStatusChangeMetadata&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;TokenUsageMetadata&lt;/code&gt; object via the keyword-only &lt;code dir=&quot;auto&quot;&gt;metadata=&lt;/code&gt; parameter.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission setup-plan&lt;/code&gt; changes its unauthenticated-host contract&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3621&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; automation that branched on the old exit code &lt;code dir=&quot;auto&quot;&gt;2&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;SAAS_SYNC_UNAUTHENTICATED&lt;/code&gt; error for an unauthenticated host. &lt;em&gt;Action:&lt;/em&gt; the command now exits &lt;code dir=&quot;auto&quot;&gt;0&lt;/code&gt; whenever local verification succeeds and reports hosted-sync unavailability as a nonfatal &lt;code dir=&quot;auto&quot;&gt;warnings[].code&lt;/code&gt; diagnostic — read that instead.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; bumps its schema and moves its charter-presence authority&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#2787&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3489&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; consumers parsing the payload. &lt;em&gt;Action:&lt;/em&gt; pin the new top-level &lt;code dir=&quot;auto&quot;&gt;context_schema_version&lt;/code&gt; (now &lt;code dir=&quot;auto&quot;&gt;1.1.0&lt;/code&gt;, adding a typed &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt; array); read &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; as the authority of record for &lt;code dir=&quot;auto&quot;&gt;project_charter.present&lt;/code&gt; (a project with only an uncompiled &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; now reports &lt;code dir=&quot;auto&quot;&gt;present: false&lt;/code&gt;, with new additive &lt;code dir=&quot;auto&quot;&gt;charter_md_present&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;charter_md_path&lt;/code&gt; keys).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt;’s committed &lt;code dir=&quot;auto&quot;&gt;analysis-report.md&lt;/code&gt; now records repo-relative &lt;code dir=&quot;auto&quot;&gt;input_artifacts.*.path&lt;/code&gt; values&lt;/strong&gt; (ledger SK-63). &lt;em&gt;What breaks:&lt;/em&gt; tooling that parsed those paths expecting absolute filesystem paths. &lt;em&gt;Action:&lt;/em&gt; expect a repo-relative path.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The printed rejection feedback-file path changed&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3554&lt;/code&gt;). &lt;em&gt;What breaks:&lt;/em&gt; automation hardcoding &lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;wp&gt;/review-cycle-N.md&lt;/code&gt; as the feedback target (which the provenance guard always refused). &lt;em&gt;Action:&lt;/em&gt; write feedback to &lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;wp&gt;/review-feedback-N.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;spec-kittys-own-ci-contributors-only&quot;&gt;Spec Kitty’s own CI (contributors only)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A push to a protected branch now starts 49 of 50 test jobs instead of about 10&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#2957&lt;/code&gt;). Pull requests are unaffected — path filtering still narrows a PR to the suites its diff touches. This is a deliberate trade of CI minutes for coverage on the branch where frozen contracts must actually run. No action for consumer projects.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-added&quot;&gt;✨ Added&lt;/h2&gt;
&lt;h3 id=&quot;orchestrator-api--external-hosts&quot;&gt;orchestrator-api &amp;#x26; external hosts&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; contract 1.3.0 → 1.4.0 adds 11 design-phase verbs&lt;/strong&gt; so an external host can drive &lt;code dir=&quot;auto&quot;&gt;specify → plan → tasks → check-prerequisites/record-analysis → decision resolution&lt;/code&gt; without any host-CLI crossing (&lt;code dir=&quot;auto&quot;&gt;#3837&lt;/code&gt;; mission &lt;code dir=&quot;auto&quot;&gt;design-phase-orchestrator-api&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt; scaffold and validate a Mission’s design artifacts; &lt;code dir=&quot;auto&quot;&gt;open-decision&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;resolve-decision&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;defer-decision&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;cancel-decision&lt;/code&gt; operate the decision ledger (each rejecting an empty rationale/final-answer, which also hardens &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; decision resolution); &lt;code dir=&quot;auto&quot;&gt;design-status&lt;/code&gt; is a read-only fail-closed query; and &lt;code dir=&quot;auto&quot;&gt;answer-decision&lt;/code&gt; resolves a &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;decision_required&lt;/code&gt; moment with full host-CLI event/lifecycle parity. Purely additive — all 21 commands and 51 error codes coexist and no existing verb changed. The 1.3.0 groundwork also added &lt;code dir=&quot;auto&quot;&gt;--review-result-json&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;orchestrator-api transition&lt;/code&gt; so a host can submit a structured review outcome without forcing a lane transition. See &lt;a href=&quot;/api/orchestrator-api/#design-phase-commands&quot;&gt;Orchestrator API Reference § Design-Phase Commands&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;explicit-worktree-owned-lifecycle&quot;&gt;Explicit worktree-owned lifecycle&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; now works across the whole single-branch Mission lifecycle&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3843&lt;/code&gt;; extends &lt;code dir=&quot;auto&quot;&gt;#3346&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3787&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-09-03-1&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;agent tasks mark-status&lt;/code&gt; all accept &lt;code dir=&quot;auto&quot;&gt;--owned-checkout PATH&lt;/code&gt; and route reads, writes, status events, and commits through one validated owned root, so an agent operating from a task-owned worktree can run a Mission end-to-end. Owned mode is &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;-only for now (a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; Mission is refused with a structured error rather than mis-routed); flagless behavior is byte-for-byte unchanged.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;charter-doctrine--packs&quot;&gt;Charter, doctrine &amp;#x26; packs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; is now the canonical governing term&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3664&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3732&lt;/code&gt;; mission arc &lt;code dir=&quot;auto&quot;&gt;retire-doctrine-term&lt;/code&gt;). The glossary authorities and &lt;code dir=&quot;auto&quot;&gt;docs/context/charter.md&lt;/code&gt; (renamed from &lt;code dir=&quot;auto&quot;&gt;doctrine.md&lt;/code&gt;) speak &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;; the internal &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; code package is relocated to &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; with a real &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; module split; and every operator-facing &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; surface keeps working through a one-time deprecation warning — &lt;code dir=&quot;auto&quot;&gt;import doctrine&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; CLI group (now an alias of &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter&lt;/code&gt;), the &lt;code dir=&quot;auto&quot;&gt;governance.doctrine&lt;/code&gt; selection key (mapped forward), the &lt;code dir=&quot;auto&quot;&gt;doctrine.org.packs&lt;/code&gt; path, and the &lt;code dir=&quot;auto&quot;&gt;doctrine:&lt;/code&gt; synthesizer URN prefix (event logs keep parsing both). &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; migrates &lt;code dir=&quot;auto&quot;&gt;interview/answers.yaml&lt;/code&gt; preserving every answer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; is now non-destructive by default&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3270&lt;/code&gt;; folds &lt;code dir=&quot;auto&quot;&gt;#2777&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3052&lt;/code&gt;). It preserves backed governance content and reconciles against the on-disk graph; &lt;code dir=&quot;auto&quot;&gt;--prune&lt;/code&gt; is the explicit opt-in for removal and &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; previews. The &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; boundary self-heals instead of hard-blocking until you resynthesize.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Org and project doctrine packs are now genuinely usable end-to-end&lt;/strong&gt; — a new &lt;code dir=&quot;auto&quot;&gt;ORG&lt;/code&gt; resolution tier ships templates and mission-FSM content, layered packs contribute end-to-end mission types with real action sequences, a chain of multiple org packs merges correctly, and cascade follows &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edges an org pack authors in &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3524&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3424&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3520&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3572&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3534&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2829&lt;/code&gt;). A unified &lt;code dir=&quot;auto&quot;&gt;pack-manifest.yaml&lt;/code&gt; schema now spans built-in/org/fetched/charter packs (&lt;code dir=&quot;auto&quot;&gt;#3500&lt;/code&gt;–&lt;code dir=&quot;auto&quot;&gt;#3503&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-16-1&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New doctrine surfaces reach the agent that earlier releases silently dropped&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt; become first-class doctrine kinds (&lt;code dir=&quot;auto&quot;&gt;#2495&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2469&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3037&lt;/code&gt;); glossary packs, procedure/tactic step descriptions, and &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;-edge paradigms/tactics now render in delivery (&lt;code dir=&quot;auto&quot;&gt;#3489&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3063&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; ships a typed &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt; array; and the four consolidated charter-bundle files fold into one authoritative &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; (schema &lt;code dir=&quot;auto&quot;&gt;2.0.0&lt;/code&gt;) with a deterministic upgrade migration (&lt;code dir=&quot;auto&quot;&gt;#2773&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-type&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; gain honesty surfaces&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;doctor mission-type&lt;/code&gt; classifies whether every Mission’s type resolves (six states, &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--fail-on&lt;/code&gt; for CI); &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; exposes a top-level &lt;code dir=&quot;auto&quot;&gt;directives_source&lt;/code&gt; provenance field and fail-loud directive-resolution diagnostics (&lt;code dir=&quot;auto&quot;&gt;#3402&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3728&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-show-me&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spk-run-verdict-capture&lt;/code&gt; skills&lt;/strong&gt; ship shared doctrine for choosing an explanatory diagram and for recording a review verdict identically across every agent harness (&lt;code dir=&quot;auto&quot;&gt;#3528&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;missions--lifecycle&quot;&gt;Missions &amp;#x26; lifecycle&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A deliberately-canceled work package is now an honest Mission ending&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#2945&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3590&lt;/code&gt;). Cancellation provenance is a first-class, operator-authored &lt;code dir=&quot;auto&quot;&gt;reason_source&lt;/code&gt; on the status event, and a single &lt;code dir=&quot;auto&quot;&gt;is_acceptable_ending&lt;/code&gt; authority lets &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; admit a &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt; WP only when it carries operator provenance; a synthetic (undocumented) cancellation is refused. &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; also gains an advisory &lt;code dir=&quot;auto&quot;&gt;check-terminability&lt;/code&gt; warning that flags, at planning time, a work package whose acceptance can only be observed after integration.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Runtime work-package state now lives in the append-only event log&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#2684&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2816&lt;/code&gt;) — &lt;code dir=&quot;auto&quot;&gt;tasks/WP##.md&lt;/code&gt; frontmatter is no longer a runtime authority; &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-runtime-state&lt;/code&gt; seeds and verifies the cutover.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty intake&lt;/code&gt; recognises an optional v1 handoff packet&lt;/strong&gt; so an upstream requirements tool can seed a Mission’s FR/AC ids (&lt;code dir=&quot;auto&quot;&gt;docs/contracts/handoff-packet-v1.md&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;intake --auto&lt;/code&gt; scans &lt;code dir=&quot;auto&quot;&gt;.handoff/*.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard work-package cards&lt;/strong&gt; now show subtask progress (&lt;code dir=&quot;auto&quot;&gt;2/4 subtasks&lt;/code&gt;) and a deterministic colored avatar for the assigned agent profile (&lt;code dir=&quot;auto&quot;&gt;#2504&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#647&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;sync-tracker--operator-config&quot;&gt;Sync, tracker &amp;#x26; operator config&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync import-history&lt;/code&gt;&lt;/strong&gt; materializes existing local Mission history into the hosted projection with deterministic, idempotent event ids and fail-closed server preflight (&lt;code dir=&quot;auto&quot;&gt;#2262&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A two-tier &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; operator-config file&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_HOME}/.kitty.env&lt;/code&gt; machine-wide, overridden per-repo) loads before any &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; module imports, so operator environment is durable instead of per-shell (&lt;code dir=&quot;auto&quot;&gt;#3495&lt;/code&gt;); committed doctrine provenance is now portable across machines and wheels via a &lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_PACKS_ROOT}&lt;/code&gt; token (&lt;code dir=&quot;auto&quot;&gt;#3494&lt;/code&gt;); and an opt-in &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PRERELEASE&lt;/code&gt; channel surfaces pinned release candidates (&lt;code dir=&quot;auto&quot;&gt;#3496&lt;/code&gt;). New &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; facets: &lt;code dir=&quot;auto&quot;&gt;provenance&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;env-file&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;channel&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;cli-ux&quot;&gt;CLI UX&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shell autocompletion, a &lt;code dir=&quot;auto&quot;&gt;-h&lt;/code&gt; short-help alias, and alphabetical command listing&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#2232&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2234&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2235&lt;/code&gt;) — additive, with a committed completion-manifest fast path and no behavior change to existing commands.&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;-fixed&quot;&gt;🐛 Fixed&lt;/h2&gt;
&lt;h3 id=&quot;startup--correctness&quot;&gt;Startup &amp;#x26; correctness&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; no longer crashes on startup after installing typer 0.27.2&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3782&lt;/code&gt;). typer 0.27.2 removed &lt;code dir=&quot;auto&quot;&gt;Abort&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Exit&lt;/code&gt; from a vendored module whose eager &lt;code dir=&quot;auto&quot;&gt;getattr&lt;/code&gt; fallback broke every &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; subprocess at import; a defensive resolver now degrades gracefully across the vendored module, its submodule, &lt;code dir=&quot;auto&quot;&gt;typer&lt;/code&gt;, and standalone &lt;code dir=&quot;auto&quot;&gt;click&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every CLI command’s cold-import boundary is restored&lt;/strong&gt; — commands no longer eagerly load the status-orchestration and workspace machinery, a regression the explicit-owned-checkout work had introduced (restores the &lt;code dir=&quot;auto&quot;&gt;#1461&lt;/code&gt; boundary; new architectural gate enforces it).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Timestamps Spec Kitty writes into your project are now correct aware-UTC&lt;/strong&gt; instead of local time mislabelled as UTC — ~20 sites (charter backup filenames, status-event stamps, auth-doctor report times) now flow through one &lt;code dir=&quot;auto&quot;&gt;kernel.clock&lt;/code&gt; producer (&lt;code dir=&quot;auto&quot;&gt;#3305&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3289&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;status-honesty--success-that-was-actually-broken&quot;&gt;Status honesty — “success” that was actually broken&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Auth and sync diagnostics are now derived from evidence&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3723&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;sync status&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;auth status&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;auth doctor&lt;/code&gt; route through one typed &lt;code dir=&quot;auto&quot;&gt;HealthVerdict&lt;/code&gt; authority (tri-state &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt;, headline computed from state, mandatory evidence for a definite claim); an expired token whose refresh chain can’t be verified resolves to &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;, never a false green. &lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; no longer reports “healthy” while the server probe disagrees, and &lt;code dir=&quot;auto&quot;&gt;sync status&lt;/code&gt; names an unreachable/decommissioned server with the exact recovery command (&lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; no longer restarts a merged Mission or stalls on a canceled work package&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#2947&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3780&lt;/code&gt;). The loop now decides from the committed status authority — a merged Mission returns &lt;code dir=&quot;auto&quot;&gt;terminal&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; instead of fabricating a fresh run against a stale coordination worktree, and an operator-canceled-with-provenance WP advances instead of stalling. &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; also serves the charter-freshness verdict from a per-repo content-hash cache instead of re-parsing the whole charter on every call (&lt;code dir=&quot;auto&quot;&gt;#3787&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A fail-loud sweep closed silent-drop defects at a dozen ground-level sites&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3578&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3548&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3517&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3412&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2991&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3624&lt;/code&gt;, and others). Each now emits the human-readable half of its contract through an existing operator-visible surface: &lt;code dir=&quot;auto&quot;&gt;orchestrator_api&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;_fail()&lt;/code&gt; keeps its &lt;code dir=&quot;auto&quot;&gt;message&lt;/code&gt; when structured &lt;code dir=&quot;auto&quot;&gt;data&lt;/code&gt; is passed; the sync emitter no longer returns a durably-unqueued event as publishable; a malformed manifest fails loud distinct from “absent”; and the background sync daemon resolves a &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;-capable interpreter before spawning instead of trusting a bare &lt;code dir=&quot;auto&quot;&gt;sys.executable&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review verdicts, arbiter overrides, and approvals are durable and single-authority&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3044&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3235&lt;/code&gt;, ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-03-1&lt;/code&gt;). Approving a work package after a rejection sticks with no &lt;code dir=&quot;auto&quot;&gt;--skip-review-artifact-check&lt;/code&gt; flag; a concurrent review-cycle commit can no longer race into a silently-lost verdict (a checkout-wide serialization queue wraps the whole write); and an arbiter override persists across a fresh clone and clears the merge gate on its own, recorded as its own first-class outcome rather than posing as a reviewer approval.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;merge--retention&quot;&gt;Merge &amp;#x26; retention&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; now honors a Mission’s declared retention policy&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3131&lt;/code&gt;). A Mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; can carry &lt;code dir=&quot;auto&quot;&gt;retain_branches&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;retain_worktrees&lt;/code&gt;; merge resolves cleanup via &lt;code dir=&quot;auto&quot;&gt;resolve_merge_retention&lt;/code&gt; with precedence explicit-CLI-flag &gt; meta.json &gt; default, failing closed toward retention on ambiguity, and tears down (or keeps) the coordination branch/worktree/marker as one coupled decision. An explicit delete override still works but prints a notice naming the contradicted policy. Mint with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission create --retain-branches --retain-worktrees&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Merge no longer discards acceptance/issue-matrix evidence or resets a filled gate artifact to a scaffold&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#2804&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2709&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3232&lt;/code&gt;). Custom merge drivers keep whichever side carries evidence; squash merges reconcile per artifact class; and rollback/&lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; stay coherent after a failed target advance (&lt;code dir=&quot;auto&quot;&gt;#2711&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2786&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;commit-boundary--workspace-integrity&quot;&gt;Commit-boundary &amp;#x26; workspace integrity&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Lifecycle commands on a protected-primary / coordination-topology Mission no longer leave a dirty tree, report false success, or refuse with un-followable guidance&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;commit-boundary-router-integrity&lt;/code&gt;; epic &lt;code dir=&quot;auto&quot;&gt;#2739&lt;/code&gt;; fixes &lt;code dir=&quot;auto&quot;&gt;#3784&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2693&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3716&lt;/code&gt;). The commit-router, the protected-primary refusal, and coordination-topology routing now agree on where planning artifacts land — &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s claim commit excludes any &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;-nested path, &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; commits its scaffold transactionally and discloses &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; as uncommitted, and &lt;code dir=&quot;auto&quot;&gt;mission close --discard&lt;/code&gt; leaves a clean tree.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement --base &amp;#x3C;ref&gt;&lt;/code&gt; actually roots the lane on the ref, and hard-errors instead of faking success when it can’t&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3616&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3571&lt;/code&gt;, plus follow-ups). The override is threaded into the topology-aware allocator; an unhonorable route raises a typed &lt;code dir=&quot;auto&quot;&gt;UnhonorableBaseError&lt;/code&gt; naming the route, work package, and base rather than printing a fabricated success line. A shared allocation seam plus a CI anti-bypass guard prevent the class recurring (&lt;code dir=&quot;auto&quot;&gt;#3460&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3462&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3536&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A command run from a linked lane worktree no longer silently acts on the primary checkout&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3129&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3346&lt;/code&gt;) — a checkout-identity guard distinguishes owned from foreign worktrees and fails closed, and &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; run correctly from a caller-owned worktree with isolated state.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;charter-doctrine--gates&quot;&gt;Charter, doctrine &amp;#x26; gates&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --include directive:&amp;#x3C;id&gt;&lt;/code&gt; resolves the exact ids the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; surface advertises&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3816&lt;/code&gt;) — the directive selector now normalizes slug, numeric, and &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_NNN&lt;/code&gt; forms through one canonical authority, closing a divergence that also silently dropped every directive from the gated &lt;code dir=&quot;auto&quot;&gt;DoctrineService.directives&lt;/code&gt; property.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate --from-interview&lt;/code&gt; reports a present-but-corrupt &lt;code dir=&quot;auto&quot;&gt;answers.yaml&lt;/code&gt; honestly&lt;/strong&gt; instead of claiming no answers exist (&lt;code dir=&quot;auto&quot;&gt;#2940&lt;/code&gt;); &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate mission-type &amp;#x3C;T&gt;&lt;/code&gt; refuses a type that resolves an empty action sequence&lt;/strong&gt; before writing (&lt;code dir=&quot;auto&quot;&gt;#3717&lt;/code&gt;); and &lt;strong&gt;a single project-local &lt;code dir=&quot;auto&quot;&gt;directives:&lt;/code&gt; entry is now additive&lt;/strong&gt; instead of silently replacing the whole resolved set (&lt;code dir=&quot;auto&quot;&gt;#3728&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --cascade&lt;/code&gt; names every asset/template node it did not cascade&lt;/strong&gt; instead of silently dropping them (&lt;code dir=&quot;auto&quot;&gt;#3705&lt;/code&gt;), and &lt;strong&gt;a malformed &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; in one pack no longer drops the other packs’ fragments&lt;/strong&gt; — the degrade is now per-pack with an operator-visible warning (&lt;code dir=&quot;auto&quot;&gt;#3629&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Governance now reaches the deciding gate, not the implementer&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;governance-at-the-gate&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3685&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3682&lt;/code&gt;) — decision-documentation is delivered at &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; (removed from &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, so smaller models stop stalling mid-implementation to demand sign-off), enforcement levels carry an explicit rank, and the review/accept gates capture real bound evidence.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;sync-tracker--auth-1&quot;&gt;Sync, tracker &amp;#x26; auth&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Review rejections reach the hosted dashboard again&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3307&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3444&lt;/code&gt;) — the backward review move now emits &lt;code dir=&quot;auto&quot;&gt;force=True&lt;/code&gt; and threads &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;, satisfying the wire contract the hosted endpoint enforces.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Machines that never ran the layout migration now capture sync events for real&lt;/strong&gt; instead of silently capturing zero while reporting success (&lt;code dir=&quot;auto&quot;&gt;#3425&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3497&lt;/code&gt;); &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;auth login&lt;/code&gt; resolves the then-current hosted URL&lt;/strong&gt; when unset (the current endpoint is &lt;code dir=&quot;auto&quot;&gt;https://team.spec-kitty.ai&lt;/code&gt;) (&lt;code dir=&quot;auto&quot;&gt;#3297&lt;/code&gt;); and a batch-400 poison event no longer strands its whole batch (&lt;code dir=&quot;auto&quot;&gt;#2736&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2755&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hosted event-sync delivers again for consented projects&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;#3564&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3620&lt;/code&gt;) — &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; no longer self-blocks on an admission gate whose server endpoint isn’t deployed, and &lt;code dir=&quot;auto&quot;&gt;import-history --apply&lt;/code&gt; honors the server’s own preflight success.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;sync share &amp;#x3C;team&gt;&lt;/code&gt; no longer crashes first-run while it self-heals&lt;/strong&gt;, and &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;auth status&lt;/code&gt; now shows each team’s slug&lt;/strong&gt; that &lt;code dir=&quot;auto&quot;&gt;sync share&lt;/code&gt; requires (&lt;code dir=&quot;auto&quot;&gt;#3699&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3731&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;upgrade--migrations&quot;&gt;Upgrade &amp;#x26; migrations&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; obeys your &lt;code dir=&quot;auto&quot;&gt;auto_commit&lt;/code&gt; opt-out, survives its own re-run, and stops misreporting success or failure&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;upgrade-command-hardening&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3651&lt;/code&gt; and cluster). Read-only generated files route through one restore→write→re-protect writer (no more ~30 &lt;code dir=&quot;auto&quot;&gt;Permission denied&lt;/code&gt; errors on re-run); the commit decision defers to &lt;code dir=&quot;auto&quot;&gt;get_auto_commit_default&lt;/code&gt; and says so when it leaves changes uncommitted; a destructive mission-state repair is a separately-scoped consent gate; and a single finalizer derives the exit code once.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; no longer silently drops skill-content migrations on Windows&lt;/strong&gt; when the managed &lt;code dir=&quot;auto&quot;&gt;SKILL.md&lt;/code&gt; is read-only (&lt;code dir=&quot;auto&quot;&gt;#3771&lt;/code&gt;), and &lt;strong&gt;refreshes a stale &lt;code dir=&quot;auto&quot;&gt;.claude/CLAUDE.md&lt;/code&gt; orientation surface&lt;/strong&gt; rather than leaving an outdated version string (&lt;code dir=&quot;auto&quot;&gt;#2265&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; gitignores the &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; root&lt;/strong&gt; (with an &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; backfill) so a mission worktree no longer shows in &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3689&lt;/code&gt;), and &lt;strong&gt;no longer blanket-gitignores all of &lt;code dir=&quot;auto&quot;&gt;.cursor/&lt;/code&gt;&lt;/strong&gt; for teams versioning their own Cursor rules (&lt;code dir=&quot;auto&quot;&gt;#2498&lt;/code&gt;). Several upgrade-wedge failures that left a stuck migration with no self-service exit are fixed (&lt;code dir=&quot;auto&quot;&gt;#3383&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;️-changed&quot;&gt;♻️ Changed&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty --version&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;-v&lt;/code&gt; is now a single copyable line&lt;/strong&gt; — no ASCII-art banner before the version string (community contribution by @zohar).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One canonical mission-type reader&lt;/strong&gt; replaces ~10–12 hand-rolled &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; readers that disagreed on field order and default; the dashboard, retrospectives, and identity now show a Mission’s &lt;em&gt;true&lt;/em&gt; type instead of masking everything as &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3598&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-22-1&lt;/code&gt;). See the Breaking-changes note on the &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-mission-type&lt;/code&gt; program ordering.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output is plain regardless of terminal colour&lt;/strong&gt; — ~77 ad-hoc &lt;code dir=&quot;auto&quot;&gt;Console()&lt;/code&gt; sites moved onto one &lt;code dir=&quot;auto&quot;&gt;CliConsole&lt;/code&gt; seam with an architectural guard (&lt;code dir=&quot;auto&quot;&gt;#2632&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-07-14-1&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Wall-clock performance tests moved off the PR path&lt;/strong&gt; to a dedicated statistical &lt;code dir=&quot;auto&quot;&gt;performance.yml&lt;/code&gt; pipeline (&lt;code dir=&quot;auto&quot;&gt;pytest-benchmark&lt;/code&gt;, per-domain baselines), after a false-red audit found 58.6% of CI failures were inactionable flake; a weekly &lt;code dir=&quot;auto&quot;&gt;ci-flake-report.yml&lt;/code&gt; now measures the false-red rate, and &lt;code dir=&quot;auto&quot;&gt;CI Quality&lt;/code&gt; fails a draft PR fast while running a ready PR to completion (ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-22-1&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3595&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3669&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Skill projection delivers real copies, never absolute symlinks&lt;/strong&gt;, healing dangling links in dev containers and sandboxes (&lt;code dir=&quot;auto&quot;&gt;#2412&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-07-19-1&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;ExecutionMode&lt;/code&gt; three-way name collision is untangled&lt;/strong&gt; — the ownership enum is renamed &lt;code dir=&quot;auto&quot;&gt;WorkProductKind&lt;/code&gt; (member string values unchanged, so WP frontmatter stays wire-compatible), the dead runtime duplicate is retired, and a re-drift guard prevents recurrence (&lt;code dir=&quot;auto&quot;&gt;#3416&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Docs consolidated under one predictable &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; root&lt;/strong&gt; with user (&lt;code dir=&quot;auto&quot;&gt;guides/&lt;/code&gt;) vs contributor (&lt;code dir=&quot;auto&quot;&gt;development/&lt;/code&gt;) split and old-URL redirects, and docs can now be marked &lt;code dir=&quot;auto&quot;&gt;durable&lt;/code&gt; so a standing reference is never flagged as a stale draft (&lt;code dir=&quot;auto&quot;&gt;#2215&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3368&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;p&gt;For the complete, line-by-line list of every change — every Added, Fixed, Changed, and Breaking entry with its full before→after detail — see the &lt;code dir=&quot;auto&quot;&gt;[3.2.6rc1]&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;[3.2.6rc2]&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;[Unreleased]&lt;/code&gt; (3.2.6rc4) sections of the &lt;a href=&quot;/changelog/CHANGELOG/&quot;&gt;canonical CHANGELOG&lt;/a&gt;.&lt;/p&gt;</content>
</entry>
