<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/changelog/CHANGELOG/">
  <id>https://docs.spec-kitty.ai/changelog/CHANGELOG/</id>
  <title>Changelog</title>
  <updated>2026-11-09T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/changelog/CHANGELOG/"/>
  <summary>Canonical changelog for the Spec Kitty CLI and templates, following Keep a Changelog and Semantic Versioning, with added, breaking, and fixed entries per release.</summary>
  <content type="html">&lt;span id=&quot;changelog&quot;&gt;&lt;/span&gt;

&lt;p&gt;All notable changes to the Spec Kitty CLI and templates are documented here.&lt;/p&gt;
&lt;p&gt;The format is based on &lt;a href=&quot;https://keepachangelog.com/en/1.0.0/&quot;&gt;Keep a Changelog&lt;/a&gt;,
and this project adheres to &lt;a href=&quot;https://semver.org/spec/v2.0.0.html&quot;&gt;Semantic Versioning&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;unreleased---400rc9&quot;&gt;[Unreleased] - 4.0.0rc9&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;4.0.0rc9 candidate cycle. Entries land here until the release chore finalizes
this section at publish.&lt;/em&gt;&lt;/p&gt;
&lt;h2 id=&quot;400rc8---2026-11-09&quot;&gt;[4.0.0rc8] - 2026-11-09&lt;/h2&gt;
&lt;p&gt;4.0.0rc8 is the eighth release candidate for Spec Kitty 4.0.0. If you are upgrading from rc7, read &lt;strong&gt;Breaking&lt;/strong&gt; and &lt;strong&gt;Upgrade Notes&lt;/strong&gt; first. In short:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; in each project and commit the result.&lt;/strong&gt; It moves charter activation into &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt; (#6496), renames the command skills to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-&amp;#x3C;command&gt;&lt;/code&gt; (#6475), keeps status files out of existing lane worktrees (#7281), stamps &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; on Missions merged before that marker existed (#7433), and repairs stale templates and overrides (#5280, #6922). Once a project is upgraded, everyone who works on it needs 4.0.0rc8 or later (#6496).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A new Mission starts on one topic branch.&lt;/strong&gt; Its topology is settled by size at the first &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; (#7282).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Landing work is stricter.&lt;/strong&gt; At &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, every &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt; issue-matrix row needs a verdict (#6653); an approved work package needs a committed implementation and an independent review on every topology (#6715); a merge on a lane that adds content of its own must be reviewed first (#7307).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;More &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; errors use the shared &lt;code dir=&quot;auto&quot;&gt;{&quot;ok&quot;: false, &quot;error&quot;: {...}}&lt;/code&gt; envelope&lt;/strong&gt;, including &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; and every owned-checkout refusal (#6557, #6353). Update scripts that parse the old error shapes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; now records an exclusion that lasts&lt;/strong&gt; (#6496), and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer commits into non-Mission worktrees you did not name (#7173).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A second &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer deletes the generated &lt;code dir=&quot;auto&quot;&gt;.claude/commands&lt;/code&gt; files the first one kept&lt;/strong&gt; (#7429, fixed by #7470).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Entries for contributors to this repository are condensed under &lt;strong&gt;Internal&lt;/strong&gt;.&lt;/p&gt;
&lt;h3 id=&quot;breaking&quot;&gt;Breaking&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Spec Kitty’s command skills now load in every Agent Skills harness, Antigravity included&lt;/strong&gt; (#6475, #6470). &lt;strong&gt;Before:&lt;/strong&gt; the skills were named &lt;code dir=&quot;auto&quot;&gt;spec-kitty.&amp;#x3C;command&gt;&lt;/code&gt;; a dot is not a valid Agent Skills name, so VS Code/Copilot, Cursor and OpenCode silently dropped them. &lt;strong&gt;After:&lt;/strong&gt; they are &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty-&amp;#x3C;command&gt;/&lt;/code&gt;. Invoke them as &lt;code dir=&quot;auto&quot;&gt;$spec-kitty-&amp;#x3C;command&gt;&lt;/code&gt; in Codex, &lt;code dir=&quot;auto&quot;&gt;/skill:spec-kitty-&amp;#x3C;command&gt;&lt;/code&gt; in Pi and &lt;code dir=&quot;auto&quot;&gt;/spec-kitty-&amp;#x3C;command&gt;&lt;/code&gt; in Vibe, Letta and Antigravity; the 12 slash-command agents keep &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.&amp;#x3C;command&gt;&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; renames them per clone; an edited dotted copy, or your own folder at a new name, is kept with a warning. &lt;code dir=&quot;auto&quot;&gt;doctor skills --json&lt;/code&gt; adds &lt;code dir=&quot;auto&quot;&gt;legacy&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;collisions&lt;/code&gt;. An older CLI cannot read the new manifest: a teammate on an older CLI who pulls a migrated, committed manifest gets a schema error (dotted name pattern, unknown &lt;code dir=&quot;auto&quot;&gt;antigravity&lt;/code&gt; agent) and nothing is deleted; upgrade that CLI. Copilot in a project also set up for Codex lists each command twice until #6471. &lt;a href=&quot;/migrations/command-skill-hyphen-names/&quot;&gt;Upgrade note&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Google Antigravity gets its Spec Kitty commands as skills, and its dead workflow files are archived&lt;/strong&gt; (#6470). &lt;strong&gt;Before:&lt;/strong&gt; Spec Kitty wrote Antigravity’s commands only to &lt;code dir=&quot;auto&quot;&gt;.agent/workflows/&lt;/code&gt;, which Antigravity stopped reading on 2026-10-19. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent config add antigravity&lt;/code&gt; install the command skills into &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; moves each Spec Kitty-generated &lt;code dir=&quot;auto&quot;&gt;.agent/workflows/spec-kitty.&amp;#x3C;command&gt;.md&lt;/code&gt; into its own &lt;code dir=&quot;auto&quot;&gt;.kittify/backups/antigravity-workflows/.backup-&amp;#x3C;timestamp&gt;/&lt;/code&gt; folder (never deleted; other files stay), and the CLI removes the unedited copies it wrote to &lt;code dir=&quot;auto&quot;&gt;~/.agent/workflows/&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter activation moves out of &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; into the activation ledger, &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;&lt;/strong&gt; (#6496). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;activated_kinds&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt; keys lived in the &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; that &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; points to, or in &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; itself. &lt;strong&gt;After:&lt;/strong&gt; they live in one git-tracked file, &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;, beside the new &lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;kind&gt;&lt;/code&gt; exclusions, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; moves them there. A project that has not been upgraded keeps reading its old keys exactly as before. &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; and commit the result; read activation with &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter list --json&lt;/code&gt; instead of parsing &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; (&lt;a href=&quot;/adr/4.x/2026-10-19-1-activation-ledger-persists-deactivation/&quot;&gt;ADR 2026-10-19-1&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; refuses on a project whose activation keys have not moved yet&lt;/strong&gt; (#6496). &lt;strong&gt;Before:&lt;/strong&gt; it removed the id from the &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; list in &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; an exclusion is recorded only in the activation ledger, so on an unmigrated project &lt;code dir=&quot;auto&quot;&gt;charter deactivate &amp;#x3C;kind&gt; &amp;#x3C;id&gt;&lt;/code&gt;, with or without &lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt;, exits 1, names &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; and writes nothing. Deactivating a mission type still works there. &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate activation-ledger&lt;/code&gt;) once, then deactivate.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --preset &amp;#x3C;name&gt; --force&lt;/code&gt; now also clears exclusions&lt;/strong&gt; (#6496). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; only let the preset overwrite customized activation keys. &lt;strong&gt;After:&lt;/strong&gt; it also clears the exclusion of every deactivated id the preset lists. Without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; such an id stays deactivated, is left out of the written list and is named in the output. &lt;strong&gt;What to do:&lt;/strong&gt; leave out &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; when you want a preset to keep your deactivations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer commits into non-Mission worktrees you did not name&lt;/strong&gt; (#7173). &lt;strong&gt;Before:&lt;/strong&gt; it wrote and committed into every non-Mission worktree under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;, including landing worktrees. &lt;strong&gt;After:&lt;/strong&gt; it skips them unless you name one with &lt;code dir=&quot;auto&quot;&gt;--include-worktree PATH&lt;/code&gt; (repeatable) or pass &lt;code dir=&quot;auto&quot;&gt;--all-worktrees&lt;/code&gt;. The preview lists every worktree and what will happen to it; the output lists what did happen. Mission worktrees are skipped as before, and a symlink that resolves outside &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; is never selected. &lt;code dir=&quot;auto&quot;&gt;--cli&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;--no-worktrees&lt;/code&gt; with an opt-in flag exits 2. In &lt;code dir=&quot;auto&quot;&gt;--plan-json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;commit_policy.worktrees_enabled&lt;/code&gt; now means at least one worktree is selected, so a plain run reports &lt;code dir=&quot;auto&quot;&gt;false&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; if a script relied on the old behavior, add &lt;code dir=&quot;auto&quot;&gt;--all-worktrees&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;At &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, every &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt; issue-matrix row now blocks, cited or not&lt;/strong&gt; (#6653). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;move-task --to done&lt;/code&gt; judged only rows whose issue was a discovered gating reference, and a Mission with no gating reference skipped the matrix entirely, so an &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt; row that was uncited, cited only as context (&lt;code dir=&quot;auto&quot;&gt;see #12&lt;/code&gt;) or a one-digit &lt;code dir=&quot;auto&quot;&gt;#8&lt;/code&gt; landed with exit 0 under a PASS reading “No unresolved (in-mission/unknown) issue-matrix rows”. &lt;strong&gt;After:&lt;/strong&gt; at &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; every row is judged by its verdict; a present matrix is judged whole (unknown verdicts and malformed rows included) even with zero gating references; a Mission with no gating reference and no matrix still passes. A PASS names the rows it judged, or says no issue-matrix was authored. &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; is unchanged. In &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt; mode the row is reported and the Mission still lands. &lt;strong&gt;What to do:&lt;/strong&gt; record a terminal verdict for each listed row with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent issue-verdict --mission &amp;#x3C;handle&gt; --issue &amp;#x3C;#NNN&gt; --verdict &amp;#x3C;fixed|verified-already-fixed|deferred-with-followup|not-applicable&gt; --actor &amp;#x3C;actor&gt;&lt;/code&gt; (&lt;a href=&quot;/adr/4.x/2026-10-26-1-done-judges-every-issue-matrix-row/&quot;&gt;ADR 2026-10-26-1&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter status --json&lt;/code&gt; reports errors in the shared &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; envelope&lt;/strong&gt; (#6557). &lt;strong&gt;Before:&lt;/strong&gt; a failure printed &lt;code dir=&quot;auto&quot;&gt;{&quot;result&quot;: &quot;error&quot;, &quot;success&quot;: false, &quot;error&quot;: &quot;&amp;#x3C;message&gt;&quot;}&lt;/code&gt;, and the text output printed &lt;code dir=&quot;auto&quot;&gt;Error: &amp;#x3C;message&gt;&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;Unexpected error: &amp;#x3C;message&gt;&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it prints &lt;code dir=&quot;auto&quot;&gt;{&quot;ok&quot;: false, &quot;error&quot;: {&quot;code&quot;: &quot;&amp;#x3C;CODE&gt;&quot;, &quot;message&quot;: &quot;&amp;#x3C;message&gt;&quot;}}&lt;/code&gt;, and text refusals print &lt;code dir=&quot;auto&quot;&gt;Error (&amp;#x3C;CODE&gt;): &amp;#x3C;message&gt;&lt;/code&gt;; the success payload is unchanged apart from the new &lt;code dir=&quot;auto&quot;&gt;activation&lt;/code&gt; block. &lt;strong&gt;What to do:&lt;/strong&gt; detect an error by the presence of &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt; (only the error envelope has it, always &lt;code dir=&quot;auto&quot;&gt;false&lt;/code&gt;; a success payload keeps &lt;code dir=&quot;auto&quot;&gt;result: &quot;success&quot;&lt;/code&gt; and has no &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt;), then read &lt;code dir=&quot;auto&quot;&gt;error.code&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;error.message&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; string; the codes are in the &lt;a href=&quot;/api/charter-commands/#error-envelope-and-codes&quot;&gt;Charter CLI Reference&lt;/a&gt;. &lt;strong&gt;Also:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; pointer in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; naming a missing file used to let &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; exit 0; it now refuses with &lt;code dir=&quot;auto&quot;&gt;ACTIVE_CHARTER_CONFIG_INVALID&lt;/code&gt;, exit 1, and says to point the key at an existing file or remove it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every owned-checkout refusal in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; mode now prints the CLI’s C2 error contract&lt;/strong&gt; (#6353, breaking for JSON consumers of owned refusals). &lt;strong&gt;Before:&lt;/strong&gt; an owned refusal had up to seven JSON shapes depending on the command, such as &lt;code dir=&quot;auto&quot;&gt;{success, error_code, error}&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;{error, error_code}&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it prints &lt;code dir=&quot;auto&quot;&gt;{&quot;ok&quot;: false, &quot;error&quot;: {&quot;code&quot;: &quot;&amp;#x3C;CODE&gt;&quot;, &quot;message&quot;: &quot;&amp;#x3C;text&gt;&quot;}}&lt;/code&gt; on stdout and exits 1, plus a &lt;code dir=&quot;auto&quot;&gt;context&lt;/code&gt; object (&lt;code dir=&quot;auto&quot;&gt;agent tasks mark-status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent mission setup-plan&lt;/code&gt;) or a &lt;code dir=&quot;auto&quot;&gt;spec_kitty_version&lt;/code&gt; stamp (&lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt;) where listed. The top-level &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;result&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;code&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;message&lt;/code&gt; keys are gone. Other errors are unchanged. In human mode, &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt;’s owned-batch refusals and &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;’ &lt;code dir=&quot;auto&quot;&gt;OWNED_INDEX_REFUSED&lt;/code&gt; now print &lt;code dir=&quot;auto&quot;&gt;Error: [&amp;#x3C;CODE&gt;] &amp;#x3C;message&gt;&lt;/code&gt; on stderr; other human output is unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; read &lt;code dir=&quot;auto&quot;&gt;error.code&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;error.message&lt;/code&gt;. See ADR &lt;code dir=&quot;auto&quot;&gt;docs/adr/4.x/2026-10-27-2-owned-refusals-use-the-c2-error-contract.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;agent decision&lt;/code&gt; verbs, &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; owned catch-all join the C2 owned refusal; orchestrator-api moves to &lt;code dir=&quot;auto&quot;&gt;1.20.0&lt;/code&gt;&lt;/strong&gt; (#6353). &lt;strong&gt;Before:&lt;/strong&gt; the decision verbs printed their owned refusals, including the decision ledger’s &lt;code dir=&quot;auto&quot;&gt;OWNED_MISSION_PATH_REFUSED&lt;/code&gt;, as &lt;code dir=&quot;auto&quot;&gt;{error, code}&lt;/code&gt; on stderr, and &lt;code dir=&quot;auto&quot;&gt;agent decision repair-runtime-lock&lt;/code&gt; printed a lock-path owned refusal as &lt;code dir=&quot;auto&quot;&gt;{status, code, message}&lt;/code&gt; with code &lt;code dir=&quot;auto&quot;&gt;RUNTIME_LOCK_REPAIR_FAILED&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; they print the C2 owned refusal on stdout with the owned code; their other errors are unchanged. orchestrator-api &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&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; and &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; read &lt;code dir=&quot;auto&quot;&gt;error.code&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;error.message&lt;/code&gt; from the host payload, so the owned code is kept, and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; embeds the new payload in &lt;code dir=&quot;auto&quot;&gt;data&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A caller-supplied &lt;code dir=&quot;auto&quot;&gt;migration:&lt;/code&gt; actor is refused, so only an in-process migration can write a reconstruction seed&lt;/strong&gt; (#6754). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent status emit --actor migration:x&lt;/code&gt;, the four &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; lifecycle verbs and the hidden &lt;code dir=&quot;auto&quot;&gt;implement --actor&lt;/code&gt; stored the value verbatim, and &lt;code dir=&quot;auto&quot;&gt;is_migration_actor&lt;/code&gt; then treated that event as a reconstruction seed — exempt from the review-exit note rule, skipped by timestamp continuity and invisible to consolidation work windows — so a caller could make a live transition look like reconstruction. &lt;strong&gt;After:&lt;/strong&gt; those surfaces refuse an identity starting with &lt;code dir=&quot;auto&quot;&gt;migration:&lt;/code&gt;, exit non-zero and write nothing; the value is never rewritten into a live-looking actor. An explicit &lt;code dir=&quot;auto&quot;&gt;--agent migration:x&lt;/code&gt; is unchanged (read as &lt;code dir=&quot;auto&quot;&gt;tool:model:profile&lt;/code&gt;, so its tool is &lt;code dir=&quot;auto&quot;&gt;migration&lt;/code&gt; and it is not a seed), a recorded &lt;code dir=&quot;auto&quot;&gt;migration:&lt;/code&gt; identity keeps its seed status when re-recorded, and stored logs read exactly as before. &lt;strong&gt;What to do:&lt;/strong&gt; drop &lt;code dir=&quot;auto&quot;&gt;migration:&lt;/code&gt; from any scripted &lt;code dir=&quot;auto&quot;&gt;--actor&lt;/code&gt; and pass the live identity instead.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;events tail&lt;/code&gt; follows every canonical ledger, and its default output is now human-readable&lt;/strong&gt; (#6611). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;events tail --mission &amp;#x3C;slug&gt;&lt;/code&gt; could tail only the mission’s &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, and its &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; flag was accepted but had no observable effect (JSON lines were the only mode). &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--log &amp;#x3C;kind&gt;&lt;/code&gt; selects any of the seven canonical ledgers — &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt; (default), &lt;code dir=&quot;auto&quot;&gt;decisions&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;run&lt;/code&gt; (the mission’s newest run journal), &lt;code dir=&quot;auto&quot;&gt;glossary&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ops&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;canonical&lt;/code&gt;; an unknown kind is a usage error (exit 2) before any file access. Without &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;, each event prints as one plain-text line (timestamp, event type, sorted payload; cursor keys omitted); &lt;code dir=&quot;auto&quot;&gt;--log run&lt;/code&gt; with no matching run journal refuses with a typed &lt;code dir=&quot;auto&quot;&gt;run_log_unavailable&lt;/code&gt; envelope, exit 1. &lt;strong&gt;What to do:&lt;/strong&gt; pass &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; to keep the machine envelope — byte-identical to the previous output on every kind, including &lt;code dir=&quot;auto&quot;&gt;tail_offset&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tail_invariant&lt;/code&gt;, so &lt;code dir=&quot;auto&quot;&gt;--from-offset&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--from-invariant&lt;/code&gt; resume contracts are unchanged (&lt;code dir=&quot;auto&quot;&gt;docs query --json&lt;/code&gt; precedent). Further log kinds are deliberately deferred.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --teamspace-dry-run&lt;/code&gt; is removed&lt;/strong&gt; (#7389). &lt;strong&gt;Before:&lt;/strong&gt; the flag synthesized hosted TeamSpace import envelopes from the repaired history and validated them against the events contract. &lt;strong&gt;After:&lt;/strong&gt; the flag is gone and passing it exits 2 with typer’s “No such option” error; the &lt;code dir=&quot;auto&quot;&gt;teamspace_dry_run&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;TeamspaceDryRunReport&lt;/code&gt; migration helpers and their tests are deleted. TeamSpace is a hosted concept that left open-core in #6164, so the flag fed an import path this repository no longer ships. The audit (&lt;code dir=&quot;auto&quot;&gt;--audit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--fail-on teamspace-blocker&lt;/code&gt;) and repair (&lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt;) arms are unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; drop &lt;code dir=&quot;auto&quot;&gt;--teamspace-dry-run&lt;/code&gt; from any script or CI job; keep running &lt;code dir=&quot;auto&quot;&gt;--audit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;NoActivationRestrictionsError&lt;/code&gt; is removed, with no alias&lt;/strong&gt; (#6496). &lt;strong&gt;Before:&lt;/strong&gt; deactivating an artifact of a kind with no &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; list raised it. &lt;strong&gt;After:&lt;/strong&gt; that deactivation records an exclusion and succeeds; the one remaining refusal, an id an org pack requires, raises &lt;code dir=&quot;auto&quot;&gt;RequiredArtifactDeactivationError&lt;/code&gt;, a subclass of &lt;code dir=&quot;auto&quot;&gt;DeactivationRefused&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;charter.activation.pack_manager&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; catch &lt;code dir=&quot;auto&quot;&gt;DeactivationRefused&lt;/code&gt; instead.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The status produce seam is renamed to transport-neutral names, with no aliases&lt;/strong&gt; (#6607). &lt;strong&gt;Before:&lt;/strong&gt; a transport owner registered into &lt;code dir=&quot;auto&quot;&gt;register_saas_fanout_handler&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;register_lifecycle_saas_fanout_handler&lt;/code&gt; and the CLI called &lt;code dir=&quot;auto&quot;&gt;fire_saas_fanout&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;fire_lifecycle_saas_fanout&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;specify_cli.status.adapters&lt;/code&gt;, along with &lt;code dir=&quot;auto&quot;&gt;queue_saas_emission&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;fanout_lifecycle_event_hosted&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; they are &lt;code dir=&quot;auto&quot;&gt;register_status_fanout_handler&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;register_lifecycle_fanout_handler&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;fire_status_fanout&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;fire_lifecycle_fanout&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;queue_fanout_emission&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;fanout_lifecycle_event&lt;/code&gt;; the old names are gone. Open-core still registers no default handler, so there is no change for a project that registers none. Log lines and the handler worker thread now say “status fan-out” / “lifecycle fan-out”. &lt;strong&gt;What to do:&lt;/strong&gt; a transport owner that calls the old names must switch to the new ones.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_FANOUT_TIMEOUT&lt;/code&gt; is renamed &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_STATUS_FANOUT_TIMEOUT&lt;/code&gt;, and the old name is ignored&lt;/strong&gt; (#6607). &lt;strong&gt;Before:&lt;/strong&gt; the variable bounded each status fan-out handler (default 10 seconds). &lt;strong&gt;After:&lt;/strong&gt; the same bound is read from &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_STATUS_FANOUT_TIMEOUT&lt;/code&gt;; the old variable has no effect and there is no fallback. &lt;strong&gt;What to do:&lt;/strong&gt; rename the variable wherever you set it. See &lt;a href=&quot;/api/environment-variables/#spec_kitty_status_fanout_timeout&quot;&gt;Environment Variables&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;upgrade-notes&quot;&gt;Upgrade Notes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; before you deactivate anything&lt;/strong&gt; (#6496). Its &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_activation_ledger&lt;/code&gt; step moves the activation keys verbatim, including &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt;, from &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;, and re-stamps the synthesis manifest. A run that was interrupted is finished by running it again; a second run changes nothing. &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; and a fresh project write the activation ledger themselves.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate activation-ledger&lt;/code&gt; runs only that move&lt;/strong&gt; (#6496). Use it when you do not want a full upgrade, or after merging a branch that wrote activation keys back into &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;. It records the step in the Migration Ledger only when &lt;code dir=&quot;auto&quot;&gt;.kittify/migration-ledger.jsonl&lt;/code&gt; already exists; otherwise it records nothing, and a later &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; finds nothing left to move.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The move refuses when two copies of a key disagree&lt;/strong&gt; (#6496). When the pointed &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; and a leftover &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; copy hold different values for a key, when only the copy holds it, or when a legacy file holds a hand-written &lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;kind&gt;&lt;/code&gt; key, the upgrade and &lt;code dir=&quot;auto&quot;&gt;migrate activation-ledger&lt;/code&gt; name the key and both files, exit 1 and change nothing. Make the files agree or delete the stale copy, then run the command again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Do not open an upgraded project with an older CLI&lt;/strong&gt; (#6496). An older CLI does not read &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;. It finds no activation keys in &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, treats every kind as unrestricted, and so puts every artifact in force and ignores every deactivation. Once a project is upgraded, everyone who works on it needs 4.0.0rc8 or later.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activation keys written back into &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; are ignored&lt;/strong&gt; (#6496). After the move, keys that an older CLI or a branch from before the move writes there are ignored, because the activation ledger wins. Each command warns once, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; reports them as &lt;code dir=&quot;auto&quot;&gt;LEGACY_KEYS_PRESENT&lt;/code&gt; errors. Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate activation-ledger&lt;/code&gt;: it strips a copy equal to the activation ledger and refuses one that differs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The org required selection now includes requirements inherited through &lt;code dir=&quot;auto&quot;&gt;extends:&lt;/code&gt;&lt;/strong&gt; (#6496). The &lt;code dir=&quot;auto&quot;&gt;required_&amp;#x3C;kind&gt;&lt;/code&gt; ids of each declared org pack’s &lt;code dir=&quot;auto&quot;&gt;extends:&lt;/code&gt; chain are unioned into &lt;code dir=&quot;auto&quot;&gt;selected_&amp;#x3C;kind&gt;&lt;/code&gt;, the same set &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; refuses to exclude.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; repairs stale documentation and research templates&lt;/strong&gt; (#5280). Its new &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_retire_stale_mission_template_forks&lt;/code&gt; step looks at the 15 documentation and research template names in &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;type&gt;/templates/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/missions/&amp;#x3C;type&gt;/templates/&lt;/code&gt;. A copy whose bytes match a version Spec Kitty shipped in its old template fork is stale. In &lt;code dir=&quot;auto&quot;&gt;overrides/&lt;/code&gt; a stale copy is removed, so the template Spec Kitty ships now resolves again. In &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&lt;/code&gt; it is replaced with the shipped template; a stale &lt;code dir=&quot;auto&quot;&gt;plan-template.md&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;spec-template.md&lt;/code&gt;, which the shipped templates renamed, is removed. A copy you edited is kept, and the upgrade names it in a warning: delete it to use the shipped template. Commit the result.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; repairs historical mission overrides the 2.0.6 sweep created&lt;/strong&gt; (#6922, #6548). Its new &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_repair_historical_sweep_overrides&lt;/code&gt; step compares each file under &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/missions/&amp;#x3C;type&gt;/&lt;/code&gt; with the file Spec Kitty ships at the same path. &lt;strong&gt;Before:&lt;/strong&gt; an older build’s 2.0.6 cleanup moved package-shipped mission files (a &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; template, &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt;) into &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/&lt;/code&gt;, where they outranked the shipped copy, and nothing removed them: 2.0.7 reported “not needed” and the #5280 step knows only the 15 documentation and research template names. &lt;strong&gt;After:&lt;/strong&gt; a byte-identical file is removed, so the next template tier (an org pack, or the shipped file) resolves again; a file that differs is kept and named in a warning, because Spec Kitty cannot prove it owns those bytes — delete it to use the shipped version. A file the package does not ship is never touched. Commit the result.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A merge that adds content of its own must be reviewed before &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; lands it&lt;/strong&gt; (#7307). A merge that resolves a conflict by keeping one side, and that is not a lane’s own reviewed merge of a declared dependency lane, is now refused; so is a dependency merge with its own content made after the work package was approved. A merge with three or more parents (an octopus merge) on a lane is refused, because git cannot show what it adds of its own. &lt;strong&gt;What to do:&lt;/strong&gt; after such a merge on a lane, send the work package back for review and approve it again, so its approval stamp covers the merge.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; excludes the status files from existing lane worktrees&lt;/strong&gt; (#7281). &lt;strong&gt;Before:&lt;/strong&gt; lane worktrees created earlier still showed the status files. &lt;strong&gt;After:&lt;/strong&gt; the clone-local migration &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_lane_checkout_status_exclusion&lt;/code&gt; reports one outcome per lane worktree: &lt;code dir=&quot;auto&quot;&gt;excluded&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;flagged_redundant&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;refused_lane_only_events&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;skipped_mid_operation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;skipped_legacy_mission&lt;/code&gt; (a genuinely-legacy Mission, which keeps writing status into its lane checkout, is left as it is) or &lt;code dir=&quot;auto&quot;&gt;already_excluded&lt;/code&gt;; it never drops an event. &lt;strong&gt;What to do:&lt;/strong&gt; for a &lt;code dir=&quot;auto&quot;&gt;refused_lane_only_events&lt;/code&gt; lane, record each transition its copy holds with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task&lt;/code&gt;, discard the lane copy’s change to the two status files, then run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; again; &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor sparse-checkout&lt;/code&gt; lists every such lane as &lt;code dir=&quot;auto&quot;&gt;LANE_STATUS_NOT_EXCLUDED&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A default &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; now mints only a topic branch&lt;/strong&gt; (#7282). &lt;strong&gt;Before:&lt;/strong&gt; a create on the primary branch made a coordination branch and worktree at once. &lt;strong&gt;After:&lt;/strong&gt; it records &lt;code dir=&quot;auto&quot;&gt;topology: single_branch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;topology_source: default&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;topology_settled: false&lt;/code&gt;, and the topology settles at the first &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;; Missions created earlier, and every Mission created with &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt;, keep their recorded topology. &lt;strong&gt;What to do:&lt;/strong&gt; update scripts that expect a coordination worktree right after create.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;In-flight &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Missions may refuse with &lt;code dir=&quot;auto&quot;&gt;APPROVAL_STAMP_MISSING&lt;/code&gt;&lt;/strong&gt; (#7283). &lt;strong&gt;Before:&lt;/strong&gt; their approvals were never checked at consolidation. &lt;strong&gt;After:&lt;/strong&gt; an approval recorded without a stamp refuses. &lt;strong&gt;What to do:&lt;/strong&gt; attest each such work package with &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --attest-approved-reviewed &amp;#x3C;WP&gt; --attest-reason &quot;&amp;#x3C;why&gt;&quot;&lt;/code&gt;, or move it back and approve it again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; stamps &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; on Missions merged before the marker existed&lt;/strong&gt; (#7433). &lt;strong&gt;Before:&lt;/strong&gt; such a Mission had no &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt;, so &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; read it as not merged, and a coordination one refused with &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_DELETED&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the migration &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_backfill_merged_at&lt;/code&gt; stamps it only when the committed status log shows every work package &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt;, at least one &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, and no reopen, dated by the latest transition to &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; (UTC). &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; is no proof of a merge (#5471). Every other Mission is left alone and named in a warning with its reason, including one mid-consolidation (finish it with &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt;). &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; and commit the changed &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; files; for a named Mission that did merge, set &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; (ISO-8601 UTC) by hand.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Core now pins the service builds it runs and fetches and verifies them on demand&lt;/strong&gt; (#6590). &lt;strong&gt;Before:&lt;/strong&gt; nothing recorded which released build of the write, read or charter service a spec-kitty version runs, and there was no supported way to get one. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;pins/&amp;#x3C;service&gt;.source.yaml&lt;/code&gt; records the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;service-v*&lt;/code&gt; release and every asset’s SHA-256, ships in the wheel (no binary does), and is bumped only with &lt;code dir=&quot;auto&quot;&gt;spec-kitty service vendor&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;spec-kitty service fetch|status|stop&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;make sync-services&lt;/code&gt; fetch and verify the pinned assets into &lt;code dir=&quot;auto&quot;&gt;~/.cache/spec-kitty/services&lt;/code&gt;, offline from the cache or &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SERVICE_ASSET_DIR&lt;/code&gt; too. No pin exists until &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; cuts its first &lt;code dir=&quot;auto&quot;&gt;service-v*&lt;/code&gt; release. See &lt;a href=&quot;/development/how-to/service-pins/&quot;&gt;Service pins&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The CLI to write-service protocol is now a checked contract, &lt;code dir=&quot;auto&quot;&gt;contracts/mission-write&lt;/code&gt;&lt;/strong&gt; (#6675). &lt;strong&gt;Before:&lt;/strong&gt; nothing defined how the CLI reaches the resident write service of ADR 2026-10-22-1, how it trusts the running service, or which codes it refuses with. &lt;strong&gt;After:&lt;/strong&gt; the contract defines six operations, a bearer token on each, protocol-version negotiation and a &lt;code dir=&quot;auto&quot;&gt;WriteRefusal&lt;/code&gt; whose codes are the CLI’s own 20 verbatim plus 9 protocol-only ones; a test checks each reused code against the CLI file that raises it. Typed client shapes and a fail-closed endpoint-file reader are in &lt;code dir=&quot;auto&quot;&gt;specify_cli.status.write_service_protocol&lt;/code&gt;. Nothing binds them yet, so the CLI writes events as before (&lt;a href=&quot;/adr/4.x/2026-10-27-1-the-write-service-protocol-is-loopback-http-with-a-bearer-token/&quot;&gt;ADR 2026-10-27-1&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor event-logs&lt;/code&gt; previews and prunes local run journals, event logs and caches past retention&lt;/strong&gt; (#6610, #5212). &lt;strong&gt;Before:&lt;/strong&gt; run journals, glossary logs and caches under &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; grew without bound. &lt;strong&gt;After:&lt;/strong&gt; it lists every item with its reason and changes nothing; &lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt; deletes the candidates and their run-index entries; &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; reports the same. An item goes only when it is outside the newest &lt;code dir=&quot;auto&quot;&gt;keep_runs&lt;/code&gt; AND older than &lt;code dir=&quot;auto&quot;&gt;max_age_days&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;ledger.retention&lt;/code&gt;) and its work is over (a run: Mission merged or run finished; a glossary log: Mission completed); committed records, the Op index, lock files and locked items never go. Every state surface now declares the cleanup policy that decides what is pruned. &lt;strong&gt;What to do:&lt;/strong&gt; run it, tune &lt;code dir=&quot;auto&quot;&gt;ledger.retention&lt;/code&gt;, then add &lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt;; see &lt;a href=&quot;/guides/how-to/monitoring/clean-up-local-event-logs/&quot;&gt;Clean Up Local Event Logs&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter deactivate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --json&lt;/code&gt; print a change report&lt;/strong&gt; (#6525). The report (&lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;1.0.0&lt;/code&gt;) lists what changed, the warnings, the &lt;code dir=&quot;auto&quot;&gt;notices&lt;/code&gt; the catalog refresh and skill projection printed, the referenced artifacts a run without &lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt; left alone (&lt;code dir=&quot;auto&quot;&gt;referenced_not_cascaded&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;referenced_kind_filtered&lt;/code&gt;), and a &lt;code dir=&quot;auto&quot;&gt;cascade&lt;/code&gt; report with one list per outcome. A refusal prints &lt;code dir=&quot;auto&quot;&gt;{&quot;ok&quot;: false, &quot;error&quot;: {&quot;code&quot;, &quot;message&quot;}}&lt;/code&gt; with a local code such as &lt;code dir=&quot;auto&quot;&gt;ACTIVATION_KIND_UNKNOWN&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;DEACTIVATION_REFUSED_REQUIRED&lt;/code&gt;, at the same exit code as the text form, which now prints &lt;code dir=&quot;auto&quot;&gt;Error (&amp;#x3C;CODE&gt;): &amp;#x3C;message&gt;&lt;/code&gt;. This is the local slice: the shape and codes are not the spec-kitty-charter activation contract, whose mapping stays with #6518.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter status --json&lt;/code&gt; carries an &lt;code dir=&quot;auto&quot;&gt;activation&lt;/code&gt; block&lt;/strong&gt; (#6526). It reports where activation was read (&lt;code dir=&quot;auto&quot;&gt;source&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;exists&lt;/code&gt;), the allow lists (&lt;code dir=&quot;auto&quot;&gt;selected&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt; when a kind has none), the exclusions (&lt;code dir=&quot;auto&quot;&gt;deactivated&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;mission_types&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;activated_kinds&lt;/code&gt; and the org-required ids of every org-requirable kind with &lt;code dir=&quot;auto&quot;&gt;in_force&lt;/code&gt;, plus &lt;code dir=&quot;auto&quot;&gt;required_error&lt;/code&gt; when an org charter is malformed. An activation read failure, including an unreadable file (&lt;code dir=&quot;auto&quot;&gt;ACTIVATION_STATE_UNREADABLE&lt;/code&gt;), degrades only this block to &lt;code dir=&quot;auto&quot;&gt;{&quot;schema_version&quot;, &quot;error&quot;}&lt;/code&gt;. This is the local slice (&lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;1.0.0&lt;/code&gt;); the contract mapping stays with #6518. See the &lt;a href=&quot;/api/charter-commands/#the-activation-block&quot;&gt;Charter CLI Reference&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor mission-state --audit&lt;/code&gt; reports &lt;code dir=&quot;auto&quot;&gt;FABRICATED_IDENTITY_SUSPECTED&lt;/code&gt; for a Mission identity an earlier upgrade invented&lt;/strong&gt; (#6668). &lt;strong&gt;Before:&lt;/strong&gt; an upgrade before #6627 could commit a baseline &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; with a newly minted &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; into a leftover folder, and nothing pointed it out. &lt;strong&gt;After:&lt;/strong&gt; the audit raises one warning for a folder when all three hold: its &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is tracked and the folder holds only &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;decisions/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;*.lock&lt;/code&gt; files; the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; has the shape the baseline writer produces for the slug; and the slug’s trailing 8 characters differ from the start of &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;. The audit only reports and never deletes, but the finding is a warning, so &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --audit --fail-on warning&lt;/code&gt; now exits 1 on it. &lt;strong&gt;What to do:&lt;/strong&gt; remove that folder’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; in a commit, as the finding says.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt; exports &lt;code dir=&quot;auto&quot;&gt;LANGUAGE_TOKENS&lt;/code&gt;, the catalog’s language tokens as plain strings&lt;/strong&gt; (#6541). &lt;strong&gt;Before:&lt;/strong&gt; the language vocabulary was reachable only through internal modules, so the charter service and the conformance corpus had nothing stable to read. &lt;strong&gt;After:&lt;/strong&gt; a read-only tuple such as &lt;code dir=&quot;auto&quot;&gt;(&quot;python&quot;, …, &quot;kotlin&quot;, &quot;java&quot;, …)&lt;/code&gt; is part of the seam, fronted by the &lt;code dir=&quot;auto&quot;&gt;charter.languages&lt;/code&gt; facade; the catalog records (&lt;code dir=&quot;auto&quot;&gt;LANGUAGES&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;LanguageSpec&lt;/code&gt;) and the &lt;code dir=&quot;auto&quot;&gt;jvm&lt;/code&gt; family helpers stay internal. ADR 2026-10-03-1 records the widening.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The Mission Status service now serves a Mission’s planning artifacts, and every removed dashboard route has a recorded home&lt;/strong&gt; (#957, #5533). &lt;strong&gt;Before:&lt;/strong&gt; after the dashboard removal (#5530) nothing served a Mission’s spec, plan, research, contracts or checklists, and the local service answered the artifact operations with 404. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;GET /api/v1/missions/{missionId}/artifacts&lt;/code&gt; lists a Mission’s files and &lt;code dir=&quot;auto&quot;&gt;.../artifacts/content?path=&lt;/code&gt; returns one file’s redacted text; oversized, binary and credential-holding files are refused and links are never followed, as the unchanged &lt;code dir=&quot;auto&quot;&gt;mission-status&lt;/code&gt; contract states. The route inventory, including the routes dropped with the dashboard, is in &lt;code dir=&quot;auto&quot;&gt;kitty-specs/mission-status-artifact-reads-01M57KY3/route-inventory.md&lt;/code&gt;; divergences are in &lt;code dir=&quot;auto&quot;&gt;services/mission-status-api/README.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Built-in and internal packs are now sourced from &lt;code dir=&quot;auto&quot;&gt;spec-kitty-open-packs&lt;/code&gt; at a pinned commit&lt;/strong&gt; (#6451, #6421, #6364). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt; were committed in this repository and could diverge from their source. &lt;strong&gt;After:&lt;/strong&gt; core commits only the pin lockfiles &lt;code dir=&quot;auto&quot;&gt;packs/built-in.source.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;packs/internal.source.yaml&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;make sync-packs&lt;/code&gt; and the wheel build hook fetch, digest-verify and place the pinned trees, and &lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt; is still never shipped in the wheel or sdist. &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack vendor&lt;/code&gt; is now a pin-bump helper (&lt;code dir=&quot;auto&quot;&gt;--ref &amp;#x3C;sha&gt;&lt;/code&gt;) and no longer copies a tree; a pack whose &lt;code dir=&quot;auto&quot;&gt;requires_core&lt;/code&gt; excludes this core is refused at bump time. &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;make sync-packs&lt;/code&gt; after pulling, and once in every worktree; a source checkout without the built-in tree fails with &lt;code dir=&quot;auto&quot;&gt;BuiltInPackMissing&lt;/code&gt;. Installed packages are unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The vendored built-in pack is now pinned and drift-gated&lt;/strong&gt; (#3504). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; could silently diverge from its &lt;code dir=&quot;auto&quot;&gt;spec-kitty-open-packs&lt;/code&gt; source, and nothing caught it. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;packs/built-in.source.yaml&lt;/code&gt; pins the tree to an open-packs commit SHA and content digest; &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack vendor [--check]&lt;/code&gt; re-vendors or verifies it. A per-PR CI gate and a release-time re-verify fail on drift. &lt;strong&gt;What to do:&lt;/strong&gt; when the gate reds, bump the pin with &lt;code dir=&quot;auto&quot;&gt;vendor&lt;/code&gt; instead of hand-editing &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; (ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-16-2&lt;/code&gt;, Option B).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate ledger&lt;/code&gt; reports which project setup steps have run&lt;/strong&gt; (#6387, #2933, #5230). Spec Kitty now keeps an explicit migration ledger that records exactly which setup steps a project has applied and in what order, so re-running &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; is safe and repeatable — it replays nothing already recorded. Repository-wide steps travel with the repository; per-clone git setup is recorded per clone, so a teammate’s fresh clone still gets it applied. Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate ledger&lt;/code&gt; to see, for every setup step, whether it is already in place, not yet applied, recorded elsewhere but absent here, or changed since it ran; &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; emits the same report. A fresh &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; seeds the ledger so the first &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; on a new project does no redundant work. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; the first &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; adopts your existing history. An older CLI run on an upgraded project no longer sees which steps were applied.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --only&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter interview --narrow-activation&lt;/code&gt; keep an activation list narrow&lt;/strong&gt; (#6408). &lt;strong&gt;Before:&lt;/strong&gt; the first selection or activation of a kind wrote every artifact already in force into the &lt;code dir=&quot;auto&quot;&gt;activated_*&lt;/code&gt; list (38 directives for one selected directive), and no command could start a list from just the selection. &lt;strong&gt;After:&lt;/strong&gt; both options set the kind’s list to the selection plus the org pack’s required ids and print the ids that stop being in force (&lt;code dir=&quot;auto&quot;&gt;narrowed&lt;/code&gt; in interview JSON). Without them nothing changes; the “Initialized from” and “Preserved” warnings now say the list is frozen, and the &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.charter&lt;/code&gt; contract names the narrow paths.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; records an exclusion that lasts&lt;/strong&gt; (#6496). The id goes into a &lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;kind&gt;&lt;/code&gt; list in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;, also when the kind has no allow list. It stays deactivated through the cascade, upgrades, the interview, presets and synthesis, until &lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt;&lt;/code&gt;, a cascade with &lt;code dir=&quot;auto&quot;&gt;--include-deactivated&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;charter activate --preset &amp;#x3C;name&gt; --force&lt;/code&gt; clears it. Deactivating an id an org pack requires exits 1, names the pack and its &lt;code dir=&quot;auto&quot;&gt;required_&amp;#x3C;kind&gt;&lt;/code&gt; policy, and records nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The activation cascade stops at a deactivated artifact, and &lt;code dir=&quot;auto&quot;&gt;--include-deactivated&lt;/code&gt; walks through it&lt;/strong&gt; (#6496). &lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --cascade &amp;#x3C;scope&gt;&lt;/code&gt; prints &lt;code dir=&quot;auto&quot;&gt;Skipped, deactivated: kind/id&lt;/code&gt; for a deactivated node, &lt;code dir=&quot;auto&quot;&gt;Unreached (behind a deactivated artifact): kind/id&lt;/code&gt; for what lies only behind it, and a hint. &lt;code dir=&quot;auto&quot;&gt;--include-deactivated&lt;/code&gt; activates them and clears their exclusions. Without &lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt;, each referenced deactivated artifact gets a warning.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate mission-type &amp;#x3C;id&gt; --cascade &amp;#x3C;scope&gt;&lt;/code&gt; walks the mission type&lt;/strong&gt; (#6496). The mission type is a cascade source: the artifacts it references are activated with the same scope and deactivation rules as any other cascade.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; accepts an artifact’s declared id&lt;/strong&gt; (#6423). &lt;code dir=&quot;auto&quot;&gt;charter activate directive DIRECTIVE_024&lt;/code&gt; works like &lt;code dir=&quot;auto&quot;&gt;charter activate directive 024-locality-of-change&lt;/code&gt;, and an allow list keeps one spelling per artifact.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate activation-ledger [--dry-run] [--json]&lt;/code&gt; moves the activation keys without a full upgrade&lt;/strong&gt; (#6496). &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; prints &lt;code dir=&quot;auto&quot;&gt;result&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;noop&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;dry_run&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;moved&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;refused&lt;/code&gt;), the &lt;code dir=&quot;auto&quot;&gt;moves&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;refusal&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ledger_record&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;written&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;not_recorded&lt;/code&gt;); a refusal exits 1.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; checks the activation ledger&lt;/strong&gt; (#6496). &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; carries &lt;code dir=&quot;auto&quot;&gt;org_drg.activation_ledger&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;errors&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;ACTIVATION_STORE_ERROR&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;LEGACY_DENY_KEY&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;LEGACY_KEYS_PRESENT&lt;/code&gt;, each turning the report unhealthy) and &lt;code dir=&quot;auto&quot;&gt;warnings&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;ACTIVATION_UNMIGRATED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;REQUIRED_OMITTED_BY_ALLOW_LIST&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DENY_UNKNOWN_ID&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DENY_REQUIRED_ID&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DENY_SELECTED_ID&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;UNKNOWN_DENY_KEY&lt;/code&gt;), each &lt;code dir=&quot;auto&quot;&gt;{code, file, key, ids, message}&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt; and preset JSON show exclusions&lt;/strong&gt; (#6496). Every &lt;code dir=&quot;auto&quot;&gt;charter list --json&lt;/code&gt; row gains &lt;code dir=&quot;auto&quot;&gt;deactivated&lt;/code&gt; (the kind’s exclusions; &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt;), and the payload gains &lt;code dir=&quot;auto&quot;&gt;required_not_in_force&lt;/code&gt; when an explicit allow list leaves out an org-required id. &lt;code dir=&quot;auto&quot;&gt;charter activate --preset &amp;#x3C;name&gt; --json&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;kept_deactivated&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;cleared_exclusions&lt;/code&gt; when they are not empty.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The activation ledger is part of the charter bundle&lt;/strong&gt; (#6496). &lt;code dir=&quot;auto&quot;&gt;charter bundle validate --json&lt;/code&gt; lists it under &lt;code dir=&quot;auto&quot;&gt;optional_tracked_files&lt;/code&gt;, and it joins the bundle content hash when present, so an edit made outside the CLI reads as stale. A project without it keeps its hash.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty invocations list&lt;/code&gt; takes &lt;code dir=&quot;auto&quot;&gt;--owned-checkout &amp;#x3C;P&gt;&lt;/code&gt; and lists the Op records kept in &lt;code dir=&quot;auto&quot;&gt;P&lt;/code&gt;&lt;/strong&gt; (#6682). &lt;strong&gt;Before:&lt;/strong&gt; it listed only the records of the checkout it ran in, so from the repository root checkout it did not show the Ops that &lt;code dir=&quot;auto&quot;&gt;dispatch --owned-checkout &amp;#x3C;P&gt;&lt;/code&gt; keeps in &lt;code dir=&quot;auto&quot;&gt;P&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; with the flag it lists &lt;code dir=&quot;auto&quot;&gt;P&lt;/code&gt;’s records; the repository root checkout and a checkout of another repository are refused. Without the flag nothing changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The glossary now disambiguates &lt;code dir=&quot;auto&quot;&gt;residue&lt;/code&gt; — a &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; child that is not a Mission — into its three live code senses&lt;/strong&gt; (#6759). &lt;strong&gt;Before:&lt;/strong&gt; the word had three different rules in code (write-seam &lt;code dir=&quot;auto&quot;&gt;is_kitty_specs_residue&lt;/code&gt;, where a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; on disk keeps a folder repairable; audit-engine &lt;code dir=&quot;auto&quot;&gt;RESIDUE_DIRECTORY&lt;/code&gt;, i.e. &lt;code dir=&quot;auto&quot;&gt;not is_mission_dir&lt;/code&gt;; read-side / &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;not is_selectable_mission_dir&lt;/code&gt;, #5875) and no &lt;code dir=&quot;auto&quot;&gt;docs/context/&lt;/code&gt; entry, so a docstring saying “residue” could mean any of them. &lt;strong&gt;After:&lt;/strong&gt; one entry, &lt;a href=&quot;/context/orchestration/#residue&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/context/orchestration.md#residue&lt;/code&gt;&lt;/a&gt;, names all three senses with “do NOT use when” guards, is linked from the three owning docstrings (plus the &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; module docstring, sense 3’s consuming surface), and joins the Terminology Canon footgun list in &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt; beside &lt;code dir=&quot;auto&quot;&gt;primary&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;routing&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; name the sense (“write-seam residue” etc.) or link the entry instead of writing bare “residue” in governed prose or &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; docstrings. The Contextive orchestration glossary is regenerated to match.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The glossary defines the activation ledger and the current active charter&lt;/strong&gt; (#6562). &lt;strong&gt;Before:&lt;/strong&gt; after #6496 moved activation into &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/activation.yaml&lt;/code&gt;, the published glossary still said &lt;code dir=&quot;auto&quot;&gt;active charter&lt;/code&gt; lived in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, and had no &lt;code dir=&quot;auto&quot;&gt;activation ledger&lt;/code&gt; term. &lt;strong&gt;After:&lt;/strong&gt; both entries name the ledger, the &lt;code dir=&quot;auto&quot;&gt;deactivated_&amp;#x3C;kind&gt;&lt;/code&gt; exclusions and the legacy location an unmigrated project still uses; the new term keeps the Migration Ledger distinct. &lt;strong&gt;What to do:&lt;/strong&gt; nothing — read &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter list --json&lt;/code&gt; for the effective set. See the &lt;a href=&quot;/context/charter/#activation-ledger&quot;&gt;Activation ledger&lt;/a&gt; entry.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-provenance&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter-encoding&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;rebaseline-dossier-hashes&lt;/code&gt; now take a real &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;&lt;/strong&gt; (#6905, #6347). &lt;strong&gt;Before:&lt;/strong&gt; since #5294 those three refused &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; outright, so an operator who legitimately wanted to re-run one migration against a single Mission had to run it corpus-wide. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--mission &amp;#x3C;handle&gt;&lt;/code&gt; (a &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;, a &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; or a slug, resolved through the canonical mission selector as &lt;code dir=&quot;auto&quot;&gt;migrate backfill-merge-commit&lt;/code&gt; does) narrows the walk to that Mission’s acceptance matrix, charter content or recorded dossier snapshot. &lt;code dir=&quot;auto&quot;&gt;charter-encoding --mission&lt;/code&gt; &lt;strong&gt;skips the global charter store&lt;/strong&gt;, leaves it byte-for-byte unchanged and reports the exclusion in both the summary and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;global_store_excluded&lt;/code&gt;); the other two payloads gain &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt;. An unknown handle fails closed rather than widening the scope, omitting &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; keeps today’s corpus-wide default, and &lt;code dir=&quot;auto&quot;&gt;rewrite-opposed-by&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;repin-hooks&lt;/code&gt; still reject the flag because they have no Mission concept.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An optional companion wheel, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-services&lt;/code&gt;, installs the service binaries with the CLI for offline use&lt;/strong&gt; (#6904). &lt;strong&gt;Before:&lt;/strong&gt; the CLI fetched each pinned service binary from its &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; release on first use, so a first write needed network access or a prepared &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SERVICE_ASSET_DIR&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;pip install &quot;spec-kitty-cli[services]&quot;&lt;/code&gt; also installs &lt;code dir=&quot;auto&quot;&gt;spec-kitty-services&lt;/code&gt; of the same version, whose platform wheel carries the pinned write and charter service builds for linux x86_64 and aarch64 (glibc 2.39 or newer), Apple Silicon macOS and Windows x64. The CLI prefers it over its cache and still checks every byte against its own pin; any other host gets a binary-free wheel and keeps the first-run fetch. The &lt;code dir=&quot;auto&quot;&gt;spec-kitty-cli&lt;/code&gt; wheel itself still ships pins only, and the events read service never ships. &lt;strong&gt;What to do:&lt;/strong&gt; nothing, unless you want offline installs; then install the extra (&lt;a href=&quot;/adr/4.x/2026-10-29-1-the-events-domain-and-its-java-services-live-in-spec-kitty-events/&quot;&gt;ADR 2026-10-29-1, Amendment 2026-10-31&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch --brief&lt;/code&gt; returns the governance payload by reference instead of re-embedding it&lt;/strong&gt; (#6990). &lt;strong&gt;Before:&lt;/strong&gt; each dispatch printed the whole governance context — 24,983 bytes here, 23,668 of it the &lt;code dir=&quot;auto&quot;&gt;governance_context_text&lt;/code&gt; render (23,739 UTF-8 bytes) — so a harness dispatching dozens of times a day paid that as prompt context every call, although after the first read it adds almost nothing. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--brief&lt;/code&gt; keeps every routing field and replaces the text with &lt;code dir=&quot;auto&quot;&gt;governance_context_reference&lt;/code&gt; — digest, size and line counts, and the fetch command; that envelope is 1,036 bytes. The printed &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --action &amp;#x3C;action&gt; --profile &amp;#x3C;profile&gt; --json --no-mark-loaded&lt;/code&gt; reproduces the text byte-for-byte, so &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; now takes &lt;code dir=&quot;auto&quot;&gt;--profile&lt;/code&gt;, which it lacked for the profile-cited directives that were most of the payload. &lt;strong&gt;What to do:&lt;/strong&gt; nothing — without &lt;code dir=&quot;auto&quot;&gt;--brief&lt;/code&gt; output, Op record and glossary scan are unchanged; opt in only after this session read the full text.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter org add&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;remove&lt;/code&gt; register an org Charter Pack with a project&lt;/strong&gt; (#7053, #6267). &lt;strong&gt;Before:&lt;/strong&gt; the only path was hand-writing a &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs[]&lt;/code&gt; entry in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, a CLI-managed file whose indentation mistakes silently disable the whole org layer. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter org add &amp;#x3C;name&gt; --local-path &amp;#x3C;dir&gt;&lt;/code&gt; validates the pack exactly as &lt;code dir=&quot;auto&quot;&gt;charter org validate&lt;/code&gt; does and writes one canonical entry, preserving comments and unrelated keys; &lt;code dir=&quot;auto&quot;&gt;--url&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--ref&lt;/code&gt; registers a published pack for &lt;code dir=&quot;auto&quot;&gt;charter fetch&lt;/code&gt; to materialize, &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; replaces an existing registration in place. &lt;code dir=&quot;auto&quot;&gt;charter org remove &amp;#x3C;name&gt;&lt;/code&gt; deletes exactly that entry and leaves the pack directory on disk. Both are offline, refuse without writing, and accept &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces --prune&lt;/code&gt; removes worktrees whose work has landed&lt;/strong&gt; (#7173). &lt;strong&gt;Before:&lt;/strong&gt; landing worktrees and branches stayed after the merge. &lt;strong&gt;After:&lt;/strong&gt; it gives every registered worktree a verdict: landed, not landed, unproven, or Mission-owned. &lt;code dir=&quot;auto&quot;&gt;--prune&lt;/code&gt; removes only worktrees whose commits are on local &lt;code dir=&quot;auto&quot;&gt;origin/&amp;#x3C;primary&gt;&lt;/code&gt; (squash and rebase merges need git 2.38+), then their branches. Linux only: on macOS and Windows it removes nothing. It never fetches or uses &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;; it prints a recreate command. It keeps dirty, locked, busy, mid-rebase and Mission worktrees. &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; is unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; after a merge, run &lt;code dir=&quot;auto&quot;&gt;git fetch origin&lt;/code&gt;, then &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces --prune&lt;/code&gt;. Ignored files such as &lt;code dir=&quot;auto&quot;&gt;.venv/&lt;/code&gt; are listed, then deleted; see the &lt;a href=&quot;/development/how-to/pr-landing/#12-after-the-merge-remove-the-landing-worktree&quot;&gt;landing runbook&lt;/a&gt; for other gaps.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An acceptance criterion can now be recorded &lt;code dir=&quot;auto&quot;&gt;deferred&lt;/code&gt;, with a reason and a follow-up reference&lt;/strong&gt; (#7308). &lt;strong&gt;Before:&lt;/strong&gt; a criterion could only be &lt;code dir=&quot;auto&quot;&gt;pass&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt;, so a criterion the Mission had agreed to postpone held &lt;code dir=&quot;auto&quot;&gt;overall_verdict&lt;/code&gt; at &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; refused for good. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent acceptance-verdict --criterion &amp;#x3C;id&gt; --result deferred --reason &quot;&amp;#x3C;why&gt;&quot; --follow-up &amp;#x3C;issue number, URL or ruling id&gt;&lt;/code&gt; records the deferral on the existing locked write path (the row carries &lt;code dir=&quot;auto&quot;&gt;deferral_reason&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;deferral_follow_up&lt;/code&gt;). A deferral without both is refused (exit 2 from the command; an evidence error that keeps the verdict &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt; if hand-written). A matrix of &lt;code dir=&quot;auto&quot;&gt;pass&lt;/code&gt; and justified &lt;code dir=&quot;auto&quot;&gt;deferred&lt;/code&gt; criteria reads &lt;code dir=&quot;auto&quot;&gt;overall_verdict: pass&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; lists every deferred criterion: a &lt;code dir=&quot;auto&quot;&gt;criteria_deferred&lt;/code&gt; entry under &lt;code dir=&quot;auto&quot;&gt;skipped_checks&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;, and a “Deferred criteria” section in the console. &lt;code dir=&quot;auto&quot;&gt;acceptance-verdict&lt;/code&gt; also takes &lt;code dir=&quot;auto&quot;&gt;--description&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--notes&lt;/code&gt; in criterion mode, so scaffolded “Verify FR-xxx” / “TODO” text no longer needs a hand edit. No &lt;code dir=&quot;auto&quot;&gt;overall_verdict&lt;/code&gt; value was added, so the &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; contract is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The glossary now defines “Contract Scenario” and calls a Charter Pack’s declared level a &lt;em&gt;level&lt;/em&gt;, not a &lt;em&gt;tier&lt;/em&gt;&lt;/strong&gt; (#6439). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;docs/context/charter.md&lt;/code&gt; had no entry for the Gherkin behavior half of the charter contract, and both the Pack Level and Charter Pack entries called a pack’s level a “tier” and “the tier token”. &lt;strong&gt;After:&lt;/strong&gt; the Contract Scenario entry says what a scenario names, calls and asserts, when a scenario runs in &lt;code dir=&quot;auto&quot;&gt;verifyAll&lt;/code&gt;, what &lt;code dir=&quot;auto&quot;&gt;@provisional&lt;/code&gt; marks, and carries a &lt;code dir=&quot;auto&quot;&gt;Do NOT use when&lt;/code&gt; guard away from “BDD scenarios”; both pack entries say “level” and “level token”. &lt;code dir=&quot;auto&quot;&gt;kernel.pack_tiers&lt;/code&gt; keeps its name, and a docs test pins the wording. A repository that imports this glossary verbatim picks both up on its next re-import.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The events domain’s Java services move to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;services/&lt;/code&gt; and the moving contracts are frozen in core&lt;/strong&gt; (#6117). &lt;strong&gt;Before:&lt;/strong&gt; these services were built in core under &lt;code dir=&quot;auto&quot;&gt;services/&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the Mission Status Read API service, the Mission Write API / event-log write core and the &lt;code dir=&quot;auto&quot;&gt;mission-status&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;mission-write&lt;/code&gt; contracts move, with their history, to &lt;code dir=&quot;auto&quot;&gt;spec-kitty/spec-kitty-events&lt;/code&gt;, which releases them on a separate &lt;code dir=&quot;auto&quot;&gt;service-v*&lt;/code&gt; line. Core will consume a pinned release, verified by sha256 and fetched on first use; the CLI wheel still ships no binary, and CLI reads are unchanged. Until the cut-over removes it, a gate (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_events_import_frozen.py&lt;/code&gt;) refuses any change under &lt;code dir=&quot;auto&quot;&gt;services/&lt;/code&gt; or the moving &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; and docs paths. &lt;strong&gt;What to do:&lt;/strong&gt; file Java work on these services in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; (&lt;a href=&quot;/adr/4.x/2026-10-29-1-the-events-domain-and-its-java-services-live-in-spec-kitty-events/&quot;&gt;ADR 2026-10-29-1&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every system-written status event now names its writer in the same structured actor as an agent write&lt;/strong&gt; (#6722). &lt;strong&gt;Before:&lt;/strong&gt; bootstrap seeds (&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;), lane recovery, consolidation bookkeeping (&lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt;), the review-artifact override and both consolidation attestations stored a bare string, so a status log carried two &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt; shapes. &lt;strong&gt;After:&lt;/strong&gt; they store &lt;code dir=&quot;auto&quot;&gt;{&quot;tool&quot;: &quot;&amp;#x3C;identity&gt;&quot;, &quot;role&quot;: &quot;system&quot;, &quot;profile&quot;: null, &quot;model&quot;: null}&lt;/code&gt;, and the migration backfills (&lt;code dir=&quot;auto&quot;&gt;migrate backfill-wp-status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;backfill-runtime-state&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;verdict-provenance&lt;/code&gt;) store the same shape with &lt;code dir=&quot;auto&quot;&gt;tool: &quot;migration:&amp;#x3C;id&gt;&quot;&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; gains one value, &lt;code dir=&quot;auto&quot;&gt;system&lt;/code&gt;; nothing is invented, and &lt;code dir=&quot;auto&quot;&gt;profile&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt; stay null because a system write has no dispatch binding. &lt;strong&gt;What to do:&lt;/strong&gt; nothing. Existing logs are untouched and still reduce; a string and a structured seed are classified the same way, &lt;code dir=&quot;auto&quot;&gt;migrate backfill-runtime-state --verify&lt;/code&gt; accepts seeds written before the change (a row is only ever compared by its identity, never by its shape), and the snapshot &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt; slot still shows the bare tool.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; (positional form) print refusals as &lt;code dir=&quot;auto&quot;&gt;Error (&amp;#x3C;CODE&gt;): &amp;#x3C;message&gt;&lt;/code&gt;&lt;/strong&gt; (#6525). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;Error: &amp;#x3C;message&gt;&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the line names the local code, the same one &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; reports. &lt;strong&gt;What to do:&lt;/strong&gt; a script that matches &lt;code dir=&quot;auto&quot;&gt;Error: &lt;/code&gt; on these commands’ output should match &lt;code dir=&quot;auto&quot;&gt;Error (&lt;/code&gt; instead, or use &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every RACI role the runtime records now names an actor, and Spec Kitty needs &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; 11.3.0&lt;/strong&gt; (#6445, #6602). &lt;strong&gt;Before:&lt;/strong&gt; when &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; could not resolve a role’s actor from its inputs, it recorded the role with an empty actor id, and its significance and RACI records used private copies of the shared event models. &lt;strong&gt;After:&lt;/strong&gt; an unresolved human role reads &lt;code dir=&quot;auto&quot;&gt;human-in-charge&lt;/code&gt; and an unresolved llm or service role reads &lt;code dir=&quot;auto&quot;&gt;UNKNOWN&lt;/code&gt;, the sentinels &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; defines; a role the inputs resolve still records that actor. The records are built from the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; models, so the package’s validator accepts them. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; installing this release pulls &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&gt;=11.3.0,&amp;#x3C;12&lt;/code&gt; (11.1 and 11.2 were never published).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; folder that is not a Mission is no longer listed or auto-selected as one&lt;/strong&gt; (#5875). &lt;strong&gt;Before:&lt;/strong&gt; any folder with a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; counted, so leftovers could block auto-select. &lt;strong&gt;After:&lt;/strong&gt; a folder with no &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, or (in a git repository) a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; that git does not track, nor the &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;, and that has no &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; or cannot be read, is &lt;code dir=&quot;auto&quot;&gt;residue&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; names each one’s reason and remedy, reports a corrupt &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; as corrupt, and accepts &lt;code dir=&quot;auto&quot;&gt;--fail-on residue&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;doctor mission-type&lt;/code&gt; skips it. A broken git index is one error line (&lt;code dir=&quot;auto&quot;&gt;GIT_INDEX_UNREADABLE&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;). The upgrade residue notice now says to add a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; with a &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;migrate backfill-wp-status --mission&lt;/code&gt; accepts every folder it repairs. &lt;strong&gt;What to do:&lt;/strong&gt; follow the remedy &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; prints.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The implement-review skill now starts implementer and reviewer agents with their sandbox and approvals on&lt;/strong&gt; (#6477). &lt;strong&gt;Before:&lt;/strong&gt; its dispatch commands launched Codex with &lt;code dir=&quot;auto&quot;&gt;--sandbox danger-full-access&lt;/code&gt;, Gemini, Qwen, Copilot and Kilocode with &lt;code dir=&quot;auto&quot;&gt;--yolo&lt;/code&gt;, LLxprt with &lt;code dir=&quot;auto&quot;&gt;--approval-mode=yolo&lt;/code&gt; and Cursor with &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;, giving each sub-agent unrestricted write and network access you never chose. &lt;strong&gt;After:&lt;/strong&gt; Codex runs in &lt;code dir=&quot;auto&quot;&gt;workspace-write&lt;/code&gt;, the Gemini-family agents in edit-only approval mode, Copilot with &lt;code dir=&quot;auto&quot;&gt;git&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; allowed and nothing more. Codex’s sandbox keeps &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; read-only, so the orchestrator now commits a Codex agent’s work and moves its work package; it does the same for any agent that may not run &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; to let more agents run &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; themselves, or to choose elevated dispatch explicitly, see &lt;a href=&quot;/guides/how-to/harnesses/agent-dispatch-permissions/&quot;&gt;Set Agent Dispatch Permissions&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter context points at &lt;code dir=&quot;auto&quot;&gt;docs/adr/&lt;/code&gt; for architectural intent, not the closed &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/&lt;/code&gt;&lt;/strong&gt; (#5428). &lt;strong&gt;Before:&lt;/strong&gt; the default authority paths in every project’s rendered charter context named &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/&lt;/code&gt;, an era that takes no new records, and a project whose ADRs live elsewhere under &lt;code dir=&quot;auto&quot;&gt;docs/adr/&lt;/code&gt; got no pointer. &lt;strong&gt;After:&lt;/strong&gt; the default names &lt;code dir=&quot;auto&quot;&gt;docs/adr/&lt;/code&gt; (shown only when that directory exists), and says ADRs are filed by era. A charter can still declare a specific era directory in &lt;code dir=&quot;auto&quot;&gt;authority_paths&lt;/code&gt;. The built-in review prompt names the same pointer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;When two org packs declare the same DRG node, the later-declared pack now wins for every node&lt;/strong&gt; (spec-kitty-charter #87, ADR-0012). &lt;strong&gt;Before:&lt;/strong&gt; for a node the built-in pack does not ship, the first pack in &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs&lt;/code&gt; won silently; for a built-in node the last pack won; a relationship both packs declared kept the first pack’s provenance and &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the later-declared pack’s node and relationship win, built-in or not, as the docs already said. Each replacement logs a warning naming both packs, and a reported &lt;code dir=&quot;auto&quot;&gt;node_override&lt;/code&gt; conflict names the overridden pack first. &lt;strong&gt;What to do:&lt;/strong&gt; if you relied on the first pack winning, list the pack that should win last in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;. Unchanged: a node declared in one pack’s root &lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; and another’s &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; (the fragment wins), and org template lookup (first match).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The CLI now requires &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; 11.0.0&lt;/strong&gt; (#6399). &lt;strong&gt;Before:&lt;/strong&gt; the CLI took &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&gt;=10.5.1,&amp;#x3C;11&lt;/code&gt; and imported &lt;code dir=&quot;auto&quot;&gt;LOCAL_ONLY_EVENT_TYPES&lt;/code&gt;, which 11.0.0 removed, and it kept its own &lt;code dir=&quot;auto&quot;&gt;LOCAL_ONLY_LIFECYCLE_EVENT_TYPES&lt;/code&gt; set to exempt &lt;code dir=&quot;auto&quot;&gt;MissionReopened&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;FollowUpRecorded&lt;/code&gt; from strict validation. &lt;strong&gt;After:&lt;/strong&gt; the range is &lt;code dir=&quot;auto&quot;&gt;&gt;=11.0.0,&amp;#x3C;12&lt;/code&gt;; the exemption is gone, because both types are canonical events and are now validated like every other lifecycle event. The membership the post-mission state needs is &lt;code dir=&quot;auto&quot;&gt;POST_MISSION_LIFECYCLE_EVENT_TYPES&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;specify_cli.status&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; reinstall or &lt;code dir=&quot;auto&quot;&gt;uv sync&lt;/code&gt; to pick up 11.0.0. If your code imports &lt;code dir=&quot;auto&quot;&gt;LOCAL_ONLY_LIFECYCLE_EVENT_TYPES&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;specify_cli.status&lt;/code&gt;, import &lt;code dir=&quot;auto&quot;&gt;POST_MISSION_LIFECYCLE_EVENT_TYPES&lt;/code&gt; instead. Existing ledgers are not rewritten.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Glossary events are written through the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; ledger contract&lt;/strong&gt; (#6399). &lt;strong&gt;Before:&lt;/strong&gt; glossary events were appended with a local JSON writer that accepted any record, appended blindly after a line a crash had cut short (merging the next event into it, so both were lost), and kept &lt;code dir=&quot;auto&quot;&gt;GlossarySenseUpdated&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;spec-kitty glossary resolve&lt;/code&gt; writes off the canonical path. &lt;strong&gt;After:&lt;/strong&gt; every glossary write, including &lt;code dir=&quot;auto&quot;&gt;GlossarySenseUpdated&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;glossary resolve&lt;/code&gt;, goes through &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events.persistence.append_event&lt;/code&gt;. A record that fails the contract is refused and not written; the refusal is logged, and &lt;code dir=&quot;auto&quot;&gt;glossary resolve&lt;/code&gt; exits 1 without writing either of its events. A ledger whose last line was cut short is repaired before the append: the fragment is moved to &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;log&gt;.torn&lt;/code&gt; next to the log, and the warning names it. &lt;strong&gt;What to do:&lt;/strong&gt; nothing for valid ledgers. If you see a &lt;code dir=&quot;auto&quot;&gt;.torn&lt;/code&gt; file under &lt;code dir=&quot;auto&quot;&gt;.kittify/events/glossary/&lt;/code&gt;, it holds the bytes of an interrupted write. &lt;code dir=&quot;auto&quot;&gt;glossary.EVENTS_AVAILABLE&lt;/code&gt; is removed; the canonical path is always used.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; reports governance diagnostics; &lt;code dir=&quot;auto&quot;&gt;charter list --json&lt;/code&gt; reports declared ids&lt;/strong&gt; (#6407, #6406, #6460). &lt;strong&gt;Before:&lt;/strong&gt; the JSON payload carried no diagnostics, so an unknown selected id was invisible, and &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt; showed only file stems. &lt;strong&gt;After:&lt;/strong&gt; context JSON gains a top-level &lt;code dir=&quot;auto&quot;&gt;diagnostics&lt;/code&gt; list (&lt;code dir=&quot;auto&quot;&gt;context_schema_version&lt;/code&gt; 1.4.0) of &lt;code dir=&quot;auto&quot;&gt;{&quot;code&quot;, &quot;message&quot;}&lt;/code&gt; objects; &lt;code dir=&quot;auto&quot;&gt;code&lt;/code&gt; is one of &lt;code dir=&quot;auto&quot;&gt;UNKNOWN_SELECTION_DROPPED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;CATALOG_DEFAULT_APPLIED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;FALLBACK_APPLIED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;SELECTION_MERGED&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;UNRESOLVED_REFERENCE&lt;/code&gt;, so consumers match on &lt;code dir=&quot;auto&quot;&gt;code&lt;/code&gt; and never on the message wording. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status doctor&lt;/code&gt; now fails its governance check on &lt;code dir=&quot;auto&quot;&gt;UNKNOWN_SELECTION_DROPPED&lt;/code&gt; (shown with ⚠, &lt;code dir=&quot;auto&quot;&gt;healthy: false&lt;/code&gt;, exit 1) instead of printing a green ✓. Available &lt;code dir=&quot;auto&quot;&gt;charter list --all --json&lt;/code&gt; entries gain &lt;code dir=&quot;auto&quot;&gt;declared_id&lt;/code&gt;. Both additions are additive.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The init and project charter walkthrough is now a governance how-to guide&lt;/strong&gt; (#5428). &lt;strong&gt;Before:&lt;/strong&gt; it sat among the plans user journeys, and a superseded launch-readiness plan and three retired plan notes sat in the live tree. &lt;strong&gt;After:&lt;/strong&gt; it is &lt;code dir=&quot;auto&quot;&gt;docs/guides/how-to/governance/init-and-project-charter.md&lt;/code&gt;, listed with the Governance &amp;#x26; Doctrine guides; the retired pages moved to &lt;code dir=&quot;auto&quot;&gt;docs/archive/&lt;/code&gt;, and the old launch-readiness page now only links to its archived copy, so existing links keep working.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Synthesized testing, quality-gate and documentation styleguides now follow their directive, and removing one sticks&lt;/strong&gt; (#6442). &lt;strong&gt;Before:&lt;/strong&gt; a synthesized styleguide had no source edge, so it reached context as a root whether or not its directive was in force, and one you removed from an explicit &lt;code dir=&quot;auto&quot;&gt;activated_styleguides&lt;/code&gt; list could come back. &lt;strong&gt;After:&lt;/strong&gt; synthesis links &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_034&lt;/code&gt; (testing), &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_030&lt;/code&gt; (quality gates) and &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_037&lt;/code&gt; (documentation) to their styleguide with a &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edge. It is delivered only while that directive is in force, now including software-dev &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;. It is appended to an explicit list once and never again after you remove it, tracked in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-artifacts.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The always-synthesized directive is now &lt;code dir=&quot;auto&quot;&gt;project-intent-directive&lt;/code&gt;, and it no longer links to a mission type&lt;/strong&gt; (#6443). &lt;strong&gt;Before:&lt;/strong&gt; the directive built from the project-intent answer was named &lt;code dir=&quot;auto&quot;&gt;mission-type-scope-directive&lt;/code&gt; and, when the answer named a shipped mission type, carried a &lt;code dir=&quot;auto&quot;&gt;requires --&gt; mission_type:*&lt;/code&gt; edge that no traversal follows. &lt;strong&gt;After:&lt;/strong&gt; it is named &lt;code dir=&quot;auto&quot;&gt;project-intent-directive&lt;/code&gt; with the title “Project Intent Directive”, the dead edge is neither emitted nor kept, and the id (&lt;code dir=&quot;auto&quot;&gt;PROJECT_001&lt;/code&gt;) and every reference to it are unchanged. The &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_project_intent_directive_rename&lt;/code&gt; migration moves an existing project, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; converges the artifact file, harness input, provenance, synthesis manifest, graph label and activation lists, and a second run reports nothing to do. &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt; run the same rename before they write.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One language catalog now drives detection, declared answers and doctrine scoping, with Kotlin and the &lt;code dir=&quot;auto&quot;&gt;jvm&lt;/code&gt; family&lt;/strong&gt; (#6444). &lt;strong&gt;Before:&lt;/strong&gt; the evidence reader and the declared-language reader kept separate vocabularies, a repository was described by a single language, &lt;code dir=&quot;auto&quot;&gt;kotlin&lt;/code&gt; was not a token, and a project declaring only “Gradle”, “Maven” or “JUnit” had no language at all. &lt;strong&gt;After:&lt;/strong&gt; one catalog in &lt;code dir=&quot;auto&quot;&gt;charter.offering.shared&lt;/code&gt; is the only language vocabulary. A JVM manifest with more &lt;code dir=&quot;auto&quot;&gt;.kt&lt;/code&gt; than &lt;code dir=&quot;auto&quot;&gt;.java&lt;/code&gt; sources, or a declared “Kotlin”, resolves to &lt;code dir=&quot;auto&quot;&gt;kotlin&lt;/code&gt;; declared “Gradle”, “Maven” or “JUnit” alone resolves to &lt;code dir=&quot;auto&quot;&gt;[jvm]&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;jvm&lt;/code&gt; is a family expanded at match time, so both &lt;code dir=&quot;auto&quot;&gt;java&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;kotlin&lt;/code&gt; projects match &lt;code dir=&quot;auto&quot;&gt;jvm&lt;/code&gt;-tagged doctrine, while &lt;code dir=&quot;auto&quot;&gt;java&lt;/code&gt;-tagged doctrine still applies only to Java.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Synthesis evidence now lists every language of a polyglot repository&lt;/strong&gt; (#6444). &lt;strong&gt;Before:&lt;/strong&gt; evidence carried only &lt;code dir=&quot;auto&quot;&gt;primary_language&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it also carries &lt;code dir=&quot;auto&quot;&gt;languages&lt;/code&gt;: the primary language is always listed, and another language is listed only when it holds at least 20% of the counted sources; a manifest alone only nominates a candidate. &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter synthesize --dry-run&lt;/code&gt; add &lt;code dir=&quot;auto&quot;&gt;languages&lt;/code&gt; to their evidence JSON, and the neutrality gate treats a slug naming any listed language as language-scoped. &lt;code dir=&quot;auto&quot;&gt;languages&lt;/code&gt; enters the evidence hash only for a polyglot repository, so the hash changes only for polyglot and Kotlin-majority repositories, whose primary language changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A configured &lt;code dir=&quot;auto&quot;&gt;languages:&lt;/code&gt; list in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; now sets the project languages&lt;/strong&gt; (#6444). &lt;strong&gt;Before:&lt;/strong&gt; languages were re-derived from files and free text on every run. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; proposes the detected languages, you confirm them, and the list is stored; a non-interactive run stores the detected list and prints a notice saying so. A configured list drives &lt;code dir=&quot;auto&quot;&gt;catalog.languages&lt;/code&gt;, evidence &lt;code dir=&quot;auto&quot;&gt;languages&lt;/code&gt; and the bundle hash. The list accepts &lt;code dir=&quot;auto&quot;&gt;jvm&lt;/code&gt; on its own, the token a declared “Gradle” or “Maven” resolves to. See &lt;a href=&quot;/api/charter-commands/&quot;&gt;charter commands&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Language-scoped styleguide slugs follow the catalog&lt;/strong&gt; (#6444). &lt;strong&gt;Before:&lt;/strong&gt; a phrase answer such as “Python 3.12” or “Kotlin and Java” was slugged as a whole. &lt;strong&gt;After:&lt;/strong&gt; “Python 3.12” gives &lt;code dir=&quot;auto&quot;&gt;python-style-guide&lt;/code&gt; and “Kotlin and Java” gives one styleguide for each language, so the slugs of an existing project that used such a phrase change on its next synthesis.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The shared JVM toolguides now apply to Kotlin projects&lt;/strong&gt; (#6444). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;java-supply-chain&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;maven-review-checks&lt;/code&gt; were tagged &lt;code dir=&quot;auto&quot;&gt;java&lt;/code&gt;, so a Kotlin project with Gradle never received them. &lt;strong&gt;After:&lt;/strong&gt; both are tagged &lt;code dir=&quot;auto&quot;&gt;jvm&lt;/code&gt;, so Java and Kotlin projects receive them and a Python project still receives neither. &lt;code dir=&quot;auto&quot;&gt;java-jenny&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;java-conventions&lt;/code&gt; stay Java-only.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Synthesis request hashes of polyglot repositories and affected targets change once&lt;/strong&gt; (#6442, #6443, #6444). &lt;strong&gt;Before:&lt;/strong&gt; the request hash covered the target slug and &lt;code dir=&quot;auto&quot;&gt;source_urns&lt;/code&gt;, but not &lt;code dir=&quot;auto&quot;&gt;languages&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it also covers &lt;code dir=&quot;auto&quot;&gt;languages&lt;/code&gt; for polyglot evidence, and the renamed project-intent slug and the new styleguide sources change those hashed values. A recorded synthesis fixture for an affected target must be re-keyed to the new hash. Some single-language repositories change once too: a Kotlin-majority repository now records &lt;code dir=&quot;auto&quot;&gt;kotlin&lt;/code&gt; as its primary language, and a repository with fewer than five root files whose evidence sampled files under &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; or an agent directory now samples project files instead, because those directories no longer count as project source.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activating a skill now warns that the org packs’ required skills are frozen&lt;/strong&gt; (#6458). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;activate skill &amp;#x3C;id&gt;&lt;/code&gt; on a project with no &lt;code dir=&quot;auto&quot;&gt;activated_skills&lt;/code&gt; list, and every &lt;code dir=&quot;auto&quot;&gt;activate skill &amp;#x3C;id&gt; --only&lt;/code&gt;, froze the org packs’ required skills at their current values without saying so, and the plain path recommended &lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; both warn that a skill an org pack requires later will not reach the project, and the plain path no longer recommends &lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt;. What is written is unchanged; the semantics are tracked in epic #6518.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activation lists are stored in one spelling: the artifact’s file name&lt;/strong&gt; (#6527, #6435). &lt;strong&gt;Before:&lt;/strong&gt; filling an absent list, presets, interview promotion and the org-required union could store an org or project artifact under both its file name and its declared id, or under its declared id alone. &lt;strong&gt;After:&lt;/strong&gt; every writer stores the file name; a declared id or a &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;kind&gt;:&amp;#x3C;id&gt;&lt;/code&gt; URN is accepted on input and stored as the file name. Writers refuse a declared id whose file name another layer uses for a different id (for example &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_024&lt;/code&gt; when an org file named &lt;code dir=&quot;auto&quot;&gt;024-locality-of-change&lt;/code&gt; declares &lt;code dir=&quot;auto&quot;&gt;ACME_024&lt;/code&gt;); the error names both files and says which one to rename (never the built-in one). Existing lists are not migrated; they take the new spelling on their next write. The contract export of declared ids stays with #6520.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Status events written by agents and operators record a structured actor&lt;/strong&gt; (#6400, #6448, #6271). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;add-history&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent status emit&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; lifecycle commands stored a bare actor string. &lt;strong&gt;After:&lt;/strong&gt; they store &lt;code dir=&quot;auto&quot;&gt;{tool, role, profile, model}&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; comes from the action, &lt;code dir=&quot;auto&quot;&gt;profile&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt; from the dispatch invocation, &lt;code dir=&quot;auto&quot;&gt;--profile&lt;/code&gt; or a compact &lt;code dir=&quot;auto&quot;&gt;tool:model:profile&lt;/code&gt; value, else &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; (new flag) and &lt;code dir=&quot;auto&quot;&gt;add-history&lt;/code&gt; parse &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt; alike, refusing a malformed one. Claim checks, the board and displays use the bare tool. A free-text &lt;code dir=&quot;auto&quot;&gt;--actor&lt;/code&gt; with over 4 segments, or starting with &lt;code dir=&quot;auto&quot;&gt;migration:&lt;/code&gt;, is stored whole. Envelopes are unchanged; string actors read. Lanes come from &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;status validate&lt;/code&gt; uses the shared seed check. &lt;code dir=&quot;auto&quot;&gt;profile_source&lt;/code&gt; is planned (#6721).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One authority now decides every per-user cache, state and config location, so a macOS user has one cache tree instead of two&lt;/strong&gt; (#6896, #6488). &lt;strong&gt;Before:&lt;/strong&gt; three callers applied an XDG-only rule (&lt;code dir=&quot;auto&quot;&gt;~/.cache/spec-kitty&lt;/code&gt; on macOS), two called &lt;code dir=&quot;auto&quot;&gt;platformdirs&lt;/code&gt; themselves (&lt;code dir=&quot;auto&quot;&gt;~/Library/Caches/spec-kitty&lt;/code&gt;), and the runtime-package marker fell back to &lt;code dir=&quot;auto&quot;&gt;~/.cache&lt;/code&gt;, so the upgrade, pack and service caches split from the upgrade-nag cache. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;kernel.user_dirs&lt;/code&gt; alone resolves them — Linux &lt;code dir=&quot;auto&quot;&gt;${XDG_CACHE_HOME:-~/.cache}/spec-kitty&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;${XDG_STATE_HOME:-~/.local/state}/spec-kitty&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;${XDG_CONFIG_HOME:-~/.config}/spec-kitty&lt;/code&gt;; macOS &lt;code dir=&quot;auto&quot;&gt;~/Library/Caches/spec-kitty&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;~/Library/Application Support/spec-kitty&lt;/code&gt;; Windows &lt;code dir=&quot;auto&quot;&gt;%LOCALAPPDATA%\spec-kitty\Cache&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;%LOCALAPPDATA%\spec-kitty&lt;/code&gt;; an XDG variable still wins where it did. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; the old directories go on the next command. On Windows the upgrade-nag settings file (&lt;code dir=&quot;auto&quot;&gt;upgrade.yaml&lt;/code&gt;) is copied to the new config location (&lt;code dir=&quot;auto&quot;&gt;%LOCALAPPDATA%\spec-kitty&lt;/code&gt;) before the old tree is removed, never over an existing file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Core now pins the read service from &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; and no longer carries its own copy&lt;/strong&gt; (#6915). &lt;strong&gt;Before:&lt;/strong&gt; core built the Mission Status Read API from &lt;code dir=&quot;auto&quot;&gt;services/&lt;/code&gt; and checked its contracts from &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt;, with the &lt;code dir=&quot;auto&quot;&gt;mission-status-api.yml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;contracts.yml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;contracts-release.yml&lt;/code&gt; workflows. &lt;strong&gt;After:&lt;/strong&gt; core pins the read service from &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;service-v0.1.0-rc.1&lt;/code&gt; (CI conformance only), and the contract tests read its release assets. &lt;code dir=&quot;auto&quot;&gt;services/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; (except the five handoff fixtures) and the three workflows are removed, and &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_events_cutover_absent.py&lt;/code&gt; replaces the freeze gate. The release verifies the service pins before it builds; the CLI wheel ships pins, never a binary. &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;make dev-setup&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;make sync-services ARGS=--extras-only&lt;/code&gt;) in each checkout; the contract tests fail closed without the pinned extras.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; writes each Op lifecycle record to its own file&lt;/strong&gt; (#7003). &lt;strong&gt;Before:&lt;/strong&gt; every &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; record was appended to the one shared &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl&lt;/code&gt;, so two pull requests that each ran &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; conflicted at its end and the merge queue dropped the second. &lt;strong&gt;After:&lt;/strong&gt; each record is a new &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ulid&gt;.json&lt;/code&gt; that no other branch writes, so the two pull requests merge with plain git. &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl&lt;/code&gt; is still read, after which the record files follow in time order, and is never written again; the orphan report and pairing rate are unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; commit the new &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&lt;/code&gt; files as you committed the log.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A bare &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt; now runs the project’s default checks instead of exiting 2&lt;/strong&gt; (#7018, #6969, superseding #4678’s exit-2 remedy). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt; with no subcommand printed the group help and exited 2 (“no diagnostic ran”), which the docs, the skills and every wrapper read as a usage error or a failed check. &lt;strong&gt;After:&lt;/strong&gt; it runs &lt;code dir=&quot;auto&quot;&gt;command-files&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;state-roots&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ops&lt;/code&gt; — all read-only and project-local — prints one line per check naming the subcommand that shows the full report, and exits 0 when every check is healthy, 1 as soon as one reports a finding (or fails). Outside a project it exits 1 with the standard not-in-project error. Every &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor &amp;#x3C;subcommand&gt;&lt;/code&gt; keeps its own output and exit codes. &lt;strong&gt;What to do:&lt;/strong&gt; a wrapper that treated exit 2 as “nothing ran” should read 0/1; use &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor &amp;#x3C;subcommand&gt; --json&lt;/code&gt; for machine-readable detail.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pinning a service now defaults to that service’s own release repository, and a GitHub bump verifies the release’s build provenance before it writes the pin&lt;/strong&gt; (#6909). &lt;strong&gt;Before:&lt;/strong&gt; every &lt;code dir=&quot;auto&quot;&gt;spec-kitty service vendor&lt;/code&gt; bump defaulted to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;, the charter service’s asset prefix was marked provisional, and a bump trusted the release’s &lt;code dir=&quot;auto&quot;&gt;SHA256SUMS&lt;/code&gt; alone. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter-service&lt;/code&gt; defaults to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter&lt;/code&gt; (the events services stay on &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;), and each downloaded asset is checked with &lt;code dir=&quot;auto&quot;&gt;gh attestation verify&lt;/code&gt; (signer workflow and source tag ref) before &lt;code dir=&quot;auto&quot;&gt;pins/&amp;#x3C;service&gt;.source.yaml&lt;/code&gt; is written. A refusal leaves the lockfile unchanged, and &lt;code dir=&quot;auto&quot;&gt;--no-attestation&lt;/code&gt; is the explicit escape for an offline mirror or a rehearsal; a &lt;code dir=&quot;auto&quot;&gt;file://&lt;/code&gt; pin and an installed CLI’s fetch still verify the pinned digest only. See &lt;a href=&quot;/development/how-to/service-pins/&quot;&gt;Service pins&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New Op records no longer persist an AI model identifier, and claims no longer accept an unprovable model actual&lt;/strong&gt; (#7013). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; wrote the router’s catalog pick into &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;ulid&gt;.jsonl&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;model_id&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;agent implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent review&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task&lt;/code&gt; checked &lt;code dir=&quot;auto&quot;&gt;--model&lt;/code&gt; against that record. &lt;strong&gt;After:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; event keeps only the harness key in &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt;, the routing recommendation stays advisory, &lt;code dir=&quot;auto&quot;&gt;--model&lt;/code&gt; is refused with a message saying to omit it, and the work package records the model slot as explicitly absent. Existing records stay byte-for-byte unchanged and still parse. &lt;strong&gt;What to do:&lt;/strong&gt; omit &lt;code dir=&quot;auto&quot;&gt;--model&lt;/code&gt; from claim commands.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty events tail&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status materialize&lt;/code&gt; refuse a status that lives only on a branch&lt;/strong&gt; (#7276). &lt;strong&gt;Before:&lt;/strong&gt; with the coordination worktree empty or absent, or a default Mission’s topic branch held by no checkout, &lt;code dir=&quot;auto&quot;&gt;events tail --once&lt;/code&gt; printed nothing and a stream waited for a file, and &lt;code dir=&quot;auto&quot;&gt;materialize&lt;/code&gt; wrote or read the repository root checkout’s copy. &lt;strong&gt;After:&lt;/strong&gt; both exit 1 with &lt;code dir=&quot;auto&quot;&gt;status_surface_on_ref&lt;/code&gt; and a remedy (materialize the coordination worktree, or check out the topic branch), and a status source the read door cannot resolve exits 1 with &lt;code dir=&quot;auto&quot;&gt;status_surface_unavailable&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; run the printed remedy, then re-run the command; scripts that treated an empty &lt;code dir=&quot;auto&quot;&gt;events tail --once&lt;/code&gt; as “no events” should check the exit code.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lane cleanup is the last step of &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;&lt;/strong&gt; (#7280). &lt;strong&gt;Before:&lt;/strong&gt; lane and coordination checkouts and branches were removed in the middle of the run. &lt;strong&gt;After:&lt;/strong&gt; they are removed only after the landing is verified, under the destructive guard, with one line per lane: &lt;code dir=&quot;auto&quot;&gt;Removed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;Kept&lt;/code&gt; (the guard refused; the line names the code) or &lt;code dir=&quot;auto&quot;&gt;Retained&lt;/code&gt; (retention policy); a &lt;code dir=&quot;auto&quot;&gt;Kept&lt;/code&gt; lane does not fail the run. An interrupted cleanup resumes from a &lt;code dir=&quot;auto&quot;&gt;cleanup_started&lt;/code&gt; marker, and &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; after it rolls nothing back and prints &lt;code dir=&quot;auto&quot;&gt;git branch &amp;#x3C;b&gt; &amp;#x3C;sha&gt;&lt;/code&gt; recreate hints. &lt;strong&gt;What to do:&lt;/strong&gt; remove a &lt;code dir=&quot;auto&quot;&gt;Kept&lt;/code&gt; lane yourself once you have checked what the guard named.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lane cleanup goes through the landed-removal guard, and &lt;code dir=&quot;auto&quot;&gt;accept --mode pr&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor workspaces --prune&lt;/code&gt; clean up a released Mission’s lanes&lt;/strong&gt; (#7280, #7275). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; removed lane worktrees with the older guarded primitives, &lt;code dir=&quot;auto&quot;&gt;accept --mode pr&lt;/code&gt; printed raw &lt;code dir=&quot;auto&quot;&gt;git worktree remove&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;git branch -d&lt;/code&gt; advice, and &lt;code dir=&quot;auto&quot;&gt;doctor workspaces --prune&lt;/code&gt; always reported a Mission lane as report-only. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; remove each lane through &lt;code dir=&quot;auto&quot;&gt;guarded_landed_removal&lt;/code&gt;, proving the local target is still at the PASS tip (a moved target keeps the lane with &lt;code dir=&quot;auto&quot;&gt;LOCAL_TARGET_OFF_GATE_TIP&lt;/code&gt;); a committed &lt;code dir=&quot;auto&quot;&gt;accept --mode pr&lt;/code&gt; removes every lane the pushed pull request head already carries and keeps the rest with &lt;code dir=&quot;auto&quot;&gt;NOT_LANDED_ON_NAMED_REMOTE&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;doctor workspaces --prune&lt;/code&gt; treats a lane of a consolidated or pr-accepted Mission as a candidate when no consolidation record is active and no retention is declared. A moved lane, or one with no process probe (macOS, Windows), is kept and reported. &lt;strong&gt;What to do:&lt;/strong&gt; after a pull request lands, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces --prune&lt;/code&gt; for any lane that was kept.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lane cleanup keeps a lane whose work never landed, and &lt;code dir=&quot;auto&quot;&gt;accept --mode pr&lt;/code&gt; honors lane retention&lt;/strong&gt; (#7280). &lt;strong&gt;Before:&lt;/strong&gt; a lane &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; did not land, such as one whose work packages were all canceled, was deleted with no ref left to restore it, and &lt;code dir=&quot;auto&quot;&gt;accept --mode pr&lt;/code&gt; removed the lanes of a Mission created with &lt;code dir=&quot;auto&quot;&gt;--retain-worktrees&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;--retain-branches&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the first is kept with &lt;code dir=&quot;auto&quot;&gt;NOT_LANDED_ON_NAMED_REMOTE&lt;/code&gt;, and the second reports its lanes &lt;code dir=&quot;auto&quot;&gt;Retained&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; remove a kept lane yourself once you no longer need its commits.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lane checkouts no longer carry the Mission’s status files&lt;/strong&gt; (#7281). &lt;strong&gt;Before:&lt;/strong&gt; every lane worktree held its own copy of &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, which could drift from the status surface. &lt;strong&gt;After:&lt;/strong&gt; a managed sparse exclusion keeps both files out of every lane checkout, and a status write aimed at a lane checkout refuses with &lt;code dir=&quot;auto&quot;&gt;STATUS_WRITE_TARGETS_LANE_CHECKOUT&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; run status commands from any checkout; the CLI writes to the status surface.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A Mission’s default topology is settled by size at the first &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;&lt;/strong&gt; (#7282). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; chose &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; from the current branch. &lt;strong&gt;After:&lt;/strong&gt; create mints one Mission topic branch and no worktree on every target; the first &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; keeps &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; for at most two work packages or at most one code lane, and otherwise settles &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; with the topic branch as the coordination branch (ADR &lt;code dir=&quot;auto&quot;&gt;2026-11-06-3&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;--validate-only&lt;/code&gt; only previews, and a failed settlement is undone and refuses with &lt;code dir=&quot;auto&quot;&gt;TOPOLOGY_SETTLEMENT_REFUSED&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuses the coordination teardown, keeping the branch, while the topic branch holds planning changes the target does not carry. &lt;strong&gt;What to do:&lt;/strong&gt; pass &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; to choose a topology yourself; &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; are explicit-only.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Core skills and agent guidance teach the shipped lane model&lt;/strong&gt; (#7285). &lt;strong&gt;Before:&lt;/strong&gt; skills taught &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt;, manual stale-lane recipes (&lt;code dir=&quot;auto&quot;&gt;cd .worktrees/...&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;git merge&lt;/code&gt;) and hand status commits. &lt;strong&gt;After:&lt;/strong&gt; they teach &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, status reads through the CLI, cleanup as the last step and the for_review gate on the lane branch; the stale-lane remedy prints &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement &amp;#x3C;WP&gt; --mission &amp;#x3C;handle&gt;&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to refresh the generated skills.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; no longer deletes a coordination branch carrying a verdict it did not project&lt;/strong&gt; (#6857; #6791). &lt;strong&gt;Before:&lt;/strong&gt; after a &lt;code dir=&quot;auto&quot;&gt;COORD_TEARDOWN_KEPT_ONLY_COPY&lt;/code&gt; refusal, the resume dropped the &lt;code dir=&quot;auto&quot;&gt;agent issue-verdict&lt;/code&gt; commit the refusal told you to make, and the Mission landed with the row still &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the late window (what changed on the coordination branch since the merge began) projects gate matrices too and proves every coordination record is committed on the target. A record it cannot land refuses with exit 1 and &lt;code dir=&quot;auto&quot;&gt;Error code: COORD_LATE_PROJECTION_REFUSED.&lt;/code&gt;, keeping the branch, worktree and marker. &lt;strong&gt;What to do:&lt;/strong&gt; any &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; whose window holds such a record now refuses; follow the repair in the message and resume.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; re-run after a failed attempt no longer re-flags, or rolls back over, commits made on the target in between&lt;/strong&gt; (#6867; #6770, #5667). &lt;strong&gt;Before:&lt;/strong&gt; a reconciliation failure whose rollback restored every branch left its target baseline in &lt;code dir=&quot;auto&quot;&gt;.kittify/runtime/merge/&amp;#x3C;mission_id&gt;/state.json&lt;/code&gt;, so the next plain &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; resumed it, judged every commit landed since un-attributable, and rolled back over them; a plain &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; then refused with &lt;code dir=&quot;auto&quot;&gt;NOT restored … no post-mutation tip was recorded&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; a rollback that restored every branch drops that attempt’s baseline, snapshot and restore targets, so the next run reads the target’s current tip and &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; finishes cleanly. A rollback that leaves a branch &lt;code dir=&quot;auto&quot;&gt;NOT restored&lt;/code&gt; keeps them. See &lt;a href=&quot;/guides/how-to/recovery/troubleshoot-merge/#a-failed-run-that-rolled-back-completely-drops-its-baseline&quot;&gt;Troubleshooting&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; with a legal activation key now passes its model&lt;/strong&gt; (#6850, #6556). &lt;strong&gt;Before:&lt;/strong&gt; the model for &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; refused &lt;code dir=&quot;auto&quot;&gt;activated_skills&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;activated_glossary_packs&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;activated_anti_patterns&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;Extra inputs are not permitted&lt;/code&gt;. Yet &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; writes those keys to &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; on a project not yet migrated to the activation ledger. So a caller that checked a valid charter through the model rejected it. &lt;strong&gt;After:&lt;/strong&gt; the model declares every activation key the writer uses and still refuses anything else, including &lt;code dir=&quot;auto&quot;&gt;activated_assets&lt;/code&gt;, which is not an activation key. A test fails if the two drift apart. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; no file on disk changes. You can drop any workaround for the three fields.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; runs can no longer lose a migration record&lt;/strong&gt; (#6842; #6613). &lt;strong&gt;Before:&lt;/strong&gt; the ledger append was an unlocked read-modify-write, so a second run could drop the first’s &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt; record and the migration re-ran. ADR 2026-10-17-1 also claimed pure ledger-diff selection, while a recorded &lt;code dir=&quot;auto&quot;&gt;runs_first&lt;/code&gt; migration was re-selected when &lt;code dir=&quot;auto&quot;&gt;structural_detect&lt;/code&gt; fired. &lt;strong&gt;After:&lt;/strong&gt; each append holds a 30 s lock in &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;state dir&gt;/spec-kitty/locks/migration-ledger/&lt;/code&gt;, never in your checkout. A lock that never frees raises &lt;code dir=&quot;auto&quot;&gt;MigrationLedgerLockTimeoutError&lt;/code&gt;, appends nothing, and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;migrate activation-ledger&lt;/code&gt; refuse (exit 1). The ADR now records the reselection, its one-&lt;code dir=&quot;auto&quot;&gt;runs_first&lt;/code&gt; bound, and that removing it is an open operator decision. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; the record format is unchanged. Closing gap G-15 in the event-ledger page waits for the events-import re-pin.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A first &lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt; no longer blocks &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;&lt;/strong&gt; (#6875; #6685). &lt;strong&gt;Before:&lt;/strong&gt; with no &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; key, both wrote the kind’s whole in-force set (38 directives, 14 paradigms). &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; read that as your activation: one companion tactic per directive, no fresh-project seed, and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; refused every work package with &lt;code dir=&quot;auto&quot;&gt;synthesized_drg missing&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the key stays absent, since every artifact of that kind is already in force. The run names the key, the flag that writes a list, and any selected id you deactivated. &lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;skill&lt;/code&gt;, ids not in force, unresolved sets and existing lists are unchanged. &lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt; deactivation leaves the children of such a kind in force and prints the &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; command for each (#6873). &lt;strong&gt;What to do:&lt;/strong&gt; nothing; to keep activation narrow, use &lt;code dir=&quot;auto&quot;&gt;--only&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;--narrow-activation&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A forced rewind out of review can no longer leave a Mission’s status log permanently invalid&lt;/strong&gt; (#6897, #6514). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent status emit WP01 --to in_progress --force --reason &quot;&amp;#x3C;why&gt;&quot;&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; work package exited 0 and appended an event with &lt;code dir=&quot;auto&quot;&gt;review_ref: null&lt;/code&gt;, which &lt;code dir=&quot;auto&quot;&gt;agent status validate&lt;/code&gt; then rejected; the append-only log could not be repaired. &lt;strong&gt;After:&lt;/strong&gt; every write door refuses that event before appending and leaves &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; untouched. &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; are not covered. &lt;code dir=&quot;auto&quot;&gt;--force --reason&lt;/code&gt; still works with a real &lt;code dir=&quot;auto&quot;&gt;--review-ref&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; pass &lt;code dir=&quot;auto&quot;&gt;--review-ref &amp;#x3C;ref&gt;&lt;/code&gt; when you force a rewind out of &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;; for older rows see &lt;a href=&quot;/architecture/status-model/#forced-rewinds-out-of-review&quot;&gt;the status model&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A lane auto-commit of a new directory commits exactly its files, and no longer blames a hook&lt;/strong&gt; (#6870, #6750). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; passed &lt;code dir=&quot;auto&quot;&gt;?? dir/&lt;/code&gt; to the commit, git expanded it, and the files landed. The check after the commit then called them unrequested and said “a pre-commit hook staged them”, even with no hooks. It also printed “could not auto-commit” for a commit that had landed. &lt;strong&gt;After:&lt;/strong&gt; untracked entries are read expanded (&lt;code dir=&quot;auto&quot;&gt;--untracked-files=all&lt;/code&gt;, as &lt;code dir=&quot;auto&quot;&gt;safe-commit&lt;/code&gt; already does). A directory path is refused with &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_DIRECTORY_ARGUMENT&lt;/code&gt; before anything is written, so a request takes exact paths or fails whole. A landed commit is reported as landed, with its SHA. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; &lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit &amp;#x3C;dir&gt;&lt;/code&gt; still expands the directory for you.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate --dependency-ref &amp;#x3C;ref&gt;&lt;/code&gt; lands a Mission that pulled in a newer dependency branch&lt;/strong&gt; (#6853, #6771). &lt;strong&gt;Before:&lt;/strong&gt; a lane that merged a dependency head (&lt;code dir=&quot;auto&quot;&gt;git merge --no-ff &amp;#x3C;dep&gt;&lt;/code&gt;) was refused as &lt;code dir=&quot;auto&quot;&gt;un-attributable&lt;/code&gt; (exit 1, rolled back), while &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; exited 0. &lt;strong&gt;After:&lt;/strong&gt; declare the ref (repeatable, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; only, not &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt;) on the preview and the run; its commits count as inherited history under &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;squash&lt;/code&gt;. A ref naming Mission work is refused. The ref is pinned at claim; a moved ref or a changed set on &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; refuses with a &lt;code dir=&quot;auto&quot;&gt;DEPENDENCY_REF_*&lt;/code&gt; code. An undeclared restack stays refused. &lt;strong&gt;Changed:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; builds the full claim, so it also reports claim-time refusals. &lt;strong&gt;What to do:&lt;/strong&gt; nothing, unless you restack (&lt;a href=&quot;/guides/how-to/missions/merge-mission/#restack-onto-a-newer-dependency-branch&quot;&gt;how to&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now retries a residue-safe repair whose predecessor never finished&lt;/strong&gt; (#6869, #6688). &lt;strong&gt;Before:&lt;/strong&gt; on a project older than the Migration Ledger, first adoption settled every step below the recorded version. That included a residue-safe successor whose superseded predecessor &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt; recorded as &lt;code dir=&quot;auto&quot;&gt;failed&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt;. The repair never retried, and a recoverable project stayed stuck. &lt;strong&gt;After:&lt;/strong&gt; a step that replaces a shipped migration is settled by its predecessor’s recorded outcome. The successor runs whenever the predecessor never recorded &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt;. A repair already done is never re-applied: &lt;code dir=&quot;auto&quot;&gt;detect()&lt;/code&gt; decides and nothing is written, so a held &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt; is never downgraded to &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; the next &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; retries the repair and later ones are no-ops.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; promotes an org-pack interview selection instead of reporting it unresolved&lt;/strong&gt; (#6862, #6686). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_promote_interview_selections&lt;/code&gt; resolved selections in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/interview/answers.yaml&lt;/code&gt; against the built-in pack only, so an org-pack or project-pack selection was skipped as &lt;code dir=&quot;auto&quot;&gt;Unresolved interview selections skipped (not promoted)&lt;/code&gt;, although &lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; had accepted it. &lt;strong&gt;After:&lt;/strong&gt; both resolve project pack, then org packs, then built-in, as &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; does; an id no layer knows is still reported. Mission-step-contract selections now resolve and promote too (the interview does not capture them). &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; again on an org-pack project; the skipped selections are appended.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent tasks mark-status&lt;/code&gt; refuses an ambiguous subtask id, and never records a work-package id as a subtask&lt;/strong&gt; (#6886, #6463). &lt;strong&gt;Before:&lt;/strong&gt; the owner was picked twice, the second time by first match. An id in one work package’s &lt;code dir=&quot;auto&quot;&gt;subtasks:&lt;/code&gt; roster and another’s &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; row silently marked the roster owner. &lt;code dir=&quot;auto&quot;&gt;mark-status WP02&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; index table recorded &lt;code dir=&quot;auto&quot;&gt;{&quot;WP02&quot;: &quot;done&quot;}&lt;/code&gt; on WP02 instead of refusing. &lt;strong&gt;After:&lt;/strong&gt; owners are the union of rosters and &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; rows. A shared id is refused before any write, naming every owner. A &lt;code dir=&quot;auto&quot;&gt;WP&amp;#x3C;digits&gt;&lt;/code&gt; id authored as a subtask needs &lt;code dir=&quot;auto&quot;&gt;--wp&lt;/code&gt;; one nobody authors gets the lane-transition rejection (&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; changes lanes). The completion event names only the resolved owner. &lt;code dir=&quot;auto&quot;&gt;--wp&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; envelope and the single-roster shape are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A fresh lane warns when its base is behind the target; &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; accepts &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt;&lt;/strong&gt; (#6753). &lt;strong&gt;Before:&lt;/strong&gt; on a coordination-topology Mission, a lane cut after the target advanced started from the stale coordination branch in silence. The path &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.implement&lt;/code&gt; use had no &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the cut prints one &lt;code dir=&quot;auto&quot;&gt;WARNING:&lt;/code&gt; on stderr naming the base ref, the target branch, the missing target commit and the &lt;code dir=&quot;auto&quot;&gt;--base &amp;#x3C;target&gt;&lt;/code&gt; command to recut. It is silent when the base is current or the target cannot be resolved; the lane still parents on the coordination branch. &lt;code dir=&quot;auto&quot;&gt;agent action implement --base &amp;#x3C;ref&gt;&lt;/code&gt; mirrors &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement --base&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; on an existing lane is refused. &lt;strong&gt;What to do:&lt;/strong&gt; if the warning appears and the work package needs the newer commits, re-run with &lt;code dir=&quot;auto&quot;&gt;--base &amp;#x3C;target&gt;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; no longer says an in-force reference “was not activated”&lt;/strong&gt; (#6742). &lt;strong&gt;Before:&lt;/strong&gt; with no &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; key, every artifact of that kind is in force, yet the command printed &lt;code dir=&quot;auto&quot;&gt;Warning: referenced kind/id was not activated (no --cascade).&lt;/code&gt; per reference (about 150 lines for a mission type), plus a useless hint to re-run with &lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; such a reference reads &lt;code dir=&quot;auto&quot;&gt;Note: referenced kind/id is already in force (&amp;#x3C;reason&gt;); not added by this command.&lt;/code&gt;, with &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;reason&gt;&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;no explicit list&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;listed in activated_&amp;#x3C;plural&gt;&lt;/code&gt;. The warning and hint stay for references truly not in force: omitted from an explicit list, or deactivated. &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;referenced_already_in_force&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;referenced_not_cascaded&lt;/code&gt; keeps only artifacts not in force, so none appears in both. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; scripts reading &lt;code dir=&quot;auto&quot;&gt;referenced_not_cascaded&lt;/code&gt; now get a truthful, smaller list.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A work package with no committed work, or approved by its own implementer, is now refused on every topology&lt;/strong&gt; (#6715; #5939). &lt;strong&gt;Before:&lt;/strong&gt; on a lanes or coordination Mission such a work package was approved, accepted and consolidated at exit 0, deliverable missing. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; (even &lt;code dir=&quot;auto&quot;&gt;--lenient&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; refuse with &lt;code dir=&quot;auto&quot;&gt;IMPLEMENTATION_MISSING&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;REVIEW_NOT_INDEPENDENT&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; keeps its &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH_*&lt;/code&gt; codes); a reviewer is independent only when its recorded identity provably differs. &lt;strong&gt;What to do:&lt;/strong&gt; commit to the owned files, have someone else approve it, and pass the full &lt;code dir=&quot;auto&quot;&gt;--agent &amp;#x3C;tool&gt;:&amp;#x3C;model&gt;:&amp;#x3C;profile&gt;&lt;/code&gt;. A work package with no deliverable by design: &lt;code dir=&quot;auto&quot;&gt;--attest-no-implementation &amp;#x3C;WP&gt; --attest-reason &quot;&amp;#x3C;why&gt;&quot;&lt;/code&gt; (&lt;a href=&quot;/adr/4.x/2026-10-04-5-approval-stamp-bounds-the-approved-claim/&quot;&gt;ADR 2026-10-04-5, Amendment 2026-10-29&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;accept --mode pr&lt;/code&gt; lands a Mission whose lane branches were pruned after the PR merged&lt;/strong&gt; (#6860, #6780). &lt;strong&gt;Before:&lt;/strong&gt; once lane branches were cleaned up, every approved or done work package refused &lt;code dir=&quot;auto&quot;&gt;IMPLEMENTATION_UNREADABLE&lt;/code&gt;, which no attestation lifts. &lt;strong&gt;After:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;--merge-commit&lt;/code&gt;, a lane whose branch is gone is judged on the PR’s own side of the landing merge (&lt;code dir=&quot;auto&quot;&gt;landing^1..landing&lt;/code&gt;). A squash landing, or overlapping &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;, still refuses &lt;code dir=&quot;auto&quot;&gt;IMPLEMENTATION_UNREADABLE&lt;/code&gt;; a branch that exists but cannot be read never falls back; a work package with no owned change still refuses &lt;code dir=&quot;auto&quot;&gt;IMPLEMENTATION_MISSING&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; pass &lt;code dir=&quot;auto&quot;&gt;--merge-commit &amp;#x3C;sha&gt;&lt;/code&gt; for a merge-commit landing, or restore the lane branch.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review tests can use a project-owned execution budget&lt;/strong&gt; (#6746). Set &lt;code dir=&quot;auto&quot;&gt;review.test_timeout_seconds&lt;/code&gt; to a whole number from 1 to 86400; both baseline and candidate use it, while the default remains 300 seconds. Invalid values refuse execution, and a changed budget recaptures the baseline instead of reusing its old receipt.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt; work again after you activate a directive&lt;/strong&gt; (#6510, #4226). &lt;strong&gt;Before:&lt;/strong&gt; the first &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; wrote an &lt;code dir=&quot;auto&quot;&gt;activated_directives&lt;/code&gt; list holding the synthesized directive (&lt;code dir=&quot;auto&quot;&gt;PROJECT_001&lt;/code&gt;). Synthesis then refused its own output with &lt;code dir=&quot;auto&quot;&gt;Additive-only violation … colliding_urn=&apos;directive:PROJECT_001&apos;&lt;/code&gt;, exit 1, and &lt;code dir=&quot;auto&quot;&gt;resynthesize --topic directive:PROJECT_001&lt;/code&gt; failed too. &lt;strong&gt;After:&lt;/strong&gt; directives the synthesis manifest records as its output are left out of its input and regenerate in place. They stay activated, so &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; still delivers them. A remaining collision names its source and how to recover. &lt;strong&gt;What to do:&lt;/strong&gt; nothing. Do not deactivate or rename &lt;code dir=&quot;auto&quot;&gt;PROJECT_00N&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; no longer refuses a companion tactic for naming your own test runner&lt;/strong&gt; (#6848, #6724). &lt;strong&gt;Before:&lt;/strong&gt; a project that activated a directive and wrote its companion tactic &lt;code dir=&quot;auto&quot;&gt;how-we-apply-&amp;#x3C;directive-id&gt;&lt;/code&gt; naming its own tool (&lt;code dir=&quot;auto&quot;&gt;Run pytest -q …&lt;/code&gt;) failed the neutrality gate with &lt;code dir=&quot;auto&quot;&gt;Language-specific terms detected in a generic-scoped artifact: &apos;pytest&apos;&lt;/code&gt;, exit 1, nothing promoted. The gate read the slug, which names a directive, never a language, as “generic”. &lt;strong&gt;After:&lt;/strong&gt; a companion tactic may name terms of the project’s own languages, observed in the code or declared in the interview (not from org packs); terms of any other language are still refused, so a Rust-only project cannot name &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt;. With no language known, the companion is still refused. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; re-run &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The contract lint rule &lt;code dir=&quot;auto&quot;&gt;enum-case&lt;/code&gt; accepts the pack tier &lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt;&lt;/strong&gt; (#6402). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;contracts/lint/ruleset.yaml&lt;/code&gt; allowed only snake_case and PascalCase enum values, so a contract carrying the pack tier with its single spelling, &lt;code dir=&quot;auto&quot;&gt;kernel.pack_tiers.BUILT_IN&lt;/code&gt; (ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-11-2&lt;/code&gt;), failed the lint. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt; is allowed by name. Every other hyphenated value, &lt;code dir=&quot;auto&quot;&gt;in-progress&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;Built-In&lt;/code&gt; for example, still fails, and a planted fixture proves the near-miss &lt;code dir=&quot;auto&quot;&gt;Built-In&lt;/code&gt; does.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor charter-packs&lt;/code&gt; no longer reports a team pack healthy when a graph fragment node or an asset sidecar points outside the pack&lt;/strong&gt; (#6418). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; node whose &lt;code dir=&quot;auto&quot;&gt;body_path&lt;/code&gt; was absolute or climbed out with &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt;, or an &lt;code dir=&quot;auto&quot;&gt;assets/*.asset.yaml&lt;/code&gt; sidecar whose &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt; left &lt;code dir=&quot;auto&quot;&gt;assets/&lt;/code&gt;, passed with exit 0 and &lt;code dir=&quot;auto&quot;&gt;errors: []&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; each one is named in &lt;code dir=&quot;auto&quot;&gt;org_drg.errors&lt;/code&gt; and in the human output, and the command exits 1. JSON also lists them in two always-present lists: &lt;code dir=&quot;auto&quot;&gt;org_drg.body_path_escapes&lt;/code&gt; (code &lt;code dir=&quot;auto&quot;&gt;ORG_FRAGMENT_BODY_PATH_ESCAPE&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;pack&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;node&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;kind&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;body_path&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;org_drg.asset_path_escapes&lt;/code&gt; (code &lt;code dir=&quot;auto&quot;&gt;ORG_ASSET_PATH_ESCAPE&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;pack&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;). A contained path, even to a missing file, is still accepted. Nodes found from artifact files stay with &lt;code dir=&quot;auto&quot;&gt;charter pack validate&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;charter org validate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; refuses a broken &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;ACTIVE_CHARTER_CONFIG_INVALID&lt;/code&gt; and a remedy&lt;/strong&gt; (#6557). &lt;strong&gt;Before:&lt;/strong&gt; an unparseable &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; was reported as &lt;code dir=&quot;auto&quot;&gt;Unexpected error&lt;/code&gt; with the raw parser message, and a list-rooted one as a missing bundle schema version with &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; as the remedy. &lt;strong&gt;After:&lt;/strong&gt; both exit 1 with &lt;code dir=&quot;auto&quot;&gt;Error (ACTIVE_CHARTER_CONFIG_INVALID):&lt;/code&gt;, naming the file, the problem and how to fix it, in text and in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Glossary checks are fast again after the locked event-log appends&lt;/strong&gt; (#6706). &lt;strong&gt;Before:&lt;/strong&gt; since #6606, every glossary event took the event-log lock on its own, and each lock re-read the installed package metadata (outside a git repository it also re-ran &lt;code dir=&quot;auto&quot;&gt;git rev-parse&lt;/code&gt;), so a step that recorded 100 glossary terms spent about 14 times longer writing its events. &lt;strong&gt;After:&lt;/strong&gt; the event-log lock is re-entrant within one thread, the lock record reads the package version once per process, and the glossary records a step’s term observations and clarification requests under one lock. &lt;strong&gt;Changed:&lt;/strong&gt; in interactive mode every clarification request of a step is recorded before the first question is asked, instead of one request just before each question; each answer still follows its request and carries its &lt;code dir=&quot;auto&quot;&gt;conflict_id&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty events tail&lt;/code&gt; shows a coordination-routed Mission’s work package transitions&lt;/strong&gt; (#5466). &lt;strong&gt;Before:&lt;/strong&gt; on a &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; Mission it read &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; in the repository root checkout, which holds no work package transitions, so &lt;code dir=&quot;auto&quot;&gt;--once&lt;/code&gt; printed none and a stream waited forever, with exit 0. &lt;strong&gt;After:&lt;/strong&gt; it tails the log on the Mission’s resolved status surface, the one every status writer uses. When that surface cannot be resolved (a deleted coordination branch, a coordination worktree on another branch, unreadable worktrees), it prints &lt;code dir=&quot;auto&quot;&gt;status_surface_unavailable&lt;/code&gt; on stderr and exits 1. A coordination branch with no worktree yet still shows nothing until the first status write. Restart a saved &lt;code dir=&quot;auto&quot;&gt;--from-offset&lt;/code&gt; cursor from 0.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; refuses when an approved lane carrying a canceled dependency lane’s commits cannot be read&lt;/strong&gt; (#6313). &lt;strong&gt;Before:&lt;/strong&gt; a git error while reading such a carrier lane’s history was swallowed. The canceled commits were left out of the approved claim, but no refusal was raised and nothing was named. On a squash, the canceled lines could then land on the target at exit 0. &lt;strong&gt;After:&lt;/strong&gt; the claim refuses before any branch moves, with reason &lt;code dir=&quot;auto&quot;&gt;spine_unreadable&lt;/code&gt;, naming the canceled WP, its lane and the carrier lane. That matches the mixed-lane rule. &lt;code dir=&quot;auto&quot;&gt;--attest-canceled-superseded&lt;/code&gt; does not lift it. Repair the carrier lane branch (or, when the error reports a path renamed to more than one path, keep one of those renames), then re-run.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The policy audit log reader names a malformed line instead of raising a bare &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt;&lt;/strong&gt; (#6588). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;read_audit_events&lt;/code&gt; raised &lt;code dir=&quot;auto&quot;&gt;JSONDecodeError&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt; on a malformed &lt;code dir=&quot;auto&quot;&gt;policy-audit.jsonl&lt;/code&gt; line. &lt;strong&gt;After:&lt;/strong&gt; invalid JSON, a non-object line, missing, unexpected or wrongly typed fields, and undecodable bytes raise &lt;code dir=&quot;auto&quot;&gt;PolicyAuditReadError&lt;/code&gt; (a &lt;code dir=&quot;auto&quot;&gt;GuardedReadError&lt;/code&gt;) carrying the file path and the line number. The module has no callers in &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; yet, so no user-visible command changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two synthesis runs in one worktree no longer lose synthesis records&lt;/strong&gt; (#6453). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt; rewrote &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-artifacts.yaml&lt;/code&gt;, the project overlay and the synthesis manifest with no lock. Two runs could drop each other’s entries, so a removed tactic or styleguide could return to an activation list. &lt;strong&gt;After:&lt;/strong&gt; a writing run holds one synthesis lock per worktree for all its writes. &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;, presets and the interview re-stamp the manifest under that lock; if synthesis holds it, they keep their change, skip the re-stamp and warn. A second run waits about 10 seconds, then exits 1 with &lt;code dir=&quot;auto&quot;&gt;CHARTER_SYNTHESIS_LOCK_HELD&lt;/code&gt;, names the lock file and writes nothing. &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--dry-run-evidence&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--list-topics&lt;/code&gt; take no lock.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The unreadable created-artifacts warning now says how to repair the file, and not to delete it&lt;/strong&gt; (#6455). &lt;strong&gt;Before:&lt;/strong&gt; it named the file and suggested activating artifacts one by one. &lt;strong&gt;After:&lt;/strong&gt; it also says to restore the file from version control (&lt;code dir=&quot;auto&quot;&gt;git checkout -- &amp;#x3C;path&gt;&lt;/code&gt;, or an earlier commit) or fix its YAML by hand, keeping every listed id. It warns that deleting the file makes synthesis forget which artifacts it created and add back ones you removed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A full &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; keeps the legacy &lt;code dir=&quot;auto&quot;&gt;applies&lt;/code&gt; edge of artifacts it did not regenerate&lt;/strong&gt; (#6456). &lt;strong&gt;Before:&lt;/strong&gt; a full run stripped that edge from every synthesized tactic and styleguide and reported “legacy applies edge replaced by suggests”, even where no &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edge was written, so the stored directive link was lost. &lt;strong&gt;After:&lt;/strong&gt; only artifacts the run regenerated have the edge replaced, and the notice lists only those. Which artifacts reach agents does not change.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Each decision gets exactly one opening record, and logs with two identical ones read again&lt;/strong&gt; (#4848; refs #6412). &lt;strong&gt;Before:&lt;/strong&gt; concurrent identical &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent decision open&lt;/code&gt; calls, or two retries of an interrupted open, could each append a &lt;code dir=&quot;auto&quot;&gt;DecisionPointOpened&lt;/code&gt; row; &lt;code dir=&quot;auto&quot;&gt;doctor decisions&lt;/code&gt; could not fold it and &lt;code dir=&quot;auto&quot;&gt;--repair&lt;/code&gt; refused. A resolve, defer or cancel after an interrupted open left no opening. &lt;strong&gt;After:&lt;/strong&gt; an open records one opening and waits for a concurrent open instead of failing after 10 s. A retry rewrites a missing &lt;code dir=&quot;auto&quot;&gt;DM-&amp;#x3C;id&gt;.md&lt;/code&gt;. Resolve, defer and cancel record a missing opening first. Openings equal but for recording time fold from the earliest; &lt;code dir=&quot;auto&quot;&gt;--repair&lt;/code&gt; rebuilds them without rewriting the log. A lock timeout reports &lt;code dir=&quot;auto&quot;&gt;DECISION_LOCK_TIMEOUT&lt;/code&gt;. The deferred-to-resolved rule now comes from &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; (envelopes stay with #92 / #6194). &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Recording an issue verdict on an owned Mission that still holds a legacy &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; now migrates it into the owned checkout&lt;/strong&gt; (#6354). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent issue-verdict --owned-checkout &amp;#x3C;P&gt;&lt;/code&gt; failed on such a Mission. &lt;strong&gt;After:&lt;/strong&gt; it writes &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; in the owned checkout’s Mission directory with every legacy row plus the new verdict; the legacy &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt; stays in place.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A built-in &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission can now be run through every step and accepted&lt;/strong&gt; (#6707; #4988). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; stopped a &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission at its first composed step with &lt;code dir=&quot;auto&quot;&gt;profile_hint is required when no action default exists&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; assumed every mission had software-dev work packages, so a planning mission could not be finished. &lt;strong&gt;After:&lt;/strong&gt; the four &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; actions use the existing researcher, architect and reviewer profiles. A completed &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; run with no work packages is accepted on its artifacts alone: every runtime step and review must be finished, the step artifacts must be present, and the usual clean-tree, path and clarification checks still apply. Software-dev, custom and research missions keep the work-package acceptance path.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The done terminality gate names the missing issue-matrix when the coordination branch holds none&lt;/strong&gt; (#6711). &lt;strong&gt;Before:&lt;/strong&gt; a Mission with gating references whose coordination branch had no &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; failed with “Could not evaluate issue-matrix verdict terminality: no issue matrix was ever committed at …”. &lt;strong&gt;After:&lt;/strong&gt; it fails with the same “issue-matrix.json is required before approval” message, referenced issues and regenerate remedy that a missing on-disk matrix gets. Whether it passes or fails is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete&lt;/code&gt; take &lt;code dir=&quot;auto&quot;&gt;--owned-checkout &amp;#x3C;P&gt;&lt;/code&gt;, so Op records for owned work stay out of the repository root checkout&lt;/strong&gt; (#6682). &lt;strong&gt;Before:&lt;/strong&gt; both commands wrote the Op record to the checkout they ran in, so running them from the repository root checkout for owned work left untracked &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; and glossary event files there. &lt;strong&gt;After:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;--owned-checkout &amp;#x3C;P&gt;&lt;/code&gt; the record is opened in, and closed from, &lt;code dir=&quot;auto&quot;&gt;P&lt;/code&gt; wherever the command runs; the repository root checkout and a checkout of another repository are refused before anything is written. Without the flag nothing changes. An Op whose record is already in another checkout is still closed in that checkout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent tasks move-task --to for_review --json&lt;/code&gt; prints one JSON document on stdout, even when spec-kitty’s own bookkeeping is dirty&lt;/strong&gt; (#6651). &lt;strong&gt;Before:&lt;/strong&gt; when &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; was left uncommitted, as &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; leaves them right before this step, the readiness check printed &lt;code dir=&quot;auto&quot;&gt;Note: 2 unrelated dirty file(s) ignored (not owned by WP01)&lt;/code&gt; to stdout ahead of the JSON, so &lt;code dir=&quot;auto&quot;&gt;json.load&lt;/code&gt; on the output failed with &lt;code dir=&quot;auto&quot;&gt;Expecting value: line 1 column 1&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the note is a human-mode aside only; &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output is the JSON document alone, and the move itself is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Running &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; from the repository root checkout on a mission created with &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; no longer leaves untracked &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; and glossary event files there&lt;/strong&gt; (#6691; #6682). &lt;strong&gt;Before:&lt;/strong&gt; the Op records and the glossary event logs of an owned mission were written to the root checkout whenever the command ran from it, so the root checkout showed new untracked files after every step. &lt;strong&gt;After:&lt;/strong&gt; they are written to the owned checkout, whichever checkout the command runs from; missions without an owned checkout are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An approval keeps the review text you pass with &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt;&lt;/strong&gt; (#6652). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task --to approved --review-feedback-file &amp;#x3C;file&gt;&lt;/code&gt; checked that the file existed, then wrote a review-cycle record holding only &lt;code dir=&quot;auto&quot;&gt;Approved by &amp;#x3C;reviewer&gt;: &amp;#x3C;reference&gt;&lt;/code&gt;, threw the file’s content away and still reported &lt;code dir=&quot;auto&quot;&gt;verdict_durably_persisted: true&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the record holds that line followed by the file’s content, checked by the same provenance guard a rejection’s file goes through. When no new record is written (the work package already has an approval record, as on an &lt;code dir=&quot;auto&quot;&gt;approved -&gt; done&lt;/code&gt; move, or the move is an arbiter override), or the file is empty, a warning on stderr says the file was not recorded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;reproduction_command&lt;/code&gt; in an approval’s review-cycle record replays the same reviewer&lt;/strong&gt; (#6654). &lt;strong&gt;Before:&lt;/strong&gt; the reviewer was written unquoted, so a name such as &lt;code dir=&quot;auto&quot;&gt;Jane Doe (model-x)&lt;/code&gt; made the command a shell syntax error, or split it into several &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt; words. &lt;strong&gt;After:&lt;/strong&gt; every argument is shell-quoted.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An unreadable synthesis manifest no longer hands agents the synthesized tactics of an inactive directive&lt;/strong&gt; (#6454). &lt;strong&gt;Before:&lt;/strong&gt; when &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesis-manifest.yaml&lt;/code&gt; could not be read, &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; treated every synthesized &lt;code dir=&quot;auto&quot;&gt;how-we-apply-*&lt;/code&gt; tactic as a root and delivered it even while its directive was deactivated, with exit 0 and no warning. &lt;strong&gt;After:&lt;/strong&gt; the membership is read from &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-artifacts.yaml&lt;/code&gt; instead, so such a tactic still reaches agents only through its active directive. When that record is missing, unreadable or lists no tactic, &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; exits 1 with &lt;code dir=&quot;auto&quot;&gt;SYNTHESIS_MEMBERSHIP_UNREADABLE&lt;/code&gt; and tells you to restore the manifest from version control. A missing manifest still means nothing was synthesized, but a dangling manifest symlink counts as unreadable.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter list&lt;/code&gt; shows an org pack’s required ids as in force when the project has no allow list for that kind&lt;/strong&gt; (#6417). &lt;strong&gt;Before:&lt;/strong&gt; with no allow list (for example no &lt;code dir=&quot;auto&quot;&gt;activated_directives&lt;/code&gt;), a &lt;code dir=&quot;auto&quot;&gt;required_&amp;#x3C;kind&gt;&lt;/code&gt; entry was in force, but &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt; only printed the absent-key label. &lt;strong&gt;After:&lt;/strong&gt; the &lt;em&gt;Activated&lt;/em&gt; cell names each such id as &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;id&gt; — in force: required by &apos;&amp;#x3C;pack&gt;&apos;&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; adds &lt;code dir=&quot;auto&quot;&gt;required_in_force: {&amp;#x3C;plural&gt;: [{id, packs}]}&lt;/code&gt;. A skill row reads &lt;code dir=&quot;auto&quot;&gt;(Org-required only — no explicit activation)&lt;/code&gt;. An unreadable required floor tells you to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; and adds &lt;code dir=&quot;auto&quot;&gt;required_floor_unreadable: [&amp;#x3C;plural&gt;]&lt;/code&gt;. A kind with an allow list still reports omitted ids as &lt;code dir=&quot;auto&quot;&gt;required_not_in_force&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Concurrent commands can no longer interleave or tear event log lines&lt;/strong&gt; (#6606). &lt;strong&gt;Before:&lt;/strong&gt; the run journal, &lt;code dir=&quot;auto&quot;&gt;decisions.events.jsonl&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission-events.jsonl&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; logs, the policy audit, the archive registry and the encoding provenance log were appended with no lock. Writers could interleave rows, and a cut-short write left a torn last line. A torn &lt;code dir=&quot;auto&quot;&gt;decisions.events.jsonl&lt;/code&gt; is committed and reaches other clones. &lt;strong&gt;After:&lt;/strong&gt; each append takes one lock per log, shared by all worktrees, and writes the row whole. A log with a torn last line is refused. When &lt;code dir=&quot;auto&quot;&gt;git&lt;/code&gt; cannot run, appends refuse with &lt;code dir=&quot;auto&quot;&gt;EVENT_LOG_LOCK_UNAVAILABLE&lt;/code&gt;. Each refusal ends with &lt;code dir=&quot;auto&quot;&gt;Error code: &amp;#x3C;CODE&gt;.&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; on &lt;code dir=&quot;auto&quot;&gt;EVENT_LOG_TORN_TAIL&lt;/code&gt;, back up the named log and cut it to its last newline. Until then the run journal stops &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; for that run; glossary logs repair themselves.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer fills an empty activation list with every artifact&lt;/strong&gt; (#6629). &lt;strong&gt;Before:&lt;/strong&gt; with interview selections but no &lt;code dir=&quot;auto&quot;&gt;activated_&amp;#x3C;kind&gt;&lt;/code&gt; key, the upgrade wrote all 38 directives and 14 paradigms into the list. &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; then wanted a tactic per directive, skipped the fresh-project seed, and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; was blocked (&lt;code dir=&quot;auto&quot;&gt;synthesized_drg missing&lt;/code&gt;). &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_promote_interview_selections&lt;/code&gt; replaces that step. It leaves an absent key absent, adds missing selections only where the old step never ran, writes to the one activation target (the ledger, or the legacy file before the keys move; #6549), and runs once. &lt;strong&gt;What to do:&lt;/strong&gt; a list an earlier build filled is kept, with a warning; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter interview --narrow-activation&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --only&lt;/code&gt; to keep only your selections.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now leaves every leftover &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; folder untouched&lt;/strong&gt; (#6669). &lt;strong&gt;Before:&lt;/strong&gt; a branch switch left an untracked &lt;code dir=&quot;auto&quot;&gt;tasks/WP01-*.md&lt;/code&gt;, event log, &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; or legacy &lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;lane&gt;/&lt;/code&gt; file in &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt;, the upgrade treated the folder as a Mission: it minted a &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; into a new &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, synthesized a &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, moved or rewrote the work package files, and auto-committed the result. &lt;strong&gt;After:&lt;/strong&gt; in a project where git tracks Mission files, a folder with no &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; that git does not know is left untouched and named once; real Missions, including committed legacy Missions with a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, are repaired as before. &lt;strong&gt;Accepted cost:&lt;/strong&gt; a committed folder holding only &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; now counts as residue and is no longer repaired. &lt;strong&gt;What to do:&lt;/strong&gt; add a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, or remove it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Recording a review verdict no longer erases which profile ran the review&lt;/strong&gt; (#6630). &lt;strong&gt;Before:&lt;/strong&gt; after &lt;code dir=&quot;auto&quot;&gt;agent action review --profile &amp;#x3C;id&gt;&lt;/code&gt;, recording the verdict with &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task --to approved&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;--to done&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;--to canceled --agent &amp;#x3C;same agent&gt;&lt;/code&gt;) without &lt;code dir=&quot;auto&quot;&gt;--profile&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--model&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;--invocation-id&lt;/code&gt; wrote an empty binding over the claim’s, so &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; showed &lt;code dir=&quot;auto&quot;&gt;agent_profile: __resolved_profile_absent__&lt;/code&gt; for every reviewed work package. &lt;strong&gt;After:&lt;/strong&gt; a verdict without those options records no binding, and the review claim’s profile and version stay in the status snapshot. A verdict that passes one of them, or hands the work package to a different &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt;, still records it, and a real pick-up still clears the previous actor’s binding. Status files already written keep the value they hold. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; no longer trip over the decision lock file&lt;/strong&gt; (#6628). &lt;strong&gt;Before:&lt;/strong&gt; a Mission that opened or resolved a Decision Moment kept &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/decisions/index.json.lock&lt;/code&gt; on disk, untracked, by design (#5925). &lt;code dir=&quot;auto&quot;&gt;agent mission record-analysis&lt;/code&gt; then refused with &lt;code dir=&quot;auto&quot;&gt;DIRTY_WORKTREE&lt;/code&gt; and told you to commit it, and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; could stage it in its acceptance commit. This included the repository root of a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; Mission. &lt;strong&gt;After:&lt;/strong&gt; that exact path counts as Spec Kitty’s own bookkeeping in every dirty-tree check that consults it, and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; never commits it. A file with the same name anywhere else is still treated as a change, and the &lt;code dir=&quot;auto&quot;&gt;DIRTY_WORKTREE&lt;/code&gt; remediation now says not to commit Spec Kitty’s lock files. &lt;strong&gt;What to do:&lt;/strong&gt; nothing. If you committed the lock to get past the refusal, remove it from git with &lt;code dir=&quot;auto&quot;&gt;git rm --cached&lt;/code&gt; and keep the file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer gives leftover &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; folders a new Mission identity&lt;/strong&gt; (#6627). &lt;strong&gt;Before:&lt;/strong&gt; when a branch switch left untracked files only in &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt; (e.g. &lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt;), the &lt;code dir=&quot;auto&quot;&gt;2.0.6_consistency_sweep&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;3.2.0a4_normalize_mission_lifecycle&lt;/code&gt; steps wrote a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; with a new &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; and a &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, and the upgrade auto-committed both. &lt;strong&gt;After:&lt;/strong&gt; a folder with no Mission files (no &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt;, status log or snapshot) that git does not track as a Mission is left alone by all three steps; normalization reports it as residue. &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor cutover&lt;/code&gt; reports nothing to cut over. Legacy or uncommitted Missions with any of them are repaired as before. &lt;strong&gt;What to do:&lt;/strong&gt; if an earlier upgrade committed such files, remove that folder’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; in a follow-up commit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Status replay reads a &lt;code dir=&quot;auto&quot;&gt;not_applicable&lt;/code&gt; subtask value as &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt;&lt;/strong&gt; (#6605). &lt;strong&gt;Before:&lt;/strong&gt; an annotation whose &lt;code dir=&quot;auto&quot;&gt;subtasks&lt;/code&gt; delta carried &lt;code dir=&quot;auto&quot;&gt;not_applicable&lt;/code&gt; (the input alias of &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt;, as &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent tasks mark-status&lt;/code&gt; treat it) stopped &lt;code dir=&quot;auto&quot;&gt;materialize&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;StoreError: ... &apos;not_applicable&apos; is not a valid Lane&lt;/code&gt;. The package’s own &lt;code dir=&quot;auto&quot;&gt;skipped_subtask&lt;/code&gt; replay fixture hits this. &lt;strong&gt;After:&lt;/strong&gt; the value reads as &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt; and is written back as &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt;; any other unknown value still fails.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer reports success when a migration could not run in a worktree&lt;/strong&gt; (#5746). &lt;strong&gt;Before:&lt;/strong&gt; when a migration could not be checked or applied in one of your worktrees, &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; printed the error and still ended on “Upgrade complete!” with exit code 0 (&lt;code dir=&quot;auto&quot;&gt;&quot;status&quot;: &quot;success&quot;&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;). &lt;strong&gt;After:&lt;/strong&gt; the run ends on “Upgrade failed.” with exit code 1 and the error listed; the main checkout’s upgrade is kept, and nothing is auto-committed in that worktree. The same holds for any other error &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; lists that no specific failure explains: an error never sits above a success line again. &lt;strong&gt;What to do:&lt;/strong&gt; fix the cause the error names and run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Op records stay in the checkout you run in, and a protected branch refuses before writing&lt;/strong&gt; (#6564). &lt;strong&gt;Before:&lt;/strong&gt; from a linked worktree, &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;profile-invocation complete&lt;/code&gt; wrote the Op record and its glossary events into the repository root checkout, often on its protected branch, then refused the commit, leaving untracked &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; files. &lt;strong&gt;After:&lt;/strong&gt; the record is written and committed in the checkout the command runs in; &lt;code dir=&quot;auto&quot;&gt;invocations list&lt;/code&gt; reads that checkout, and &lt;code dir=&quot;auto&quot;&gt;--invocation-id&lt;/code&gt; works from any checkout. Where the commit would be refused, both commands stop first with exit 1 and &lt;code dir=&quot;auto&quot;&gt;OP_WRITE_PROTECTED_BRANCH&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;OP_WRITE_PROTECTION_CONFIG_INVALID&lt;/code&gt; for unreadable &lt;code dir=&quot;auto&quot;&gt;protection:&lt;/code&gt; settings). &lt;strong&gt;What to do:&lt;/strong&gt; run them from a branch that is not protected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;safe-commit&lt;/code&gt; commits an explicitly named file under a gitignored directory when it is the only path named&lt;/strong&gt; (#6649). &lt;strong&gt;Before:&lt;/strong&gt; naming only such a file reported &lt;code dir=&quot;auto&quot;&gt;&quot;result&quot;: &quot;success&quot;&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;&quot;committed&quot;: false&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;No requested changes to commit&lt;/code&gt;) and exit 0, while naming the same file beside another changed path committed it. &lt;strong&gt;After:&lt;/strong&gt; the file is committed in both cases. A directory argument still expands to changed, non-ignored files only. A file inside an ignored nested git repository now exits 1 (&lt;code dir=&quot;auto&quot;&gt;empty changeset&lt;/code&gt;) instead of reporting success.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Upgrade no longer swaps the research task prompt template for an older copy&lt;/strong&gt; (#5280). &lt;strong&gt;Before:&lt;/strong&gt; with a &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/research/&lt;/code&gt; folder, &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; copied an old research &lt;code dir=&quot;auto&quot;&gt;task-prompt-template.md&lt;/code&gt; in, and the 2.0.6 cleanup moved it to &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/&lt;/code&gt;, where it beat the shipped template. That copy lacks &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;authoritative_surface&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;execution_mode&lt;/code&gt; and the “Load Agent Profile” step. Older pre-2.x upgrades did the same for the documentation templates. &lt;strong&gt;After:&lt;/strong&gt; upgrade removes those copies (see Upgrade Notes), and built-in missions read the shipped templates. The 2.0.6 cleanup and &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate&lt;/code&gt; compare each file under &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;type&gt;/&lt;/code&gt; with the shipped one (#6548): an equal copy is removed, a different one stays put. Neither moves to &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; refuses a committed or unreadable review lock before claiming the work package&lt;/strong&gt; (#6386). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/review-lock.json&lt;/code&gt; was read only after the review claim had moved the work package to &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; and committed &lt;code dir=&quot;auto&quot;&gt;Start review&lt;/code&gt;. A lock committed on the lane branch, such as &lt;code dir=&quot;auto&quot;&gt;{}&lt;/code&gt;, stopped the command with &lt;code dir=&quot;auto&quot;&gt;ReviewLock.__init__() missing 5 required positional arguments&lt;/code&gt;, every re-run added another commit, and releasing a committed lock left a deletion that blocked &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the lock is checked first. A lock git tracks is refused with &lt;code dir=&quot;auto&quot;&gt;REVIEW_LOCK_COMMITTED&lt;/code&gt;, whatever it holds; an unreadable one with &lt;code dir=&quot;auto&quot;&gt;REVIEW_LOCK_UNREADABLE&lt;/code&gt;. Nothing changes, and a workspace created by &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; excludes &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/&lt;/code&gt; from git. &lt;strong&gt;What to do:&lt;/strong&gt; follow the printed remedy, then re-run the review.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Upgrade guidance now links to the live install and upgrade guide&lt;/strong&gt; (#6468). &lt;strong&gt;Before:&lt;/strong&gt; when Spec Kitty could not detect how it was installed, the upgrade hint and the reinstall note pointed at two different pages on &lt;code dir=&quot;auto&quot;&gt;spec-kitty.dev&lt;/code&gt;, a domain Spec Kitty does not own, so both links were dead and whoever registered the domain would have chosen what they showed. &lt;strong&gt;After:&lt;/strong&gt; both print &lt;code dir=&quot;auto&quot;&gt;https://docs.spec-kitty.ai/guides/how-to/installation/install-and-upgrade&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Spec Kitty’s schema identifiers move to &lt;code dir=&quot;auto&quot;&gt;spec-kitty.ai&lt;/code&gt;&lt;/strong&gt; (#6468). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;$id&lt;/code&gt; of the 13 doctrine schemas and of the skills manifest schema began &lt;code dir=&quot;auto&quot;&gt;https://spec-kitty.dev/schemas/&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; they begin &lt;code dir=&quot;auto&quot;&gt;https://spec-kitty.ai/schemas/&lt;/code&gt;. Nothing fetches these identifiers today. &lt;strong&gt;What to do:&lt;/strong&gt; if a tool or editor setting of yours maps a Spec Kitty schema by its &lt;code dir=&quot;auto&quot;&gt;$id&lt;/code&gt;, update the prefix.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A read-only home folder no longer stops &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; before your command runs&lt;/strong&gt; (#6473). &lt;strong&gt;Before:&lt;/strong&gt; at startup &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; installs its runtime assets and global agent commands and skills in your home folder. In a sandbox that only allows workspace writes or a container with a read-only home, an empty home crashed with a Python traceback, and a set-up home with something to refresh exited 1, for every command except &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;migrate&lt;/code&gt; and the agent hooks. &lt;strong&gt;After:&lt;/strong&gt; the command runs and prints one warning naming what could not be updated (until then it uses the runtime templates already installed, or the packaged ones); under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; the warning is silent so stdout stays one JSON object. Commands that need those assets, such as &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;, still fail with a named error. &lt;strong&gt;What to do:&lt;/strong&gt; run any &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; command once where the home folder is writable to install the assets.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; runs the charter-pack cutover before every other pending migration again&lt;/strong&gt; (#6582). &lt;strong&gt;Before:&lt;/strong&gt; since the migration ledger landed, the cutover ran at its &lt;code dir=&quot;auto&quot;&gt;4.0.0rc6&lt;/code&gt; version slot, so about forty older migrations ran first on a pre-cutover project, and a cutover that refused a collision between the retired project layer and &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt; had already let them write &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; merge-driver lines. &lt;strong&gt;After:&lt;/strong&gt; the cutover runs right after the two steps it depends on: the ledger backfill and the charter-bundle upgrade from schema v1. A refused collision now leaves the project as it was, apart from the backfill’s ledger records (&lt;a href=&quot;/adr/4.x/2026-10-17-1-explicit-migration-ledger/&quot;&gt;ADR 2026-10-17-1, Amendment 2026-10-22&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; no longer ships a canceled work package’s change that an approved one only partly reworked&lt;/strong&gt; (#6309). &lt;strong&gt;Before:&lt;/strong&gt; a canceled change counted as gone as soon as one of its added lines was missing, so an approved rework that kept two of three canceled lines, left a canceled deletion standing under a later edit, or renamed the file passed the gate and landed the rejected work. &lt;strong&gt;After:&lt;/strong&gt; the gate judges each line by who wrote it: a kept non-blank canceled line, or a canceled deletion still in effect, fails consolidation, and a renamed file is checked and named at its new path. Blank and punctuation-only lines are ignored, and an approved rewrite of the canceled change itself still passes. A rework that keeps only a canceled signature line now fails too: rewrite that line as well.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty --help&lt;/code&gt; no longer reads the metadata of every installed package&lt;/strong&gt; (#6584). &lt;strong&gt;Before:&lt;/strong&gt; importing the CLI resolved its own version at once, through a scan of every installed distribution’s metadata, so &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; and every other command paid for it even when no version was printed; that cost tipped the nightly &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; start-up budget over its limit. &lt;strong&gt;After:&lt;/strong&gt; the version is resolved the first time something prints or records it, such as &lt;code dir=&quot;auto&quot;&gt;--version&lt;/code&gt; or a &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; payload’s &lt;code dir=&quot;auto&quot;&gt;spec_kitty_version&lt;/code&gt;, and reports the same value. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty --help&lt;/code&gt; and every other command no longer import an HTTP client or a charset detector at start-up&lt;/strong&gt; (#6638). &lt;strong&gt;Before:&lt;/strong&gt; the upgrade-nag provider imported &lt;code dir=&quot;auto&quot;&gt;httpx&lt;/code&gt; and the encoding-recovery reader imported &lt;code dir=&quot;auto&quot;&gt;charset_normalizer&lt;/code&gt; as soon as the CLI loaded, about 90 ms (&lt;code dir=&quot;auto&quot;&gt;httpx&lt;/code&gt; about 70 ms, &lt;code dir=&quot;auto&quot;&gt;charset_normalizer&lt;/code&gt; about 18 ms) that no command needs until it checks PyPI or reads a mis-encoded file. With that cost the nightly &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; start-up budget went over its limit again. &lt;strong&gt;After:&lt;/strong&gt; each is imported when it is first used, with the same behavior, and a per-PR architectural gate fails any change that brings them, &lt;code dir=&quot;auto&quot;&gt;jsonschema&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt; back onto the &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; import path. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Spec Kitty no longer hides the files your team commits in agent folders&lt;/strong&gt; (#6474). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; ignored whole agent folders (&lt;code dir=&quot;auto&quot;&gt;.claude/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kiro/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; and more) for every agent, so a new &lt;code dir=&quot;auto&quot;&gt;.claude/settings.json&lt;/code&gt; never reached teammates. &lt;strong&gt;After:&lt;/strong&gt; one &lt;code dir=&quot;auto&quot;&gt;# &gt;&gt;&gt; Spec Kitty agent files&lt;/code&gt; block in &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; lists only what Spec Kitty generates for the configured agents (&lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; commands, its own and pack skill folders, whole session files), plus credential files (&lt;code dir=&quot;auto&quot;&gt;.codex/auth.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.gemini/.env&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.claude/settings.local.json&lt;/code&gt; …) and the &lt;code dir=&quot;auto&quot;&gt;.vibe/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.pi/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.letta/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.github/copilot/&lt;/code&gt; state folders for every agent; &lt;code dir=&quot;auto&quot;&gt;agent config&lt;/code&gt;, pack-skill changes and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; keep it current. &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; removes the whole-folder lines Spec Kitty wrote, keeps yours with a warning, and lists files git now shows. &lt;strong&gt;What to do:&lt;/strong&gt; commit the ones your team shares.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A later upgrade no longer writes the whole-folder agent ignores back&lt;/strong&gt; (#6589). &lt;strong&gt;Before:&lt;/strong&gt; once the 4.0.0rc8 upgrade had narrowed &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;, a later &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; could run two older steps again, and they re-added &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; (hiding your team’s own skills) and the &lt;code dir=&quot;auto&quot;&gt;.cursor/commands/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.cursor/skills/&lt;/code&gt; rows. &lt;strong&gt;After:&lt;/strong&gt; both older steps are recorded as superseded and change nothing, so the narrowed rows stay. A project upgrading from before 3.2.5 no longer gets &lt;code dir=&quot;auto&quot;&gt;.kittify/skills-manifest.json&lt;/code&gt; added to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;, and Spec Kitty command skill copies it committed stay tracked. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; to stop tracking those copies, run &lt;code dir=&quot;auto&quot;&gt;git rm -r --cached --ignore-unmatch -- &apos;.agents/skills/spec-kitty[-.]*&apos; &apos;.agents/skills/spk-*&apos; .kittify/skills-manifest.json&lt;/code&gt; (check first that none of your own skills match) and commit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; no longer edits a committed &lt;code dir=&quot;auto&quot;&gt;.claude/settings.json&lt;/code&gt;&lt;/strong&gt; (#6474). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; merged its &lt;code dir=&quot;auto&quot;&gt;SessionStart&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;Stop&lt;/code&gt; hooks into the file even when your team had committed it. &lt;strong&gt;After:&lt;/strong&gt; a tracked settings file is left alone and &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; prints the two hooks to add yourself (&lt;code dir=&quot;auto&quot;&gt;spec-kitty session-start&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty session-stop&lt;/code&gt;). An untracked or missing file still gets them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An empty agent list no longer means every agent&lt;/strong&gt; (#6494). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;available: []&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; (for example after &lt;code dir=&quot;auto&quot;&gt;agent config remove&lt;/code&gt; of every agent) made migrations, &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; and surface repair act on every agent folder. &lt;strong&gt;After:&lt;/strong&gt; an explicit empty list means no Spec Kitty-managed agents, and an unreadable &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; stops these commands with an error that names &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config list&lt;/code&gt;, instead of falling back to every agent. A config with no agent list at all still covers every agent, as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A branch name in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; that starts with &lt;code dir=&quot;auto&quot;&gt;-&lt;/code&gt; can no longer run a git option&lt;/strong&gt; (#4304). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; created a missing coordination or mission branch with &lt;code dir=&quot;auto&quot;&gt;git branch &amp;#x3C;name&gt; &amp;#x3C;target&gt;&lt;/code&gt;, so a hand-edited &lt;code dir=&quot;auto&quot;&gt;&quot;coordination_branch&quot;: &quot;-f&quot;&lt;/code&gt; ran &lt;code dir=&quot;auto&quot;&gt;git branch -f main&lt;/code&gt; and force-reset the local &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt; passed both branch names to &lt;code dir=&quot;auto&quot;&gt;git diff&lt;/code&gt; the same way, so a name such as &lt;code dir=&quot;auto&quot;&gt;--output=&amp;#x3C;path&gt;&lt;/code&gt; could write a file. &lt;strong&gt;After:&lt;/strong&gt; both commands mark the end of git options before the names, so git rejects such a name as an invalid branch instead of running it. Valid branch names behave as before. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Four text parsers no longer slow down sharply on long, unusual lines&lt;/strong&gt; (#4696). &lt;strong&gt;Before:&lt;/strong&gt; four regular expressions took time proportional to the square of the line length on some inputs: the session-presence header check in agent rules files such as &lt;code dir=&quot;auto&quot;&gt;CLAUDE.md&lt;/code&gt;, the charter-context &lt;code dir=&quot;auto&quot;&gt;### &amp;#x3C;heading&gt;&lt;/code&gt; split, and the trace-section id and issue-ref parsing in the merge drivers. A single pathological line of about 100 KB could hold a command for a minute or more. &lt;strong&gt;After:&lt;/strong&gt; each is a single linear pass that returns the same result for every input. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; on a project &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; just set up commits nothing&lt;/strong&gt; (#6416). &lt;strong&gt;Before:&lt;/strong&gt; the first upgrade after &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; auto-committed two files: &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; gained &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**/issue-matrix.md merge=spec-kitty-issue-matrix&lt;/code&gt;, the inert line the historical &lt;code dir=&quot;auto&quot;&gt;3.2.6_gate_artifact_merge_drivers&lt;/code&gt; step still seeds and &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; never wrote, and &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; had &lt;code dir=&quot;auto&quot;&gt;last_upgraded_at:&lt;/code&gt; rewritten as &lt;code dir=&quot;auto&quot;&gt;last_upgraded_at: null&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; writes every merge-driver line an upgrade seeds, from the one list both read, so a new project’s &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; now also carries that inert &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; line (no file matches it), and the upgrade’s schema stamp skips the rewrite when no value changes. Already-initialized projects are unaffected: their first upgrade already committed both changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; refuses a broken &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; instead of overwriting packs with the minimal seed&lt;/strong&gt; (#6415). &lt;strong&gt;Before:&lt;/strong&gt; if &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; did not parse, was empty or was not a mapping, &lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt; (plain, &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;) wrote the built-in-only seed and exited 0. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;resynthesize&lt;/code&gt; refuse with &lt;code dir=&quot;auto&quot;&gt;ACTIVE_CHARTER_CONFIG_INVALID&lt;/code&gt; before writing. The message names the file, the error and the remedy; &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; emits the failure envelope. &lt;strong&gt;What to do:&lt;/strong&gt; fix the YAML, or re-run &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate --from-interview&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; and the preflight no longer suggest &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; for a stale &lt;code dir=&quot;auto&quot;&gt;synthesized_drg&lt;/code&gt; when &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; is missing or unparseable; they show the upstream remedy, or none for a broken file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A deactivated charter artifact stays deactivated&lt;/strong&gt; (#6496, spec-kitty/spec-kitty-charter#63). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; only removed the id from an allow list, so the activation cascade, the one-time rc6 reset, the charter interview and org-required promotion could quietly put it back, and a kind with no allow list could not be deactivated at all. &lt;strong&gt;After:&lt;/strong&gt; the exclusion is stored on its own in the activation ledger, and only an explicit &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; clears it. The core side of spec-kitty/spec-kitty-charter#62, spec-kitty/spec-kitty-charter#64, spec-kitty/spec-kitty-charter#66 and spec-kitty/spec-kitty-charter#67.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The CLI writes slash-command files into your home folder only for the agents your project uses&lt;/strong&gt; (#6470). &lt;strong&gt;Before:&lt;/strong&gt; every CLI run wrote command files for every slash-command agent, configured or not, even outside a project. &lt;strong&gt;After:&lt;/strong&gt; it writes only for the slash-command agents configured in the current project and nothing outside a project; &lt;code dir=&quot;auto&quot;&gt;agent config add&lt;/code&gt; writes the added agent at once. Global skills fan-out is still open (#3048).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Generated skills keep their frontmatter inside the Agent Skills specification, and CI checks it&lt;/strong&gt; (#6475). &lt;strong&gt;Before:&lt;/strong&gt; shared-root skills carried Claude-only keys such as &lt;code dir=&quot;auto&quot;&gt;argument-hint&lt;/code&gt; at the top level, and pack skills had no name or description limit. &lt;strong&gt;After:&lt;/strong&gt; in &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; only specification fields stay top level and other keys move under &lt;code dir=&quot;auto&quot;&gt;metadata&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;.claude/skills/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.qwen/skills/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kilocode/skills/&lt;/code&gt; keep them); pack skills over 64 characters of name or 1024 of description are refused; the always-on &lt;code dir=&quot;auto&quot;&gt;agent-skills&lt;/code&gt; CI job validates every generated and shipped skill with &lt;code dir=&quot;auto&quot;&gt;skills-ref==0.1.1&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; outside a git repository can no longer report a half-applied migration as skipped&lt;/strong&gt; (#6539). &lt;strong&gt;Before:&lt;/strong&gt; the runner turned any “not inside a git repository” error into a silent skip, even one raised by &lt;code dir=&quot;auto&quot;&gt;apply()&lt;/code&gt; after the migration had written files, and &lt;code dir=&quot;auto&quot;&gt;upgrade --dry-run --verbose&lt;/code&gt; crashed outside git. &lt;strong&gt;After:&lt;/strong&gt; a migration that needs a repository declares &lt;code dir=&quot;auto&quot;&gt;requires_git_repository&lt;/code&gt; and is skipped before any step runs, with nothing recorded; the same error from &lt;code dir=&quot;auto&quot;&gt;apply()&lt;/code&gt;, or a repository probe that cannot run, is a recorded failure that the next run retries; the preview reports these migrations instead of crashing. &lt;code dir=&quot;auto&quot;&gt;3.2.0rc35_unified_bundle&lt;/code&gt; declares the flag, so projects that recorded it see a one-time, audit-only content-hash drift in &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate ledger&lt;/code&gt; (ADR 2026-10-17-1 note); nothing re-runs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An aborted &lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; no longer leaves &lt;code dir=&quot;auto&quot;&gt;languages:&lt;/code&gt; written&lt;/strong&gt; (#6542). &lt;strong&gt;Before:&lt;/strong&gt; the interview wrote the settled language list to &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; before asking its questions, so an abort or a failed answers write left the setting behind. &lt;strong&gt;After:&lt;/strong&gt; the list is still proposed first but written only after the answers and before selection promotion, so an interview that stops early writes neither; a failed languages write exits non-zero and says the answers were saved. The never-overwrite rule and the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; keys are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reading every Mission’s status no longer slows down quadratically as Missions accumulate&lt;/strong&gt; (#6517). &lt;strong&gt;Before:&lt;/strong&gt; each Mission status read resolved its handle three to four times, and every resolution re-read the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; of every Mission in &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;, so a project-wide read of 639 Missions parsed about 1.4 million &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; files and the nightly corpus run took 160 s against its 120 s bound. &lt;strong&gt;After:&lt;/strong&gt; a handle that is a Mission’s exact directory name reads only that Mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;; every other handle form (mission id, mid8, numeric prefix, bare slug) still searches all Missions and still refuses an ambiguous handle. The same read of 639 Missions takes about 30 s. One difference: a Mission whose &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; holds a non-string &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; no longer breaks resolving other Missions by their directory names.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The first ledger-era upgrade no longer replays older setup steps&lt;/strong&gt; (#6431, #6369). &lt;strong&gt;Before:&lt;/strong&gt; for a project set up before the migration ledger, every step up to its recorded version ran again, since pre-ledger &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; recorded none. It rewrote Mission &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, undid a forced lane transition and auto-committed. &lt;code dir=&quot;auto&quot;&gt;upgrade --target X&lt;/code&gt; applied steps above &lt;code dir=&quot;auto&quot;&gt;X&lt;/code&gt;. An &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; outside git marked per-clone setup done, so &lt;code dir=&quot;auto&quot;&gt;git init&lt;/code&gt; never got it. &lt;strong&gt;After:&lt;/strong&gt; adopting the ledger marks done every step below both 4.0.0rc8 and the recorded version. Skipped or failed steps are left alone; per-clone steps count only where their effect exists in a git repo. &lt;code dir=&quot;auto&quot;&gt;upgrade --dry-run&lt;/code&gt; lists only what the real run applies, and &lt;code dir=&quot;auto&quot;&gt;--target X&lt;/code&gt; selects nothing above &lt;code dir=&quot;auto&quot;&gt;X&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; nothing. The first upgrade still commits once, to move the record into &lt;code dir=&quot;auto&quot;&gt;.kittify/migration-ledger.jsonl&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; no longer prints &lt;code dir=&quot;auto&quot;&gt;collisions: none&lt;/code&gt; when an org pack overrode a built-in&lt;/strong&gt; (#5777). &lt;strong&gt;Before:&lt;/strong&gt; its org-layer section printed &lt;code dir=&quot;auto&quot;&gt;collisions: none&lt;/code&gt; after every org-layer merge that succeeded, even when a permitted same-kind org override of a built-in node had been recorded. &lt;strong&gt;After:&lt;/strong&gt; it reports how many built-ins an org pack overrode (for example &lt;code dir=&quot;auto&quot;&gt;collisions: 1 permitted org override of a built-in (see the sanction report)&lt;/code&gt;), and prints &lt;code dir=&quot;auto&quot;&gt;collisions: none&lt;/code&gt; only when there are none.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;LICENSE&lt;/code&gt; carries GitHub’s original copyright notice again&lt;/strong&gt; (#6478). &lt;strong&gt;Before:&lt;/strong&gt; an August 2026 edit replaced the upstream &lt;code dir=&quot;auto&quot;&gt;Copyright GitHub, Inc.&lt;/code&gt; line with the Spec Kitty, Inc. line, so the wheel shipped without the notice the Spec Kit MIT license requires. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;LICENSE&lt;/code&gt; keeps both lines, and the charter’s Attribution section says so instead of claiming “All Rights Reserved” under MIT. Counsel confirms the final wording before the 4.0.0 release.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The bulk-edit review gate no longer blocks a work package on files it only created&lt;/strong&gt; (#6568). &lt;strong&gt;Before:&lt;/strong&gt; the gate read &lt;code dir=&quot;auto&quot;&gt;git diff --name-only&lt;/code&gt;, so an added file was judged as an edit and any work package that added files was rejected; on a coord topology the Mission’s own status files blocked their review, and templates, stylesheets and webfonts blocked as unclassified. &lt;strong&gt;After:&lt;/strong&gt; it reads &lt;code dir=&quot;auto&quot;&gt;--name-status&lt;/code&gt;: a created file passes as a note, while edits, deletions, renames and cross-mission writes are still judged. The &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;&lt;/code&gt; runtime-state exemption outranks map exceptions, and the output lists what blocks and summarizes the rest. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; an &lt;code dir=&quot;auto&quot;&gt;exceptions:&lt;/code&gt; entry still wins. Details: &lt;code dir=&quot;auto&quot;&gt;docs/api/bulk-edit-gate.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Glossary event records no longer carry placeholder values&lt;/strong&gt; (#6399). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;SemanticCheckEvaluated&lt;/code&gt; event emitted before the generation gate had resolved strictness recorded &lt;code dir=&quot;auto&quot;&gt;effective_strictness&lt;/code&gt; as the string &lt;code dir=&quot;auto&quot;&gt;&quot;None&quot;&lt;/code&gt;, a &lt;code dir=&quot;auto&quot;&gt;GlossaryClarificationRequested&lt;/code&gt; event with no preceding semantic check recorded an empty &lt;code dir=&quot;auto&quot;&gt;semantic_check_event_id&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty glossary resolve&lt;/code&gt; recorded an empty provenance timestamp. &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; 11.0.0 refuses all three. &lt;strong&gt;After:&lt;/strong&gt; an unresolved strictness is recorded as &lt;code dir=&quot;auto&quot;&gt;&quot;medium&quot;&lt;/code&gt;, the default it was already treated as, the semantic-check reference is left out when there was none, and &lt;code dir=&quot;auto&quot;&gt;glossary resolve&lt;/code&gt; records the time of the resolution. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; lines already written are not rewritten.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Closing an Op no longer commits its record into a repository that does not keep Op records&lt;/strong&gt; (#6410).
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops --close-stale&lt;/code&gt; force-committed &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;id&gt;.jsonl&lt;/code&gt; (or the &lt;code dir=&quot;auto&quot;&gt;op-closures.jsonl&lt;/code&gt; spine) onto whatever branch was checked out. They did so even when the repository gitignored &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; or never tracked Op records, so an unrelated &lt;code dir=&quot;auto&quot;&gt;op(&amp;#x3C;profile&gt;): &amp;#x3C;action&gt;&lt;/code&gt; commit rode into every issue-branch PR. The refusal warning on protected &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; also advised an override that agents must not use.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;After:&lt;/strong&gt; the commit is skipped when the record matches an ignore rule, or when the primary branch tracks no Op record. The record stays on disk, still listed by &lt;code dir=&quot;auto&quot;&gt;spec-kitty invocations list&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor ops&lt;/code&gt;, and the close output says it was not committed and why. Repositories that track Op records keep the commit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What to do:&lt;/strong&gt; nothing in a repository that never tracked Op records. To stop the commit in a repository whose &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; already carries some, add &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;; that is now honored.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The Mission Status service no longer serves a &lt;code dir=&quot;auto&quot;&gt;.env&lt;/code&gt;, a key or a credential file from a Mission directory&lt;/strong&gt; (#6422). &lt;strong&gt;Before:&lt;/strong&gt; any file below &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/&lt;/code&gt;, dotfiles included, was listed and served to any local process unless its text matched one of four token patterns, so a &lt;code dir=&quot;auto&quot;&gt;.env&lt;/code&gt; holding an API key was returned. &lt;strong&gt;After:&lt;/strong&gt; eligibility denies by default: only names ending in &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.jsonl&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.yml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.csv&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;.txt&lt;/code&gt;, with no path segment starting with a dot, and, for data files, not a credential file name (&lt;code dir=&quot;auto&quot;&gt;credentials.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;secrets.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;client_secret_*.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;service-account.json&lt;/code&gt;), are listed or read; anything else is 404 and never opened. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; files under a Mission’s dot directories (&lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.gates/&lt;/code&gt;) are no longer listed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A built-in &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission no longer hard-blocks at &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt;&lt;/strong&gt; (#6388). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission returned &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;Required artifact missing: spec.md&lt;/code&gt; even with &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; committed, and named no path, because the plan mission’s expected-artifacts manifest still used its old phase names and &lt;code dir=&quot;auto&quot;&gt;goals.md&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the manifest uses the runtime step names (&lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;), a committed &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; is found, and a missing one is named. A CI check now fails when a mission’s manifest and its step contracts disagree. &lt;strong&gt;What to do:&lt;/strong&gt; nothing for new plan missions; a plan mission that wrote &lt;code dir=&quot;auto&quot;&gt;goals.md&lt;/code&gt; needs that file renamed to &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Owned-checkout status, accept and review-handoff no longer drop the owned fact&lt;/strong&gt; (#6321). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; execution-mode fallback (used only with no &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; and no frontmatter &lt;code dir=&quot;auto&quot;&gt;execution_mode&lt;/code&gt;) read the primary checkout, not the owned one. &lt;code dir=&quot;auto&quot;&gt;agent mission accept&lt;/code&gt; had no &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; flag and relied on running inside the owned checkout. The review-handoff topology renderer took no owned input. &lt;strong&gt;After:&lt;/strong&gt; the status fallback reads the owned checkout. &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; takes an explicit &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; flag. The renderer accepts the owned input, a no-op today since &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; refuse &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;. None was an acceptance-authority gap (that is #6320). Ordinary repository-root resolution is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An owned-only mission can now record issue-matrix verdicts with &lt;code dir=&quot;auto&quot;&gt;issue-verdict --owned-checkout&lt;/code&gt;&lt;/strong&gt; (#6320). &lt;strong&gt;Before:&lt;/strong&gt; an owned, PR-bound &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission that lived only in its owned checkout could not record issue-matrix verdicts — &lt;code dir=&quot;auto&quot;&gt;agent mission issue-verdict&lt;/code&gt; had no &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; option, and its fail-closed write-target gate refused a mission resolved from the repository root. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;issue-verdict&lt;/code&gt; takes &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; (and adopts an owned caller checkout) and carries the ownership fact through the write-target gate and the coordination-owned read path, so owned verdicts record. Ordinary repository-root and coordination behavior is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Five &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate&lt;/code&gt; subcommands now reject &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; instead of silently ignoring it&lt;/strong&gt; (#5294). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;backfill-provenance&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter-encoding&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;rebaseline-dossier-hashes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;rewrite-opposed-by&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;repin-hooks&lt;/code&gt; are not mission-scoped, yet each silently accepted and discarded &lt;code dir=&quot;auto&quot;&gt;--mission &amp;#x3C;handle&gt;&lt;/code&gt; and exited 0 — so an agent following Spec Kitty’s own “pass &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; to every command” instruction unknowingly ran a corpus- or repo-wide mutation it believed was scoped to one Mission. &lt;strong&gt;After:&lt;/strong&gt; those five reject &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; with an explicit, scope-neutral usage error (exit 2), reusing the #4964 refusal machinery. Every genuinely mission-scoped &lt;code dir=&quot;auto&quot;&gt;migrate&lt;/code&gt; command and every other accept-and-ignore command (#3953) is unchanged, and &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; stays byte-identical. Real per-Mission scoping for the corpus-walking commands is deferred to a follow-up.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A custom mission type now gets the work-package advance guard and the substantive-spec gate through two capabilities on its resolved mission type&lt;/strong&gt; (#6315). &lt;strong&gt;Before:&lt;/strong&gt; both checks were keyed on the literal &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; family, so an activated custom type that iterates work packages let &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; proceed with packages still pending, and accepted a stub spec. &lt;strong&gt;After:&lt;/strong&gt; a mission type declares &lt;code dir=&quot;auto&quot;&gt;wp_driven&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;requires_substantive_spec&lt;/code&gt;, and the runtime and CLI read them from the resolved type; the runtime-shape parser now lives once in &lt;code dir=&quot;auto&quot;&gt;kernel&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; behave as before. The non-work-package CLI pre-check stays &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;-scoped by design, since custom types get the same guard from composition dispatch. Template precedence and the code-producing review gate (#6328, which needs the #6327 capability) are out of scope.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An activated custom mission type now resolves its lifecycle and gets the &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; analysis gate&lt;/strong&gt; (#4983). &lt;strong&gt;Before:&lt;/strong&gt; a custom type from an org pack (steps in &lt;code dir=&quot;auto&quot;&gt;missions/&amp;#x3C;type&gt;/mission-runtime.yaml&lt;/code&gt;) failed with &lt;code dir=&quot;auto&quot;&gt;MissionTypeEmptyActionSequenceError&lt;/code&gt;. Its &lt;code dir=&quot;auto&quot;&gt;analyze&lt;/code&gt; step also never enforced analysis currency, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; let &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; run on a stale or missing report. &lt;strong&gt;After:&lt;/strong&gt; the action sequence resolves from the type’s own steps. Any mission whose runtime declares &lt;code dir=&quot;auto&quot;&gt;analyze&lt;/code&gt; re-runs the stale-analysis gate before &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, on the decide and preview paths. &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; are unchanged. Acceptance and merge for custom types land in later slices.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A custom mission type whose runtime shape repeats a step id now fails with the governed error instead of a raw &lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt;&lt;/strong&gt; (#6323). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;missions/&amp;#x3C;type&gt;/mission-runtime.yaml&lt;/code&gt; with a duplicate &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; in its &lt;code dir=&quot;auto&quot;&gt;steps:&lt;/code&gt; list let the charter reader hand a duplicate-bearing sequence to the action-sequence projection, which rejected it with a bare &lt;code dir=&quot;auto&quot;&gt;ValueError: action_sequence must contain unique step IDs&lt;/code&gt; escaping custom-type resolution. &lt;strong&gt;After:&lt;/strong&gt; the reader fails closed on duplicate ids as it does for any other malformed runtime shape, so resolution surfaces the governed &lt;code dir=&quot;auto&quot;&gt;MissionTypeEmptyActionSequenceError&lt;/code&gt; naming the type and layer. The runtime loader still tolerates duplicate ids (and its step-id grammar stays laxer); both are deliberate, test-pinned charter↔runtime divergences where charter refuses rather than accept what runtime would. Built-in types are unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Owned-checkout acceptance records criterion verdicts and recognizes the minted Mission branch&lt;/strong&gt; (#6023). &lt;strong&gt;Before:&lt;/strong&gt; an owned, PR-bound &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission living only in its owned checkout could not finish. &lt;code dir=&quot;auto&quot;&gt;agent mission acceptance-verdict&lt;/code&gt; had no &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;, searched the repository root and exited &lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_FOUND&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;accept --owned-checkout --mode pr&lt;/code&gt; read work-package kinds from the repository root, saw no code, refused on the minted &lt;code dir=&quot;auto&quot;&gt;kitty/mission-&amp;#x3C;slug&gt;&lt;/code&gt; branch and skipped the acceptance-matrix checks. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;acceptance-verdict&lt;/code&gt; takes &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; (and adopts an owned caller checkout) and writes the matrix there. The branch gate reads the owned checkout’s work-package kinds, so a truly approved Mission’s minted branch is recognized and the matrix checks run. Repository-root and coordination acceptance is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; (squash) no longer refuses identical Mission files the classifier did not recognize&lt;/strong&gt; (#5697). &lt;strong&gt;Before:&lt;/strong&gt; a Mission file the classifier did not recognize (such as &lt;code dir=&quot;auto&quot;&gt;research/**&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;findings.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;gap-analysis.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;occurrence_map.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;goals.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;release.md&lt;/code&gt;) was treated as coordination bookkeeping by the squash, which refused the merge even though both sides were identical (the #5552 class). &lt;strong&gt;After:&lt;/strong&gt; an unrecognized file is never treated as a coordination record, and these files now have proper PRIMARY kinds. Real coordination bookkeeping (&lt;code dir=&quot;auto&quot;&gt;traces/&lt;/code&gt;, the decision log, review-cycle files) still carries forward. The separate #5847 window is not addressed here.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; no longer ships a fully-canceled lane’s content&lt;/strong&gt; (#5814). &lt;strong&gt;Before:&lt;/strong&gt; it merged every lane in &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;. A fully-canceled-with-provenance lane whose work package committed content before it was canceled was merged anyway: the canceled code landed, the envelope said &lt;code dir=&quot;auto&quot;&gt;success: true&lt;/code&gt;, and the reviewer’s rejection was silently undone. Host &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; already skipped such lanes. &lt;strong&gt;After:&lt;/strong&gt; the orchestrator-api uses the same rule as host. A fully-canceled lane is skipped: its content never lands, and its work packages are neither gate-checked nor marked merged/done. Approved lanes land unchanged. The contract moves to 1.18.0 (a behavior change to a call that used to succeed; no envelope field or error code changes).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer refuses approved work whose canceled dependency never started&lt;/strong&gt; (#5937). &lt;strong&gt;Before:&lt;/strong&gt; canceling a work package while it was still &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; (so its lane branch was never created) made &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuse the whole Mission, landing nothing, when an approved work package depended on it, saying the canceled lane’s commits could not be read, and its recovery said to restore a branch that never existed. &lt;strong&gt;After:&lt;/strong&gt; the lane is accepted when the status event log shows that every work package in it was canceled from &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; and none ever moved into any other lane than &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt;, with or without &lt;code dir=&quot;auto&quot;&gt;--attest-canceled-superseded&lt;/code&gt;; a lane whose branch was lost after work began, a claim recorded by a migration, an incomplete event log, or a lane-tip ref still recorded for the branch keep refusing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; no longer moves a &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; work package back without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;&lt;/strong&gt; (#5447). &lt;strong&gt;Before:&lt;/strong&gt; an unforced &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task &amp;#x3C;WP&gt; --to approved|in_progress|for_review|in_review|claimed&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;--to planned&lt;/code&gt; with a review feedback file, on a &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; work package exited 0 and recorded the move as forced (“backward rewind: done -&gt; X”); the &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; form also wrote a review verdict, &lt;code dir=&quot;auto&quot;&gt;status validate&lt;/code&gt; still passed, and a merged Mission read as active again. &lt;strong&gt;After:&lt;/strong&gt; the move is refused (exit 1) before anything is recorded, and the message names the forced command for that target (&lt;code dir=&quot;auto&quot;&gt;--force --note &quot;&amp;#x3C;why&gt;&quot;&lt;/code&gt;, plus &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission reopen&lt;/code&gt; for a merged Mission. Moves with &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; behave as before, and &lt;code dir=&quot;auto&quot;&gt;done -&gt; blocked&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;done -&gt; canceled&lt;/code&gt; stay refused.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Retrying an interrupted decision resolve, defer or cancel now completes it&lt;/strong&gt; (#5681). &lt;strong&gt;Before:&lt;/strong&gt; if the call stopped after the decision index was written but before the event log, the retry reported &lt;code dir=&quot;auto&quot;&gt;idempotent: true&lt;/code&gt; and wrote nothing. &lt;code dir=&quot;auto&quot;&gt;doctor decisions --repair&lt;/code&gt; then reopened the decision and erased its answer. &lt;strong&gt;After:&lt;/strong&gt; the retry writes the missing event once and reports its &lt;code dir=&quot;auto&quot;&gt;event_lamport&lt;/code&gt;; concurrent identical calls never write it twice. The orchestrator-api contract moves to 1.17.0: resolve/defer/cancel-decision can return &lt;code dir=&quot;auto&quot;&gt;DECISION_EVENT_REPAIR_FAILED&lt;/code&gt;, and an unreadable event log on retry returns &lt;code dir=&quot;auto&quot;&gt;DESIGN_STATUS_EVENT_LOG_UNREADABLE&lt;/code&gt; there and in &lt;code dir=&quot;auto&quot;&gt;decision resolve|defer|cancel&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; retry first; &lt;code dir=&quot;auto&quot;&gt;doctor decisions --repair&lt;/code&gt; before a retry still reopens the decision.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;On a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission, claiming the work package &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; just handed out no longer fails on &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;’s own files&lt;/strong&gt; (#5930). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; left &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; and the Mission’s &lt;code dir=&quot;auto&quot;&gt;mission-events.jsonl&lt;/code&gt; uncommitted in the write checkout, so the claim that followed refused with &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_DIRTY&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt;) or &lt;code dir=&quot;auto&quot;&gt;Workspace allocation failed&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt;), and committing them only helped until the next &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; call wrote them again. &lt;strong&gt;After:&lt;/strong&gt; the claim ignores &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; and the claimed Mission’s own &lt;code dir=&quot;auto&quot;&gt;mission-events.jsonl&lt;/code&gt;; any other uncommitted change, including another Mission’s event log, still refuses the claim.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt; no longer erases a status change recorded while it runs&lt;/strong&gt; (#5974). &lt;strong&gt;Before:&lt;/strong&gt; the repair read &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; outside the Mission write lock and rewrote the file from that read, so a transition another agent recorded in between was silently lost while the repair reported &lt;code dir=&quot;auto&quot;&gt;updated&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; could be replaced by a stale copy. &lt;strong&gt;After:&lt;/strong&gt; one Mission-lock hold covers the read through the rewrite (extended to the new lock key when the repair mints the &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; of a coordination Mission), and the &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; rebuild is one check-and-write under the lanes lock, so it never overwrites a manifest created meanwhile. A writer whose wait is bounded may now get the lock-timeout error during a long repair: its transition is not recorded and erases nothing, so retry it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A blocking policy mode is no longer silently turned into &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt;&lt;/strong&gt; (#5754). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;policy.&amp;#x3C;section&gt;.mode&lt;/code&gt; was matched exactly, so &lt;code dir=&quot;auto&quot;&gt;Block&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;BLOCK&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;block &lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; became &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; landed a Mission with an unresolved &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt; issue-matrix row at exit 0; &lt;code dir=&quot;auto&quot;&gt;risk&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;commit_guard&lt;/code&gt; had the same defect. &lt;strong&gt;After:&lt;/strong&gt; modes are matched ignoring case and surrounding whitespace, and an unrecognized value resolves to &lt;code dir=&quot;auto&quot;&gt;block&lt;/code&gt; with a warning naming the setting and the value. &lt;code dir=&quot;auto&quot;&gt;Off&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;OFF&lt;/code&gt; now mean &lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; (they used to mean &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt;), and an absent or null (&lt;code dir=&quot;auto&quot;&gt;mode:&lt;/code&gt; with no value) mode is still &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; no longer erases a work package’s dependencies when &lt;code dir=&quot;auto&quot;&gt;wps.yaml&lt;/code&gt; leaves them out&lt;/strong&gt; (#5448). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;wps.yaml&lt;/code&gt; entry with no &lt;code dir=&quot;auto&quot;&gt;dependencies&lt;/code&gt; key, a misspelled key such as &lt;code dir=&quot;auto&quot;&gt;depends_on&lt;/code&gt;, or no entry at all made finalize rewrite the WP file’s &lt;code dir=&quot;auto&quot;&gt;dependencies&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt;, plan an independent lane and print “Dependencies: None” in &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;, exit 0, so the work package could start before its prerequisite. &lt;strong&gt;After:&lt;/strong&gt; the WP file’s non-empty dependencies are kept and used for the lane plan, the report and the regenerated &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;; an explicit &lt;code dir=&quot;auto&quot;&gt;dependencies&lt;/code&gt; key, &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; included, still wins, and two disagreeing non-empty values are still refused.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Completing an Op with evidence that is not UTF-8 text (such as a PNG) no longer closes it half-done&lt;/strong&gt; (#5397). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;profile-invocation complete&lt;/code&gt; recorded the &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; event, then failed to read the file, losing the artifact and commit links and refusing every corrected retry as &lt;code dir=&quot;auto&quot;&gt;already_closed&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the evidence is checked before anything is written; unsupported evidence is refused with &lt;code dir=&quot;auto&quot;&gt;complete_failed&lt;/code&gt; (exit 1) and the Op stays open, so a retry with a text evidence file completes with all of its links.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate&lt;/code&gt; no longer overwrites an existing &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/&lt;/code&gt; file with an older legacy copy&lt;/strong&gt; (#5450). &lt;strong&gt;Before:&lt;/strong&gt; when a user-created file existed both in a legacy folder (&lt;code dir=&quot;auto&quot;&gt;missions/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;templates/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;scripts/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;command-templates/&lt;/code&gt;) and under &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;migrate --force&lt;/code&gt; (and the &lt;code dir=&quot;auto&quot;&gt;2.0.6_consistency_sweep&lt;/code&gt; upgrade step) moved the legacy copy on top of the override without a backup, listed the replaced file as &lt;code dir=&quot;auto&quot;&gt;kept&lt;/code&gt; and exited 0; a symbolically linked shared overrides folder was overwritten outside git, a folder at the destination crashed the run, and a relative link was moved where it no longer resolved. &lt;strong&gt;After:&lt;/strong&gt; such files stay where they are, the run prints how many were not moved and why (&lt;code dir=&quot;auto&quot;&gt;--verbose&lt;/code&gt; lists each), &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; reports a warning, and the exit code is still 0.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; now refuses a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission whose approved work has no committed implementation or no independent review&lt;/strong&gt; (#5939). &lt;strong&gt;Before:&lt;/strong&gt; an unforced &lt;code dir=&quot;auto&quot;&gt;move-task &amp;#x3C;WP&gt; --to approved&lt;/code&gt; could auto-walk a &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; work package to &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; with the same actor as implementer and reviewer and no implementation commit, and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; landed it &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; at exit 0. &lt;strong&gt;After:&lt;/strong&gt; a two-layer fail-closed net — a &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; gate and a &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; backstop (also in &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;PREFLIGHT_FAILED&lt;/code&gt;) — refuses an approved work package with no implementation commit in its &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt; or no independent review. &lt;strong&gt;Solo single_branch users:&lt;/strong&gt; independence is strict — implementing and approving under the same &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt; identity (or &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; with no &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt;) is now refused; use a distinct reviewer. &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; are unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; refusal for a work package with no committed work now says “no implementation commit”&lt;/strong&gt; (#6369). &lt;strong&gt;Before:&lt;/strong&gt; the #5939 move-side gate, which runs before the for_review gate, refused with “Refusing to move WP01 into review without a committed implementation”, so its wording differed from the for_review gate and the &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; check. &lt;strong&gt;After:&lt;/strong&gt; it reads “WP01 cannot move into review: no implementation commit touching its owned_files on the single_branch mission branch”. The error code &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH_IMPLEMENTATION_MISSING&lt;/code&gt; and the refusal itself are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; commands on a project that still needs the charter-pack upgrade now get a JSON error instead of an empty stdout&lt;/strong&gt; (#6232). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;LEGACY_CHARTER_STATE&lt;/code&gt; refusal always printed prose on stderr, so &lt;code dir=&quot;auto&quot;&gt;doctor skills --json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter status --json&lt;/code&gt; and every other &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; command returned nothing on stdout. &lt;strong&gt;After:&lt;/strong&gt; under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; the refusal is one &lt;code dir=&quot;auto&quot;&gt;{&quot;ok&quot;: false, &quot;error&quot;: {&quot;code&quot;: &quot;LEGACY_CHARTER_STATE&quot;, ...}}&lt;/code&gt; object on stdout, still with exit 1; without &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; the message is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Synthesized “how we apply” tactics reach action context through their directive&lt;/strong&gt; (#6404). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; linked each &lt;code dir=&quot;auto&quot;&gt;how-we-apply-*&lt;/code&gt; tactic with an &lt;code dir=&quot;auto&quot;&gt;applies&lt;/code&gt; edge no traversal follows, so an explicit &lt;code dir=&quot;auto&quot;&gt;activated_tactics&lt;/code&gt; list filtered them out, and with no list they were delivered for every action regardless of their directive. &lt;strong&gt;After:&lt;/strong&gt; synthesis emits &lt;code dir=&quot;auto&quot;&gt;directive --suggests--&gt; tactic&lt;/code&gt;, appends a newly created tactic to an explicit list, and delivers it only while its directive is active. A tactic you remove stays removed: synthesis records every tactic it creates in &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-artifacts.yaml&lt;/code&gt; and never appends it again. Re-running replaces the old &lt;code dir=&quot;auto&quot;&gt;applies&lt;/code&gt; edges and reports how many.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Org-pack artifacts are named and delivered by their declared id&lt;/strong&gt; (#6406). &lt;strong&gt;Before:&lt;/strong&gt; an activated org directive filed as &lt;code dir=&quot;auto&quot;&gt;qa-003-no-fake-green&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;id: QA_003&lt;/code&gt; was shown as &lt;code dir=&quot;auto&quot;&gt;QA_003_NO_FAKE_GREEN&lt;/code&gt;, and org tactics, paradigms and other kinds whose file stem differed from their id were silently not delivered. &lt;strong&gt;After:&lt;/strong&gt; one layer-aware identity index maps a stem or a declared id to the declared id for every kind, across context, &lt;code dir=&quot;auto&quot;&gt;--include&lt;/code&gt;, presets and &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An org-pack id in &lt;code dir=&quot;auto&quot;&gt;selected_directives&lt;/code&gt; no longer erases governance&lt;/strong&gt; (#6407). &lt;strong&gt;Before:&lt;/strong&gt; selections were checked against the built-in catalog only, so one org-pack id made &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; report “governance unresolved” and drop every directive while still exiting 0. &lt;strong&gt;After:&lt;/strong&gt; selections are checked against built-in, org and project packs; an id no layer knows is dropped with a diagnostic pointing at org packs and &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;, and every other id still resolves. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status doctor&lt;/code&gt; warns about it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stack detection reads the repository root first&lt;/strong&gt; (#6405). &lt;strong&gt;Before:&lt;/strong&gt; a nested &lt;code dir=&quot;auto&quot;&gt;site/package.json&lt;/code&gt; made a Gradle/Java repository read as &lt;code dir=&quot;auto&quot;&gt;typescript&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;build.gradle.kts&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;settings.gradle&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;gradlew&lt;/code&gt; were not recognized. &lt;strong&gt;After:&lt;/strong&gt; root-level manifests decide, those files and &lt;code dir=&quot;auto&quot;&gt;mvnw&lt;/code&gt; count as Java, and same-depth ties go by source-file counts. A repository with only nested manifests in two languages now resolves by file counts rather than defaulting to JavaScript.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; outside a git repository no longer crashes&lt;/strong&gt; (#6437). &lt;strong&gt;Before:&lt;/strong&gt; a migration that needs a git repository raised &lt;code dir=&quot;auto&quot;&gt;NotInsideRepositoryError&lt;/code&gt; and stopped the whole upgrade. &lt;strong&gt;After:&lt;/strong&gt; the runner treats that migration as not applicable, skips it with a warning and records nothing, so it runs on the next upgrade inside a repository.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --only&lt;/code&gt; now reports what it wrote and nothing that contradicts it&lt;/strong&gt; (#6457). &lt;strong&gt;Before:&lt;/strong&gt; it printed the absent-key “initialized from …” warnings beside its own output, and for a mission type with no activation list it also said the effective set could not be resolved, although nothing was in force. &lt;strong&gt;After:&lt;/strong&gt; it prints what the kind now lists (&lt;code dir=&quot;auto&quot;&gt;Now listed for &amp;#x3C;kind&gt; (N): ...&lt;/code&gt;), and a kind whose effective set cannot be resolved gets one warning that gives the reason and &lt;code dir=&quot;auto&quot;&gt;No longer in force: unknown&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;(0): (none)&lt;/code&gt;. What is written is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The Pack Level and Charter Pack glossary entries now describe &lt;code dir=&quot;auto&quot;&gt;PACK_LEVEL_MISSING&lt;/code&gt; as shipped&lt;/strong&gt; (#6403). &lt;strong&gt;Before:&lt;/strong&gt; they said loading refuses a &lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt; that omits &lt;code dir=&quot;auto&quot;&gt;pack_level&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; they describe it as a non-blocking diagnostic during the deprecation window of ADR 2026-10-11-2 (loading warns and uses the configured level), which becomes a refusal once the window closes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter compile&lt;/code&gt; and the consistency check resolve activation entries the way the runtime does&lt;/strong&gt; (#6433). &lt;strong&gt;Before:&lt;/strong&gt; compile refused a URN or a declared id that no single file name represents, and the consistency check reported stored declared ids and project-layer artifacts as unknown and reported an unknown entry twice. &lt;strong&gt;After:&lt;/strong&gt; both resolve file names, declared ids and URNs through one identity index that covers the built-in, org and project layers. Compile still refuses a truly unknown entry; the consistency check reports it once and leaves it in the list. The activation filter used by the review gate bindings, the mission-step-contract executor, the reference resolver and the consistency check resolves through the same index, so a URN or a declared id is admitted where it was dropped.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two checkouts writing one Mission event log now serialize decision writes, so one &lt;code dir=&quot;auto&quot;&gt;decision_id&lt;/code&gt; cannot open twice&lt;/strong&gt; (#6872, #6765). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;decision open&lt;/code&gt; (and &lt;code dir=&quot;auto&quot;&gt;resolve&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;defer&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;cancel&lt;/code&gt;) locked &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/decisions/index.json.lock&lt;/code&gt;, keyed on the checkout’s ledger directory, while the row went to &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;. Two checkouts sharing a log took different locks, both passed the duplicate check, and the fold then refused both openings. &lt;strong&gt;After:&lt;/strong&gt; a write first takes one lock per resolved event log (under the git common dir, shared by all worktrees), then that sidecar. Writers of one log queue; writers of different logs do not. The sidecar, its &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; setup, &lt;code dir=&quot;auto&quot;&gt;repair-runtime-lock&lt;/code&gt;, the reconciler and the timed-out refusal are unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An org-required artifact is written to an activation list by its file name, not its declared id&lt;/strong&gt; (#6435). &lt;strong&gt;Before:&lt;/strong&gt; activating an artifact of a kind whose absent key means “only what the org packs require” (skills) copied the org’s &lt;code dir=&quot;auto&quot;&gt;required_&amp;#x3C;kind&gt;&lt;/code&gt; list verbatim, so the list mixed a declared id with file names, and activating the required artifact by id stored both spellings. &lt;strong&gt;After:&lt;/strong&gt; each entry is stored by its file name (ids inherited through &lt;code dir=&quot;auto&quot;&gt;extends:&lt;/code&gt; included); a colliding required id is still refused with &lt;code dir=&quot;auto&quot;&gt;ActivationIdCollisionError&lt;/code&gt;. Existing lists take the new spelling on their next write. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The generated Claude plugin wrapper now runs the CLI on a machine that only has &lt;code dir=&quot;auto&quot;&gt;uv&lt;/code&gt;&lt;/strong&gt; (#6476). &lt;strong&gt;Before:&lt;/strong&gt; with no &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; on PATH the wrapper fell back to &lt;code dir=&quot;auto&quot;&gt;uvx &quot;spec-kitty-cli==&amp;#x3C;version&gt;&quot;&lt;/code&gt;, which asks uvx for an executable named after the distribution; the distribution ships only &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt;, so it exited 1 and every bundled skill failed. Any PATH &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; was used, whatever its version. &lt;strong&gt;After:&lt;/strong&gt; both wrappers run &lt;code dir=&quot;auto&quot;&gt;uvx --from &quot;spec-kitty-cli==&amp;#x3C;version&gt;&quot; spec-kitty&lt;/code&gt;, use a PATH CLI only when its version is inside the bundle’s &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;major&gt;.&amp;#x3C;minor&gt;&lt;/code&gt; series, and — when the pinned build version is not on PyPI — retry with &lt;code dir=&quot;auto&quot;&gt;spec-kitty-cli&gt;=&amp;#x3C;version&gt;,&amp;#x3C;&amp;#x3C;next minor&gt;&lt;/code&gt;. The remedy names &lt;code dir=&quot;auto&quot;&gt;uv tool install&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;pipx install&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;pip install&lt;/code&gt;. See &lt;a href=&quot;/guides/how-to/installation/install-claude-code-plugin/#how-the-runtime-wrapper-works&quot;&gt;the plugin install guide&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter activation commands no longer lose a change to a concurrent synthesis run&lt;/strong&gt; (#6719). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--preset&lt;/code&gt; and the activation-ledger migration wrote outside the synthesis lock. A &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; during &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; was overwritten, or refused with &lt;code dir=&quot;auto&quot;&gt;precondition_changed&lt;/code&gt; with the artifact still in force, and the migration stamp could drop entries the run had just written. &lt;strong&gt;After:&lt;/strong&gt; each change runs under the synthesis lock (#6453). If another run holds it, they wait about 10 seconds, then exit 1 with &lt;code dir=&quot;auto&quot;&gt;CHARTER_SYNTHESIS_LOCK_HELD&lt;/code&gt;, naming the lock file and writing nothing. &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--dry-run-evidence&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--list-topics&lt;/code&gt; take no lock.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt; no longer refuses, and synthesis no longer overwrites, a hand-written directive&lt;/strong&gt; (#6768; #6510, #4226). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter resynthesize --topic directive:&amp;#x3C;PROJECT_xxx&gt;&lt;/code&gt; refused an activated project-authored directive with &lt;code dir=&quot;auto&quot;&gt;Additive-only violation (FR-020 / EC-6)&lt;/code&gt; (exit 1). With no &lt;code dir=&quot;auto&quot;&gt;activated_directives&lt;/code&gt; key, &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; could replace a hand-written directive sharing a target’s id (exit 0). &lt;strong&gt;After:&lt;/strong&gt; resynthesis reports &lt;code dir=&quot;auto&quot;&gt;Nothing to regenerate&lt;/code&gt;, exits 0 and leaves the file alone; edit it directly. It reports only the targets it generated. A target whose id matches a directive synthesis did not create, an activated org directive or shipped doctrine refuses, activated or not. &lt;strong&gt;What to do:&lt;/strong&gt; give a project agent profile that reuses a shipped &lt;code dir=&quot;auto&quot;&gt;profile-id&lt;/code&gt;, and a hand-written directive sharing a synthesis target’s id, their own ids.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An org asset sidecar whose YAML is not a mapping no longer crashes the asset load&lt;/strong&gt; (#6735). &lt;strong&gt;Before:&lt;/strong&gt; an &lt;code dir=&quot;auto&quot;&gt;*.asset.yaml&lt;/code&gt; (or any kind’s overlay sidecar, or a built-in file) whose top level was a list or scalar raised &lt;code dir=&quot;auto&quot;&gt;AttributeError: &apos;list&apos; object has no attribute &apos;get&apos;&lt;/code&gt; and aborted the whole load. That broke every asset consumer, and in &lt;code dir=&quot;auto&quot;&gt;doctor charter-packs&lt;/code&gt; the org asset containment check failed closed and hid every other named escape. &lt;strong&gt;After:&lt;/strong&gt; such a file is treated as malformed, like invalid YAML: it is skipped with the usual &lt;code dir=&quot;auto&quot;&gt;Skipping invalid &amp;#x3C;layer&gt; &amp;#x3C;kind&gt; &amp;#x3C;file&gt;: expected a YAML mapping, got &amp;#x3C;type&gt;&lt;/code&gt; warning, and every valid sidecar beside it still loads. Empty files still count as absent (no warning). This holds for every artifact kind in the org, project and built-in tiers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A compact &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt; value no longer stores blank segments or drops segments past the fourth&lt;/strong&gt; (#6755). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--agent &quot;claude: :&quot;&lt;/code&gt; stored &lt;code dir=&quot;auto&quot;&gt;model: &quot; &quot;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--agent &quot;claude\n&quot;&lt;/code&gt; stored the newline, and &lt;code dir=&quot;auto&quot;&gt;--agent &quot;a:b:c:d:e&quot;&lt;/code&gt; silently dropped &lt;code dir=&quot;auto&quot;&gt;d:e&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;add-history&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; each segment is stripped, a blank one counts as absent (&lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt;), and more than four segments is refused before any write (&lt;code dir=&quot;auto&quot;&gt;Invalid --agent value: Too many segments in --agent value: … (expected at most 4, got 5)&lt;/code&gt;). A blank tool is refused as before. Free-text &lt;code dir=&quot;auto&quot;&gt;--actor&lt;/code&gt; values and recorded identities are stored whole (#6400). &lt;strong&gt;What to do:&lt;/strong&gt; nothing for well-formed values; a value that now refuses was losing segments.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The mission-ID migration guide documents the &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; audit the CLI actually prints&lt;/strong&gt; (#6760). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;docs/migrations/mission-id-canonical-identity.md&lt;/code&gt; listed the states &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;legacy&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;conflict&lt;/code&gt;, showed a &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; sample with &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;total&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;conflicts&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;dir&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mission_slug&lt;/code&gt; rows, and claimed the backfill refuses while conflicts are present. &lt;strong&gt;After:&lt;/strong&gt; the page lists the five live states (&lt;code dir=&quot;auto&quot;&gt;assigned&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;legacy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;orphan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;residue&lt;/code&gt;), both JSON samples match the live report key-for-key (&lt;code dir=&quot;auto&quot;&gt;summary&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;missions[]&lt;/code&gt; rows, &lt;code dir=&quot;auto&quot;&gt;duplicate_prefixes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ambiguous_selectors&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;fail_on_triggered&lt;/code&gt;, conditional &lt;code dir=&quot;auto&quot;&gt;residue_remedies&lt;/code&gt;), the backfill transcript matches live output, and a structural test pins the page to the imported contract so it cannot drift silently again. &lt;strong&gt;What to do:&lt;/strong&gt; nothing — read the page; your existing output was already the new shape.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The accept path-convention failure names the honest fixes for a repo with no &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt;&lt;/strong&gt; (#6633). &lt;strong&gt;Before:&lt;/strong&gt; when &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; blocked on software-dev path conventions, it offered only &lt;code dir=&quot;auto&quot;&gt;accept --lenient&lt;/code&gt; (which also skips the per-WP &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;assignee&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt; checks) or &lt;code dir=&quot;auto&quot;&gt;mkdir -p src/ tests/ docs/&lt;/code&gt;. It never named the &lt;code dir=&quot;auto&quot;&gt;project.path_conventions&lt;/code&gt; remap in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; (#3016) or the mission-type override at &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/missions/&amp;#x3C;type&gt;/mission.yaml&lt;/code&gt; (#4088). &lt;strong&gt;After:&lt;/strong&gt; the failure names &lt;code dir=&quot;auto&quot;&gt;project.path_conventions&lt;/code&gt; with a copy-paste example of the missing remappable keys (never &lt;code dir=&quot;auto&quot;&gt;deliverables&lt;/code&gt;, which the &lt;code dir=&quot;auto&quot;&gt;contracts: none&lt;/code&gt; waiver governs). It names the mission override for a key with no directory. The &lt;code dir=&quot;auto&quot;&gt;--lenient&lt;/code&gt;-then-&lt;code dir=&quot;auto&quot;&gt;mkdir&lt;/code&gt; order is unchanged, and the accept how-to names both routes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;grep_absence&lt;/code&gt; acceptance verdict no longer counts a stale &lt;code dir=&quot;auto&quot;&gt;.pyc&lt;/code&gt; as still present with blank evidence&lt;/strong&gt; (#6804, #6761). &lt;strong&gt;Before:&lt;/strong&gt; the invariant ran plain &lt;code dir=&quot;auto&quot;&gt;grep -n&lt;/code&gt;, so a stale &lt;code dir=&quot;auto&quot;&gt;.pyc&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;__pycache__/&lt;/code&gt; still containing the pattern made GNU grep &gt;= 3.5 print &lt;code dir=&quot;auto&quot;&gt;binary file matches&lt;/code&gt; on stderr and exit 0 with empty stdout; the matcher recorded &lt;code dir=&quot;auto&quot;&gt;still_present&lt;/code&gt; with the evidence &lt;code dir=&quot;auto&quot;&gt;grep found matches: &lt;/code&gt; (blank). &lt;strong&gt;After:&lt;/strong&gt; grep runs with &lt;code dir=&quot;auto&quot;&gt;-I&lt;/code&gt;, so only text files are judged and a binary sidecar alone records &lt;code dir=&quot;auto&quot;&gt;confirmed_absent&lt;/code&gt;; on a match where stdout is empty (exit 0), the non-empty stderr lines are recorded as the evidence, with a never-blank fallback, keeping the 5-line cap. Still one grep subprocess per invariant; no CLI or schema change.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; now refreshes a shared lane’s workspace context; the false &lt;code dir=&quot;auto&quot;&gt;ACTIVE_WP_CONTEXT_STALE&lt;/code&gt; warning is gone&lt;/strong&gt; (#6650; #3946). &lt;strong&gt;Before:&lt;/strong&gt; claiming a later work package into an existing lane with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; kept &lt;code dir=&quot;auto&quot;&gt;current_wp&lt;/code&gt; on the first work package. Every later commit warned &lt;code dir=&quot;auto&quot;&gt;ACTIVE_WP_CONTEXT_STALE&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty context info&lt;/code&gt; showed the wrong one. PR #4584 had fixed &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; and the orchestrator API’s &lt;code dir=&quot;auto&quot;&gt;start-implementation&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; all three claim paths share one refresh, so the context follows the work package that claimed the lane. A lane with no saved context stays that way. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; re-claiming the lane is enough.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;’s printed commit command now names every path the run wrote&lt;/strong&gt; (#6631). &lt;strong&gt;Before:&lt;/strong&gt; the printed &lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit&lt;/code&gt; recipe named only &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesis-manifest.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/provenance/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;. The run also wrote &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/synthesized-artifacts.yaml&lt;/code&gt; (the record that keeps artifact removals sticking) and, on activation promotion, the activation file. Running the command left the record uncommitted, so other clones could re-add a removed tactic. &lt;strong&gt;After:&lt;/strong&gt; the recipe names the always-written synthesis paths plus exactly the activation paths the run wrote. The &lt;code dir=&quot;auto&quot;&gt;spk-charter-governance&lt;/code&gt; skill (step 7) and &lt;code dir=&quot;auto&quot;&gt;charter-artifact-structure&lt;/code&gt; tables now name the record. What &lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt; writes, its &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; envelopes and &lt;code dir=&quot;auto&quot;&gt;resynthesize&lt;/code&gt; output are unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; copy the printed command as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;move-task --review-feedback-file&lt;/code&gt; is refused on moves that write no review cycle&lt;/strong&gt; (#6699). &lt;strong&gt;Before:&lt;/strong&gt; only rejection moves (&lt;code dir=&quot;auto&quot;&gt;--to planned&lt;/code&gt;, with or without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;in_review -&gt; in_progress&lt;/code&gt;) and approval moves (&lt;code dir=&quot;auto&quot;&gt;--to approved&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--to done&lt;/code&gt;) used the file; on any other move, such as &lt;code dir=&quot;auto&quot;&gt;in_progress -&gt; for_review&lt;/code&gt;, it exited 0 and silently dropped it. &lt;strong&gt;After:&lt;/strong&gt; those moves refuse with exit 1 before writing, name the moves that record a review cycle, and suggest removing the flag or using &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; says the same. Approval moves keep the #6652 record-or-warn behavior. &lt;strong&gt;What to do:&lt;/strong&gt; drop the flag from moves that only change lane; put rationale in &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent release prep&lt;/code&gt; classifies accepted work packages from the resolved status surface, and fails on a corrupt status log&lt;/strong&gt; (#6612). &lt;strong&gt;Before:&lt;/strong&gt; the changelog draft took the last &lt;code dir=&quot;auto&quot;&gt;to_lane&lt;/code&gt; in file order from the primary checkout’s &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; and skipped corrupt lines, so an out-of-order log, or a stale copy under a coordination topology, put work packages in the wrong section. &lt;strong&gt;After:&lt;/strong&gt; each work package is classified by the canonical status reducer over the resolved status surface. A corrupt log fails, naming the Mission and line; a deleted coordination branch fails with its fix; a missing coordination worktree falls back to frontmatter. &lt;strong&gt;What to do:&lt;/strong&gt; if prep names a Mission whose coordination branch is gone, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination --fix&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A malformed &lt;code dir=&quot;auto&quot;&gt;charter_packs&lt;/code&gt; registry gets the same code from &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt;&lt;/strong&gt; (#6772). &lt;strong&gt;Before:&lt;/strong&gt; for a bad &lt;code dir=&quot;auto&quot;&gt;charter_packs&lt;/code&gt; value in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; (such as &lt;code dir=&quot;auto&quot;&gt;[1, 2]&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt; reported &lt;code dir=&quot;auto&quot;&gt;ACTIVATION_FAILED&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt; reported &lt;code dir=&quot;auto&quot;&gt;ACTIVE_CHARTER_CONFIG_INVALID&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; both report &lt;code dir=&quot;auto&quot;&gt;ACTIVE_CHARTER_CONFIG_INVALID&lt;/code&gt;, in text and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;, exit 1 and write nothing. A declared org pack that was never fetched still gets &lt;code dir=&quot;auto&quot;&gt;ACTIVATION_FAILED&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt;, with the &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter fetch&lt;/code&gt; remedy. &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; and the orchestrator-api are unaffected. &lt;strong&gt;What to do:&lt;/strong&gt; tooling that matched &lt;code dir=&quot;auto&quot;&gt;ACTIVATION_FAILED&lt;/code&gt; for a malformed registry must now match &lt;code dir=&quot;auto&quot;&gt;ACTIVE_CHARTER_CONFIG_INVALID&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The docs now describe the real status ordering: wall clock, not Lamport&lt;/strong&gt; (#6604). &lt;strong&gt;Before:&lt;/strong&gt; the two living C4 pages, the API/dashboard domain plan and &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt;’s “Status Model Patterns” (which &lt;code dir=&quot;auto&quot;&gt;CLAUDE.md&lt;/code&gt; inherits through its symlink) said the CLI status path was Lamport-ordered, with two reducers that could disagree. &lt;strong&gt;After:&lt;/strong&gt; they state one reducer, &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events.diary.reduce_parsed&lt;/code&gt;, ordered by the writer’s &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; then &lt;code dir=&quot;auto&quot;&gt;event_id&lt;/code&gt;, with the #4941 approved-departure lift. They keep the open residual: a non-approval transition minted on a clock behind the event it follows still sorts before it. ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-01-2&lt;/code&gt; records this as Amendment 2026-10-30, the gap table closes G-3, and &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_status_path_ordering_claims.py&lt;/code&gt; fails if the old wording returns. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; no command or output changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A leftover &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; folder no longer fakes a prefix collision on a healthy Mission&lt;/strong&gt; (#6757). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --audit&lt;/code&gt; could report &lt;code dir=&quot;auto&quot;&gt;DUPLICATE_PREFIX&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;AMBIGUOUS_SELECTOR&lt;/code&gt; on a real Mission because of a folder holding only a &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;, which every other command treats as residue. &lt;strong&gt;After:&lt;/strong&gt; collisions are judged only among Missions that selection can reach. Two real Missions sharing a prefix, and a pre-identity Mission with no &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;, are reported as before; the leftover folder keeps its own &lt;code dir=&quot;auto&quot;&gt;IDENTITY_MISSING&lt;/code&gt;, so &lt;code dir=&quot;auto&quot;&gt;--fail-on error&lt;/code&gt; still exits 1. &lt;strong&gt;What to do:&lt;/strong&gt; nothing if a report got shorter. For a folder still named &lt;code dir=&quot;auto&quot;&gt;IDENTITY_MISSING&lt;/code&gt;, commit a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; with a &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;, or remove it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops&lt;/code&gt; finds and closes Op records in every checkout, not only the root&lt;/strong&gt; (#6661). &lt;strong&gt;Before:&lt;/strong&gt; since #6564 an Op record is written in the checkout the command runs in, but the sweep read only &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;project root&gt;/kitty-ops&lt;/code&gt;. An Op opened in a linked worktree was invisible and never closed by &lt;code dir=&quot;auto&quot;&gt;--close-stale&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the sweep reads every checkout from &lt;code dir=&quot;auto&quot;&gt;git worktree list&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;--close-stale&lt;/code&gt; closes each stale Op in the checkout that owns it, so the closure lands in that checkout’s &lt;code dir=&quot;auto&quot;&gt;kitty-ops/op-closures.jsonl&lt;/code&gt; and branch. Listed paths name their checkout (&lt;code dir=&quot;auto&quot;&gt;../lane/kitty-ops/&amp;#x3C;id&gt;.jsonl&lt;/code&gt;). An unreadable Op store is named on stderr, not treated as empty. The &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; shape, the session-start/stop reminder (root only, no git call) and exit codes are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor event-logs&lt;/code&gt; reclaims orphaned runs and Op-scoped glossary logs&lt;/strong&gt; (#6831, #6739). &lt;strong&gt;Before:&lt;/strong&gt; both stayed forever as &lt;code dir=&quot;auto&quot;&gt;Mission not found&lt;/code&gt;: runs whose &lt;code dir=&quot;auto&quot;&gt;feature-runs.json&lt;/code&gt; entry was replaced or removed, and the &lt;code dir=&quot;auto&quot;&gt;profile-invocation-&amp;#x3C;id&gt;.events.jsonl&lt;/code&gt; logs in &lt;code dir=&quot;auto&quot;&gt;.kittify/events/glossary/&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; a run naming its Mission by slug follows that Mission; one naming none is judged on age (&lt;code dir=&quot;auto&quot;&gt;past retention; no Mission recorded&lt;/code&gt;). An Op log is kept while its Op is open (&lt;code dir=&quot;auto&quot;&gt;Op is open&lt;/code&gt;), then eligible (&lt;code dir=&quot;auto&quot;&gt;past retention; Op completed&lt;/code&gt;), or judged on age with no Op record (&lt;code dir=&quot;auto&quot;&gt;past retention; no Op recorded&lt;/code&gt;). Limits and locks still apply; a run whose recorded Mission cannot be resolved stays &lt;code dir=&quot;auto&quot;&gt;Mission not found&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; preview with &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor event-logs&lt;/code&gt;, then &lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt;. See &lt;a href=&quot;/guides/how-to/monitoring/clean-up-local-event-logs/&quot;&gt;Clean Up Local Event Logs&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A review rejection no longer leaves its feedback draft behind to block the next &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt;&lt;/strong&gt; (#6832, #6632). &lt;strong&gt;Before:&lt;/strong&gt; the prompt called &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/tasks/&amp;#x3C;wp&gt;/review-feedback-N.md&lt;/code&gt; “committed with the project”, but the rejection committed only the derived &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt;, so that file stayed untracked and the WP’s next &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; refused on it (&lt;code dir=&quot;auto&quot;&gt;Blocking: 1 uncommitted file(s)&lt;/code&gt;). &lt;strong&gt;After:&lt;/strong&gt; the record holds the reviewer’s text, so the rejection removes that work package’s own &lt;code dir=&quot;auto&quot;&gt;review-feedback-*.md&lt;/code&gt; once the committed record is verified to contain it, says so on stderr, and reports &lt;code dir=&quot;auto&quot;&gt;retired_feedback_draft&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;. Any other file (&lt;code dir=&quot;auto&quot;&gt;notes.md&lt;/code&gt;, another work package’s draft, a symlink, a tracked or edited draft) is kept, with a stderr warning when it was a draft that could not be removed safely. There is no opt-out.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer re-identifies a Mission whose &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is missing from the working tree&lt;/strong&gt; (#6843, #6673). &lt;strong&gt;Before:&lt;/strong&gt; when git tracked &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/meta.json&lt;/code&gt; but the working tree lost it (an accidental &lt;code dir=&quot;auto&quot;&gt;rm&lt;/code&gt;, sparse checkout), the &lt;code dir=&quot;auto&quot;&gt;2.0.6&lt;/code&gt; sweep rebuilt it from the directory name, the &lt;code dir=&quot;auto&quot;&gt;3.2.0a4&lt;/code&gt; normalization minted a fresh &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; into it, and the runtime-state cutover wrote a &lt;code dir=&quot;auto&quot;&gt;{&quot;status_phase&quot;: &quot;1&quot;}&lt;/code&gt; stub if it was still missing. The next &lt;code dir=&quot;auto&quot;&gt;git add -A&lt;/code&gt; committed a second identity. &lt;strong&gt;After:&lt;/strong&gt; the upgrade rebuilds the file from git’s copy and the Mission keeps its &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;. A copy that lost its &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; takes the tracked one back. An unusable tracked copy is left alone and the output names the repair. &lt;strong&gt;What to do:&lt;/strong&gt; nothing (&lt;a href=&quot;/guides/how-to/installation/upgrade-project/#if-a-mission-s-meta-json-is-missing&quot;&gt;upgrade notes&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Generated charter fetches preserve an explicit owned Mission&lt;/strong&gt; (#6845). &lt;strong&gt;Before:&lt;/strong&gt; a prompt from an owned checkout could fetch charter context from the primary checkout. &lt;strong&gt;After:&lt;/strong&gt; generated commands carry the validated checkout and Mission, and &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; revalidates that claim before reading or writing context. Ordinary commands retain their existing scope.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reopening approved implementation preserves supplied review feedback&lt;/strong&gt; (#6845). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task &amp;#x3C;WP&gt; --to in_progress --review-feedback-file &amp;#x3C;file&gt;&lt;/code&gt; discarded a valid reference and recorded a forced transition. &lt;strong&gt;After:&lt;/strong&gt; the reference reaches the existing transition validators and the reopen records &lt;code dir=&quot;auto&quot;&gt;force: false&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;. Omitting feedback retains the existing forced-reopen policy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Global runtime storage cannot authorize project migrations by itself&lt;/strong&gt; (#6845). &lt;strong&gt;Before:&lt;/strong&gt; an inferred global &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt; directory could trigger project scans or recreate an ancestor &lt;code dir=&quot;auto&quot;&gt;.git/hooks&lt;/code&gt; directory outside a repository. &lt;strong&gt;After:&lt;/strong&gt; inferred global storage needs fresh repository authority before project-wide migration work, and hook repinning requires an existing Git repository. Explicit supported project overrides and ordinary non-Git projects retain their existing migration behavior.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An explicit migrated owned checkout can create a Mission while the primary checkout remains legacy&lt;/strong&gt; (#6845). &lt;strong&gt;Before:&lt;/strong&gt; startup inspected the primary checkout before validating &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; and refused with &lt;code dir=&quot;auto&quot;&gt;LEGACY_CHARTER_STATE&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the canonical custody validator selects the explicit linked checkout for startup schema and legacy checks. Invalid claims still refuse, and command-level Mission and write custody checks remain in force. The validated basic claim is shared only within one command, preserving the existing Git-call budget.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;upgrade --project&lt;/code&gt; no longer stalls on a legacy Mission whose &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; is its own slug&lt;/strong&gt; (#6689). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;migrate backfill-runtime-state&lt;/code&gt; wrote its seed row without the &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;, so its own check reported &lt;code dir=&quot;auto&quot;&gt;claim mismatch (deterministic seed payload diverged)&lt;/code&gt; on every run; one such Mission blocked the runtime-state cutover for all others. &lt;strong&gt;After:&lt;/strong&gt; the seed row carries the &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, the check passes, the Mission flips, and a re-run appends nothing. A project half-migrated by the old build converges without hand edits. &lt;strong&gt;What to do:&lt;/strong&gt; re-run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --project&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-runtime-state --mission &amp;#x3C;slug&gt;&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Decision Moment records are written byte-safe, so a Mission that opens one passes &lt;code dir=&quot;auto&quot;&gt;validate-encoding&lt;/code&gt;&lt;/strong&gt; (#6878, #6579). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/decisions/store.py&lt;/code&gt; rendered the record’s &lt;code dir=&quot;auto&quot;&gt;## Change log&lt;/code&gt; bullets with a literal U+2014 em dash (&lt;code dir=&quot;auto&quot;&gt;- \&lt;/code&gt;&lt;ts&gt;` — opened&lt;code dir=&quot;auto&quot;&gt;), so every mission that opened a decision wrote a &lt;/code&gt;kitty-specs/&lt;slug&gt;/decisions/DM-*.md&lt;code dir=&quot;auto&quot;&gt;whose bytes the strict ASCII gate refused, and a maintainer had to run&lt;/code&gt;validate-encoding —fix&lt;code dir=&quot;auto&quot;&gt; over a file the tool itself wrote. **After:** both bullets render through one ASCII separator (&lt;/code&gt;- `&lt;ts&gt;` - opened&lt;code dir=&quot;auto&quot;&gt;), so a written record is ASCII for ASCII inputs in every status and the gate passes without a repair pass. Authored prose is still rendered verbatim and still flagged by the gate; &lt;/code&gt;validate-encoding&lt;code dir=&quot;auto&quot;&gt;and its mapping table are unchanged, and records already on disk can be repaired with&lt;/code&gt;—fix` as before.&lt;/ts&gt;&lt;/slug&gt;&lt;/ts&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Status and review locks share one runtime-directory name&lt;/strong&gt; (#6883, #6516). &lt;strong&gt;Before:&lt;/strong&gt; both lock modules typed &lt;code dir=&quot;auto&quot;&gt;.spec-kitty&lt;/code&gt; themselves and were exempted from the audit guard that catches scattered runtime-home paths. &lt;strong&gt;After:&lt;/strong&gt; they import the name from &lt;code dir=&quot;auto&quot;&gt;specify_cli.paths.RUNTIME_STATE_DIR_NAME&lt;/code&gt;, and the guard scans both modules again. Lock locations are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --dry-run&lt;/code&gt; now predicts the migrations the real run applies&lt;/strong&gt; (#6552). &lt;strong&gt;Before:&lt;/strong&gt; a migration whose &lt;code dir=&quot;auto&quot;&gt;detect()&lt;/code&gt; reads a file or git config that an earlier migration rewrites was judged against the pre-run tree. So &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; reported &lt;code dir=&quot;auto&quot;&gt;3.2.6_issue_matrix_driver_repoint&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;not needed (project already in target state)&lt;/code&gt; while the real run applied it. &lt;strong&gt;After:&lt;/strong&gt; a migration that declares the predecessors its &lt;code dir=&quot;auto&quot;&gt;detect()&lt;/code&gt; reads (&lt;code dir=&quot;auto&quot;&gt;sequenced_after&lt;/code&gt;; the 3.2.6 repoint declares the gate-artifact migration) is reported applied, with a &lt;code dir=&quot;auto&quot;&gt;Predicted by an earlier migration in this run (dry run)&lt;/code&gt; line naming that migration. &lt;code dir=&quot;auto&quot;&gt;--dry-run --verbose&lt;/code&gt; agrees instead of saying &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt;. An undeclared dry-run skip now says &lt;code dir=&quot;auto&quot;&gt;not needed on the current tree&lt;/code&gt;. Real-run verdicts, warnings and records are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activating or deactivating a built-in mission step contract now reaches its graph node&lt;/strong&gt; (#6887, #6741). &lt;strong&gt;Before:&lt;/strong&gt; the DRG names a step contract by its owning pair (&lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation/accept&lt;/code&gt;), but activation resolved it to &lt;code dir=&quot;auto&quot;&gt;mission_step_contract:documentation-accept&lt;/code&gt;, which no node carries. Activating one made &lt;code dir=&quot;auto&quot;&gt;charter consistency-check&lt;/code&gt; report a gap whose only remedy, &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt;, could not help; deactivating one by id did nothing. &lt;strong&gt;After:&lt;/strong&gt; activation, the config-graph parity check and the deny sets resolve tokens one way. An activated step contract is kept, a deactivated one is dropped, and one whose mission type is inactive gets a suggestion naming &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt;. A new gate fails if a shipped graph URN and its artifact’s declared identity disagree. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Another Mission’s lanes no longer block &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; as “legacy sparse-checkout state”&lt;/strong&gt; (#6888, #6844). &lt;strong&gt;Before:&lt;/strong&gt; the managed-lane check read lane policy only from &lt;code dir=&quot;auto&quot;&gt;kitty-specs/*/meta.json&lt;/code&gt; on the repository-root checkout’s current branch. On a branch without an (often long-merged) Mission’s &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt;, that Mission’s lane worktrees counted as legacy state. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; refused and pointed at &lt;code dir=&quot;auto&quot;&gt;doctor sparse-checkout --fix&lt;/code&gt;, which would disable those lanes. &lt;strong&gt;After:&lt;/strong&gt; a lane’s policy is also read from its own &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/meta.json&lt;/code&gt;, so the verdict no longer depends on the root checkout’s branch. Real legacy state still refuses; a lane with no &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; still blocks (fail closed). &lt;strong&gt;What to do:&lt;/strong&gt; nothing. After the old refusal, re-run without &lt;code dir=&quot;auto&quot;&gt;--allow-sparse-checkout&lt;/code&gt;; do not run &lt;code dir=&quot;auto&quot;&gt;doctor sparse-checkout --fix&lt;/code&gt; on those lanes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The project-intent rename keeps a deactivation instead of lifting it&lt;/strong&gt; (#6565). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;mission-type-scope-directive&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;project-intent-directive&lt;/code&gt; rename (&lt;code dir=&quot;auto&quot;&gt;#6443&lt;/code&gt;, run by &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt;) rewrote only the allow lists. An exclusion naming the old stem was left pointing at nothing (&lt;code dir=&quot;auto&quot;&gt;DENY_UNKNOWN_ID&lt;/code&gt;), and the renamed directive came back into force. &lt;strong&gt;After:&lt;/strong&gt; the rename moves the exclusion to &lt;code dir=&quot;auto&quot;&gt;NNN-project-intent-directive&lt;/code&gt; in the same write, so the directive stays deactivated; other exclusions, and an entry spelled as a declared id, are untouched. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;charter resynthesize&lt;/code&gt;) as usual.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A project with no agent list no longer makes migrations and &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; act on every agent folder&lt;/strong&gt; (#6890, #6501). &lt;strong&gt;Before:&lt;/strong&gt; a missing &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, or one with no &lt;code dir=&quot;auto&quot;&gt;agents&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tools&lt;/code&gt; section, returned the whole registry. &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt;, shim generation and &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; repair touched all 12 slash-command agents, creating folders the project never had. &lt;strong&gt;After:&lt;/strong&gt; such a project uses the agents whose directory it already has (&lt;code dir=&quot;auto&quot;&gt;.github&lt;/code&gt; counts only with its managed &lt;code dir=&quot;auto&quot;&gt;prompts/&lt;/code&gt; directory). It warns once, naming &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agents.available&lt;/code&gt;, and never adds a surface. A project with no agent directory gets none. A stated list is unchanged: &lt;code dir=&quot;auto&quot;&gt;available: []&lt;/code&gt; still means no managed agents (#6494), and an unreadable config still fails closed. &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config add &amp;#x3C;agent&gt;&lt;/code&gt; to record the set and stop the warning.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An upgrade no longer restores the &lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; command files that 3.1.2 retired&lt;/strong&gt; (#6547). &lt;strong&gt;Before:&lt;/strong&gt; on a project whose migration ledger was adopted before 4.0.0rc8’s adoption floor, &lt;code dir=&quot;auto&quot;&gt;2.1.4_enforce_command_file_state&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;3.0.2_restore_prompt_commands&lt;/code&gt; were re-selected. They saw the removed files as missing and wrote 14 back, while the recorded &lt;code dir=&quot;auto&quot;&gt;3.1.2_globalize_commands&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;3.2.0a4_safe_globalize_commands&lt;/code&gt; were skipped. The upgrade exited 0, and since &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; gitignores &lt;code dir=&quot;auto&quot;&gt;.claude/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; stayed clean. &lt;strong&gt;After:&lt;/strong&gt; both writers are recorded no-ops superseded by &lt;code dir=&quot;auto&quot;&gt;3.2.0a4_safe_globalize_commands&lt;/code&gt;, whatever the ledger holds; your own &lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; files are never touched. &lt;strong&gt;What to do:&lt;/strong&gt; delete any copies an earlier upgrade restored.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Projects using a harness plugin’s commands are reported as set up&lt;/strong&gt; (#6894, #6493). &lt;strong&gt;Before:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;agents.available: []&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; (meaning “no CLI-managed agents” since #6494), &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config list&lt;/code&gt; printed &lt;code dir=&quot;auto&quot;&gt;No agents configured.&lt;/code&gt; and suggested &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agent config add&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; claimed to verify untouched skill surfaces; &lt;code dir=&quot;auto&quot;&gt;init --ai claude&lt;/code&gt; exited 1 with &lt;code dir=&quot;auto&quot;&gt;Requested agents are not configured&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;doctor skills&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor command-files&lt;/code&gt; printed &lt;code dir=&quot;auto&quot;&gt;all … healthy (0 …)&lt;/code&gt; without checking anything. Following that advice duplicated plugin commands. &lt;strong&gt;After:&lt;/strong&gt; all of them name the no-CLI-managed state, exit 0 and install nothing; &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; prints &lt;code dir=&quot;auto&quot;&gt;no CLI-managed agents — nothing to check&lt;/code&gt;. A config with no agent list reports the agents present. JSON keys and &lt;code dir=&quot;auto&quot;&gt;agent config sync --create-missing&lt;/code&gt; for &lt;em&gt;listed&lt;/em&gt; agents are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --target &amp;#x3C;protected&gt;&lt;/code&gt; is refused instead of landing on a protected branch&lt;/strong&gt; (#6895, #6464). &lt;strong&gt;Before:&lt;/strong&gt; the squash was committed to whatever &lt;code dir=&quot;auto&quot;&gt;--target&lt;/code&gt; named, bypassing the protected-branch policy. On a Mission recorded for &lt;code dir=&quot;auto&quot;&gt;develop&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--target main&lt;/code&gt; landed on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; and only unwound by accident; the preview called it fine. &lt;strong&gt;After:&lt;/strong&gt; when the target differs from the recorded one and is protected, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;consolidate --dry-run --json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; refuse before any branch moves with &lt;code dir=&quot;auto&quot;&gt;PROTECTED_BRANCH_REFUSED&lt;/code&gt;, naming both branches and three ways forward: drop &lt;code dir=&quot;auto&quot;&gt;--target&lt;/code&gt;, fix &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, or use &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS&lt;/code&gt;. The #5385 recorded-target refusal is unchanged. Land protected branches through a pull request.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor skills&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces&lt;/code&gt; no longer report a project healthy when they checked nothing&lt;/strong&gt; (#6891). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; with no &lt;code dir=&quot;auto&quot;&gt;agents.available&lt;/code&gt; list — the legacy no-agent-list shape (#6501) — printed &lt;code dir=&quot;auto&quot;&gt;all manifest entries healthy (0 file(s))&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;all surfaces healthy (0 checked)&lt;/code&gt; at exit 0, claiming health over an empty examined set while &lt;code dir=&quot;auto&quot;&gt;doctor command-files&lt;/code&gt; reported real problems on the same tree. &lt;strong&gt;After:&lt;/strong&gt; both summaries say &lt;code dir=&quot;auto&quot;&gt;no stated agent list — nothing to check&lt;/code&gt;, name what was not examined and point at the missing &lt;code dir=&quot;auto&quot;&gt;agents.available&lt;/code&gt; list; a project that states its agent list keeps the healthy line with a real count, and every &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; key, exit code and &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; behavior is unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; to have the CLI check your surfaces, state the agents you use in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The lifecycle-envelope migration marks rewritten legacy rows unclocked, not clocked at zero&lt;/strong&gt; (#6906, #6414; #6411). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;migrate_lifecycle_envelope&lt;/code&gt; step stamped &lt;code dir=&quot;auto&quot;&gt;lamport_clock: 0&lt;/code&gt; on each legacy row it rewrote. Since &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; 11.0.0 made &lt;code dir=&quot;auto&quot;&gt;Event.lamport_clock&lt;/code&gt; optional, &lt;code dir=&quot;auto&quot;&gt;0&lt;/code&gt; is a real clock value. The row sorted after every unclocked row in the log, whatever its timestamp, and grouped as “concurrent” with every other migrated row. &lt;strong&gt;After:&lt;/strong&gt; those rows carry &lt;code dir=&quot;auto&quot;&gt;lamport_clock: null&lt;/code&gt;, so they keep their timestamp order. A re-run stays byte-identical, and rows an older migration stamped &lt;code dir=&quot;auto&quot;&gt;0&lt;/code&gt; are left alone. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; it applies at the next &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;. See &lt;a href=&quot;/development/reference/optional-lamport-clock-consumers/&quot;&gt;Consumers of the optional clock&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; draws the 👤 human-in-charge marker without loading the full profile catalog&lt;/strong&gt; (#6917). &lt;strong&gt;Before:&lt;/strong&gt; the read-only board loaded every shipped profile (26) and the 358-node graph to answer one &lt;code dir=&quot;auto&quot;&gt;sentinel&lt;/code&gt; flag per claimed row (about 2 s cold). &lt;strong&gt;After:&lt;/strong&gt; it reads only the profiles its rows name, through the same built-in, org and project layers, overlay merge and language scope. A two-profile board parses two documents (about 0.3 s warm), an empty board none, and profile lineage loads on first use again (#6462’s lazy graph, undone by a later refactor). The marker, its overlay precedence and its survival of a narrowed or denied &lt;code dir=&quot;auto&quot;&gt;activated_agent_profiles&lt;/code&gt; are unchanged. A broken &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; still fails the command closed. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize&lt;/code&gt; plans generator-shape proposals&lt;/strong&gt; (#6385). &lt;strong&gt;Before:&lt;/strong&gt; every &lt;code dir=&quot;auto&quot;&gt;retrospect create&lt;/code&gt; record carries &lt;code dir=&quot;auto&quot;&gt;proposals: []&lt;/code&gt;, and even a hand-written generator proposal was dropped: &lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt; printed &lt;code dir=&quot;auto&quot;&gt;planned: [] applied: [] conflicts: []&lt;/code&gt;, warned only when a proposal existed, and exited 0. &lt;strong&gt;After:&lt;/strong&gt; a generator-shape proposal may carry an optional &lt;code dir=&quot;auto&quot;&gt;payload&lt;/code&gt; block, validated as &lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt; applies it, and becomes a pending proposal. JSON and text output report a &lt;code dir=&quot;auto&quot;&gt;diagnostics&lt;/code&gt; block: record shape, finding counts, translated/planned counts, and each untranslatable proposal with why. &lt;code dir=&quot;auto&quot;&gt;retrospect create&lt;/code&gt; no longer says “review proposals” for none. Generator proposals are never auto-accepted, despite &lt;code dir=&quot;auto&quot;&gt;auto_applicable&lt;/code&gt;: select one with &lt;code dir=&quot;auto&quot;&gt;--proposal-id&lt;/code&gt; (add &lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt; to mutate). An unknown or untranslatable id is refused with &lt;code dir=&quot;auto&quot;&gt;proposal_not_selectable&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A landed consolidation ends with a clean tree, and its hints fit the topology&lt;/strong&gt; (#6924, #6450). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; tombstoned each lane’s &lt;code dir=&quot;auto&quot;&gt;.kittify/workspaces/*.json&lt;/code&gt; after its only bookkeeping commit, so a project tracking those files was left with uncommitted deletions by a run reporting success; &lt;code dir=&quot;auto&quot;&gt;accept --mode pr&lt;/code&gt; on a coordination-topology Mission said “Push and open a pull request if needed”; and the &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; issue-matrix refusal said “Fill in verdicts” even when every row had one. &lt;strong&gt;After:&lt;/strong&gt; the tombstones land in one scoped commit (none when nothing tracked was removed, re-pushed for &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; names &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --mission &amp;#x3C;handle&gt;&lt;/code&gt; there instead of a pull request; and the refusal names the diagnostics, keeping the verdict remedy only when a verdict is missing, unresolved or &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;. Gate decisions are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;deactivate --cascade&lt;/code&gt; start from the artifact you named, however you spelled it&lt;/strong&gt; (#6433). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;kind&gt;:&amp;#x3C;id&gt;&lt;/code&gt; URN or a normalized directive id (&lt;code dir=&quot;auto&quot;&gt;24&lt;/code&gt;) changed the right artifact but silently skipped the cascade: no &lt;code dir=&quot;auto&quot;&gt;Cascade-activated:&lt;/code&gt; line, and no &lt;code dir=&quot;auto&quot;&gt;Skipped (shared artifact):&lt;/code&gt; line on deactivate. &lt;strong&gt;After:&lt;/strong&gt; a file stem, declared id, URN and normalized directive id all reach the same artifact, for the cascade and on every other surface; an unknown token still yields no source, and a directive id no file name can represent still refuses. URNs and the normalized form are now also accepted in compile/resynthesis preflight and interview selection, which used to refuse or warn.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer re-runs legacy mission migrations when &lt;code dir=&quot;auto&quot;&gt;~/.kittify&lt;/code&gt; was never bootstrapped&lt;/strong&gt; (#6946, #6551). &lt;strong&gt;Before:&lt;/strong&gt; the check looked for &lt;code dir=&quot;auto&quot;&gt;~/.kittify/cache/version.lock&lt;/code&gt; before reading the project’s &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; does not bootstrap that home. On a new machine or CI runner whose first command was &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;0.6.7_ensure_missions&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;0.12.0_documentation_mission&lt;/code&gt; treated a 4.x project as not centralized, copied the packaged missions in, and auto-committed them. The project then resolved all three built-in &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; from those frozen copies. &lt;strong&gt;After:&lt;/strong&gt; a readable &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt; stamped 2.0.0 or later decides alone, so one commit gives one answer everywhere. The home is checked only with no stamp. &lt;strong&gt;What to do:&lt;/strong&gt; nothing. Projects that already have such overrides are repaired under #6548.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; are faster on a large project&lt;/strong&gt; (#6506). &lt;strong&gt;Before:&lt;/strong&gt; with this repository’s charter (165 KB &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, 264 references) one call took ~16.7 s, 45 % of it writing the compiled charter: &lt;code dir=&quot;auto&quot;&gt;catalog&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;metadata&lt;/code&gt; were written separately, each a full load, render and verify, with costly equality checks. &lt;strong&gt;After:&lt;/strong&gt; both are written in one cycle, and equality is checked structurally (1,189 ms to 1-4 ms, same verdicts). The command takes ~10.4 s (1.6x faster), with 6 whole-document round trips per recompile instead of 18 and byte-identical output. A no-op recompile writes nothing and keeps &lt;code dir=&quot;auto&quot;&gt;generated_at&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; and skill rendering share the faster check. &lt;strong&gt;Why not 2 s:&lt;/strong&gt; a pure read already takes 2.6 s here (&lt;a href=&quot;/adr/4.x/2026-10-31-1-charter-write-budget-for-repository-scale-projects/&quot;&gt;ADR 2026-10-31-1&lt;/a&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A custom code-producing mission type can no longer reach review with nothing implemented&lt;/strong&gt; (#6328; with #6327). &lt;strong&gt;Before:&lt;/strong&gt; the check for implementation commits on the work package’s lane ran only for &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;, so a custom code-producing type passed &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; with an empty lane. &lt;strong&gt;After:&lt;/strong&gt; a mission type carries a &lt;code dir=&quot;auto&quot;&gt;code_producing&lt;/code&gt; capability: &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; true; &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; and undeclared custom types false. The check reads it, so a custom code-producing type is refused with the missing commits named; &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; are unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; a custom type that produces code declares &lt;code dir=&quot;auto&quot;&gt;code_producing: true&lt;/code&gt; in its mission-type descriptor; other types need nothing. The #6715/#5939 evidence gates are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The source distribution ships only the repository’s own &lt;code dir=&quot;auto&quot;&gt;README.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;CHANGELOG.md&lt;/code&gt;&lt;/strong&gt; (#6926, #7007). &lt;strong&gt;Before:&lt;/strong&gt; the unanchored &lt;code dir=&quot;auto&quot;&gt;README.md&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;CHANGELOG.md&lt;/code&gt; include entries matched at any depth, so the sdist carried about 750 stray files from &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;scripts/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;packs/README.md&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;README.md&lt;/code&gt; entry is anchored to the repository root, &lt;code dir=&quot;auto&quot;&gt;CHANGELOG.md&lt;/code&gt; ships at the root as the real file rather than a link into &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;site/**&lt;/code&gt; is excluded ahead of the doc-kitty docsite, and a packaging-safety test on the built archive keeps &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;site/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;scripts/&lt;/code&gt; out. The wheel is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; warns about an activation list a &lt;em&gt;released&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt; preset wrote&lt;/strong&gt; (#7021, #6684). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_promote_interview_selections&lt;/code&gt; recognized a machine-written list only if it equaled today’s full set, so a project seeded from an older preset (19 directives at 3.2.6rc1, 38 now) got no warning and stayed blocked in &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it also recognizes the released preset lists, alone or plus the interview ids, says the list is machine-written, and names both narrowing commands. Nothing is written (the #6684 ruling keeps upgrade report-only), and a hand-picked list is left alone. &lt;strong&gt;What to do:&lt;/strong&gt; to narrow, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter interview --narrow-activation&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --only&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --dry-run&lt;/code&gt; now heads its migration list “Migrations that would be applied:” instead of a green “Migrations applied:”&lt;/strong&gt; (#7023, #6234). &lt;strong&gt;Before:&lt;/strong&gt; a preview printed the &lt;code dir=&quot;auto&quot;&gt;DRY RUN - No changes were made&lt;/code&gt; panel and then the same green &lt;code dir=&quot;auto&quot;&gt;Migrations applied:&lt;/code&gt; list with a &lt;code dir=&quot;auto&quot;&gt;✓&lt;/code&gt; on each migration it would have run, closing with “no changes applied” — so the output said nothing had been applied and that two migrations had. &lt;strong&gt;After:&lt;/strong&gt; a dry run heads that list &lt;code dir=&quot;auto&quot;&gt;Migrations that would be applied:&lt;/code&gt; and marks each entry with &lt;code dir=&quot;auto&quot;&gt;→&lt;/code&gt;, while a real run keeps &lt;code dir=&quot;auto&quot;&gt;Migrations applied:&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;✓&lt;/code&gt; unchanged; a dry run with nothing pending still prints no list at all. No migration selection, ordering, write or JSON behavior changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The launcher now calls the resident write service at the contract’s &lt;code dir=&quot;auto&quot;&gt;/api/v1&lt;/code&gt; paths&lt;/strong&gt; (#6910). &lt;strong&gt;Before:&lt;/strong&gt; the launcher’s loopback client sent bare &lt;code dir=&quot;auto&quot;&gt;/handshake&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/health&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;/shutdown&lt;/code&gt;, while &lt;code dir=&quot;auto&quot;&gt;contracts/mission-write/openapi.yaml&lt;/code&gt; declares &lt;code dir=&quot;auto&quot;&gt;servers: [{url: /api/v1}]&lt;/code&gt;, so the ready check, health check and stop call answered 404 against the real &lt;code dir=&quot;auto&quot;&gt;command-cli&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; every operation is &lt;code dir=&quot;auto&quot;&gt;GET /api/v1/handshake&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;GET /api/v1/health&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;POST /api/v1/shutdown&lt;/code&gt;, derived from one prefix constant that a contract test pins to the contract’s &lt;code dir=&quot;auto&quot;&gt;servers&lt;/code&gt; url, and the test stand-in service serves only the prefixed routes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; routes documentation requests, and a refusal names the closest profiles and the fix&lt;/strong&gt; (#7027, #6970). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;dispatch &quot;mark ADR-0068 Accepted and regenerate the ADR index&quot;&lt;/code&gt; exited 1 with &lt;code dir=&quot;auto&quot;&gt;ROUTER_NO_MATCH&lt;/code&gt; and no candidates; no profile declared &lt;code dir=&quot;auto&quot;&gt;adr&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;changelog&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;readme&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;guide&lt;/code&gt;. Declared multi-word or hyphenated keywords like &lt;code dir=&quot;auto&quot;&gt;knowledge base&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;transcribe-notes&lt;/code&gt; never matched. &lt;strong&gt;After:&lt;/strong&gt; documentation nouns route to the documentation profile (&lt;code dir=&quot;auto&quot;&gt;router_confidence: domain_keyword&lt;/code&gt;); bare &lt;code dir=&quot;auto&quot;&gt;index&lt;/code&gt; does not. Those keywords match as a fallback tier, so no earlier route moves. &lt;code dir=&quot;auto&quot;&gt;ROUTER_NO_MATCH&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ROUTER_AMBIGUOUS&lt;/code&gt; list ordered candidates with a runnable &lt;code dir=&quot;auto&quot;&gt;--profile &amp;#x3C;id&gt;&lt;/code&gt; command. A tie names every tied id, and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; lists them by &lt;code dir=&quot;auto&quot;&gt;profile_id&lt;/code&gt;, not score. Without &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;, refusals print readable lines, not raw JSON.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;implement --mission &amp;#x3C;human-slug&gt;&lt;/code&gt; no longer refuses a Mission that &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; resolves&lt;/strong&gt; (#7029, #6278). &lt;strong&gt;Before:&lt;/strong&gt; a Mission created today is &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;human-slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;smoke-test-01M6BTQX&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;agent tasks status --mission smoke-test&lt;/code&gt; accepted it while &lt;code dir=&quot;auto&quot;&gt;implement WP01 --mission smoke-test&lt;/code&gt; exited 2 with &lt;code dir=&quot;auto&quot;&gt;No mission found for handle &quot;smoke-test&quot;&lt;/code&gt;; only the composed slug and the mid8 resolved. &lt;strong&gt;After:&lt;/strong&gt; the identity resolver’s human-slug rung also folds the Mission’s own trailing &lt;code dir=&quot;auto&quot;&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt;, so every command that takes &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; accepts the same forms. A tail that is not that Mission’s &lt;code dir=&quot;auto&quot;&gt;mission_id[:8]&lt;/code&gt; is never stripped, and two Missions sharing a human slug still refuse with both candidates (&lt;code dir=&quot;auto&quot;&gt;MISSION_AMBIGUOUS_SELECTOR&lt;/code&gt;). &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The orchestrator contract now admits &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_DIRECTORY_ARGUMENT&lt;/code&gt;, a safe-commit refusal core has emitted without registering it&lt;/strong&gt; (#7036, #6997, #6750). &lt;strong&gt;Before:&lt;/strong&gt; since the #6750 fix, &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; refused a directory pathspec with &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_DIRECTORY_ARGUMENT&lt;/code&gt; — before writing anything — yet the code was absent from &lt;code dir=&quot;auto&quot;&gt;orchestrator_api.allowed_error_codes&lt;/code&gt;, so a caller keying on the contract had no name for that refusal and core’s own contract guard was red. &lt;strong&gt;After:&lt;/strong&gt; the code is registered in the vendored contract and its pinned mirror, listed in the API reference and the operator skill’s error-code table, and pinned by name in the contract test; the contract is &lt;code dir=&quot;auto&quot;&gt;1.22.0&lt;/code&gt;. It is a pre-mutation refusal, not a &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_RECOVERY_FAILED&lt;/code&gt; refinement: nothing was committed, and &lt;code dir=&quot;auto&quot;&gt;data.offending_path&lt;/code&gt; names the path. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; no longer advertises action-critical charter sections a consumer charter does not have&lt;/strong&gt; (#7041, #6968). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter context --action implement&lt;/code&gt; (and &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;) emitted &lt;code dir=&quot;auto&quot;&gt;Run: … --include section:terminology-canon&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;…-code-review-checklist&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;…-regression-vigilance&lt;/code&gt; even when &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; carried none of them, and each fetch answered “This charter has not yet authored … Add one”, so an agent was told that loading a placeholder was action-critical. &lt;strong&gt;After:&lt;/strong&gt; only headings the active charter resolves are advertised, each with its verbatim body and recovery stanza; an absent, empty or fence-masked heading is not, and the block header is omitted when nothing resolves. Output for a project that authors them is unchanged, and an explicit &lt;code dir=&quot;auto&quot;&gt;--include section:&amp;#x3C;slug&gt;&lt;/code&gt; still returns the honest placeholder. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Plugin bundles now stage when a project configures more than one harness&lt;/strong&gt; (#7043, #6273). &lt;strong&gt;Before:&lt;/strong&gt; with Claude and Codex configured, &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces --fix&lt;/code&gt; mapped &lt;code dir=&quot;auto&quot;&gt;.codex/agents/&amp;#x3C;id&gt;.toml&lt;/code&gt; onto the Claude bundle’s &lt;code dir=&quot;auto&quot;&gt;agents/&amp;#x3C;id&gt;.md&lt;/code&gt;. The batch was refused, &lt;code dir=&quot;auto&quot;&gt;dist/spec-kitty-plugins/&lt;/code&gt; was never created, the audit stayed at &lt;code dir=&quot;auto&quot;&gt;missing: 3&lt;/code&gt;, and the command exited 0. Copilot profiles staged as &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;id&gt;.agent.agent.md&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; each bundle takes one native rendering per member (Claude, Copilot/VS Code, and the shared &lt;code dir=&quot;auto&quot;&gt;.agents&lt;/code&gt; rendering for command/charter skills). A Codex TOML never becomes Markdown, Copilot keeps its suffix, and a Codex-only project’s bundles have no &lt;code dir=&quot;auto&quot;&gt;agents/&lt;/code&gt; member. A &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; that cannot repair prints &lt;code dir=&quot;auto&quot;&gt;Failed to repair:&lt;/code&gt; with each surface and reason, and exits 1. The OPTIONAL missing-manifest policy is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter synthesize --json&lt;/code&gt; reports repository-relative paths with &lt;code dir=&quot;auto&quot;&gt;/&lt;/code&gt; on every platform&lt;/strong&gt; (#7045, #6277). &lt;strong&gt;Before:&lt;/strong&gt; the fresh-seed envelope (&lt;code dir=&quot;auto&quot;&gt;files_written&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;files_planned&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;planned_deletes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;written_artifacts[].path&lt;/code&gt;) and the entries recorded in &lt;code dir=&quot;auto&quot;&gt;synthesis-manifest.yaml&lt;/code&gt; were rendered with &lt;code dir=&quot;auto&quot;&gt;str(Path.relative_to(...))&lt;/code&gt;, so Windows spelled them &lt;code dir=&quot;auto&quot;&gt;.kittify\charter-packs\PROVENANCE.md&lt;/code&gt; where Linux and macOS spelled them &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/PROVENANCE.md&lt;/code&gt;: a consumer read a different path spelling per operating system, and the committed manifest differed by platform. &lt;strong&gt;After:&lt;/strong&gt; every reported and recorded repository-relative path is POSIX, and the real-run envelope also normalizes a manifest written by an older Windows run. &lt;strong&gt;What to do:&lt;/strong&gt; nothing — the envelope shape and field names are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A custom mission type keeps its WP-advance guard when the planning directory’s name is not its mission handle, and a failed &lt;code dir=&quot;auto&quot;&gt;requires_substantive_spec&lt;/code&gt; resolution is logged&lt;/strong&gt; (#7046, #6330). &lt;strong&gt;Before:&lt;/strong&gt; the guard re-resolved the run from &lt;code dir=&quot;auto&quot;&gt;feature_dir.name&lt;/code&gt;; when that lookup failed, &lt;code dir=&quot;auto&quot;&gt;wp_driven&lt;/code&gt; read &lt;code dir=&quot;auto&quot;&gt;false&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; could advance with work packages pending. A failed &lt;code dir=&quot;auto&quot;&gt;requires_substantive_spec&lt;/code&gt; resolution fell back silently to the default (&lt;code dir=&quot;auto&quot;&gt;false&lt;/code&gt; for a custom type), so a stub spec could pass. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; threads the run it already resolved into &lt;code dir=&quot;auto&quot;&gt;gather_artifact_presence&lt;/code&gt;, so the fact never guesses a handle from a name; the capability fallback logs a warning naming the type and the failure; &lt;code dir=&quot;auto&quot;&gt;ResolvedMissionType.wp_driven&lt;/code&gt; is documented as advisory, with the frozen runtime DAG authoritative. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; the four built-in types are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project detection stops at &lt;code dir=&quot;auto&quot;&gt;GIT_CEILING_DIRECTORIES&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;make test-fast&lt;/code&gt; stays green when the temp directory sits inside a git repository&lt;/strong&gt; (#7022, #5356, #7058). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;locate_project_root&lt;/code&gt; and the plain-&lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; fallback of &lt;code dir=&quot;auto&quot;&gt;find_repo_root&lt;/code&gt; walked past the ceiling that git and &lt;code dir=&quot;auto&quot;&gt;resolve_canonical_root&lt;/code&gt; honor, so a directory below it resolved to the checkout above, and on a host whose temp directory lived inside any git work tree 18 fast-tier tests failed (lock fallback, lanes rebuild, the non-repository git probe, status actors, read-only-home startup) while CI stayed green. &lt;strong&gt;After:&lt;/strong&gt; the three walks read the ceiling through one helper that ignores relative entries as git does, and the test harness lists the run’s basetemp and isolated home as ceilings, replacing the &lt;code dir=&quot;auto&quot;&gt;tests/status/&lt;/code&gt; fixture that ran &lt;code dir=&quot;auto&quot;&gt;git init&lt;/code&gt; in every escaping &lt;code dir=&quot;auto&quot;&gt;tmp_path&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The issue matrix no longer marks a Mission’s own target issue context-only&lt;/strong&gt; (#7011). &lt;strong&gt;Before:&lt;/strong&gt; a positional label (&lt;code dir=&quot;auto&quot;&gt;parent #&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;epic #&lt;/code&gt;, a leading &lt;code dir=&quot;auto&quot;&gt;see #&lt;/code&gt;) matched anywhere on its line, so &lt;code dir=&quot;auto&quot;&gt;**Input**: Issue #6926 (part of epic #6100, …)&lt;/code&gt; classified the target &lt;code dir=&quot;auto&quot;&gt;#6926&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;context_only&lt;/code&gt; and scaffolded a terminal &lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt; row the approval gate accepted. &lt;strong&gt;After:&lt;/strong&gt; a positional label binds only to the reference it leads. The Mission’s source issue (from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;source_description&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;**Input**:&lt;/code&gt; line, or a &lt;code dir=&quot;auto&quot;&gt;Closes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Fixes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Resolves #N&lt;/code&gt; line) always scaffolds &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;, forcing a verdict. The scaffold, approval blocker, &lt;code dir=&quot;auto&quot;&gt;status doctor&lt;/code&gt; and merge gate share this classification; &lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt; stays available as an &lt;em&gt;explicit&lt;/em&gt; verdict. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; re-scaffold a Mission in flight, or record the verdict with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent issue-verdict&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The orchestrator error-code reference is now complete and checked&lt;/strong&gt; (#7035). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;docs/api/orchestrator-api.md&lt;/code&gt; left many of the contract’s codes out, as did the shipped &lt;code dir=&quot;auto&quot;&gt;spec-kitty-orchestrator-api-operator&lt;/code&gt; reference table, so an integrator could not enumerate the failure surface and a newly registered code could go missing from both. &lt;strong&gt;After:&lt;/strong&gt; both surfaces enumerate every code, each as its own list item or table row, and &lt;code dir=&quot;auto&quot;&gt;tests/contract/test_orchestrator_api.py::TestProseErrorCodeEnumerations&lt;/code&gt; compares every anchored enumeration with &lt;code dir=&quot;auto&quot;&gt;orchestrator_api.allowed_error_codes&lt;/code&gt; — failing on a registered code that is undocumented, a documented code the contract does not allow, a duplicate entry, and a missing or empty anchor.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The pre-review regression gate is usable again: a pinned &lt;code dir=&quot;auto&quot;&gt;pre_review_test_scope&lt;/code&gt; parses, and the budget matches the scope the gate runs&lt;/strong&gt; (#6865). &lt;strong&gt;Before:&lt;/strong&gt; every &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; move on a repo that declares a whole-suite review command (this repo’s &lt;code dir=&quot;auto&quot;&gt;make test-fast&lt;/code&gt;) was refused with &lt;code dir=&quot;auto&quot;&gt;timed_out&lt;/code&gt; at the scoped 300 s default; and the recovery the gate advertised — a bounded &lt;code dir=&quot;auto&quot;&gt;pre_review_test_scope&lt;/code&gt; in the WP frontmatter — made the WP unreadable, so the subtask-roster guard failed. &lt;strong&gt;After:&lt;/strong&gt; the key is part of the strict WP model, a whole-declared-command run is bounded by a whole-command budget (1,200 s, or your declared &lt;code dir=&quot;auto&quot;&gt;review.test_timeout_seconds&lt;/code&gt;), a pinned target list keeps the scoped default, and both refusals name the scope shape, the executed command, the policy metadata and the recovery. No gate is weakened.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer keeps generated project command files just because this machine has no global copy&lt;/strong&gt; (#6954). &lt;strong&gt;Before:&lt;/strong&gt; the 3.1.2 migration checked &lt;code dir=&quot;auto&quot;&gt;~/.kittify/missions&lt;/code&gt; and the global command folders, so an &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; on an empty home could keep a generated file another machine removed and still record &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; a successor reads &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;; a stamp at or above 3.1.2 proves a version-marked project command is generated and obsolete, so every machine removes it. Projects without a usable stamp keep the old check, and files without the marker are kept. The global copy is recreated at the next CLI start; the legacy &lt;code dir=&quot;auto&quot;&gt;.codex/prompts&lt;/code&gt; folder is not, because Codex uses skills.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; report one path spelling on every OS&lt;/strong&gt; (#7044). &lt;strong&gt;Before:&lt;/strong&gt; both &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; envelopes, their &lt;code dir=&quot;auto&quot;&gt;Charter:&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;Interview file:&lt;/code&gt; lines, the missing and malformed interview-answers errors, and the &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; family’s output spelled repository-relative paths with the host separator, so Windows showed &lt;code dir=&quot;auto&quot;&gt;.kittify\charter\charter.md&lt;/code&gt; where Linux and macOS showed &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; every repository-relative path those commands report is POSIX, rendered through one seam (&lt;code dir=&quot;auto&quot;&gt;kernel.charter_pack_paths.repo_relative_posix()&lt;/code&gt;); a path outside the repository keeps its native spelling.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A forced &lt;code dir=&quot;auto&quot;&gt;approved -&gt; in_progress&lt;/code&gt; reopen now records a status event hosted sync accepts&lt;/strong&gt; (#6955). &lt;strong&gt;Before:&lt;/strong&gt; reopening an approved work package for rework without &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt; recorded &lt;code dir=&quot;auto&quot;&gt;force: true&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;review_ref: null&lt;/code&gt;, and the row was silently rejected on sync. &lt;strong&gt;After:&lt;/strong&gt; the row cites the established &lt;code dir=&quot;auto&quot;&gt;force-override&lt;/code&gt; rewind marker, a pointerless rewind from &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; is refused before it is appended (as &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; already was), and a supplied &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt; is recorded again — the #6699 edge guard had started refusing it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept --owned-checkout&lt;/code&gt; checks the owned Mission’s implementation&lt;/strong&gt; (#7103, #7099). &lt;strong&gt;Before:&lt;/strong&gt; a real, independently reviewed implementation could be refused because evidence checks read ownership and topology from the primary checkout; stale primary ownership could also hide missing owned ownership. &lt;strong&gt;After:&lt;/strong&gt; evidence checks use the validated owned-checkout authority, while missing implementation, self-review, and missing ownership still fail closed. Owned self-review refusals also use the owned topology’s &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH_REVIEW_NOT_INDEPENDENT&lt;/code&gt; code, even with a stale primary topology. Coordination without an owned checkout keeps PRIMARY authority.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; records a ready coordination-topology mission’s acceptance instead of failing its own tidy-up commit over a keep-local log&lt;/strong&gt; (#7091). &lt;strong&gt;Before:&lt;/strong&gt; acceptance reached readiness &lt;code dir=&quot;auto&quot;&gt;ready&lt;/code&gt; and wrote its metadata, then exited 1 with &lt;code dir=&quot;auto&quot;&gt;safe_commit: refusing to stage path under .worktrees/&lt;/code&gt; because the coordination worktree’s &lt;code dir=&quot;auto&quot;&gt;mission-events.jsonl&lt;/code&gt; was handed to the primary checkout. &lt;strong&gt;After:&lt;/strong&gt; a coordination-worktree residual that is not a mission artifact is left where it lives and named in the acceptance notes, while every classified artifact still commits on its owning surface; the consolidate instructions print and the command exits 0.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A first &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; lands the coordination commit it never received instead of refusing a complete landing&lt;/strong&gt; (#6871, #6857). &lt;strong&gt;Before:&lt;/strong&gt; the late-window projection and its proof ran only on &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt;, so a coordination commit made between the projection gate and the teardown made a first run refuse at the gate, leaving you to hand-assemble a landing that already stood. &lt;strong&gt;After:&lt;/strong&gt; a first run projects everything committed after the coordination tip it captured, commits it on the target, and proves every record byte-identical there before the branch goes. A record it cannot land refuses with &lt;code dir=&quot;auto&quot;&gt;Error code: COORD_LATE_PROJECTION_REFUSED.&lt;/code&gt;, keeps the branch, worktree and marker, and names its repair. A first run that recorded no coordination tip can still lose such a commit with the branch (#7121). &lt;strong&gt;What to do:&lt;/strong&gt; follow the refusal’s repair, then re-run.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A review rewind from &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; now records a status event hosted sync accepts&lt;/strong&gt; (#7080). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent status emit WP01 --to in_progress&lt;/code&gt; (and the &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; transition door) recorded &lt;code dir=&quot;auto&quot;&gt;review_ref: null&lt;/code&gt; even when the caller supplied a structured review result, and a pointerless forced rewind exited 0 — both rows were rejected at sync and the rework never propagated. &lt;strong&gt;After:&lt;/strong&gt; the status emit path records &lt;code dir=&quot;auto&quot;&gt;review_result.reference&lt;/code&gt; as the event’s &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; when no &lt;code dir=&quot;auto&quot;&gt;--review-ref&lt;/code&gt; was given (as &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; already did), a forced &lt;code dir=&quot;auto&quot;&gt;in_review -&gt; in_progress&lt;/code&gt; with no pointer is refused before the append, and &lt;code dir=&quot;auto&quot;&gt;status validate&lt;/code&gt; reports a row written before this fix. &lt;strong&gt;What to do:&lt;/strong&gt; a reviewer’s rewind passes &lt;code dir=&quot;auto&quot;&gt;--review-result-json&lt;/code&gt; (its &lt;code dir=&quot;auto&quot;&gt;reference&lt;/code&gt; is recorded); an operator rewind that is not a review result passes &lt;code dir=&quot;auto&quot;&gt;--review-ref &amp;#x3C;ref&gt;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Claiming a work package no longer invalidates the recorded analysis&lt;/strong&gt; (#7127, #7106). &lt;strong&gt;Before:&lt;/strong&gt; the first &lt;code dir=&quot;auto&quot;&gt;agent action implement WPxx&lt;/code&gt; wrote &lt;code dir=&quot;auto&quot;&gt;base_branch&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;base_commit&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;created_at&lt;/code&gt; into the prompt and the VCS lock into &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, inside the analysis-freshness fingerprint. Every later claim, and every rework re-claim, was refused with &lt;code dir=&quot;auto&quot;&gt;analysis_report_required&lt;/code&gt; until the unchanged &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.analyze&lt;/code&gt; report was re-recorded. &lt;strong&gt;After:&lt;/strong&gt; the fingerprint skips those runtime keys and a rejected work package’s &lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;wp&gt;/&lt;/code&gt; review artifacts. Record the analysis once and claim all work packages. Edits to &lt;code dir=&quot;auto&quot;&gt;subtasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;dependencies&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;requirement_refs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;, a prompt body, or a new work package still make it stale. An unexpected &lt;code dir=&quot;auto&quot;&gt;vcs&lt;/code&gt; value still refuses. A report recorded under an older release after a claim or rework shows stale once after upgrade; re-record it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tracer-append&lt;/code&gt; writes into the checkout that owns the Mission&lt;/strong&gt; (#7081). &lt;strong&gt;Before:&lt;/strong&gt; it resolved the repository root, so from an owned checkout it staged &lt;code dir=&quot;auto&quot;&gt;traces/&amp;#x3C;category&gt;.md&lt;/code&gt; into the primary checkout on protected &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; and refused &lt;code dir=&quot;auto&quot;&gt;PROTECTED_BRANCH_REFUSED&lt;/code&gt;, losing the finding and leaving untracked residue. &lt;strong&gt;After:&lt;/strong&gt; it accepts &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; and adopts the checkout it is invoked from, taking the write root, write branch and mission-scoped protection policy from that owned Mission fact, and refuses a typed owned error before writing anything when the target is invalid. Alternate Mission handles retain the same mission-scoped protected-target opt-in. A non-owned invocation is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Subtask-completion advice now names the work package&lt;/strong&gt; (#7108). &lt;strong&gt;Before:&lt;/strong&gt; copying an unscoped &lt;code dir=&quot;auto&quot;&gt;mark-status T001 --status done&lt;/code&gt; recipe failed when WPs reused the same labels; the surrounding refusal advertised &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;, although manually adding &lt;code dir=&quot;auto&quot;&gt;--wp&lt;/code&gt; already worked. &lt;strong&gt;After:&lt;/strong&gt; the refusal, generated prompts, runbooks and canonical implement/review skill name the WP. Executing the advice records completion against that WP without changing attribution authority or bypassing the gate. Owned checkout paths containing spaces are now quoted as one shell argument in completion commands. &lt;strong&gt;What to do:&lt;/strong&gt; run the scoped advice; replace any explicit runbook placeholders first.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Semantic-check events now record the glossary strictness the generation gate actually enforced&lt;/strong&gt; (#7065). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;SemanticCheckEvaluated&lt;/code&gt; was emitted before the gate resolved strictness, so every event published &lt;code dir=&quot;auto&quot;&gt;effective_strictness: &quot;medium&quot;&lt;/code&gt; and derived &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;strictness != &quot;off&quot;&lt;/code&gt;: a run configured &lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; was logged as a blocking &lt;code dir=&quot;auto&quot;&gt;medium&lt;/code&gt; run, a &lt;code dir=&quot;auto&quot;&gt;max&lt;/code&gt; run was under-stated, and a medium-severity conflict under &lt;code dir=&quot;auto&quot;&gt;medium&lt;/code&gt; was logged as blocked although the gate let it through. &lt;strong&gt;After:&lt;/strong&gt; the gate, the semantic-check middleware and the emitter share one resolution path, so the event carries the configured value (global, mission, step or &lt;code dir=&quot;auto&quot;&gt;--strictness&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; mirrors the gate’s decision. &lt;code dir=&quot;auto&quot;&gt;spec-kitty glossary conflicts --strictness off|medium&lt;/code&gt; lists the conflicts the gate let through with their real type and strictness. Gate behavior is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Core’s generated &lt;code dir=&quot;auto&quot;&gt;tasks/README.md&lt;/code&gt; now passes its encoding check&lt;/strong&gt; (#6877, core part only). &lt;strong&gt;Before:&lt;/strong&gt; the scaffold had a U+2013 en dash that &lt;code dir=&quot;auto&quot;&gt;validate-encoding&lt;/code&gt; refused, and it and a worktree emitter carried a non-ASCII box-drawing tree. &lt;strong&gt;After:&lt;/strong&gt; both use one ASCII-only scaffold; its WP history example matches the pinned pack’s &lt;code dir=&quot;auto&quot;&gt;at:&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;actor:&lt;/code&gt; fields. Guards check rendered text and keep caller-authored characters. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; existing artifacts keep their bytes. Pack-owned spec/plan/task templates are tracked in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-open-packs#112&lt;/code&gt;, and taking that fix needs the operator’s pin decision, so a Mission can still report encoding findings in those files.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;record-analysis --report-only&lt;/code&gt; records over verified ignored pack inputs in the documented &lt;code dir=&quot;auto&quot;&gt;make sync-packs&lt;/code&gt; layout&lt;/strong&gt; (#7128). &lt;strong&gt;Before:&lt;/strong&gt; fetched &lt;code dir=&quot;auto&quot;&gt;packs/&amp;#x3C;name&gt;/&lt;/code&gt; files caused &lt;code dir=&quot;auto&quot;&gt;DIRTY_ANALYSIS_INPUT&lt;/code&gt; because they were deliberately absent from the index. &lt;strong&gt;After:&lt;/strong&gt; a registered in-repository tree is exempt from that untracked-material refusal when its clean tracked sibling pin names the same repo-relative subtree and the canonical offline check verifies both digests without symlinks. Modified trees, uncommitted pins and unrelated ignored inputs still refuse; a refused pin is named alongside pack files. Status-visible dirt is never exempt. Non-mirroring, aliased and nested layouts remain fail-closed pending #7194; the report still hashes tree bytes, not the pin or remote provenance. CI also names both missed contract-reader routes (#7180).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; refuses a worktree that already belongs to a Mission&lt;/strong&gt; (#6956). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission create --owned-checkout &amp;#x3C;path&gt;&lt;/code&gt; admitted a registered coordination worktree or lane worktree, scaffolded the new Mission inside another Mission’s write surface, and let the refusal arrive only afterwards; the read-only startup gates could consult such a checkout too. &lt;strong&gt;After:&lt;/strong&gt; the create claim refuses either worktree up front with &lt;code dir=&quot;auto&quot;&gt;OWNED_CHECKOUT_IS_MISSION_WORKTREE&lt;/code&gt;, before any branch switch, commit or scaffold, and the same refusal covers &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;profile-invocation complete&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;invocations list&lt;/code&gt;. An ordinary linked owned checkout is unaffected, including one under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;, unless its directory name has the lane-worktree shape &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-lane-&amp;#x3C;letters&gt;&lt;/code&gt;: that name is now reserved, and the refusal tells you to rename or move the checkout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An absent lane window no longer sends agents into an impossible retry&lt;/strong&gt; (#7120). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; asked for an unreadable lane branch to be made readable even when that lane never existed. &lt;strong&gt;After:&lt;/strong&gt; Git-confirmed absence gets a local, history-neutral diagnosis shared with &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;. A sibling ref does not prove the missing lane existed: restore only its actual recorded history, never a manufactured branch pointing at target-branch work. With no local lane refs, target-branch execution, pruning and incomplete fetches remain indistinguishable. A lane that never existed has no window to restore; without a verified PR landing, escalate the open evidence-policy question instead of retrying that window. The existing verified-merge route remains available under its unchanged checks. The refusal code, evidence windows and fail-closed gate do not change.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; report unreadable ownership instead of missing implementation&lt;/strong&gt; (#7160; #7149). &lt;strong&gt;Before:&lt;/strong&gt; an approved work package whose task file was missing, unreadable or invalid was refused with &lt;code dir=&quot;auto&quot;&gt;IMPLEMENTATION_MISSING&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;--attest-no-implementation&lt;/code&gt; offered to lift it, leading operators to rewrite history or attest falsely. &lt;strong&gt;After:&lt;/strong&gt; it is refused with &lt;code dir=&quot;auto&quot;&gt;OWNERSHIP_UNRESOLVED&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH_OWNERSHIP_UNRESOLVED&lt;/code&gt;), naming the missing directory, the unreadable file and its error, or the missing id; no attestation lifts it. &lt;code dir=&quot;auto&quot;&gt;accept --owned-checkout&lt;/code&gt; also reads canceled work packages from the owned checkout, the orchestrator-api contract is 1.23.0, and an owned &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; into review refuses an unreadable task file with &lt;code dir=&quot;auto&quot;&gt;OWNED_IMPLEMENTATION_MISSING&lt;/code&gt; (file and error named) instead of a traceback.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --target &amp;#x3C;branch&gt;&lt;/code&gt; now commits the terminus retrospective onto &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;branch&gt;&lt;/code&gt; instead of refusing it&lt;/strong&gt; (#7201). &lt;strong&gt;Before:&lt;/strong&gt; the retrospective bookkeeping commit resolved its destination from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;, so after a &lt;code dir=&quot;auto&quot;&gt;--target&lt;/code&gt; landing &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; warned &lt;code dir=&quot;auto&quot;&gt;HEAD is &apos;&amp;#x3C;branch&gt;&apos;, expected &apos;main&apos;&lt;/code&gt;, refused the commit, and left &lt;code dir=&quot;auto&quot;&gt;retrospective.yaml&lt;/code&gt; plus its &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; append uncommitted for the operator to commit by hand; the suggested recovery, &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission close&lt;/code&gt;, resolved the same stale target and refused too. &lt;strong&gt;After:&lt;/strong&gt; the consolidate run hands the terminus the landing target it already resolved, so both files are committed on that branch with no manual step, and &lt;code dir=&quot;auto&quot;&gt;mission close --target &amp;#x3C;branch&gt;&lt;/code&gt; heals a Mission refused before this fix (the warning now prints it). The commit guard and the fail-open policy are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; stops re-adding the retired &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; merge-driver row&lt;/strong&gt; (#7217, #7174). &lt;strong&gt;Before:&lt;/strong&gt; the first upgrade on a fresh clone appended &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**/issue-matrix.md merge=spec-kitty-issue-matrix&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; and left it dirty, and &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; seeded the same inert row into new projects: the historical &lt;code dir=&quot;auto&quot;&gt;3.2.6_gate_artifact_merge_drivers&lt;/code&gt; migration is clone-local, so it was re-selected on every clone, and nothing writes &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; any more (the canonical artifact is &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt;, whose driver merges JSON rows). &lt;strong&gt;After:&lt;/strong&gt; that migration is superseded; &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_retire_issue_matrix_md_row&lt;/code&gt; keeps the &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; drivers, removes the retired row where it was already written (every other line keeps its bytes and line ending), and leaves a correct &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; byte-identical.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Locked installs no longer trust the compromised emSign G3 certificate chain&lt;/strong&gt; (#7167). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;certifi&lt;/code&gt; 2026.4.22 retained the root affected by GHSA-6q48-6c7w-9gw2. &lt;strong&gt;After:&lt;/strong&gt; the vendor-recommended 2026.10.19 bundle removes it, retains unaffected emSign roots, and includes intervening routine CA updates. Refresh existing locked environments and rebuild images that vendor the old bundle; already-installed environments do not update automatically.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --skip-lanes&lt;/code&gt; can complete a direct-on-target Mission instead of refusing it outright&lt;/strong&gt; (#7209). &lt;strong&gt;Before:&lt;/strong&gt; a Mission with no &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; got a synthesized lanes manifest with no planning commit, so the evidence axis refused every approved work package with &lt;code dir=&quot;auto&quot;&gt;EVIDENCE_WINDOW_UNCOMPUTABLE&lt;/code&gt;, and the recovery advice named a file that Mission does not have. &lt;strong&gt;After:&lt;/strong&gt; the synthesized manifest resolves its evidence-window base from the target branch’s own history — the tip immediately before the commit that introduced &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt; — so the net change since the Mission appeared is judged, and the evidence and review-independence gates are unchanged. An unresolvable window still refuses, with a remedy this topology can perform: commit the Mission’s planning artifacts on the target branch.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;accept --diagnose&lt;/code&gt; keeps readiness visible for corrupt lane metadata and missing coordination worktrees&lt;/strong&gt; (#7222, #7223, #7247). &lt;strong&gt;Before:&lt;/strong&gt; a corrupt &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; aborted diagnosis, and a missing coordination worktree could raise a raw exception. &lt;strong&gt;After:&lt;/strong&gt; diagnosis reports &lt;code dir=&quot;auto&quot;&gt;implementation_evidence skipped: &amp;#x3C;reason&gt;&lt;/code&gt; and exits 0 with a not-ready report and the other blockers. Other modes refuse with &lt;code dir=&quot;auto&quot;&gt;EVIDENCE_WINDOW_UNCOMPUTABLE&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_UNMATERIALIZED&lt;/code&gt; (with its &lt;code dir=&quot;auto&quot;&gt;next_step&lt;/code&gt;). An unreadable status log refuses with &lt;code dir=&quot;auto&quot;&gt;EVIDENCE_STATUS_UNREADABLE&lt;/code&gt;, even under &lt;code dir=&quot;auto&quot;&gt;--diagnose&lt;/code&gt;. Broader CLI recovery is tracked in #7290, separately from API contracts (#7251). &lt;strong&gt;What to do:&lt;/strong&gt; repair the corrupt input, or create the coordination worktree using its &lt;code dir=&quot;auto&quot;&gt;next_step&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --dry-run&lt;/code&gt; under squash no longer refuses a mission branch commit the real squash run lands&lt;/strong&gt; (#7244). &lt;strong&gt;Before:&lt;/strong&gt; the dry run always ran the merge strategy’s per-commit check, so a mission branch commit whose content the squash leaves unchanged on the target was reported as &lt;code dir=&quot;auto&quot;&gt;UNATTRIBUTABLE_CONTENT_FORECAST&lt;/code&gt;, while the real squash run landed the Mission. &lt;strong&gt;After:&lt;/strong&gt; under squash the dry run checks the mission branch’s squashed tree the way the real squash run does (each changed file must carry content an approved work package wrote), and still scans lane commits one by one, because the preview does not fold lanes in yet; &lt;code dir=&quot;auto&quot;&gt;--strategy merge&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--strategy rebase&lt;/code&gt; keep the per-commit check. A check that cannot be completed is reported as &lt;code dir=&quot;auto&quot;&gt;CLAIM_REFUSED_FORECAST&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; records a planning commit for a Mission whose &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; never had one&lt;/strong&gt; (#7210). &lt;strong&gt;Before:&lt;/strong&gt; an in-flight Mission whose &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; predates the planning pin refused every approved work package with &lt;code dir=&quot;auto&quot;&gt;EVIDENCE_WINDOW_UNCOMPUTABLE&lt;/code&gt;. The named remedy failed: plain &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; left the pin empty with a warning, and &lt;code dir=&quot;auto&quot;&gt;--refresh-planning-commit&lt;/code&gt; recorded the live target tip, leaving an empty window. &lt;strong&gt;After:&lt;/strong&gt; with no pin, plain &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; records the target-branch commit just before the Mission’s &lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt; first appeared, as &lt;code dir=&quot;auto&quot;&gt;consolidate --skip-lanes&lt;/code&gt; does (#7209), and reports it as &lt;code dir=&quot;auto&quot;&gt;derived&lt;/code&gt;, if every lane branch contains it. The refusal names this route and warns against &lt;code dir=&quot;auto&quot;&gt;--refresh-planning-commit&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; for an older Mission that refuses, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission finalize-tasks&lt;/code&gt; without flags, then re-run.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --fix&lt;/code&gt; rebuilds &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; with a planning commit the evidence gate can use&lt;/strong&gt; (#7210). &lt;strong&gt;Before:&lt;/strong&gt; rebuilding a missing &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; for a Mission whose work had already started recorded the live target-branch tip as its planning commit, so work already committed on the target branch fell outside the evidence window. &lt;strong&gt;After:&lt;/strong&gt; the rebuild records the commit &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; derives, the one just before the Mission’s &lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt; first appeared on the target branch. When none can be derived it keeps the live tip, reports &lt;code dir=&quot;auto&quot;&gt;lanes_rebuilt_pin_is_target_tip&lt;/code&gt;, and prints a warning. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A busy decisions lock is now a retryable refusal in &lt;code dir=&quot;auto&quot;&gt;doctor decisions --repair&lt;/code&gt;, an owned &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent decision repair-runtime-lock&lt;/code&gt;&lt;/strong&gt; (#7272, #6763). &lt;strong&gt;Before:&lt;/strong&gt; when another command held &lt;code dir=&quot;auto&quot;&gt;decisions/index.json.lock&lt;/code&gt; past the 10 s wait, the first two raised an uncaught &lt;code dir=&quot;auto&quot;&gt;LockAcquireTimeout&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;repair-runtime-lock&lt;/code&gt; said &lt;code dir=&quot;auto&quot;&gt;RUNTIME_LOCK_REPAIR_FAILED&lt;/code&gt; with raw lock text. &lt;strong&gt;After:&lt;/strong&gt; all three report &lt;code dir=&quot;auto&quot;&gt;DECISION_LOCK_TIMEOUT&lt;/code&gt;: the doctor’s &lt;code dir=&quot;auto&quot;&gt;{&quot;ok&quot;: false, &quot;error&quot;: {...}}&lt;/code&gt; envelope (human mode: &lt;code dir=&quot;auto&quot;&gt;Error: [DECISION_LOCK_TIMEOUT] ...&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;next_step&lt;/code&gt;, the repair verb’s &lt;code dir=&quot;auto&quot;&gt;{status, code, message}&lt;/code&gt;. They exit 1 and print no partial report. &lt;strong&gt;What to do:&lt;/strong&gt; match &lt;code dir=&quot;auto&quot;&gt;DECISION_LOCK_TIMEOUT&lt;/code&gt; and retry; for an owned &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;, re-run without &lt;code dir=&quot;auto&quot;&gt;--result&lt;/code&gt;. A held &lt;strong&gt;tracked&lt;/strong&gt; runtime lock still refuses at repair’s preflight (#6836).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor decisions&lt;/code&gt; now names decisions whose event log holds duplicate openings it already tolerates&lt;/strong&gt; (#7272, #6764). &lt;strong&gt;Before:&lt;/strong&gt; concurrent identical &lt;code dir=&quot;auto&quot;&gt;agent decision open&lt;/code&gt; calls, or a retry of one, could append a second &lt;code dir=&quot;auto&quot;&gt;DecisionPointOpened&lt;/code&gt; row; since #4848 the fold reads such a log correctly, but &lt;code dir=&quot;auto&quot;&gt;doctor decisions&lt;/code&gt; reported the Mission clean and said nothing. &lt;strong&gt;After:&lt;/strong&gt; the report adds an informational line naming each such decision, and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; gains a &lt;code dir=&quot;auto&quot;&gt;duplicate_openings_tolerated&lt;/code&gt; list (always present, empty when there is nothing to report). The finding uses the fold’s own rule, so a decision whose openings differ beyond their recorded time is still reported as a malformed fold, never here. The log is left as it is, and neither the exit code, the clean verdict nor &lt;code dir=&quot;auto&quot;&gt;--repair&lt;/code&gt; changes. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; a non-empty list only says the log was written before the fix.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;More repository-root lookups honor &lt;code dir=&quot;auto&quot;&gt;GIT_CEILING_DIRECTORIES&lt;/code&gt; instead of adopting an enclosing checkout&lt;/strong&gt; (#7056, #7022). &lt;strong&gt;Before:&lt;/strong&gt; checkout-identity, mission-metadata, legacy-charter, coordination, gitignore, env-file, ledger-posture, context, charter-lint, next-planner and catalog-diagnosis lookups could climb out of a hermetic tree. &lt;strong&gt;After:&lt;/strong&gt; those walks, the status read root, the worktree-context probe and the &lt;code dir=&quot;auto&quot;&gt;regen&lt;/code&gt; dev-checkout probe share one boundary. Failed Git redirection, ownership or config probes refuse identity backfill instead of minting over an unknown tracked copy. The test-only &lt;code dir=&quot;auto&quot;&gt;stop=&lt;/code&gt; parameter is gone (#7076). Results differ only when the working directory is reached through a symlink. Loop-form walks and the root-walk gate are tracked separately (#7269, #7122, #7056).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; approves a late coordination commit only once every change in it is proved landed&lt;/strong&gt; (#7198, #7199, #7265). &lt;strong&gt;Before:&lt;/strong&gt; only coordination records were checked, so a status event committed on the coordination branch from another checkout, or a late &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; edit, was deleted with the branch at exit 0. A &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; could refuse with &lt;code dir=&quot;auto&quot;&gt;compare-and-swap failed&lt;/code&gt;, so you had to resume twice. &lt;strong&gt;After:&lt;/strong&gt; every change in the window is landed, proved or refused, on a first run and on &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; alike; anything unproved refuses with &lt;code dir=&quot;auto&quot;&gt;Error code: COORD_LATE_PROJECTION_REFUSED.&lt;/code&gt; and keeps the branch, worktree and marker. A resume finishes in one attempt. &lt;strong&gt;What to do:&lt;/strong&gt; follow a refusal’s own repair, then re-run.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A pack skill whose &lt;code dir=&quot;auto&quot;&gt;body_path&lt;/code&gt; leaves its own folder is refused when it is read, not only when it loads&lt;/strong&gt; (#6734; follow-up to #6418). &lt;strong&gt;Before:&lt;/strong&gt; the read that renders &lt;code dir=&quot;auto&quot;&gt;SKILL.md&lt;/code&gt; into your agent folders joined &lt;code dir=&quot;auto&quot;&gt;body_path&lt;/code&gt; with no check, so a symlink swapped after load served a file from outside the skill directory. &lt;strong&gt;After:&lt;/strong&gt; load and read both go through the one containment check, &lt;code dir=&quot;auto&quot;&gt;resolve_relative_path_within_root&lt;/code&gt;. An absolute path, a &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt; part or a symlink pointing outside is refused before anything is read. A contained path to a missing file still reports “not found”. &lt;strong&gt;Changed:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;body_path&lt;/code&gt; such as &lt;code dir=&quot;auto&quot;&gt;nested/../body.md&lt;/code&gt;, whose &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt; resolves back inside, is now refused. &lt;strong&gt;What to do:&lt;/strong&gt; write &lt;code dir=&quot;auto&quot;&gt;body_path&lt;/code&gt; relative to the &lt;code dir=&quot;auto&quot;&gt;.skill.yaml&lt;/code&gt; folder, with no &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter org validate&lt;/code&gt; report an org-pack path that escapes its pack, like &lt;code dir=&quot;auto&quot;&gt;doctor charter-packs&lt;/code&gt;&lt;/strong&gt; (#6733, #6731). &lt;strong&gt;Before:&lt;/strong&gt; for a &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; node whose &lt;code dir=&quot;auto&quot;&gt;body_path&lt;/code&gt; escaped the pack, the doctor exited 1 while &lt;code dir=&quot;auto&quot;&gt;charter status --json&lt;/code&gt; returned &lt;code dir=&quot;auto&quot;&gt;org_layer.errors: []&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter org validate&lt;/code&gt; exited 0, and &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; also missed an escaping asset sidecar &lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; all three report the same finding with the same message. &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; adds it to &lt;code dir=&quot;auto&quot;&gt;org_layer.errors&lt;/code&gt; (no new key), and &lt;code dir=&quot;auto&quot;&gt;charter org validate&lt;/code&gt; reports category &lt;code dir=&quot;auto&quot;&gt;body_path_escape&lt;/code&gt; and exits 1. Each judges the pack against the root it was loaded from, reading the pack registry once. A check that cannot run says so. The doctor’s JSON is unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; fix any path these now report.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;migrate backfill-identity&lt;/code&gt; tell a stray &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; apart from a repository, and name the real repair when Git cannot answer&lt;/strong&gt; (#7262, #7093, #7084, #7131, #7135). &lt;strong&gt;Before:&lt;/strong&gt; any &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; above a Mission folder blocked its identity repair with &lt;code dir=&quot;auto&quot;&gt;TRACKED_META_UNAVAILABLE&lt;/code&gt; and a &lt;code dir=&quot;auto&quot;&gt;git checkout --&lt;/code&gt; that could not work, while a repository that had lost its &lt;code dir=&quot;auto&quot;&gt;HEAD&lt;/code&gt; could be read as nothing tracked. &lt;strong&gt;After:&lt;/strong&gt; an empty or hooks/locks-only &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; is ignored and the identity is written. A repository, or a &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; that is neither (a lost or dangling &lt;code dir=&quot;auto&quot;&gt;HEAD&lt;/code&gt;, other contents, an unreadable entry, a &lt;code dir=&quot;auto&quot;&gt;GIT_DIR&lt;/code&gt;-style override, or Git that cannot start), still refuses. The notice names the &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; and the repair: fix the repository, or remove the residue. &lt;strong&gt;What to do:&lt;/strong&gt; re-run a backfill that was refused only because of such residue.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer refuses a lane’s own dependency merge as content of no approved work package&lt;/strong&gt; (#7307). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;Merge dependency lane X into Y&lt;/code&gt; commit that &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; makes was reported as belonging to no approved work package whenever both lanes touched one file, so the landing and &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; refused. &lt;strong&gt;After:&lt;/strong&gt; a merge is judged by what it adds beyond its parents (&lt;code dir=&quot;auto&quot;&gt;git show --remerge-diff&lt;/code&gt;): a clean merge carries nothing, and a resolution in a lane’s own merge of a declared dependency lane counts as that lane’s work. &lt;strong&gt;Changed:&lt;/strong&gt; a merge that no lane owns and that resolves a conflict by keeping one side is now refused; it used to pass. Judging a merge needs git 2.36 or newer; with older git the gate refuses. A dependency merge counts only when the approval covers it. &lt;strong&gt;What to do:&lt;/strong&gt; nothing, or upgrade git to 2.36 or newer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer refuses a lane as stale for a change the lane already contains&lt;/strong&gt; (#7311). &lt;strong&gt;Before:&lt;/strong&gt; the stale check diffed the Mission branch from a single merge base, which on a lane that depends on another lane could be an older base, so the dependency’s change looked missing and the lane was refused. &lt;strong&gt;After:&lt;/strong&gt; a Mission-branch path counts as overlapping only when a commit the lane does not contain changed it (a merge counts only for what its own resolution introduced). A genuine overlap still refuses, and a failed probe falls back to the stricter merge-base diff.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Status reads go through one read door&lt;/strong&gt; (#7277). &lt;strong&gt;Before:&lt;/strong&gt; readers resolved a Mission’s status through several path helpers, and an empty coordination worktree could read as an empty history. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;status/read_surface.py::resolve_status_read&lt;/code&gt; picks one source per topology and coordination state (ADR &lt;code dir=&quot;auto&quot;&gt;2026-11-06-2&lt;/code&gt;): the coordination branch, the Mission branch or the checkout that holds it, or the target once the Mission has landed; consolidation’s status readers use it, and &lt;code dir=&quot;auto&quot;&gt;materialize&lt;/code&gt; on a ref-sourced status exits 1 with &lt;code dir=&quot;auto&quot;&gt;status_surface_on_ref&lt;/code&gt; and a remedy. &lt;strong&gt;What to do:&lt;/strong&gt; read status with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status&lt;/code&gt;, never from a lane checkout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; gate counts commits on the lane branch&lt;/strong&gt; (#7278). &lt;strong&gt;Before:&lt;/strong&gt; its verdict depended on a guess about the checkout topology and on whether a lane checkout existed. &lt;strong&gt;After:&lt;/strong&gt; it counts &lt;code dir=&quot;auto&quot;&gt;git rev-list &amp;#x3C;base&gt;..refs/heads/&amp;#x3C;lane&gt;&lt;/code&gt; from the repository root, with the same verdict on every surface, and a missing lane branch refuses with &lt;code dir=&quot;auto&quot;&gt;LANE_BRANCH_MISSING&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission branches are bounded by per-work-package approval windows&lt;/strong&gt; (#7283). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission landed its Mission branch without checking commits against approvals. &lt;strong&gt;After:&lt;/strong&gt; consolidation runs the approval-stamp check on the Mission branch and refuses with &lt;code dir=&quot;auto&quot;&gt;LANE_MOVED_AFTER_APPROVAL&lt;/code&gt; any content commit that lies in no approved work package’s window, from its first claim stamp to its newest approval stamp, naming the work package approved before it. &lt;strong&gt;What to do:&lt;/strong&gt; rework, review and approve that work package again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Owned &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; Missions can advance from their canonical coordination status directory&lt;/strong&gt; (#6788). &lt;strong&gt;Before:&lt;/strong&gt; prompt governance refused the canonical status path whenever it differed from the primary Mission directory. &lt;strong&gt;After:&lt;/strong&gt; it accepts only that same owned Mission’s primary or canonical status directory, keeps the primary charter anchor, and continues refusing foreign directories.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; on a repository with no commits names a remedy that works&lt;/strong&gt; (#7342). &lt;strong&gt;Before:&lt;/strong&gt; the refusal said to run &lt;code dir=&quot;auto&quot;&gt;git commit --allow-empty -m &apos;Initial commit&apos;&lt;/code&gt;, which leaves the files &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; wrote uncommitted, so the next &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; was refused with &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_DIRTY&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it says &lt;code dir=&quot;auto&quot;&gt;git add -- . &amp;#x26;&amp;#x26; git commit -m &apos;Initial commit&apos;&lt;/code&gt;, and offers the empty commit only when there is nothing to commit, as the getting-started tutorial already did.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; claims a work package of a default &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; Mission&lt;/strong&gt; (#7372). &lt;strong&gt;Before:&lt;/strong&gt; on a Mission created without &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; and settled to &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; refused at “Validate planning state” with &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_PATH_POLICY&lt;/code&gt;, then at workspace allocation with a HEAD mismatch, and &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; reported the lane’s inherited planning files as contamination, so no work package could be claimed or handed to review without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; and hand commits. &lt;strong&gt;After:&lt;/strong&gt; until the Mission lands, the planning-artifact commit and the claim commit run in the checkout that holds the Mission’s topic branch (the coordination worktree), and the lane-hygiene check measures the lane against that topic branch, as the placement seam resolves the PRIMARY partition there.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter consistency-check&lt;/code&gt; now resolves project-layer activated artifacts through the layered authority its readers use&lt;/strong&gt; (#6749). &lt;strong&gt;Before:&lt;/strong&gt; the known-id catalog passed only the org chain to &lt;code dir=&quot;auto&quot;&gt;list_available&lt;/code&gt;, so a project-layer mission type — resolved by the runtime roster, shown as &lt;code dir=&quot;auto&quot;&gt;source_layer: project&lt;/code&gt; by &lt;code dir=&quot;auto&quot;&gt;charter mission-type list&lt;/code&gt; — was reported &lt;code dir=&quot;auto&quot;&gt;mission-type/&amp;#x3C;id&gt;: Not found in doctrine&lt;/code&gt;, exit 1. &lt;strong&gt;After:&lt;/strong&gt; the catalog passes the canonical project-layer roots and &lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt; membership comes from the same layered roster the runtime and &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;’s preflight use, read once per run. Unknown ids are still reported and an unreadable &lt;code dir=&quot;auto&quot;&gt;mission_types/&lt;/code&gt; layer fails closed with a &lt;code dir=&quot;auto&quot;&gt;verification_errors&lt;/code&gt; entry. &lt;strong&gt;What to do:&lt;/strong&gt; nothing. &lt;code dir=&quot;auto&quot;&gt;charter activate mission-type&lt;/code&gt; still refuses such a type from the same project-blind scan; tracked separately.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate &amp;#x3C;kind&gt; &amp;#x3C;id&gt; --cascade&lt;/code&gt; resolves every cascaded artifact’s file name once, not once per artifact&lt;/strong&gt; (#6777). &lt;strong&gt;Before:&lt;/strong&gt; the cascade mapped each artifact it reached from one DRG URN to its config file name with its own fresh identity pass, re-walking and re-parsing the whole doctrine catalog for every artifact: a full &lt;code dir=&quot;auto&quot;&gt;--cascade all&lt;/code&gt; walk from one directive (114 artifacts across six kinds) parsed 5,028 artifact files and took 70–95 s on a development host, and the charter activation test that drives it crossed the 240 s per-test timeout on a slower CI runner. &lt;strong&gt;After:&lt;/strong&gt; the whole target batch shares one read-only identity pass, resolved before the first activation write — 240 parses for the same walk, ~0.62–0.70× the wall clock, the same activation lists in the same order, and no change to what the command prints.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A lifecycle payload the published contract rejects is now refused at emit time instead of being written&lt;/strong&gt; (#6438). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;MissionReopened&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;FollowUpRecorded&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ReviewerSelfApproval&lt;/code&gt; were written to &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; from a hand-built dict, so a field the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; model rejects — an empty &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;recorded_by&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;failure_reason&lt;/code&gt; — reached the status event log and was only caught later by a consumer. &lt;strong&gt;After:&lt;/strong&gt; the three emitters build &lt;code dir=&quot;auto&quot;&gt;MissionReopenedPayload&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;FollowUpRecordedPayload&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ReviewerSelfApprovalPayload&lt;/code&gt;, so such a payload raises at emit time and nothing is appended, while a valid emit persists the same row as before and existing lines are never rewritten. &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission reopen --reason &quot;&quot;&lt;/code&gt; now refuses with &lt;code dir=&quot;auto&quot;&gt;reason_required&lt;/code&gt; and writes nothing. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; give &lt;code dir=&quot;auto&quot;&gt;mission reopen&lt;/code&gt; a non-empty &lt;code dir=&quot;auto&quot;&gt;--reason&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A declared-command run that fails opaquely is no longer reported as no new failures&lt;/strong&gt; (#7377, #6751). &lt;strong&gt;Before:&lt;/strong&gt; every unparseable nonzero result had the placeholder identity &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;declared-command&gt;&lt;/code&gt;, and the gate matched failures by name only, so a candidate that failed for a different reason than the baseline passed as &lt;code dir=&quot;auto&quot;&gt;no_new_failures&lt;/code&gt;, with no exit status on the verdict. &lt;strong&gt;After:&lt;/strong&gt; an opaque failure’s identity is its exit status plus a digest of the run’s full output; it is pre-existing only when both match, and a differing one is a new failure. The verdict records the candidate’s observed exit status and says that a &lt;code dir=&quot;auto&quot;&gt;no_new_failures&lt;/code&gt; result is baseline-relative. Named &lt;code dir=&quot;auto&quot;&gt;FAIL &amp;#x3C;name&gt;&lt;/code&gt; and JUnit failures keep name-based matching; an older baseline still loads but cannot verify-equal a known candidate. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A workflow call no longer parses the whole doctrine catalog&lt;/strong&gt; (#6462). &lt;strong&gt;Before:&lt;/strong&gt; every charter context render (&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action &amp;#x3C;step&gt;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --action &amp;#x3C;step&gt;&lt;/code&gt;) parsed all eight built-in doctrine domains (265 documents in this repository’s pack), although the governance resolution reads only paradigms, directives and template sets. &lt;strong&gt;After:&lt;/strong&gt; the render parses only those three domains (52 documents). Rendered context and resolved governance selections are unchanged, and there is no new cache or flag.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Refused &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; runs no longer accumulate failed staging directories without bound&lt;/strong&gt; (#6723). &lt;strong&gt;Before:&lt;/strong&gt; every refusal preserved &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/.staging/&amp;#x3C;run_id&gt;.failed/&lt;/code&gt; for diagnosis and nothing pruned them, so a repeatedly-refused project — exactly what an agent retrying the implement gate’s remedy produces — grew one directory per attempt (#4226 counted 15, then 16). &lt;strong&gt;After:&lt;/strong&gt; the newest 3 are kept and older ones are removed as the next refusal is preserved; the failure the command just reported is never removed, a live &lt;code dir=&quot;auto&quot;&gt;.staging/&amp;#x3C;run_id&gt;/&lt;/code&gt; is never touched, and the refusal hint says how many are kept. Nothing to do: a tree that already holds more than 3 is brought down to 3 by the next refusal.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; and read-surface walk asks one rule whether a &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; folder is a Mission, so a leftover folder is no longer reported as a broken Mission&lt;/strong&gt; (#7380, #6758). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;doctor topology&lt;/code&gt; printed a folder with no &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; as a Mission with &lt;code dir=&quot;auto&quot;&gt;topology: null&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;meta.json not found&lt;/code&gt;, while &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; called it residue; &lt;code dir=&quot;auto&quot;&gt;doctor coordination&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor review-cycle-reconcile&lt;/code&gt; scans, &lt;code dir=&quot;auto&quot;&gt;materialize&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; in-flight warning and &lt;code dir=&quot;auto&quot;&gt;release prep&lt;/code&gt;’s changelog block decided for themselves too. &lt;strong&gt;After:&lt;/strong&gt; all six use the read-side predicate Mission selection uses, so the folder gets no topology row, finding, derived view, coordination probe, in-flight warning or release-notes entry, and &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt; remains the one reporter, with a reason and a remedy. &lt;strong&gt;What to do:&lt;/strong&gt; nothing; a repository with no leftover folders behaves as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A planning-lane work package’s pre-review gate record no longer claims nothing changed&lt;/strong&gt; (#7384, #6792). &lt;strong&gt;Before:&lt;/strong&gt; moving a &lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; work package to &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; after committing its deliverables recorded outcome &lt;code dir=&quot;auto&quot;&gt;no_coverage&lt;/code&gt; with reason &lt;code dir=&quot;auto&quot;&gt;no changed files detected for this WP — skipping the gate cheaply&lt;/code&gt;. Such a work package commits in the repository root checkout, on the branch the gate diffs against, so its merge-base diff is empty by construction and the reason contradicted the commit. &lt;strong&gt;After:&lt;/strong&gt; the gate still skips cheaply, never dispatches and never blocks, but records &lt;code dir=&quot;auto&quot;&gt;planning-lane WP — committed diff not inspected (a planning_artifact WP commits in the repository root checkout, on the branch the gate diffs against, so no workspace diff exists)&lt;/code&gt;. Other work packages keep the previous wording, and the gate still does not inspect a planning-lane commit (#6851).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty plugin build&lt;/code&gt; manifests now meet the Claude, Codex/OpenAI and Copilot directory requirements&lt;/strong&gt; (#7386, #6479). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;codex&lt;/code&gt; manifest had a PEP 440 version (&lt;code dir=&quot;auto&quot;&gt;4.0.0rc8&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;skills/&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;./&lt;/code&gt;, a 34-character short description and no listing fields; the &lt;code dir=&quot;auto&quot;&gt;claude-code&lt;/code&gt; manifest redeclared the default &lt;code dir=&quot;auto&quot;&gt;hooks/hooks.json&lt;/code&gt;; no manifest named a homepage, repository or license; and Copilot/VS Code got &lt;code dir=&quot;auto&quot;&gt;version: 0.0.0&lt;/code&gt; and an unknown &lt;code dir=&quot;auto&quot;&gt;distribution_target&lt;/code&gt; key. &lt;strong&gt;After:&lt;/strong&gt; every version is SemVer (&lt;code dir=&quot;auto&quot;&gt;4.0.0-rc8&lt;/code&gt;); the Codex manifest has &lt;code dir=&quot;auto&quot;&gt;./&lt;/code&gt; paths, the 30-character limit, the listing fields and the logo it declares (shipped in the wheel); every manifest carries the links and &lt;code dir=&quot;auto&quot;&gt;license: MIT&lt;/code&gt;; Copilot/VS Code get an Agent Plugins 1.0.0 manifest. &lt;strong&gt;What to do:&lt;/strong&gt; delete a stale &lt;code dir=&quot;auto&quot;&gt;dist/spec-kitty-plugins/&lt;/code&gt; and rebuild.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The lifecycle event vocabulary now has one owner&lt;/strong&gt; (#6447). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;specify_cli/status/lifecycle_events.py&lt;/code&gt; hand-copied the twelve event-type strings from &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;, so the copy could drift from the package that owns it. &lt;strong&gt;After:&lt;/strong&gt; the twelve names are imported from &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --audit&lt;/code&gt; no longer flags &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;UNKNOWN_SHAPE&lt;/code&gt;&lt;/strong&gt; (#6111). &lt;strong&gt;Before:&lt;/strong&gt; the audit’s &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; key list was hand-written and lacked &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt;, so every reducer-written snapshot produced an info-level finding (216 across the 779 missions in this repository). &lt;strong&gt;After:&lt;/strong&gt; the known keys are derived from &lt;code dir=&quot;auto&quot;&gt;StatusSnapshot&lt;/code&gt;, the snapshot writer, so the reducer’s own keys are known.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The orchestrator API answers a refused status write with JSON, not a traceback&lt;/strong&gt; (#5642, #5156). &lt;strong&gt;Before:&lt;/strong&gt; a refused status write in &lt;code dir=&quot;auto&quot;&gt;start-implementation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;start-review&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;transition&lt;/code&gt; (policy refusal, lock timeout, unresolvable worktree, &lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_DIVERGED&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_UNREADABLE&lt;/code&gt;), or a &lt;code dir=&quot;auto&quot;&gt;StatusReadPathNotFound&lt;/code&gt;, escaped as a traceback with empty stdout. &lt;strong&gt;After:&lt;/strong&gt; one JSON envelope with a non-zero exit. A refused write reports &lt;code dir=&quot;auto&quot;&gt;BOOKKEEPING_FAILED&lt;/code&gt; with the cause in &lt;code dir=&quot;auto&quot;&gt;data.bookkeeping_error_code&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;BOOKKEEPING_LOCK_TIMEOUT&lt;/code&gt; means retry; &lt;code dir=&quot;auto&quot;&gt;BOOKKEEPING_POLICY_REFUSED&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_DIVERGED&lt;/code&gt; means an operator must act. A read-path refusal keeps &lt;code dir=&quot;auto&quot;&gt;STATUS_READ_PATH_NOT_FOUND&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;data.coord_candidate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;data.primary_candidate&lt;/code&gt;. API contract &lt;code dir=&quot;auto&quot;&gt;1.26.0&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; key on &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt;, then &lt;code dir=&quot;auto&quot;&gt;data.bookkeeping_error_code&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An artifact with no authored id is skipped by the offering catalog&lt;/strong&gt; (#4856). &lt;strong&gt;Before:&lt;/strong&gt; the catalog fell back to the filename stem for its identity, the one remaining spot that inferred identity from a cosmetic kebab slug. &lt;strong&gt;After:&lt;/strong&gt; identity comes from the authored &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; alone; an artifact that declares none is skipped. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;load_org_pack&lt;/code&gt; honors a declared &lt;code dir=&quot;auto&quot;&gt;pack_drg&lt;/code&gt; pointer&lt;/strong&gt; (#6059). &lt;strong&gt;Before:&lt;/strong&gt; the org-pack runtime loader always read &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt;, so an org pack pointing &lt;code dir=&quot;auto&quot;&gt;pack_drg&lt;/code&gt; elsewhere loaded the wrong file (or nothing). &lt;strong&gt;After:&lt;/strong&gt; the pointer wins and the convention path is only the fallback when it is absent. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;section:*&lt;/code&gt; prompt stanzas come from the one fetch-stanza composer&lt;/strong&gt; (#3093). &lt;strong&gt;Before:&lt;/strong&gt; the action-critical section renderer hand-rolled the pair and emitted &lt;code dir=&quot;auto&quot;&gt;When you …&lt;/code&gt; lines that did not match the closed prompt-governance lead-in set. &lt;strong&gt;After:&lt;/strong&gt; it delegates to the canonical composer, so every stanza is normalized. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The runtime prompt path renders the SPDD/REASONS block&lt;/strong&gt; (#5129). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; inserted the built-in template raw, so the agent-facing prompt showed the &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;!-- spdd:reasons-block --&gt;&lt;/code&gt; marker comments verbatim, and with SPDD inactive the block that should have been removed. &lt;strong&gt;After:&lt;/strong&gt; it applies the same renderer the slash-command and skills paths use. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;$HOME&lt;/code&gt; with a &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt; segment or a relative &lt;code dir=&quot;auto&quot;&gt;$HOME&lt;/code&gt; no longer crashes the runtime bootstrap with a &lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt;&lt;/strong&gt; (#6176). &lt;strong&gt;Before:&lt;/strong&gt; the global reporting anchor was built from the unnormalized &lt;code dir=&quot;auto&quot;&gt;Path.home()&lt;/code&gt;, so the runtime bootstrap died with &lt;code dir=&quot;auto&quot;&gt;ValueError: Root requires an identity and an absolute normalized path&lt;/code&gt; (exit 1). &lt;strong&gt;After:&lt;/strong&gt; the anchor is normalized, so the crash is gone; such a &lt;code dir=&quot;auto&quot;&gt;$HOME&lt;/code&gt; is still refused with a named &lt;code dir=&quot;auto&quot;&gt;runtime_bootstrap&lt;/code&gt; diagnostic (exit 1) because the global destinations themselves are not yet normalized (#6176 stays open). &lt;strong&gt;What to do:&lt;/strong&gt; spell &lt;code dir=&quot;auto&quot;&gt;$HOME&lt;/code&gt; as an absolute path without &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt; segments.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Non-interactive git contacts can no longer open a GUI askpass dialog&lt;/strong&gt; (#5860). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;GIT_TERMINAL_PROMPT=0&lt;/code&gt; was set but &lt;code dir=&quot;auto&quot;&gt;GIT_ASKPASS&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;SSH_ASKPASS&lt;/code&gt; stayed set (also with &lt;code dir=&quot;auto&quot;&gt;GIT_SSH&lt;/code&gt;), so a helper such as the VS Code askpass could open a credential dialog. &lt;strong&gt;After:&lt;/strong&gt; both are cleared for every remote contact: origin-freshness reads, charter-pack git sources (clone, tag and subtree fetch), and pack fetch and vendor. &lt;strong&gt;What to do:&lt;/strong&gt; CI that authenticates through askpass should use a non-interactive &lt;code dir=&quot;auto&quot;&gt;credential.helper&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;http.extraHeader&lt;/code&gt;); spec-kitty leaves those alone. &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK=warn&lt;/code&gt; only relaxes the origin-freshness gates; the &lt;code dir=&quot;auto&quot;&gt;ORIGIN_UNREACHABLE&lt;/code&gt; remedy says the same.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The atomic YAML temp-file create is hardened against symlinks&lt;/strong&gt; (#4847). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;write_mapping_atomic&lt;/code&gt; created its temp file with a bare &lt;code dir=&quot;auto&quot;&gt;os.open&lt;/code&gt;, which already refused a pre-planted symlink on POSIX and Windows because &lt;code dir=&quot;auto&quot;&gt;O_CREAT|O_EXCL&lt;/code&gt; fails on it. &lt;strong&gt;After:&lt;/strong&gt; the temp file is created through &lt;code dir=&quot;auto&quot;&gt;kernel.no_follow.open_no_follow&lt;/code&gt;, the shared symlink-refusing open primitive, as defence-in-depth hardening. On a platform without &lt;code dir=&quot;auto&quot;&gt;O_NOFOLLOW&lt;/code&gt;, a refusal now raises the named &lt;code dir=&quot;auto&quot;&gt;NoFollowPathError&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Clearer bookkeeping commits&lt;/strong&gt; (#4610, #4837, #5319). &lt;strong&gt;Before:&lt;/strong&gt; a benign empty changeset was detected by matching the error text, so new wording could make it a failure. Implicit subjects named only the operation (&lt;code dir=&quot;auto&quot;&gt;chore(spec-kitty): status transition batch WP01&lt;/code&gt;), so Missions’ commits looked alike. The protected-branch refusal offered &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS=1&lt;/code&gt; unlabeled, hiding the branch remedy. &lt;strong&gt;After:&lt;/strong&gt; empty changesets are detected by error type, with text match as fallback. Subjects name the staged areas, e.g. &lt;code dir=&quot;auto&quot;&gt;chore(spec-kitty): status transition batch WP01 (kitty-specs/&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;)&lt;/code&gt;. The refusal and &lt;code dir=&quot;auto&quot;&gt;REMEDY_PROTECTED_PRIMARY&lt;/code&gt; name the topic branch first (e.g. &lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit &amp;#x3C;files&gt; -m &amp;#x3C;message&gt; --to-branch &amp;#x3C;branch&gt;&lt;/code&gt;; only it has that flag) and label the env var an operator-only override.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor bytecode-cache&lt;/code&gt; no longer flags a stale checked-hash pyc&lt;/strong&gt; (#4531). &lt;strong&gt;Before:&lt;/strong&gt; a pyc compiled with &lt;code dir=&quot;auto&quot;&gt;--invalidation-mode checked-hash&lt;/code&gt; was trusted on its flags alone, so its body was checked even when its source had changed, and a stale cache that Python would simply recompile could be reported as corrupt. &lt;strong&gt;After:&lt;/strong&gt; a checked-hash pyc is trusted only when its embedded hash equals &lt;code dir=&quot;auto&quot;&gt;importlib.util.source_hash&lt;/code&gt; of the current source; a stale one is left alone, because Python revalidates the hash on import and recompiles on mismatch. An unchecked-hash pyc is still trusted, as Python trusts it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor decisions&lt;/code&gt; now reports unreadable ledger lines instead of silently skipping them&lt;/strong&gt; (#5304). &lt;strong&gt;Before:&lt;/strong&gt; a corrupt line in the decisions event ledger crashed the command with a traceback (invalid JSON, a non-object row, or a non-object payload), or was silently skipped (a missing or null payload, or a missing decision point id), so &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; reported a clean state and &lt;code dir=&quot;auto&quot;&gt;--repair&lt;/code&gt; could “succeed” over input it never read. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;clean&lt;/code&gt; surfaces the unreadable lines with their line numbers and reasons (a human warning and an &lt;code dir=&quot;auto&quot;&gt;unreadable_lines&lt;/code&gt; JSON key), and &lt;code dir=&quot;auto&quot;&gt;--repair&lt;/code&gt; refuses to run, writing nothing and exiting 1, until the ledger is fixed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent config lint-hooks&lt;/code&gt; no longer crashes or substitutes defaults on a corrupt &lt;code dir=&quot;auto&quot;&gt;.cursor/hooks.json&lt;/code&gt;&lt;/strong&gt; (#5293). &lt;strong&gt;Before:&lt;/strong&gt; a UTF-8 decoding error raised an unhandled exception, and a syntactically valid non-object JSON document silently fell back to the default hook configuration. &lt;strong&gt;After:&lt;/strong&gt; both are reported as an unreadable-hooks warning and the command moves on without linting hooks against invented data.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;migrate repair-mission-meta&lt;/code&gt; no longer mints a fresh mission id over a tracked, id-less &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;&lt;/strong&gt; (#6833). &lt;strong&gt;Before:&lt;/strong&gt; when git tracked a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; that carried no &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;, the repair minted a brand-new ULID into it, silently diverging from the identity the repository had recorded. &lt;strong&gt;After:&lt;/strong&gt; the repair reuses the tracked mission id when the tracked file carries a canonical ULID, and refuses, recording a validation error and writing nothing, when the tracked file is unavailable; a present-but-corrupt meta still fails loudly at read time. &lt;strong&gt;Behavior change:&lt;/strong&gt; a tracked copy that is index-only, differs from the index (a staged edit), is corrupt, or cannot be read from &lt;code dir=&quot;auto&quot;&gt;HEAD&lt;/code&gt;, and a legacy non-ULID id while &lt;code dir=&quot;auto&quot;&gt;HEAD&lt;/code&gt; is unavailable, now refuse where the repair used to mint a new id.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;issue-matrix migrate&lt;/code&gt; no longer silently drops rows with an unknown verdict&lt;/strong&gt; (#5453). &lt;strong&gt;Before:&lt;/strong&gt; a matrix row whose verdict matched no known value was filtered out of the migration with no diagnostic reaching the operator. &lt;strong&gt;After:&lt;/strong&gt; the mission is refused and listed under &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty issue-matrix migrate --json&lt;/code&gt; carries the reason, naming each dropped row and the allowed verdicts, in &lt;code dir=&quot;auto&quot;&gt;skip_reasons&lt;/code&gt;; the command still exits 0 so one bad mission does not stop the sweep.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;migrate backfill-runtime-state --dry-run&lt;/code&gt; no longer labels a would-fail mission “Skipped (already migrated)”&lt;/strong&gt; (#4044). &lt;strong&gt;Before:&lt;/strong&gt; a mission whose fail-closed verify refused (for example a phantom work-package row injected into the event ledger) would neither flip nor seed, so the dry-run summary counted it under “Skipped (already migrated)” — although a live run reports it as Failed. &lt;strong&gt;After:&lt;/strong&gt; the dry-run Skipped bucket counts only missions that are genuinely already migrated; a mission that would fail a live run lands in no bucket rather than under a label that lies.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lane and recovery correctness fixes&lt;/strong&gt; (QW4, #7395). Six corrections across lane-id minting, the claim-ancestry gate, crash recovery and single-branch landing docs:
&lt;ul&gt;
&lt;li&gt;Per-lane test database names respect PostgreSQL’s 63-byte identifier cap (#3122). &lt;strong&gt;Before:&lt;/strong&gt; a long mission slug composed a name the engine silently truncated, collapsing distinct lanes into one database. &lt;strong&gt;After:&lt;/strong&gt; an over-long name is truncated to 63 bytes with a stable sha1 digest suffix, so distinct &lt;code dir=&quot;auto&quot;&gt;(mission, lane)&lt;/code&gt; pairs stay distinct. An existing lane whose name was over 63 bytes gets a new database name, so its old test database is orphaned and can be dropped.&lt;/li&gt;
&lt;li&gt;A failure of the claim-ancestry gate’s recheck self-heal surfaces as the structured &lt;code dir=&quot;auto&quot;&gt;ANCESTRY_NOT_ESTABLISHED&lt;/code&gt; refusal at every claim seam (#3763). &lt;strong&gt;Before:&lt;/strong&gt; the original exception escaped raw — a traceback at the &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; CLI seam, a non-JSON crash at the &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; boundary. &lt;strong&gt;After:&lt;/strong&gt; the gate wraps it in &lt;code dir=&quot;auto&quot;&gt;AncestryNotEstablishedError&lt;/code&gt; (the original failure chained as &lt;code dir=&quot;auto&quot;&gt;__cause__&lt;/code&gt;), and both seams render the structured envelope and exit non-zero.&lt;/li&gt;
&lt;li&gt;Crash recovery globs &lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt; once per scan instead of once per candidate work package (#4523). &lt;strong&gt;Before:&lt;/strong&gt; an N-WP mission ran N directory scans while computing &lt;code dir=&quot;auto&quot;&gt;ready_to_start&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; one sorted glob builds an id-to-file map consulted per WP; the first match is now deterministic (sorted order) instead of OS-order arbitrary.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;_list_mission_branches&lt;/code&gt; recognizes a mission’s branches through the canonical branch-name parser instead of trusting the glob’s prefix (#5152). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;kitty/mission-057-foo*&lt;/code&gt; also listed &lt;code dir=&quot;auto&quot;&gt;kitty/mission-057-foobar-lane-a&lt;/code&gt; — a different mission whose slug merely shares a prefix — so recovery could scan and act on a sibling mission’s branches. &lt;strong&gt;After:&lt;/strong&gt; only branches that parse to the exact recorded slug (or its &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; recombination) are listed.&lt;/li&gt;
&lt;li&gt;Lane-id minting fails closed when all 26 positional ids are claimed (#5155). &lt;strong&gt;Before:&lt;/strong&gt; the minting loop walked past &lt;code dir=&quot;auto&quot;&gt;z&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;{&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;|&lt;/code&gt; and beyond, silently minting ids like &lt;code dir=&quot;auto&quot;&gt;lane-{&lt;/code&gt; that match no lane-id grammar. &lt;strong&gt;After:&lt;/strong&gt; it raises &lt;code dir=&quot;auto&quot;&gt;LaneIdExhaustedError&lt;/code&gt; (error code &lt;code dir=&quot;auto&quot;&gt;LANE_ID_EXHAUSTED&lt;/code&gt;), so an over-wide mission is refused loudly instead of persisting malformed ids.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;is_single_branch_mission&lt;/code&gt;’s docstring no longer claims &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuses an unmigrated single-branch mission with code lanes (#7250). &lt;strong&gt;Before:&lt;/strong&gt; it said &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH_CODE_LANES_UNMIGRATED&lt;/code&gt; trips first — no consolidation path runs that check. &lt;strong&gt;After:&lt;/strong&gt; the docstring names the real callers (finalize-tasks, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s lane allocation, the review gate) and states that &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; does not run the check.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--allow-fail&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; now exits 0 instead of 1&lt;/strong&gt; (#3084). &lt;strong&gt;Before:&lt;/strong&gt; a not-ready acceptance summary printed the checklist but still exited 1, so &lt;code dir=&quot;auto&quot;&gt;--allow-fail&lt;/code&gt; was indistinguishable from a plain failure to any caller gating on the exit code. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--allow-fail&lt;/code&gt; is report-only — it prints the same checklist and exits 0 — while a plain &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; still refuses with exit 1. &lt;code dir=&quot;auto&quot;&gt;--mode checklist&lt;/code&gt; is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks add-history&lt;/code&gt; can read the note from a file or stdin&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;--note-file&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;-&lt;/code&gt; for stdin) (#2708). &lt;strong&gt;Before:&lt;/strong&gt; the note had to be inlined in &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt;, so a shell-based orchestrator passed through shell expansion and mangled literal Markdown backticks and &lt;code dir=&quot;auto&quot;&gt;$(…)&lt;/code&gt; before the CLI saw them. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--note-file NOTES.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;git show -s --format=%B | spec-kitty agent tasks add-history WP01 --note-file -&lt;/code&gt; record the note verbatim; &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; stays the simple inline door, and passing both (or neither) is refused before any write.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty intake --clear&lt;/code&gt; is the canonical brief-intake cleanup&lt;/strong&gt; (#706). &lt;strong&gt;Before:&lt;/strong&gt; the specify step’s brief-intake mode deleted &lt;code dir=&quot;auto&quot;&gt;.kittify/mission-brief.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kittify/brief-source.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kittify/ticket-context.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/pending-origin.yaml&lt;/code&gt; with four raw &lt;code dir=&quot;auto&quot;&gt;rm -f&lt;/code&gt; lines in the prompt. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty intake --clear&lt;/code&gt; removes exactly those artifacts (idempotent, exit 0 when there is nothing to clear, files outside that set untouched). The specify prompt still uses the &lt;code dir=&quot;auto&quot;&gt;rm -f&lt;/code&gt; lines until the built-in pack switches to the command.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --include&lt;/code&gt; accepts several selectors, and refuses a comma&lt;/strong&gt; (#3261). &lt;strong&gt;Before:&lt;/strong&gt; a repeated &lt;code dir=&quot;auto&quot;&gt;--include&lt;/code&gt; silently kept only the last selector, and &lt;code dir=&quot;auto&quot;&gt;--include a,b&lt;/code&gt; resolved the whole tail as one bogus id (“No agent_profile found for selector ’…,&lt;id&gt;’”). &lt;strong&gt;After:&lt;/strong&gt; the flag is repeatable and every selector is rendered, a comma-containing selector fails loudly with the correct one-selector-per-flag syntax, and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; lists the selectors under &lt;code dir=&quot;auto&quot;&gt;include&lt;/code&gt;. With &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;include&lt;/code&gt; keeps its string value (the first selector) and a new &lt;code dir=&quot;auto&quot;&gt;includes&lt;/code&gt; key lists every selector.&lt;/id&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent issue-verdict&lt;/code&gt; can set the issue title&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;--title&lt;/code&gt;) (#7348). &lt;strong&gt;Before:&lt;/strong&gt; recording a verdict left the row’s placeholder title in place, with no CLI way to fill it. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--title &quot;…&quot;&lt;/code&gt; stamps the title on the row (creating or replacing it) while an omitted &lt;code dir=&quot;auto&quot;&gt;--title&lt;/code&gt; preserves the existing one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status&lt;/code&gt; reads &lt;code dir=&quot;auto&quot;&gt;dependencies:&lt;/code&gt; through the canonical parser&lt;/strong&gt; (#5435). &lt;strong&gt;Before:&lt;/strong&gt; a WP with &lt;code dir=&quot;auto&quot;&gt;dependencies: []&lt;/code&gt; was reported as depending on a work package named &lt;code dir=&quot;auto&quot;&gt;&quot;[]&quot;&lt;/code&gt;, and a YAML list became one fused dependency string, so the board’s readiness map disagreed with the dependency gate. &lt;strong&gt;After:&lt;/strong&gt; the board uses the same parser the gate enforces, so an empty flow list, a flow list and a block list all read correctly.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;session-start&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;session-stop&lt;/code&gt; project-root discovery honors &lt;code dir=&quot;auto&quot;&gt;GIT_CEILING_DIRECTORIES&lt;/code&gt; and no longer carries a test-only &lt;code dir=&quot;auto&quot;&gt;stop=&lt;/code&gt; bound&lt;/strong&gt; (#7122). &lt;strong&gt;Before:&lt;/strong&gt; the hook commands’ &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt; walk ignored the discovery ceiling every other root walk reads. &lt;strong&gt;After:&lt;/strong&gt; it uses the one ceiling-aware ancestor walk, so it honors the same ceiling reading as every other root walk (it stops after a listed ceiling directory or at the filesystem root).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate --dry-run&lt;/code&gt; reports its refusal reasons with stable error codes&lt;/strong&gt; (#5373). The slug-unresolvable, unreadable-lanes and integration-preview failures now carry &lt;code dir=&quot;auto&quot;&gt;MISSION_SLUG_UNRESOLVED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;LANES_MANIFEST_UNREADABLE&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;TARGET_INTEGRATION_PREVIEW_FAILED&lt;/code&gt; in the JSON forecast, so tooling can key on them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate --dry-run&lt;/code&gt; refuses a deleted mission branch instead of crashing&lt;/strong&gt; (#7267). The forecast now runs the same missing-branch check as the real run and reports &lt;code dir=&quot;auto&quot;&gt;MISSION_BRANCH_MISSING&lt;/code&gt; with the run’s own remedy, instead of raising an unhandled &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consolidation target-branch tip captures resolve the branch, not a same-named tag&lt;/strong&gt; (#5058). Four merge-domain tip reads (&lt;code dir=&quot;auto&quot;&gt;bookkeeping_projection&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;phase_claim&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;phase_advance&lt;/code&gt; baseline and re-anchor) route through the canonical &lt;code dir=&quot;auto&quot;&gt;capture_branch_tip&lt;/code&gt; authority, so a tag sharing the target branch’s name can no longer misresolve a baseline or the transaction-start tip to the tag SHA.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission done records state what actually happened&lt;/strong&gt; (#7354). A &lt;code dir=&quot;auto&quot;&gt;direct_repo&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission’s merge-complete events now carry &lt;code dir=&quot;auto&quot;&gt;execution_mode: direct_repo&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;merge_phase: direct_repo&lt;/code&gt;, instead of the false &lt;code dir=&quot;auto&quot;&gt;worktree&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;lane_integrated&lt;/code&gt; audit stamp for a lane integration that never happened.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Owned-checkout writers follow nested Mission symlinks, and that is now the documented contract&lt;/strong&gt; (#5923). The &lt;code dir=&quot;auto&quot;&gt;files()&lt;/code&gt; docstring states the follow behavior, the false “still refused” comment in &lt;code dir=&quot;auto&quot;&gt;owned_mission.py&lt;/code&gt; is corrected, and the previously vacuous symlink-escape test now asserts the real contract (link returned by where it sits; refused only by an explicit &lt;code dir=&quot;auto&quot;&gt;follow_links=True&lt;/code&gt; boundary screen).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The review interpreter needs &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; before building &lt;code dir=&quot;auto&quot;&gt;uv run --frozen&lt;/code&gt;&lt;/strong&gt; (#3594). &lt;strong&gt;Before:&lt;/strong&gt; a repo with &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; but no &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; still produced the &lt;code dir=&quot;auto&quot;&gt;uv run --frozen …&lt;/code&gt; command, which fails without a lock. &lt;strong&gt;After:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;uv&lt;/code&gt; form requires both files; a missing lock falls back to &lt;code dir=&quot;auto&quot;&gt;sys.executable&lt;/code&gt;, so the verdict is real either way.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ownership overlap compares on the path-component boundary&lt;/strong&gt; (#6312). &lt;strong&gt;Before:&lt;/strong&gt; a prefix compare made &lt;code dir=&quot;auto&quot;&gt;src/p1/**&lt;/code&gt; read as overlapping &lt;code dir=&quot;auto&quot;&gt;src/p10/**&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; a prefix only matches through a following &lt;code dir=&quot;auto&quot;&gt;/&lt;/code&gt; (or an exact path), so sibling directories with a shared prefix do not overlap.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; builds its summary from a linked worktree&lt;/strong&gt; (#3656). &lt;strong&gt;Before:&lt;/strong&gt; the summary’s relative paths were computed against the worktree root, so a WP resolved under a linked git worktree raised on path relativization. &lt;strong&gt;After:&lt;/strong&gt; the relative path is computed against the root the WP path was resolved under, and a summary from a linked worktree no longer raises.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Acceptance cleanup advice no longer prints raw &lt;code dir=&quot;auto&quot;&gt;git worktree remove&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;git branch -d&lt;/code&gt; recipes&lt;/strong&gt; (#7327). &lt;strong&gt;Before:&lt;/strong&gt; local-mode acceptance instructions told the operator to run &lt;code dir=&quot;auto&quot;&gt;git worktree remove&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;git branch -d&lt;/code&gt; by hand, bypassing the guards that keep stranded lane work recoverable. &lt;strong&gt;After:&lt;/strong&gt; the worktree line points at &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces --prune&lt;/code&gt;, and the branch line names the consolidate-owned guarded removal, with the prune as the backstop.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;accept --lenient&lt;/code&gt; records &lt;code dir=&quot;auto&quot;&gt;lenient: true&lt;/code&gt; in the acceptance history entry&lt;/strong&gt; (#7356). &lt;strong&gt;Before:&lt;/strong&gt; the lenient flag gated the run but the persisted history entry did not say the acceptance was lenient, so an audit could not tell a lenient acceptance from a strict one. &lt;strong&gt;After:&lt;/strong&gt; the flag is threaded through &lt;code dir=&quot;auto&quot;&gt;perform_acceptance&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;_stamp_acceptance_record&lt;/code&gt;; the entry carries &lt;code dir=&quot;auto&quot;&gt;lenient: true&lt;/code&gt;, and strict acceptances keep the key absent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A requirement ID declared twice is refused at each repeat&lt;/strong&gt; (#5674). &lt;strong&gt;Before:&lt;/strong&gt; the declared-id collector de-duplicated into a set, so a requirements table repeating &lt;code dir=&quot;auto&quot;&gt;FR-001&lt;/code&gt; read as one requirement and a WP mapping it covered both rows. &lt;strong&gt;After:&lt;/strong&gt; an id’s first declaration fixes its site, and another row of that same table (or another id-naming heading, for a heading-declared id) is an &lt;code dir=&quot;auto&quot;&gt;InvalidRequirementId&lt;/code&gt; at its own line, refusing setup-plan and design validation. A bullet or bold note, a later traceability table or a detail heading that restates the id is not a declaration and is never refused.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The dossier indexer hashes a &lt;code dir=&quot;auto&quot;&gt;WP##&lt;/code&gt;-named file outside &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; as a generic artifact&lt;/strong&gt; (#2900). &lt;strong&gt;Before:&lt;/strong&gt; every &lt;code dir=&quot;auto&quot;&gt;WP##*.md&lt;/code&gt; anywhere under the mission dir went through the work-package projection, so an auxiliary file that only shared the prefix (a glossary fragment, an activity log) failed closed through the &lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; schema. &lt;strong&gt;After:&lt;/strong&gt; only a &lt;code dir=&quot;auto&quot;&gt;WP##*.md&lt;/code&gt; whose parent directory is &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; is hashed as a work package; any other &lt;code dir=&quot;auto&quot;&gt;WP##&lt;/code&gt;-named file is hashed by its raw bytes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bulk-edit diff check classifies &lt;code dir=&quot;auto&quot;&gt;.jsonl&lt;/code&gt; as serialized&lt;/strong&gt; (#1791). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;.jsonl&lt;/code&gt; diff was judged as plain text, flagging serialized event logs as a semantic edit. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;\.jsonl$&lt;/code&gt; joins the serialized-keys classification.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The upgrade no-migrations stamp refreshes the environment block&lt;/strong&gt; (#4160). &lt;strong&gt;Before:&lt;/strong&gt; a project upgraded across a platform-affecting release with no migrations to run kept &lt;code dir=&quot;auto&quot;&gt;python_version&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;platform&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;platform_version&lt;/code&gt; from the earlier build. &lt;strong&gt;After:&lt;/strong&gt; the environment fields are re-stamped in the same write as the version bump.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The Op auto-commit carries the operator attribution trailer&lt;/strong&gt; (#7315). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;op(...)&lt;/code&gt; commit minted by &lt;code dir=&quot;auto&quot;&gt;profile-invocation complete&lt;/code&gt; was generated by the executor, so the configured &lt;code dir=&quot;auto&quot;&gt;Co-Authored-By&lt;/code&gt; trailer never rode it. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;complete_invocation&lt;/code&gt; takes &lt;code dir=&quot;auto&quot;&gt;co_author&lt;/code&gt;, resolves the trailer configured under the new optional &lt;code dir=&quot;auto&quot;&gt;commit.co_author&lt;/code&gt; key in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; (with &lt;code dir=&quot;auto&quot;&gt;profile-invocation complete --co-author&lt;/code&gt; overriding it), and the per-record and closure-spine commits both carry it; an invalid explicit value is refused before any write.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The orientation block renders ASCII-only&lt;/strong&gt; (#5757). &lt;strong&gt;Before:&lt;/strong&gt; the session-presence block wrote a warning glyph, em dash and arrow, which some toolchains mangle. &lt;strong&gt;After:&lt;/strong&gt; the render is ASCII (&lt;code dir=&quot;auto&quot;&gt;[!]&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;-&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;-&gt;&lt;/code&gt;), and blocks written before the change are still recognized as Spec Kitty’s — legacy glyphs are normalized before the canonical compare, so an older block is refreshed instead of preserved as “edited”.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status&lt;/code&gt; reads the same status log as every other command&lt;/strong&gt; (#7335, #7408). &lt;strong&gt;Before:&lt;/strong&gt; for a coordination Mission whose coordination worktree was empty or not checked out, the board showed the repository root checkout’s stale copy of the log while &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; showed the coordination branch; a reopened Mission still read as merged. &lt;strong&gt;After:&lt;/strong&gt; the board reads through the one status read door: it shows the coordination branch in that state, exits 1 on an unreadable log or ref instead of showing an empty board, and treats a Mission as merged only when &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; is set; older merged Missions get it from &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; (see the upgrade notes), which the &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_DELETED&lt;/code&gt; remedy names when the target’s log shows all work finished. Origin-freshness lane selection, lane-tip cleanup and the review dependents warning read the same door.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; removes an auto-rebased lane again&lt;/strong&gt; (#6736, #7382). &lt;strong&gt;Before:&lt;/strong&gt; cleanup checked each lane against its tip from before the run, so a lane the run auto-rebased was kept with &lt;code dir=&quot;auto&quot;&gt;WORKTREE_TIP_MOVED&lt;/code&gt;, reported as “has uncommitted changes”, at exit 0. On a coordination topology a lane was also kept with &lt;code dir=&quot;auto&quot;&gt;NOT_LANDED_ON_NAMED_REMOTE&lt;/code&gt;: it carries an older copy of the Mission’s status log, which the target appends to after the landing. &lt;strong&gt;After:&lt;/strong&gt; cleanup follows the run’s own auto-rebase merge (recorded, so &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; keeps it) and treats the status log and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; as landed when every lane event is in the target’s log. Any other move or difference still keeps the lane, and a moved tip is reported as moved. &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; does the same.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty retrospect summary&lt;/code&gt; walks &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; once per run&lt;/strong&gt; (#6788). &lt;strong&gt;Before:&lt;/strong&gt; every Mission’s slug lookup walked the whole &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; tree up to five times, so the summary grew with the square of the Mission count (200 Missions: about 7 s; 400: about 28 s). &lt;strong&gt;After:&lt;/strong&gt; one walk per run serves every lookup, so 200 Missions take about 1.3 s and 400 about 3.3 s. The output is unchanged. &lt;strong&gt;What to do:&lt;/strong&gt; nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every reader of the tracked &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; (for example &lt;code dir=&quot;auto&quot;&gt;migrate backfill-identity&lt;/code&gt;) treats git’s dubious-ownership refusal as a refusal on its own&lt;/strong&gt; (#7061). &lt;strong&gt;Before:&lt;/strong&gt; the refusal only held when the &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; search above the Mission also found the repository, so a search that stopped short of the repository git refused could read the Mission as untracked and let a new &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; be minted. &lt;strong&gt;After:&lt;/strong&gt; git’s ownership diagnosis alone refuses with &lt;code dir=&quot;auto&quot;&gt;TRACKED_META_UNAVAILABLE&lt;/code&gt;, and no identity is minted. Hardening: the nightly failure filed as #7061 was a test-isolation fault (the runner’s &lt;code dir=&quot;auto&quot;&gt;safe.directory = *&lt;/code&gt;), not an observed mint.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces --prune&lt;/code&gt; proves each destructive step first&lt;/strong&gt; (#7211, #7212, #7214; ADR &lt;code dir=&quot;auto&quot;&gt;2026-11-06-1&lt;/code&gt;). &lt;strong&gt;Before:&lt;/strong&gt; a branch that moved between the tip check and &lt;code dir=&quot;auto&quot;&gt;git branch -D&lt;/code&gt; lost its new commit; a commit only the destroyed reflogs held could be collected by &lt;code dir=&quot;auto&quot;&gt;git gc&lt;/code&gt;; and a fork clone could never prove a landing, because only &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt; was read. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--remote &amp;#x3C;name&gt;&lt;/code&gt; (default &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;) names the proving remote; commits only a reflog held are kept under &lt;code dir=&quot;auto&quot;&gt;refs/spec-kitty/discarded/reflog/&amp;#x3C;sha&gt;&lt;/code&gt; unless their content is already on that remote’s primary; and the branch is deleted by compare-and-swap, so a moved branch is kept as &lt;code dir=&quot;auto&quot;&gt;BRANCH_MOVED&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;remote&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;kept_commits&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A second &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer deletes the generated &lt;code dir=&quot;auto&quot;&gt;.claude/commands&lt;/code&gt; files the first one kept&lt;/strong&gt; (#7429, fixed by #7470). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;4.0.0rc8_stamp_globalize_commands&lt;/code&gt; was never recorded as settled, so every upgrade ran it again; on the second run it read the version stamp the first run had written and removed every generated &lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; command file the first run had kept. &lt;strong&gt;After:&lt;/strong&gt; its own successful run settles it, so a repeat upgrade applies nothing and changes nothing.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal&quot;&gt;Internal&lt;/h3&gt;
&lt;p&gt;These entries matter to contributors to this repository, not to people who use the CLI. They are condensed; each issue or PR number leads to the full record.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Release process: the cross-repository end-to-end suite and the live deployed-dev canary are retired&lt;/strong&gt; (#7469). &lt;code dir=&quot;auto&quot;&gt;RELEASE_CHECKLIST.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;scripts/release/README.md&lt;/code&gt; no longer ask the release owner to run them before tagging; a dedicated cross-repository checks pipeline is planned to replace them (#7468).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Merging and CI control.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; merges through GitHub’s merge queue (#6992). A &lt;code dir=&quot;auto&quot;&gt;pr:pause-ci&lt;/code&gt; label holds a PR’s CI and merge, and removing it restarts CI (#6961, #7019, #7047).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI routing.&lt;/strong&gt; CI runs every architectural gate whose declared scan scope a PR touches, prose-only PRs included, and a gate that reads a new path cannot go undeclared (#6996, #6994, #6999, #7000, #7037, #7001, #6879). Pin bumps, &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; changes and charter edits fan out to the shards that read them (#6637, #6605, #6908, #6336). Duplicate scans and setup are reduced (#7078).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Nightly and timing gates.&lt;/strong&gt; Pinning-inventory and battery timing drift are nightly-strict instead of per-PR blockers, and timings are recaptured and budgeted (#6365, #7020, #6998, #7052, #7288). The nightly reports its real failures again, its suites carry their own timeouts, and the integration suite runs in four shards (#7109, #6787, #7110, #5378, #7456). Nightly reds were cleared (#7177, #7178, #7111, #7181, #7182, #7183, #7175, #7176, #7221, #7341, #7342, #7343).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Docs build and changelog.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;docs-site&lt;/code&gt; build is a required gate, and the docs tree carries doc-kitty’s frontmatter and builds on doc-kitty (#6937, #6929, #6930, #6931, #7388, #6927, #6928, #2358, #3914). PRs no longer regenerate the docs index, page inventory or ADR era tables (#6993). Changelog entries are per-PR fragments (#6988).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Supply chain and security of CI.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;ci-aggregate.yml&lt;/code&gt; declares least-privilege token scopes (#5554); release builds check each companion wheel’s platform tag (#7048, #6948); the two SonarCloud reliability blockers are fixed at source (#7113); a plain &lt;code dir=&quot;auto&quot;&gt;uv sync&lt;/code&gt; yields &lt;code dir=&quot;auto&quot;&gt;ruff&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mypy&lt;/code&gt; (#5064, #4599, #6051, #7141, #7220).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Direction records.&lt;/strong&gt; The charter stays in core: the 4.0.0 charter leg is a frozen seam and a green conformance corpus, with its public surface frozen in a committed census (#6099, #6288, #6285). The Mission Status Read API’s domain types and event-log reader are framework-free libraries (#6192, #6117). ADRs for coordination without a worktree (#7284).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Code structure.&lt;/strong&gt; Event logs other than &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; have a writes gate and dead write doors are deleted (#6603, #6614); status reads go through one read door, guarded against bypass (#7408, #7310); lock paths, lane adoption and lane-checkout creation each have one owner (#6826, #6727, #6898, #7279); the &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; worktree pass is split into plan and apply steps (#7405); the language settlement moves to remove an import cycle (#6540).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Other test, CI and code-structure work&lt;/strong&gt; with no user-visible change: #2778, #2972, #3950, #4361, #4437, #4695, #4697, #4842, #4848, #4891, #5015, #5179, #5184, #5189, #5441, #5691, #5716, #5740, #5927, #5939, #6169, #6193, #6218, #6260, #6333, #6362, #6367, #6379, #6418, #6432, #6447, #6451, #6459, #6474, #6496, #6513, #6543, #6553, #6563, #6570, #6578, #6581, #6582, #6607, #6621, #6641, #6666, #6673, #6675, #6715, #6728, #6732, #6739, #6745, #6762, #6766, #6776, #6777, #6786, #6850, #6854, #6855, #6859, #6876, #6902, #6907, #6913, #6915, #6921, #6957, #6966, #7006, #7022, #7026, #7030, #7032, #7055, #7057, #7061, #7073, #7074, #7112, #7120, #7140, #7174, #7200, #7206, #7224, #7282, #7306, #7308, #7322, #7334, #7381, #7429, #7434.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;400rc7---2026-10-15&quot;&gt;[4.0.0rc7] - 2026-10-15&lt;/h2&gt;
&lt;h3 id=&quot;breaking-1&quot;&gt;Breaking&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; is now &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;, with no alias&lt;/strong&gt; (#3732). &lt;strong&gt;Before:&lt;/strong&gt; config keys, directories and commands used the &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; name. &lt;strong&gt;After:&lt;/strong&gt; everything uses &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;, and until you migrate every command except &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--version&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt;, the git merge drivers and the hook entry points stops with &lt;code dir=&quot;auto&quot;&gt;LEGACY_CHARTER_STATE&lt;/code&gt; (exit 1). &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; once per project, commit it in the repository root checkout, then merge that branch into each lane — never rebase a lane, or a later &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuses with &lt;code dir=&quot;auto&quot;&gt;APPROVAL_STAMP_NOT_ON_LANE&lt;/code&gt;. See the &lt;a href=&quot;/migrations/charter-pack-cutover/&quot;&gt;runbook&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: the &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; command group is gone&lt;/strong&gt; (#3732). &lt;strong&gt;Before:&lt;/strong&gt; pack, fetch and scaffolding commands ran under &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; they live under &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter&lt;/code&gt;, and an old spelling fails as an unknown command (exit 2). &lt;strong&gt;What to do:&lt;/strong&gt; rename &lt;code dir=&quot;auto&quot;&gt;doctrine …&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;charter …&lt;/code&gt; in your scripts, for example &lt;code dir=&quot;auto&quot;&gt;charter pack validate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter mission-type list --include-inactive&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;doctrine regenerate-graph&lt;/code&gt; becomes &lt;code dir=&quot;auto&quot;&gt;charter pack regenerate-graph&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctrine asset …&lt;/code&gt; becomes &lt;code dir=&quot;auto&quot;&gt;charter pack asset …&lt;/code&gt;. The &lt;a href=&quot;/migrations/charter-pack-cutover/&quot;&gt;runbook&lt;/a&gt; lists every command.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: activation presets are applied with &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate --preset &amp;#x3C;name&gt;&lt;/code&gt;&lt;/strong&gt; (#3732). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack apply &amp;#x3C;name&gt;&lt;/code&gt; applied a preset. &lt;strong&gt;After:&lt;/strong&gt; presets are pack data and &lt;code dir=&quot;auto&quot;&gt;charter pack&lt;/code&gt; works on packs. &lt;strong&gt;What to do:&lt;/strong&gt; replace &lt;code dir=&quot;auto&quot;&gt;charter pack apply &amp;#x3C;name&gt;&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;charter activate --preset &amp;#x3C;name&gt;&lt;/code&gt; (add &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; to change a customized key); the built-in pack ships &lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;minimal&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tracker&lt;/code&gt; follow the charter vocabulary&lt;/strong&gt; (#3732). &lt;strong&gt;Before:&lt;/strong&gt; they used the doctrine names and a &lt;code dir=&quot;auto&quot;&gt;doctrine_mode&lt;/code&gt; JSON key. &lt;strong&gt;After:&lt;/strong&gt; use &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker bind --ownership-mode &amp;#x3C;m&gt;&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; read &lt;code dir=&quot;auto&quot;&gt;ownership_mode&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;doctrine_mode&lt;/code&gt;, and update the command names.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: some &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; error codes were renamed&lt;/strong&gt; (#3732). &lt;strong&gt;Before:&lt;/strong&gt; the active charter’s invalid-config code was &lt;code dir=&quot;auto&quot;&gt;CHARTER_PACK_CONFIG_INVALID&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it is &lt;code dir=&quot;auto&quot;&gt;ACTIVE_CHARTER_CONFIG_INVALID&lt;/code&gt;, alongside new codes such as &lt;code dir=&quot;auto&quot;&gt;LEGACY_CHARTER_STATE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;PACK_NOT_FOUND&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;PRESET_NOT_FOUND&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DEFAULT_PRESET_MISSING&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;PRESET_ID_UNRESOLVED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;PRESET_WOULD_OVERWRITE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;PRESET_INVALID&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;RESYNTHESIS_FAILED&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;RETIRED_PACK_FIELD&lt;/code&gt; (the &lt;a href=&quot;/migrations/charter-pack-cutover/&quot;&gt;runbook&lt;/a&gt; says when each is raised). &lt;strong&gt;What to do:&lt;/strong&gt; update any tooling that matches the old code strings.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The host &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; code for an unresolvable mission is now &lt;code dir=&quot;auto&quot;&gt;MISSION_CONTEXT_UNRESOLVED&lt;/code&gt;&lt;/strong&gt; (#5976). &lt;strong&gt;Before:&lt;/strong&gt; host commands emitted &lt;code dir=&quot;auto&quot;&gt;FEATURE_CONTEXT_UNRESOLVED&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; they emit &lt;code dir=&quot;auto&quot;&gt;MISSION_CONTEXT_UNRESOLVED&lt;/code&gt;; the public orchestrator-api still reports its own &lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_FOUND&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; if you read the host &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt; directly, update the string.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: a Charter Pack must declare &lt;code dir=&quot;auto&quot;&gt;pack_level&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt;&lt;/strong&gt; (#6048, #3732). &lt;strong&gt;Before:&lt;/strong&gt; a pack’s level was inferred, and &lt;code dir=&quot;auto&quot;&gt;accompanies_doctrine_pack&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;doctrine_pack_id&lt;/code&gt; were accepted. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;pack_level&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;org&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;project&lt;/code&gt;) is required, a mismatch is refused with &lt;code dir=&quot;auto&quot;&gt;PACK_LEVEL_MISMATCH&lt;/code&gt;, a pack without it with &lt;code dir=&quot;auto&quot;&gt;PACK_LEVEL_MISSING&lt;/code&gt;, and the retired fields are rejected with &lt;code dir=&quot;auto&quot;&gt;RETIRED_PACK_FIELD&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; add &lt;code dir=&quot;auto&quot;&gt;pack_level&lt;/code&gt;, delete &lt;code dir=&quot;auto&quot;&gt;accompanies_doctrine_pack&lt;/code&gt;, and rename &lt;code dir=&quot;auto&quot;&gt;doctrine_pack_id&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;charter_pack_id&lt;/code&gt;; the upgrade writes &lt;code dir=&quot;auto&quot;&gt;pack_level&lt;/code&gt; into existing project packs for you. For one release an org pack with no &lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt; still loads, with a deprecation warning.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The markdown &lt;code dir=&quot;auto&quot;&gt;## Activity Log&lt;/code&gt; section is removed from the work-package templates&lt;/strong&gt; (#5986, #2334). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks add-history&lt;/code&gt; rewrote a markdown Activity Log in the prompt file. &lt;strong&gt;After:&lt;/strong&gt; it records the note in &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, so history no longer drifts between checkouts, and the shipped templates no longer carry the section. Files that still have one are still read, so no earlier history is lost. &lt;strong&gt;What to do:&lt;/strong&gt; read history with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status&lt;/code&gt;, and run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to refresh the shipped command copies.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Minimum dependencies are raised&lt;/strong&gt; (#6004, #6007). &lt;strong&gt;Before:&lt;/strong&gt; older &lt;code dir=&quot;auto&quot;&gt;typer&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; were allowed. &lt;strong&gt;After:&lt;/strong&gt; spec-kitty needs typer 0.27.3 or newer and spec-kitty-events 10.4.4 or newer. &lt;strong&gt;What to do:&lt;/strong&gt; let a fresh install resolve them, or raise your pins.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: several Python modules and public names were renamed or removed&lt;/strong&gt; (#3732, #5996, #5824). &lt;strong&gt;Before:&lt;/strong&gt; the library exposed the doctrine-named modules and &lt;code dir=&quot;auto&quot;&gt;ArtifactKind.core&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;CORE_KIND_PLURALS&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; they move under &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter_packs&lt;/code&gt;, with &lt;code dir=&quot;auto&quot;&gt;ArtifactKind.has_layered_repository&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;LAYERED_REPOSITORY_KIND_PLURALS&lt;/code&gt; replacing the removed names, and no alias. Most-used renames: &lt;code dir=&quot;auto&quot;&gt;CharterPackManager&lt;/code&gt; is now &lt;code dir=&quot;auto&quot;&gt;ActiveCharterManager&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DoctrineService&lt;/code&gt; is &lt;code dir=&quot;auto&quot;&gt;CharterOfferingService&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;ActiveCharterService&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DoctrineCatalog&lt;/code&gt; is &lt;code dir=&quot;auto&quot;&gt;OfferingCatalog&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;load_doctrine_catalog&lt;/code&gt; is &lt;code dir=&quot;auto&quot;&gt;load_offering_catalog&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;compile_charter(doctrine_service=…)&lt;/code&gt; is &lt;code dir=&quot;auto&quot;&gt;charter_service=…&lt;/code&gt;. &lt;strong&gt;What to do:&lt;/strong&gt; update your imports if you use spec-kitty as a library; the full table is in the &lt;a href=&quot;/migrations/charter-pack-cutover/#python-callers&quot;&gt;runbook&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: the remaining old command spellings are gone&lt;/strong&gt; (#3732). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine fetch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine pack validate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine pack assemble …&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine regenerate-graph&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine mission-type list&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine asset list&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor tool-surfaces --kind doctrine-skill&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker bind --doctrine-mode&lt;/code&gt;, and the org commands &lt;code dir=&quot;auto&quot;&gt;doctrine org init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctrine org validate&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; use &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter …&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;charter org init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter org validate&lt;/code&gt; included; for example &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack consistency-check&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack path&lt;/code&gt;, which now work on packs), &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--kind charter-skill&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--ownership-mode&lt;/code&gt;; the old spellings fail. &lt;strong&gt;What to do:&lt;/strong&gt; rename them in your scripts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: the old config keys, paths and error name are gone&lt;/strong&gt; (#3732). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;doctrine.org.packs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;organisation_packs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;governance.doctrine&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tracker.doctrine&lt;/code&gt; configured packs, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine asset path &amp;#x3C;id&gt;&lt;/code&gt; located assets, and a missing default preset raised &lt;code dir=&quot;auto&quot;&gt;DefaultCharterPackMissingError&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the keys use the charter names, &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack asset path &amp;#x3C;id&gt;&lt;/code&gt; locates assets, and the exception is &lt;code dir=&quot;auto&quot;&gt;DefaultPresetMissingError&lt;/code&gt; (code &lt;code dir=&quot;auto&quot;&gt;DEFAULT_PRESET_MISSING&lt;/code&gt;). &lt;strong&gt;What to do:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;, which rewrites the keys for you; update any code that catches the old exception name.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: thirteen old skill names map to seven skills&lt;/strong&gt; (#3732). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-bulk-edit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-charter&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-glossary&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-profile-load&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-semantic-compression&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-show-me&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-spdd-reasons&lt;/code&gt; shipped beside &lt;code dir=&quot;auto&quot;&gt;spec-kitty-bulk-edit-classification&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-charter-doctrine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty-glossary-context&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty-spdd-reasons&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; each skill has one &lt;code dir=&quot;auto&quot;&gt;spk-&lt;/code&gt; name, such as &lt;code dir=&quot;auto&quot;&gt;spk-charter-profile-load&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; removes installed copies of the old names; a copy you edited is kept and becomes yours. &lt;strong&gt;What to do:&lt;/strong&gt; update prompts that name an old skill.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter sync&lt;/code&gt; is removed&lt;/strong&gt; (#5828). &lt;strong&gt;Before:&lt;/strong&gt; the command only printed a “kept for compatibility” banner and exited 0; it had done nothing for a long time. &lt;strong&gt;After:&lt;/strong&gt; it is deleted with no alias, and the old spelling fails as an unknown command (exit 2). Remove &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter sync&lt;/code&gt; calls from your scripts and CI; nothing replaces it, because edits to &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; are read live and need no post-edit step.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;upgrade-notes-1&quot;&gt;Upgrade Notes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Charter pack cutover: run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; once in each project before any other command&lt;/strong&gt; (#3732). It moves &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt;, rewrites the old config keys, re-enables newer built-ins (naming any key to set back if you had customized it), and removes the old skill copies (a skill you edited is kept). Upgrade and commit in the repository root checkout, then merge the target branch into each lane — never rebase. Replace &lt;code dir=&quot;auto&quot;&gt;/ad-hoc-profile-load&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;/spk-charter-profile-load&lt;/code&gt; in prompt files an earlier upgrade wrote. See the &lt;a href=&quot;/migrations/charter-pack-cutover/&quot;&gt;runbook&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commit &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/pack.yaml&lt;/code&gt; once after &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;&lt;/strong&gt; (#6076). Do it from one clone; other clones delete their local copy and pull, so every contributor shares one &lt;code dir=&quot;auto&quot;&gt;pack_id&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Remove &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter sync&lt;/code&gt; from scripts and CI&lt;/strong&gt; (#5828). The command is gone and now exits 2; nothing replaces it, because &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; edits are read live.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-1&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Charter Packs can ship activation presets&lt;/strong&gt; (#3732). A pack carries &lt;code dir=&quot;auto&quot;&gt;presets/&amp;#x3C;name&gt;.yaml&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack list&lt;/code&gt; shows each pack with its presets, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate --pack &amp;#x3C;pack&gt; --preset &amp;#x3C;name&gt;&lt;/code&gt; applies one. The built-in pack ships &lt;code dir=&quot;auto&quot;&gt;default&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;minimal&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt; can declare an optional &lt;code dir=&quot;auto&quot;&gt;requires_core&lt;/code&gt; version range&lt;/strong&gt; (#6046). It is a standard Python (PEP 440) version specifier for the spec-kitty versions the pack works with.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One declaration-first &lt;code dir=&quot;auto&quot;&gt;repo_root&lt;/code&gt;/branch resolution entry at the command-entry layer&lt;/strong&gt; (#6142). A new typed producer (&lt;code dir=&quot;auto&quot;&gt;specify_cli.core.command_target.resolve_command_repo_target&lt;/code&gt;) resolves a mission-scoped command’s &lt;code dir=&quot;auto&quot;&gt;(repo_root, target_branch)&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;repo_root&lt;/code&gt; is always the repository root checkout, never a worktree, and &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; comes from the same authority the placement seam uses for the write, so the two always agree. A &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; declared in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; wins over the checked-out branch. When none is declared, the branch is that authority’s fallback, which in a repository without &lt;code dir=&quot;auto&quot;&gt;origin/HEAD&lt;/code&gt; can still be the checked-out branch; a fallback independent of it is follow-up #6152. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent record-analysis&lt;/code&gt; is the first command routed through it; its commit target is unchanged. Increment 1 of the scoped-shadow-workspace direction (ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-10-1&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-1&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; runs an analysis step between tasks and implement&lt;/strong&gt; (#5885). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; jumped to implement, which then refused because no analysis report existed. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; issues &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.analyze&lt;/code&gt; first and hands out implement only once the report is current.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The shipped software-dev prompts match what the CLI actually does&lt;/strong&gt; (#5885). &lt;strong&gt;Before:&lt;/strong&gt; a prompt could name a refused command, a missing path, or a wrong “next advances here” claim. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; plans from the one canonical pack template, so an agent following the prompts no longer hits a surprise; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to refresh generated command copies.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Operator-facing text and planning commits say “mission”, not “feature”&lt;/strong&gt; (#5885, #5977). &lt;strong&gt;Before:&lt;/strong&gt; commit subjects, some command errors and the specify/plan prompts used “feature”. &lt;strong&gt;After:&lt;/strong&gt; they use the canonical term, and a mission finalized under the older wording raises no false drift warning.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor charter-packs&lt;/code&gt; and the org lint cover glossary packs, skills and assets&lt;/strong&gt; (#5996). &lt;strong&gt;Before:&lt;/strong&gt; they scanned only the eight original kinds. &lt;strong&gt;After:&lt;/strong&gt; they scan every layered kind, so an existing org pack may surface new findings.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-1&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A migration seed no longer stands in for the real implementer or the approving reviewer&lt;/strong&gt; (#6093, #6257). &lt;strong&gt;Before:&lt;/strong&gt; an event by a &lt;code dir=&quot;auto&quot;&gt;migration:&lt;/code&gt; actor made &lt;code dir=&quot;auto&quot;&gt;implementer_of_record&lt;/code&gt;, the review-lane resume, the move-task reviewer check and the consolidation independent-review check judge the seed, not the person. &lt;strong&gt;After:&lt;/strong&gt; they judge the real implementer and approver. In Missions upgraded by older status migrations, a work package whose only implementing events are seeds now has no implementer authority, so review-lane moves on it may need &lt;code dir=&quot;auto&quot;&gt;--force --note&lt;/code&gt; and consolidation may newly print the hollow-review warning. The bare &lt;code dir=&quot;auto&quot;&gt;migration&lt;/code&gt; actor of the state-rebuild migration is not treated as a seed. A non-terminal Mission whose v2 &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; predates this fix may report &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; until its next status write re-materializes it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A user-authored custom slash command is no longer deleted or rewritten by &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;&lt;/strong&gt; (#6247). &lt;strong&gt;Before:&lt;/strong&gt; command-file migrations matched &lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; by name and deleted — or rewrote in place — any file they had not generated, so a hand-authored command such as &lt;code dir=&quot;auto&quot;&gt;spec-kitty.custom.md&lt;/code&gt; was destroyed, even on a failed upgrade that “committed nothing”. &lt;strong&gt;After:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; file is deleted or rewritten only when its version marker proves it is package-generated; an unmarked, user-authored file is preserved, because a name is not proof of package ownership (charter “User Customization Preservation”). &lt;strong&gt;What to do:&lt;/strong&gt; nothing — custom commands now survive upgrades, and one lost earlier can be recovered from git history.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A reviewer’s rejection recorded after a clock-ahead approval is no longer lost, so &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; no longer lands rejected code&lt;/strong&gt; (#4941, P0). &lt;strong&gt;Before:&lt;/strong&gt; the status reducer the consolidation gate reads (&lt;code dir=&quot;auto&quot;&gt;materialize_snapshot&lt;/code&gt; → the wall-clock diary reducer) ordered lane transitions by their &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt;, so an &lt;code dir=&quot;auto&quot;&gt;approved -&gt; in_progress&lt;/code&gt; rejection minted on a correct clock after an approval whose clock ran ahead (or arriving via &lt;code dir=&quot;auto&quot;&gt;git pull&lt;/code&gt; + the union merge driver) sorted before the approval and was dropped as causally stale — &lt;code dir=&quot;auto&quot;&gt;status emit&lt;/code&gt; printed &lt;code dir=&quot;auto&quot;&gt;OK&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status validate&lt;/code&gt; passed, and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; kept the work package &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; and landed the rejected code. &lt;strong&gt;After:&lt;/strong&gt; the diary reducer (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&gt;=10.5.1&lt;/code&gt;, spec-kitty-events PR #102, fixing issue #101) sorts a non-seed departure from &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; after the approval it followed, so the rejection applies and the gate drops the work package; &lt;code dir=&quot;auto&quot;&gt;status validate&lt;/code&gt; also warns (never fails) on such out-of-order logs. The wrong “Lamport” docstrings in &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/consolidation/&lt;/code&gt; are corrected (#6213).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Agent profiles no longer read as local edits under Git for Windows’ &lt;code dir=&quot;auto&quot;&gt;core.autocrlf=true&lt;/code&gt;&lt;/strong&gt; (#6235). &lt;strong&gt;Before:&lt;/strong&gt; the drift check hashed the raw on-disk bytes against the LF manifest hash, so every tracked profile a CRLF checkout rewrote read as drift — a fresh clone’s &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --project --yes&lt;/code&gt; exited 1 with phantom “local edits”, &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces&lt;/code&gt; reported drift, and the repair had to be repeated after any git operation that rewrote a profile. &lt;strong&gt;After:&lt;/strong&gt; a profile whose content differs from the LF render only in line endings is recognized as git-clean and left untouched, so &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; exits 0 and &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; reports no drift; a genuine edit still requires consent. Mirrors the #5576 / #5593 fix on the agent-profile surface it did not reach.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api answer-decision&lt;/code&gt; now reports a refused decision-log commit instead of a silent success&lt;/strong&gt; (#6222, follow-up to #3930). &lt;strong&gt;Before:&lt;/strong&gt; when the decision record’s &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; was refused, the host &lt;code dir=&quot;auto&quot;&gt;next --answer --json&lt;/code&gt; surfaced a &lt;code dir=&quot;auto&quot;&gt;warnings&lt;/code&gt; key (#3930) but the orchestrator-api verb returned &lt;code dir=&quot;auto&quot;&gt;success: true&lt;/code&gt; with no warning, so an external orchestrator never learned the committed decision record had diverged. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;answer-decision&lt;/code&gt; wraps the answer persistence in the same &lt;code dir=&quot;auto&quot;&gt;capture_commit_warnings()&lt;/code&gt; span and surfaces a &lt;code dir=&quot;auto&quot;&gt;warnings&lt;/code&gt; key in &lt;code dir=&quot;auto&quot;&gt;data&lt;/code&gt; when, and only when, the commit was refused — byte-identical to the host surface, absent on a clean commit. The orchestrator-api contract moves to &lt;code dir=&quot;auto&quot;&gt;1.16.0&lt;/code&gt; (additive, optional field; no field removed or renamed).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Claude plugin bundle repair now works from the project root&lt;/strong&gt; (#5843). &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces --kind plugin-manifest --fix&lt;/code&gt; skips informational unsupported native-config entries instead of treating &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;unsupported&gt;&lt;/code&gt; as a source file; selected staging and validation give the same result from any working directory.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement --recover&lt;/code&gt; now works when a coordination mission’s worktree has not been checked out&lt;/strong&gt; (#5410). Recovery materializes the declared local coordination branch before scanning status, then reports or repairs crashed sessions as usual.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; preserves cleanup choices&lt;/strong&gt; (#5439). &lt;strong&gt;Before:&lt;/strong&gt; resuming without &lt;code dir=&quot;auto&quot;&gt;--keep-branch&lt;/code&gt; could delete lane and mission branches kept by the interrupted run. &lt;strong&gt;After:&lt;/strong&gt; resume reuses the original branch and worktree cleanup choices and refuses conflicting flags.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Regenerated command skills are named, counted, gated on the surface class, and retired drift is pruned&lt;/strong&gt; (#6155). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent config sync&lt;/code&gt; regenerated a drifted git-ignored &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty.&amp;#x3C;command&gt;/SKILL.md&lt;/code&gt; silently, left it out of the &lt;code dir=&quot;auto&quot;&gt;N command skills installed&lt;/code&gt; count, regenerated unconditionally, and kept a retired command’s drifted projection as drift. &lt;strong&gt;After:&lt;/strong&gt; each regenerated path is named once, and listed under &lt;code dir=&quot;auto&quot;&gt;upgrade --json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;surface_repair.regenerated&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent config sync --json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;regenerated&lt;/code&gt;; it counts as installed; the regenerate only runs while the state contract declares the surface DERIVED and git-IGNORED, otherwise the drift is kept for consent; a retired command’s drifted projection is pruned with its manifest entry. Exit codes are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Issues cited as &lt;code dir=&quot;auto&quot;&gt;#NNNN:&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#NNNN!&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#NNNN?&lt;/code&gt;, wrapped in bold, backticks, quotes, pipes or dashes, or by a wrapped same-repo URL now get matrix rows&lt;/strong&gt; (#6069, #6239). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;Issue #NNNN: title&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;**Issue #NNNN**&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;`#NNNN`&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#NNNN/#MMMM&lt;/code&gt; and an issue URL in backticks, &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;...&gt;&lt;/code&gt;, bold or quotes got no issue-matrix row, so approval never asked for a verdict. &lt;strong&gt;After:&lt;/strong&gt; these shapes gate like &lt;code dir=&quot;auto&quot;&gt;(#NNNN)&lt;/code&gt;; line references such as &lt;code dir=&quot;auto&quot;&gt;#NNNN:45&lt;/code&gt; stay ignored. &lt;strong&gt;What to do:&lt;/strong&gt; re-running a gate on an older Mission can report newly missing rows (about 80 older Missions flip from complete to incomplete, and several unconsolidated ones need new rows). Known limitations: another project’s issue cited in prose as &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;name&gt; #NNNN:&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;name&gt; - Issue #NNNN:&lt;/code&gt;) reads as this repository’s, as it already did without the colon, and the second item of &lt;code dir=&quot;auto&quot;&gt;owner/repo#N/#M&lt;/code&gt; reads as this repository’s.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A migrated work package no longer reads as in progress because of a reconstructed review verdict&lt;/strong&gt; (#6061). &lt;strong&gt;Before:&lt;/strong&gt; a rollback-shaped verdict seed appended by the verdict backfill could take a lane the work package never had, so a merged &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; WP could read &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; and a never-claimed WP could read &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; spec-kitty-events 10.4.6 (which also carries spec-kitty-events#87, an equal-timestamp approved-to-done ordering fix) lets such a seed take a lane only when the WP’s lifecycle continues from it. &lt;strong&gt;What to do:&lt;/strong&gt; missions migrated before this release that are not complete may report &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; once; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status materialize --mission &amp;#x3C;slug&gt;&lt;/code&gt;. This repository’s own 079 snapshot was corrected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The verdict backfill keeps &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; in step with the events it adds&lt;/strong&gt; (#5869). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; appended review-verdict events but left an existing &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; behind, so the audit reported a &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; error on a Mission that is not finished. &lt;strong&gt;After:&lt;/strong&gt; the backfill refreshes an existing &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; right after it appends, and only then; it never creates one, and a re-run or a dry run leaves it untouched. A refresh failure, including an unreadable &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, is a warning, not an error. To heal a snapshot an earlier run left stale, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status materialize --mission &amp;#x3C;slug&gt;&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;consolidate&lt;/code&gt; never deletes the only copy of a file while exiting 0&lt;/strong&gt; (#5965, #5966). &lt;strong&gt;Before:&lt;/strong&gt; teardown could remove review feedback, traces or another mission’s edits and still exit 0. &lt;strong&gt;After:&lt;/strong&gt; it stops at exit 76 (&lt;code dir=&quot;auto&quot;&gt;COORD_TEARDOWN_KEPT_ONLY_COPY&lt;/code&gt;), names what it kept, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt; finishes once you move them. &lt;code dir=&quot;auto&quot;&gt;consolidate --abort&lt;/code&gt;, a lane retry reset, a mission-creation rollback, an auto-rebase abort and the &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; husk cleanup refuse over the only copy of work too, while &lt;code dir=&quot;auto&quot;&gt;agent mission create --force-recreate&lt;/code&gt; still discards. &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; reports the same code and keeps a lane branch no other ref reaches.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty mission close --discard&lt;/code&gt; works again and shows what it deletes&lt;/strong&gt; (#6085, #6071). It lists each branch it will delete, keeps each deleted tip under &lt;code dir=&quot;auto&quot;&gt;refs/spec-kitty/discarded/&amp;#x3C;branch&gt;&lt;/code&gt;, and prints the restore command.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer deletes a team’s own committed &lt;code dir=&quot;auto&quot;&gt;.agents/skills/**&lt;/code&gt;&lt;/strong&gt; (#5964). &lt;strong&gt;Before:&lt;/strong&gt; a pre-3.2.5 upgrade untracked the whole tree and committed the deletion, so teammates lost those skills on &lt;code dir=&quot;auto&quot;&gt;git pull&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it untracks only spec-kitty’s own generated skill copies.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Two commands writing one mission’s files at once no longer lose each other’s changes&lt;/strong&gt; (#5883). Every mission-file write takes one lock, so two overlapping updates both survive.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A refused final step no longer truncates your run log or another writer’s state&lt;/strong&gt; (#5884). The completion gate runs before anything is written, so a refusal leaves the log and state intact.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; can no longer land a rejected dependency’s rewritten-away content through a dependent lane&lt;/strong&gt; (#5968). The rejected files are now un-attributable, so the merge fails and rolls back instead of landing them at exit 0.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A teammate’s stale &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; can no longer bury a pushed cancel or rejection&lt;/strong&gt; (#5967). The event-log merge now stops at a conflict for a person to resolve, and a migrated mission reads its real lifecycle again.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A rejected work package can no longer read as approved after a bare approval&lt;/strong&gt; (#6084). With spec-kitty-events 10.4.4 the rejection stands until a genuine rework and review.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; warns when a mission’s &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; has drifted from its event log&lt;/strong&gt; (#5863). It names the fix, &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status materialize&lt;/code&gt;, instead of consolidating silently on a stale snapshot.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Running &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; from two agents at once can no longer complete a step neither reviewed&lt;/strong&gt; (#5854, #5682). &lt;strong&gt;Before:&lt;/strong&gt; overlapping advances could mark a review step &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; while its work package sat in &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;, then report &lt;code dir=&quot;auto&quot;&gt;terminal&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; advances take turns, and a stale or busy caller gets a &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; result to re-query.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The pre-review gate in a lane tests the lane’s own code&lt;/strong&gt; (#2803). &lt;strong&gt;Before:&lt;/strong&gt; it ran against an empty environment or the primary checkout’s code, giving false passes and failures. &lt;strong&gt;After:&lt;/strong&gt; it runs against the lane’s own code, using the project’s &lt;code dir=&quot;auto&quot;&gt;test&lt;/code&gt; extra or group when one is declared.&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 status doctor&lt;/code&gt; reports corrupt or unreadable status history&lt;/strong&gt; (#5924). &lt;strong&gt;Before:&lt;/strong&gt; a corrupt log read as healthy, or crashed. &lt;strong&gt;After:&lt;/strong&gt; it exits 1 in text and JSON and names the log path and reason.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; no longer spuriously aborts a healthy coordination mission&lt;/strong&gt; (#6073, #1772). It no longer fails with “merged WPs did not reach done in target branch history”.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; of a bare-slug coordination mission completes again&lt;/strong&gt; (#6071, #5651). It no longer refuses over its own composed coordination directory after a failed bookkeeping commit.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A consolidation killed mid-fold now points you at &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt;&lt;/strong&gt; (#6071, #5748). It refuses with &lt;code dir=&quot;auto&quot;&gt;MERGE_UNSAFE_PRIMARY_DIRTY&lt;/code&gt; and names the directory, instead of a stale “Merge lock already held” error.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate KIND ARTIFACT_ID&lt;/code&gt; works again on typer 0.26 or newer&lt;/strong&gt;. &lt;strong&gt;Before:&lt;/strong&gt; a positional activation such as &lt;code dir=&quot;auto&quot;&gt;charter activate mission-type qa&lt;/code&gt; refused with a traceback about preset-only flags, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; had the same defect. &lt;strong&gt;After:&lt;/strong&gt; both exit 2 cleanly only on a genuine flag misuse.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Every charter surface reads all of your configured org packs, in order&lt;/strong&gt; (#6006, #6012, #5779). An artifact only a later org pack defines now resolves everywhere, including &lt;code dir=&quot;auto&quot;&gt;charter context --include&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;, and a declared-but-unfetched pack fails closed, naming the pack and &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter fetch&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;charter lint&lt;/code&gt; no longer flags the built-in &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_035&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_039&lt;/code&gt; as orphaned&lt;/strong&gt; (#6017). Both now resolve against the shipped graph.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; no longer reports shared-agent skills, such as Cursor’s, as “skipped”&lt;/strong&gt; (#3788). The progress line now says setup is queued until project configuration is saved, and &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; make the same install decision.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A claim via &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; returns promptly again&lt;/strong&gt; (#6062). It no longer hangs on a baseline test run that held the pre-review-gate lock.&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 mission-state --audit&lt;/code&gt; passes again on migrated missions&lt;/strong&gt; (#6058). Dozens of older missions no longer report a false &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; blocker, while a lost claim agent or shell is still reported.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lane worktree reuse and crash recovery no longer refuse over a leftover &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/review-lock.json&lt;/code&gt;&lt;/strong&gt; (#5434). A migration backfills the fix in existing projects.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The orchestrator-api merge path no longer reports a completed, pushed merge as &lt;code dir=&quot;auto&quot;&gt;PREFLIGHT_FAILED&lt;/code&gt;&lt;/strong&gt; (#4796). A dirty lane worktree is now caught before anything changes and refuses with &lt;code dir=&quot;auto&quot;&gt;PREFLIGHT_FAILED&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;MERGE_UNSAFE_WORKTREE_DIRTY&lt;/code&gt;, so the verdict is truthful.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A review rejection interrupted before its commit, then retried, no longer deletes the review-cycle artifact&lt;/strong&gt; (#5969). The implementer is no longer wedged by a missing feedback file.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A coordination worktree switched to another branch is no longer read as the mission’s status&lt;/strong&gt; (#2908). Status reads, writes and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuse and name the fix, &lt;code dir=&quot;auto&quot;&gt;git -C &amp;#x3C;worktree&gt; checkout &amp;#x3C;branch&gt;&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lifecycle commands run from an owned checkout stay inside that checkout and on its write branch&lt;/strong&gt; (#6002). &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; and the decision commands gained an &lt;code dir=&quot;auto&quot;&gt;--owned-checkout &amp;#x3C;path&gt;&lt;/code&gt; option, and a flagless command adopts the validated checkout.&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 --owned-checkout&lt;/code&gt; no longer commits the decision ledger’s runtime lock&lt;/strong&gt; (#5925). If an earlier run already committed it, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent decision repair-runtime-lock --mission &amp;#x3C;handle&gt; --owned-checkout &amp;#x3C;path&gt;&lt;/code&gt; (try &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; first).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Owned-checkout mission create no longer resolves its lock across the owned-checkout boundary&lt;/strong&gt; (#5988). It anchors the lock on the owned checkout instead of the main repository root.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The implement step points at the real template path&lt;/strong&gt; (#5989). It names &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/mission-steps/software-dev/implement/prompt.md&lt;/code&gt;, so an agent can find the file it is told to check.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Broken references in an org pack’s &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; now fail validation&lt;/strong&gt; (#5833). A &lt;code dir=&quot;auto&quot;&gt;drg_dangling_edge&lt;/code&gt; error names the file and endpoint; a cross-pack reference is reported as an advisory instead.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Re-running charter synthesis after only upgrading spec-kitty no longer rewrites the synthesis manifest&lt;/strong&gt; (#5089). There is no longer a noisy no-op diff to review.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The retrospective status event records a repository-relative path&lt;/strong&gt; (#5868). A consolidation no longer leaks your home directory into tracked history.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The charter-pack cutover no longer hides the project &lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt;, so its &lt;code dir=&quot;auto&quot;&gt;pack_level&lt;/code&gt; reaches every contributor&lt;/strong&gt; (#6076). &lt;strong&gt;Before:&lt;/strong&gt; the cutover rewrote a consumer’s old ignore rules into &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/**&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;!.kittify/charter-packs/graph.yaml&lt;/code&gt; with no allow-rule for &lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt;, so the descriptor (carrying &lt;code dir=&quot;auto&quot;&gt;pack_id&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;pack_level&lt;/code&gt;) stayed ignored and each clone minted its own &lt;code dir=&quot;auto&quot;&gt;pack_id&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the cutover adds &lt;code dir=&quot;auto&quot;&gt;!.kittify/charter-packs/pack.yaml&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; adds it to an already-cutover project wherever the blanket rule is present; commit the file once. A &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; without the blanket rule, or that already allows &lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt;, is untouched.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Native &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent mission finalize-tasks&lt;/code&gt; now refuse stale content on API-authored Missions&lt;/strong&gt; (#5879). &lt;strong&gt;Before:&lt;/strong&gt; only the orchestrator-api checked that specification, plan and task content was current and finished, so switching to a native command completed or finalized a Mission with stale content. &lt;strong&gt;After:&lt;/strong&gt; both native commands refuse with the same &lt;code dir=&quot;auto&quot;&gt;DESIGN_*&lt;/code&gt; error before changing anything, and a successful native finalize keeps &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; working afterwards. Missions not authored through the API are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A staged software-dev Mission advances from &lt;code dir=&quot;auto&quot;&gt;tasks-outline&lt;/code&gt; after &lt;code dir=&quot;auto&quot;&gt;wps.yaml&lt;/code&gt; is committed&lt;/strong&gt; (#2642). The outline guard checks the manifest the prompt asks agents to write. Package generation does not require &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;; finalization checks it after generating it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; no longer silently commits the operator’s unstaged edits when a pre-commit hook stages files&lt;/strong&gt; (#5903). &lt;strong&gt;Before:&lt;/strong&gt; a pre-commit hook that runs &lt;code dir=&quot;auto&quot;&gt;git add -u&lt;/code&gt; (formatters, lint-staged-style hooks) staged the operator’s other modified tracked files into the commit &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; was building, so the commit carried files the operation never wrote, &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; reported success (exit 0), and the operator’s real index was left staging a revert of the swept edit (&lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; showed &lt;code dir=&quot;auto&quot;&gt;MM&lt;/code&gt;). Both commit routes were affected — the normal path-scoped commit and the index-deletion commit. &lt;strong&gt;After:&lt;/strong&gt; once the commit lands, &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; compares the committed paths against the ones it was asked to commit; if a hook swept in anything else, it re-syncs the operator’s index so no stale &lt;code dir=&quot;auto&quot;&gt;MM&lt;/code&gt; revert remains and reports the already-landed commit through the new &lt;code dir=&quot;auto&quot;&gt;SafeCommitUnrequestedPaths&lt;/code&gt; (contract error code &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_UNREQUESTED_PATHS&lt;/code&gt;, orchestrator-api contract &lt;code dir=&quot;auto&quot;&gt;1.15.0&lt;/code&gt;), naming the extra paths — a landed-commit outcome, not a failure-to-land. A commit with no such hook is unchanged, and hooks still run.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty research&lt;/code&gt; run from an owned single-branch checkout no longer scaffolds its artifacts into the primary; it honors the owned Mission, or refuses before writing&lt;/strong&gt; (#5882). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; exposed only &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;; run from an owned checkout it followed the worktree &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; pointer to the primary and scaffolded &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt; / the two research CSV stubs into a stale same-slug primary copy (or refused &lt;code dir=&quot;auto&quot;&gt;Mission not found&lt;/code&gt;) — silently redirecting authoring into an unowned, dirty primary. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; accepts &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; and auto-adopts an owned checkout when run from inside one (mirroring &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;, #6002); it resolves the four assets from the owned Mission directory through the placement seam, and an invalid owned target refuses before any &lt;code dir=&quot;auto&quot;&gt;mkdir&lt;/code&gt;/write. The non-owned path is unchanged; the coord-topology research/plan split stays with #2683.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty plan&lt;/code&gt; now forwards &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; to the owned-aware plan authoring seam&lt;/strong&gt; (#5882). &lt;strong&gt;Before:&lt;/strong&gt; the top-level &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; wrapper delegated to &lt;code dir=&quot;auto&quot;&gt;setup_plan&lt;/code&gt; (which gained owned support in #6002) but exposed no &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;, so an owned single-branch plan step had no owned authoring path at the top-level command. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty plan --mission &amp;#x3C;slug&gt; --owned-checkout &amp;#x3C;P&gt;&lt;/code&gt; reaches the owned-aware &lt;code dir=&quot;auto&quot;&gt;setup_plan&lt;/code&gt; seam and skips the plan interview, which cannot yet record its decisions in the owned checkout (#6143); the non-owned path is unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; now regenerate a drifted, generated Codex command skill instead of keeping it out of sync with the manifest&lt;/strong&gt; (#702). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty.&amp;#x3C;command&gt;/SKILL.md&lt;/code&gt; (Codex, Vibe, Pi, Letta) is generated, git-ignored state, but the installer treated a projection whose bytes matched neither the recorded &lt;code dir=&quot;auto&quot;&gt;.kittify/command-skills-manifest.json&lt;/code&gt; hash nor the current render as a local edit — so across two checkouts of one project (where the tracked manifest and the ignored bytes legitimately disagree) an untouched projection read as &lt;code dir=&quot;auto&quot;&gt;Managed command content has drifted&lt;/code&gt; and was kept, leaving &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; out of sync and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor skills&lt;/code&gt; red, with no automatic way back. &lt;strong&gt;After:&lt;/strong&gt; the reconcile regenerates a manifest-owned projection to the canonical render on this &lt;code dir=&quot;auto&quot;&gt;DERIVED&lt;/code&gt;/git-&lt;code dir=&quot;auto&quot;&gt;IGNORED&lt;/code&gt; surface (&lt;code dir=&quot;auto&quot;&gt;state/contract.py&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;shared_skills_projection&lt;/code&gt;), keeping &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; idempotent against the manifest. A hand edit to a &lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; command skill is replaced too (ADR 2026-10-04-3 amendment); your own non-&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; skills under &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; are untouched.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty moments on/off&lt;/code&gt; no longer wipes an unparseable &lt;code dir=&quot;auto&quot;&gt;config.toml&lt;/code&gt;&lt;/strong&gt; (#5451). &lt;strong&gt;Before:&lt;/strong&gt; when the config file was present but had a TOML syntax error, the non-strict &lt;code dir=&quot;auto&quot;&gt;write_toml_table_key&lt;/code&gt; helper treated it as empty and rewrote the whole file, destroying every other table and key (&lt;code dir=&quot;auto&quot;&gt;[sync].server_url&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;[hosted] drain&lt;/code&gt;, moments filters) with no backup and exit 0. &lt;strong&gt;After:&lt;/strong&gt; the helper distinguishes a genuinely absent file (still starts fresh and writes) from a present-but-unreadable one, including a file that is not valid UTF-8. &lt;code dir=&quot;auto&quot;&gt;moments on&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;moments off&lt;/code&gt; now refuse with a one-line error naming the file and exit 1, leaving the file byte-for-byte unchanged, like &lt;code dir=&quot;auto&quot;&gt;moments drain on&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Shadow Clone activation binds the current Git worktree&lt;/strong&gt; (#3215), even when the helper comes from another checkout. It refuses a &lt;code dir=&quot;auto&quot;&gt;.venv&lt;/code&gt; without a local CLI; the guide explains per-worktree login.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent tasks mark-status&lt;/code&gt; now updates the work package you name, and can mark a subtask skipped&lt;/strong&gt; (#5067). &lt;strong&gt;Before:&lt;/strong&gt; it marked the first matching subtask id across all work packages, so a shared id like &lt;code dir=&quot;auto&quot;&gt;T001&lt;/code&gt; could update the wrong work package, and a repeat re-emitted a duplicate event. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--wp WP02&lt;/code&gt; scopes the mark, an id shared by several work packages is refused before anything is written, and a repeat is a no-op. &lt;code dir=&quot;auto&quot;&gt;--status skipped&lt;/code&gt; (or its alias &lt;code dir=&quot;auto&quot;&gt;not_applicable&lt;/code&gt;) records a subtask as deliberately not done; it counts as finished for the review gate and survives a rollback to &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;agent status emit&lt;/code&gt; also accepts &lt;code dir=&quot;auto&quot;&gt;--wp WP02&lt;/code&gt; in place of the positional id.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-1&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The charter activation layer gets its own entry-point seam, &lt;code dir=&quot;auto&quot;&gt;charter.activation.api&lt;/code&gt;, with a boundary gate&lt;/strong&gt; (#6200, #6188). External consumers should import activation through that module, as they do offering through &lt;code dir=&quot;auto&quot;&gt;charter.offering.api&lt;/code&gt;. A new gate, &lt;code dir=&quot;auto&quot;&gt;test_runtime_charter_activation_boundary.py&lt;/code&gt;, freezes the 236 existing direct reaches into activation internals as a shrink-only baseline: a new reach fails, and so does a baseline row left behind after its reach is drained.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Start-up, glossary and the charter-offering ADR&lt;/strong&gt; (#5991, #3732, #5885). &lt;code dir=&quot;auto&quot;&gt;spec-kitty --help&lt;/code&gt; starts up faster by deferring heavy imports; the glossary now defines the charter offering, Charter Pack, activation preset, topic branch, Mission and Mission Run; and &lt;a href=&quot;/adr/4.x/2026-10-06-2-charter-offering-active-charter-and-activation-presets/&quot;&gt;ADR 2026-10-06-2&lt;/a&gt; records the charter-offering model behind the cutover.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; promises now run every night on Linux, macOS and Windows as plain Gherkin scenarios&lt;/strong&gt; (#6053).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every pull request now checks the acceptance scenarios, and the nightly run keeps versioned evidence&lt;/strong&gt; (#6133, #6134, #6135, #6136). The always-on architectural fast gate parses each feature file, checks its tags and confirms every gating step matches exactly one step definition. The nightly job writes one folder per pass plus an &lt;code dir=&quot;auto&quot;&gt;evidence.json&lt;/code&gt; bundle, fails when a gating pass produced no results, and keeps the upload for 30 days.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The pull-request mission-state audit always publishes every blocker, and a nightly run on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; backstops it&lt;/strong&gt; (#6087, #6058).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The 4.0.0 nightly interpreter, integration and contract shards are green again, and seven P0 escalations are closed&lt;/strong&gt; (#6024, #6025, #6026, #6027, #6028, #6029, #6030, #5989, #5990).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two dead &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; modules were removed (&lt;code dir=&quot;auto&quot;&gt;CharterParser&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;CharterSection&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;CharterTemplateResolver&lt;/code&gt; leave the public names; nothing imported them), a credential-redaction test now drives the real clone path, and the acceptance-test harness was split into smaller pieces&lt;/strong&gt; (#6009, #5987, #6097).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A mission-manifest edit now runs the &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;dossier&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;specify_cli_runtime&lt;/code&gt; tests per pull request, for maintainers&lt;/strong&gt; (#6125). &lt;code dir=&quot;auto&quot;&gt;tests/dossier&lt;/code&gt; used to run only nightly; a &lt;code dir=&quot;auto&quot;&gt;dossier&lt;/code&gt; CI module now runs it when dossier code or a manifest changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Maintainers gain an internal-only &lt;code dir=&quot;auto&quot;&gt;kitty-semi-auto&lt;/code&gt; command; &lt;code dir=&quot;auto&quot;&gt;packs/internal/&lt;/code&gt; never ships to consumers&lt;/strong&gt; (#6055, #6057).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A local Mission Status API service now answers the project header, paged Mission overviews and a change stream from each Mission’s event log, and a nightly job checks it against the Python reference&lt;/strong&gt; (#5529, for the Mission Status Read API, #5528). It is read-only and loopback-only, is built from &lt;code dir=&quot;auto&quot;&gt;services/mission-status-api/&lt;/code&gt; (Java and Spring Boot) and is not part of the PyPI package, and nothing in spec-kitty starts it yet. A tag-triggered release job publishes unsigned native binaries for four targets with build-provenance attestations (&lt;code dir=&quot;auto&quot;&gt;gh attestation verify &amp;#x3C;binary&gt; --repo spec-kitty/spec-kitty&lt;/code&gt;); no such tag has been pushed, so no release exists yet.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The PyPI sdist no longer ships the &lt;code dir=&quot;auto&quot;&gt;services/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; trees, and the Mission Status Read API service scaffold lands in the repository without shipping&lt;/strong&gt; (#5529). The sdist had picked up the nested &lt;code dir=&quot;auto&quot;&gt;README.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;CHANGELOG.md&lt;/code&gt; files of both trees. The Java service under &lt;code dir=&quot;auto&quot;&gt;services/mission-status-api/&lt;/code&gt; and its path-filtered &lt;code dir=&quot;auto&quot;&gt;Mission Status API&lt;/code&gt; CI workflow are repository-only: neither the wheel nor the sdist carries them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next --answer --json&lt;/code&gt; reports a decision-log commit refusal&lt;/strong&gt; (#3930). The decision response now includes a &lt;code dir=&quot;auto&quot;&gt;warnings&lt;/code&gt; entry when the Git commit fails (for example, a rejecting pre-commit hook). Any event already written remains on disk for recovery; the command’s commit behavior is unchanged.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;400rc6---2026-10-08&quot;&gt;[4.0.0rc6] - 2026-10-08&lt;/h2&gt;
&lt;h3 id=&quot;upgrade-notes-2&quot;&gt;Upgrade Notes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A work package leaves &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; only through a review verdict or an operator force with a note&lt;/strong&gt; (#5446). &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; no longer moves it for any agent; only its own implementer may pull back a submission no reviewer has claimed. To override, an operator runs &lt;code dir=&quot;auto&quot;&gt;agent action implement &amp;#x3C;WP&gt; --agent &amp;#x3C;who-implements&gt; --force --note &quot;&amp;#x3C;why&gt;&quot;&lt;/code&gt;; the note becomes the event reason. &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; needs a non-blank &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; needs &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;. The same rule holds on every transition surface: &lt;code dir=&quot;auto&quot;&gt;move-task --force&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent status emit --force&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api transition --force&lt;/code&gt; out of &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; need a note (&lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;--reason&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;agent status emit&lt;/code&gt;) unless the move records a verdict. Each misuse is refused before anything is written, exit 1 (a &lt;code dir=&quot;auto&quot;&gt;TRANSITION_REJECTED&lt;/code&gt; envelope on orchestrator-api). Scripts that forced out of review with no note must now pass one.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A forced move into &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; no longer satisfies &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;’s approval bound unless a review backs it&lt;/strong&gt; (#5721). &lt;code dir=&quot;auto&quot;&gt;move-task &amp;#x3C;WP&gt; --to approved --force&lt;/code&gt; (from any lane) and a &lt;code dir=&quot;auto&quot;&gt;--self-review-fallback&lt;/code&gt; approval now leave the work package bounded at its last review approval, or refused as &lt;code dir=&quot;auto&quot;&gt;APPROVAL_STAMP_MISSING&lt;/code&gt; when it has none (attest it with &lt;code dir=&quot;auto&quot;&gt;--attest-approved-reviewed&lt;/code&gt;). A forced approval still counts only when it is an approved-reviewed attestation, an arbiter override, or a hop out of &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; that carries an approved review result after a reviewer claimed the review (an unforced move into &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt;). An &lt;code dir=&quot;auto&quot;&gt;--approval-ref&lt;/code&gt;, the reference of the approval’s own review-cycle file and a reviewer name no longer count. Both &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent status emit&lt;/code&gt; print a one-line warning when such a forced approval is recorded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; removes the four retired &lt;code dir=&quot;auto&quot;&gt;spk-team-*&lt;/code&gt; skills it installed&lt;/strong&gt; (ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-06-1&lt;/code&gt;). Skills you wrote yourself are kept. The hosted commands still run when you type them, and with drain on they are listed in &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; again.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The rc5 note that four &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; fixes “do not fully hold” is superseded&lt;/strong&gt; (#5569, #5570, #5571, #5572). All four shapes it named are fixed in this release (see Fixed). The workarounds it listed are no longer needed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A Mission approved by a release before 4.0.0rc5 stops at &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; until each approved work package is re-reviewed or attested&lt;/strong&gt; (#5668). Those releases recorded no approval stamp (the lane head at approval time), so &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuses with &lt;code dir=&quot;auto&quot;&gt;APPROVAL_STAMP_MISSING&lt;/code&gt; and names the work package. Move it back for review and approve it again, or check the lane yourself and run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --attest-approved-reviewed &amp;#x3C;WP&gt; --attest-reason &quot;&amp;#x3C;what you checked&gt;&quot;&lt;/code&gt;. A commit made after an attestation is still refused. If an upgrade from before the #5457 fix committed to your lanes after approval, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuses with &lt;code dir=&quot;auto&quot;&gt;LANE_MOVED_AFTER_APPROVAL&lt;/code&gt;; approve the work packages again (attestation does not lift this one). See ADR &lt;a href=&quot;/adr/4.x/2026-10-04-5-approval-stamp-bounds-the-approved-claim/&quot;&gt;2026-10-04-5&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automation that reads a run’s &lt;code dir=&quot;auto&quot;&gt;decisions.events.jsonl&lt;/code&gt; sees new content for audit gates reached after a composed action&lt;/strong&gt; (#2562). A MEDIUM-band gate now requests &lt;code dir=&quot;auto&quot;&gt;decide_solo&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;open_stand_up&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;defer&lt;/code&gt; instead of approve/reject, and a LOW-band gate requests nothing because it auto-proceeds (see Changed). The event schema is unchanged. A run already paused at a MEDIUM gate under the old approve/reject options reads its missing &lt;code dir=&quot;auto&quot;&gt;raci:&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;significance:&lt;/code&gt; record as none only until its next poll: that poll records the MEDIUM band, and a later &lt;code dir=&quot;auto&quot;&gt;approve&lt;/code&gt; is then refused. Answer such a gate before polling the run again (#5855).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-2&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent status doctor&lt;/code&gt; now catches a work package that exists in the event log but has no prompt in &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt;, or the reverse&lt;/strong&gt; (#3433, #5901). &lt;strong&gt;Before:&lt;/strong&gt; a Mission could count eight work packages in its event log and seven prompts, and status doctor still reported it healthy, even with a stale &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; each mismatch is named with a recovery step. A &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt; work package whose prompt was archived is a warning; any other mismatch is an error.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The Mission Status contract now describes project health, drift findings and Ops invocation records&lt;/strong&gt; (#5776, for the Mission Status Read API, #5528). &lt;strong&gt;Before:&lt;/strong&gt; a dashboard could read a project’s Missions and work packages, but not whether the project itself was healthy, where its recorded state disagreed with its event logs, or which Ops had run. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;GET /project&lt;/code&gt; also carries the recorded Spec Kitty version, schema version, a &lt;code dir=&quot;auto&quot;&gt;health&lt;/code&gt; field (provisional), the current branch and the latest Mission activity. &lt;code dir=&quot;auto&quot;&gt;GET /drift&lt;/code&gt; lists status snapshots that disagree with their event logs, missing status files and missing expected branches, capped at 1000 findings. &lt;code dir=&quot;auto&quot;&gt;GET /ops/invocations&lt;/code&gt; pages Op records newest first, with closure, outcome and redacted evidence. Credential-shaped values are never served. All of it is additive to the unreleased &lt;code dir=&quot;auto&quot;&gt;1.0.0-SNAPSHOT&lt;/code&gt;, and the provisional parts are listed in &lt;code dir=&quot;auto&quot;&gt;contracts/mission-status/CHANGELOG.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;External orchestrators can author and commit Mission planning artifacts through the JSON API&lt;/strong&gt; (#5846). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; created specification and plan scaffolds, but a client had to write the intervening Mission files and run Git itself. &lt;strong&gt;After:&lt;/strong&gt; contract &lt;code dir=&quot;auto&quot;&gt;1.12.0&lt;/code&gt; adds &lt;code dir=&quot;auto&quot;&gt;design-context&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;interview-record&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;artifact-read&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;artifact-submit&lt;/code&gt; (including stdin JSON), &lt;code dir=&quot;auto&quot;&gt;design-validate&lt;/code&gt; and native &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;, so a client reaches ready work without touching Mission files or Git. Through orchestrator-api, stale parent or context revisions, unfinished stage content and finalized edits are refused, and the delivery profile names the translated Orchestrator 2 semantics and the Go guarantees it does not offer. See ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-07-2&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The built-in glossary now defines “tool-surface drift”, “integrating worktree” and “target-owned bookkeeping”&lt;/strong&gt; (#5761). &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; and its recovery runbook use these terms, but before they were defined only in this repository’s own docs, so your glossary tooling could not resolve them. The &lt;code dir=&quot;auto&quot;&gt;spec-kitty-core&lt;/code&gt; glossary pack now carries all three. See ADRs &lt;code dir=&quot;auto&quot;&gt;2026-10-04-3&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;2026-10-04-4&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A team can share agent commands through its charter packs instead of pasting private copies&lt;/strong&gt; (#5193). A pack can now declare a &lt;code dir=&quot;auto&quot;&gt;skill&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate skill &amp;#x3C;id&gt;&lt;/code&gt; installs it as &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;skill_namespace&gt;-&amp;#x3C;id&gt;&lt;/code&gt; for each configured tool, and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; keep it (before, the next upgrade pruned anything a pack did not ship). &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor skills&lt;/code&gt; flags a copy you edited, one older than its pack, or one its pack dropped, and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; gains a &lt;code dir=&quot;auto&quot;&gt;pack_skills&lt;/code&gt; key. &lt;code dir=&quot;auto&quot;&gt;skill_namespace&lt;/code&gt; and skill ids must be lowercase kebab-case; invalid values are refused before anything is written. See ADR &lt;code dir=&quot;auto&quot;&gt;2026-09-27-1&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Programs that read Mission status can build on a versioned, machine-readable contract&lt;/strong&gt; (#5558, for the Mission Status Read API, #5528). Before, a Mission’s status shape existed only in the code of its readers, and the dashboard that read it was removed in #5530. Now &lt;code dir=&quot;auto&quot;&gt;contracts/mission-status/&lt;/code&gt; describes it as an OpenAPI 3.1 document (project header, Mission overviews, one Mission, one work package, change stream), checked on every change against every Mission in this repository. It is version &lt;code dir=&quot;auto&quot;&gt;1.0.0-SNAPSHOT&lt;/code&gt; with no &lt;code dir=&quot;auto&quot;&gt;contract-*&lt;/code&gt; tag yet, so pin a commit until the first release. See &lt;code dir=&quot;auto&quot;&gt;contracts/README.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A coordination Mission now keeps its status, decision and trace records in one place from the moment it is created&lt;/strong&gt; (#5440). &lt;strong&gt;Before:&lt;/strong&gt; they sat in your repository root checkout until a coordination worktree existed, and later commands could look elsewhere. &lt;strong&gt;After:&lt;/strong&gt; create writes them to the coordination surface immediately. &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; commits an uncommitted decision ledger onto your target branch, and a real &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; creates a missing coordination worktree and continues; &lt;code dir=&quot;auto&quot;&gt;consolidate --dry-run&lt;/code&gt; still stops without creating one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-wp-status&lt;/code&gt; repairs Missions whose status snapshot misses work packages&lt;/strong&gt; (#5579). &lt;strong&gt;Before:&lt;/strong&gt; work packages (WPs) with no lane event were absent from the snapshot, so 51 Missions’ WP counts disagreed with their &lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt; files. &lt;strong&gt;After:&lt;/strong&gt; one run adds the missing &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; events (actor &lt;code dir=&quot;auto&quot;&gt;migration:backfill_wp_status&lt;/code&gt;), and a finished Mission (&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;accepted_at&lt;/code&gt;, or listed in &lt;code dir=&quot;auto&quot;&gt;--evidence-manifest&lt;/code&gt;) lands in &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;. Options: &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--evidence-manifest&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;; it is idempotent and leaves WPs that already have lane events alone. Give the full evidence manifest on the first live run. A Mission with a live coordination surface is refused (&lt;code dir=&quot;auto&quot;&gt;COORD_SURFACE_LIVE&lt;/code&gt;, exit 0); consolidate it first. See &lt;a href=&quot;/migrations/backfill-wp-status/&quot;&gt;How to repair a Mission whose status snapshot misses work packages&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A software-dev Mission that defines no interfaces can pass strict &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt;&lt;/strong&gt; (#5298). &lt;strong&gt;Before:&lt;/strong&gt; a missing &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; blocked strict &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; unless you used &lt;code dir=&quot;auto&quot;&gt;--lenient&lt;/code&gt; (which relaxes every path convention) or an empty placeholder directory. &lt;strong&gt;After:&lt;/strong&gt; add &lt;code dir=&quot;auto&quot;&gt;&quot;contracts&quot;: &quot;none&quot;&lt;/code&gt; and a non-empty &lt;code dir=&quot;auto&quot;&gt;&quot;contracts_rationale&quot;&lt;/code&gt; to the Mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; skips the requirement and shows the rationale in its warnings. A malformed declaration keeps the requirement and says what is wrong. See ADR &lt;a href=&quot;/adr/4.x/2026-10-04-1-mission-contracts-waiver-in-meta-json/&quot;&gt;2026-10-04-1&lt;/a&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 consolidate --abort --release-branch &amp;#x3C;branch&gt; --release-reason &quot;&amp;#x3C;why&gt;&quot;&lt;/code&gt; lets an abort finish by keeping a branch it cannot restore&lt;/strong&gt; (#5687, #5686). Use it when the rollback report says &lt;code dir=&quot;auto&quot;&gt;NOT restored&lt;/code&gt; and you want to keep that branch’s commits. The branch stays as it is and is reported as &lt;code dir=&quot;auto&quot;&gt;kept&lt;/code&gt; with your reason and a warning that it may hold unverified changes; review them afterwards. Every other branch is restored as usual. The flag is repeatable, needs &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--release-reason&lt;/code&gt;, and works only on the target, mission or coordination branch, never a lane branch; misuse is refused with &lt;code dir=&quot;auto&quot;&gt;RELEASE_BRANCH_INVALID&lt;/code&gt; (exit 2) before anything changes. It never keeps a branch &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; can restore, and stops applying once the branch moves.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-2&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission tracer files now show the entry format the retrospective actually reads&lt;/strong&gt; (#3072). &lt;strong&gt;Before:&lt;/strong&gt; the tracer procedure and the three seeded templates (&lt;code dir=&quot;auto&quot;&gt;approach.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;design-decisions.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tooling-friction.md&lt;/code&gt;) suggested a dated free-text comment, which the retrospective does not pick up, so tracer notes written that way never became findings. &lt;strong&gt;After:&lt;/strong&gt; they show a dated, bold-lead list entry, &lt;code dir=&quot;auto&quot;&gt;- **[YYYY-MM-DD][phase] Short symptom.** ...&lt;/code&gt;, with an inline example that an untouched template does not turn into a finding.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; advance after a composed action (every built-in &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; action, and a custom Mission step bound to a profile or contract) now records what the engine’s own advance records&lt;/strong&gt; (#2562). &lt;strong&gt;Before:&lt;/strong&gt; it recorded no &lt;code dir=&quot;auto&quot;&gt;raci:&amp;#x3C;step&gt;&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;significance:audit:&amp;#x3C;step&gt;&lt;/code&gt; decision and no &lt;code dir=&quot;auto&quot;&gt;SignificanceEvaluated&lt;/code&gt; event, a MEDIUM audit gate offered approve/reject and a LOW gate stopped for input. &lt;strong&gt;After:&lt;/strong&gt; it plans and commits through the engine, so those records appear, a MEDIUM gate offers &lt;code dir=&quot;auto&quot;&gt;decide_solo&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;open_stand_up&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;defer&lt;/code&gt;, a LOW gate auto-proceeds, and &lt;code dir=&quot;auto&quot;&gt;decisions.events.jsonl&lt;/code&gt; content changes for MEDIUM and LOW gates. A malformed significance configuration now returns a &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; Decision, as the engine path does, and a plan the run moved past is refused with nothing written (two writers committing at once now take turns, #5854).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The hosted Team Kitty commands no longer appear in &lt;code dir=&quot;auto&quot;&gt;spec-kitty --help&lt;/code&gt;, shell completion or the CLI reference, and the &lt;code dir=&quot;auto&quot;&gt;spk-team-*&lt;/code&gt; skills are retired&lt;/strong&gt; (ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-06-1&lt;/code&gt;). Team Kitty is no longer actively supported. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;auth&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;issue-search&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;live-work&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;moments&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;routes&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;zeitgeist&lt;/code&gt; were listed for everyone, and the shipped &lt;code dir=&quot;auto&quot;&gt;spk-team-auth&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spk-team-sync&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spk-team-tracker&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spk-team-connectors&lt;/code&gt; skills routed agents to the hosted product. &lt;strong&gt;After:&lt;/strong&gt; those six entries are hidden unless the hosted drain posture is on (&lt;code dir=&quot;auto&quot;&gt;hosted.drain&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;[hosted] drain&lt;/code&gt; in your personal &lt;code dir=&quot;auto&quot;&gt;config.toml&lt;/code&gt;); each still runs when you type it. &lt;code dir=&quot;auto&quot;&gt;tracker&lt;/code&gt; stays listed for its local providers (&lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;), and its help no longer points SaaS-backed providers at &lt;code dir=&quot;auto&quot;&gt;auth login&lt;/code&gt;. A command under a hidden group is now also left out of the main CLI reference.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine&lt;/code&gt; points at the activation view under its Selections block&lt;/strong&gt; (#4836). &lt;strong&gt;Before:&lt;/strong&gt; the block listed globally selected artifacts only, so after &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; an operator could read &lt;code dir=&quot;auto&quot;&gt;(none)&lt;/code&gt; everywhere and conclude the activation failed. &lt;strong&gt;After:&lt;/strong&gt; the block ends with &lt;code dir=&quot;auto&quot;&gt;Active charter (activated artifacts): spec-kitty charter list&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output is unchanged apart from the order of the &lt;code dir=&quot;auto&quot;&gt;collisions&lt;/code&gt; list.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The built-in onboarding procedure (&lt;code dir=&quot;auto&quot;&gt;onboard-external-agent-to-pack&lt;/code&gt;) covers the project tier and names its commands&lt;/strong&gt; (#4836). It now starts by choosing the tier (project or org pack) and gives each step that tier’s validate, graph and verify commands, instead of “run pack validation” and “per the pack’s build tooling”.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI now collects the list of tests once, before pytest, for the architectural battery and the &lt;code dir=&quot;auto&quot;&gt;ci&lt;/code&gt; module shard&lt;/strong&gt; (#5559). &lt;strong&gt;Before:&lt;/strong&gt; the first test that needed the list collected it during its own setup while four test workers competed for CPUs. &lt;strong&gt;After:&lt;/strong&gt; a step before pytest collects once into &lt;code dir=&quot;auto&quot;&gt;.pytest_cache/universe-store/&lt;/code&gt; and the tests read it; re-running the same commit restores it from the CI cache (key &lt;code dir=&quot;auto&quot;&gt;universe-&amp;#x3C;key&gt;-&amp;#x3C;commit&gt;&lt;/code&gt;). The step took 89 to 233 s on a first run and 0.3 to 0.6 s restored. A first run still collects once per consuming job, twice per pull-request update (battery leg 1/2 and the &lt;code dir=&quot;auto&quot;&gt;ci&lt;/code&gt; shard). The job fails when the list cannot be stored; only an unsupported platform falls back to collecting in the test.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every module’s shard timings are now measured, and no module is exempt from the exact-count check&lt;/strong&gt; (#5561). &lt;strong&gt;Before:&lt;/strong&gt; 17 modules could record a test count that disagreed with live collection. &lt;strong&gt;After:&lt;/strong&gt; every registry module has a captured count and a valid capture record, and &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_module_length_agreement.py&lt;/code&gt; checks all of them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The scheduled shard-timings recapture now covers every module, and a rejected push names the token problem&lt;/strong&gt; (#5536). &lt;strong&gt;Before:&lt;/strong&gt; it recaptured only &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;, and a rejected push (HTTP 403) surfaced as a raw git error. &lt;strong&gt;After:&lt;/strong&gt; it recaptures every module whose test count drifted, within a 70-minute budget, reports the rest as deferred and adds a plain follow-up commit to an open proposal. A rejected push names &lt;code dir=&quot;auto&quot;&gt;CHARTER_SHARD_RECAPTURE_TOKEN&lt;/code&gt; and the missing &lt;code dir=&quot;auto&quot;&gt;contents: write&lt;/code&gt; permission; the token itself still needs replacing, see #5624. The workflow is renamed &lt;code dir=&quot;auto&quot;&gt;ci-shard-recapture.yml&lt;/code&gt; and the proposal branch is now &lt;code dir=&quot;auto&quot;&gt;ci/recapture-shard-timings&lt;/code&gt;: close any pull request still open on &lt;code dir=&quot;auto&quot;&gt;ci/recapture-charter-shard-timings&lt;/code&gt;, because the new runs do not continue it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; stops with &lt;code dir=&quot;auto&quot;&gt;COORD_SEED_COMMIT_REFUSED&lt;/code&gt; when git refuses the commit of the coordination status files it creates&lt;/strong&gt; (#5651). &lt;strong&gt;Before:&lt;/strong&gt; it logged a warning and carried on, then stopped later with advice that did not name the refused commit. &lt;strong&gt;After:&lt;/strong&gt; it exits 1 before any branch moves, names the cause and the uncommitted files, and keeps them. Fix the cause (for example a rejecting git hook) and re-run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; stops with &lt;code dir=&quot;auto&quot;&gt;ALIAS_STATUS_EVENTS_NOT_PRESERVED&lt;/code&gt; when the composed directory’s event log has an event the primary Mission directory’s log lacks&lt;/strong&gt; (#5651). &lt;strong&gt;Before:&lt;/strong&gt; for a Mission whose primary directory has no &lt;code dir=&quot;auto&quot;&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; suffix, it ended in a traceback after rolling the run back. &lt;strong&gt;After:&lt;/strong&gt; it exits 1, names the Mission, the composed &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; directory and the missing event ids, removes nothing and keeps the rollback. Add those events to the primary log, then re-run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; stops with &lt;code dir=&quot;auto&quot;&gt;ALIAS_FILE_NOT_PRESERVED&lt;/code&gt; when a coordination file of the composed directory is missing from the primary Mission directory&lt;/strong&gt; (#5651). &lt;strong&gt;Before:&lt;/strong&gt; for a Mission whose primary directory has no &lt;code dir=&quot;auto&quot;&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; suffix, a trace, matrix, decision log or review cycle under the composed &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; directory stayed on the target and the reconciliation check refused the run. &lt;strong&gt;After:&lt;/strong&gt; the fold removes those files too, each only when the primary directory holds the same bytes. If it cannot prove that (for example a trace written under the composed name during the Mission), it exits 1, names the Mission, directory and files, removes nothing and keeps the rollback; such a Mission cannot be consolidated as it stands (#5751). A file that is not a coordination file is never removed and still fails the check.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; stops with &lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_BRANCH_MISMATCH&lt;/code&gt; when a Mission’s coordination branch is not the one Spec Kitty composes&lt;/strong&gt; (#5651). &lt;strong&gt;Before:&lt;/strong&gt; a coordination worktree on &lt;code dir=&quot;auto&quot;&gt;kitty/mission-&amp;#x3C;slug&gt;&lt;/code&gt;, without the &lt;code dir=&quot;auto&quot;&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; suffix, escaped as a traceback or advice that did not recover, plus a “before any state change” notice that was not true. &lt;strong&gt;After:&lt;/strong&gt; it exits 1 before any branch moves, names both branches, lists the status files left uncommitted in the coordination worktree and says they are kept. It prints no command: the coordination branch has to be &lt;code dir=&quot;auto&quot;&gt;kitty/mission-&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt;. Every other coordination-worktree failure behaves as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;After a &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; run was killed during the directory fold, the next run says to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt;, then again&lt;/strong&gt; (#5651). &lt;strong&gt;Before:&lt;/strong&gt; it listed the deleted files and told you to commit, stash or revert them, which never led to a successful consolidation. &lt;strong&gt;After:&lt;/strong&gt; when exactly the composed directory’s coordination files (status files, traces, matrices, decision log, review cycles) are deleted, it prints the recovery that works: &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt;, then &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two failed-commit warnings print the command that re-runs the step, not a raw &lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt; recipe&lt;/strong&gt; (#5708). &lt;strong&gt;Before:&lt;/strong&gt; a failed retrospective commit after &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, and a failed metadata commit in &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission close --discard&lt;/code&gt;, told you to commit by hand. &lt;strong&gt;After:&lt;/strong&gt; both print &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission close --mission &amp;#x3C;slug&gt;&lt;/code&gt; (with &lt;code dir=&quot;auto&quot;&gt;--discard --force&lt;/code&gt; for the discard leg). For a Mission with no recorded identity, the retrospective warning says to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-identity --mission &amp;#x3C;slug&gt;&lt;/code&gt; first.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-2&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; now returns the real instructions for a Mission’s planning steps&lt;/strong&gt; (#3909, #5908). &lt;strong&gt;Before:&lt;/strong&gt; for &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; and the other Mission-level steps, the prompt file held only a heading and “This step is dispatched via composition.”, with no instructions and a next command that left out the Mission. &lt;strong&gt;After:&lt;/strong&gt; the step’s own prompt template is used. A step that has no template, such as &lt;code dir=&quot;auto&quot;&gt;discovery&lt;/code&gt; or a step inserted by a project workflow, gets a short prompt that names the step and gives the exact &lt;code dir=&quot;auto&quot;&gt;spec-kitty next --agent &amp;#x3C;agent&gt; --mission &amp;#x3C;slug&gt;&lt;/code&gt; command.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; no longer warns about missing &lt;code dir=&quot;auto&quot;&gt;plan_concern_refs&lt;/code&gt; when &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt; declares no implementation concerns&lt;/strong&gt; (#5079, #5922). &lt;strong&gt;Before:&lt;/strong&gt; a work-package manifest that included the concern fields got a &lt;code dir=&quot;auto&quot;&gt;missing plan_concern_refs and cross_cutting is not set&lt;/code&gt; warning per work package, even when the plan had no &lt;code dir=&quot;auto&quot;&gt;IC-##&lt;/code&gt; concern to cite, so agents marked work packages &lt;code dir=&quot;auto&quot;&gt;cross_cutting&lt;/code&gt; just to silence it. &lt;strong&gt;After:&lt;/strong&gt; the warning appears only when &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt; has an &lt;code dir=&quot;auto&quot;&gt;IC-##&lt;/code&gt; heading.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer loses status events that exist only on the coordination branch&lt;/strong&gt; (#3272, #5914). &lt;strong&gt;Before:&lt;/strong&gt; an event committed only on the coordination branch, such as a late cut-over seed, was deleted with the branch at teardown, so the consolidated Mission landed un-cut-over and turned CI red. &lt;strong&gt;After:&lt;/strong&gt; teardown first unions the coordination log into the primary Mission log and commits it. If that step fails, the coordination branch, worktree and marker are kept and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; exits with the cause; fix it and run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A blank line added to a Mission status log now blocks the next &lt;code dir=&quot;auto&quot;&gt;--no-auto-commit&lt;/code&gt; lane allocation&lt;/strong&gt; (#2570). The allocator continues to accept its own uncommitted claim events, but treats an extra blank line as an unrelated edit and reports the log under “Planning artifacts not committed” instead of silently proceeding.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lane test runs fail loudly when &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; comes from another checkout&lt;/strong&gt; (#5096). The built-in implement prompt now asks for the project’s configured linter instead of assuming Python, Ruff, and a local &lt;code dir=&quot;auto&quot;&gt;.venv&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 consolidate --resume&lt;/code&gt; now records the right review baseline when the first attempt had already landed the Mission&lt;/strong&gt; (#3688, #5915). &lt;strong&gt;Before:&lt;/strong&gt; if a run landed the Mission and then failed, the resumed run recorded the Mission’s own squash commit as &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, so a post-merge review diff from that baseline was empty. &lt;strong&gt;After:&lt;/strong&gt; a resume records the target tip saved before the first attempt changed anything. A wrong baseline recorded by an earlier version is not rewritten.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A failed status commit no longer erases another agent’s committed transition, and a committed claim is never reported as rolled back&lt;/strong&gt; (#5819, #5804, #5468). &lt;strong&gt;Before:&lt;/strong&gt; a failed &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; commit cut the status log back to a size measured earlier, so a transition another agent had committed meanwhile could vanish, and a claim that had reached git could still be reported as rolled back. &lt;strong&gt;After:&lt;/strong&gt; the claim, its commit and its undo run under one lock per Mission, and the undo removes only this operation’s uncommitted rows. A claim that is already committed (always so on a coordination Mission) is reported as ”&lt;wp&gt; claim was committed; the follow-up &lt;operation&gt; commit failed: &lt;error&gt;” with exit 1; there is nothing to revert. If it cannot prove the rows are its own, it leaves the log unchanged and reports &lt;code dir=&quot;auto&quot;&gt;STATUS_ROLLBACK_REFUSED&lt;/code&gt;; run the &lt;code dir=&quot;auto&quot;&gt;git diff HEAD -- &amp;#x3C;log&gt;&lt;/code&gt; command the message shows, keep or revert those rows yourself, then re-run.&lt;/error&gt;&lt;/operation&gt;&lt;/wp&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Two agents recording &lt;code dir=&quot;auto&quot;&gt;tracer-append&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;add-history&lt;/code&gt; at once now keep both entries&lt;/strong&gt; (#5467, #5820). &lt;strong&gt;Before:&lt;/strong&gt; both read the same file, and the second write replaced the first agent’s entry. &lt;strong&gt;After:&lt;/strong&gt; each reads and writes under the same per-Mission lock, so both entries are kept.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Two overlapping claims in one &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; checkout can no longer both pass the shared-checkout check&lt;/strong&gt; (#5796). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api start-implementation&lt;/code&gt; each scanned for a busy checkout and then claimed, so two started together both saw it free. &lt;strong&gt;After:&lt;/strong&gt; the scan and the claim run under one lock per checkout; the second claim is refused with &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_OCCUPIED&lt;/code&gt;. A claim that waits too long for that lock exits 1 with &lt;code dir=&quot;auto&quot;&gt;STATUS_LOCK_HELD&lt;/code&gt; and asks you to retry.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; now warn when another actor works in the same checkout&lt;/strong&gt; (#5099; the commit-scope half is #5443). &lt;strong&gt;Before:&lt;/strong&gt; an agent could edit alongside another’s work package unaware. &lt;strong&gt;After:&lt;/strong&gt; the command names the other actor and work package and continues; it never refuses. The shipped implement and review prompts state the rule: one writer per checkout.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Two owned checkouts that advance Missions at the same time no longer block each other with &lt;code dir=&quot;auto&quot;&gt;OWNED_COORDINATION_WORKSPACE_UNAVAILABLE&lt;/code&gt;&lt;/strong&gt; (#5894). &lt;strong&gt;Before:&lt;/strong&gt; while one process ran &lt;code dir=&quot;auto&quot;&gt;git worktree add&lt;/code&gt; for its coordination worktree, &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; in the other could catch the new worktree half-registered, and &lt;code dir=&quot;auto&quot;&gt;git worktree list&lt;/code&gt; exited 128. It then stopped with a &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; decision that suggested &lt;code dir=&quot;auto&quot;&gt;git worktree prune&lt;/code&gt;, and the reason left out git’s own message. &lt;strong&gt;After:&lt;/strong&gt; that state is retried within the existing bounded window, the same as git lock contention. A registration that stays broken is still refused, and the reason now ends with git’s diagnostic.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt;’s claim commit carries only what the claim wrote&lt;/strong&gt; (#5673). &lt;strong&gt;Before:&lt;/strong&gt; the claim commit took &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, the Mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and the claimed work package’s prompt whether or not the claim had changed them, so a pending &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; edit went in with it; &lt;code dir=&quot;auto&quot;&gt;--no-auto-commit&lt;/code&gt; staged that &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and prompt the same way. &lt;strong&gt;After:&lt;/strong&gt; the claim carries only the status files, &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; when the first claim’s VCS lock changed it, and the prompt’s workspace stamp. Your other edits in the Mission folder are handled as before: with auto-commit, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s planning-artifacts commit still records them, and with &lt;code dir=&quot;auto&quot;&gt;--no-auto-commit&lt;/code&gt; they still refuse the claim. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; commits the same status files, and a VCS lock left by a claim that failed before its commit is committed by the retry.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; gives three safe-commit failures their own codes, contract &lt;code dir=&quot;auto&quot;&gt;1.14.0&lt;/code&gt;&lt;/strong&gt; (#5443). &lt;strong&gt;Before:&lt;/strong&gt; a symlink-loop path, a path both requested and deleted from the index, and a commit that landed but left the index staging a committed path had no distinct code. &lt;strong&gt;After:&lt;/strong&gt; they report &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_PATH_LOOP&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_INDEX_DELETION_CONFLICT&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_INDEX_RESIDUE&lt;/code&gt;. The last means the commit did land (&lt;code dir=&quot;auto&quot;&gt;commit_sha&lt;/code&gt; names it), unlike &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_RECOVERY_FAILED&lt;/code&gt;, which may not have. A client that matches error codes should handle the new values.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Recording a Mission’s number during merge or consolidation no longer commits your other work&lt;/strong&gt; (#5443). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; bookkeeping commit could carry files you had staged or your own pending &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; edit, and could land on another branch or a detached HEAD. &lt;strong&gt;After:&lt;/strong&gt; it commits only that Mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, on the Mission branch from a temporary worktree or, when that branch does not carry &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; (a coordination-topology Mission), onto the merge target in your primary checkout, and leaves your staged, unstaged and untracked work as it was. If &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is untracked, ignored or has your own pending edits, nothing is written and the merge summary says the number could not be baked, with the reason.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; keeps &lt;code dir=&quot;auto&quot;&gt;project_uuid&lt;/code&gt; and your own keys in &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;&lt;/strong&gt; (#5229). &lt;strong&gt;Before:&lt;/strong&gt; the upgrade could drop &lt;code dir=&quot;auto&quot;&gt;project_uuid&lt;/code&gt;, the schema capability map or keys you had added, and a failed upgrade restored the version stamp without the capability map. &lt;strong&gt;After:&lt;/strong&gt; every metadata writer keeps the keys it does not own, the upgrade stamps the same capability map &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; writes, and the writes are atomic. A failed upgrade restores the map along with the version stamp. A &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt; that is not valid YAML is refused instead of replaced.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A failed schema-3 upgrade no longer leaves backup debris in &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;&lt;/strong&gt; (#4763). &lt;strong&gt;Before:&lt;/strong&gt; rolling back copied the backup’s &lt;code dir=&quot;auto&quot;&gt;kitty-specs-backup&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;gitignore-backup&lt;/code&gt; entries into &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;, left &lt;code dir=&quot;auto&quot;&gt;.kittify/.migration-backup&lt;/code&gt; behind, and kept a &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; the run had created. &lt;strong&gt;After:&lt;/strong&gt; a full rollback restores &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; as they were and removes the backup. If the restore is only partial, the backup is kept so you can recover from it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit &amp;#x3C;dir&gt;/&lt;/code&gt; now commits a staged rename completely&lt;/strong&gt; (#5401). &lt;strong&gt;Before:&lt;/strong&gt; for a rename inside the directory argument, the old path was not removed in the commit. &lt;strong&gt;After:&lt;/strong&gt; the commit removes the old path and adds the new one, and nothing of the rename is left staged. A rename with one side outside the directory argument is refused, naming the outside path.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty spec-commit&lt;/code&gt; commit a symlink as the link, never the file it points to&lt;/strong&gt; (#5671). &lt;strong&gt;Before:&lt;/strong&gt; a symlink argument was resolved to its target, so the target’s uncommitted work was committed instead of the link. &lt;strong&gt;After:&lt;/strong&gt; the link is committed as a link, tracked or untracked, relative or absolute, or reached through a directory, and a symlinked directory is committed as one link. A symlink loop is refused, and the target’s work stays uncommitted.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit&lt;/code&gt; fails on a path that does not exist, and names the path git refused&lt;/strong&gt; (#4722). &lt;strong&gt;Before:&lt;/strong&gt; a path unknown both on disk and to git printed “No requested changes to commit” and exited 0, and a failed batch did not say which path broke it. &lt;strong&gt;After:&lt;/strong&gt; such a path is an error, and a batch with one bad path names that path and git’s reason and commits nothing. A deleted tracked file is still a valid argument.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The shipped skills, git toolguide and upgrade docs no longer tell agents to stage with &lt;code dir=&quot;auto&quot;&gt;git add -A&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;git add .&lt;/code&gt;&lt;/strong&gt; (#5443). &lt;strong&gt;Before:&lt;/strong&gt; the shipped skills, the git worktree toolguide and two upgrade docs recommended sweeping or directory adds, so an agent that followed them could commit unrelated work. &lt;strong&gt;After:&lt;/strong&gt; they teach explicit-path staging with &lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit &amp;#x3C;paths&gt;&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;git add -- &amp;#x3C;files&gt;&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A teammate on a second clone no longer lands rejected work or reviews a superseded lane&lt;/strong&gt; (#5780, #5758). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; trusted your local branches, so a rejection your teammate had pushed landed as done, and &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; after a &lt;code dir=&quot;auto&quot;&gt;git pull&lt;/code&gt; still opened the old lane. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api accept-mission&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;consolidate-mission&lt;/code&gt; ask the remote first and refuse before anything moves with &lt;code dir=&quot;auto&quot;&gt;ORIGIN_STATUS_STALE&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_STALE&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;ORIGIN_UNREACHABLE&lt;/code&gt;. Review fast-forwards a behind lane or refuses a diverged one with &lt;code dir=&quot;auto&quot;&gt;ORIGIN_LANE_DIVERGED&lt;/code&gt;. No remote: unchanged. &lt;code dir=&quot;auto&quot;&gt;--origin-check warn&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ORIGIN_CHECK=warn&lt;/code&gt; turns refusals into warnings; &lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt; contacts nothing and accepts stale evidence, so a pushed rejection can land as done. Review honors only the variable. Contract 1.11.0 adds &lt;code dir=&quot;auto&quot;&gt;data.origin_freshness&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;When a repository has remotes but none owns the branch, the origin check now refuses with &lt;code dir=&quot;auto&quot;&gt;ORIGIN_REMOTE_AMBIGUOUS&lt;/code&gt;&lt;/strong&gt; (#5780). &lt;strong&gt;Before:&lt;/strong&gt; with several remotes and none of them &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt;, no &lt;code dir=&quot;auto&quot;&gt;branch.&amp;#x3C;name&gt;.remote&lt;/code&gt; set, the check found no remote to ask and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; passed silently. &lt;strong&gt;After:&lt;/strong&gt; they refuse before anything moves, naming the remotes and &lt;code dir=&quot;auto&quot;&gt;git config branch.&amp;#x3C;name&gt;.remote &amp;#x3C;remote&gt;&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;--origin-check warn&lt;/code&gt; turns it into a warning, and review warns. A repository with no remote at all is still not contacted and still passes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now install the merge-driver settings on a clone of an initialized project, and keep ones you customized&lt;/strong&gt; (#5759). &lt;strong&gt;Before:&lt;/strong&gt; a fresh clone never received them, so its first &lt;code dir=&quot;auto&quot;&gt;git pull&lt;/code&gt; of a divergent Mission left conflict markers in &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and every command failed with &lt;code dir=&quot;auto&quot;&gt;MISSION_META_READ_ERROR&lt;/code&gt;; and an install would have overwritten a driver command you had set yourself. &lt;strong&gt;After:&lt;/strong&gt; either command installs them idempotently (&lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; still reports “Already initialized”), and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; lists the install in its one outcome. A &lt;code dir=&quot;auto&quot;&gt;merge.&amp;#x3C;key&gt;.name&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;.driver&lt;/code&gt; value you set is kept, with a warning naming the key and the value Spec Kitty ships.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer commits your uncommitted work, bypasses your pre-commit hook, or commits after a failed run&lt;/strong&gt; (#5443). &lt;strong&gt;Before:&lt;/strong&gt; upgrading a pre-3.0 project ran the schema-3 migration’s own &lt;code dir=&quot;auto&quot;&gt;git add -A&lt;/code&gt; commit, retrying with &lt;code dir=&quot;auto&quot;&gt;--no-verify&lt;/code&gt;, so untracked secrets, staged files and unstaged edits were committed; a failed migration still committed its backup (ignored files included); generated commands were wrongly held for review, skipping the whole commit. &lt;strong&gt;After:&lt;/strong&gt; the upgrade commits only files it wrote that were clean before, honors hooks, commits nothing after a failure, never commits paths ignored before the run, holds and names only files lacking the version marker, and says why when it does not commit. A file a migration untracks is removed in the same commit and stays on disk. A pre-commit hook that stages files itself (&lt;code dir=&quot;auto&quot;&gt;git add -u&lt;/code&gt;) can still add them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-runtime-state&lt;/code&gt; no longer leaves a stale &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; behind&lt;/strong&gt; (#5862). &lt;strong&gt;Before:&lt;/strong&gt; it appended its seed events (for example &lt;code dir=&quot;auto&quot;&gt;tracker_refs&lt;/code&gt;) to the event log but did not regenerate an existing &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, so the snapshot disagreed with the log and status validation and the TeamSpace preview reported &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; every run (also a re-run with nothing new to seed, so an already-stale snapshot repairs itself, and the upgrade migration) refreshes an existing &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;; a failed refresh is reported as a warning. &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; commits the refreshed snapshot together with the seed events.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;, including &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt;, no longer rewrites your Missions’ status history&lt;/strong&gt; (#5811). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt; also consented to the TeamSpace mission-state repair, which ran over every directory under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;. On an up-to-date project it rewrote the append-only &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; of nearly every Mission (adding &lt;code dir=&quot;auto&quot;&gt;&quot;reason_source&quot;: null&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;&quot;review_result&quot;: null&lt;/code&gt;, re-sorting rows), re-wrote &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, and still reported “blockers cleared” when Missions errored. &lt;strong&gt;After:&lt;/strong&gt; upgrade only reports mission-state blockers, and only when hosted drain is on; the repair runs only through &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --fix&lt;/code&gt;. That repair now leaves history written by the current status writer byte-identical and in its original order, rewrites &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; only for a Mission whose log it changed, never creates &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, and exits non-zero naming every Mission it could not repair. History already rewritten by an earlier upgrade is not restored; it is git-recoverable while uncommitted. See ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-07-1&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A leftover &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; directory is no longer treated as a Mission&lt;/strong&gt; (#5812). &lt;strong&gt;Before:&lt;/strong&gt; a directory holding only untracked or gitignored files (for example a stray &lt;code dir=&quot;auto&quot;&gt;*.lock&lt;/code&gt;) raised an &lt;code dir=&quot;auto&quot;&gt;IDENTITY_MISSING&lt;/code&gt; blocker, and the repair minted a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; into it. &lt;strong&gt;After:&lt;/strong&gt; a directory is a Mission only when its &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; carries a &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; or its &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is tracked in git (also for a project nested inside a larger repository). Anything else gets one non-blocking &lt;code dir=&quot;auto&quot;&gt;RESIDUE_DIRECTORY&lt;/code&gt; finding and is never written into.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Another agent can no longer pull a work package out of review or approval with exit 0 and a made-up rework reason&lt;/strong&gt; (#5446). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent action implement &amp;#x3C;WP&gt; --agent &amp;#x3C;other&gt;&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; work package force-moved it to &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; with the reason “Re-implementing after review feedback”, although no reviewer had rejected anything; the reviewer silently lost their claim and an approval was discarded. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; is refused as a claim conflict naming the reviewer, &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; is refused naming &lt;code dir=&quot;auto&quot;&gt;move-task &amp;#x3C;WP&gt; --to planned --review-feedback-file &amp;#x3C;file&gt;&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; is refused unless the caller is the work package’s implementer of record. No event carries a review reason that no reviewer gave. &lt;strong&gt;Also:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task --force&lt;/code&gt; out of &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; no longer records a made-up &lt;code dir=&quot;auto&quot;&gt;Force move to &amp;#x3C;lane&gt;&lt;/code&gt; reason or a &lt;code dir=&quot;auto&quot;&gt;changes_requested&lt;/code&gt; review result that no reviewer gave; without &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; it is refused on every transition surface (&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent status emit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;orchestrator-api transition&lt;/code&gt;), with the existing note-required message.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A work package forced out of &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; with no verdict can be approved again&lt;/strong&gt; (#5446). &lt;strong&gt;Before:&lt;/strong&gt; the forced exit left an empty review result in the status log, and every later approval was refused with “review-cycle-damaged-event-record.md has no parseable review verdict. Repair the review artifact”, naming a file that did not exist. &lt;strong&gt;After:&lt;/strong&gt; an empty result reads as “no verdict on record”, so the next review approves normally; a genuinely unreadable result is still refused, with a message that names a route that works (reject with &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt;, then review again). The status board no longer labels such a work package as damaged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer warns that a reviewer approved their own work after an honest reject, rework and approve loop&lt;/strong&gt; (#5340). &lt;strong&gt;Before:&lt;/strong&gt; the hollow-review check counted the reviewer’s own rework verdict (&lt;code dir=&quot;auto&quot;&gt;in_review -&gt; in_progress&lt;/code&gt;) as the implementer, so implementer and reviewer looked identical. &lt;strong&gt;After:&lt;/strong&gt; the check reads the same implementer-of-record projection the move-task and implement guards use (&lt;code dir=&quot;auto&quot;&gt;status/review_roles&lt;/code&gt;), and compares full actor identities, so two agents of the same tool with different profiles are not confused either.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A forced re-approval no longer lets a commit made after the real review land through &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;&lt;/strong&gt; (#5721, forced-approval residual). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task &amp;#x3C;WP&gt; --to approved --force&lt;/code&gt; restamped the lane at its current tip and a late commit landed at exit 0: the recorded reviewer is filled from &lt;code dir=&quot;auto&quot;&gt;git config user.name&lt;/code&gt;, with auto-commit on the approval writes its own review-cycle file whose pointer replaced the reference, and forcing the work package into &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; first attached an approved review result. &lt;strong&gt;After:&lt;/strong&gt; the bound reads the newest review approval (an unforced approval, an arbiter override, an attestation, or a review result after a reviewer’s claim), so the late commit is refused with &lt;code dir=&quot;auto&quot;&gt;LANE_MOVED_AFTER_APPROVAL&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A second review rejection no longer reuses or overwrites &lt;code dir=&quot;auto&quot;&gt;review-cycle-1.md&lt;/code&gt;&lt;/strong&gt; (#5194). &lt;strong&gt;Before:&lt;/strong&gt; on a Mission with a coordination branch, the next cycle number was counted only on the surface being written, so a cycle 1 recorded on the primary surface was numbered 1 again on the coordination surface, and the write replaced any existing file. &lt;strong&gt;After:&lt;/strong&gt; the number is taken across every surface the review readers consult, the review prompt advertises the same number, and a cycle file is created exclusively, never replaced.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine pack validate&lt;/code&gt; no longer reports a DRG edge in a pack’s &lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; files to the pack’s own asset as dangling&lt;/strong&gt; (#5538). &lt;strong&gt;Before:&lt;/strong&gt; the validator scanned &lt;code dir=&quot;auto&quot;&gt;assets/*.asset.yaml&lt;/code&gt; sidecars but never registered their &lt;code dir=&quot;auto&quot;&gt;asset:&amp;#x3C;id&gt;&lt;/code&gt; URNs, so an edge such as &lt;code dir=&quot;auto&quot;&gt;directive:ACME-001 -&gt; asset:company-logo&lt;/code&gt; failed with &lt;code dir=&quot;auto&quot;&gt;drg_dangling_edge&lt;/code&gt; and exit 1. &lt;strong&gt;After:&lt;/strong&gt; every artifact kind the validator scans registers its URNs, read from the one artifact-kind list, so the edge validates.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Operator hints and shipped skills name real config keys and current commands&lt;/strong&gt; (#4836). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine&lt;/code&gt; told you to add a &lt;code dir=&quot;auto&quot;&gt;&apos;charter.offering.org&apos;&lt;/code&gt; block to &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;; the runtime doctor said to set &lt;code dir=&quot;auto&quot;&gt;charter.offering.template_set&lt;/code&gt;; shipped skills cited &lt;code dir=&quot;auto&quot;&gt;governance.charter.offering.*&lt;/code&gt; keys and told agents to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine validate .kittify/&lt;/code&gt;; and &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt;, charter compilation and org-pack discovery hints said to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine validate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine fetch&lt;/code&gt;. None of those keys exist, and the commands print a deprecation banner that agents treat as a fault. &lt;strong&gt;After:&lt;/strong&gt; the hints say &lt;code dir=&quot;auto&quot;&gt;charter_packs.org&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;governance.charter.template_set&lt;/code&gt;, the skills cite &lt;code dir=&quot;auto&quot;&gt;governance.charter.*&lt;/code&gt; (and, for the SPDD skill, the &lt;code dir=&quot;auto&quot;&gt;activated_*&lt;/code&gt; keys its helper actually reads), and every hint names &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter validate|new|fetch|org&lt;/code&gt;. The &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; deprecation banner no longer claims &lt;code dir=&quot;auto&quot;&gt;mission-type list&lt;/code&gt; has no &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; home; it names &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter mission-type list --include-inactive&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A teammate’s &lt;code dir=&quot;auto&quot;&gt;git pull&lt;/code&gt; no longer silently undoes &lt;code dir=&quot;auto&quot;&gt;mission close --discard&lt;/code&gt;&lt;/strong&gt; (#5460). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; merge driver ignored the merge base, so a clone that had discarded a Mission lost the discard on an ordinary &lt;code dir=&quot;auto&quot;&gt;git pull&lt;/code&gt; or merge when a teammate had changed an unrelated key, with exit 0. &lt;strong&gt;After:&lt;/strong&gt; for ordinary merges each key is compared against the merge base: a change, removal or addition on one side survives, keys that belong together move as one, and only a genuine both-sides conflict keeps the old precedence. &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;’s mission-to-target merge (squash or merge strategy) keeps the two-way rule (its ancestry is stale after a reopen) through the internal &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_META_MERGE_TWO_WAY&lt;/code&gt; variable (set by consolidate; never set it by hand), while its merges with real ancestry are base-aware.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;In-flight PR-bound Missions no longer fail the cutover guard on their first push&lt;/strong&gt; (#5835, #5300). &lt;strong&gt;Before:&lt;/strong&gt; once a work package was claimed, &lt;code dir=&quot;auto&quot;&gt;spec-kitty cutover-guard&lt;/code&gt; (and the dogfood check) failed every unaccepted Mission until you ran &lt;code dir=&quot;auto&quot;&gt;migrate backfill-runtime-state&lt;/code&gt; by hand. &lt;strong&gt;After:&lt;/strong&gt; a Mission with no &lt;code dir=&quot;auto&quot;&gt;status_phase&lt;/code&gt; stamp, no accept/merge evidence and no claim runtime in its WP files (&lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;assignee&lt;/code&gt;, a completed review; planning-time &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tracker_refs&lt;/code&gt; do not count) passes with a “pre-accept” note. Accepted, merged, legacy or malformed Missions still fail, as do an ambiguous &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; (a repeated key, a non-string &lt;code dir=&quot;auto&quot;&gt;accepted_at&lt;/code&gt;) and an unreadable &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt;. &lt;strong&gt;Changed output:&lt;/strong&gt; some failure reasons and remedies are reworded; for the reasons about a missing stamp, match the leading &lt;code dir=&quot;auto&quot;&gt;status_phase not flipped&lt;/code&gt; text, not the sentence. &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; gains an additive &lt;code dir=&quot;auto&quot;&gt;exempt&lt;/code&gt; list of &lt;code dir=&quot;auto&quot;&gt;{slug, reasons}&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 upgrade&lt;/code&gt; no longer fails when a configured tool folder such as &lt;code dir=&quot;auto&quot;&gt;.claude/&lt;/code&gt; is missing, and a failed upgrade no longer records the new version&lt;/strong&gt; (#4275). &lt;strong&gt;Before:&lt;/strong&gt; the upgrade could stop on the missing folder, and a failed run could still leave the new &lt;code dir=&quot;auto&quot;&gt;version&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;last_upgraded_at&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;, so the project looked upgraded. &lt;strong&gt;After:&lt;/strong&gt; a failed upgrade restores all three to their previous values and says so (&lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml restored to &amp;#x3C;version&gt;; the change is uncommitted&lt;/code&gt;); a run that ends with unresolved tool-surface drift keeps its stamp. A conflict between two owner effects now names both owners and the fields that differ (&lt;code dir=&quot;auto&quot;&gt;Owner effect conflict at &amp;#x3C;path&gt;: &amp;#x3C;a&gt; vs &amp;#x3C;b&gt; (differs in: ...)&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 doctor skills&lt;/code&gt; now reports pack skills that are in force but not installed, and &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; installs them; it also fails when no configured tool folder exists&lt;/strong&gt; (#5801). &lt;strong&gt;Before:&lt;/strong&gt; a deleted or never-projected pack skill passed the check, and a project with none of its tool folders reported healthy. &lt;strong&gt;After:&lt;/strong&gt; the check reports &lt;code dir=&quot;auto&quot;&gt;missing&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;no_tool_folder&lt;/code&gt; findings, and &lt;code dir=&quot;auto&quot;&gt;doctor skills --fix&lt;/code&gt; projects the missing skills (their paths appear in &lt;code dir=&quot;auto&quot;&gt;repaired_paths&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; also warns &lt;code dir=&quot;auto&quot;&gt;pack_skill_missing&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A refused &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; create on a protected target no longer blocks the retry, and re-running it for the same name refuses with one stable code&lt;/strong&gt; (#5704, #5726). &lt;strong&gt;Before:&lt;/strong&gt; when the protected mission-branch mint refused (uncommitted changes in the checkout, a target branch with no commit, or the mission branch already existing), the Mission directory stayed behind without &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, and the retry after you fixed the cause was refused &lt;code dir=&quot;auto&quot;&gt;MISSION_ALREADY_EXISTS&lt;/code&gt; until you deleted that directory by hand. Re-running create (or &lt;code dir=&quot;auto&quot;&gt;orchestrator-api specify&lt;/code&gt;) for a name whose Mission was just created gave &lt;code dir=&quot;auto&quot;&gt;MISSION_ALREADY_EXISTS&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;MISSION_CREATE_FAILED&lt;/code&gt; depending on timing. &lt;strong&gt;After:&lt;/strong&gt; a mint refusal removes the directory it wrote, so the retry succeeds; and while the earlier Mission’s minted mission branch exists, a re-run against the same protected target is refused &lt;code dir=&quot;auto&quot;&gt;MISSION_ALREADY_EXISTS&lt;/code&gt; every time. A re-run made on the earlier Mission’s branch, without a protected target, is still allowed as before.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A rolled-back &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer leaves the coordination worktree’s status files behind its own HEAD&lt;/strong&gt; (#5638). &lt;strong&gt;Before:&lt;/strong&gt; when the rollback could not restore the coordination branch (for example another actor had committed on it), the worktree kept the pre-&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; status bytes while the branch kept the committed &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, so every later status change refused with &lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_DIVERGED&lt;/code&gt; until the operator repaired the worktree by hand. &lt;strong&gt;After:&lt;/strong&gt; the rollback brings that checkout back to the coordination tip it leaves in place, discarding only toolchain status residue; any other change there is kept and the rollback report says the checkout was left as found. The committed &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; stays recorded by the reconcile marker, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination --fix --mission &amp;#x3C;slug&gt;&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; still reverts it. The guard stays as the backstop.&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; no longer wedges on the ordinary dependency plan shape — it dispatches the review of a &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; work package that a planned one depends on&lt;/strong&gt; (#5669, #5310). &lt;strong&gt;Before:&lt;/strong&gt; with WP01 in &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; and WP02 (&lt;code dir=&quot;auto&quot;&gt;dependencies: [WP01]&lt;/code&gt;) &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; and dependency-walled, every &lt;code dir=&quot;auto&quot;&gt;spec-kitty next --result success&lt;/code&gt; returned &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;dependencies_not_satisfied&lt;/code&gt; (exit 1) and query mode agreed — the loop could never dispatch WP01’s review, the only work that unblocks WP02 — and on &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; the manual approval was itself refused because &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; left &lt;code dir=&quot;auto&quot;&gt;mission-events.jsonl&lt;/code&gt; uncommitted. &lt;strong&gt;After:&lt;/strong&gt; the finalized-board router gates its &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; arm on real claimability, so a walled planned WP falls through to the pending review (dispatch and query agree); first-contact &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; advance now consults the finalized board like query mode (#5310); and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;mission-events.jsonl&lt;/code&gt; write is a scoped review-handoff survivor, so &lt;code dir=&quot;auto&quot;&gt;move-task --to approved&lt;/code&gt; is no longer refused over it. The #4860 guard and the global churn owner are untouched.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A built-in promotion no longer turns your &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine&lt;/code&gt; red when an org pack replaces that built-in&lt;/strong&gt; (#5767). &lt;strong&gt;Before:&lt;/strong&gt; only your hand-copied &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/replaceable-builtins.yaml&lt;/code&gt; could sanction an override, so each upstream promotion left stale copies with exit 1. &lt;strong&gt;After:&lt;/strong&gt; a pack lists the built-ins it replaces in a pack-root &lt;code dir=&quot;auto&quot;&gt;replaceable-builtins.yaml&lt;/code&gt;, which &lt;code dir=&quot;auto&quot;&gt;doctor doctrine&lt;/code&gt; reads for that pack’s own overrides, shows per source, and can revoke with &lt;code dir=&quot;auto&quot;&gt;revoked_pack_sanctions&lt;/code&gt;. &lt;strong&gt;Pack authors:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;git mv templates/setup/replaceable-builtins.yaml replaceable-builtins.yaml&lt;/code&gt; (to the pack root, or its &lt;code dir=&quot;auto&quot;&gt;subdir&lt;/code&gt;). &lt;strong&gt;Behavior change:&lt;/strong&gt; with an org pack configured, a malformed consumer allowlist or a &lt;code dir=&quot;auto&quot;&gt;revoked_pack_sanctions&lt;/code&gt; entry naming an unconfigured pack now makes &lt;code dir=&quot;auto&quot;&gt;doctor doctrine&lt;/code&gt; unhealthy.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A crafted branch or ref name can no longer be read as a git option by spec-kitty’s internal git calls&lt;/strong&gt; (#5775). &lt;strong&gt;Before:&lt;/strong&gt; a ref starting with &lt;code dir=&quot;auto&quot;&gt;-&lt;/code&gt; was read as an option; in the one reachable case, a lane base ref of &lt;code dir=&quot;auto&quot;&gt;--local-env-vars&lt;/code&gt; made &lt;code dir=&quot;auto&quot;&gt;git rev-parse&lt;/code&gt; print git environment-variable names at exit 0. &lt;strong&gt;After:&lt;/strong&gt; those calls pass &lt;code dir=&quot;auto&quot;&gt;--end-of-options&lt;/code&gt; (and &lt;code dir=&quot;auto&quot;&gt;rev-parse --verify&lt;/code&gt;), so such a value is only ever an unresolvable revision; legitimate refs behave as before. This closes the SonarCloud S6350 findings. A separate S2083 path-traversal finding on skill file reads is a documented false positive (the read is already confined to the skill directory) and is now pinned by a regression test.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upgrading while a Mission has live lanes no longer makes &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;, review and implement refuse on &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;&lt;/strong&gt; (#5457). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; committed its own copy of that file (and, on 4.0.0rc5 and later, an identical &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; line) on every lane and coordination branch, so &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refused with &lt;code dir=&quot;auto&quot;&gt;Lane lane-b is stale&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;TARGET_BRANCH_CONTENT_CONFLICT&lt;/code&gt;, and review start and implement resume failed with &lt;code dir=&quot;auto&quot;&gt;LANE_AUTO_REBASE_FAILED&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; upgrade writes project-wide state once, in the repository root checkout, and skips Mission, lane and coordination worktrees. An affected Mission recovers on its next &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, review or implement with no manual edit (&lt;a href=&quot;/operations/upgrade-with-live-lanes-recovery/&quot;&gt;recovery guide&lt;/a&gt;); a real overlap on a file a work package edits still stops &lt;code dir=&quot;auto&quot;&gt;consolidate&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 consolidate&lt;/code&gt; no longer lands commits made after a work package was approved, or prints “Reconciliation verified” over them&lt;/strong&gt; (#5668). &lt;strong&gt;Before:&lt;/strong&gt; such a commit landed with exit 0 and the verified banner, under both strategies. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuses before any branch moves with &lt;code dir=&quot;auto&quot;&gt;LANE_MOVED_AFTER_APPROVAL&lt;/code&gt;, names the commit and work package, and prints the &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; command that sends it back for review; the check repeats before the run finishes and rolls back on failure. &lt;code dir=&quot;auto&quot;&gt;APPROVAL_STAMP_MISSING&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;APPROVAL_STAMP_NOT_ON_LANE&lt;/code&gt; cover an approval with no recorded lane head and a rewritten lane; &lt;code dir=&quot;auto&quot;&gt;--attest-approved-reviewed&lt;/code&gt; bounds the first. &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; reports the code as &lt;code dir=&quot;auto&quot;&gt;data.preflight_error_code&lt;/code&gt; (contract 1.10.0). Open cases: ADR &lt;a href=&quot;/adr/4.x/2026-10-04-5-approval-stamp-bounds-the-approved-claim/&quot;&gt;2026-10-04-5&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--attest-canceled-superseded&lt;/code&gt; no longer approves a commit made after a work package was approved, and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; names every refusal at once&lt;/strong&gt; (#5720). &lt;strong&gt;Before:&lt;/strong&gt; on a lane mixing an approved and a canceled work package, such a commit was refused, then landed with exit 0 once the canceled work package was attested, and each refusal appeared only after you fixed the one before. &lt;strong&gt;After:&lt;/strong&gt; the commit stays refused with &lt;code dir=&quot;auto&quot;&gt;LANE_MOVED_AFTER_APPROVAL&lt;/code&gt; until the approved work package is approved again, since the attestation says the canceled work is absent, not that new content was reviewed. The canceled work package’s own commits never cover it either, even if reverted (a forced move into &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; is #5721). The first message now lists every refusal, the approval one after &lt;code dir=&quot;auto&quot;&gt;This Mission also has:&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; adds &lt;code dir=&quot;auto&quot;&gt;data.preflight_error_codes&lt;/code&gt;. ADR &lt;a href=&quot;/adr/4.x/2026-10-04-5-approval-stamp-bounds-the-approved-claim/&quot;&gt;2026-10-04-5&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The default (squash) &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer refuses a coordination Mission whose plan produced &lt;code dir=&quot;auto&quot;&gt;quickstart.md&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt;&lt;/strong&gt; (#5552). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; stopped with “projected coordination bookkeeping content did not land on the target” although the content was identical; the workarounds were &lt;code dir=&quot;auto&quot;&gt;--strategy merge&lt;/code&gt; or committing a copy on the coordination branch. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;quickstart.md&lt;/code&gt; and everything under &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; count as planning artifacts, like &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt;, and go to your target branch, never through the coordination branch. If both the Mission branch and your target branch changed one, the squash follows the target-newer rule of the other plan artifacts (the later commit wins overlapping lines; edits to different lines are both kept) instead of stopping. A binary file under &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; changed on both sides is still refused.&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 merge&lt;/code&gt; works again&lt;/strong&gt; (#5650, #3457). &lt;strong&gt;Before:&lt;/strong&gt; it exited 1 on every run with &lt;code dir=&quot;auto&quot;&gt;{&quot;error&quot;: &quot;&apos;OptionInfo&apos; object has no attribute &apos;strip&apos;&quot;, &quot;success&quot;: false}&lt;/code&gt; before it looked at the Mission, because it called the consolidate command with only some of its options and the rest arrived as unset placeholders. &lt;strong&gt;After:&lt;/strong&gt; it passes every option with its real default and consolidates the Mission as &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; does.&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 action implement&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission now guards the write checkout and records the claim base, as &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; does&lt;/strong&gt; (#5459). &lt;strong&gt;Before:&lt;/strong&gt; it skipped both, so &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; refused every WP with &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;no recorded claim base&gt;&lt;/code&gt; until &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;, and a second WP could be claimed into a busy or dirty checkout with exit 0. &lt;strong&gt;After:&lt;/strong&gt; it refuses with &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_WRONG_BRANCH&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_OCCUPIED&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_DIRTY&lt;/code&gt; before any status write; resuming the same WP stays allowed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; WP of a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission no longer blocks claims on a branch that Mission does not write to&lt;/strong&gt; (#5550). &lt;strong&gt;Before:&lt;/strong&gt; if the Mission reached your branch without &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; (for example through a squash-merged PR) while a WP was still &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; refused every &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; claim with &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_OCCUPIED&lt;/code&gt; and no command to clear it. &lt;strong&gt;After:&lt;/strong&gt; a WP blocks the checkout only when its Mission writes to the branch the checkout is on (the Mission branch in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, otherwise its target branch); a Mission whose write branch cannot be determined (for example a detached HEAD) still blocks. The refusal now names the branch and the command that frees it: &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task &amp;#x3C;WP&gt; --to blocked --mission &amp;#x3C;mission&gt; --note &quot;&amp;#x3C;reason&gt;&quot;&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;--to canceled&lt;/code&gt; if the work is abandoned.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission now commit the status files they write&lt;/strong&gt; (#5655). &lt;strong&gt;Before:&lt;/strong&gt; subtask-completion and implementer-identity annotations were written to &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; but not committed, so the checkout stayed dirty and a later &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; refused. &lt;strong&gt;After:&lt;/strong&gt; they commit on the Mission’s write branch, like lane transitions; &lt;code dir=&quot;auto&quot;&gt;mark-status --no-auto-commit&lt;/code&gt; still leaves them uncommitted. A Mission recorded directly on a protected branch keeps the old uncommitted write and now logs a warning saying so.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A reviewer’s lock file no longer blocks the next work package on a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; Mission&lt;/strong&gt; (#5659, #5459). &lt;strong&gt;Before:&lt;/strong&gt; while one WP was in review, &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; refused to claim another with &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_DIRTY ... uncommitted changes: .spec-kitty/&lt;/code&gt;, telling you to commit or stash the tool’s own &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/review-lock.json&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the lock file does not count as a dirty checkout, for &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt;; your own uncommitted edits still refuse.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty spec-commit&lt;/code&gt; keep every &lt;code dir=&quot;auto&quot;&gt;-m&lt;/code&gt;&lt;/strong&gt; (#5647). &lt;strong&gt;Before:&lt;/strong&gt; a repeated &lt;code dir=&quot;auto&quot;&gt;-m&lt;/code&gt; kept only the last value, so &lt;code dir=&quot;auto&quot;&gt;-m &quot;subject&quot; -m &quot;Co-Authored-By: ...&quot;&lt;/code&gt; committed only the trailer, with exit 0. &lt;strong&gt;After:&lt;/strong&gt; repeated &lt;code dir=&quot;auto&quot;&gt;-m&lt;/code&gt; values are joined with a blank line, as &lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt; does; an all-empty message is refused.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The CI gate-mechanics reference names &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent acceptance-verdict&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt;&lt;/strong&gt; (#5648). &lt;strong&gt;Before:&lt;/strong&gt; it said the matrix had no CLI and told operators to hand-edit it. &lt;strong&gt;After:&lt;/strong&gt; it points to the supported writer and its negative-invariant mode.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer lands a canceled work package’s code through a lane that depends on it&lt;/strong&gt; (#5569, regression of #4977). &lt;strong&gt;Before:&lt;/strong&gt; if you canceled a rejected WP that another WP depended on, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; printed “Skipping lane-a (all WPs canceled …)”, yet landed the canceled code through the dependent lane, deleted the canceled lane and exited 0, under both strategies. &lt;strong&gt;After:&lt;/strong&gt; while that code is live on the dependent lane, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuses with a non-zero exit, names the canceled WP and leaves the target unchanged; it says &lt;code dir=&quot;auto&quot;&gt;--attest-canceled-superseded&lt;/code&gt; cannot override this and to revert the canceled lane’s commits on the dependent lane before re-running. A canceled lane no other lane depends on is still skipped. See #5613 below for the stable code, the fully superseded case and the one refusal an attestation lifts.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt; no longer drops an approved lane after an interrupted run&lt;/strong&gt; (#5571, regression of #4982). &lt;strong&gt;Before:&lt;/strong&gt; if &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; was killed, or hit a busy &lt;code dir=&quot;auto&quot;&gt;index.lock&lt;/code&gt;, after advancing the mission branch but before refreshing the coordination worktree, &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; refused with &lt;code dir=&quot;auto&quot;&gt;MERGE_UNSAFE_WORKTREE_DIRTY&lt;/code&gt; and advised “Commit, stash, or revert”. Committing recorded a revert of that lane, and the next resume marked every WP &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; and exited 0 without that WP’s code. &lt;strong&gt;After:&lt;/strong&gt; when the coordination worktree only lags its own HEAD, &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; refreshes it in place and finishes with every approved lane’s code on the target (mission and lane worktrees: see the #5613 entry below). If the worktree also holds your own edits, &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; refuses and tells you not to stage or record the listed changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer destroys a status change committed while it tears down the coordination branch&lt;/strong&gt; (#5570, regression of #4981). &lt;strong&gt;Before:&lt;/strong&gt; teardown checked the coordination branch once and later force-deleted it, so a status change committed in between (for example a reviewer reopening a WP) was lost and both commands exited 0. &lt;strong&gt;After:&lt;/strong&gt; the branch is deleted only if it still points at the checked commit. If it moved, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; keeps the branch and your change, exits 75 with &lt;code dir=&quot;auto&quot;&gt;COORD_MOVED_AFTER_LANDING&lt;/code&gt; (#5613) and tells you to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt;, which carries the late commit onto your target branch in a bookkeeping commit, removes the coordination marker and finishes. If another commit lands in that second window, it refuses again and keeps the branch.&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 coordination --fix&lt;/code&gt; no longer reverts a reviewer’s later reopen while printing “Healed”&lt;/strong&gt; (#5572, the doctor half of #4973). &lt;strong&gt;Before:&lt;/strong&gt; the repair reverted every status-log commit made after the failed consolidation, including a reopen recorded afterwards. &lt;strong&gt;After:&lt;/strong&gt; the repair marker records exactly which commits the failed consolidation wrote, and &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; (and the same repair inside &lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt;) reverts only those. If the coordination branch also holds other status changes, or the marker recorded no strand commits (written by an older release, or unreadable), it changes nothing, does not print “Healed”, keeps the marker and asks you to reconcile manually; &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt; then exits non-zero, while &lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; warns and continues (the stranded commit does not ship, because the coordination branch is torn down).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer finishes when an approved work package’s code is missing from the target&lt;/strong&gt; (#5613, follow-up to #5571). &lt;strong&gt;Before:&lt;/strong&gt; if you committed the staged deletions that a lagging coordination or mission worktree showed after an interrupted run and then resumed, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; could mark every WP &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; and exit 0 without that WP’s code. &lt;strong&gt;After:&lt;/strong&gt; it fails with &lt;code dir=&quot;auto&quot;&gt;APPROVED_CONTENT_MISSING&lt;/code&gt;, names the approved WP, its lane and the path, and restores every branch it moved, under the default squash strategy and &lt;code dir=&quot;auto&quot;&gt;--strategy merge&lt;/code&gt;. The check covers a lane’s own net change to a path that the target left alone since the lane was cut and no later approved lane replaced; a path the target also changed is not judged by it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A status change no longer drops events that the coordination branch has already committed&lt;/strong&gt; (#5613, follow-up to #5572). &lt;strong&gt;Before:&lt;/strong&gt; after a rolled-back consolidation the coordination worktree’s &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; could hold fewer events than its branch HEAD, and the next status change committed that shorter log, silently losing the committed events. &lt;strong&gt;After:&lt;/strong&gt; the write refuses with &lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_DIVERGED&lt;/code&gt; before writing anything, names the missing events and gives two remedies: &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination --fix --mission &amp;#x3C;slug&gt;&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume --mission &amp;#x3C;slug&gt;&lt;/code&gt;, which also completes the consolidation) reverts the stranded &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, while &lt;code dir=&quot;auto&quot;&gt;git checkout HEAD --&lt;/code&gt; on the two status files keeps the committed events. Always pass &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;; without it &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt; acts on every Mission. An unreadable, malformed or duplicate-id committed log refuses with &lt;code dir=&quot;auto&quot;&gt;COORD_STATUS_SURFACE_UNREADABLE&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 consolidate --resume&lt;/code&gt; now recovers a mission worktree or lane worktree that only lags its own HEAD&lt;/strong&gt; (#5613, follow-up to #5571). &lt;strong&gt;Before:&lt;/strong&gt; only your repository root checkout and the coordination worktree were refreshed in place; a lagging mission or lane worktree stopped the resume with advice to commit, which reverts the integrated lanes. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; refreshes each of them when the lag is proven against the branch tip recorded before the run moved anything. A dirty mission-branch worktree is refused only when a lane remains to be consolidated or the worktree lags, and a leftover &lt;code dir=&quot;auto&quot;&gt;index.lock&lt;/code&gt; no longer gets “Commit” advice. A worktree that lags and also holds your edit gets steps instead: save the edit with &lt;code dir=&quot;auto&quot;&gt;git diff --binary&lt;/code&gt; to a patch, &lt;code dir=&quot;auto&quot;&gt;git reset --hard HEAD&lt;/code&gt;, resume, &lt;code dir=&quot;auto&quot;&gt;git apply&lt;/code&gt;. Your repository root checkout in that state still gets “Commit, stash, or revert”.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer refuses a canceled dependency whose code a later approved WP fully replaced&lt;/strong&gt; (#5613, follow-up to #5569). &lt;strong&gt;Before:&lt;/strong&gt; under &lt;code dir=&quot;auto&quot;&gt;--strategy merge&lt;/code&gt;, any commit of a canceled WP that a dependent lane carried made &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuse, even when the approved WP had rewritten every file that commit touched. &lt;strong&gt;After:&lt;/strong&gt; commits that every carrying lane fully superseded stay part of the approved work and consolidation proceeds. Canceled code still live on the target fails with &lt;code dir=&quot;auto&quot;&gt;CANCELED_REACHABLE_VIA_DEPENDENCY&lt;/code&gt;, naming the canceled WP, both lanes and the path; no attestation lifts it. A canceled dependency WP with no &lt;code dir=&quot;auto&quot;&gt;lane_head&lt;/code&gt; stamp (for example in an older Mission) is refused before any branch moves, and &lt;code dir=&quot;auto&quot;&gt;--attest-canceled-superseded &amp;#x3C;WP&gt; --attest-reason &quot;...&quot;&lt;/code&gt; lifts that refusal only, for each WP you attest.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; reports a branch that moved after landing with its own code and exit code&lt;/strong&gt; (#5613, follow-up to #5570). &lt;strong&gt;Before:&lt;/strong&gt; when the coordination branch (or the mission branch of a Mission without coordination topology) moved after the landing and was kept, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; exited 1 with prose only. &lt;strong&gt;After:&lt;/strong&gt; the message ends with &lt;code dir=&quot;auto&quot;&gt;Error code: COORD_MOVED_AFTER_LANDING.&lt;/code&gt; and the exit code is 75: nothing was lost and the cleanup can be finished afterwards. &lt;code dir=&quot;auto&quot;&gt;spec-kitty orchestrator-api consolidate-mission&lt;/code&gt; keeps its &lt;code dir=&quot;auto&quot;&gt;PREFLIGHT_FAILED&lt;/code&gt; envelope and adds the code as &lt;code dir=&quot;auto&quot;&gt;data.teardown_error_code&lt;/code&gt; (orchestrator API contract 1.9.0). The same race caught earlier, before teardown starts, keeps &lt;code dir=&quot;auto&quot;&gt;PROJECTION_TEARDOWN_ABORTED&lt;/code&gt; and exit 1; &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; now prints it as &lt;code dir=&quot;auto&quot;&gt;Error: coordination teardown refused: PROJECTION_TEARDOWN_ABORTED: ...&lt;/code&gt; instead of a raw traceback (#5637).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Re-running &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; no longer moves a started work package to another lane&lt;/strong&gt; (#5573, after #3311 and #4945). &lt;strong&gt;Before:&lt;/strong&gt; an amendment that made a planned WP overlap a started one could re-letter the started WP’s lane, and the next &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; failed with &lt;code dir=&quot;auto&quot;&gt;LANE_WORK_TIP_UNKNOWN&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; a started WP keeps its recorded lane and the planned WP joins it; a retired started WP’s lane id is not reused while its branch still has recorded work. If a re-finalize cannot keep started work in place, it refuses with &lt;code dir=&quot;auto&quot;&gt;LANE_MEMBERSHIP_FROZEN&lt;/code&gt; and a non-destructive remedy before writing a status event, &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; or a commit. The &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt; is &lt;code dir=&quot;auto&quot;&gt;started_lanes_collapsed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;started_wp_removed&lt;/code&gt; (cancel the WP instead), &lt;code dir=&quot;auto&quot;&gt;started_wp_kind_changed&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;status_unreadable&lt;/code&gt;. See ADR &lt;a href=&quot;/adr/4.x/2026-10-04-2-started-work-package-lane-membership-is-frozen/&quot;&gt;2026-10-04-2&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks --validate-only&lt;/code&gt; now checks lanes the way a real run does&lt;/strong&gt; (#5573). &lt;strong&gt;Before:&lt;/strong&gt; it did not read &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, and its lane preview minted lane ids by position. &lt;strong&gt;After:&lt;/strong&gt; it reads &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, so a corrupt manifest fails it as it fails a real run, and the preview shows the lane ids a real run writes. A successful run’s &lt;code dir=&quot;auto&quot;&gt;collapse_report&lt;/code&gt; can carry the new rule value &lt;code dir=&quot;auto&quot;&gt;frozen_lane_membership&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 upgrade --yes&lt;/code&gt; no longer stops on command skills that already match the current release&lt;/strong&gt; (#5574). &lt;strong&gt;Before:&lt;/strong&gt; a command skill under &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; whose content was identical to what this release installs was still reported as drifted when an older release had recorded a different hash, so an unattended upgrade exited 1 and pointed you at &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor tool-surfaces&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; content that matches the current release counts as up to date, the recorded hash is refreshed, and the upgrade finishes. &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor tool-surfaces&lt;/code&gt; also reports such a file as present. A command skill you edited yourself is still reported and left untouched.&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 tool-surfaces --fix&lt;/code&gt; now restores a command skill you edited&lt;/strong&gt; (#5575). &lt;strong&gt;Before:&lt;/strong&gt; the repair the drift message sent you to reported success but kept your edited &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty.&amp;#x3C;command&gt;/SKILL.md&lt;/code&gt;, so the drift never cleared. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; replaces the edited file with the current release’s version, as it already did for agent profiles, and the drift finding names that command. An unattended &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --yes&lt;/code&gt; still never overwrites your edit; it reports it and exits non-zero.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; that exits non-zero now always says why, and never prints a success line&lt;/strong&gt; (#4925, #4893). &lt;strong&gt;Before:&lt;/strong&gt; on an up-to-date project with a hand-edited managed file, &lt;code dir=&quot;auto&quot;&gt;upgrade --yes&lt;/code&gt; printed only &lt;code dir=&quot;auto&quot;&gt;Project is already up to date!&lt;/code&gt; and exited 1; an unapplied repair was reported as &lt;code dir=&quot;auto&quot;&gt;drift in 0 file(s)&lt;/code&gt;; a broken &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; pointer ended in a traceback. &lt;strong&gt;After:&lt;/strong&gt; it names each file it kept (&lt;code dir=&quot;auto&quot;&gt;Not updated, your local edit was kept: &amp;#x3C;path&gt;&lt;/code&gt;), says how to take the current version or keep your edit, ends on &lt;code dir=&quot;auto&quot;&gt;Upgrade finished, but N managed file(s) with local edits were not updated.&lt;/code&gt; and still exits 1. A broken charter pack config is reported as an error with its remedy, and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;outcome&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;failure_reasons&lt;/code&gt;. Whether kept edits should exit non-zero at all is open in #5745; #4893 stays open for its ordering defect. See ADR &lt;a href=&quot;/adr/4.x/2026-10-04-3-upgrade-reports-one-outcome/&quot;&gt;2026-10-04-3&lt;/a&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 implement&lt;/code&gt; no longer treats line-ending-only differences in planning files as uncommitted changes&lt;/strong&gt; (#5576). &lt;strong&gt;Before:&lt;/strong&gt; on a checkout where Git converts line endings (for example Windows with &lt;code dir=&quot;auto&quot;&gt;core.autocrlf&lt;/code&gt;, or a &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;eol=crlf&lt;/code&gt; rule), planning files that &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; reported as clean were seen as changed, so &lt;code dir=&quot;auto&quot;&gt;implement --no-auto-commit&lt;/code&gt; asked you to commit them and auto-commit could attempt an empty commit. &lt;strong&gt;After:&lt;/strong&gt; the check compares what Git would store, so a clean checkout starts implementation without a commit. A planning file whose text you actually changed is still listed, whatever its line endings.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A failed &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission finalize-tasks&lt;/code&gt; no longer leaves status commits behind&lt;/strong&gt; (#5641). &lt;strong&gt;Before:&lt;/strong&gt; when the run failed at its final commit (or a later gate refused), it restored the Mission files but kept the &lt;code dir=&quot;auto&quot;&gt;status transition&lt;/code&gt; commits that seed each work package, so the checkout was left with changes against its own HEAD and a second run seeded every work package again. &lt;strong&gt;After:&lt;/strong&gt; on every topology the run puts the branch, index and status files back, and a second run seeds each work package once. A commit the run did not make is never undone: the branch is kept and a &lt;code dir=&quot;auto&quot;&gt;status_commits_not_undone&lt;/code&gt; warning (also in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output) names the commits left behind. A detached HEAD and a coordination worktree the run itself creates are not restored.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The Windows install guide no longer tells you to get Python from the Microsoft Store&lt;/strong&gt; (#5596). &lt;strong&gt;Before:&lt;/strong&gt; it offered python.org or the Store, and described only the per-version installer that python.org deprecated in Python 3.14. &lt;strong&gt;After:&lt;/strong&gt; it requires Python 3.11–3.13 from python.org, covers python.org’s Python install manager (&lt;code dir=&quot;auto&quot;&gt;py install 3.13&lt;/code&gt;), and shows how to spot and replace a Store Python or the &lt;code dir=&quot;auto&quot;&gt;python.exe&lt;/code&gt; Store stub.&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 config sync --create-missing&lt;/code&gt; restores a missing Mistral Vibe pointer again&lt;/strong&gt; (#5612). &lt;strong&gt;Before:&lt;/strong&gt; when &lt;code dir=&quot;auto&quot;&gt;.vibe/config.toml&lt;/code&gt; was missing but the vibe command skills were installed, the recovery command that &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; recommends (&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config sync --create-missing --keep-orphaned&lt;/code&gt;) printed “No changes needed” and left the pointer missing, so Mistral Vibe could not find the skills. &lt;strong&gt;After:&lt;/strong&gt; the command restores the pointer and reports the change; a repeat run reports no change. It never rewrites the command-skill manifest. If an existing &lt;code dir=&quot;auto&quot;&gt;.vibe/config.toml&lt;/code&gt; cannot be parsed, the command leaves the file as is, prints an error and exits 1.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; lands a coordination Mission whose primary directory has no &lt;code dir=&quot;auto&quot;&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; suffix onto a protected branch&lt;/strong&gt; (#5651, #5611). &lt;strong&gt;Before:&lt;/strong&gt; it stopped with &lt;code dir=&quot;auto&quot;&gt;MERGE_UNSAFE_WORKTREE_DIRTY&lt;/code&gt; and listed the Mission’s own &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; as untracked files in the coordination worktree. &lt;strong&gt;After:&lt;/strong&gt; it lands the Mission under both &lt;code dir=&quot;auto&quot;&gt;--strategy&lt;/code&gt; values, and the target branch holds one Mission directory, &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt;, with the complete event log. The composed &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; directory’s coordination files (status files, traces, matrices, decision log, review cycles) are removed in the bookkeeping commit, each only after it is proven redundant against the primary directory; nothing else under the composed name is touched. Missions created by &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission create&lt;/code&gt; end in their &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; and were never affected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A failed reconciliation check in &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer discards a commit someone else added to the target&lt;/strong&gt; (#5666). &lt;strong&gt;Before:&lt;/strong&gt; when the reconciliation check failed or refused after the landing, the target branch was reset to its pre-consolidation commit with a compare-and-swap against whatever tip it had then, so a commit that a teammate or another Mission landed on top of the landing was lost, and the report said the target was unchanged. &lt;strong&gt;After:&lt;/strong&gt; the check moves no branch itself; the run’s single rollback restores the target only while it is still at the commit this run recorded. A commit added on top is kept, the report names the target &lt;code dir=&quot;auto&quot;&gt;NOT restored ... moved by another actor&lt;/code&gt;, and the run exits non-zero.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt; no longer reports a branch as restored when an interrupted run left it moved without a record&lt;/strong&gt; (#5686, and the deadlock part of #5687). &lt;strong&gt;Before:&lt;/strong&gt; if &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; was killed after moving the target but before recording the move, &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; printed “Branches restored to their pre-consolidation commits”, exited 0 and deleted the record, while the target kept an unverified landing; a branch that could not be restored made every &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; refuse. &lt;strong&gt;After:&lt;/strong&gt; the run saves each move before making it, so &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; restores a move the run provably made. A move it cannot explain is never adopted: a re-run or &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; refuses with &lt;code dir=&quot;auto&quot;&gt;UNEXPLAINED_BRANCH_MOVE&lt;/code&gt; before moving anything, and &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; reports the branch &lt;code dir=&quot;auto&quot;&gt;NOT restored&lt;/code&gt;; to keep it and finish, use &lt;code dir=&quot;auto&quot;&gt;--abort --release-branch&lt;/code&gt; (see Added). A commit landing on the target during reconciliation now makes &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; refuse (exit 1) and keep it. See &lt;a href=&quot;/guides/how-to/recovery/troubleshoot-merge/#a-branch-moved-without-a-record&quot;&gt;troubleshooting&lt;/a&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 consolidate --abort --release-branch&lt;/code&gt; no longer lets a released branch finish the abort while an approved work package’s code is missing from the target&lt;/strong&gt; (#5788). &lt;strong&gt;Before:&lt;/strong&gt; the abort could exit 0 with that code silently dropped. &lt;strong&gt;After:&lt;/strong&gt; it stops with &lt;code dir=&quot;auto&quot;&gt;APPROVED_CONTENT_MISSING&lt;/code&gt; and names the work package and the path.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; refuses an auto-commit claim run off the claim commit’s branch before it changes anything&lt;/strong&gt; (#5738). &lt;strong&gt;Before:&lt;/strong&gt; with auto-commit on, a claim run from a checkout on another branch (or a detached HEAD) created the lane worktree and recorded the claim, then failed on the claim commit with exit 1 and no error, leaving both behind. &lt;strong&gt;After:&lt;/strong&gt; the claim is refused first, with an &lt;code dir=&quot;auto&quot;&gt;Error:&lt;/code&gt; line naming both branches and the &lt;code dir=&quot;auto&quot;&gt;git checkout&lt;/code&gt; command (&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; gets the error envelope); when the needed branch is protected, it also says to rerun with &lt;code dir=&quot;auto&quot;&gt;--no-auto-commit&lt;/code&gt;. Resuming an &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; WP and &lt;code dir=&quot;auto&quot;&gt;--no-auto-commit&lt;/code&gt; claims are not refused. An error no step reported, such as &lt;code dir=&quot;auto&quot;&gt;SafeCommitPathPolicyError&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;PlacementResolutionRequired&lt;/code&gt; from the claim commit, now prints an &lt;code dir=&quot;auto&quot;&gt;Error:&lt;/code&gt; line instead of a silent exit 1.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Consecutive &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement --no-auto-commit&lt;/code&gt; claims no longer need a commit in between&lt;/strong&gt; (#3471). &lt;strong&gt;Before:&lt;/strong&gt; the next claim was refused with “Planning artifacts not committed”, listing the previous claim’s own writes (&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, the WP file), and “changes staged only” was untrue: nothing was staged. &lt;strong&gt;After:&lt;/strong&gt; the planning check ignores exactly those claim writes, so the next claim goes through; any other uncommitted planning edit, hand-edited &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; or other appended status event still refuses. The claim now stages its own changes with &lt;code dir=&quot;auto&quot;&gt;git add --force&lt;/code&gt;, so “changes staged only” is true; a failed staging warns and says “changes left unstaged”.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-2&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The changelog style guard now refuses leftover merge-conflict marker lines (&lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;&amp;#x3C;&amp;#x3C;&amp;#x3C;&amp;#x3C;&amp;#x3C;&amp;#x3C;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;|||||||&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&gt;&lt;/code&gt;, and a &lt;code dir=&quot;auto&quot;&gt;=======&lt;/code&gt; inside an open conflict) in the Unreleased section, as rule &lt;code dir=&quot;auto&quot;&gt;conflict-marker&lt;/code&gt;, so a botched rebase can no longer leave diff3 markers in the changelog as it did in #5906 (#5910).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Every merge, revert and squash conclusion goes through one owner, and a gate keeps it that way&lt;/strong&gt; (#5443). Consolidation, auto-rebase, lane allocation and the coordination rollbacks conclude through it: it never skips hooks, never commits without a merge, revert, cherry-pick or squash in progress, and concludes a squash only in a fresh merge worktree whose index matches HEAD, so untracked files a hook writes never enter the squash commit. Restoring target-newer planning files no longer sweeps another staged file into the squash commit. A new architectural gate with an empty allowlist reports every sweeping, pathspec-less or hook-bypassing &lt;code dir=&quot;auto&quot;&gt;git&lt;/code&gt; call it can read from a literal argument list in &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; outside &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; and that owner; argument lists built across statements, shell strings and plumbing commits (&lt;code dir=&quot;auto&quot;&gt;commit-tree&lt;/code&gt;) are outside its reach.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The unused sweeping commit helpers are removed, for maintainers&lt;/strong&gt; (#5443). &lt;code dir=&quot;auto&quot;&gt;GitVCS.commit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;VCSProtocol.commit&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;git add -A&lt;/code&gt; when given no paths, then a pathspec-less commit) and &lt;code dir=&quot;auto&quot;&gt;specify_cli.core.git_ops.init_git_repo&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;git add .&lt;/code&gt;, then a pathspec-less commit) are gone, with the &lt;code dir=&quot;auto&quot;&gt;specify_cli.core&lt;/code&gt; re-export and its &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt; entry. They had no product callers; code that commits uses the path-scoped &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;tests (corpus-blocking)&lt;/code&gt; CI job’s timeout is 20 minutes, up from 10&lt;/strong&gt; (#5838): it passed all tests and was still canceled at the cap on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, because its runtime grows with the Mission corpus.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The artifact-kind single-authority gate covers every package under &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;, at any depth, with an empty allowlist&lt;/strong&gt; (#5538). It found seven hand-copied kind lists outside &lt;code dir=&quot;auto&quot;&gt;src/charter&lt;/code&gt; or inside function bodies; all now derive from &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;, which gains &lt;code dir=&quot;auto&quot;&gt;core&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;CORE_KIND_PLURALS&lt;/code&gt; for the eight original kinds several surfaces still cover. Two new derived gates stop a config key being written as a &lt;code dir=&quot;auto&quot;&gt;charter.offering.*&lt;/code&gt; module path and stop guidance naming a &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; command that the &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; group registers with the same handler (#4836).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-06-2&lt;/code&gt; records the charter offering / active charter model and activation presets&lt;/strong&gt; that bind the doctrine-pack rename (#3732): &lt;code dir=&quot;auto&quot;&gt;charter activate --pack &amp;#x3C;pack&gt; --preset &amp;#x3C;preset&gt;&lt;/code&gt;, presets as pack data, &lt;code dir=&quot;auto&quot;&gt;spk-charter-*&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;spk-practice-*&lt;/code&gt; skills, and a full cutover with no aliases. These are the target of the #3732 mission and are not implemented yet.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Maintainers get shared &lt;code dir=&quot;auto&quot;&gt;kitty-land-pr&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;kitty-issue-triage&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;kitty-mission-from-issue&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;kitty-report-debrief&lt;/code&gt; commands from the internal pack&lt;/strong&gt; (#5193). They are four thin pack skills in &lt;code dir=&quot;auto&quot;&gt;packs/internal/skills/&lt;/code&gt; (namespace &lt;code dir=&quot;auto&quot;&gt;kitty&lt;/code&gt;, in force through &lt;code dir=&quot;auto&quot;&gt;required_skills&lt;/code&gt;) that point at the &lt;code dir=&quot;auto&quot;&gt;landing-contributor-prs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;issue-triage-pass&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;issue-to-mission-delivery&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;executive-debrief-generation&lt;/code&gt; procedures, which now carry the rules the private copies used to restate. The debrief collector, renderer, template, logo and fonts moved from &lt;code dir=&quot;auto&quot;&gt;scripts/reporting/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;packs/internal/assets/debrief/&lt;/code&gt; as pack assets, with the debrief tests loading them from there. No consumer-visible change: the pack never ships to consumers.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; is now a thin command over ordered phase modules, for maintainers&lt;/strong&gt; (#5635). No operator-visible change from the decomposition itself (its two fixes are under Fixed, #5738 and #3471): refusals, exit codes, console and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output, commits and state files are unchanged. &lt;code dir=&quot;auto&quot;&gt;cli/commands/implement.py&lt;/code&gt; went from 2,304 to 438 lines and runs the phases in &lt;code dir=&quot;auto&quot;&gt;implement_phases.py&lt;/code&gt;; claim recording moved to &lt;code dir=&quot;auto&quot;&gt;implement_claim.py&lt;/code&gt;, the planning-artifact commit to &lt;code dir=&quot;auto&quot;&gt;implement_planning_commit.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--recover&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;implement_recover.py&lt;/code&gt;, and the CLI-free decisions (they return typed results or raise typed errors, and the command turns those into output and exit codes) behind the &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;coordination&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;workspace&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;core&lt;/code&gt; seams. The meta-derived planning-placement fallback in &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; is replaced by a seam-owned typed placement (&lt;code dir=&quot;auto&quot;&gt;coordination/planning_commit.py&lt;/code&gt;), with no operator-visible change (#5232). The #5673 fix is now a change to one function, &lt;code dir=&quot;auto&quot;&gt;implement_claim.claim_commit_paths&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The consolidation executor is now split into one module per phase&lt;/strong&gt; (#5650, #2026, #2600, #3457). &lt;code dir=&quot;auto&quot;&gt;consolidation/executor.py&lt;/code&gt; used to hold every phase of &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;; it now keeps the entry, the lock and the rollback door, and each phase has its own module. The Mission-number bake code moved from &lt;code dir=&quot;auto&quot;&gt;consolidation/ordering.py&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;consolidation/mission_number/bake.py&lt;/code&gt;, and code that calls the consolidate command directly passes a &lt;code dir=&quot;auto&quot;&gt;ConsolidateOptions&lt;/code&gt; object to &lt;code dir=&quot;auto&quot;&gt;run_consolidate&lt;/code&gt;. The behavior of &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The move-task transition gates now live in their own module&lt;/strong&gt; (#5661, #5629). The pre-review and transition gates moved out of &lt;code dir=&quot;auto&quot;&gt;cli/commands/agent/tasks_move_task.py&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;tasks_move_task_gates.py&lt;/code&gt;, the first slice of #5629; the command module went from 3,786 to about 2,730 lines. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task&lt;/code&gt; behaves as before, and every name stays importable from &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tasks_move_task&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; is now a facade plus seven phase modules&lt;/strong&gt; (#5679, #5627). &lt;code dir=&quot;auto&quot;&gt;cli/commands/agent/mission_finalize.py&lt;/code&gt; used to hold the whole command in one module of about 5,720 lines; it is now a facade of about 1,420 lines that keeps &lt;code dir=&quot;auto&quot;&gt;finalize_tasks&lt;/code&gt;, its context and the branch-setup phase, and seven sibling &lt;code dir=&quot;auto&quot;&gt;mission_finalize_*&lt;/code&gt; modules each hold one phase (seams, branch contract, validation, bootstrap, planning pin, lanes, commit). &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission finalize-tasks&lt;/code&gt; behaves as before, and every name stays importable from &lt;code dir=&quot;auto&quot;&gt;mission_finalize&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The move-task hop builders and executor now live in their own modules&lt;/strong&gt; (#5695, #5629, #5684). The hop builders and the code that emits the transitions, persists the work package file and releases the review lock or rolls back under the status lock moved out of &lt;code dir=&quot;auto&quot;&gt;cli/commands/agent/tasks_move_task.py&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;tasks_move_task_hops.py&lt;/code&gt; (369 lines) and &lt;code dir=&quot;auto&quot;&gt;tasks_move_task_executor.py&lt;/code&gt; (588 lines); the command module went from 2,734 to 1,886 lines. &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; now choose how a runtime annotation is written through one function, &lt;code dir=&quot;auto&quot;&gt;emit_runtime_annotation&lt;/code&gt;, instead of each repeating the choice. The one-shot capture harness for the gate parity fixtures is retired and its golden fixtures stay. The patch-target liveness check now covers every &lt;code dir=&quot;auto&quot;&gt;tasks_*&lt;/code&gt; module. No product behavior changes, and every name stays importable from &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tasks_move_task&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission creation is now a facade plus eleven sibling modules&lt;/strong&gt; (#5634). &lt;code dir=&quot;auto&quot;&gt;core/mission_creation.py&lt;/code&gt; used to hold all of mission creation in about 2,360 lines; it is now a facade of about 740 lines that keeps &lt;code dir=&quot;auto&quot;&gt;create_mission_core&lt;/code&gt;, its failure-atomic body and the orchestration. Ten sibling &lt;code dir=&quot;auto&quot;&gt;mission_creation_*&lt;/code&gt; modules each hold one step (errors, identity, roots, duplicates, protected mint, scaffold, meta, events, commit, rollback), and &lt;code dir=&quot;auto&quot;&gt;mission_creation_decisions&lt;/code&gt; holds the pure decision cores, which do no I/O. Tests pass a fixed &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; through a private input instead of patching the minting, and the patch sites on the module family went from 279 to 11. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission create&lt;/code&gt; behaves as before, and every name other modules import stays importable from &lt;code dir=&quot;auto&quot;&gt;mission_creation&lt;/code&gt;. Those re-exports are import points, not patch points: a test that patches a name on &lt;code dir=&quot;auto&quot;&gt;mission_creation&lt;/code&gt; intercepts a leaf’s call only for &lt;code dir=&quot;auto&quot;&gt;build_mission_created_payload&lt;/code&gt;; patch any other name on the leaf that calls it. See &lt;code dir=&quot;auto&quot;&gt;docs/api/mission-creation-internals.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Nightly test repairs for the Python 3.13 shard 3, &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; out-of-matrix and performance suites (#5418, #5258, #5419). No product behavior changes. The frozen &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; surface test lists the new &lt;code dir=&quot;auto&quot;&gt;doctor run-index&lt;/code&gt; subcommand, and three count tests follow the command registry after the dashboard removal; the handle-equivalence test runs its custom mission on a mission of that type; the hosted-endpoint sequencing tests apply only the two migrations they order; and the shared test source snapshot is readable when CI checks out a single commit. The owned-checkout wall-clock tests now use the same 2.5 s budget as the CLI start-up test. A later entry in this section replaces that budget with a runner-relative ratio (#5614).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Nightly test suites are green again after origin freshness landed&lt;/strong&gt; (#5912). Nightly test repairs for the Python 3.13 shards 3 and 5 and the &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; out-of-matrix and integration suites, after origin freshness landed (#5886, #5887, #5888, #5889). No product behavior changes. The doctrine git-source test recorder answers the &lt;code dir=&quot;auto&quot;&gt;core.sshCommand&lt;/code&gt; reads that &lt;code dir=&quot;auto&quot;&gt;no_prompt_env&lt;/code&gt; now makes, instead of letting them use up its scripted clone results. &lt;code dir=&quot;auto&quot;&gt;test_merge_cli_golden&lt;/code&gt; lists &lt;code dir=&quot;auto&quot;&gt;--origin-check&lt;/code&gt;. The accept harness stands in for the origin gate. The owned-checkout accept tests read stdout, the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; payload, rather than stdout and stderr mixed: the origin note goes to stderr.&lt;/li&gt;
&lt;li&gt;Nightly test repairs for the stress, integration and integration-slice suites (#5610, #5611, #5612). Beyond the Fixed entry above, no product behavior changes. The stress fixture now writes a Mission &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; that declares its coordination branch and uses an 8-character &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt;. Three integration tests follow the coordination single-home behavior (#5440). The nightly integration slice checks out full history for the Mission corpus recovery tests, the repository-root status guard self-test reads pytest’s summary lines when &lt;code dir=&quot;auto&quot;&gt;CI&lt;/code&gt; is set, and the &lt;code dir=&quot;auto&quot;&gt;implement --recover --json&lt;/code&gt; characterization runs on a materialized coordination worktree. The &lt;code dir=&quot;auto&quot;&gt;regression&lt;/code&gt;-marked reproduction pinned to #5651 now passes; see the Fixed entry (#5651) for the product fix.&lt;/li&gt;
&lt;li&gt;Two test repairs and one dead-code removal (#5693, #5654, #5186). No product behavior changes. The upgrade history-store test now denies the write at the filesystem call instead of with &lt;code dir=&quot;auto&quot;&gt;chmod&lt;/code&gt;, so it also fails for a root user when the error stops being swallowed; the &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; symlink-race test now exercises the writer that is actually used; &lt;code dir=&quot;auto&quot;&gt;TestOrdering&lt;/code&gt; in the provision-kitty-env migration tests registers the migrations it asserts on, so it passes when run alone. The unused &lt;code dir=&quot;auto&quot;&gt;GitignoreManager._atomic_write&lt;/code&gt; is removed.&lt;/li&gt;
&lt;li&gt;Regression-slice test cleanup (#5656, #5618, #5619, #5620, #5621, #5622). No product behavior changes. The per-PR &lt;code dir=&quot;auto&quot;&gt;regression&lt;/code&gt; test slice now holds only issue-pinned end-to-end guards of fixed bugs, which cuts it from 725 tests in 143 files to about 424 in 108 files. Slow end-to-end replays whose contract a cheaper seam test already holds are trimmed to one smoke test per behavior, and permission-denied tests now give the same verdict when the suite runs as root.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The runtime bridge’s compat-delegate layer is retired, for maintainers&lt;/strong&gt; (#2561, #2633). &lt;code dir=&quot;auto&quot;&gt;src/runtime/next/runtime_bridge.py&lt;/code&gt; no longer carries the 36 thin functions that forwarded to its six seam modules (&lt;code dir=&quot;auto&quot;&gt;runtime_bridge_identity&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_cores&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_engine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_retrospective&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_composition&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_io&lt;/code&gt;), and the seams no longer read those names back off the bridge; the bridge went from 4,082 to about 3,575 lines. Each name now lives only on its seam, and a test patches that seam. &lt;code dir=&quot;auto&quot;&gt;get_or_start_run&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;build_operational_context_for_claim&lt;/code&gt; stay importable from &lt;code dir=&quot;auto&quot;&gt;runtime_bridge&lt;/code&gt; as the seam’s own function objects for the CLI modules that use them; those two are import points, not patch points for the runtime package’s own calls. A new gate, &lt;code dir=&quot;auto&quot;&gt;tests/runtime/test_bridge_no_compat_delegates.py&lt;/code&gt;, fails if a forwarder or a lookup through the bridge comes back. No product behavior changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The runtime bridge’s read path and decision mapping have their own modules, for maintainers&lt;/strong&gt; (#2560). &lt;code dir=&quot;auto&quot;&gt;runtime_bridge.py&lt;/code&gt; now holds only the advance path of &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; (about 3,575 → 1,400 lines); query/answer mode moved to &lt;code dir=&quot;auto&quot;&gt;runtime_bridge_query&lt;/code&gt;, the shared decision mapping to &lt;code dir=&quot;auto&quot;&gt;runtime_bridge_decision_mapping&lt;/code&gt;, the decision-log wrapper to &lt;code dir=&quot;auto&quot;&gt;runtime_bridge_decision_log&lt;/code&gt; and the guard facts to &lt;code dir=&quot;auto&quot;&gt;runtime_bridge_guards&lt;/code&gt;, verbatim. No &lt;code dir=&quot;auto&quot;&gt;runtime_bridge_*&lt;/code&gt; module imports the bridge any more, and the public names (&lt;code dir=&quot;auto&quot;&gt;query_current_state&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;answer_decision_via_runtime&lt;/code&gt;, the two query exceptions, &lt;code dir=&quot;auto&quot;&gt;DecisionGitLogUnavailable&lt;/code&gt;) stay importable from it as the same objects. &lt;code dir=&quot;auto&quot;&gt;test_bridge_no_compat_delegates&lt;/code&gt; covers every moved name, and &lt;code dir=&quot;auto&quot;&gt;test_runtime_bridge_query_seam_layout&lt;/code&gt; pins ownership and import direction. No behavior change; moved code logs under its new module name.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator_api/commands.py&lt;/code&gt; is split into per-concern modules behind an unchanged &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; contract (#5628). No product behavior changes.&lt;/li&gt;
&lt;li&gt;Charter command tests no longer fail when the test run starts in a linked git worktree, such as a mission lane worktree (#5317, #5601, #5660). About 20 tests were refused there by the charter write guard and passed from a repository root checkout. One shared &lt;code dir=&quot;auto&quot;&gt;charter_cwd_isolation&lt;/code&gt; fixture replaces the per-file copies and moves the process working directory into the test’s temporary project. A suite-wide check now fails any test that reaches the write guard with its working directory inside the checkout, in every checkout. The stale release pinning inventory is regenerated. No product behavior changes.&lt;/li&gt;
&lt;li&gt;The transitive dependencies &lt;code dir=&quot;auto&quot;&gt;pyjwt&lt;/code&gt; (2.13.0 to 2.15.1) and &lt;code dir=&quot;auto&quot;&gt;urllib3&lt;/code&gt; (2.7.0 to 2.8.0) are bumped in &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; to clear 16 Dependabot alerts, one of them critical (a PyJWT asymmetric-PEM detection bypass); &lt;code dir=&quot;auto&quot;&gt;pyjwt[crypto]&lt;/code&gt; is pulled in by &lt;code dir=&quot;auto&quot;&gt;mcp&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;urllib3&lt;/code&gt; by &lt;code dir=&quot;auto&quot;&gt;requests&lt;/code&gt;, spec-kitty calls neither directly, and no product behavior changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The performance tests compare against a start-up floor measured in the same run, and the commit-recipe gate runs on every pull request&lt;/strong&gt; (#5419, #5614, #5708). No product behavior changes. The three owned-checkout tests assert the ratio of their median to a &lt;code dir=&quot;auto&quot;&gt;--version&lt;/code&gt; floor sampled in the same run; the &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; and warm &lt;code dir=&quot;auto&quot;&gt;context list --json&lt;/code&gt; tests assert a ratio to a fixed interpreter workload. The absolute 2.5 s and 5.0 s limits are gone; the new limits are provisional until checked on the CI runner (#5753). The two planted-work controls use larger plants and per-test bands after the first CI run showed one clearing its limit by 1.5 percent (#5753). A clock-free test pins how many git subprocesses the three commands spawn; it runs in the &lt;code dir=&quot;auto&quot;&gt;cli&lt;/code&gt; shard for changes to those commands. The commit-recipe gate moved to &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_commit_recipe_strings.py&lt;/code&gt;, which runs on every &lt;code dir=&quot;auto&quot;&gt;src/specify_cli&lt;/code&gt; change. It flags a &lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt; command-line shape, not the bare substring; its allowlist went from 14 entries to 2 (#5752).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;400rc5---2026-10-02&quot;&gt;[4.0.0rc5] - 2026-10-02&lt;/h2&gt;
&lt;p&gt;This release candidate removes the bundled dashboard, renames &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; and makes hosted interaction opt-in: a fresh install sends nothing to a hosted endpoint until you turn sending on for both the repository and yourself. Most fixes harden &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;, which now checks that everything it lands came from an approved lane, refuses instead of guessing when it cannot tell, and restores the branches it moved when it fails. It also runs &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; missions one work package at a time in your repository root checkout, stops several commands from deleting or overwriting files you wrote, reads requirement IDs with one shared grammar, and starts faster (a warm &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; went from about 13.2 s to about 1.4 s in local measurement). Scripts that call &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;spec-kitty dashboard&lt;/code&gt;, and projects that use hosted interaction, need changes. See Breaking and Upgrade Notes.&lt;/p&gt;
&lt;h3 id=&quot;breaking-2&quot;&gt;Breaking&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The bundled dashboard is removed: &lt;code dir=&quot;auto&quot;&gt;spec-kitty dashboard&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.dashboard&lt;/code&gt; agent command and the &lt;code dir=&quot;auto&quot;&gt;spk-admin-dashboard&lt;/code&gt; skill are gone&lt;/strong&gt; (#5530, #5527). &lt;strong&gt;Why:&lt;/strong&gt; the local web server was a large, often broken surface with open security defects (#4767, #4768, #4769), and a status UI belongs outside the CLI as an ordinary consumer. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty dashboard&lt;/code&gt; started a detached local web server. &lt;strong&gt;After:&lt;/strong&gt; the command no longer exists. Use &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;) to see mission and work package status, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty orchestrator-api mission-state&lt;/code&gt; from scripts. A read-only Mission Status Read API (#5528) and a separate UI repository are planned as the replacement. &lt;code dir=&quot;auto&quot;&gt;spec-kitty verify-setup --diagnostics&lt;/code&gt; keeps working without its dashboard health panel, and its &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output no longer has the &lt;code dir=&quot;auto&quot;&gt;dashboard_health&lt;/code&gt; key.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; is renamed to &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;&lt;/strong&gt; (#3080). &lt;strong&gt;Why:&lt;/strong&gt; the new name makes clear that the command consolidates lanes into your local branch and does not publish to origin. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; takes the same flags (&lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--keep-branch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--keep-worktree&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--target&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt; and the rest) and behaves the same. &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; is now a hidden, deprecated command that prints a migration message naming &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;, exits non-zero and never consolidates. Unchanged: the &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; key in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;&quot;merge&quot;&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;&quot;squash&quot;&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;&quot;rebase&quot;&lt;/code&gt; strategy values, the &lt;code dir=&quot;auto&quot;&gt;state.json&lt;/code&gt; resume file under &lt;code dir=&quot;auto&quot;&gt;.kittify/runtime/merge/&amp;#x3C;id&gt;/&lt;/code&gt;, and every &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge-driver-*&lt;/code&gt; subcommand.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Hosted interaction is now off by default and needs an explicit opt-in in two places&lt;/strong&gt; (#4971). &lt;strong&gt;Before:&lt;/strong&gt; the CLI shipped a built-in default endpoint (&lt;code dir=&quot;auto&quot;&gt;https://team.spec-kitty.ai&lt;/code&gt;, #3980) and sent status, lifecycle and runtime moments (the live updates it shares with your team) to it whenever an endpoint resolved, with no per-developer or per-repository consent. &lt;strong&gt;After:&lt;/strong&gt; a fresh install has no hosted endpoint, and nothing is sent until you turn sending (“drain”) on in two places: the repository (&lt;code dir=&quot;auto&quot;&gt;hosted.drain&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;) and your personal &lt;code dir=&quot;auto&quot;&gt;config.toml&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;[hosted] drain&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;spec-kitty moments drain on|off|status&lt;/code&gt; manages both. An environment variable can narrow drain but never turn it on. A hosted command you run before setting this up stops with setup guidance instead of a traceback. See &lt;a href=&quot;/adr/3.x/2026-09-26-3-hosted-interaction-opt-in/&quot;&gt;ADR 2026-09-26-3&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; now creates a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission instead of a &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; one&lt;/strong&gt; (#2602). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent mission create --owned-checkout&lt;/code&gt; produced a &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; mission. &lt;strong&gt;After:&lt;/strong&gt; it produces a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission. If you need a &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; mission, create it without &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; (owned checkouts support only &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;) and pass &lt;code dir=&quot;auto&quot;&gt;--topology coord&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 research&lt;/code&gt; now finds its templates through the same resolver as every other mission template&lt;/strong&gt; (#5254). &lt;strong&gt;Before:&lt;/strong&gt; research templates were read from &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;type&gt;/templates/&lt;/code&gt; or from a project-root &lt;code dir=&quot;auto&quot;&gt;templates/&lt;/code&gt; directory. &lt;strong&gt;After:&lt;/strong&gt; those two locations are no longer read. Project overrides go in &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/templates/&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/missions/&amp;#x3C;type&gt;/templates/&lt;/code&gt;), and org packs, &lt;code dir=&quot;auto&quot;&gt;~/.kittify&lt;/code&gt; and the shipped pack defaults apply as for other templates.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;terminology-guard&lt;/code&gt; toolguide is no longer shipped to projects&lt;/strong&gt; (#5223, #5203). &lt;strong&gt;Before:&lt;/strong&gt; every project received it, although it names a test that only the Spec Kitty repository has. &lt;strong&gt;After:&lt;/strong&gt; it lives in Spec Kitty’s own maintainer-only pack, so a project that activated it sees it reported as unknown by &lt;code dir=&quot;auto&quot;&gt;charter pack consistency-check&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The shipped &lt;code dir=&quot;auto&quot;&gt;docs_structural_lint.py&lt;/code&gt; no longer finds its defaults in the &lt;code dir=&quot;auto&quot;&gt;common-docs&lt;/code&gt; styleguide.&lt;/strong&gt; The defaults now live in &lt;code dir=&quot;auto&quot;&gt;packs/built-in/assets/docs_structural_lint.config.yaml&lt;/code&gt;. &lt;strong&gt;Before:&lt;/strong&gt; passing the shipped &lt;code dir=&quot;auto&quot;&gt;common-docs&lt;/code&gt; styleguide to &lt;code dir=&quot;auto&quot;&gt;--styleguide&lt;/code&gt; loaded the lint settings. &lt;strong&gt;After:&lt;/strong&gt; it finds none and exits with code 2. The &lt;code dir=&quot;auto&quot;&gt;structural_lint_config&lt;/code&gt; key is unchanged, and your own override keeps working.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api merge-mission&lt;/code&gt; is renamed to &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt;&lt;/strong&gt; (#3080). The rename follows the CLI command rename above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Orchestrator API &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; now reports setup failures whose error codes are not part of the orchestrator contract as &lt;code dir=&quot;auto&quot;&gt;PLAN_SETUP_FAILED&lt;/code&gt;.&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; returned codes such as &lt;code dir=&quot;auto&quot;&gt;SPEC_REQUIREMENT_IDS_INVALID&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;SPEC_FILE_MISSING&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;TEMPLATE_CONFIGURATION_ERROR&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;PLAN_CONTEXT_UNRESOLVED&lt;/code&gt; directly. &lt;strong&gt;After:&lt;/strong&gt; it returns &lt;code dir=&quot;auto&quot;&gt;PLAN_SETUP_FAILED&lt;/code&gt; and puts the original code in &lt;code dir=&quot;auto&quot;&gt;data.reason&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The top-level &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; Python import shim is removed&lt;/strong&gt; (CR-06). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;import doctrine&lt;/code&gt; still worked and warned that it would be removed in 3.3.0. &lt;strong&gt;After:&lt;/strong&gt; it raises &lt;code dir=&quot;auto&quot;&gt;ImportError&lt;/code&gt;. Import from &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; instead, where that code has lived since the convergence. The &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; command is not affected.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;upgrade-notes-3&quot;&gt;Upgrade Notes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; after installing&lt;/strong&gt; (#4971, #4259, #5100, #5115, #5253). It applies this release’s migrations. They re-stamp older &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; missions whose lane manifest has code lanes (&lt;code dir=&quot;auto&quot;&gt;4_0_0rc5_single_branch_code_lanes_restamp&lt;/code&gt;). They install lane-tip recorder git hooks (&lt;code dir=&quot;auto&quot;&gt;4_0_0rc5_install_lane_tip_recorder&lt;/code&gt;). They repair stale absolute template-set paths in charter catalogs (&lt;code dir=&quot;auto&quot;&gt;4_0_0rc5_heal_template_set_provenance&lt;/code&gt;). They rewrite absolute run directories in the run index to portable project-relative tokens so a copied or moved project resolves its own runtime (&lt;code dir=&quot;auto&quot;&gt;4_0_0rc5_heal_run_index_paths&lt;/code&gt;, #5390). On a logged-in machine they backfill your hosted endpoint from your session (&lt;code dir=&quot;auto&quot;&gt;4_0_0rc5_hosted_endpoint_session_backfill&lt;/code&gt;). They delete a saved &lt;code dir=&quot;auto&quot;&gt;[sync].server_url&lt;/code&gt; that names the retired &lt;code dir=&quot;auto&quot;&gt;https://app.spec-kitty.ai&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;4_0_0_retired_hosted_target&lt;/code&gt;). They retire the doctrine ids this release removes and activate their successors (&lt;code dir=&quot;auto&quot;&gt;4.0.0rc5_retire_single_owner_doctrine_ids&lt;/code&gt;). The bullets below cover what you still have to do yourself.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Replace &lt;code dir=&quot;auto&quot;&gt;spec-kitty dashboard&lt;/code&gt; in scripts and habits&lt;/strong&gt; (#5530). Use &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status --mission &amp;#x3C;handle&gt;&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; for tools) per mission; a multi-mission overview arrives with the Mission Status Read API (#5528). Migration &lt;code dir=&quot;auto&quot;&gt;4.0.0rc5_retire_bundled_dashboard&lt;/code&gt; removes the old &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.dashboard&lt;/code&gt; command files and the &lt;code dir=&quot;auto&quot;&gt;.kittify/.dashboard&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/preflight-warning.json&lt;/code&gt; runtime files. It also stops a dashboard server an older CLI left running in the project, once its command line proves it is that server. If it cannot stop it, it keeps &lt;code dir=&quot;auto&quot;&gt;.kittify/.dashboard&lt;/code&gt; and prints the PID and port so you can stop it by hand. A command file you edited yourself is kept and reported.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Replace &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; (same flags) in scripts, aliases and CI steps, and replace &lt;code dir=&quot;auto&quot;&gt;orchestrator-api merge-mission&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt;&lt;/strong&gt; (#3080).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;To keep using hosted interaction, make sure an endpoint is configured, then turn drain on in both scopes: &lt;code dir=&quot;auto&quot;&gt;spec-kitty moments drain on --repo&lt;/code&gt; (repository, &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;spec-kitty moments drain on&lt;/code&gt; (your personal &lt;code dir=&quot;auto&quot;&gt;config.toml&lt;/code&gt;)&lt;/strong&gt; (#4971). An endpoint comes from &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;config.toml [sync].server_url&lt;/code&gt;; on a machine that is already logged in, &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; backfills it from your session. Check the result with &lt;code dir=&quot;auto&quot;&gt;spec-kitty moments drain status&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Older &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; missions need a one-time topology fix&lt;/strong&gt; (#5100). &lt;strong&gt;Before:&lt;/strong&gt; a mission stored as &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; whose lane manifest still has code lanes silently ran in lane worktrees. &lt;strong&gt;After:&lt;/strong&gt; it stops with &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH_CODE_LANES_UNMIGRATED&lt;/code&gt;. Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; (migration &lt;code dir=&quot;auto&quot;&gt;4_0_0rc5_single_branch_code_lanes_restamp&lt;/code&gt;), or &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-topology --restamp-single-branch&lt;/code&gt; (add &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; to preview). Both change the stored topology to &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, which is how the mission always ran, and nothing else. Missions that are already consolidated, or whose work packages are all in a final lane, are skipped. If &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; reports nothing to do because the migration is already recorded (for example, after merging an upgraded &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;), use the &lt;code dir=&quot;auto&quot;&gt;migrate&lt;/code&gt; command.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; now blocks (&lt;code dir=&quot;auto&quot;&gt;policy.merge_gates.mode: block&lt;/code&gt;) or warns (&lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt;) on issue-matrix rows with an &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt; verdict&lt;/strong&gt; (#5222). &lt;strong&gt;Before:&lt;/strong&gt; consolidation let those verdicts through. &lt;strong&gt;After:&lt;/strong&gt; it applies the same rule as &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;. Resolve such rows with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent issue-verdict&lt;/code&gt; before you consolidate. &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt; is the default.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Default (squash) consolidations that hit a same-hunk conflict with newer target-branch changes now stop with &lt;code dir=&quot;auto&quot;&gt;TARGET_BRANCH_CONTENT_CONFLICT&lt;/code&gt; instead of silently keeping the mission’s side&lt;/strong&gt; (#4892). Update the mission branch against the current target branch, resolving the listed paths, then re-run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;consolidate --dry-run&lt;/code&gt; shows the conflicts first.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; can now fail on an older mission whose spec declares letter-suffixed requirements (&lt;code dir=&quot;auto&quot;&gt;FR-006a&lt;/code&gt;) that no work package maps&lt;/strong&gt; (#3519). Earlier releases did not see those IDs. Map them with &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt;, or re-run &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt; to list malformed declared IDs. See the requirement-ID grammar entry under Changed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;If &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; now refuses a 3.2.0-era coordination mission because &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; is missing, run &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --fix&lt;/code&gt;&lt;/strong&gt; (#4891). Earlier releases skipped the acceptance checks in this case and recorded acceptance anyway.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;After any &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --fix&lt;/code&gt;, commit &lt;code dir=&quot;auto&quot;&gt;.kittify/mission-state-audit/&lt;/code&gt;&lt;/strong&gt; (#4928). The repair manifest and quarantined rows now live there, so they survive &lt;code dir=&quot;auto&quot;&gt;git clean&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;If your repository uses husky, your own &lt;code dir=&quot;auto&quot;&gt;post-commit&lt;/code&gt; hook, or a &lt;code dir=&quot;auto&quot;&gt;core.hooksPath&lt;/code&gt; set globally or inside your working tree, the new lane-tip recorder hooks are skipped. Check for the warning after &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;&lt;/strong&gt; (#5115). Migration &lt;code dir=&quot;auto&quot;&gt;4_0_0rc5_install_lane_tip_recorder&lt;/code&gt; adds &lt;code dir=&quot;auto&quot;&gt;post-commit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;post-rewrite&lt;/code&gt; hooks to &lt;code dir=&quot;auto&quot;&gt;.git/hooks&lt;/code&gt; (or to a &lt;code dir=&quot;auto&quot;&gt;core.hooksPath&lt;/code&gt; set in this repository’s git config that points outside the working tree), so work on a deleted lane can be found again. It never overwrites a hook of your own. Without the hooks, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; can refuse a deleted lane it cannot vouch for (&lt;code dir=&quot;auto&quot;&gt;LANE_WORK_TIP_UNKNOWN&lt;/code&gt;) instead of treating it as empty.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt; on a coordination-topology mission that an earlier release interrupted now refuses instead of resuming without its safety check&lt;/strong&gt; (#5108). The check compares each non-canceled code lane’s latest commit with its commit before the interruption. Resume state saved by an earlier release lacks that record for missions whose lane branches were created under a different naming form (see the lane-naming fix under Fixed), so the resumed run cannot run it. If you see this refusal on an in-flight consolidation, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt; and start a fresh &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;. This is the intended remedy, not a bug.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;In-flight missions whose lane mixes an approved work package (WP) with a WP canceled after it started work will refuse at &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;&lt;/strong&gt; (#5046, #5047). Check the canceled WP’s changes by hand, then recover with &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --attest-canceled-superseded &amp;#x3C;WP&gt; --attest-reason &quot;&amp;#x3C;what you checked&gt;&quot;&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;If your own org packs or project doctrine reference any of the doctrine ids below, update them by hand.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; (migration &lt;code dir=&quot;auto&quot;&gt;4.0.0rc5_retire_single_owner_doctrine_ids&lt;/code&gt;) retires these ids and activates their successors. It rewrites &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; (activation lists, catalog and the legacy &lt;code dir=&quot;auto&quot;&gt;governance.charter.selected_*&lt;/code&gt; block), &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/references.yaml&lt;/code&gt; and your interview answers, so a later &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; cannot bring the old ids back, but it does not touch your own packs. An unreadable file among these is skipped with a warning. An earlier search-tooling retirement migration now cleans that legacy block too. Mapping:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;adversarial-squad-cadence&lt;/code&gt; (styleguide): removed; the &lt;code dir=&quot;auto&quot;&gt;adversarial-squad-deployment&lt;/code&gt; procedure owns the rules.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;bug-fixing-checklist&lt;/code&gt;: replaced by the &lt;code dir=&quot;auto&quot;&gt;test-first-bug-fixing&lt;/code&gt; procedure.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;locality-of-change&lt;/code&gt; (tactic): replaced by &lt;code dir=&quot;auto&quot;&gt;avoid-gold-plating&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;common-docs-curation&lt;/code&gt;: replaced by the &lt;code dir=&quot;auto&quot;&gt;common-docs-scaffold&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;common-docs-write&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;common-docs-find&lt;/code&gt; tactics.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;boring-code-review&lt;/code&gt; (tactic): replaced by the &lt;code dir=&quot;auto&quot;&gt;boring-code-review&lt;/code&gt; styleguide.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;behavior-driven-development&lt;/code&gt; (tactic): replaced by &lt;code dir=&quot;auto&quot;&gt;bdd-scenario-formulation&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;iterative-deepening-review&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tracker-organisation-workflow&lt;/code&gt;: maintainer-only, no longer shipped.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Move research templates from &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;type&gt;/templates/&lt;/code&gt; or a project-root &lt;code dir=&quot;auto&quot;&gt;templates/&lt;/code&gt; directory to &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/templates/&lt;/code&gt;&lt;/strong&gt; (#5254). They are no longer read from the old locations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;If you pass the shipped &lt;code dir=&quot;auto&quot;&gt;common-docs&lt;/code&gt; styleguide to &lt;code dir=&quot;auto&quot;&gt;--styleguide&lt;/code&gt; for structural lint, point it at the asset config &lt;code dir=&quot;auto&quot;&gt;packs/built-in/assets/docs_structural_lint.config.yaml&lt;/code&gt; or at your own override.&lt;/strong&gt; The old form now exits with code 2.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;If &lt;code dir=&quot;auto&quot;&gt;charter pack consistency-check&lt;/code&gt; reports &lt;code dir=&quot;auto&quot;&gt;terminology-guard&lt;/code&gt; as unknown, run &lt;code dir=&quot;auto&quot;&gt;charter deactivate toolguide terminology-guard&lt;/code&gt;&lt;/strong&gt; (#5223).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept --normalize-encoding&lt;/code&gt; now blocks (exit 1) on an artifact it cannot safely disambiguate&lt;/strong&gt; (#4968). Example: a single stray smart-quote byte in an otherwise ASCII spec. It no longer alters such a file silently. Its message points to &lt;code dir=&quot;auto&quot;&gt;spec-kitty validate-encoding --fix &amp;#x3C;path&gt;&lt;/code&gt;, which repairs the file byte by byte.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;If your integration matches on the old &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; error codes, read &lt;code dir=&quot;auto&quot;&gt;data.reason&lt;/code&gt; instead&lt;/strong&gt; (orchestrator API contract 1.8.0).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;If your integration parses &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; JSON, expect different values in &lt;code dir=&quot;auto&quot;&gt;requirement_refs_parsed&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;unknown_requirement_refs&lt;/code&gt;.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;requirement_refs_parsed&lt;/code&gt; now lists refs with their case preserved, including malformed and foreign ones, and &lt;code dir=&quot;auto&quot;&gt;unknown_requirement_refs&lt;/code&gt; also lists malformed refs.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-3&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;New &lt;code dir=&quot;auto&quot;&gt;javascript-supply-chain&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;python-supply-chain&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;java-supply-chain&lt;/code&gt; toolguides&lt;/strong&gt; (#5218). Supply-chain install safety is now language-neutral, and these three toolguides hold the ecosystem-specific commands.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission record-analysis --report-only&lt;/code&gt; records an analysis report without refusing on unrelated dirty work&lt;/strong&gt; (#5017, #4228). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt; refused with &lt;code dir=&quot;auto&quot;&gt;DIRTY_WORKTREE&lt;/code&gt; when any path in the checkout was dirty, including files of another mission that a concurrent session was writing. &lt;strong&gt;After:&lt;/strong&gt; the opt-in &lt;code dir=&quot;auto&quot;&gt;--report-only&lt;/code&gt; flag commits only the report path, on the branch that holds the mission’s planning files, with &lt;code dir=&quot;auto&quot;&gt;git commit --only&lt;/code&gt;. Other staged, edited and untracked files stay as they were. The ordinary command keeps its broad dirty-worktree refusal. &lt;code dir=&quot;auto&quot;&gt;--report-only&lt;/code&gt; still refuses dirty governance or mission inputs, unsafe git state, and governance sources it cannot pin to fixed content (for example a pack root chosen with &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt;). Known limitation: it detects races between cooperating writers, not an OS-wide writer lock.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Re-recording an unchanged &lt;code dir=&quot;auto&quot;&gt;record-analysis --report-only&lt;/code&gt; report is a no-op&lt;/strong&gt; (#5017). It returns &lt;code dir=&quot;auto&quot;&gt;unchanged&lt;/code&gt; and touches nothing. A report copied into another checkout must be re-recorded there.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The software-dev spec template now says whether a requirement builds new behavior or only pins existing behavior&lt;/strong&gt; (#5061). &lt;strong&gt;Before:&lt;/strong&gt; the template could not tell those apart. &lt;strong&gt;After:&lt;/strong&gt; the Functional Requirements table gains trailing &lt;code dir=&quot;auto&quot;&gt;Delivery&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;[build]&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;[ratchet]&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;[folded]&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;No-op passable?&lt;/code&gt; columns, and success criteria get a matching suffix. Requirement-ID parsing and coverage checks are unchanged. The new built-in tactic &lt;code dir=&quot;auto&quot;&gt;acceptance-criteria-non-vacuity&lt;/code&gt; defines the labels and three review rules: pair every refusal or absence assertion with a case where the thing is present, prove each half of a two-part fix on its own, and test the real code path instead of a helper. The software-dev review prompt names the tactic. This is guidance only; nothing enforces the labels.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agents now follow a shipped rule for choosing between a &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; Op and a full Mission before they start work&lt;/strong&gt; (#5266). &lt;strong&gt;Before:&lt;/strong&gt; no shipped doctrine covered the choice, so agents improvised. &lt;strong&gt;After:&lt;/strong&gt; the built-in directive &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_053&lt;/code&gt; (“Choose Op or Mission Before Starting”, &lt;code dir=&quot;auto&quot;&gt;required&lt;/code&gt;) and the &lt;code dir=&quot;auto&quot;&gt;op-or-mission-selection&lt;/code&gt; tactic reach every project through charter context. Any of these means a mission: it needs a spec or plan, it splits into reviewable work packages, it needs a review gate, it spans more than one sitting, or it must be resumable by name or by another agent. An Op is re-checked as it runs and escalated to a mission instead of grown, and every Op is closed with its real outcome.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; missions can commit straight onto a protected branch when you ask for it&lt;/strong&gt; (#5100). &lt;strong&gt;Before:&lt;/strong&gt; the only way was the global &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS&lt;/code&gt; switch, which unprotects the branch for everything. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent mission create --topology single_branch --commit-to-target&lt;/code&gt; records the choice in the mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and lets only that mission’s own writes reach its own target branch. Other missions and ordinary commits stay protected. The flag is refused for any other topology.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor topology&lt;/code&gt; reports missions that need attention, with the fix&lt;/strong&gt; (#5100). &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH_CODE_LANES_UNMIGRATED&lt;/code&gt; names live missions that need the topology fix described in Upgrade Notes (completed missions are skipped). &lt;code dir=&quot;auto&quot;&gt;LANES_MANIFEST_UNREADABLE&lt;/code&gt; names a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission whose &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; cannot be read and tells you how to restore or rebuild it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orchestrator API contract 1.8.0: &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;parsed_spec_ids&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;rejected_requirement_refs&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;success_criteria_coverage&lt;/code&gt;.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --attest-canceled-superseded &amp;#x3C;WP&gt; --attest-reason &quot;&amp;#x3C;what you checked&gt;&quot;&lt;/code&gt; lets you override a canceled-work refusal after checking by hand&lt;/strong&gt; (#5046, #5047). Use it when the refusal says the evidence can never appear later and you have confirmed the canceled content is absent or superseded. It records an operator attestation in the status event log. The attestation covers lane commits made up to that point; a commit made afterward still refuses. It never lifts a failure, or an unreadable event log or git history.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-3&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Charter, &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; and tool-surface commands no longer re-parse shipped doctrine on every lookup&lt;/strong&gt; (#5526). &lt;strong&gt;Before:&lt;/strong&gt; one command parsed the same built-in doctrine files over and over: &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; re-read every artifact file once per referenced artifact while printing its no-cascade warnings, and the built-in DRG, built-in agent profiles, the doctrine catalog and command-template glossary seeds were re-parsed each time a caller asked for them. &lt;strong&gt;After:&lt;/strong&gt; a built-in file is parsed once per process and re-parsed only when its size or modification time changes, and each caller gets its own copy. The warning lines in &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt; share one read-only resolution pass. Output is unchanged. In local measurement the &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; test module went from 15m33s to 5m43s and the &lt;code dir=&quot;auto&quot;&gt;core_misc&lt;/code&gt; module from 13m11s to 6m04s, with identical results.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; now undoes its own branch moves on every failure after the first write, and refuses a protected-target mission before touching anything&lt;/strong&gt; (#5385). &lt;strong&gt;Before:&lt;/strong&gt; only a reconciliation-gate failure rolled back; any other failure between the first write and the gate (a bookkeeping error, a crash, Ctrl-C) left the target, mission or coordination branch advanced, and a LANES mission recorded for protected &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; squashed its lanes and only then failed on the done write, so a re-run needed manual cleanup. &lt;strong&gt;After:&lt;/strong&gt; any non-zero exit, exception or interrupt in that span restores the branches through the snapshot rollback and re-raises the original error, and the merge record claims no completed work packages. Before any branch moves, consolidate (also &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt;) refuses a protected recorded-target mission with &lt;code dir=&quot;auto&quot;&gt;PROTECTED_BRANCH_REFUSED&lt;/code&gt; and its remedy, honoring &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS&lt;/code&gt; and an all-done resume. After a crash that already moved branches, a &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; says so and points to &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt;. See ADR &lt;code dir=&quot;auto&quot;&gt;2026-09-19-1&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission wrap-up now requires a fold-or-keep verdict for every issue-named test file the mission added&lt;/strong&gt; (#5353). &lt;strong&gt;Before:&lt;/strong&gt; the development-assist-test-cleanup step judged a mission’s scaffolding tests, but a file named after an issue (&lt;code dir=&quot;auto&quot;&gt;test_issue_NNNN*&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_repro_NNNN*&lt;/code&gt;) could land without any verdict, and such files accumulated. &lt;strong&gt;After:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;development-assist-test-cleanup&lt;/code&gt; procedure and the &lt;code dir=&quot;auto&quot;&gt;mission-wrap-up-sequence&lt;/code&gt; require a recorded verdict for each one before hand-off: fold its cases into the suite that owns the contract, or keep it renamed after that contract with a one-line reason. This is doctrine guidance only; no CLI behavior changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Shipped docs doctrine no longer points new ADRs at &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/&lt;/code&gt;&lt;/strong&gt; (#5428). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;common-docs&lt;/code&gt; styleguide, the &lt;code dir=&quot;auto&quot;&gt;common-docs-scaffold&lt;/code&gt; tactic and two communication tactics used &lt;code dir=&quot;auto&quot;&gt;adr/3.x/&lt;/code&gt; as the example home for a new ADR, and named &lt;code dir=&quot;auto&quot;&gt;docs/development/3-2-page-inventory.yaml&lt;/code&gt; as the page inventory. &lt;strong&gt;After:&lt;/strong&gt; they describe ADRs as filed under &lt;code dir=&quot;auto&quot;&gt;adr/&amp;#x3C;era&gt;/&lt;/code&gt; for the current era (1.x through 4.x), and name the version-neutral &lt;code dir=&quot;auto&quot;&gt;page-inventory.yaml&lt;/code&gt;. Only the doctrine wording changes. No CLI behavior changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Ownership refusals use one output format on every command&lt;/strong&gt; (#5026, #5277). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent mission check-prerequisites&lt;/code&gt; printed refusals as red &lt;code dir=&quot;auto&quot;&gt;CODE: message&lt;/code&gt; text on stdout and compact JSON. &lt;strong&gt;After:&lt;/strong&gt; they match the other owned commands: &lt;code dir=&quot;auto&quot;&gt;Error: [CODE] message&lt;/code&gt; on stderr in human mode, and indented JSON that always carries &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; (individual commands add their own fields on top — for example &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt; keeps &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; keeps its recovery detail).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Options that cannot work in an owned checkout now refuse instead of being ignored&lt;/strong&gt; (#5277). &lt;strong&gt;Before:&lt;/strong&gt; combining &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;accept --diagnose&lt;/code&gt; (encoding repair), &lt;code dir=&quot;auto&quot;&gt;agent mission check-prerequisites --resume-probe&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; without auto-commit was not checked, because those paths had no owned-checkout handling. &lt;strong&gt;After:&lt;/strong&gt; these combinations refuse with &lt;code dir=&quot;auto&quot;&gt;OWNED_OPTION_UNSUPPORTED&lt;/code&gt;, and a &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; target the owned checkout cannot resolve refuses with &lt;code dir=&quot;auto&quot;&gt;OWNED_INPUT_INVALID&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Language-independent built-in tactics now apply to every project&lt;/strong&gt; (#5284). &lt;strong&gt;Before:&lt;/strong&gt; the catastrophic-regex-backtracking, chain-of-responsibility rule-pipeline and dependency-hygiene tactics carried a language scope, so projects in other languages never saw them. &lt;strong&gt;After:&lt;/strong&gt; they have no language scope, their language-specific snippets are labeled as examples, and they no longer point into Spec Kitty’s own source tree. The value &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt; can no longer be used as a doctrine artifact’s language scope.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt; now read requirement IDs with one shared grammar&lt;/strong&gt; (#3519). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; rejected &lt;code dir=&quot;auto&quot;&gt;FR-006a&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;SC-###&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; could not see them, so an unmapped declared &lt;code dir=&quot;auto&quot;&gt;FR-006a&lt;/code&gt; passed validation unnoticed. &lt;strong&gt;After:&lt;/strong&gt; they share one ID grammar (a declared letter-suffixed requirement must now be mapped): kinds &lt;code dir=&quot;auto&quot;&gt;FR&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;NFR&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;C&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;SC&lt;/code&gt;, digits, an optional lowercase letter, and an optional &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;mission-slug&gt;#&lt;/code&gt; prefix for another mission’s ID. Declared suffixed functional requirements are coverage-gated. Success criteria are tracked in &lt;code dir=&quot;auto&quot;&gt;success_criteria_coverage&lt;/code&gt; but never fail a run, and the “SC … dropped, not traced” warning is gone. A &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;mission-slug&gt;#&amp;#x3C;ID&gt;&lt;/code&gt; citation is never counted as this mission’s own and never fails a run.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A rejected requirement ref now says why&lt;/strong&gt; (#2066). &lt;strong&gt;Before:&lt;/strong&gt; coverage failures listed unmapped IDs, without the IDs the parser found or why a ref was refused. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; reports &lt;code dir=&quot;auto&quot;&gt;parsed_spec_ids&lt;/code&gt; (by kind) and &lt;code dir=&quot;auto&quot;&gt;rejected_requirement_refs&lt;/code&gt;, with one reason per ref: &lt;code dir=&quot;auto&quot;&gt;malformed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;unknown_spec_id&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;foreign_qualified&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; refusals carry &lt;code dir=&quot;auto&quot;&gt;parsed_spec_ids&lt;/code&gt; and the same reasons, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; findings use them too. &lt;code dir=&quot;auto&quot;&gt;--refs&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--batch&lt;/code&gt; accept comma- or whitespace-separated IDs. A foreign citation is never offered for &lt;code dir=&quot;auto&quot;&gt;--replace&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;setup-plan&lt;/code&gt; now catches malformed requirement IDs when the spec is handed to planning&lt;/strong&gt; (#2066). &lt;strong&gt;Before:&lt;/strong&gt; a malformed ID passed through unnoticed. &lt;strong&gt;After:&lt;/strong&gt; a malformed ID in a declared position stops &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt; (exit 1, &lt;code dir=&quot;auto&quot;&gt;SPEC_REQUIREMENT_IDS_INVALID&lt;/code&gt;), naming the ID, the line and the rule. Suspect IDs in prose are returned as non-blocking &lt;code dir=&quot;auto&quot;&gt;requirement_id_warnings&lt;/code&gt;. The shipped spec template, task prompts, review guidelines and anti-pattern checklist now describe the grammar. See &lt;a href=&quot;/adr/3.x/2026-09-29-1-requirement-id-grammar-single-authority/&quot;&gt;ADR 2026-09-29-1&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt; and the retrospective now read requirement IDs the same way &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; does&lt;/strong&gt; (#5387, #5388). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt; judged a spec “not substantive” when its functional requirements were all letter-suffixed (&lt;code dir=&quot;auto&quot;&gt;FR-006a&lt;/code&gt;) or wider than three digits (&lt;code dir=&quot;auto&quot;&gt;FR-1001&lt;/code&gt;), and the retrospective’s “has no WP coverage” gaps missed suffixed FRs, flagged another mission’s FR cited in prose, and let &lt;code dir=&quot;auto&quot;&gt;other-mission#FR-001&lt;/code&gt; in a work package count as covering this mission’s &lt;code dir=&quot;auto&quot;&gt;FR-001&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; both read IDs through the shared requirement-ID grammar: a suffixed or wide FR row makes a spec substantive (a commented-out example row does not), and the retrospective reports exactly the declared FRs no work package cites.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks --refresh-planning-commit&lt;/code&gt; previews what it will change and refuses unsafe split writes&lt;/strong&gt; (#5328). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--validate-only&lt;/code&gt; could report success without showing that &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; would be pointed at a new planning commit, and a refresh could write coordination status before finding out that the planning commit could not be recorded safely. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--validate-only&lt;/code&gt; writes nothing and reports the old and proposed planning commit, plus any leftover status files on the primary planning surface or the coordination branch that would block a real refresh. A real refresh checks both the primary planning surface and the coordination branch before it writes anything and refuses pending work or work split across both, without creating a coordination worktree. A clean commit of only &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; on the primary planning surface still works.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Agents now receive one version of each squad, testing, docs, change-scope, review and supply-chain rule&lt;/strong&gt; (#5218, #5219, #5220, #5221). &lt;strong&gt;Before:&lt;/strong&gt; the same rule was repeated across directives, tactics, prompts, profiles and the charter, and some copies disagreed. &lt;strong&gt;After:&lt;/strong&gt; each rule family has one owning artifact that the others point to by id. The squad rules are now owned by the &lt;code dir=&quot;auto&quot;&gt;adversarial-squad-deployment&lt;/code&gt; procedure.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Every commit command the CLI prints now uses &lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit&lt;/code&gt;&lt;/strong&gt; (#5078). &lt;strong&gt;Before:&lt;/strong&gt; printed recipes suggested a raw &lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt;, which skips the protected-branch and path checks. &lt;strong&gt;After:&lt;/strong&gt; they print &lt;code dir=&quot;auto&quot;&gt;safe-commit&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;--to-branch&lt;/code&gt; filled in. The implement prompt now says the agent working on a work package (WP) pushes its lane and the orchestrator opens the pull request.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The built-in &lt;code dir=&quot;auto&quot;&gt;test-desiderata-and-boundaries&lt;/code&gt; styleguide now says where each test weakness should be caught&lt;/strong&gt; (#5351). &lt;strong&gt;Before:&lt;/strong&gt; it listed Kent Beck’s twelve Test Desiderata but not where to detect a violation. &lt;strong&gt;After:&lt;/strong&gt; it asks for each violation to be caught at the earliest point that can see it: formatter or linter before any test, unit test before end-to-end, a lint-time check before human review. A pattern maps each desideratum to its earliest detector. Two new principles: show that a guard test fails when the thing it guards is broken, and make a test’s body assert what its name promises.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The styleguide now suggests &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_041&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;development-assist-test-cleanup&lt;/code&gt; procedure, so &lt;code dir=&quot;auto&quot;&gt;--cascade all&lt;/code&gt; from the &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; mission types reaches that procedure too.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The built-in doctrine pack no longer ships Spec Kitty’s own maintainer rules to every project&lt;/strong&gt; (#5223, #5203). &lt;strong&gt;Before:&lt;/strong&gt; built-in procedures, styleguides and tactics carried this repository’s package map, test paths, tracker label scheme, issue numbers and mission ids. &lt;strong&gt;After:&lt;/strong&gt; those artifacts give repository-agnostic guidance, and the Spec Kitty specifics live only in Spec Kitty’s own maintainer-only pack.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;architect-alphonso&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implementer-ivan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine-daphne&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;python-pedro&lt;/code&gt; profiles now warn against skipping a canonical prompt, skill or CLI command because it looks too big to load&lt;/strong&gt; (#5165, #5005). &lt;strong&gt;Before:&lt;/strong&gt; agents skipped &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.analyze&lt;/code&gt; on that assumption, and doctrine did not name the failure. &lt;strong&gt;After:&lt;/strong&gt; the built-in &lt;code dir=&quot;auto&quot;&gt;canonical-source-unification&lt;/code&gt; tactic has a new &lt;code dir=&quot;auto&quot;&gt;Unverified size assumption&lt;/code&gt; failure mode: measure or load the surface first, and if it really is too large, file an upstream gap instead of improvising a substitute. The four profiles cite the rule through &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_044&lt;/code&gt;, so it appears in their governance context. Known limitation: mission steps run with no profile bound, so the orchestrating agent is not yet covered automatically (#5005).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The agent-profile schema now documents the &lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt; field as your routing preference for that profile&lt;/strong&gt; (#5117). The &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; routing advisory shows it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Research work packages (WPs) now carry the same ownership contract and profile-load block as every other mission’s task prompt&lt;/strong&gt; (#4060). &lt;strong&gt;Before:&lt;/strong&gt; the research mission’s &lt;code dir=&quot;auto&quot;&gt;task-prompt-template.md&lt;/code&gt; was the only shipped task prompt without &lt;code dir=&quot;auto&quot;&gt;execution_mode&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;authoritative_surface&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;create_intent&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt; in its frontmatter, and without the &lt;code dir=&quot;auto&quot;&gt;## ⚡ Do This First: Load Agent Profile&lt;/code&gt; section. A research WP started with no profile bound and no declared file ownership for the finalize-time checks. &lt;strong&gt;After:&lt;/strong&gt; the template declares &lt;code dir=&quot;auto&quot;&gt;execution_mode: planning_artifact&lt;/code&gt;, lists the research and source-register surfaces as owned files with create intent, and opens with the profile-load block. A drifted duplicate of this template inside the CLI package is left alone here; #5280 removes it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CLI invocations start faster&lt;/strong&gt; (#4211, #4213). &lt;strong&gt;Before:&lt;/strong&gt; every invocation re-rendered the global agent slash-commands from scratch and imported every command module, even for a single command such as a bare &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; a freshness check (template hash, version and on-disk health) skips the render when nothing changed and falls back to a full render on any doubt, and only the invoked command’s module is imported. A warm bare &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; went from about 13.2 s to about 1.4 s in local measurement. The CLI help output is byte-identical.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; missions now run in your repository root checkout, one work package (WP) at a time&lt;/strong&gt; (#5100, #4828). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission still created lane worktrees and &lt;code dir=&quot;auto&quot;&gt;kitty/mission-*-lane-*&lt;/code&gt; branches, so code landed on branches you never declared, and running a solo, sequential mission in one checkout was only possible through manual workarounds. &lt;strong&gt;After:&lt;/strong&gt; there are no lane worktrees or lane branches. Each WP runs in order in the repository root checkout (or your owned checkout), with clean linear history. Create such a mission with &lt;code dir=&quot;auto&quot;&gt;--topology single_branch&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;). See &lt;a href=&quot;/context/topology/&quot;&gt;Context: Topology&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission refuses unsafe checkouts, with an error code and a fix&lt;/strong&gt; (#5100). &lt;strong&gt;Before:&lt;/strong&gt; when a work package ran in the repository root checkout, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; did not check which branch was checked out, whether another work package was already in progress there, or whether you had uncommitted changes. &lt;strong&gt;After:&lt;/strong&gt; it stops with &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_WRONG_BRANCH&lt;/code&gt; when the checkout is on the wrong branch (for planning and code work packages (WPs) alike), &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_OCCUPIED&lt;/code&gt; when a WP is already in progress there, and &lt;code dir=&quot;auto&quot;&gt;WRITE_CHECKOUT_DIRTY&lt;/code&gt; when there are uncommitted changes (resuming your own WP is exempt). Only WPs in progress in the repo-root lane of a live &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission count as occupying it, so older missions without a lane manifest and completed missions never block you.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;New missions created on a non-primary branch now default to &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, never &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;&lt;/strong&gt; (#2602). &lt;strong&gt;Before:&lt;/strong&gt; a mission created on a non-primary branch, or a PR-bound mission whose coordination branch was unreachable, could silently come out &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the default there is &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; (parallel lane worktrees). You get &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; only by asking with &lt;code dir=&quot;auto&quot;&gt;--topology single_branch&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;. In a repository with no &lt;code dir=&quot;auto&quot;&gt;origin/HEAD&lt;/code&gt; (for example, no remote), the current branch counts as the primary branch, so a create there still defaults to &lt;code dir=&quot;auto&quot;&gt;coord&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 doctor coordination --fix&lt;/code&gt; no longer turns a mission it flattens into &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;&lt;/strong&gt; (#2602). &lt;strong&gt;Before:&lt;/strong&gt; the flattened mission could become &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it records &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, which is how such a mission already ran.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Creating a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission on a protected branch now switches your repository root checkout to a new mission branch&lt;/strong&gt; (#5100). &lt;strong&gt;Before:&lt;/strong&gt; on a protected branch such as &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, it skipped the scaffold commit and left the new mission’s files uncommitted. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; creates and checks out &lt;code dir=&quot;auto&quot;&gt;kitty/mission-&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt;, refusing first if the checkout is dirty. &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; prints “Switched checkout to …”, and &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt; reports the mission branch as the expected checkout. &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; lands the branch onto the target, switches you back and clears the recorded branch, also when you keep the branch with &lt;code dir=&quot;auto&quot;&gt;--keep-branch&lt;/code&gt;. Run from any other checkout, it names the mission branch to check out. &lt;code dir=&quot;auto&quot;&gt;mission close --discard&lt;/code&gt; switches you back to the target before deleting the mission branch, and refuses instead of reporting success when the mission’s files are not in your checkout. Discarding a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission never deletes its target branch.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;For code work packages (WPs) of a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission, &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; now refuses until there is a real commit since the claim&lt;/strong&gt; (#5100). Claim bookkeeping commits do not count. &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; also never sweeps unrelated uncommitted files into a commit.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;With hosted interaction off, the local execution-state view still refreshes automatically&lt;/strong&gt; (#4971). The &lt;code dir=&quot;auto&quot;&gt;ledger.projection&lt;/code&gt; setting controls this and is on by default.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-3&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; in a copied or moved project now uses that project’s own run cursor&lt;/strong&gt; (#5390, #5389, refs #2624). The run index (&lt;code dir=&quot;auto&quot;&gt;.kittify/runtime/feature-runs.json&lt;/code&gt;) stored each run’s directory as an absolute path and updated it without a lock. &lt;strong&gt;Before:&lt;/strong&gt; running &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; in a copied project folder (with its &lt;code dir=&quot;auto&quot;&gt;.kittify/runtime&lt;/code&gt; state) advanced the &lt;strong&gt;original&lt;/strong&gt; folder’s run cursor and exited 0 — marking a step complete in the original from an artifact that only existed in the copy; a moved project instead failed with &lt;code dir=&quot;auto&quot;&gt;RUN_STATE_MISSING&lt;/code&gt; at the old path; and two concurrent &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; starts could lose one mission’s registration, silently restarting it from step one. &lt;strong&gt;After:&lt;/strong&gt; run directories are stored relative to the project and resolved against the project you run the command in, so a copied or moved project operates on its own runtime; one resolving outside the project is refused. Concurrent starts take a lock and merge, so no registration is lost. Heal an older index with &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate&lt;/code&gt; (inspect it with &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor run-index&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Coordination missions no longer commit their status log to the target branch, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer fails with &lt;code dir=&quot;auto&quot;&gt;TARGET_BRANCH_CONTENT_CONFLICT&lt;/code&gt;&lt;/strong&gt; (#5440). &lt;strong&gt;Before:&lt;/strong&gt; on a &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; mission, &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; committed &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; to the target branch, and later lifecycle commands kept writing status to the repository root checkout because the coordination worktree had no mission directory yet. Consolidation then refused. &lt;strong&gt;After:&lt;/strong&gt; create seeds the status log on the coordination branch (with &lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;SpecifyStarted&lt;/code&gt;) and the target-branch scaffold commit carries only &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; records &lt;code dir=&quot;auto&quot;&gt;TasksStarted&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;WPCreated&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;TasksCompleted&lt;/code&gt; in that same log and leaves no &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; in the root checkout. &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; missions are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A documented review rejection is now reported once, as a review loop&lt;/strong&gt; (#2267).
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;retrospect create&lt;/code&gt; reported each &lt;code dir=&quot;auto&quot;&gt;move-task --to planned --force --review-feedback-file&lt;/code&gt; rejection up to three times: as a &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; override that “typically indicates the runtime guard failed”, as a lane bounce when the reviewer rejected from &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; without claiming the work package, and as rework “not captured as a documented review rejection”. &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;’s “Hollow reviews detected” warning counted the same forced rejections towards its &lt;code dir=&quot;auto&quot;&gt;force_count&lt;/code&gt; threshold, so it named the most-reviewed work packages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;After:&lt;/strong&gt; a backward move that carries a review-feedback pointer is a review rejection wherever the reviewer issued it, and feeds only the &lt;code dir=&quot;auto&quot;&gt;review_loop&lt;/code&gt; finding. A reviewer’s forced &lt;code dir=&quot;auto&quot;&gt;for_review → in_progress&lt;/code&gt; review claim is no longer reported as a &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; override or a lane bounce either. The force-override finding counts only other &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; moves, the implementation-cycle finding reports only &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; re-entries that no documented rejection explains, and the hollow-review warning discounts forced documented rejections and review claims. A &lt;code dir=&quot;auto&quot;&gt;force-override&lt;/code&gt; marker or a synthetic &lt;code dir=&quot;auto&quot;&gt;review:&amp;#x3C;WP&gt;&lt;/code&gt; ref is not feedback: a move sent back with &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; but no &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt; now counts as a lane bounce (and a &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; override when forced), not as a review loop.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; now commits status rows it leaves in the coordination worktree&lt;/strong&gt; (#5513).
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Before:&lt;/strong&gt; on a coordination-topology mission, the commit router dropped a status log (&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;) named by its primary-checkout path and reported it as already committed when the change existed only in the coordination worktree. &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; exited cleanly with those status rows uncommitted, where a later coordination teardown could lose them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;After:&lt;/strong&gt; the router commits the coordination copy in place, under the status lock. It still never copies the primary copy over it, and a change that exists only in the primary checkout is still refused as a wrong-surface write.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine pack validate&lt;/code&gt; no longer reports a spurious &lt;code dir=&quot;auto&quot;&gt;same_id_collision&lt;/code&gt; advisory when a pack declares its augmentation intent in &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt;&lt;/strong&gt; (#5494).
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Before:&lt;/strong&gt; the validator read intent only from &lt;code dir=&quot;auto&quot;&gt;drg/*.graph.yaml&lt;/code&gt; (a shape the validator itself has rejected since #3387) and ignored &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt;, the shape the runtime actually loads. A pack that correctly declared an &lt;code dir=&quot;auto&quot;&gt;enhances&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;overrides&lt;/code&gt; edge in &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; was still warned that its artifact collided with a built-in of the same id. An edge whose endpoints use bare node ids was dropped altogether, so a misspelled bare target passed validation even though the runtime refuses it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;After:&lt;/strong&gt; the validator reads &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; intent through the same pack loader the runtime uses, and resolves bare-id endpoints by the runtime’s rules. Declared augmentation suppresses the advisory, and a bare target that names no known artifact is reported as &lt;code dir=&quot;auto&quot;&gt;unknown_target&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty retrospect create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;backfill&lt;/code&gt; now auto-commit coordination-topology missions, and never commit to a protected branch&lt;/strong&gt; (#5353). &lt;strong&gt;Before:&lt;/strong&gt; on a &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; mission git refused the add from the repository root, so nothing was committed; on other missions the record landed on whatever branch was checked out, protected &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; included. &lt;strong&gt;After:&lt;/strong&gt; the auto-commit goes through the standard mission commit router. The event log of a coordination-topology mission is committed on the coordination branch; the record, and the event log of other missions, on the target branch. &lt;code dir=&quot;auto&quot;&gt;backfill&lt;/code&gt; commits one mission at a time. On a protected target such as &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; the record is left uncommitted (exit 0) with a warning naming the files and saying to commit them from a feature branch through a pull request. Nothing new to commit is silent; other failures still warn.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty retrospect create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;backfill&lt;/code&gt; write the &lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptured&lt;/code&gt; event to the mission’s canonical event log&lt;/strong&gt; (#5353). &lt;strong&gt;Before:&lt;/strong&gt; the event (and &lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptureFailed&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;RetrospectiveSkipped&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;backfill&lt;/code&gt;) was appended to the repository root checkout’s copy of &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, so on a coordination-topology mission it never reached the coordination branch and was left uncommitted. &lt;strong&gt;After:&lt;/strong&gt; the event is written to the same event log the command commits, as resolved by the canonical status surface. &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent retrospect synthesize --fabricate-empty&lt;/code&gt; resolves its &lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptured&lt;/code&gt; event the same way, so the fabricated-record path no longer strands its event on the primary copy either.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent retrospect synthesize --proposal-id&lt;/code&gt; no longer applies pending or rejected proposals&lt;/strong&gt; (#5353). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--proposal-id&lt;/code&gt; replaced the accepted-only selection, so naming a pending or rejected proposal planned it, and with &lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt; applied it. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--proposal-id&lt;/code&gt; only narrows the accepted proposals. An id that is pending, rejected or not in the record is refused with exit 1 before anything is planned or applied; the error names each id and its status, and under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; stderr carries &lt;code dir=&quot;auto&quot;&gt;{&quot;error&quot;: &quot;proposal_not_accepted&quot;, &quot;detail&quot;, &quot;proposal_ids&quot;, &quot;statuses&quot;}&lt;/code&gt;. On a generator-shaped record (the shape &lt;code dir=&quot;auto&quot;&gt;retrospect create&lt;/code&gt; writes), every id is refused as &lt;code dir=&quot;auto&quot;&gt;unsupported_generator_record&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; error too. With &lt;code dir=&quot;auto&quot;&gt;--fabricate-empty&lt;/code&gt;, the message says the empty record was written.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission commands now work from an owned checkout, and read and write only there&lt;/strong&gt; (#3449, #4252, #5026, #4867, #5277). An owned checkout is a linked worktree you pass with &lt;code dir=&quot;auto&quot;&gt;--owned-checkout &amp;#x3C;path&gt;&lt;/code&gt; (or run from, see below) that holds its own copy of the mission. &lt;strong&gt;Before:&lt;/strong&gt; most commands ignored it and resolved the mission from the repository root checkout. &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent mission setup-plan&lt;/code&gt; returned &lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_FOUND&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;PLAN_CONTEXT_UNRESOLVED&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt; read work packages from the repository root. &lt;code dir=&quot;auto&quot;&gt;next --result success&lt;/code&gt; could crash with a traceback and leave the run stuck at &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; could refuse after writing half its changes. &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; read charter activation and templates from the repository root. &lt;strong&gt;After:&lt;/strong&gt; every lifecycle command validates ownership once and reads and writes only inside the owned checkout, leaving the repository root checkout untouched:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent mission setup-plan&lt;/code&gt; accept &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; runs the same ownership validator as every other owned command, instead of checking only the claim.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; either succeeds or leaves the owned checkout’s mission directory unchanged, instead of refusing after a partial write (a non-owned coordination-topology finalize keeps its prior residual, tracked in #5343).&lt;/li&gt;
&lt;li&gt;Coordination-topology failures come back as typed error codes instead of raw git errors.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Running a command from inside a valid owned checkout adopts it without &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;&lt;/strong&gt; (#5026). &lt;strong&gt;Before:&lt;/strong&gt; flagless &lt;code dir=&quot;auto&quot;&gt;context resolve&lt;/code&gt; adopted the current directory without validating it, and other commands refused. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent tasks mark-status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent mission check-prerequisites&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; adopt a valid owned checkout after exactly one validation. Lane and coordination worktrees are still refused as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A stale copy of the mission in the repository root no longer wins&lt;/strong&gt; (#5277). &lt;strong&gt;Before:&lt;/strong&gt; if the repository root checkout also held the mission, &lt;code dir=&quot;auto&quot;&gt;context resolve&lt;/code&gt; could exit 0 while pointing at the repository root’s work-package file and a lane worktree that did not exist. &lt;strong&gt;After:&lt;/strong&gt; the owned checkout’s copy wins. The JSON output of &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent mission setup-plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent mission finalize-tasks&lt;/code&gt; gains a &lt;code dir=&quot;auto&quot;&gt;stale_repository_root_copy&lt;/code&gt; key (&lt;code dir=&quot;auto&quot;&gt;{&quot;path&quot;, &quot;mission_id&quot;}&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt;, owned runs only), and a warning names the stale path.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; lane guard’s cleanup command no longer deletes planning files you wrote&lt;/strong&gt; (#3931). When &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task&lt;/code&gt; finds &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; files committed on a lane branch, it prints a &lt;code dir=&quot;auto&quot;&gt;git restore&lt;/code&gt; command to clean them off. &lt;strong&gt;Before:&lt;/strong&gt; that command restored the whole &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; directory from the planning branch tip, so following it deleted lane-local files the planning branch did not carry (for example &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt;) and pulled other missions’ planning content into the lane. &lt;strong&gt;After:&lt;/strong&gt; it restores only the named offending files, and from the merge-base of the lane and its planning branch, so the files you wrote on the lane are left untouched.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;consolidation-integrity-and-rollback&quot;&gt;Consolidation integrity and rollback&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; now refuses before it overwrites an ignored or untracked file whose path contains a space or a non-ASCII character&lt;/strong&gt; (#5392). &lt;strong&gt;Before:&lt;/strong&gt; git prints such a path quoted (&lt;code dir=&quot;auto&quot;&gt;!! &quot;src/local data/&quot;&lt;/code&gt;), the advance compared that text with the incoming tree’s unquoted paths, found no match, and the checkout refresh overwrote the local file (for example ignored &lt;code dir=&quot;auto&quot;&gt;src/local data/notes.txt&lt;/code&gt; when a lane started tracking that path). &lt;strong&gt;After:&lt;/strong&gt; paths are read from git as NUL-separated data and compared by component, so the advance stops with a dirty-worktree refusal that names the path, and the target and the local bytes stay as they were. A file whose name contains &lt;code dir=&quot;auto&quot;&gt;-&gt;&lt;/code&gt; is now read as one path instead of being mistaken for a rename.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; now refuses before it advances the target when a commit replaces a tracked directory with a file and ignored or untracked files still sit inside that directory&lt;/strong&gt; (#5400). &lt;strong&gt;Before:&lt;/strong&gt; consolidation treated the replacement as safe. The checkout refresh deleted the local files (for example ignored &lt;code dir=&quot;auto&quot;&gt;src/store/local.txt&lt;/code&gt; when tracked &lt;code dir=&quot;auto&quot;&gt;src/store/default.txt&lt;/code&gt; became the tracked file &lt;code dir=&quot;auto&quot;&gt;src/store&lt;/code&gt;), advanced the target, marked the work package done, and saved no stash. &lt;strong&gt;After:&lt;/strong&gt; the advance stops with a dirty-worktree refusal that names the obstructing path. The target commit, the tracked directory, and the local bytes stay as they were, and the work package stays approved. A path that only shares text with the replaced directory, such as &lt;code dir=&quot;auto&quot;&gt;storehouse&lt;/code&gt; next to &lt;code dir=&quot;auto&quot;&gt;store&lt;/code&gt;, is left alone.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A refused or failed &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; restores the branches it moved and reports what it restored&lt;/strong&gt; (#5338, #5318, #5332, #5296). &lt;strong&gt;Before:&lt;/strong&gt; a consolidation whose approved-work claim could not be proven could still merge lanes, mark work packages (WPs) &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, number the mission and advance the target branch before refusing. A failed integrity check or a refused bookkeeping-file check restored at most the target. &lt;strong&gt;After:&lt;/strong&gt; such a claim refuses before any change. A failed check, a refused bookkeeping-file check and &lt;code dir=&quot;auto&quot;&gt;consolidate --abort&lt;/code&gt; restore every branch the run moved (target, mission branch, coordination branch) to its pre-run commit, only if nobody moved it since, and print which were restored. A branch another actor moved is reported, not overwritten. Known limitation: a commit that lands on a branch during the same phase is not detected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A deleted lane branch no longer blocks &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt;&lt;/strong&gt; (#5338, #5318, #5332, #5296). &lt;strong&gt;Before:&lt;/strong&gt; the abort stopped at the missing branch. &lt;strong&gt;After:&lt;/strong&gt; it prints the &lt;code dir=&quot;auto&quot;&gt;git branch&lt;/code&gt; command to recreate it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Claiming a planning work package (WP) on the target checkout no longer merges code lanes onto the target branch&lt;/strong&gt; (#5338, #5318, #5332, #5296). &lt;strong&gt;Before:&lt;/strong&gt; a planning WP that depended on code WPs merged those code lanes straight onto the target branch at claim time. &lt;strong&gt;After:&lt;/strong&gt; it no longer does. The code lanes reach the target through &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; stale-assertion findings show their grade again&lt;/strong&gt; (#5353). &lt;strong&gt;Before:&lt;/strong&gt; each post-consolidation stale-assertion finding was printed without its &lt;code dir=&quot;auto&quot;&gt;[high]&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;[medium]&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;[low]&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;[info]&lt;/code&gt; label, because the console read the label as a markup tag and dropped it, so actionable findings looked the same as informational ones. &lt;strong&gt;After:&lt;/strong&gt; the grade label is printed as written.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer ships a canceled work package’s changes when it shared a lane with an approved one&lt;/strong&gt; (#5046, #5047). &lt;strong&gt;Before:&lt;/strong&gt; if a work package (WP) committed changes and was then canceled while another WP in the same lane was approved, consolidation trusted the whole lane. The canceled changes reached the target branch with exit 0, under both the &lt;code dir=&quot;auto&quot;&gt;squash&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; strategies. &lt;strong&gt;After:&lt;/strong&gt; every WP status change records the lane’s latest commit in the status event log, so consolidation’s integrity check can tell which commits the canceled WP made. Canceled changes that no surviving WP superseded fail the check, naming the file, WP and lane. Superseded changes still pass. To recover, revert the change on the lane through a surviving WP and re-run &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;; a WP the failed run already recorded &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; is recorded again once its rework lands. Known limitation: five edge cases remain open (#5330).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; refuses instead of guessing when it cannot tell what a canceled work package (WP) changed&lt;/strong&gt; (#5046, #5047). &lt;strong&gt;Before:&lt;/strong&gt; there was no such check. &lt;strong&gt;After:&lt;/strong&gt; when the canceled WP’s commits cannot be established (for example, in a mission created before this change), consolidation refuses. On a lane that mixes approved and canceled WPs, it also refuses a content commit that falls outside every WP’s period of work (such as a commit made after the cancel), naming the lane, the commit and a path. Commits a lane inherits from a dependency lane or from the target branch never count. The refusal names the &lt;code dir=&quot;auto&quot;&gt;--attest-canceled-superseded&lt;/code&gt; override (see Added). Background: &lt;a href=&quot;/adr/3.x/2026-09-29-1-closed-world-refuse-on-mixed-lanes/&quot;&gt;ADR 2026-09-29-1&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A refusal from consolidation’s integrity check now restores the target branch, as a failure always did&lt;/strong&gt; (#5046, #5047). &lt;strong&gt;Before:&lt;/strong&gt; a refusal exited non-zero with the advanced target branch left in place. &lt;strong&gt;After:&lt;/strong&gt; the target returns to its pre-consolidation commit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer destroys your own uncommitted &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; edits&lt;/strong&gt; (#4933). &lt;strong&gt;Before:&lt;/strong&gt; the dirty-tree safety check exempted any file named &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; anywhere in the tree, so a user’s own &lt;code dir=&quot;auto&quot;&gt;src/app/meta.json&lt;/code&gt; was treated as Spec Kitty bookkeeping, and consolidation could &lt;code dir=&quot;auto&quot;&gt;reset --hard&lt;/code&gt; the repository root checkout or force-remove a lane worktree over it, exiting 0. &lt;strong&gt;After:&lt;/strong&gt; only &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/meta.json&lt;/code&gt; and the legacy &lt;code dir=&quot;auto&quot;&gt;.kittify/meta.json&lt;/code&gt; are exempt; one level deeper (for example &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/research/meta.json&lt;/code&gt;) counts as real changes again. A dirty user &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; refuses with &lt;code dir=&quot;auto&quot;&gt;MERGE_UNSAFE_PRIMARY_DIRTY&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;MERGE_UNSAFE_WORKTREE_DIRTY&lt;/code&gt;, names the file(s) and prints the commit-or-stash fix. The refusal’s reset-to-HEAD advice now appears only when the checkout is provably behind its own HEAD, instead of on every fresh consolidation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; that stops at a merge gate can be re-run&lt;/strong&gt; (#5111). &lt;strong&gt;Before:&lt;/strong&gt; a fresh run saved its resume state before the merge gates ran but wrote the integrity-check marker only after them. A gate failure, the history check or a declined review prompt left state without a marker, and the next plain &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; auto-resumed it and was refused as a “pre-fix in-flight merge state”, forcing &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; and a manual check of branches no command had touched. &lt;strong&gt;After:&lt;/strong&gt; any exit before the first change clears the run’s own state and marker, so the re-run is genuinely fresh and honors its own &lt;code dir=&quot;auto&quot;&gt;--target&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--strategy&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt;. The marker is written together with a fresh state, so even a hard-killed run leaves a resumable record, and &lt;code dir=&quot;auto&quot;&gt;consolidate --abort&lt;/code&gt; removes the marker along with the state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Issue-matrix checks on coordination-topology missions now read verdicts from the coordination branch&lt;/strong&gt; (#5222, #5171, #4943). &lt;strong&gt;Before:&lt;/strong&gt; mission-review Gate 4 and the consolidation merge gate read the copy of &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; in your working tree, which can hold stale content. Mission-review reported a false hard failure (#5171), and the merge gate found nothing to enforce and passed falsely (#4943). &lt;strong&gt;After:&lt;/strong&gt; both read verdicts from the coordination branch and refuse if that branch was deleted or cannot be read. A legacy &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; is still accepted, and a mission with no gating references still passes. &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; missions read the same directory as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The default &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer fails a legitimate squash when two approved work packages (WPs) edit different regions of the same file&lt;/strong&gt; (#5051, #5001, #5038, #4945, #4977, #4981). &lt;strong&gt;Before:&lt;/strong&gt; the merged result matched neither lane’s content, so the integrity check could not trace it to an approved lane and reverted the target. &lt;strong&gt;After:&lt;/strong&gt; a path touched by exactly two approved lanes is accepted when &lt;code dir=&quot;auto&quot;&gt;git merge-tree --write-tree&lt;/code&gt; of the two lanes’ commits merges cleanly to exactly the content on the target. A binary file, a genuine conflict, more than two approved lanes, an unresolvable base or git older than 2.38 still fail. Content from canceled, removed or superseded work is still caught. Known limitation: when two lanes change the same line and you resolve the conflict by hand, the result matches neither lane, so the check still fails that consolidation (#5051).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; (fresh or &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt;) no longer refuses a legitimate mission whose lanes were created under a different naming form than its lanes manifest implies&lt;/strong&gt; (#5108). &lt;strong&gt;Before:&lt;/strong&gt; consolidation re-derived each lane’s branch and worktree name from the manifest’s mission identity instead of using the name lane creation produced. It failed with “no approved lane resolved any commits” for a legacy &lt;code dir=&quot;auto&quot;&gt;NNN-slug&lt;/code&gt; mission whose identity was backfilled later, for a slug embedding a mismatched mid8, and for an invalid manifest identity of any length; an identity shorter than 8 characters crashed outright. &lt;strong&gt;After:&lt;/strong&gt; every stage uses the lane branch and worktree that were actually created, all four shapes consolidate cleanly, and cleanup leaves no orphaned branch or worktree. See &lt;a href=&quot;/adr/3.x/2026-09-26-2-lane-naming-keyed-on-creation-input/&quot;&gt;ADR 2026-09-26-2&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; now refuses, naming the branch, when an approved lane’s created branch does not exist in git&lt;/strong&gt; (#5108). &lt;strong&gt;Before:&lt;/strong&gt; it silently produced an empty commit set for that lane.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --strategy merge --resume&lt;/code&gt; no longer loses the mission’s code when the repository root checkout lags behind its own HEAD after an interrupted run&lt;/strong&gt; (#4997, #4982). &lt;strong&gt;Before:&lt;/strong&gt; if the target branch had advanced but refreshing the checkout failed or the process was killed, the mission’s files showed as staged deletions. &lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; refused with &lt;code dir=&quot;auto&quot;&gt;MERGE_UNSAFE_PRIMARY_DIRTY&lt;/code&gt;. Committing those deletions let the resumed run mark every work package (WP) &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, delete the lanes and exit 0 with none of the mission’s code on the target. &lt;strong&gt;After:&lt;/strong&gt; when the checkout is provably only lagging behind its own HEAD, &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; refreshes it in place and continues, so the approved code lands. If there is a real edit, an intentional deletion outside the mission, or an untracked or gitignored file in the way, resume refuses and discards nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A consolidation that integrates nothing no longer reports success when the target is missing approved mission content&lt;/strong&gt; (#4997). &lt;strong&gt;Before:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;--strategy merge&lt;/code&gt;, an “Already up to date” integration was not checked against the approved work, so a target that lacked the mission’s files still exited 0. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; checks that case the same way as the default squash and refuses (non-zero) when approved content would be missing. Lane-to-mission steps that legitimately have nothing to integrate still pass.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The default &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer refuses a legitimate consolidation when a &lt;code dir=&quot;auto&quot;&gt;traces/*.md&lt;/code&gt; file was edited on both the target and an approved lane&lt;/strong&gt; (#5038). &lt;strong&gt;Before:&lt;/strong&gt; the check demanded that the landed file match the coordination copy byte for byte. The file’s registered merge driver (for example &lt;code dir=&quot;auto&quot;&gt;merge-driver-traces&lt;/code&gt;, a lossless union) legitimately produces a third version, so a clean single-lane consolidation exited 1 with no teardown. &lt;strong&gt;After:&lt;/strong&gt; the check replays the registered merge driver and passes when the landed file equals its result. It still refuses when a changed path has no registered driver, a version is missing, or the driver errors.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The default &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer lets a canceled work package’s file deletion reach the target&lt;/strong&gt; (#5022, #5001). &lt;strong&gt;Before:&lt;/strong&gt; the default squash consolidation checked added and changed files but skipped deletions. A deletion by a canceled or removed work package (WP) of a file that no approved lane re-authors could ride another lane onto the target and exit 0, losing the file on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; deletions are checked too. A squashed deletion is accepted only when an approved lane also deleted the path, or the path is mission bookkeeping. Otherwise the consolidation fails and restores the target to its earlier state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A lane holding both an approved work package (WP) and a canceled WP no longer makes a legitimate &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --strategy merge&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;rebase&lt;/code&gt;) fail&lt;/strong&gt; (#5018). &lt;strong&gt;Before:&lt;/strong&gt; if any WP in a lane was canceled, all of that lane’s commits were treated as excluded, colliding with the approved WP’s own commits. The consolidation then failed and the target was reverted. &lt;strong&gt;After:&lt;/strong&gt; the approved WP’s commits count as approved work and are no longer double-counted as excluded. A canceled commit that is not part of the approved history still fails when it is on the target, so canceled code is still kept out.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt; no longer refuses a squash consolidation that had already landed and only crashed during teardown&lt;/strong&gt; (#5021). &lt;strong&gt;Before:&lt;/strong&gt; the resume rebuilt its checks from a partly torn-down lane, could not trace the landed content to an approved lane, and refused. &lt;strong&gt;After:&lt;/strong&gt; once the checks have passed, resume sees the target already at that commit and finishes the teardown without re-running them. A genuinely incomplete resume still runs the full checks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The default (squash) &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; now checks that everything it lands came from an approved lane&lt;/strong&gt; (#5013, #4945, #4977, #4981, #5001). &lt;strong&gt;Before:&lt;/strong&gt; the content checks ran only under &lt;code dir=&quot;auto&quot;&gt;--strategy merge&lt;/code&gt;. The default squash returned success before them, so the code of a removed or canceled work package (WP) could ride another lane onto the target with exit 0. &lt;strong&gt;After:&lt;/strong&gt; each content path of the squashed diff is matched against the final file contents authored on the approved lanes. A path that matches none fails the integrity check and restores the target. If the check cannot run (a git error, an unresolved base, or no authored content found), the consolidation refuses instead of passing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt; now keeps your original &lt;code dir=&quot;auto&quot;&gt;--strategy&lt;/code&gt; and no longer drops a lane that was already consolidated&lt;/strong&gt; (#4982, #4997). &lt;strong&gt;Before:&lt;/strong&gt; the strategy was never saved, so a resume silently fell back to squash. The resume also compared the lane with a state that already held the first attempt’s partial work, so the pre-interrupt commit of an already-consolidated lane was dropped. &lt;strong&gt;After:&lt;/strong&gt; resume uses the saved strategy and refuses a contradictory explicit &lt;code dir=&quot;auto&quot;&gt;--strategy&lt;/code&gt;. It keeps the already-consolidated lane’s exact commit. It tolerates the lagging-checkout window but refuses when the lane truly diverged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer exits 0 after deleting lanes and marking work packages (WPs) &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; while the target holds the wrong code&lt;/strong&gt; (#4945, #4977, #5001). &lt;strong&gt;Before:&lt;/strong&gt; an ordinary &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; could land removed or canceled code on the target, or leave an approved WP’s code off it, and still exit 0. &lt;strong&gt;After:&lt;/strong&gt; an integrity check runs before any teardown. Every approved WP’s commits must be on the target, and no excluded commit may be. Approvals are read from the ordered status log and from lane-branch tips. A commit that cannot be traced to any WP fails the consolidation and restores the target.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer overwrites a target branch that moved while it ran&lt;/strong&gt; (#4996, #5001). &lt;strong&gt;Before:&lt;/strong&gt; the target branch was advanced with a plain write, guarded only by an earlier ancestry check. A second mission consolidating at the same time could be rewound off &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, leaving its code reachable only through unreachable git objects while both runs exited 0. &lt;strong&gt;After:&lt;/strong&gt; the advance now succeeds only if the branch is still where &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; last read it. If it moved, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; stops and does not retry.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer destroys status and verdict commits made after its bookkeeping commit&lt;/strong&gt; (#4981, #5001). &lt;strong&gt;Before:&lt;/strong&gt; coordination teardown removed the coordination branch without carrying over later commits, so a concurrent status change or &lt;code dir=&quot;auto&quot;&gt;acceptance-verdict&lt;/code&gt; that reported “committed” survived only in &lt;code dir=&quot;auto&quot;&gt;git fsck --unreachable&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; teardown first carries over every commit made after that point, and stops if the coordination branch moved in the meantime.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt; now resumes onto the branch you targeted&lt;/strong&gt; (#4985, #4991, #5001). &lt;strong&gt;Before:&lt;/strong&gt; an explicit &lt;code dir=&quot;auto&quot;&gt;--target develop&lt;/code&gt; lost to the stale target in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, so a crashed consolidation resumed onto &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, and resuming with a non-default target could be blocked. &lt;strong&gt;After:&lt;/strong&gt; the target has one persisted source of truth with the order &lt;code dir=&quot;auto&quot;&gt;--target&lt;/code&gt;, then the persisted value, then &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;. Resume honors it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt; no longer frees the lock of another consolidation that is still running&lt;/strong&gt; (#4996, #5001). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt;, the remedy that the lock error prints, could remove the global lock of a live consolidation. &lt;strong&gt;After:&lt;/strong&gt; the lock carries an owner token, and &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; frees only its own lock.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission no longer runs &lt;code dir=&quot;auto&quot;&gt;reset --hard&lt;/code&gt; over your uncommitted planning files&lt;/strong&gt; (#4978, #5001). &lt;strong&gt;Before:&lt;/strong&gt; the dirty-checkout check assumed every mission used coordination topology, so uncommitted edits to &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;traces/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;decisions/&lt;/code&gt; and the status log were treated as coordination residue and destroyed with exit 0. &lt;strong&gt;After:&lt;/strong&gt; the check follows the mission’s actual topology.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement WP##&lt;/code&gt; in a teammate’s clone no longer starts a fresh lane when the lane exists only on the remote&lt;/strong&gt; (#4969, #5001). &lt;strong&gt;Before:&lt;/strong&gt; the lane branch was cut from local &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, so a teammate’s approved work package (WP) code was silently missing and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; still marked it &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; lane identity is stable and checks the remote branch first.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt; no longer erase a reviewer’s reopen when repairing a &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; commit left behind by a failed consolidation&lt;/strong&gt; (#4973, #5001). &lt;strong&gt;Before:&lt;/strong&gt; after a coordination consolidation that failed late, both commands ran a broad revert that could erase a work package (WP) reopen from &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, so the WP shipped as &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the repair reverts only the commits it recorded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;consolidate --resume&lt;/code&gt; advice for a checkout that lags behind its HEAD no longer suggests a commit that reverts the consolidation&lt;/strong&gt; (#4982, #5001). &lt;strong&gt;Before:&lt;/strong&gt; the advice suggested committing the staged deletions, which reverts the consolidation. &lt;strong&gt;After:&lt;/strong&gt; it no longer suggests that commit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The default squash &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer silently reverts newer changes on the target branch&lt;/strong&gt; (#4892). &lt;strong&gt;Before:&lt;/strong&gt; it ran &lt;code dir=&quot;auto&quot;&gt;git merge --squash -X theirs&lt;/code&gt;, so a same-hunk source conflict was resolved in the mission’s favor and consolidation went on to finish the work packages (WPs) and remove the lanes with exit 0. &lt;strong&gt;After:&lt;/strong&gt; squash uses normal three-way rules and refuses on an unresolved content conflict before committing or moving the target branch. Edits to different hunks still combine, and registered merge drivers still decide their own paths. &lt;code dir=&quot;auto&quot;&gt;consolidate --dry-run&lt;/code&gt; and the real run both report &lt;code dir=&quot;auto&quot;&gt;TARGET_BRANCH_CONTENT_CONFLICT&lt;/code&gt; with the conflicting paths and remediation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --resume&lt;/code&gt; no longer mistakes a conflict for an “already merged” branch&lt;/strong&gt; (#4892). &lt;strong&gt;Before:&lt;/strong&gt; a conflict whose path contained the word “already” could be read as an already-merged branch and slip through to marking work packages (WPs) &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; and cleanup. &lt;strong&gt;After:&lt;/strong&gt; the conflict is carried as structured data and always refuses.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A squash &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; whose conflicts all resolve to the target is reported as a no-op, and a failing &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; returns a JSON error instead of a traceback&lt;/strong&gt; (#4892). &lt;strong&gt;Before:&lt;/strong&gt; the first produced an empty squash commit, and the second printed a traceback.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --abort&lt;/code&gt; on a mission with no active consolidation no longer records a fake completion or deletes the mission’s live coordination worktree&lt;/strong&gt; (#4863, #4765). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidate --abort --mission &amp;#x3C;slug&gt;&lt;/code&gt; with no consolidation state treated a resolvable mission handle as proof of an active one. It printed “No active merge state found … Workspace cleaned up” and exited 0. It also committed a retrospective to the target branch and removed the coordination worktree. &lt;strong&gt;After:&lt;/strong&gt; the destructive path runs only when consolidation state exists. With none, abort may clean genuinely orphaned scratch files but leaves the target branch, ledger, retrospective and coordination worktree untouched, and prints “Coordination workspace left unchanged.” A real abort still tears down the coordination topology but is no longer recorded as a successful completion.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A consolidated coordination-topology mission keeps its full status history, so no manual backfill is needed&lt;/strong&gt; (#4787). &lt;strong&gt;Before:&lt;/strong&gt; consolidating a coordination-topology mission whose status log was upgraded at consolidation time wrote the backfilled status rows only to the coordination branch. That branch is removed afterward, so the mission on your target branch was missing those rows and the backfill check failed with “subtasks mismatch (deterministic seed missing)”. &lt;strong&gt;After:&lt;/strong&gt; consolidation copies those rows onto your target branch’s status log as well. The copy is best-effort and never stops a consolidation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;coordination-topology-missions&quot;&gt;Coordination-topology missions&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; on a coordination-topology mission whose coordination worktree is missing now refuses with the fix instead of crashing&lt;/strong&gt; (#5399). &lt;strong&gt;Before:&lt;/strong&gt; when the coordination branch existed but its worktree had never been checked out, &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; stopped with a raw &lt;code dir=&quot;auto&quot;&gt;CoordinationWorktreeUnmaterialized&lt;/code&gt; traceback. &lt;strong&gt;After:&lt;/strong&gt; the acceptance gate records &lt;code dir=&quot;auto&quot;&gt;acceptance_matrix_cannot_evaluate&lt;/code&gt; with the error code &lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_UNMATERIALIZED&lt;/code&gt; and how to fix it, and acceptance refuses. Accepting a mission that has an approved planning lane in the repository root checkout no longer crashes either.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Claiming a work package no longer refuses when a coordination-topology mission still carries a legacy &lt;code dir=&quot;auto&quot;&gt;mission-events.jsonl&lt;/code&gt;&lt;/strong&gt; (#5151). &lt;strong&gt;Before:&lt;/strong&gt; on a coordination-topology mission where a retained copy of &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/mission-events.jsonl&lt;/code&gt; (legacy observability) in your checkout coexisted with the newer coordination-owned event stream, the claim preflight in &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; saw the split stream as unexpected dirty planning state and refused, with no clean way forward. &lt;strong&gt;After:&lt;/strong&gt; the claim guard ignores only an untracked &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/mission-events.jsonl&lt;/code&gt; under coordination topology. It never merges, deletes, rewrites, stages or commits either event stream. Staged or unstaged edits to a tracked copy of the event file, structural planning edits and unrelated dirty files still block the claim. Missions on other topologies are unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate --dry-run&lt;/code&gt; no longer crashes when the coordination worktree is not checked out&lt;/strong&gt; (#5110). &lt;strong&gt;Before:&lt;/strong&gt; the preview raised a raw &lt;code dir=&quot;auto&quot;&gt;CoordinationWorktreeUnmaterialized&lt;/code&gt; traceback, and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; printed no JSON. &lt;strong&gt;After:&lt;/strong&gt; the dry run exits 1 with the same remediation the real consolidation prints, and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; emits a valid error object carrying &lt;code dir=&quot;auto&quot;&gt;error_code: COORDINATION_WORKTREE_UNMATERIALIZED&lt;/code&gt;. A deleted coordination branch is handled the same way, with &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_DELETED&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination --fix&lt;/code&gt; no longer sends you back to itself when the coordination branch exists only on the remote&lt;/strong&gt; (#5258). &lt;strong&gt;Before:&lt;/strong&gt; when the missing-worktree finding carried no coordination-branch detail, the fixer passed on the refusal’s own advice, “fetch, then run &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt;”. After a fetch the branch is still not a local head, so the same command refused again, and the advice never mentioned &lt;code dir=&quot;auto&quot;&gt;git branch &amp;#x3C;b&gt; origin/&amp;#x3C;b&gt;&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the fixer uses the branch named in the refusal and prints the ordered fetch, branch and fix steps. A local branch that still cannot be checked out keeps the generic advice to create the worktree now.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination --fix&lt;/code&gt; no longer flattens a live coordination mission when your clone cannot see the remote coordination branch&lt;/strong&gt; (#4979). This applies to a &lt;code dir=&quot;auto&quot;&gt;git clone --single-branch&lt;/code&gt;, a &lt;code dir=&quot;auto&quot;&gt;--depth 1&lt;/code&gt; or CI clone, or a pruned origin ref. &lt;strong&gt;Before:&lt;/strong&gt; the branch check looked only at local refs and reported the branch as deleted although it still existed on origin, so &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt; dropped &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and demoted &lt;code dir=&quot;auto&quot;&gt;topology: coord&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;. Once pulled, teammates’ missions flattened too: approved work packages (WPs) read &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the check also asks the remote (&lt;code dir=&quot;auto&quot;&gt;git ls-remote&lt;/code&gt;), and an unreachable remote counts as “branch exists”. &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; re-checks the remote first and refuses without touching &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, telling you to run &lt;code dir=&quot;auto&quot;&gt;git fetch&lt;/code&gt;. A repository with no remotes still reports a deleted branch as absent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; now refuses to auto-commit a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; change that drops &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt;&lt;/strong&gt; (#4979). &lt;strong&gt;Before:&lt;/strong&gt; the planning-artifact auto-commit carried a flattened &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; to the target branch, which spread the demotion to every teammate. &lt;strong&gt;After:&lt;/strong&gt; the commit is refused. A first commit and ordinary edits that do not demote the topology are unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The second work package (WP) on a coordination-topology mission can now start&lt;/strong&gt; (#4905). &lt;strong&gt;Before:&lt;/strong&gt; the lifecycle commit (claim, resume, review claim) staged &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/tasks/WP*.md&lt;/code&gt; onto the coordination branch. Every later lane then hit an add/add conflict (&lt;code dir=&quot;auto&quot;&gt;PlanningCommitMergeConflictError&lt;/code&gt;), so the second WP could not start. &lt;strong&gt;After:&lt;/strong&gt; WP files go to the target branch, and the coordination branch no longer carries &lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review feedback and review verdicts are no longer silently dropped when a mission’s status directory does not exist&lt;/strong&gt; (#5180). &lt;strong&gt;Before:&lt;/strong&gt; when the repository-root search landed on a foreign enclosing checkout (a mission in a non-git directory inside another repository), the implement/fix prompt and the &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; verdict read looked at a missing event log. A rejected work package (WP) was re-rendered without its reviewer feedback, and an existing verdict was treated as absent. &lt;strong&gt;After:&lt;/strong&gt; these reads fall back to the mission’s own directory. A deleted coordination branch, or a coordination worktree that has not been created, still raises an error.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer stop on a drifted &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;&lt;/strong&gt; (#5160, #4955). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; is a snapshot derived from &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;. When it diverged on both sides of a merge, the event log merged cleanly but the snapshot conflicted. Lane allocation failed with “cannot auto-merge the recorded planning commit / dependency lane”, and consolidation refused, with no fix you could apply. &lt;strong&gt;After:&lt;/strong&gt; when &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; is the only remaining conflict, both commands regenerate it from the merged event log and continue. A conflict in human-authored content (a &lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt; file, a source file) still stops the command, as does a missing event log. Known limitation: union drivers for &lt;code dir=&quot;auto&quot;&gt;mission-events.jsonl&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl&lt;/code&gt;, and the &lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt; re-fold, are not done yet (#4955).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent context resolve --action tasks&lt;/code&gt; (and the other planning actions) now reports the same &lt;code dir=&quot;auto&quot;&gt;mission_dir&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt;&lt;/strong&gt; (#5160, #2017, #2101). &lt;strong&gt;Before:&lt;/strong&gt; on a coordination-topology mission, &lt;code dir=&quot;auto&quot;&gt;context resolve&lt;/code&gt; returned the coordination-worktree directory while &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; used the repository root checkout. An agent that wrote tasks at the reported path wrote to the wrong place, and &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; found an empty &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; directory. &lt;strong&gt;After:&lt;/strong&gt; the planning actions (&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;tasks_outline&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks_packages&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks_finalize&lt;/code&gt;) report the repository root checkout path (the legacy alias &lt;code dir=&quot;auto&quot;&gt;feature_dir&lt;/code&gt; carries the same path). Status-reading actions (&lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;analyze&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;) still report the coordination worktree.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The error for a coordination worktree that has not been created yet now names a command that creates it&lt;/strong&gt; (#5113). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;CoordinationWorktreeUnmaterialized&lt;/code&gt; advised &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces --fix&lt;/code&gt;, which only removes stale registrations and cannot create a worktree. &lt;strong&gt;After:&lt;/strong&gt; the message names &lt;code dir=&quot;auto&quot;&gt;git -C &amp;#x3C;repo&gt; worktree add &amp;#x3C;coord-worktree&gt; &amp;#x3C;coord-branch&gt;&lt;/code&gt;, for both the local-branch and remote-only cases, and says that &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; cannot create the worktree.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;decision open&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;defer&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;cancel&lt;/code&gt; no longer partly write the decision ledger and then fail on a new coordination-topology mission&lt;/strong&gt; (#5113). &lt;strong&gt;Before:&lt;/strong&gt; when the coordination branch existed but its worktree was not created yet, these commands could write part of the ledger and then fail. &lt;strong&gt;After:&lt;/strong&gt; each command creates the coordination worktree before writing, and fails with nothing written only if that step fails.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination --mission &amp;#x3C;slug&gt; --fix&lt;/code&gt; now creates a missing coordination worktree&lt;/strong&gt; (#5113). &lt;strong&gt;Before:&lt;/strong&gt; the remedy named in the error did not create it. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; creates it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tracer-append&lt;/code&gt; no longer overwrites a teammate’s tracer file when the coordination worktree is not checked out&lt;/strong&gt; (#4959, #4966, #5002). &lt;strong&gt;Before:&lt;/strong&gt; on a coordination-topology mission in a fresh clone, on a CI runner or after the worktree was removed, the read fell through to an empty document and &lt;code dir=&quot;auto&quot;&gt;tracer-append&lt;/code&gt; committed a from-scratch header over a populated &lt;code dir=&quot;auto&quot;&gt;traces/&amp;#x3C;category&gt;.md&lt;/code&gt;, losing every earlier finding, with exit 0. &lt;strong&gt;After:&lt;/strong&gt; the read raises a typed error that says how to create the worktree. &lt;code dir=&quot;auto&quot;&gt;tracer-append&lt;/code&gt; refuses and leaves the file untouched, and it also refuses a file it cannot decode.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The decision ledger and &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; no longer get stuck when the coordination worktree is not checked out&lt;/strong&gt; (#4959, #4966). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;decision open&lt;/code&gt; read a copy of the ledger that held only status files and returned &lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_FOUND&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; could stay blocked on a clarification marker with no CLI way out. &lt;strong&gt;After:&lt;/strong&gt; the ledger and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; read the same authoritative copy, so a resolved decision is visible to &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;. Known limitation: reconciling the decision ledger across both places is tracked separately (#5023).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer dies with a raw traceback when the coordination worktree is not checked out&lt;/strong&gt; (#4959, #4966, #5002). &lt;strong&gt;Before:&lt;/strong&gt; it crashed with a traceback. &lt;strong&gt;After:&lt;/strong&gt; it stops before changing anything and prints the same create-the-worktree remedy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Coordination-branch writes no longer overwrite committed issue-matrix rows&lt;/strong&gt; (#4970). &lt;strong&gt;Before:&lt;/strong&gt; a local coordination branch with no worktree that already carried committed issue-matrix rows was treated as a first write and overwritten. &lt;strong&gt;After:&lt;/strong&gt; the write is refused when the coordination branch already holds committed matrix content.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;issue-verdict&lt;/code&gt; no longer writes through a degraded read&lt;/strong&gt; (#4970). &lt;strong&gt;Before:&lt;/strong&gt; it found its write location through a read path that could fall back to a default. &lt;strong&gt;After:&lt;/strong&gt; it uses a write path that refuses instead of falling back.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination --fix&lt;/code&gt; no longer fast-forwards the wrong branch and reports success&lt;/strong&gt; (#4950, #4920). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; ran &lt;code dir=&quot;auto&quot;&gt;git merge --ff-only &amp;#x3C;target&gt;&lt;/code&gt; in the coordination worktree without checking which branch was checked out there. If someone had checked out another branch, or left a detached HEAD, &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; fast-forwarded that branch, reported success with exit 0, while the coordination branch stayed stale and &lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_BRANCH_MISMATCH&lt;/code&gt; kept appearing. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; first refuses, with &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_STALE_FIX_BLOCKED&lt;/code&gt; and exit 1, if the worktree is on another branch, detached, or not a worktree of this repository. It prints &lt;code dir=&quot;auto&quot;&gt;Fast-forwarded&lt;/code&gt; only after re-reading the coordination branch and confirming it matches the target; otherwise it reports the new &lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_STALE_FIX_POSTCONDITION_FAILED&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A fast-forward that git rejects during &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt; is now reported as a finding&lt;/strong&gt; (#4950). Other missions in the same run are still repaired.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The strand repair in &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; no longer reverts on the wrong branch&lt;/strong&gt; (#4950). &lt;strong&gt;Before:&lt;/strong&gt; after a rolled-back consolidation, the repair of a stranded &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; commit ran on whatever branch was checked out, reported the strand healed, and stopped reporting it. &lt;strong&gt;After:&lt;/strong&gt; it refuses on the wrong branch and keeps reporting the strand until it is really repaired.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty retrospect create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;retrospect backfill&lt;/code&gt; now warn when the retrospective auto-commit fails&lt;/strong&gt; (#5353). &lt;strong&gt;Before:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;auto_commit&lt;/code&gt; on, a failed &lt;code dir=&quot;auto&quot;&gt;git add&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt; was swallowed without a word, so the operator believed the retrospective record was committed when it was not. This happens on every coordination-topology mission, where the canonical event log sits in the git-ignored coordination worktree, and whenever a hook rejects the commit. &lt;strong&gt;After:&lt;/strong&gt; the command still succeeds (the record is on disk), but prints a &lt;code dir=&quot;auto&quot;&gt;Warning: retrospective auto-commit failed: &amp;#x3C;git&apos;s reason&gt;&lt;/code&gt; line on stderr naming the files to commit by hand; &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; stdout stays parseable.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;review-loop-and-verdicts&quot;&gt;Review loop and verdicts&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; resumes a work package after a reviewer’s rework verdict without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;&lt;/strong&gt; (#5377, #5196). &lt;strong&gt;Before:&lt;/strong&gt; after a reviewer’s unforced &lt;code dir=&quot;auto&quot;&gt;in_review → in_progress&lt;/code&gt; rejection, &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; exited 1 (&lt;code dir=&quot;auto&quot;&gt;WorkPackageClaimConflict&lt;/code&gt;) for the implementer, because the slot held the reviewer. &lt;strong&gt;After:&lt;/strong&gt; the implementer of record resumes as a no-op, with no &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; and no event written. An unrelated agent is still refused, and if the implementer of record cannot be read, the old refusal applies. &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; follows the same rule, and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api start-implementation&lt;/code&gt; returns &lt;code dir=&quot;auto&quot;&gt;no_op: true&lt;/code&gt; for the implementer instead of &lt;code dir=&quot;auto&quot;&gt;WP_ALREADY_CLAIMED&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An ordinary review loop (reject, rework, resubmit, approve) no longer needs &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;&lt;/strong&gt; (#5196). &lt;strong&gt;Before:&lt;/strong&gt; after a reviewer rejected a work package (WP), the ownership check refused the implementer’s resume and resubmission, and refused the reviewer’s claim or approval of the reworked WP the same way. &lt;strong&gt;After:&lt;/strong&gt; the WP’s latest implementer resumes and resubmits with its own &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt; and no &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;. Any named agent whose tool differs from the latest implementer’s can claim, approve or reject from &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;; a generic identity such as &lt;code dir=&quot;auto&quot;&gt;user&lt;/code&gt; never counts as a reviewer. &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; verdicts stay with the review-claim holder, and an unrelated agent is still refused. The shipped implement-review and runtime-review skills and the review how-to show the unforced commands. The ownership check compares agent tools only, so it guards against accidents, not same-tool self-review.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The review history no longer records a fake arbiter override for a forced rework resubmission&lt;/strong&gt; (#5196). &lt;strong&gt;Before:&lt;/strong&gt; every forced rework resubmission was recorded as an arbiter override, so the history showed &lt;code dir=&quot;auto&quot;&gt;Cycle N: rejected → overridden&lt;/code&gt; for a verdict nobody overrode, while a real arbiter override after an &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; rejection went unrecorded. &lt;strong&gt;After:&lt;/strong&gt; an arbiter override is recorded only for a forced &lt;code dir=&quot;auto&quot;&gt;planned → approved&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; after a rejection from either &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt;. Forced moves to &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; are no longer classified as overrides.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; no longer passes on an acceptance matrix that a concurrent verdict just changed to failing&lt;/strong&gt; (#4974, #4887). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; read &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt;, ran its checks, then wrote its stale snapshot back without a lock. A verdict recorded at the same moment by &lt;code dir=&quot;auto&quot;&gt;agent mission acceptance-verdict&lt;/code&gt; was erased, and accept could pass on a matrix that no longer said pass. &lt;strong&gt;After:&lt;/strong&gt; every accept and verdict update of the matrix goes through one locked path. &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; judges the fresh matrix and re-checks the verdict under the lock right before it stamps &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;. A lock timeout stops the command with exit 1.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orchestrator &lt;code dir=&quot;auto&quot;&gt;accept-mission&lt;/code&gt; now refuses to record acceptance when the mission is not ready&lt;/strong&gt; (#4934). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;accept-mission&lt;/code&gt; never read the readiness verdict, so it recorded acceptance over outstanding or failing checks. &lt;strong&gt;After:&lt;/strong&gt; it refuses with &lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_READY&lt;/code&gt;, listing the outstanding, activity, skipped and blocked checks, and records no acceptance. This includes a malformed matrix.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Rejecting a work package from &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; back to &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt; now keeps the feedback&lt;/strong&gt; (#4899). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; reported success but discarded the feedback. It wrote no review-cycle record, left the feedback path empty, and left behind a reference that could not be resolved. It also accepted a rejection with no rationale. The &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; edge already worked. &lt;strong&gt;After:&lt;/strong&gt; both rejection edges write a committed review-cycle record, a feedback path and a resolvable &lt;code dir=&quot;auto&quot;&gt;review-cycle://&lt;/code&gt; reference. A rejection without a rationale is refused, and the message names the target edge.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The regenerated implement prompt now shows the reviewer’s rejection feedback, including on coordination-topology missions&lt;/strong&gt; (#5024). &lt;strong&gt;Before:&lt;/strong&gt; on a coordination-topology mission the prompt read the event log from the wrong branch and said no feedback existed. Any failure while generating a fix-mode prompt also fell back to a prompt without feedback, with no signal. &lt;strong&gt;After:&lt;/strong&gt; the feedback appears in the regenerated prompt on &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; and coordination-topology missions. A fix-mode prompt failure now prints a visible warning.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A reviewer’s rejection is no longer overwritten by a concurrent stale approval, so rejected code is no longer consolidated&lt;/strong&gt; (#4990, spec-kitty/spec-kitty-events#69). &lt;strong&gt;Before:&lt;/strong&gt; the code that works out a work package’s current state from the event log kept whichever event had the later wall-clock time. If two reviewers worked on one work package (WP) from two checkouts, a reject (&lt;code dir=&quot;auto&quot;&gt;in_review -&gt; planned&lt;/code&gt;) followed by a later-timestamped stale approve reduced to &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; after a pull. &lt;code dir=&quot;auto&quot;&gt;status validate&lt;/code&gt; passed and the consolidation shipped the rejected implementation with exit 0. &lt;strong&gt;After:&lt;/strong&gt; the CLI requires &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&gt;=10.4.0,&amp;#x3C;11&lt;/code&gt; (was &lt;code dir=&quot;auto&quot;&gt;&gt;=9,&amp;#x3C;10&lt;/code&gt;). The newer version keeps the committed rejection regardless of timestamp. A genuine reject, rework, approve sequence is unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --audit&lt;/code&gt; no longer raises a blocking error for a mission whose snapshot differs only in provenance&lt;/strong&gt; (#4990). &lt;strong&gt;Before:&lt;/strong&gt; the newer &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; release re-derives who last changed each work package (&lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;last_event_id&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;last_transition_at&lt;/code&gt;) for missions with &lt;code dir=&quot;auto&quot;&gt;verdict_provenance_backfill&lt;/code&gt; events, without changing any lane. An archived mission’s committed &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; then raised a blocking &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; that could not be fixed. &lt;strong&gt;After:&lt;/strong&gt; when only those three fields differ, the audit reports a non-blocking &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT_PROVENANCE&lt;/code&gt; warning. Any drift in a lane, count or other field still raises &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next --result success&lt;/code&gt; no longer loops forever after a review is rejected&lt;/strong&gt; (#4980). &lt;strong&gt;Before:&lt;/strong&gt; after a rejection (&lt;code dir=&quot;auto&quot;&gt;move-task &amp;#x3C;wp&gt; --to planned&lt;/code&gt;), every later &lt;code dir=&quot;auto&quot;&gt;next --result success&lt;/code&gt; returned &lt;code dir=&quot;auto&quot;&gt;kind=step action=review wp_id=null&lt;/code&gt; (“Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; to advance”) with exit 0, indefinitely. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; reads the same finalized task board that query mode uses and dispatches &lt;code dir=&quot;auto&quot;&gt;implement &amp;#x3C;wp&gt;&lt;/code&gt; for the rejected work package (WP) on every topology. When the board has no actionable WP (all in review, or a coordination worktree that has not been created), it returns &lt;code dir=&quot;auto&quot;&gt;kind=blocked&lt;/code&gt; with a runnable &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; recovery command instead of the empty placeholder.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Concurrent &lt;code dir=&quot;auto&quot;&gt;acceptance-verdict&lt;/code&gt; calls no longer lose each other’s rows&lt;/strong&gt; (#4858). &lt;strong&gt;Before:&lt;/strong&gt; the command read the matrix, ran its slow check that something is absent, then wrote the whole matrix back with no lock. Two concurrent calls for different entries lost a committed row, and &lt;code dir=&quot;auto&quot;&gt;overall_verdict&lt;/code&gt; could flip from &lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;pass&lt;/code&gt;, both exiting 0, on &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; and coordination-topology missions. &lt;strong&gt;After:&lt;/strong&gt; the command re-reads the matrix inside a lock, updates only its own row, and writes and commits under that lock, with the slow check outside it. It never resets an already-judged absence check to &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt;. On a lock timeout it refuses with a non-zero exit instead of writing without the lock. &lt;code dir=&quot;auto&quot;&gt;overall_verdict&lt;/code&gt; comes from the re-read matrix, and the matrix file is written atomically so no reader sees a partial file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;issue-verdict&lt;/code&gt; no longer drops earlier verdicts when it migrates a legacy &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; on a coordination mission&lt;/strong&gt; (#4868). &lt;strong&gt;Before:&lt;/strong&gt; on the first JSON write it migrated the legacy matrix from the repository root checkout instead of the authoritative coordination copy. Recording one issue produced a matrix containing only that issue, and all earlier verdicts vanished from active state. &lt;strong&gt;After:&lt;/strong&gt; it reads the legacy matrix from the authoritative coordination copy and keeps the existing rows before adding the new issue. A malformed matrix now fails with a structured error instead of dropping rows.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Concurrent &lt;code dir=&quot;auto&quot;&gt;issue-verdict&lt;/code&gt; calls no longer lose each other’s verdicts&lt;/strong&gt; (#4884). &lt;strong&gt;Before:&lt;/strong&gt; two concurrent calls for different issues each read the whole row set, added their own issue and wrote it back, so the later writer dropped the earlier verdict. &lt;strong&gt;After:&lt;/strong&gt; the command re-reads the issue matrix inside the same lock, updates only its own issue, and writes and commits under the lock. It refuses on a lock timeout, and the file is written atomically.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A merge (a plain &lt;code dir=&quot;auto&quot;&gt;git merge&lt;/code&gt; or a consolidation) that touches a mission’s &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt; no longer silently flips an accepted verdict to &lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt;&lt;/strong&gt; (#4880). &lt;strong&gt;Before:&lt;/strong&gt; when both sides changed a field of the same row (for example &lt;code dir=&quot;auto&quot;&gt;pass_fail&lt;/code&gt;), the row-aware merge driver wrote a git-style conflict marker as the field’s value and let the merge finish. The verdict calculation then read that marker and set &lt;code dir=&quot;auto&quot;&gt;overall_verdict&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt;. In the issue matrix, the marker corrupted the row’s values. &lt;strong&gt;After:&lt;/strong&gt; the merge stops only when two lanes recorded different authored verdicts (for example &lt;code dir=&quot;auto&quot;&gt;pass&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt;). An unset placeholder (&lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;) yields to the authored value, and other fields prefer the target, so ordinary lane consolidations are unaffected. The review-cycle &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt; prose is unchanged.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;charter-doctrine-and-project-languages&quot;&gt;Charter, doctrine and project languages&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Projects in a language Spec Kitty does not recognize are no longer labeled Python&lt;/strong&gt; (#5284, #4613). &lt;strong&gt;Before:&lt;/strong&gt; an interview answer such as “Zig 0.16.0 is the primary implementation language” produced no language signal, which admitted every language-scoped guide, so a Zig project’s mission context listed Python conventions and review checks (or &lt;code dir=&quot;auto&quot;&gt;Languages: python&lt;/code&gt; from a stale value). &lt;strong&gt;After:&lt;/strong&gt; a declared but unrecognized language is recorded as &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;. Mission context lists only language-neutral doctrine, shows &lt;code dir=&quot;auto&quot;&gt;Languages: unknown&lt;/code&gt;, and adds one advisory line pointing to the new how-to &lt;em&gt;Extend your charter for an unsupported language&lt;/em&gt;. Projects whose language has no installed specialist guidance, including Rust, Swift and Ruby, see the advisory too, while &lt;code dir=&quot;auto&quot;&gt;Languages:&lt;/code&gt; still shows the recorded value. Interviews that declare no language behave as before.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Your languages/frameworks interview answer alone now decides your project’s languages&lt;/strong&gt; (#5284). &lt;strong&gt;Before:&lt;/strong&gt; words in other answers, such as &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt; in a testing answer, could override it. &lt;strong&gt;After:&lt;/strong&gt; they no longer do.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A language name inside a hyphenated compound (&lt;code dir=&quot;auto&quot;&gt;librespot-java&lt;/code&gt;) no longer activates that language&lt;/strong&gt; (#5284).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An unregistered &lt;code dir=&quot;auto&quot;&gt;available_tools&lt;/code&gt; entry is now reported as a tool id, not mistaken for a language&lt;/strong&gt; (#5284).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Correcting your interview answer and regenerating now updates the project’s languages&lt;/strong&gt; (#4614). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;catalog.languages&lt;/code&gt; was read back from the existing &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; as authoritative, so a wrong first inference survived every &lt;code dir=&quot;auto&quot;&gt;charter generate --from-interview&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter generate --from-interview&lt;/code&gt; (the default) and &lt;code dir=&quot;auto&quot;&gt;charter activate --resynthesize&lt;/code&gt; re-derive languages from the current answers, replacing a hand-edited value. &lt;code dir=&quot;auto&quot;&gt;--no-from-interview&lt;/code&gt;, a plain &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; and pack recompiles keep the recorded value, and runtime reads still prefer the compiled charter.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission context no longer lists other languages’ guidance for a project in a recognized language&lt;/strong&gt; (#5357). &lt;strong&gt;Before:&lt;/strong&gt; a Rust project’s context still listed Python- and TypeScript-specific guides, because the action doctrine walk ignored language scope. &lt;strong&gt;After:&lt;/strong&gt; guides scoped to other languages are dropped for any declared language. Projects that declare no language are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter lint&lt;/code&gt; no longer reports the built-in &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_052&lt;/code&gt; (“Prefer Durable Fixes”) as orphaned&lt;/strong&gt; (#5258). &lt;strong&gt;Before:&lt;/strong&gt; the directive had only outgoing links, so every install that ran &lt;code dir=&quot;auto&quot;&gt;charter lint&lt;/code&gt; got an orphan finding for a directive it had not authored. &lt;strong&gt;After:&lt;/strong&gt; the built-in &lt;code dir=&quot;auto&quot;&gt;disciplined-defect-diagnosis&lt;/code&gt; procedure suggests &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_052&lt;/code&gt;. The link is a suggestion, so activating the procedure activates &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_052&lt;/code&gt; only when you pass &lt;code dir=&quot;auto&quot;&gt;--cascade&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 charter activate&lt;/code&gt;’s recovery hint now names the real &lt;code dir=&quot;auto&quot;&gt;charter pack consistency-check&lt;/code&gt; command&lt;/strong&gt; (#5267, #5266). &lt;strong&gt;Before:&lt;/strong&gt; when activation left referenced artifacts un-cascaded, the hint told you to run &lt;code dir=&quot;auto&quot;&gt;charter consistency-check&lt;/code&gt;, which is not a command, so following it hit &lt;code dir=&quot;auto&quot;&gt;No such command&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the hint names &lt;code dir=&quot;auto&quot;&gt;charter pack consistency-check&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Generated charter catalogs no longer pin the built-in template-set path to the checkout that generated them&lt;/strong&gt; (#5253). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; stored an absolute path to the generating checkout, so another checkout could not collect the bundled analysis inputs. &lt;strong&gt;After:&lt;/strong&gt; new output stores &lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_PACKS_ROOT}/built-in/missions/&amp;#x3C;mission&gt;/mission.yaml&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor provenance&lt;/code&gt; reports legacy absolute paths.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Built-in prompts and templates no longer tell agents to run commands that do not exist&lt;/strong&gt; (#5217, #5204). &lt;strong&gt;Before:&lt;/strong&gt; agents that followed the shipped doctrine hit &lt;code dir=&quot;auto&quot;&gt;No such command&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;agent tasks transition&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent mission info&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent mission tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent bulk-edit validate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent workflow implement/review&lt;/code&gt;. The PowerShell toolguide also described wrapper scripts that never existed. &lt;strong&gt;After:&lt;/strong&gt; every &lt;code dir=&quot;auto&quot;&gt;spec-kitty …&lt;/code&gt; command in the built-in pack resolves against the real CLI.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The documentation mission now uses the iteration mode &lt;code dir=&quot;auto&quot;&gt;mission_specific&lt;/code&gt;&lt;/strong&gt; (#5217, #5205). &lt;strong&gt;Before:&lt;/strong&gt; the mission told agents to write &lt;code dir=&quot;auto&quot;&gt;feature_specific&lt;/code&gt;, which the documentation state reader rejected. &lt;strong&gt;After:&lt;/strong&gt; the mode is &lt;code dir=&quot;auto&quot;&gt;mission_specific&lt;/code&gt;. A stored legacy &lt;code dir=&quot;auto&quot;&gt;feature_specific&lt;/code&gt; still reads back as &lt;code dir=&quot;auto&quot;&gt;mission_specific&lt;/code&gt;, without the file being rewritten. Writing an unrecognized iteration mode to the documentation state now raises an error instead of being saved.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Built-in prompts now say “mission” instead of “feature”, and mission commands emit a &lt;code dir=&quot;auto&quot;&gt;mission_dir&lt;/code&gt; key&lt;/strong&gt; (#5217, #5206). &lt;strong&gt;Before:&lt;/strong&gt; prompts used “feature” wording for the mission and read a &lt;code dir=&quot;auto&quot;&gt;feature_dir&lt;/code&gt; key. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt; emit &lt;code dir=&quot;auto&quot;&gt;mission_dir&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;feature_dir&lt;/code&gt; stays as a legacy alias.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; commands now print bracketed tokens such as &lt;code dir=&quot;auto&quot;&gt;[build]&lt;/code&gt; exactly as written&lt;/strong&gt; (#5061, #5130). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; (both &lt;code dir=&quot;auto&quot;&gt;--include tactic:&amp;#x3C;id&gt;&lt;/code&gt; and the action body) and every &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; error message (across all 8 subcommands) ran text through a markup parser, so tokens such as &lt;code dir=&quot;auto&quot;&gt;[build]&lt;/code&gt; were stripped or mangled. &lt;strong&gt;After:&lt;/strong&gt; doctrine text and error messages print with markup disabled or escaped, and the red error label stays styled.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter pack apply --compile&lt;/code&gt; no longer change a non-&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; project’s mission type to &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;&lt;/strong&gt; (#4908). &lt;strong&gt;Before:&lt;/strong&gt; on a project generated with &lt;code dir=&quot;auto&quot;&gt;--mission-type research&lt;/code&gt;, one &lt;code dir=&quot;auto&quot;&gt;charter activate directive &amp;#x3C;id&gt;&lt;/code&gt; recompiled &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;catalog.mission&lt;/code&gt; set to &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;catalog.template_set&lt;/code&gt; set to &lt;code dir=&quot;auto&quot;&gt;software-dev-default&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;catalog.references&lt;/code&gt; cut from 268 to 165 ids. It exited 0 with no notice and no backup, and &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; and dispatch then ran under the wrong governance. &lt;strong&gt;After:&lt;/strong&gt; the recompile reads the recorded mission type from &lt;code dir=&quot;auto&quot;&gt;catalog.mission&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, then from &lt;code dir=&quot;auto&quot;&gt;mission:&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;answers.yaml&lt;/code&gt;, and falls back to &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; only when neither exists. A malformed &lt;code dir=&quot;auto&quot;&gt;answers.yaml&lt;/code&gt; still degrades quietly instead of aborting.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A project agent profile’s cited doctrine now appears in the dispatch capsule and governance context when no organization packs are declared&lt;/strong&gt; (#4912, #4838). &lt;strong&gt;Before:&lt;/strong&gt; in a project with no org packs, &lt;code dir=&quot;auto&quot;&gt;--profile &amp;#x3C;id&gt;&lt;/code&gt; for a profile under &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/agent_profiles/&lt;/code&gt; printed &lt;code dir=&quot;auto&quot;&gt;WARNING  Profile &apos;&amp;#x3C;id&gt;&apos; not found; profile-cited sections omitted&lt;/code&gt; and dropped every cited section, although the profile’s header, governance context and model routing rendered. &lt;strong&gt;After:&lt;/strong&gt; the lookup covers project, org and built-in profiles. Activation now applies without org packs too, so an explicitly de-activated profile (project or built-in) has its cited sections omitted. If you use no &lt;code dir=&quot;auto&quot;&gt;activated_agent_profiles&lt;/code&gt; allowlist, nothing changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The dispatch capsule and governance context now show the same profile-cited sections as &lt;code dir=&quot;auto&quot;&gt;profiles show&lt;/code&gt;, including those a profile inherits through &lt;code dir=&quot;auto&quot;&gt;specializes_from&lt;/code&gt;&lt;/strong&gt; (#4917, #901). &lt;strong&gt;Before:&lt;/strong&gt; a profile that &lt;code dir=&quot;auto&quot;&gt;specializes_from&lt;/code&gt; an abstract base and cited directives or tactics only on that base showed them in &lt;code dir=&quot;auto&quot;&gt;profiles show&lt;/code&gt; but not in the dispatch capsule, so one profile had two different governance contexts. &lt;strong&gt;After:&lt;/strong&gt; every capsule path resolves the inheritance chain the same way, so both match. Only the profile you select is gated by &lt;code dir=&quot;auto&quot;&gt;activated_agent_profiles&lt;/code&gt;: a de-activated ancestor still passes its citations down, so de-activating an abstract base does not strip an active child. A broken chain (missing parent or cycle) falls back to the profile’s own record. Known limitation: the charter-interview profile lookup has the same gap and is left for a follow-up.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Charter activation entries accept the documented &lt;code dir=&quot;auto&quot;&gt;charter.interview&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter.context&lt;/code&gt; actions again&lt;/strong&gt; (#5353). &lt;strong&gt;Before:&lt;/strong&gt; an activation entry with &lt;code dir=&quot;auto&quot;&gt;action: charter.interview&lt;/code&gt;, the form the data model documents and the one that matches &lt;code dir=&quot;auto&quot;&gt;charter.generate&lt;/code&gt;, was rejected as an unknown action. &lt;strong&gt;After:&lt;/strong&gt; the short &lt;code dir=&quot;auto&quot;&gt;charter.interview&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter.context&lt;/code&gt; actions are accepted again. The long &lt;code dir=&quot;auto&quot;&gt;charter.activation.*&lt;/code&gt; spellings, which were never documented, are rejected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Charter reads from inside a git submodule now find the submodule’s own &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt;&lt;/strong&gt; (#5353, #2624, #2011). &lt;strong&gt;Before:&lt;/strong&gt; run from a submodule, charter, bundle and dashboard reads looked for &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt; under the superproject’s &lt;code dir=&quot;auto&quot;&gt;.git/modules&lt;/code&gt; directory, which is neither the submodule nor the superproject. &lt;strong&gt;After:&lt;/strong&gt; a submodule, or a linked worktree of one, resolves to the submodule’s working tree (what &lt;code dir=&quot;auto&quot;&gt;git rev-parse --show-toplevel&lt;/code&gt; prints there). Plain checkouts and their linked worktrees are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; no longer silently drops activated references that language scoping filters out&lt;/strong&gt; (#5429; #5257). &lt;strong&gt;Before:&lt;/strong&gt; a full regeneration left activated ids such as &lt;code dir=&quot;auto&quot;&gt;styleguide/java-conventions&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;toolguide/maven-review-checks&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;java-jenny&lt;/code&gt; agent profile out of &lt;code dir=&quot;auto&quot;&gt;catalog.references&lt;/code&gt; with no message, and the activation-parity guard then failed. &lt;strong&gt;After:&lt;/strong&gt; a scope-filtered reference keeps a placeholder entry in the catalog, and every other unresolved reference is reported with its cause: filtered by language scope, missing artifact, suspected typo, malformed or unattributable reference, or graph load failure. &lt;code dir=&quot;auto&quot;&gt;charter generate --json&lt;/code&gt; gains an always-present &lt;code dir=&quot;auto&quot;&gt;unresolved_references&lt;/code&gt; list, which is &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; when everything resolves.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; now fails when none of a doctrine kind’s activated references resolve&lt;/strong&gt; (#5429; #5257). &lt;strong&gt;Before:&lt;/strong&gt; it wrote an empty section for that kind and exited 0. &lt;strong&gt;After:&lt;/strong&gt; it exits non-zero, names the kind, and still lists the records in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;unresolved_references&lt;/code&gt;. This also applies to a kind reached only through other artifacts. &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter deactivate&lt;/code&gt; keep your config change and print a “Catalog not recompiled” notice naming the kind. &lt;code dir=&quot;auto&quot;&gt;charter pack apply --compile&lt;/code&gt; exits 1 with a clear error instead of a traceback.&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; no longer passes its preflight when the automatic charter refresh fails&lt;/strong&gt; (#5429; #5257). &lt;strong&gt;Before:&lt;/strong&gt; a failed or crashed &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; during the references-parity auto-refresh was ignored, and the preflight reported success. &lt;strong&gt;After:&lt;/strong&gt; the preflight is blocked, with a reason that quotes the real error message.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;files-spec-kitty-no-longer-deletes-or-overwrites&quot;&gt;Files Spec Kitty no longer deletes or overwrites&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent config sync --sync-hooks&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;live-work install&lt;/code&gt; no longer wipe a non-UTF-8 &lt;code dir=&quot;auto&quot;&gt;.claude/settings.json&lt;/code&gt;&lt;/strong&gt; (#4940). &lt;strong&gt;Before:&lt;/strong&gt; a settings file saved as cp1252, Latin-1, UTF-16 or UTF-32 was silently read as empty and overwritten, losing permissions (including deny rules), env and every hook entry, with no backup and exit 0. &lt;strong&gt;After:&lt;/strong&gt; an encoding is used only when it can be proven (a byte-order mark, or strict UTF-8). A provably non-UTF-8 file is decoded, merged, backed up byte-for-byte to a &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;path&gt;.&amp;#x3C;timestamp&gt;&lt;/code&gt; sidecar, then rewritten as UTF-8. A file whose encoding cannot be proven is left untouched, and the command raises &lt;code dir=&quot;auto&quot;&gt;SettingsNotDecodableError&lt;/code&gt;, exits non-zero and names the file with the fix “re-save it as UTF-8”. The same check also fixes a UTF-32 mis-decode in charter encoding recovery.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate charter-encoding&lt;/code&gt; no longer corrupts a legacy Windows-1252 charter&lt;/strong&gt; (#4962). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;migrate charter-encoding --yes&lt;/code&gt; could decode the charter with the wrong single-byte code page (cp1250 or cp775) at a false “confidence 1.0” and overwrite the file in place with no backup. &lt;code dir=&quot;auto&quot;&gt;José Peña, São Paulo&lt;/code&gt; became &lt;code dir=&quot;auto&quot;&gt;José Peńa, Săo Paulo&lt;/code&gt;, the command exited 0, and a second run reported &lt;code dir=&quot;auto&quot;&gt;already_utf8&lt;/code&gt;, which locked in the damage. &lt;strong&gt;After:&lt;/strong&gt; the command reports an honest confidence and prefers cp1252 among tied candidates, so a Windows-authored charter round-trips byte for byte. It writes a backup of the original bytes before any in-place rewrite. When no cp1252-family code page fits, it exits non-zero and leaves the file untouched, with no backup.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept --normalize-encoding&lt;/code&gt; no longer garbles a mixed-encoding spec or charter&lt;/strong&gt; (#4968). &lt;strong&gt;Before:&lt;/strong&gt; the flag re-decoded the whole file through a fallback chain (cp1252, latin-1, then UTF-8 with replacement). Non-ASCII characters came out garbled or as &lt;code dir=&quot;auto&quot;&gt;�&lt;/code&gt;, with no backup, while the command printed “Normalized”. &lt;strong&gt;After:&lt;/strong&gt; it uses the same detector as &lt;code dir=&quot;auto&quot;&gt;migrate charter-encoding&lt;/code&gt;, with the same backup and refusal behavior. &lt;code dir=&quot;auto&quot;&gt;validate-encoding --fix&lt;/code&gt; is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; centralization migration no longer deletes a shared asset just because it differs from the shipped default&lt;/strong&gt; (#4961, #4792, #4915). &lt;strong&gt;Before:&lt;/strong&gt; a shared asset that differed from the package copy was treated as removable. An outdated default and a team customization look the same by content, so a hand-authored file could be deleted with no backup. &lt;strong&gt;After:&lt;/strong&gt; the migration deletes a file only when it is byte-identical to the shipped one. Any differing file is kept and reported as preserved, including a customized file that merely contains the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-command-version&lt;/code&gt; marker text.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Installing a doctrine pack from a git repository no longer overwrites a pre-existing pack directory&lt;/strong&gt; (#4960). &lt;strong&gt;Before:&lt;/strong&gt; a first install could overwrite a non-empty target directory, such as a hand-authored pack. &lt;strong&gt;After:&lt;/strong&gt; the install refuses a non-empty target up front. It clones into a temporary sibling directory and moves it into place. A failed clone, checkout or move removes only the temporary files this run created, never the target.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Updating a doctrine pack installed from a git repository no longer discards local work&lt;/strong&gt; (#4989). &lt;strong&gt;Before:&lt;/strong&gt; the update ran &lt;code dir=&quot;auto&quot;&gt;git reset --hard&lt;/code&gt;, silently dropping uncommitted changes and local commits ahead of the reset target. &lt;strong&gt;After:&lt;/strong&gt; the update refuses when the working tree is dirty or has commits ahead of the reset target. It also picks the reset target by ref type (&lt;code dir=&quot;auto&quot;&gt;origin/&amp;#x3C;ref&gt;&lt;/code&gt; only for a real remote branch), so tag-pinned and SHA-pinned packs are not moved to the wrong commit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent config remove &amp;#x3C;agent&gt;&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent config sync&lt;/code&gt; no longer delete user-authored command files&lt;/strong&gt; (#4907, #4915). &lt;strong&gt;Before:&lt;/strong&gt; both commands ran an unconditional delete of an agent’s managed directory (for example &lt;code dir=&quot;auto&quot;&gt;.claude/commands/**&lt;/code&gt;, which in 4.x is user-owned and gitignored, so the loss was unrecoverable). &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; did this in its default orphan sweep. &lt;strong&gt;After:&lt;/strong&gt; a directory whose ownership cannot be proven is kept whole and reported as preserved, with exit 0. A directory proven to be manifest-managed is still removed. The output can no longer say “Removed” for something that was preserved.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A normal &lt;code dir=&quot;auto&quot;&gt;agent config sync&lt;/code&gt; no longer rewrites a repository-pinned &lt;code dir=&quot;auto&quot;&gt;command-skills-manifest.json&lt;/code&gt;&lt;/strong&gt; (#2691). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; re-registered already-installed skill agents and rewrote the pinned manifest. &lt;strong&gt;After:&lt;/strong&gt; that step is skipped and pinned release and hash values stay byte-identical. &lt;code dir=&quot;auto&quot;&gt;sync --json&lt;/code&gt; lists each tracked change, and lists none for a &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; that refreshes nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; no longer overwrites your repository’s own &lt;code dir=&quot;auto&quot;&gt;.git/hooks/pre-commit&lt;/code&gt;&lt;/strong&gt; (#4895, #4915). &lt;strong&gt;Before:&lt;/strong&gt; the hook installer replaced any existing hook with no check. That silently disabled your commit-time checks for every commit in the repository, because &lt;code dir=&quot;auto&quot;&gt;.git/hooks&lt;/code&gt; is shared across worktrees. &lt;strong&gt;After:&lt;/strong&gt; a hook that lacks the &lt;code dir=&quot;auto&quot;&gt;# Generated by spec-kitty.&lt;/code&gt; signature is first backed up to a timestamped file, and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; prints the backup path. A hook signed by spec-kitty is replaced as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty intake&lt;/code&gt; no longer overwrites a hand-written &lt;code dir=&quot;auto&quot;&gt;.kittify/mission-brief.md&lt;/code&gt;&lt;/strong&gt; (#4910, #4915). &lt;strong&gt;Before:&lt;/strong&gt; the overwrite check required both the brief and its provenance sidecar to exist, so a hand-written brief with no sidecar was silently replaced. &lt;strong&gt;After:&lt;/strong&gt; the check looks at the brief alone, in both the explicit and the &lt;code dir=&quot;auto&quot;&gt;--auto&lt;/code&gt; paths. A missing sidecar counts as unknown origin, so &lt;code dir=&quot;auto&quot;&gt;intake&lt;/code&gt; refuses without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; and leaves the brief unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;validate-encoding --fix&lt;/code&gt; no longer corrupts the files it claims to repair&lt;/strong&gt; (#4896, #4915). &lt;strong&gt;Before:&lt;/strong&gt; one stray byte triggered a whole-file cp1252 re-decode that garbled every multi-byte character. Binary files named &lt;code dir=&quot;auto&quot;&gt;*.md&lt;/code&gt; were rewritten, and CRLF line endings became LF across the file. All of it was reported &lt;code dir=&quot;auto&quot;&gt;Fixed&lt;/code&gt; with exit 0. &lt;strong&gt;After:&lt;/strong&gt; text and binary are told apart by content, so binaries are skipped. The fallback decode covers only the offending bytes, or the file is refused with the byte offsets. Line endings are preserved, and &lt;code dir=&quot;auto&quot;&gt;Fixed&lt;/code&gt; is reported only for a faithful repair.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Spec Kitty’s automatic commits no longer strand your staged work&lt;/strong&gt; (#4888, #4915). &lt;strong&gt;Before:&lt;/strong&gt; each auto-commit stashed and restored your unrelated staged changes with &lt;code dir=&quot;auto&quot;&gt;git stash push --staged&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;git stash pop --index&lt;/code&gt;. That fails whenever a tracked file is partly staged (an ordinary &lt;code dir=&quot;auto&quot;&gt;git add -p&lt;/code&gt;), leaving your staged work in a stash that cannot be popped. &lt;strong&gt;After:&lt;/strong&gt; the auto-commit commits only the requested paths with &lt;code dir=&quot;auto&quot;&gt;git commit --only&lt;/code&gt; and never touches your index or working tree.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now exits non-zero and names the stash ref and the landed commit SHA when restoring your staged work fails&lt;/strong&gt; (#4888). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; exited 0 with “please commit manually”, although the commit had landed, and never named the stash.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; no longer deletes a hand-authored &lt;code dir=&quot;auto&quot;&gt;.kittify/templates/&lt;/code&gt; directory&lt;/strong&gt; (#4931, #4861). &lt;strong&gt;Before:&lt;/strong&gt; on a project with no &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; treated &lt;code dir=&quot;auto&quot;&gt;.kittify/templates&lt;/code&gt; as package-owned because of its name. It deleted your custom templates with no backup, printed &lt;code dir=&quot;auto&quot;&gt;Project ready&lt;/code&gt; and exited 0. The full-copy template step did the same in both the &lt;code dir=&quot;auto&quot;&gt;--local&lt;/code&gt; and the pip-default modes. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; treats the directory as its own only when this run created it. A pre-existing directory is kept, or archived to &lt;code dir=&quot;auto&quot;&gt;.kittify/.backup-&amp;#x3C;ts&gt;/&lt;/code&gt;, with the same “not package-owned — left in place” message that &lt;code dir=&quot;auto&quot;&gt;command-templates&lt;/code&gt; already prints. Both copy modes back up an existing &lt;code dir=&quot;auto&quot;&gt;templates/&lt;/code&gt; before overwriting.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty research&lt;/code&gt; no longer creates empty “ready” artifacts when no template resolves&lt;/strong&gt; (#4926). &lt;strong&gt;Before:&lt;/strong&gt; on a &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; mission, which ships no research templates, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; created four 0-byte files (&lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research/evidence-log.csv&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research/source-register.csv&lt;/code&gt;), showed the green “N artifacts ready” panel and exited 0. &lt;strong&gt;After:&lt;/strong&gt; nothing is written unless a template actually resolved, and the panel shows only real writes. A run with no template says “no research template for mission type X”. A re-run over existing files says “existing artifacts preserved; re-run with —force”.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty research --force&lt;/code&gt; no longer truncates your research files&lt;/strong&gt; (#4926). &lt;strong&gt;Before:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; over an existing artifact, it emptied that file. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; never empties a file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; and the upgrade migrations no longer delete your own commands, skills, command templates, governance files or scripts just because their names match a retired path&lt;/strong&gt; (#4859, #4861, #4862, #4792, #3347). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; in global-runtime mode deleted &lt;code dir=&quot;auto&quot;&gt;.kittify/command-templates/&lt;/code&gt;, a directory you can author. The skill-retirement migration (#4859) and the charter-rename migration (#4862) deleted governance and skill files by name, and the python-only migration deleted your &lt;code dir=&quot;auto&quot;&gt;.sh&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.ps1&lt;/code&gt; scripts. None made a backup. &lt;strong&gt;After:&lt;/strong&gt; a file is deleted only when its content proves Spec Kitty owns it (a manifest &lt;code dir=&quot;auto&quot;&gt;content_hash&lt;/code&gt;, a regenerable package file, or a matching &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;!-- spec-kitty-command-version:&lt;/code&gt; marker or canonical bytes). Otherwise it is kept, or archived to &lt;code dir=&quot;auto&quot;&gt;.kittify/.backup-&amp;#x3C;ts&gt;/&lt;/code&gt; when its parent is being removed, and you get a warning, never a non-zero exit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A refused review gate in &lt;code dir=&quot;auto&quot;&gt;agent tasks move-task&lt;/code&gt; no longer deletes your uncommitted files when it cannot read &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt;&lt;/strong&gt; (#5392, #5400). &lt;strong&gt;Before:&lt;/strong&gt; if the dirty-file snapshot taken before the gate failed, every pre-existing untracked or modified file in the lane looked like a file the gate had created, and an aborted gate removed it. &lt;strong&gt;After:&lt;/strong&gt; when either snapshot cannot be read, the gate cleans up nothing. The &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor sparse-checkout&lt;/code&gt; repair likewise treats an unreadable &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; as dirty and refuses before running &lt;code dir=&quot;auto&quot;&gt;git checkout HEAD -- .&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;windows&quot;&gt;Windows&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer crashes on Windows while applying managed skills&lt;/strong&gt; (#4923, #4930). &lt;strong&gt;Before:&lt;/strong&gt; each managed-skill write called &lt;code dir=&quot;auto&quot;&gt;os.utime&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;Path.chmod&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;follow_symlinks=False&lt;/code&gt;, which Windows does not support. &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; aborted with &lt;code dir=&quot;auto&quot;&gt;NotImplementedError: utime: follow_symlinks unavailable on this platform&lt;/code&gt; and left &lt;code dir=&quot;auto&quot;&gt;.kittify/command-skills-manifest.json&lt;/code&gt; partly applied. The released 4.0.0rc4 wheel is affected. &lt;strong&gt;After:&lt;/strong&gt; those calls use the flag only where the host supports it and fall back to a normal call otherwise. Symlink behavior on POSIX hosts is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A converged Windows project no longer reports phantom repairs from &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --dry-run&lt;/code&gt;&lt;/strong&gt; (#4927). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;upgrade --dry-run&lt;/code&gt; reported &lt;code dir=&quot;auto&quot;&gt;Would repair 184 supporting surface paths&lt;/code&gt;, one phantom &lt;code dir=&quot;auto&quot;&gt;chmod&lt;/code&gt; per managed file, because Windows never shows the planned POSIX mode. &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces&lt;/code&gt; reported the same project clean. &lt;strong&gt;After:&lt;/strong&gt; a mode difference that Windows cannot represent no longer produces a repair, so a converged Windows project reports zero and agrees with &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces&lt;/code&gt;. A real mode difference on a POSIX host still produces a repair. Known limitation: &lt;code dir=&quot;auto&quot;&gt;upgrade --yes&lt;/code&gt; exiting 1 on a no-op is not reproduced yet and may be fixed by this change; it is tracked for Windows re-verification (#4925).&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;requirements-tasks-and-other-fixes&quot;&gt;Requirements, tasks and other fixes&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; no longer erases or rewrites the &lt;code dir=&quot;auto&quot;&gt;requirement_refs&lt;/code&gt; you write&lt;/strong&gt; (#2991). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; rebuilt the &lt;code dir=&quot;auto&quot;&gt;requirement_refs&lt;/code&gt; of each work package (WP) with a parser that only knew &lt;code dir=&quot;auto&quot;&gt;FR&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;NFR&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;C&lt;/code&gt;, so success criteria (&lt;code dir=&quot;auto&quot;&gt;SC-001&lt;/code&gt;), letter-suffixed IDs (&lt;code dir=&quot;auto&quot;&gt;FR-006a&lt;/code&gt;) and citations were deleted from disk, sometimes without a warning. &lt;strong&gt;After:&lt;/strong&gt; it never rewrites an item you authored.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; is now append-only&lt;/strong&gt; (#2991). &lt;strong&gt;Before:&lt;/strong&gt; it deleted the same items from the work package (WP) it mapped and re-sorted what was left. &lt;strong&gt;After:&lt;/strong&gt; existing items stay byte-identical and in order. New refs are added in canonical form (&lt;code dir=&quot;auto&quot;&gt;FR-006a&lt;/code&gt;) and duplicates are dropped by canonical form. &lt;code dir=&quot;auto&quot;&gt;--replace&lt;/code&gt; keeps the stored spelling and lists what it removed in &lt;code dir=&quot;auto&quot;&gt;replaced_refs_removed&lt;/code&gt;. One exception: a legacy comma-joined item (&lt;code dir=&quot;auto&quot;&gt;&quot;FR-001, FR-002&quot;&lt;/code&gt;) is split into separate refs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dotted requirement IDs (&lt;code dir=&quot;auto&quot;&gt;FR-002.3&lt;/code&gt;) are no longer silently truncated to their parent ID&lt;/strong&gt; (#3519).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A refused &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; no longer modifies &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;&lt;/strong&gt; (#5100).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Creating a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission on a protected branch that has no commit yet now names the branch and the fix&lt;/strong&gt; (#5100). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; surfaced git’s raw &lt;code dir=&quot;auto&quot;&gt;fatal: &apos;&amp;#x3C;branch&gt;&apos; is not a commit&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it refuses before changing anything and tells you to create the branch or pass &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A corrupt &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; now stops lane allocation instead of silently skipping the &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; check&lt;/strong&gt; (#5100). &lt;strong&gt;Before:&lt;/strong&gt; when a mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; could not be parsed, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; ignored its topology and could allocate a lane worktree for a &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission. &lt;strong&gt;After:&lt;/strong&gt; it refuses with the parse error before any git change. A missing &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; still means there is nothing to check.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Moving a planning-artifact work package (WP) to review no longer needs &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;&lt;/strong&gt; (#5100). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; looked for a lane worktree that a planning WP never has and demanded &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; it passes once the deliverable is committed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete --artifact &amp;#x3C;url&gt;&lt;/code&gt; records the URL intact&lt;/strong&gt; (#5270). &lt;strong&gt;Before:&lt;/strong&gt; every &lt;code dir=&quot;auto&quot;&gt;--artifact&lt;/code&gt; value was treated as a filesystem path, so a pull-request link such as &lt;code dir=&quot;auto&quot;&gt;https://github.com/org/repo/pull/1&lt;/code&gt; was stored and echoed as &lt;code dir=&quot;auto&quot;&gt;https:/github.com/org/repo/pull/1&lt;/code&gt;, a broken link. &lt;strong&gt;After:&lt;/strong&gt; any value that starts with a URL scheme and &lt;code dir=&quot;auto&quot;&gt;://&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;https://&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;http://&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;file://&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;s3://&lt;/code&gt;, …) is recorded exactly as given. Filesystem paths, including Windows drive paths such as &lt;code dir=&quot;auto&quot;&gt;C:\x&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;C:/x&lt;/code&gt;, are still normalized to repo-relative or absolute paths.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission run &amp;#x3C;key&gt; --mission &amp;#x3C;handle&gt;&lt;/code&gt; no longer retypes an existing mission&lt;/strong&gt; (#4965). &lt;strong&gt;Before:&lt;/strong&gt; when the handle (a mid8, numeric prefix or reused slug) resolved to an existing mission of another type, the command rewrote that mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;key&gt;&lt;/code&gt; and reported success (exit 0); &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; then drove the custom mission’s steps for the in-flight mission, or blocked with “No step contract found” when a run already existed. &lt;strong&gt;After:&lt;/strong&gt; the command refuses with exit 2 and &lt;code dir=&quot;auto&quot;&gt;MISSION_TYPE_CONFLICT&lt;/code&gt;, naming the existing type, before any &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, run or contract-registry write. A new slug still creates a fresh mission, re-running the same key against its own mission still attaches, and a typeless mission can still be typed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt; no longer fails every non-Python mission at the dead-code check&lt;/strong&gt; (#5283). &lt;strong&gt;Before:&lt;/strong&gt; the Python-only dead-code scan turned a change set with no Python source (Zig, Go, TypeScript, docs-only…) into a hard &lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_DEAD_CODE_UNDETERMINABLE&lt;/code&gt; failure, so a non-Python mission could never get a clean review. &lt;strong&gt;After:&lt;/strong&gt; the gate is recorded as skipped with a &lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_DEAD_CODE_NOT_APPLICABLE&lt;/code&gt; note that names the unsupported file types and points you to extend your local charter with your own analyzer or test command. The verdict is &lt;code dir=&quot;auto&quot;&gt;pass_with_notes&lt;/code&gt;. Mixed change sets (the Python part is still scanned) and genuine failures (git unavailable, unreadable source) behave as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The mission-review dead-code scan recognizes test paths and Python files more accurately&lt;/strong&gt; (#5283). &lt;strong&gt;Before:&lt;/strong&gt; any path containing “test” counted as test-only, and non-ASCII and upper-case &lt;code dir=&quot;auto&quot;&gt;.PY&lt;/code&gt; paths were skipped. &lt;strong&gt;After:&lt;/strong&gt; test-only paths are matched by path segment or file name (&lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_*.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;*_test.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;conftest.py&lt;/code&gt;), and non-ASCII and &lt;code dir=&quot;auto&quot;&gt;.PY&lt;/code&gt; paths are scanned, so Python missions may see fewer false “unreferenced symbol” notes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A missing &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt; in the CLI’s own environment is now a warning during &lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt;&lt;/strong&gt; (#5283). &lt;strong&gt;Before:&lt;/strong&gt; it stopped the review before any check ran. &lt;strong&gt;After:&lt;/strong&gt; the review continues and warns.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task&lt;/code&gt; no longer refuses to move a work package (WP) because of another work package’s dirty files&lt;/strong&gt; (#5007, #5151, #5159). &lt;strong&gt;Before:&lt;/strong&gt; the move preflight treated any uncommitted file under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/tasks/WPxx-*/&lt;/code&gt; as blocking, even when it belonged to a different WP, and the refusal always blamed the WP being moved. &lt;strong&gt;After:&lt;/strong&gt; only the moving WP’s own dirty files block the move. A dirty file that cannot be matched to any WP also still blocks. The refusal names each blocking file’s real owner, &lt;code dir=&quot;auto&quot;&gt;(owned by WPxx)&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;(not attributable to a specific work package)&lt;/code&gt;. Staged renames are judged on both their old and new paths.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; no longer understates how far a source branch is behind on target branches with many merge commits&lt;/strong&gt; (#4593, #4883). &lt;strong&gt;Before:&lt;/strong&gt; the behind count skipped commits reachable only through merges that add no changes. &lt;strong&gt;After:&lt;/strong&gt; it counts them. The count still only informs a message, and a failed count does not block the command.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor decisions --repair&lt;/code&gt; no longer silently drops a decision that was deferred and then resolved&lt;/strong&gt; (#4919). &lt;strong&gt;Before:&lt;/strong&gt; the documented &lt;code dir=&quot;auto&quot;&gt;open → defer → resolve&lt;/code&gt; flow (a &lt;code dir=&quot;auto&quot;&gt;deferred&lt;/code&gt; event followed by a &lt;code dir=&quot;auto&quot;&gt;resolved&lt;/code&gt; event) was dropped from the rebuilt &lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt;, and the command exited 0. &lt;strong&gt;After:&lt;/strong&gt; the pair folds to &lt;code dir=&quot;auto&quot;&gt;resolved&lt;/code&gt; whatever order the git merge driver re-sorts the events into. Read-only &lt;code dir=&quot;auto&quot;&gt;doctor decisions&lt;/code&gt; now runs the same fold, so an unfoldable decision or a stale index status is reported (&lt;code dir=&quot;auto&quot;&gt;clean: false&lt;/code&gt;) even without &lt;code dir=&quot;auto&quot;&gt;--repair&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;--repair&lt;/code&gt; never drops a malformed decision: it leaves the entry unchanged, names it, and exits 1.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; prints &lt;code dir=&quot;auto&quot;&gt;Assigned mission_number=N&lt;/code&gt; only after that number is really recorded&lt;/strong&gt; (#4900). &lt;strong&gt;Before:&lt;/strong&gt; the line printed before the target-tree write, and a &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; on the target could win the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; merge, so the announced number was often not the recorded one and missions could end up &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt; or renumbered to 1. &lt;strong&gt;After:&lt;/strong&gt; only a positive integer counts as an assigned number, the number is always written to the target through the bookkeeping commit, and “Assigned” prints only after reading the committed target &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; back. A mismatch exits 1 with &lt;code dir=&quot;auto&quot;&gt;Error:&lt;/code&gt; instead of claiming success.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Installing doctrine skills from a CRLF checkout no longer produces drift that &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; cannot repair&lt;/strong&gt; (#4998). &lt;strong&gt;Before:&lt;/strong&gt; on a CRLF source checkout the installer kept CRLF, did not recognize existing frontmatter and prepended a second, bogus block, so &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; reported about 275 drifts that &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; could not repair. &lt;strong&gt;After:&lt;/strong&gt; newlines are normalized to LF before parsing, so CRLF and LF sources render identically. &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces --kind doctrine-skill --fix&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor skills --fix&lt;/code&gt; now repair a corrupted install whose hash matches its manifest. A user-edited file with a mismatched hash stays &lt;code dir=&quot;auto&quot;&gt;consent_required&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate --dry-run &amp;#x3C;subcommand&gt;&lt;/code&gt; no longer runs the real migration&lt;/strong&gt; (#4964). &lt;strong&gt;Before:&lt;/strong&gt; group-level flags typed before a subcommand (&lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--verbose&lt;/code&gt;) were silently dropped, so &lt;code dir=&quot;auto&quot;&gt;migrate --dry-run backfill-runtime-state&lt;/code&gt; ran the real migration and exited 0. &lt;strong&gt;After:&lt;/strong&gt; such a flag is forwarded when the subcommand declares the same flag. Otherwise the command refuses with a usage error (exit 2) naming the flag and the subcommand and pointing to &lt;code dir=&quot;auto&quot;&gt;migrate &amp;#x3C;sub&gt; --help&lt;/code&gt;, before anything runs. This also holds under typer 0.26+. The trailing form &lt;code dir=&quot;auto&quot;&gt;migrate &amp;#x3C;sub&gt; --dry-run&lt;/code&gt; is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The software-dev &lt;code dir=&quot;auto&quot;&gt;discovery&lt;/code&gt; step (also installed as &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.research&lt;/code&gt;) can now be completed as written&lt;/strong&gt; (#5254). &lt;strong&gt;Before:&lt;/strong&gt; the step told the agent to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty research&lt;/code&gt;. For a software-dev mission that command created nothing, refused without a filled &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt; that cannot exist yet, and was shown without its required &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; option. The prompt also told the agent to stop when on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the step tells the agent to record findings directly in &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt; (create it or extend it, never replace it) using only commands that work before a spec or plan exists. The plan step’s Phase 0 extends that file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty research --mission &amp;#x3C;handle&gt;&lt;/code&gt; creates all four advertised files for research-type missions&lt;/strong&gt; (#5254). &lt;strong&gt;Before:&lt;/strong&gt; it never created &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt; for any mission type, because it looked for template names the research pack does not ship. &lt;strong&gt;After:&lt;/strong&gt; after planning, it creates &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt; and both CSV stubs from the shipped templates. For mission types without research templates it still creates nothing and never writes an empty file.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; includes the work package (WP) task in implement and review prompts on coordination-topology missions with lanes&lt;/strong&gt; (#5255, #5259). &lt;strong&gt;Before:&lt;/strong&gt; the prompt read the task from the coordination branch, which holds only status files, found nothing, and still issued a step with a placeholder body and &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;subtask-ids&gt;&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the task body, agent profile and subtasks come from the task file under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/tasks/&lt;/code&gt;. If the task file of any WP in the status log is missing, unreadable, malformed or declares another WP id, &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; and its query mode block with recovery guidance. Canceled WPs are skipped, so canceling a WP whose task file was removed on purpose unblocks the mission.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A symlink loop is now refused the same way on Python 3.11, 3.12, 3.13 and 3.14&lt;/strong&gt; (#3189). &lt;strong&gt;Before:&lt;/strong&gt; Python 3.13 changed how symlink loops resolve, so path guards behaved differently by interpreter. On 3.11 and 3.12 a loop surfaced as an uncaught &lt;code dir=&quot;auto&quot;&gt;RuntimeError&lt;/code&gt; from several guards (command installation, coordination writes, org-pack config, skill update, analysis-report recording). On 3.13 and later the same loop was silently accepted, including by &lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit&lt;/code&gt;, which committed a looping symlink pair. &lt;strong&gt;After:&lt;/strong&gt; every guard refuses a symlink loop on every interpreter with its normal error, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit&lt;/code&gt; stops with a clean error. Known limitation: other code that resolves a path and then checks containment is not covered yet (#3189).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer crashes on a legacy mission whose &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is not a JSON object or not valid UTF-8&lt;/strong&gt; (#2479, #2477, #2478, #4362, #5135). &lt;strong&gt;Before:&lt;/strong&gt; the 0.13.8 &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; migration flagged a &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; holding a JSON array or scalar as needing migration and then aborted with a &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt;. A non-UTF-8 &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; aborted detection with a &lt;code dir=&quot;auto&quot;&gt;UnicodeDecodeError&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the 0.13.0, 0.13.5 and 0.13.8 migrations skip a malformed file during detection. The 0.13.8 upgrade reports it per mission (&lt;code dir=&quot;auto&quot;&gt;Malformed JSON in &amp;#x3C;mission&gt;/meta.json: …&lt;/code&gt;) instead of crashing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; no longer silently re-creates a lane whose branch and worktree were deleted&lt;/strong&gt; (#4889, #5115). &lt;strong&gt;Before:&lt;/strong&gt; when the lane worktree and branch of a work package (WP) were both gone while the WP was still in a non-terminal state, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; cut a new empty lane, printed &lt;code dir=&quot;auto&quot;&gt;✓ Lane worktree ready&lt;/code&gt;, exited 0 and overwrote the lane metadata. The committed work became unreachable, and a later consolidation landed the empty lane. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; (CLI and orchestrator API) refuses with &lt;code dir=&quot;auto&quot;&gt;DESTROYED_LANE&lt;/code&gt; and names the missing branch. Where Spec Kitty recorded the lane’s latest commit, the message names that commit and the restore command (&lt;code dir=&quot;auto&quot;&gt;git branch &amp;#x3C;b&gt; refs/spec-kitty/lane-tip/&amp;#x3C;b&gt;&lt;/code&gt;); on a coordination-topology mission it points you to &lt;code dir=&quot;auto&quot;&gt;git reflog&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;git fsck --lost-found&lt;/code&gt; to find the commit. Squash-merged lanes can still be reopened; recognizing them needs git 2.38 or newer, and older git refuses. Resuming an intact lane is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; refuses a deleted lane whose latest commit Spec Kitty never recorded&lt;/strong&gt; (#5115). &lt;strong&gt;Before:&lt;/strong&gt; such a lane looked empty, so &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; re-created it. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; refuses with &lt;code dir=&quot;auto&quot;&gt;LANE_WORK_TIP_UNKNOWN&lt;/code&gt; and explains how to recover or clean up. It refuses the same way when the recording hook is not active in your repository (for example an in-tree &lt;code dir=&quot;auto&quot;&gt;core.hooksPath&lt;/code&gt; such as husky, or your own &lt;code dir=&quot;auto&quot;&gt;post-commit&lt;/code&gt; hook) and the recorded commit never moved.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Re-running &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; no longer rewrites the recorded mission branch after an identity backfill&lt;/strong&gt; (#5108). &lt;strong&gt;Before:&lt;/strong&gt; every &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; run recomputed the recorded &lt;code dir=&quot;auto&quot;&gt;mission_branch&lt;/code&gt; in the lanes manifest from the current mission identity. After a legacy mission’s identity was backfilled, a re-run silently rewrote it to a name that creation never produced, and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; then pointed at a mission branch that was never created. &lt;strong&gt;After:&lt;/strong&gt; only the first &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; sets the recorded mission branch, and later runs keep it unchanged. A remaining fallback that would rebuild it from an invalid identity refuses, naming &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-identity&lt;/code&gt; as the remedy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Concurrent Spec Kitty commands no longer crash at startup on a fresh machine or CI runner&lt;/strong&gt; (#3998, #4017). &lt;strong&gt;Before:&lt;/strong&gt; when several commands ran startup asset preparation at once on a cold shared Spec Kitty home (a new CI runner, or an orchestrator starting several agents), 1 to 5 of 16 to 32 processes intermittently crashed with &lt;code dir=&quot;auto&quot;&gt;RuntimeError: Asset changed during preparation: …&lt;/code&gt;. They read a peer’s half-written install, retried three times without waiting, then aborted. &lt;strong&gt;After:&lt;/strong&gt; the read waits for the installing peer and re-checks once under that peer’s lock, then the command runs normally. A warm start is unchanged. Source-asset drift is still refused. If startup preparation genuinely cannot complete, the command prints one &lt;code dir=&quot;auto&quot;&gt;Error:&lt;/code&gt; line (or a JSON error object with &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;) and exits 1, with no traceback.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A tag with the same name as the target branch no longer causes a lane’s recorded planning commit to be classified against the wrong commit&lt;/strong&gt; (#4857, #4883). &lt;strong&gt;Before:&lt;/strong&gt; the target branch tip was looked up by its bare name, and git resolves an ambiguous name to the tag. The recorded planning commit could therefore be checked against the tag’s commit instead of the branch tip. &lt;strong&gt;After:&lt;/strong&gt; every lookup uses &lt;code dir=&quot;auto&quot;&gt;refs/heads/&amp;#x3C;branch&gt;&lt;/code&gt;, so it always gets the branch tip. A missing branch returns nothing instead of raising.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; now refuses when &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; is missing, instead of skipping every acceptance-matrix check and recording acceptance&lt;/strong&gt; (#4891). &lt;strong&gt;Before:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/lanes.json&lt;/code&gt; absent, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; skipped the branch gate and all acceptance-matrix checks with no message and exited 0. It wrote &lt;code dir=&quot;auto&quot;&gt;accepted_at&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept_commit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;acceptance_history&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; while every criterion was still &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; already refused. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; exits non-zero, lists the skipped and blocked checks, points at the recovery (&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt;), and records nothing. The &lt;code dir=&quot;auto&quot;&gt;--skip-lanes&lt;/code&gt; opt-in of &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; no longer stops at exit 1 when it reaches the &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; step on the default &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; topology&lt;/strong&gt; (#4975). &lt;strong&gt;Before:&lt;/strong&gt; advancing to &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; returned &lt;code dir=&quot;auto&quot;&gt;kind=blocked reason=&quot;No action mapped for WP step &apos;implement&apos;&quot;&lt;/code&gt;, although query mode and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api list-ready&lt;/code&gt; reported the work package (WP) ready. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; finds the WP on &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;lanes_with_coord&lt;/code&gt; topologies, and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; dispatch succeeds. Dispatch on &lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; missions is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Repeating &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; on an already-current project no longer leaves live coordination worktrees with conflicting metadata&lt;/strong&gt; (#4972). &lt;strong&gt;Before:&lt;/strong&gt; when the CLI was already at the target version, &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; still wrote a fresh &lt;code dir=&quot;auto&quot;&gt;last_upgraded_at&lt;/code&gt; into each live worktree’s &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; and auto-committed it. &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, the coordination branch and each lane branch ended with three different values, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement WP##&lt;/code&gt; failed to merge the dependency lane and &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; refused the lane as stale, although both upgrade runs exited 0. &lt;strong&gt;After:&lt;/strong&gt; when only version bookkeeping changes, every worktree gets the main checkout’s stored &lt;code dir=&quot;auto&quot;&gt;last_upgraded_at&lt;/code&gt;; if main has none, all share one timestamp minted once per run. The file is identical everywhere and merges cleanly. A real content migration still writes a fresh timestamp.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer reports an interrupted lifecycle-envelope migration as successful&lt;/strong&gt; (#4876, #4872). &lt;strong&gt;Before:&lt;/strong&gt; if a lifecycle event log still had a &lt;code dir=&quot;auto&quot;&gt;.pre-migration.bak&lt;/code&gt; snapshot from an earlier interrupted run, the migration skipped that file but &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; printed &lt;code dir=&quot;auto&quot;&gt;✓ migrate_lifecycle_envelope&lt;/code&gt;, recorded &lt;code dir=&quot;auto&quot;&gt;result: success&lt;/code&gt; and advanced the project metadata, leaving the log in its legacy shape. Following the on-screen fix (remove the snapshot, rerun &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;) then said “already applied, skipping”, so the log stayed legacy. &lt;strong&gt;After:&lt;/strong&gt; a refused file fails the whole migration, which is recorded as &lt;code dir=&quot;auto&quot;&gt;failed&lt;/code&gt; and leaves the project version and schema stamp unchanged. Other logs in the same run still migrate. After you remove the stale snapshot, a normal &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; retries the migration.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --fix&lt;/code&gt; no longer silently discards a mission record whose event type was added after the repair’s hard-coded list&lt;/strong&gt; (#4993). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; kept only a fixed list of non-lane event types and quarantined every other record, including ones the running tool treats as real, while reporting exit-0 success. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; preserves exactly what the normal event-log reader preserves and errors instead of dropping any such record.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;traces/&lt;/code&gt; merge helper no longer loses or mis-merges sections that use &lt;code dir=&quot;auto&quot;&gt;~~~&lt;/code&gt; code fences or repeated headings&lt;/strong&gt; (#4993). &lt;strong&gt;Before:&lt;/strong&gt; such sections could be dropped or merged wrongly. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;~~~&lt;/code&gt; fences and repeated section headings are handled, so no trace section is lost.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --fix&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer quarantine a healthy mission’s Decision Moment records while reporting &lt;code dir=&quot;auto&quot;&gt;errors=0&lt;/code&gt;&lt;/strong&gt; (#4897). &lt;strong&gt;Before:&lt;/strong&gt; the repair kept only a narrow list of non-lane record types and treated &lt;code dir=&quot;auto&quot;&gt;DecisionPointOpened&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;DecisionPointResolved&lt;/code&gt; rows in &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; as removable. &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; on a healthy mission removed them and exited 0. The suggested follow-up &lt;code dir=&quot;auto&quot;&gt;doctor decisions --repair&lt;/code&gt; then rebuilt the index to zero entries, so the question, options, answer, rationale and resolver became unreadable. &lt;strong&gt;After:&lt;/strong&gt; the repair and the normal event-log reader share one list of record types that must be kept, and a repair that would quarantine one of those rows now reports an error instead of &lt;code dir=&quot;auto&quot;&gt;errors=0&lt;/code&gt;. Record types that were already preserved are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state --fix&lt;/code&gt; now keeps its repair manifest and quarantined rows in a tracked location where they survive &lt;code dir=&quot;auto&quot;&gt;git clean&lt;/code&gt;&lt;/strong&gt; (#4928, #4897). &lt;strong&gt;Before:&lt;/strong&gt; the manifest and quarantined rows were written under the gitignored &lt;code dir=&quot;auto&quot;&gt;.kittify/migrations/mission-state/&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;git clean -xfd&lt;/code&gt; destroyed the only record of a destructive repair, and &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; did not warn that the files were untracked. &lt;strong&gt;After:&lt;/strong&gt; they go to &lt;code dir=&quot;auto&quot;&gt;.kittify/mission-state-audit/&lt;/code&gt;, which git tracks. A &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; run still never blocks &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; prints a summary naming the manifest, and the quarantine path and row count when rows were moved, marked as tracked but uncommitted. &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; carries the same paths and count.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;spec-kitty-traces&lt;/code&gt; git merge driver no longer deletes repeated lines (code fences, headings, repeated prose) from &lt;code dir=&quot;auto&quot;&gt;traces/*.md&lt;/code&gt; during an ordinary merge&lt;/strong&gt; (#4894). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; binds &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**/traces/*.md&lt;/code&gt; to this driver for every &lt;code dir=&quot;auto&quot;&gt;git merge&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;rebase&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;cherry-pick&lt;/code&gt;. It dropped every non-empty line already seen, so a document with four fenced blocks kept one fence line and swallowed the rest into an unterminated code block. &lt;code dir=&quot;auto&quot;&gt;git merge&lt;/code&gt; still exited 0 with a clean merge. &lt;strong&gt;After:&lt;/strong&gt; the driver merges by markdown section, removing only sections that are byte-identical. It uses the merge base, so a section unchanged from the base is superseded by your edit and a new section is kept. A section changed on both sides keeps both copies. No non-empty line from either side is lost silently; otherwise the merge conflicts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The legacy &lt;code dir=&quot;auto&quot;&gt;agent tasks finalize-tasks&lt;/code&gt; no longer accepts a broken dependency graph as valid&lt;/strong&gt; (#4890, #4915). &lt;strong&gt;Before:&lt;/strong&gt; it validated the graph from &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; but saved the work package (WP) frontmatter dependencies unchecked. A cycle, self-reference or unknown-WP reference that existed only in frontmatter finalized with exit 0 and seeded status, leaving both WPs unclaimable. &lt;strong&gt;After:&lt;/strong&gt; it validates the dependency graph it will actually save, using the same checks as &lt;code dir=&quot;auto&quot;&gt;agent mission finalize-tasks&lt;/code&gt;. On any violation it exits non-zero and seeds no status.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty mission reopen&lt;/code&gt; now works on a merged mission whose only completion proof is its &lt;code dir=&quot;auto&quot;&gt;merged_*&lt;/code&gt; markers&lt;/strong&gt; (#4870). &lt;strong&gt;Before:&lt;/strong&gt; the command cleared the &lt;code dir=&quot;auto&quot;&gt;merged_*&lt;/code&gt; markers in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; before writing the &lt;code dir=&quot;auto&quot;&gt;MissionReopened&lt;/code&gt; event. For a mission completed by merge with no terminal work packages (WPs), that left nothing to prove completion, so the reopen failed, and every retry was refused because the proof was already gone. &lt;strong&gt;After:&lt;/strong&gt; it saves the markers, writes the reopen event (carrying the saved markers so the reopen can be reversed), and only then clears them. If the command refuses before the event is written, &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is left byte-for-byte unchanged. If the final clear fails after the event is recorded, it reports a retryable &lt;code dir=&quot;auto&quot;&gt;mission_reopen_clear_failed&lt;/code&gt; error, and rerunning &lt;code dir=&quot;auto&quot;&gt;reopen&lt;/code&gt; fixes it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Creating missions from several threads in one process no longer fails intermittently or resolves a mission type with a missing step&lt;/strong&gt; (#4589). &lt;strong&gt;Before:&lt;/strong&gt; threads in a long-lived host or parallel tooling could fail with &lt;code dir=&quot;auto&quot;&gt;TemplateConfigurationError&lt;/code&gt; (”… is missing the requested mapping key”), or silently resolve a mission type missing a step. Template resolution shared one YAML parser and one cache-fill path across threads. &lt;strong&gt;After:&lt;/strong&gt; each thread parses YAML separately, and only one thread fills the cache while the others wait for its result. Single-threaded behavior and public APIs are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commands that read file paths from git now handle paths with spaces, non-ASCII characters or &lt;code dir=&quot;auto&quot;&gt;-&gt;&lt;/code&gt; in the name&lt;/strong&gt; (#5392, #5400). &lt;strong&gt;Before:&lt;/strong&gt; about 50 modules parsed git’s quoted display text, so such a path was misread or missed: for example the &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; commit guard never matched &lt;code dir=&quot;auto&quot;&gt;kitty-specs/café…&lt;/code&gt;, the review dead-code scan reported no new symbols for &lt;code dir=&quot;auto&quot;&gt;src/my pkg/mod.py&lt;/code&gt;, and a staged rename into an expected file hid the deletion of its source from the post-consolidation check. &lt;strong&gt;After:&lt;/strong&gt; every path listing is read as NUL-separated data and compared by path component. Where a check used to treat a failed git call as “no changes”, the ones that protect data now refuse instead: the commit guard hook (unless the guard is disabled), &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt;’s clean-tree check, the post-consolidation porcelain check, the squash-projection proof, the planning-recency check and the &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; lane-write guard.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate anti-pattern &amp;#x3C;id&gt;&lt;/code&gt; and the activation registry now accept anti-patterns instead of rejecting a kind they advertised as valid&lt;/strong&gt; (#5409). &lt;strong&gt;Before:&lt;/strong&gt; the activation registry listed &lt;code dir=&quot;auto&quot;&gt;anti_pattern&lt;/code&gt; as an accepted &lt;code dir=&quot;auto&quot;&gt;artifact_kind&lt;/code&gt; alias, then rejected both &lt;code dir=&quot;auto&quot;&gt;anti_pattern&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;anti_patterns&lt;/code&gt; with an error message that named &lt;code dir=&quot;auto&quot;&gt;anti_pattern&lt;/code&gt; as accepted — the registry’s allowed-kinds set was a hand-copied list that omitted anti-patterns while the alias map, and &lt;code dir=&quot;auto&quot;&gt;PackContext.activated_anti_patterns&lt;/code&gt;, already carried them. &lt;strong&gt;After:&lt;/strong&gt; the doctrine artifact-kind vocabulary derives from one authority (the &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; enum, now carrying &lt;code dir=&quot;auto&quot;&gt;plural&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;activatable&lt;/code&gt; facts), so anti-patterns are charter-activatable end to end and every activation kind-vocabulary list stays consistent by construction. A structural gate replaces the former hand-kept drift guard. No configuration changes are required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-3&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;The test suite’s green now means the tests ran: tests that skipped on every run or cited closed issues now run or point at open ones, exact-count pins became invariants proven by planted breaks, and the dead-symbol allowlist is keyed by &lt;code dir=&quot;auto&quot;&gt;(module, name)&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;tests/architectural/dead_symbol_allowlist.yaml&lt;/code&gt; (ADR &lt;code dir=&quot;auto&quot;&gt;2026-10-01-1&lt;/code&gt;) (#5346, #5353).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Git path listings have one owner, &lt;code dir=&quot;auto&quot;&gt;kernel.git&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/kernel/git/&lt;/code&gt;): one runner, NUL-safe listing queries, a &lt;code dir=&quot;auto&quot;&gt;GitPath&lt;/code&gt; value type and a typed &lt;code dir=&quot;auto&quot;&gt;GitCommandError&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_git_path_listing_owner.py&lt;/code&gt; refuses any path-listing git call or git-output parsing outside it, with an empty allowlist (119 sites in 51 files at the start, 0 now); it replaces the porcelain registry in &lt;code dir=&quot;auto&quot;&gt;test_destructive_op_routing.py&lt;/code&gt;. ADR &lt;code dir=&quot;auto&quot;&gt;docs/adr/4.x/2026-09-30-1-allowlist-ratchets-are-priced-debt.md&lt;/code&gt; records that allowlist ratchets are recurring CI cost to drain, not a resting state (#5392, #5400; follow-up #5475).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The PR-body validator ships as a maintainer-only asset&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;packs/internal/assets/validate-pr-body.py&lt;/code&gt;). It checks a PR body against the five-section contract in &lt;code dir=&quot;auto&quot;&gt;docs/development/how-to/pr-landing.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.github/PULL_REQUEST_TEMPLATE.md&lt;/code&gt;, and with &lt;code dir=&quot;auto&quot;&gt;--verify-discovery --expected-head &amp;#x3C;sha&gt;&lt;/code&gt; re-runs the Blast-radius &lt;code dir=&quot;auto&quot;&gt;git grep&lt;/code&gt; and compares the &lt;code dir=&quot;auto&quot;&gt;Files:&lt;/code&gt; list. It is not shipped to consumers.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;About 5,000 lines of dead &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; code were removed, following the 2026-09-30 dead-code review: the unused &lt;code dir=&quot;auto&quot;&gt;specify_cli.proof&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;specify_cli.auth.websocket&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_runtime.facade&lt;/code&gt; packages, the &lt;code dir=&quot;auto&quot;&gt;runtime.next._internal_runtime&lt;/code&gt; re-export modules, leftovers of the retired sync transport (the &lt;code dir=&quot;auto&quot;&gt;sync_dossier&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ensure_daemon&lt;/code&gt; parameters, &lt;code dir=&quot;auto&quot;&gt;Event&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;LamportClock&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;RuntimeRoot.sync_dir&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;daemon_dir&lt;/code&gt;), and symbols the review marked dead with high confidence. The dead-code gate allowlists shrink with them. No command behaves differently.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Guard tests that stayed green when the behavior they guard broke now fail on it, three legacy test harnesses stopped stubbing newer safety gates, and redundant tests were retired (#5353, #5344, #5345, #4036, #4105, #4210, #4388, #4408, #4536, #4883).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;An unused template-path helper was removed (#5254).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Per-PR charter shard-timings drift now warns instead of failing the build, and a scheduled workflow re-captures the artifact and opens a PR (#5189, #5240, #5164, #5175). Maintainer action: create the repository secret &lt;code dir=&quot;auto&quot;&gt;CHARTER_SHARD_RECAPTURE_TOKEN&lt;/code&gt; (fine-grained, this repository only, Contents and Pull requests read/write).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;A new shrink-only test gate stops repository-local paths and provenance tokens from growing in &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; (#5223).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The lane branch and worktree naming helpers no longer accept a &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; argument (#5108).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Architectural test allowlists now identify exemptions by content instead of &lt;code dir=&quot;auto&quot;&gt;path:line&lt;/code&gt;, so unrelated edits no longer turn them red, and gates that could never fail were fixed or retired (#5104, #5085, #3011, #3026, #3962, #2631, #5145, #5116).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;CI now guards against test suites being silently skipped on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; pushes, and a nightly &lt;code dir=&quot;auto&quot;&gt;integration-next&lt;/code&gt; lane opens a deduplicated &lt;code dir=&quot;auto&quot;&gt;priority:P0&lt;/code&gt; issue on red (#5034).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;release.yml&lt;/code&gt; now blocks &lt;code dir=&quot;auto&quot;&gt;build-release&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;publish-pypi&lt;/code&gt; unless the &lt;code dir=&quot;auto&quot;&gt;ci-nightly&lt;/code&gt; run for the exact release SHA is green (#5034). Maintainer action: create the repository secret &lt;code dir=&quot;auto&quot;&gt;RELEASE_NIGHTLY_DISPATCH_TOKEN&lt;/code&gt; (see &lt;code dir=&quot;auto&quot;&gt;RELEASE_CHECKLIST.md&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Nightly CI timeout caps for interpreter shards 1-3 and 5 and the out-of-matrix leg are re-derived from five measured runs, so a slow runner no longer ends in &lt;code dir=&quot;auto&quot;&gt;cancelled&lt;/code&gt; (#5378).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Nightly &lt;code dir=&quot;auto&quot;&gt;tests/integration&lt;/code&gt; fixtures now match five earlier product changes, so 22 red tests are green again (#5044, #5045, #5049, #4959, #5001, #4764, #4758, #4990).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The nightly integration and performance suites are green again: their fixtures now create the real lane branches an approved lane needs, which &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; has required at claim time since #5338, through a shared &lt;code dir=&quot;auto&quot;&gt;create_lane_branches&lt;/code&gt; helper; the claim-time refusal is unchanged (#5417).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The three &lt;code dir=&quot;auto&quot;&gt;*-supply-chain&lt;/code&gt; toolguides drop inert inline &lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt;; the doctrine graph is unchanged and the nightly raw-material census is re-pinned from 19 to 20 (#5367).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The test suite no longer leaks working directory, environment, import path, loaded modules or argv between tests, and a new architectural gate blocks new manual global-state changes (#5118).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The merge-driver code moved out of the CLI command module into the merge domain, so git’s driver and the consolidation integrity check replay run the same code; behavior is unchanged (#5119).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;make test-fast&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;make test-full&lt;/code&gt; no longer fail with &lt;code dir=&quot;auto&quot;&gt;ModuleNotFoundError: pytestarch&lt;/code&gt; in a fresh lane worktree; &lt;code dir=&quot;auto&quot;&gt;pytestarch&lt;/code&gt; is now in the &lt;code dir=&quot;auto&quot;&gt;dev&lt;/code&gt; dependency group (#5160).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;make test-fast&lt;/code&gt; no longer shows three unrelated charter test failures when run from a linked worktree; the tests now use the working-directory isolation fixture (#4873).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;CI Fleet Verdict&lt;/code&gt; workflow runs again on every &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; push after &lt;code dir=&quot;auto&quot;&gt;scripts/ci/fleet_verdict.py&lt;/code&gt; crashed at startup (#5127, #5000).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Removed a dead frontmatter-field check from the &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; dependency path and fixed a cyclic-dependency test whose exit-code assertion could not fail (#4152, #4883).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Architectural checks now fail on any unguarded destructive removal or overwrite in &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, the mission-brief writers, &lt;code dir=&quot;auto&quot;&gt;init.py&lt;/code&gt;, migrations, the &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; migration, the git pack fetch and &lt;code dir=&quot;auto&quot;&gt;agent config&lt;/code&gt; (#4901, #4859, #4861, #4862, #4961, #4960, #4989, #4915).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The “do not overwrite an existing mission brief” rule now lives in the brief writer itself, and the &lt;code dir=&quot;auto&quot;&gt;intake&lt;/code&gt; paths delegate to it (#4921, #4910, #4918).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The project’s configured mission type is now read through one shared parser instead of two (#4993).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Docs prose is now spell-checked in CI (typos, and US spelling in the guides, context pages and this section), and a style guard keeps Unreleased entries in the Breaking to Internal shape (#5426).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Mission-step guidelines are loaded only from &lt;code dir=&quot;auto&quot;&gt;mission-steps/&amp;#x3C;type&gt;/&amp;#x3C;action&gt;/guidelines.md&lt;/code&gt;, and the duplicate copies under &lt;code dir=&quot;auto&quot;&gt;missions/&amp;#x3C;type&gt;/actions/&lt;/code&gt; are removed (#5202).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;spec-kitty-mission-review&lt;/code&gt; skill’s Gate 3 floor no longer lists the retired &lt;code dir=&quot;auto&quot;&gt;saas_sync_enabled.py&lt;/code&gt; scenario or the inert &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC=1&lt;/code&gt; pin (#5136, #5003, #4949).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Every test now has a 240-second per-test timeout, set once in &lt;code dir=&quot;auto&quot;&gt;pytest.ini&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;timeout = 240&lt;/code&gt;) so it applies uniformly to the Linux module shards, the Windows job, local &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt; runs and the &lt;code dir=&quot;auto&quot;&gt;make&lt;/code&gt; targets (#3143, refs #3864). Previously a hanging test was only killed by a job-level &lt;code dir=&quot;auto&quot;&gt;timeout-minutes&lt;/code&gt;, ending the run with no summary, no counter and no named test; now pytest-timeout fails that one test by name (signal method on POSIX, thread fallback on Windows, where there is no SIGALRM) and the run continues. The redundant &lt;code dir=&quot;auto&quot;&gt;--timeout=240 --timeout-method=signal&lt;/code&gt; flags on the Makefile serial passes were dropped in favor of the ini default, and a new gate (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_pytest_ini_timeout_default.py&lt;/code&gt;) pins the value so it cannot drift out again.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Per-PR CI is faster and no longer runs the same tests twice (#5510, #3265, #3315, #5086, #5092). The architectural battery now runs as an always-on fast job plus two balanced heavy legs with four pytest workers each (it used two on the 4-vCPU runners), and expensive whole-tree scans are cached once per test file. The duplicate router &lt;code dir=&quot;auto&quot;&gt;tests (cli|status|consolidation)&lt;/code&gt; jobs and the second corpus run are removed. The 40 corpus tests no module owns keep a blocking router job, and Packs runs the corpus as advisory. A &lt;code dir=&quot;auto&quot;&gt;ready_for_review&lt;/code&gt; (or other re-trigger) on a head and base that already ran green skips the heavy jobs and points CI Aggregate at the matched run. Any doubt runs the jobs in full. Workflow, &lt;code dir=&quot;auto&quot;&gt;pytest.ini&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; and registry changes now select the full battery. A nightly &lt;code dir=&quot;auto&quot;&gt;architectural-backstop&lt;/code&gt; job runs the whole per-PR battery, and a live check rejects any test that two same-tier jobs both run. The consolidation module row is split into two shards with recaptured timings, and a timing artifact that no longer matches the tests now fails loudly. ADR amendments: &lt;code dir=&quot;auto&quot;&gt;2026-09-26-1&lt;/code&gt; (nightly backstop) and &lt;code dir=&quot;auto&quot;&gt;2026-09-23-1&lt;/code&gt; (skip-if-green).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;400rc4---2026-09-21&quot;&gt;[4.0.0rc4] - 2026-09-21&lt;/h2&gt;
&lt;p&gt;Fourth release candidate for the Team Kitty 4.x cold-start walkthrough. The
headline is the &lt;strong&gt;Windows runtime repair&lt;/strong&gt; — Spec Kitty is usable on Windows
again, with the &lt;code dir=&quot;auto&quot;&gt;[Errno 13] Permission denied&lt;/code&gt; family closed (#4703) on a
unified cross-OS lock / safe-delete / OS-detection foundation that now has one
canonical owner each. This candidate also lands &lt;strong&gt;local write-safety
hardening&lt;/strong&gt; (routine commands can no longer truncate an unrelated file or
destroy operator work), &lt;strong&gt;merge / abort / close safety&lt;/strong&gt; (no silent loss of
uncommitted work, no wedged missions; #4752–#4754, #4764, #4474), &lt;strong&gt;charter and
doctrine correctness&lt;/strong&gt; (canonical doctrine artifact slug #4832–#4834, custom
mission-type resolution, and &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; re-pinning an orphaned
&lt;code dir=&quot;auto&quot;&gt;planning_commit_sha&lt;/code&gt; after a mid-mission rebase #4827), an &lt;strong&gt;auth fix&lt;/strong&gt; (no
refresh/access token is sent to a server the session never authenticated
against), the Zeitgeist &lt;code dir=&quot;auto&quot;&gt;activity --person&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--project&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;watch --seed&lt;/code&gt;
selectors (#4215), and a broad sweep of CLI, &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; fixes.&lt;/p&gt;
&lt;p&gt;The final release remains subject to a Windows 11 artifact smoke test.&lt;/p&gt;
&lt;h3 id=&quot;added-4&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty zeitgeist activity --person&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--project&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;watch --seed&lt;/code&gt; close #4215’s remaining read-surface scope (the 2026-09-17 narrowing over the 2026-09-14 re-scope).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;activity&lt;/code&gt;’s two missing selectors are client-side membership rules over the retained frames — &lt;code dir=&quot;auto&quot;&gt;--person&lt;/code&gt; keeps only frames whose actor &lt;code dir=&quot;auto&quot;&gt;user&lt;/code&gt; names that teammate (unattributed frames never match), &lt;code dir=&quot;auto&quot;&gt;--project&lt;/code&gt; keeps only frames whose mission correlation (&lt;code dir=&quot;auto&quot;&gt;focus_ref&lt;/code&gt;, or an event frame’s &lt;code dir=&quot;auto&quot;&gt;ref&lt;/code&gt;) is the slug or begins &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;.&lt;/code&gt;, with BOTH ref kinds grammar-routed so prose that merely contains — or starts with — a slug cannot attach itself to a mission. Both are reported with their own matched/withheld counts in a &lt;code dir=&quot;auto&quot;&gt;selector&lt;/code&gt; block, so an empty result under a selector never reads as an empty relay; the relay’s &lt;code dir=&quot;auto&quot;&gt;/managed/events&lt;/code&gt; route has no such filter, so the narrowing happens on this side of the wire. &lt;code dir=&quot;auto&quot;&gt;watch --seed &amp;#x3C;seconds&gt;&lt;/code&gt; (and the MCP &lt;code dir=&quot;auto&quot;&gt;zeitgeist_watch&lt;/code&gt; tool’s &lt;code dir=&quot;auto&quot;&gt;seed_window_s&lt;/code&gt;) switches to the relay’s race-safe &lt;code dir=&quot;auto&quot;&gt;follow=1&lt;/code&gt; handoff (zeitgeist#296): the preface &lt;code dir=&quot;auto&quot;&gt;SnapshotDocument&lt;/code&gt; seeds presence/focus state from the registries at the cut, its retained history is delivered first through the same novelty/receipt policy, and live frames that duplicate a history frame are dropped by &lt;code dir=&quot;auto&quot;&gt;(epoch, seq)&lt;/code&gt; — whole, never state-applied, so a duplicated pre-cut signal cannot wipe the just-seeded registries — the overlap the relay’s reserve-before-snapshot ordering makes correct. The preface read is bounded by the watch call’s own &lt;code dir=&quot;auto&quot;&gt;idle_timeout_s&lt;/code&gt; (a relay trickling only SSE heartbeat lines gets a named &lt;code dir=&quot;auto&quot;&gt;TimeoutError&lt;/code&gt;, never an indefinite hang), a requested seed against a relay without the follow route is reported as the missing route it is (not a connectivity fault), and the MCP &lt;code dir=&quot;auto&quot;&gt;seed_window_s&lt;/code&gt; parameter is schema-strict (&lt;code dir=&quot;auto&quot;&gt;&gt;= 0&lt;/code&gt;, no bool/string coercion — same rejection the CLI’s &lt;code dir=&quot;auto&quot;&gt;min=0.0&lt;/code&gt; applies). &lt;code dir=&quot;auto&quot;&gt;0&lt;/code&gt;/omitted stays future-only; a relay that serves no snapshot answers 404 and an unusable preface raises — a requested seed is never silently degraded. The preface’s coverage metadata rides the result as &lt;code dir=&quot;auto&quot;&gt;seed&lt;/code&gt;, so a truncated backfill is visible. CLI and MCP call the same &lt;code dir=&quot;auto&quot;&gt;subscription.agent_activity&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agent_watch&lt;/code&gt; service; &lt;code dir=&quot;auto&quot;&gt;docs/api/cli-commands.md&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;zeitgeist status&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;watch&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;activity&lt;/code&gt; sections are regenerated to match. Deferred with evidence: credential renewal on an expired capability stays with auth epic #3892 (no renewal seam exists for readers to call yet; a denied read already fails legibly as a fault, never as an empty team). The same PR folds #4335’s two squad MINORs on the slice-1 status surface: &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;’s fallback listen now reports the &lt;strong&gt;measured&lt;/strong&gt; listen time instead of the configured bound (a relay that closes the stream early no longer prints “listened for 2.0s”), and snapshot entry ages are derived &lt;strong&gt;skew-free&lt;/strong&gt; from the document’s own &lt;code dir=&quot;auto&quot;&gt;observed_at&lt;/code&gt; anchor (anchor − entry &lt;code dir=&quot;auto&quot;&gt;observed_at&lt;/code&gt;, both on the relay’s clock, plus only the locally-measured time since fetch) instead of subtracting a relay timestamp from the local wall clock — a relay an hour ahead of the client no longer clamps a 40-second-old observation to a lying &lt;code dir=&quot;auto&quot;&gt;observed 0s ago&lt;/code&gt;. The anchor and fetch time ride the JSON result as top-level &lt;code dir=&quot;auto&quot;&gt;observed_at&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fetched_at&lt;/code&gt;; the listen path (no anchor exists there) keeps the legacy derivation and says so in &lt;code dir=&quot;auto&quot;&gt;_observation_age&lt;/code&gt;’s docstring.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-4&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; now heals a &lt;code dir=&quot;auto&quot;&gt;planning_commit_sha&lt;/code&gt; that a mid-mission rebase orphaned, instead of silently preserving the dead SHA and wedging lane allocation&lt;/strong&gt; (#4827). When a lanes mission’s branch is rebased onto a moved base, the planning commit is rewritten to a new SHA and the one recorded in &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; becomes &lt;em&gt;orphaned&lt;/em&gt; — still present in the object store but no longer reachable from the target-branch tip. &lt;strong&gt;Before:&lt;/strong&gt; a plain &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission finalize-tasks&lt;/code&gt; silently preserved that orphaned SHA (&lt;code dir=&quot;auto&quot;&gt;action=preserved&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;--refresh-planning-commit&lt;/code&gt; refused to re-point it (it was advance-only and treated any non-ancestor recorded SHA as a dangerous rewrite), so subsequent &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; lane allocation and the dependency-lane auto-merge dead-ended against a commit no longer on the branch — surfaced as a generic “merge conflicts — resolve manually” — and the only escape was hand-editing &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;. The claim-ancestry gate refused with a bare &lt;code dir=&quot;auto&quot;&gt;missing_refs&lt;/code&gt; entry and the owned-review base was silently computed against the dead commit. &lt;strong&gt;After:&lt;/strong&gt; finalize classifies the recorded pin against the target-branch tip into &lt;em&gt;advanced&lt;/em&gt; / &lt;em&gt;orphaned&lt;/em&gt; / &lt;em&gt;foreign&lt;/em&gt;; a plain run &lt;strong&gt;fails closed&lt;/strong&gt; on a proven orphan, naming the recovery command and the recorded/tip SHAs (still degrading to the historical preserve when the tip is uncapturable, the repo is non-git, or the object is genuinely absent), and the new &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks --refresh-planning-commit --allow-orphaned&lt;/code&gt;&lt;/strong&gt; re-pins the recorded SHA to the live planning tip (reported as &lt;code dir=&quot;auto&quot;&gt;action=repinned&lt;/code&gt; in human and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output). Every recorded-pin consumer now names the stale pin and the re-pin recovery instead of a false conflict: lane allocation and the workspace-reconcile merge raise a distinct &lt;code dir=&quot;auto&quot;&gt;OrphanedPlanningCommitError&lt;/code&gt; (not the generic conflict, so an orphan is never removed-and-retried), the claim-ancestry gate emits an orphan-aware diagnostic, and the owned-review base fails closed rather than diffing against the dead commit. Bare &lt;code dir=&quot;auto&quot;&gt;--refresh-planning-commit&lt;/code&gt; keeps its #4141 advance-only semantics unchanged (a genuinely divergent, foreign pin is still refused), and a lane allocated before the rebase catches up to the live planning state through an ordinary merge once the pin is healed. The orchestrator-api &lt;code dir=&quot;auto&quot;&gt;planning_commit&lt;/code&gt; decision contract gains the additive &lt;code dir=&quot;auto&quot;&gt;repinned&lt;/code&gt; action (&lt;code dir=&quot;auto&quot;&gt;CONTRACT_VERSION&lt;/code&gt; 1.6.0). The same change folds #4178’s preserve-path drift-warning false positive (it no longer fires on finalize’s own bookkeeping commit, and the decision is reported after the &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; write). Reduced false dependency-lane conflicts (#3936) are a welcome side effect; a first-class “rebase mission onto moved base” command (#2273) and durable-artifact SHA hygiene (#2897) remain separate, deferred concerns.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Org-tier custom mission types and project mission-type overrides now resolve as themselves instead of being replaced by software-dev&lt;/strong&gt; (#3831, #4088). The mission-type &lt;em&gt;loader&lt;/em&gt; (&lt;code dir=&quot;auto&quot;&gt;specify_cli/mission.py&lt;/code&gt;) was org-blind: it consulted only &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;type&gt;/&lt;/code&gt; and the packaged built-ins, never the org doctrine-pack tier or the &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/missions/&lt;/code&gt; override tier that command-template resolution already uses. &lt;strong&gt;Before:&lt;/strong&gt; a mission type delivered by an org pack (activated via &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs&lt;/code&gt;) fell through the loader, and &lt;code dir=&quot;auto&quot;&gt;get_mission_for_feature&lt;/code&gt; warn-and-substituted &lt;strong&gt;software-dev&lt;/strong&gt; — validating the mission against software-dev’s &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt; path conventions and required/optional artifacts; a project override under &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/missions/&amp;#x3C;type&gt;/&lt;/code&gt; was likewise ignored. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;get_mission_by_name&lt;/code&gt; resolves &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; through the shared org-aware resolver (override → legacy → org → global → package), and, for a type registered via a sparse &lt;code dir=&quot;auto&quot;&gt;mission_types/&amp;#x3C;type&gt;.yaml&lt;/code&gt; with no &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt;, builds a neutral &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; carrying the type’s own identity and conventions (never software-dev’s). A typeless feature still loads the software-dev &lt;em&gt;template&lt;/em&gt; default with no warning; a typed-but-&lt;strong&gt;unknown&lt;/strong&gt; type now fails visibly (&lt;code dir=&quot;auto&quot;&gt;MissionNotFoundError&lt;/code&gt;) instead of silently substituting. Built-ins stay byte-unchanged and agree with mission discovery: a built-in mission-type name’s package-tier and global-runtime-cache (&lt;code dir=&quot;auto&quot;&gt;~/.kittify/missions/&amp;#x3C;type&gt;/&lt;/code&gt;) hits are pinned back to the packaged &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&amp;#x3C;type&gt;/&lt;/code&gt; source, so a populated global runtime can never silently shadow a built-in; project-level overrides (&lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/missions/&amp;#x3C;type&gt;/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;type&gt;/&lt;/code&gt;) and org-pack mission types still resolve through the org-aware chain, so no built-in path convention or artifact set changes for the resolution paths mission discovery already covers. The &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&lt;/code&gt; project tier now emits the shared resolver’s &lt;code dir=&quot;auto&quot;&gt;run spec-kitty migrate&lt;/code&gt; deprecation nudge (consistent with command-template resolution). Unifying the two built-in package roots (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt; vs &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/&lt;/code&gt;) is part of the deferred #2652 convergence. A new charter &lt;code dir=&quot;auto&quot;&gt;MissionType.path_conventions&lt;/code&gt; doctrine slot (with a canonical &lt;code dir=&quot;auto&quot;&gt;VALID_PATH_KEYS&lt;/code&gt; home in charter) lets org types declare their own path conventions. Full convergence onto charter &lt;code dir=&quot;auto&quot;&gt;ResolvedMissionType&lt;/code&gt; (retiring the legacy resolver + reconciling built-in doctrine data, which encodes a different concern than the legacy template list) is deferred to the #2652 epic. See ADR &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-09-20-1-canonical-mission-type-source.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The CLI no longer transmits a refresh or access token to a server the session was never authenticated against — closing both a credential-exfiltration vector and a self-hosted lockout class&lt;/strong&gt; (#4755; folds #4053, #4265). Four token-bearing auth flows — token refresh (&lt;code dir=&quot;auto&quot;&gt;/oauth/token&lt;/code&gt;), token revoke / &lt;code dir=&quot;auto&quot;&gt;auth logout&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;/oauth/revoke&lt;/code&gt;), membership rehydrate (&lt;code dir=&quot;auto&quot;&gt;/api/v1/me&lt;/code&gt;), and WebSocket token provisioning (&lt;code dir=&quot;auto&quot;&gt;/api/v1/ws-token&lt;/code&gt;) — built their target URL from &lt;code dir=&quot;auto&quot;&gt;get_saas_base_url()&lt;/code&gt; (env override or packaged default only), ignoring both the canonical &lt;code dir=&quot;auto&quot;&gt;resolve_server_target()&lt;/code&gt; (which honours &lt;code dir=&quot;auto&quot;&gt;config.toml [sync].server_url&lt;/code&gt;) and the session’s own &lt;code dir=&quot;auto&quot;&gt;issuer_url&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;auth login&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; were migrated to the resolver plus an issuer guard (#3406 / #234 / #4259); the paths that actually &lt;strong&gt;transmit&lt;/strong&gt; the tokens were skipped. &lt;strong&gt;Before:&lt;/strong&gt; a self-hosted operator configured only via &lt;code dir=&quot;auto&quot;&gt;config.toml&lt;/code&gt; had every refresh and every logout POST their long-lived refresh token to the packaged default host &lt;code dir=&quot;auto&quot;&gt;team.spec-kitty.ai&lt;/code&gt; — never reaching their own server — and the foreign host’s &lt;code dir=&quot;auto&quot;&gt;invalid_grant&lt;/code&gt; then wiped the local session, a forced re-login loop with the refresh token exposed to a host they never chose; and a hostile checkout shipping &lt;code dir=&quot;auto&quot;&gt;.kittify/.kitty.env&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL=&amp;#x3C;attacker&gt;&lt;/code&gt; exfiltrated the victim’s refresh token on &lt;code dir=&quot;auto&quot;&gt;auth logout&lt;/code&gt; (and the access token on any rehydrate), with the real server never receiving the revoke so the leaked token stayed valid. &lt;strong&gt;After:&lt;/strong&gt; every token-bearing flow resolves its endpoint through one canonical authority — &lt;code dir=&quot;auto&quot;&gt;specify_cli.auth.server_target.resolve_token_endpoint(session)&lt;/code&gt; — that targets the session’s &lt;code dir=&quot;auto&quot;&gt;issuer_url&lt;/code&gt;, &lt;strong&gt;refuses and transmits nothing&lt;/strong&gt; when the resolved target differs from the issuer (the same boundary &lt;code dir=&quot;auto&quot;&gt;auth login&lt;/code&gt; already enforced), and falls back to &lt;code dir=&quot;auto&quot;&gt;resolve_server_target(process_wide_override=False)&lt;/code&gt; only for legacy &lt;code dir=&quot;auto&quot;&gt;issuer_url=None&lt;/code&gt; sessions — never the packaged default. Each flow adapts the refusal to its own contract: refresh raises the new &lt;code dir=&quot;auto&quot;&gt;IssuerTargetMismatchError&lt;/code&gt; (now a member of &lt;code dir=&quot;auto&quot;&gt;saas_client&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;_dead_session_errors()&lt;/code&gt;, so the held-token fast path can no longer demote it into sending a still-valid access token); &lt;code dir=&quot;auto&quot;&gt;auth logout&lt;/code&gt; returns &lt;code dir=&quot;auto&quot;&gt;RevokeOutcome.ISSUER_MISMATCH&lt;/code&gt;, skips the remote revoke, still tears down local credentials, and warns the operator to rotate via the real server; membership rehydrate fail-closes to a specific, token-free warning; WebSocket provisioning raises &lt;code dir=&quot;auto&quot;&gt;WebSocketProvisioningError&lt;/code&gt;. The pre-existing &lt;code dir=&quot;auto&quot;&gt;saas_client._guard_session_issuer&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;auth login&lt;/code&gt; mismatch warning now consume the &lt;strong&gt;same&lt;/strong&gt; shared decision (one normalizer, one remedy token — no parallel copy), and &lt;code dir=&quot;auto&quot;&gt;get_saas_base_url()&lt;/code&gt; is fenced off every token-send path by a non-vacuous architectural gate (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_egress_consent_boundary.py&lt;/code&gt;) that fails both when a token-send module regains the call and when one is added to its allowlist. Refusal diagnostics never contain token material. Network-free reproductions for both live consequences are RED through the pre-existing entry points before the fix; the dormant ws path is covered by direct invocation (defence-in-depth). &lt;strong&gt;Folded same-seam cleanups:&lt;/strong&gt; #4053 removes a now-unreachable &lt;code dir=&quot;auto&quot;&gt;except ConfigurationError&lt;/code&gt; branch and fixes a no-opinion-default provenance mislabel in &lt;code dir=&quot;auto&quot;&gt;_auth_saas_target.py&lt;/code&gt;; #4265 makes the &lt;code dir=&quot;auto&quot;&gt;auth login&lt;/code&gt; issuer-mismatch refusal exit non-zero (so &lt;code dir=&quot;auto&quot;&gt;login &amp;#x26;&amp;#x26; …&lt;/code&gt; scripts stop) and switches its custom-endpoint label to a canonical-host comparison.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Local write-safety hardening: routine commands can no longer truncate an unrelated file, drop concurrent decision records, destroy operator-authored &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; content, or leave credentials/prompt files world-readable&lt;/strong&gt; (#4756, #4757, #4759, #4811, #4812, #4760, #4721; follow-up #4817). Seven defects across the CLI’s on-disk writes, closed under one theme — every write on a shared or pre-existing path now carries a safety envelope. &lt;strong&gt;#4756:&lt;/strong&gt; the canonical kernel lock primitive (&lt;code dir=&quot;auto&quot;&gt;kernel.locks&lt;/code&gt;) opens lock files &lt;code dir=&quot;auto&quot;&gt;O_NOFOLLOW&lt;/code&gt; at both &lt;code dir=&quot;auto&quot;&gt;open_fd&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;force_release&lt;/code&gt; (via a no-follow module hoisted to &lt;code dir=&quot;auto&quot;&gt;kernel.no_follow&lt;/code&gt;), and the cold-install sentinel moved out of world-shared &lt;code dir=&quot;auto&quot;&gt;$TMPDIR&lt;/code&gt; to a per-user &lt;code dir=&quot;auto&quot;&gt;0700&lt;/code&gt; root — a local user can no longer pre-plant a symlink and make another user’s &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; truncate an arbitrary victim-writable file. &lt;strong&gt;#4757:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt; read-modify-write is serialized at the service level via &lt;code dir=&quot;auto&quot;&gt;kernel.locks&lt;/code&gt; (8 concurrent decision opens previously collapsed to 1), and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor decisions [--repair]&lt;/code&gt; rebuilds a diverged index from the authoritative event log, refusing to silently mis-attribute a lossy &lt;code dir=&quot;auto&quot;&gt;slot_key&lt;/code&gt;-origin decision (upstream schema enrichment tracked in #4817). &lt;strong&gt;#4759:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; backs up operator-authored &lt;code dir=&quot;auto&quot;&gt;missions/&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;memory/&lt;/code&gt; to a timestamped &lt;code dir=&quot;auto&quot;&gt;.kittify/.backup-&amp;#x3C;ts&gt;/&lt;/code&gt; at every destructive site instead of &lt;code dir=&quot;auto&quot;&gt;rmtree&lt;/code&gt;-ing them, and the “already initialized” gate no longer keys solely on &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt;. &lt;strong&gt;#4811:&lt;/strong&gt; the last hand-rolled &lt;code dir=&quot;auto&quot;&gt;mission_state&lt;/code&gt; lock now routes through the canonical &lt;code dir=&quot;auto&quot;&gt;kernel.locks&lt;/code&gt; authority (symlink-safe; advisory truncate-and-reuse also clears a stale-lock wedge). &lt;strong&gt;#4812 + #4760:&lt;/strong&gt; credential files on the zeitgeist and tracker transports are created owner-only (&lt;code dir=&quot;auto&quot;&gt;0600&lt;/code&gt;) by construction — no &lt;code dir=&quot;auto&quot;&gt;write_text&lt;/code&gt;-then-&lt;code dir=&quot;auto&quot;&gt;chmod&lt;/code&gt; world-readable window — with a single canonical owner for &lt;code dir=&quot;auto&quot;&gt;~/.spec-kitty&lt;/code&gt; at &lt;code dir=&quot;auto&quot;&gt;0700&lt;/code&gt;. &lt;strong&gt;#4721:&lt;/strong&gt; prompt temp files are relocated under the per-user runtime root, written symlink-safe, and never world-readable. All changes are red-first tested (each defect’s exploit/data-loss reproduced against pre-fix code) and reviewed per work package.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter bundle validate&lt;/code&gt; no longer reports 2 false-positive errors per project directive, and no longer rejects the registration engine’s own &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; sidecars&lt;/strong&gt; (#4832, #4833; refs #4834). The scaffolder, registration engine, and bundle validator each independently derived a project artifact’s on-disk slug/filename, and the derivations disagreed. &lt;strong&gt;Before:&lt;/strong&gt; the validator’s filename parser did not match the engine’s own kebab-slug output (#4832), and its recognised-kind table covered only 3 of the 5 kinds the engine writes sidecars for, so it also rejected the engine’s own &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; sidecars outright — &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; was a latent identical twin of the same bug (#4833). &lt;strong&gt;After:&lt;/strong&gt; kebab-case is the single canonical slug convention, computed by one pure &lt;code dir=&quot;auto&quot;&gt;slug_for(kind, id)&lt;/code&gt; authority (&lt;code dir=&quot;auto&quot;&gt;src/charter/offering/artifact_kinds.py&lt;/code&gt;, preserving the engine’s existing &lt;code dir=&quot;auto&quot;&gt;quote(…, safe=&quot;&quot;)&lt;/code&gt; URL-encoding) shared by the scaffolder and the engine; the recognised-kind table is extended to the full 5 kinds behind one importable &lt;code dir=&quot;auto&quot;&gt;DIRECT_WRITE_KINDS&lt;/code&gt; constant with a parity test; and the validator resolves registered artifacts through the synthesis manifest (which already records the canonical slug) while retaining the filesystem walk for orphan/legacy detection. &lt;code dir=&quot;auto&quot;&gt;#4834&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;_registration_records&lt;/code&gt; path/provenance-drift re-write is fixed alongside it as an independent correctness fix. &lt;strong&gt;Go-forward only:&lt;/strong&gt; no filename migration ships — existing SCREAMING-filename repositories validate green via the manifest without any rename, since renaming a directive’s file stem risks silently dropping a stem-keyed activation (the #3816 class); see &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-09-21-1-kebab-canonical-doctrine-artifact-slug.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; no longer refuses to re-claim an approved work package with a bogus “review feedback artifact is missing” error, and a long review note can no longer drop the Team Kitty status moment&lt;/strong&gt; (#4801; refs #4327, closes the #3954 note-overflow class on the status-attr lane). The &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; status attribute is now a pointer only. &lt;strong&gt;Before:&lt;/strong&gt; when a work package was approved or rejected without an explicit &lt;code dir=&quot;auto&quot;&gt;--approval-ref&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--review-ref&lt;/code&gt;, the operator’s &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; prose was written into &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; itself — a long note overflowed the codec’s 240-UTF-8-byte wire attribute (the #3954 dropped/mangled-moment class), and on the read side an approved WP whose newest &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; was that prose made &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; try to resolve it as a feedback artifact and refuse the re-claim. &lt;strong&gt;After:&lt;/strong&gt; approval/rejection references carry only a real pointer or a synthetic marker token (&lt;code dir=&quot;auto&quot;&gt;approval:&amp;#x3C;WP&gt;&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;review:&amp;#x3C;WP&gt;&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;auto-approval:&amp;#x3C;WP&gt;:&amp;#x3C;date&gt;&lt;/code&gt;); the operator’s note stays whole in the durable &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt; (which the pinned codec keeps off the wire), the read seam skips the synthetic markers instead of mis-resolving them, and the #3954 interim wire-side truncation is removed so the events codec’s own byte bound is the single authority again. The one remaining prose path — an over-long &lt;code dir=&quot;auto&quot;&gt;--review-ref&lt;/code&gt; an operator types themselves — now fails closed loudly (logged warning, zero network attempts), never silently truncated or dropped.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; no longer blocks an approved work package that went through an ordinary review-rejection cycle with a “missing agent in canonical runtime state” refusal&lt;/strong&gt; (#4758, #4786). &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; is a &lt;em&gt;live-claim&lt;/em&gt; slot that legitimately changes hands between implementer and reviewer, and is correctly RELEASED when a review rejects a work package back to &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; (#4673) — that release was never the bug. &lt;strong&gt;Before:&lt;/strong&gt; once the claim was released, nothing recovered durable &lt;em&gt;implementer&lt;/em&gt; provenance, so a routine claim → for_review → reject → re-review → approve cycle (no fresh &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt; on the return legs) reached &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; reporting the work package as unowned, even though it had been fully implemented and reviewed — forcing an operator to hand-replant a claim just to unblock acceptance. &lt;strong&gt;After:&lt;/strong&gt; a new read-root projection (&lt;code dir=&quot;auto&quot;&gt;status/reducer.py::_project_implementer_attribution&lt;/code&gt;, a sibling of the existing cancellation-provenance projection) re-derives “who claimed this work package as implementer” from the immutable &lt;code dir=&quot;auto&quot;&gt;planned -&gt; claimed&lt;/code&gt; event in the raw log — never from the live, release-able &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; slot — and the accept gate (&lt;code dir=&quot;auto&quot;&gt;acceptance/summary_core.py&lt;/code&gt;) reads it through a shared accessor as a fallback when the live claim has been released. A work package that was genuinely never claimed still refuses honestly (no fabricated owner), and the refusal now names the repair that actually re-establishes the slot — a same-lane &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task &amp;#x3C;wp&gt; --to &amp;#x3C;lane&gt; --agent &amp;#x3C;name&gt;&lt;/code&gt; re-plant (the #3029 remedy), not &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt; (which rebuilds &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, not claims, and so cannot recover a missing implementer). &lt;code dir=&quot;auto&quot;&gt;status doctor&lt;/code&gt;’s blanked-runtime-slot detector (&lt;code dir=&quot;auto&quot;&gt;status/doctor.py&lt;/code&gt;) is narrowed to match: a blank &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; explained by the derived provenance is no longer reported as corrupt canonical state. A related crash in &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge --mission&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; — an unresolved Typer &lt;code dir=&quot;auto&quot;&gt;OptionInfo&lt;/code&gt; sentinel reaching &lt;code dir=&quot;auto&quot;&gt;.strip()&lt;/code&gt; when the mission flag is threaded through a direct Python call rather than the CLI — is also guarded, falling through cleanly instead of raising &lt;code dir=&quot;auto&quot;&gt;AttributeError&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The pre-review regression gate no longer fires in a consumer repo that never declared a review test command&lt;/strong&gt; (#3821). The gate binding ships built-in with the &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; review contract, so binding resolution alone could not tell a repo that configured a gate from one that never did. &lt;strong&gt;Before:&lt;/strong&gt; moving a work package to &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; in a repo with no declared &lt;code dir=&quot;auto&quot;&gt;review.test_command&lt;/code&gt; still tried to run the gate and surfaced an internal-sounding &lt;code dir=&quot;auto&quot;&gt;no_coverage&lt;/code&gt; concern, leaking a gate the repo never asked for. &lt;strong&gt;After:&lt;/strong&gt; the repo’s own declaration is the signal — the move probes the same activation-selected test-command authority the dispatch would use, and when the binding is active but nothing is declared it records one quiet &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt; verdict (no console line, a calm consumer-facing reason that names no internal concept) instead of dispatching. A configured-but-malformed &lt;code dir=&quot;auto&quot;&gt;review.test_command&lt;/code&gt; still counts as declared, so a broken declaration surfaces a visible warning rather than a silent skip; a repo that did declare the gate is unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A failed charter preflight under &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; now says &lt;code dir=&quot;auto&quot;&gt;consumer=next&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;consumer=dashboard&lt;/code&gt;&lt;/strong&gt; (#4731). Query mode (&lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; without &lt;code dir=&quot;auto&quot;&gt;--result&lt;/code&gt;) is read-only, so it reuses the dashboard’s warn-and-continue preflight helper. &lt;strong&gt;Before:&lt;/strong&gt; that helper hardcoded its own name in the log line it emits, so the only charter output an operator saw from &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; was labelled as the dashboard’s — misleading when working out which surface tripped the preflight. &lt;strong&gt;After:&lt;/strong&gt; the helper takes the consumer name from its caller (still &lt;code dir=&quot;auto&quot;&gt;dashboard&lt;/code&gt; by default), and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; passes its own, so the warning names the command you actually ran. The remediation text, the warn-and-continue behaviour, and the dashboard’s own label are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces --fix&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; now repair every detected-stale agent surface and converge in one run&lt;/strong&gt;: root-level orientation files (GEMINI.md, LLXPRT.md) refresh regardless of a harness command dir; the managed-skills completion re-check and the doctrine command-parent check are host-aware so Windows upgrades converge in one pass (command + doctrine skills) with no phantom dry-run repairs; command-skills manifest content is deterministic; residual drift is reported as a failure instead of exit-0 (#4782, #4776, #4777, #4134).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --yes&lt;/code&gt; is now fully non-interactive, and a non-interactive confirmation that hits EOF cancels cleanly instead of crashing&lt;/strong&gt; (#4775). Two prompt sites called bare &lt;code dir=&quot;auto&quot;&gt;typer.confirm&lt;/code&gt;, which raises &lt;code dir=&quot;auto&quot;&gt;typer.Abort&lt;/code&gt; on Ctrl-C or when reading hits EOF (a closed/non-interactive stdin) — uncaught, which crashes an otherwise-successful upgrade. &lt;strong&gt;Before:&lt;/strong&gt; (a) the &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; consent flag (&lt;code dir=&quot;auto&quot;&gt;confirm&lt;/code&gt;) was wired to the migration-apply decision (&lt;code dir=&quot;auto&quot;&gt;assume_yes&lt;/code&gt;) but never to the mission-state repair sub-gate’s own opt-in (&lt;code dir=&quot;auto&quot;&gt;repair_opt_in&lt;/code&gt;, defaulted &lt;code dir=&quot;auto&quot;&gt;False&lt;/code&gt;), so &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt; at an interactive TTY still asked &lt;code dir=&quot;auto&quot;&gt;Run &apos;spec-kitty doctor mission-state --fix&apos; now?&lt;/code&gt;; (b) both that prompt and the separate &lt;code dir=&quot;auto&quot;&gt;Apply N migration(s)?&lt;/code&gt; confirmation had no EOF/abort handling. &lt;strong&gt;After:&lt;/strong&gt; a shared &lt;code dir=&quot;auto&quot;&gt;safe_confirm(prompt, *, default)&lt;/code&gt; helper (&lt;code dir=&quot;auto&quot;&gt;_teamspace_mission_state_gate.py&lt;/code&gt;) wraps &lt;code dir=&quot;auto&quot;&gt;typer.confirm&lt;/code&gt;, explicitly catching &lt;code dir=&quot;auto&quot;&gt;typer.Abort&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;EOFError&lt;/code&gt; (never a bare &lt;code dir=&quot;auto&quot;&gt;except Exception&lt;/code&gt; — any other exception still propagates) and folding either into a plain decline; both prompt sites route through it, and &lt;code dir=&quot;auto&quot;&gt;upgrade.py&lt;/code&gt;’s finalizer now wires &lt;code dir=&quot;auto&quot;&gt;repair_opt_in=confirm&lt;/code&gt; alongside the existing &lt;code dir=&quot;auto&quot;&gt;assume_yes=confirm&lt;/code&gt;, so &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; skips the repair sub-gate’s prompt too. &lt;strong&gt;Behavior delta (automation-visible):&lt;/strong&gt; a non-interactive caller that omits &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt; with pending migrations and hits EOF at the &lt;code dir=&quot;auto&quot;&gt;Apply N migration(s)?&lt;/code&gt; prompt now prints &lt;code dir=&quot;auto&quot;&gt;Upgrade cancelled.&lt;/code&gt; and exits &lt;strong&gt;0&lt;/strong&gt; (previously an uncaught &lt;code dir=&quot;auto&quot;&gt;Abort&lt;/code&gt; crash). FR-014’s existing repair-failure/exit-code isolation (&lt;code dir=&quot;auto&quot;&gt;upgrade/outcome.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;upgrade/finalize.py&lt;/code&gt;) is unchanged and unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activating a built-in charter directive now keeps the compiled &lt;code dir=&quot;auto&quot;&gt;catalog.references&lt;/code&gt; coherent by construction, and charter authoring is worktree-safe&lt;/strong&gt; (#4785; folds the CLI-write half of #4250). Four coupled tooling gaps are closed. &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt;&lt;/strong&gt; — &lt;strong&gt;Before:&lt;/strong&gt; a config-only write that left &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;’s compiled &lt;code dir=&quot;auto&quot;&gt;catalog.references&lt;/code&gt; stale, tripping the suite-tier coherence guard (the #2524 dangler class); only &lt;code dir=&quot;auto&quot;&gt;--resynthesize&lt;/code&gt; recompiled. &lt;strong&gt;After:&lt;/strong&gt; activation/deactivation recompile the catalog by default through the single &lt;code dir=&quot;auto&quot;&gt;compile_charter&lt;/code&gt; authority (the &lt;code dir=&quot;auto&quot;&gt;charter pack apply --compile&lt;/code&gt; pattern, &lt;code dir=&quot;auto&quot;&gt;from_interview=False&lt;/code&gt;) when a compiled &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; already exists, so the coherence guard stays green with no manual edit; a new &lt;code dir=&quot;auto&quot;&gt;--no-compile&lt;/code&gt; flag preserves the fast config-only write with an explicit “not recompiled” notice (a not-yet-synthesized config-only project is left untouched — no bootstrap, no activation-authority split). &lt;strong&gt;Remediation guidance&lt;/strong&gt; — &lt;strong&gt;Before:&lt;/strong&gt; the coherence-guard message and &lt;code dir=&quot;auto&quot;&gt;--resynthesize&lt;/code&gt; help pointed operators at &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;, which is architecturally incapable of recompiling &lt;code dir=&quot;auto&quot;&gt;catalog.references&lt;/code&gt; and, on an established store with no &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/&lt;/code&gt;, short-circuited to a fresh-project seed. &lt;strong&gt;After:&lt;/strong&gt; the guard message and help name &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt;’s fresh-project detection keys on actual catalog establishment (an active &lt;code dir=&quot;auto&quot;&gt;activated_*&lt;/code&gt; entry, or a real prior synthesis manifest with interview answers), not on &lt;code dir=&quot;auto&quot;&gt;generated/&lt;/code&gt; absence, so an established store is no longer misclassified while a genuinely-incomplete store is still repaired. &lt;strong&gt;Worktree safety&lt;/strong&gt; — &lt;strong&gt;Before:&lt;/strong&gt; charter write commands (&lt;code dir=&quot;auto&quot;&gt;activate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;resynthesize&lt;/code&gt;) resolved the project root to the PRIMARY checkout, so running from a linked git worktree silently wrote into the primary repo. &lt;strong&gt;After:&lt;/strong&gt; they fail closed from a linked worktree (“use a repository-root checkout or dedicated clone for charter authoring”, non-zero exit) via a shared resolver built on the kernel &lt;code dir=&quot;auto&quot;&gt;git_topology&lt;/code&gt; probe (git-dir vs git-common-dir; git-absent degrades safely), and the &lt;code dir=&quot;auto&quot;&gt;activate --resynthesize&lt;/code&gt; chdir split-brain is eliminated. &lt;strong&gt;Complete summaries&lt;/strong&gt; — &lt;strong&gt;Before:&lt;/strong&gt; a full recompile left directive entries reading &lt;code dir=&quot;auto&quot;&gt;summary: Definition unavailable in bundled doctrine.&lt;/code&gt; when the transitive-closure surfaced a directive absent from the activation-filtered doctrine repository. &lt;strong&gt;After:&lt;/strong&gt; summary lookup routes through the raw (unfiltered) doctrine repository, so transitively-reached directives resolve to their real summary, a genuinely-unresolvable id is reported through the existing unresolved-reference diagnostics (never a silent placeholder row), catalog membership is unchanged (still driven by the DRG closure), and &lt;code dir=&quot;auto&quot;&gt;catalog.references&lt;/code&gt; is emitted in a canonical deterministic order with &lt;code dir=&quot;auto&quot;&gt;metadata.generated_at&lt;/code&gt; preserved when the catalog is byte-unchanged. The dead, uncalled &lt;code dir=&quot;auto&quot;&gt;_build_references_from_yaml&lt;/code&gt; reference-builder is removed. &lt;strong&gt;Known cost:&lt;/strong&gt; recompile-on-activate adds ~2.4–2.5 s (the single-authority &lt;code dir=&quot;auto&quot;&gt;compile_charter&lt;/code&gt; DRG/doctrine resolution) — accepted over a competing minimal-writer, which the charter’s single-canonical-authority principle forbids. Cross-referenced, out of scope: #4250’s hosted-binding-recovery half + saas#1713; the synthesize-recovery siblings #4042/#4226; the generate-honesty siblings #4618/#4615/#4614.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;merge --abort&lt;/code&gt; no longer silently destroy uncommitted operator work&lt;/strong&gt; (#4752, #4753, #4754). Three merge/abort-lifecycle paths fired destructive git commands against operator state with no dirty/branch/state guard. &lt;strong&gt;Before:&lt;/strong&gt; (a) &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; ran &lt;code dir=&quot;auto&quot;&gt;git reset --hard HEAD&lt;/code&gt; on the repository-root checkout unconditionally after advancing the target ref — a checkout on another branch with uncommitted tracked edits lost them, and the merge then crashed mid-bookkeeping with a raw &lt;code dir=&quot;auto&quot;&gt;SafeCommitHeadMismatch&lt;/code&gt; (#4752); (b) lane cleanup ran &lt;code dir=&quot;auto&quot;&gt;git worktree remove --force&lt;/code&gt; on every lane worktree with no dirty check, deleting uncommitted implementer work never on the lane branch, exit 0 (#4753); (c) &lt;code dir=&quot;auto&quot;&gt;merge --abort&lt;/code&gt; ran &lt;code dir=&quot;auto&quot;&gt;git merge --abort&lt;/code&gt; on the primary checkout whenever &lt;code dir=&quot;auto&quot;&gt;MERGE_HEAD&lt;/code&gt; existed — even with no spec-kitty merge state — destroying the user’s own in-progress merge while printing “No active merge state to abort.” immediately followed by “Aborted in-progress git merge.” (#4754). &lt;strong&gt;After:&lt;/strong&gt; a single git-plumbing-pure refuse-before-destroy guard (&lt;code dir=&quot;auto&quot;&gt;git/destructive_guard.py&lt;/code&gt;, reusing &lt;code dir=&quot;auto&quot;&gt;ref_advance._dirty_entries&lt;/code&gt; with the injected toolchain-churn classifier — no new parallel dirty predicate) runs as a pre-mutation preflight before any ref advance: &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; refuses fail-closed and byte-identical to pre-invocation when the primary checkout is off-target or dirty, or when any lane/coord worktree is dirty and removal is requested (&lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; honors the same guard); lane, coordination, and orchestrator-api worktree removal all route through &lt;code dir=&quot;auto&quot;&gt;guarded_worktree_remove&lt;/code&gt; so a dirty worktree is never force-removed and the coordination triple is held back atomically; and &lt;code dir=&quot;auto&quot;&gt;merge --abort&lt;/code&gt; aborts a git merge only when active spec-kitty merge state exists, scoped to the merge workspace, never &lt;code dir=&quot;auto&quot;&gt;repo_root&lt;/code&gt;. The defect class is closed by construction by a non-vacuous architectural routing gate (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_destructive_op_routing.py&lt;/code&gt;, proven fail-able by self-mutation). Deferred with rationale: standalone &lt;code dir=&quot;auto&quot;&gt;git branch -D&lt;/code&gt; unmerged-commit loss (a distinct loss surface needing an is-branch-merged guard) is tracked as a follow-up mission.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; under the default &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt; gate mode no longer consolidates an unapproved mission and wedges it beyond recovery&lt;/strong&gt; (#4764). &lt;strong&gt;Before:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;policy.merge_gates.mode: warn&lt;/code&gt; (the default), a merge on a mission whose work packages were still &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; printed the missing-approval gate as a &lt;em&gt;warning&lt;/em&gt;, then went ahead and consolidated the lane branches onto the coordination branch and baked &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; into the coord &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; — and only then failed the post-merge backstop with exit 1, rolling nothing back. The lane was left with zero commits beyond coordination (so the &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; gate rejected it forever), coord and primary &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; disagreed on &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; (split-brain), and the work package could never be reviewed again without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; or hand git surgery — and the unreviewed code was now on the mission branch a later successful merge would squash to the mainline. &lt;strong&gt;After:&lt;/strong&gt; an unconditional &lt;em&gt;merge-ready&lt;/em&gt; precondition (&lt;code dir=&quot;auto&quot;&gt;_assert_mission_terminal_ready&lt;/code&gt;) runs before any mutation, regardless of gate mode: if any non-cancelled work package is not &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; (a work package with no status event is treated as not-ready, never silently dropped), the merge refuses with exit 1 naming the missing work packages and changes nothing. &lt;code dir=&quot;auto&quot;&gt;warn&lt;/code&gt; still softens evidence-&lt;em&gt;quality&lt;/em&gt; gates (review verdict, risk, hollow-review); it can no longer soften the terminal-lane invariant. As defense-in-depth, the lane-consolidation and primary-tree &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; bake are wrapped in a transactional rollback that resets the coordination ref/worktree &lt;strong&gt;and&lt;/strong&gt; the target branch on a post-mutation failure, so a later failure can no longer strand the mission or orphan a bookkeeping commit on the target branch. Red-first &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.regression&lt;/code&gt; coverage drives the real &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; entry point.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty mission close&lt;/code&gt; (without &lt;code dir=&quot;auto&quot;&gt;--discard&lt;/code&gt;) on an unmerged in-flight mission is refused instead of fabricating a completion record on the mainline&lt;/strong&gt; (#4765). &lt;strong&gt;Before:&lt;/strong&gt; it exited 0, printed “closed”, committed a &lt;code dir=&quot;auto&quot;&gt;retrospective.yaml&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;kind: runtime_post_completion&lt;/code&gt; to the target branch, and tore down the coordination worktree — despite its own &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; promising it “requires that the mission has already been merged”; &lt;code dir=&quot;auto&quot;&gt;retrospect summary&lt;/code&gt; and downstream tooling then counted the in-flight mission as completed, and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; reported it blocked until the operator guessed to re-run &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the non-discard path checks &lt;code dir=&quot;auto&quot;&gt;is_mission_merged&lt;/code&gt; before any write; an unmerged mission is refused with exit 1 pointing at &lt;code dir=&quot;auto&quot;&gt;--discard&lt;/code&gt;, writing no retrospective, emitting no &lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptured&lt;/code&gt; event, and leaving the coordination worktree intact. The guard keys on &lt;em&gt;merged&lt;/em&gt; (a recorded merge baseline), not &lt;em&gt;all-terminal&lt;/em&gt;, so an all-cancelled-but-unmerged mission is correctly sent to &lt;code dir=&quot;auto&quot;&gt;--discard&lt;/code&gt; rather than torn down as a completion. A genuinely-merged mission still runs the teardown as before.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A successful merge no longer silently loses &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; on a coordination-topology mission&lt;/strong&gt; (#4474). &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; write-back composed the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; path inside the detached mission-branch worktree and, when it was absent there — which on a coordination topology it structurally is, because &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is a primary-partition artifact — logged a warning and returned without writing, so &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; was lost everywhere and &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; stayed stuck at &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt; forever (the opposite failure mode from #4764’s too-early bake). &lt;strong&gt;After:&lt;/strong&gt; the bake is topology-aware — it writes and commits &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; to the primary checkout’s own &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; (where a coordination mission’s canonical copy lives); only when no reachable surface exists does it fall back to an observable merge-summary notice instead of a silent log-only skip. The &lt;code dir=&quot;auto&quot;&gt;path_is_under_worktrees&lt;/code&gt; guard is preserved, and the bake now participates in the merge rollback (above) so a failed merge never orphans the number on the target branch.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A mission whose work was implemented directly on the target branch can now be completed and closed cleanly, and its half-termination paths are made safe&lt;/strong&gt; (#2745, facets 1 &amp;#x26; 3). &lt;strong&gt;Before:&lt;/strong&gt; the sanctioned direct-on-target fallback (a work package committed on the target branch with no lane branch) was a dead end — &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; hard-failed on the missing lane branch, and &lt;code dir=&quot;auto&quot;&gt;mission close&lt;/code&gt; choked on an orphaned &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt; marker (with a doubled slug and no &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;); worse, a completion on that path could half-terminate the mission. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge --skip-lanes&lt;/code&gt; (alias &lt;code dir=&quot;auto&quot;&gt;--no-lanes&lt;/code&gt;) transactionally completes a merge-ready direct-on-target mission with no lane branch — while still enforcing the merge-ready precondition (no bypass), so a not-merge-ready mission refuses &lt;em&gt;before&lt;/em&gt; advancing the target ref (making the half-terminated state unreachable), and the choice is persisted so &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; honors it without re-passing the flag; &lt;code dir=&quot;auto&quot;&gt;mission close&lt;/code&gt; tolerates an orphaned coordination-branch marker without a traceback, renders the mission slug once, and honors &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;. Consolidation: all three terminus commands (&lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission close&lt;/code&gt;) now derive terminal readiness from one shared authority — the per-lane &lt;code dir=&quot;auto&quot;&gt;is_acceptable_ending&lt;/code&gt; predicate plus a new provenance-aware &lt;code dir=&quot;auto&quot;&gt;mission_terminal_acceptability&lt;/code&gt; aggregate — rather than re-inlined loops, and the duplicate terminal-lane set in &lt;code dir=&quot;auto&quot;&gt;status/doctor.py&lt;/code&gt; was retired. The direct-on-target rollback-&lt;em&gt;after&lt;/em&gt;-target-advance arm is tracked as a follow-up under epic #3897; the refuse-before-advance guard keeps the interim state safe. Red-first &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.regression&lt;/code&gt; coverage per facet.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; on a protected-primary mission with no lane branch already names a followable escape hatch — verified, no code change needed&lt;/strong&gt; (#2745 facet 2, FR-014). Liveness confirmation: the historical impossible guidance (“run status commit operations from the mission lane branch/worktree” — impossible to satisfy when no lane branch exists) was already replaced by &lt;code dir=&quot;auto&quot;&gt;accept.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt; routing, whose refusal now names a concrete, followable command (&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission finalize-tasks --mission &amp;#x3C;slug&gt; --target-branch &amp;#x3C;feature-branch&gt;&lt;/code&gt;) or the documented &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS=1&lt;/code&gt; env hatch. A new &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.regression&lt;/code&gt; probe (&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/cli/commands/test_accept_guidance_liveness.py&lt;/code&gt;) pins this as an enduring guard against regressing back to the impossible instruction.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A single canonical guarded-read + CLI error-presentation seam replaces the scattered per-command crash/emitter patchwork&lt;/strong&gt; (umbrella #2899; children #4746/#4738/#4724/#4637/#4739/#4720). A format-agnostic kernel primitive, &lt;code dir=&quot;auto&quot;&gt;kernel.guarded_read.read_guarded(path, parse, *, errors=(), error_cls=GuardedReadError, mode=&quot;text&quot;)&lt;/code&gt;, reads a file once and collapses &lt;code dir=&quot;auto&quot;&gt;(OSError, UnicodeDecodeError, *caller-declared exceptions)&lt;/code&gt; into one typed &lt;code dir=&quot;auto&quot;&gt;GuardedReadError&lt;/code&gt; subclass (chained via &lt;code dir=&quot;auto&quot;&gt;raise ... from exc&lt;/code&gt;); a single global Typer error-presentation hook registered on the top-level &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; app catches the &lt;code dir=&quot;auto&quot;&gt;GuardedReadError&lt;/code&gt; family and renders a clean &lt;code dir=&quot;auto&quot;&gt;Error: &amp;#x3C;reason&gt;&lt;/code&gt; line (stderr, exit 1) or a &lt;code dir=&quot;auto&quot;&gt;{&quot;error&quot;, &quot;kind&quot;, &quot;path&quot;}&lt;/code&gt; JSON object (stdout, exit 1) under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; — a Typer usage error keeps its existing exit 2 unchanged, and any non-domain exception still re-raises as a traceback. The 7 pre-existing typed reader errors (&lt;code dir=&quot;auto&quot;&gt;MissionMetaReadError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DecisionIndexReadError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;CorruptLanesError&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;MissingLanesError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;AgentConfigError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;UnsafePathSegmentError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;IntakeFileUnreadableError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;kernel.meta_decode.MetaDecodeError&lt;/code&gt;) are re-parented onto &lt;code dir=&quot;auto&quot;&gt;GuardedReadError&lt;/code&gt; &lt;strong&gt;in place&lt;/strong&gt; via multiple inheritance — every pre-existing &lt;code dir=&quot;auto&quot;&gt;except &amp;#x3C;LegacyError&gt;&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;except ValueError&lt;/code&gt; call site (the &lt;code dir=&quot;auto&quot;&gt;UnsafePathSegmentError&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;MetaDecodeError&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt; contract is preserved) keeps matching, verified by a dedicated back-compat regression over the ~85-site caller census. Every in-scope command adopts the seam, so a bad file/handle/stream now yields a clean actionable error instead of a raw traceback: &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;workflow import&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;export&lt;/code&gt;&lt;/strong&gt; on malformed/wrong-schema/wrong-type/unreadable YAML (#4738), &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission close&lt;/code&gt;&lt;/strong&gt; and &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;&lt;/strong&gt; on an invalid &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; (plus the &lt;code dir=&quot;auto&quot;&gt;-f&lt;/code&gt;=&lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; footgun removed on all four sites) (#4724), &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent release prep&lt;/code&gt;&lt;/strong&gt; on a missing/incomplete/malformed &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; (#4637), &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;intake -&lt;/code&gt;&lt;/strong&gt; on non-UTF-8 stdin (now at parity with the file path) (#4739), and &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify --json&lt;/code&gt;&lt;/strong&gt; name validation — which now raises a hook-owned domain error instead of a &lt;code dir=&quot;auto&quot;&gt;typer.BadParameter&lt;/code&gt; Rich panel, emits a proper JSON error object, and &lt;strong&gt;rejects non-ASCII names explicitly&lt;/strong&gt; with no silent character loss (#4720). Seven still-unguarded state readers (&lt;code dir=&quot;auto&quot;&gt;decisions/service&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge/state&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review/{baseline,lock,artifacts}&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status/validate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;core/wps_manifest&lt;/code&gt;) are hardened through the primitive while preserving each reader’s missing-vs-corrupt return contract, and the &lt;code dir=&quot;auto&quot;&gt;runtime_bridge&lt;/code&gt; requirement-mapping mask is narrowed so a corrupt work-package manifest surfaces as a typed finding (#4746). The class is closed &lt;strong&gt;by construction&lt;/strong&gt;: a non-vacuous architectural gate (&lt;code dir=&quot;auto&quot;&gt;test_cli_error_surface_seam.py&lt;/code&gt;, proven fail-able by a self-mutation test) rejects any new in-scope command that reads/decodes/resolves outside the primitive or drops the global hook. &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;’s existing bespoke emitters, the residual &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;(exit 2)/others(exit 1) inconsistency, and the org-pack cascade non-vacuity reds surfaced during the mission (#4773) are tracked as explicit follow-ups, not silently folded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty routes&lt;/code&gt; in a checkout with no &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt; remote now tells you to add one, instead of sending you to a “Spec Kitty mission repository” you are already in&lt;/strong&gt; (#4626). &lt;strong&gt;Before:&lt;/strong&gt; the error diagnosed the cause correctly (no &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt; remote) but closed with “run this from inside a Spec Kitty mission repository”, and Rich swallowed the &lt;code dir=&quot;auto&quot;&gt;[kitty &quot;quarantine&quot;]&lt;/code&gt; config-section name as markup, leaving an unexplained “no quarantine record”. &lt;strong&gt;After:&lt;/strong&gt; the message ends with the fix that matches the diagnosis — add an &lt;code dir=&quot;auto&quot;&gt;origin&lt;/code&gt; remote (&lt;code dir=&quot;auto&quot;&gt;git remote add origin &amp;#x3C;url&gt;&lt;/code&gt;); repository identity is derived from it, never from the directory name — and the quarantine record is named as what it is (a &lt;code dir=&quot;auto&quot;&gt;[kitty &quot;quarantine&quot;]&lt;/code&gt; record in &lt;code dir=&quot;auto&quot;&gt;.git/config&lt;/code&gt; preserving a former origin). The refusal itself is unchanged: an identity is still never minted from a directory name.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CLI hints that name a &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.&amp;#x3C;command&gt;&lt;/code&gt; slash command now say it runs inside your coding agent, not in the shell&lt;/strong&gt; (#4624). Several error and next-step messages listed a slash command next to shell commands with nothing to tell them apart, and typing the slash command into a terminal fails with “no such file or directory”. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate&lt;/code&gt; without interview answers said “Run &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.charter&lt;/code&gt; so the agent can capture guidance, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter interview --defaults&lt;/code&gt; …” as if both were shell commands. &lt;strong&gt;After:&lt;/strong&gt; every such hint names the surface — “Run &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.charter&lt;/code&gt; inside your coding agent (Claude Code, Codex, Cursor) … run &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter interview --defaults&lt;/code&gt; here …” — across &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, the plan-unfilled check, the mission-ticket and removed-&lt;code dir=&quot;auto&quot;&gt;mission switch&lt;/code&gt; hints, the &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; mission-template note, the implement analysis gate, and the dashboard’s next-action line. Shell alternatives are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status&lt;/code&gt; no longer needs &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; when there is only one active mission&lt;/strong&gt; (#4677). &lt;strong&gt;Before:&lt;/strong&gt; the help’s own first example (&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status&lt;/code&gt;) exited 1 with &lt;code dir=&quot;auto&quot;&gt;--mission &amp;#x3C;slug&gt; is required&lt;/code&gt;, even in a project with a single mission, and &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; was listed as an ordinary option. &lt;strong&gt;After:&lt;/strong&gt; with exactly one mission that is not completed (merged, or every work package terminal), the command defaults to it; with zero or several active missions the existing error is unchanged, and the help now says when the flag can be omitted.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A corrupt per-mission state file fails closed with a clean operator error instead of crashing with a raw traceback&lt;/strong&gt; (#4642). A malformed-JSON, non-UTF-8, or wrong-shape &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt; (realistic after a partial write or merge conflict) crashed two command paths. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; — the central agent control loop — died with an uncaught &lt;code dir=&quot;auto&quot;&gt;MissionMetaReadError&lt;/code&gt; traceback on a corrupt &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent decision verify&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;resolve&lt;/code&gt; (and the other decision subcommands) died with a raw &lt;code dir=&quot;auto&quot;&gt;JSONDecodeError&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;UnicodeDecodeError&lt;/code&gt;/pydantic &lt;code dir=&quot;auto&quot;&gt;ValidationError&lt;/code&gt; on a corrupt &lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; both fail closed — a single operator-readable error naming the corrupt file plus the &lt;code dir=&quot;auto&quot;&gt;run: spec-kitty doctor&lt;/code&gt; hint, exit 1, no traceback (a valid JSON error payload under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; now catches &lt;code dir=&quot;auto&quot;&gt;MissionMetaReadError&lt;/code&gt; at the real downstream escape site (the query-mode/&lt;code dir=&quot;auto&quot;&gt;decide_next&lt;/code&gt; calls, not the slug-resolution guard), and &lt;code dir=&quot;auto&quot;&gt;decisions/store.py:load_index&lt;/code&gt; wraps its decode/validate into a typed &lt;code dir=&quot;auto&quot;&gt;DecisionIndexReadError&lt;/code&gt; (reusing the canonical kernel decoder), fixing all six decision subcommands at the one reader. The four &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; decision write verbs (open/resolve/defer/cancel-decision) — a JSON-first machine-contract surface — now fail closed with a valid error payload too, instead of leaking a raw traceback with empty output. Mirrors the existing &lt;code dir=&quot;auto&quot;&gt;MissionMetaReadError&lt;/code&gt; precedent; the remaining un-guarded readers (the interview and accept-gate command paths) are tracked as a follow-up hardening mission subsuming #4600 and #4642. Red-first &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.regression&lt;/code&gt; coverage drives the real commands over all three corruption classes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --help&lt;/code&gt; points at documentation that exists again&lt;/strong&gt; (#4688). Its “See also” line named &lt;code dir=&quot;auto&quot;&gt;docs/guides/install-and-upgrade.md&lt;/code&gt;, a path that no longer exists; it now names &lt;code dir=&quot;auto&quot;&gt;docs/guides/how-to/installation/install-and-upgrade.md&lt;/code&gt;, where the install-and-upgrade guide lives, and a test keeps every documentation path in that help text honest.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter sync&lt;/code&gt; now says it is a no-op instead of looking like a failure&lt;/strong&gt; (#4679). The command is kept for compatibility only: the charter.md-to-YAML extraction it used to perform is retired, so there is never anything to sync. &lt;strong&gt;Before:&lt;/strong&gt; it printed a red &lt;code dir=&quot;auto&quot;&gt;Charter was not synced&lt;/code&gt; and exited 1 (or reported &lt;code dir=&quot;auto&quot;&gt;success: false&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;), which reads as something to fix. &lt;strong&gt;After:&lt;/strong&gt; it prints an explicit &lt;code dir=&quot;auto&quot;&gt;No-op:&lt;/code&gt; line and exits 0, &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; reports &lt;code dir=&quot;auto&quot;&gt;result: &quot;noop&quot;&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;success: true&lt;/code&gt; with the same message, and the &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; text and &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; description no longer claim it syncs anything.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A bare &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt; no longer looks like a passing health check&lt;/strong&gt; (#4678). The group runs nothing by itself — every diagnostic is a subcommand. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt; printed the help and exited 0, indistinguishable from a check that ran and passed. &lt;strong&gt;After:&lt;/strong&gt; it still lists the available diagnostics, but states that no diagnostic ran and exits 2 (usage error), so neither a person nor a script can mistake it for a clean bill of health. Every &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor &amp;#x3C;subcommand&gt;&lt;/code&gt; is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops --close-stale&lt;/code&gt; no longer slows down quadratically as the closure history grows&lt;/strong&gt; (#4424). A sweep closes each stale Op through one executor, but the shared idempotency guard re-read the entire append-only closure spine (&lt;code dir=&quot;auto&quot;&gt;kitty-ops/op-closures.jsonl&lt;/code&gt;) once per Op. &lt;strong&gt;Before:&lt;/strong&gt; closing N stale Ops re-parsed the ever-growing spine N times — O(N²) — so a large backlog on a long-lived project made the sweep drag. &lt;strong&gt;After:&lt;/strong&gt; the sweep reads the spine once into a per-run snapshot and extends it after each close, so the whole sweep is linear; a pinning test asserts exactly one spine read per sweep. The individual-agent close path is unchanged (it reads fresh — a single close has no such cost), and Op-close idempotency is preserved.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The session orientation block can report &lt;code dir=&quot;auto&quot;&gt;upgrade-available&lt;/code&gt; again instead of always saying &lt;code dir=&quot;auto&quot;&gt;healthy&lt;/code&gt;&lt;/strong&gt; (#4707). The banner derives its health from a background version cache, but that cache was written for the stable channel only and an out-of-date cached version was never refreshed — so the health line was pinned to &lt;code dir=&quot;auto&quot;&gt;(healthy)&lt;/code&gt; even when an upgrade was published. &lt;strong&gt;Before:&lt;/strong&gt; the orientation block never surfaced an available upgrade. &lt;strong&gt;After:&lt;/strong&gt; the cache refresh queries the configured release channel and records that channel with the result, a cache written for a different channel is rejected, and a cache past its TTL triggers a background refresh while still returning the last known version — so &lt;code dir=&quot;auto&quot;&gt;health&lt;/code&gt; reflects a real upgrade. SessionStart stays free of foreground network calls (the refresh is a detached, fire-and-forget subprocess, at most one per session).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A yanked pre-release no longer shadows the real latest version on the pre-release channel&lt;/strong&gt; (#4705). Version selection took the highest version across every entry in PyPI’s release list, without checking whether any of its files were still installable — so a fully &lt;strong&gt;yanked&lt;/strong&gt; pre-release (&lt;code dir=&quot;auto&quot;&gt;4.2.0a1&lt;/code&gt;) outranked the live &lt;code dir=&quot;auto&quot;&gt;4.0.0rc3&lt;/code&gt;, even though &lt;code dir=&quot;auto&quot;&gt;pip&lt;/code&gt;, reading the same index, correctly skips it. &lt;strong&gt;Before:&lt;/strong&gt; an opted-in pre-release user was told to “upgrade” to a version that cannot be installed. &lt;strong&gt;After:&lt;/strong&gt; a shared &lt;code dir=&quot;auto&quot;&gt;installable_release_versions()&lt;/code&gt; filter (PEP 592) drops releases that have no files or only yanked files before picking the highest, and both the compatibility provider and the background upgrade probe use it, so they never disagree on what is installable. The stable channel is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --cli&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;upgrade --dry-run --json&lt;/code&gt; report the real latest version again when output is piped or &lt;code dir=&quot;auto&quot;&gt;CI&lt;/code&gt; is set&lt;/strong&gt; (#4704). These are the environments agents and CI actually run in, and an explicit upgrade query is exactly when you want the answer. &lt;strong&gt;Before:&lt;/strong&gt; an over-correction (the earlier RISK-3 nag-suppression fix) routed explicit queries through the same network suppression as the passive per-command nag, so under a redirected stdout or &lt;code dir=&quot;auto&quot;&gt;CI=1&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;upgrade --cli&lt;/code&gt; printed no guidance and &lt;code dir=&quot;auto&quot;&gt;upgrade --dry-run --json&lt;/code&gt; reported a null version and &lt;code dir=&quot;auto&quot;&gt;is_outdated: false&lt;/code&gt; — silently wrong. &lt;strong&gt;After:&lt;/strong&gt; an explicit query resolves the latest published version regardless of TTY/CI (fail-soft — the provider has a 2-second timeout and returns nothing on error), while the passive nag stays suppressed exactly as before and the read-only query never writes the nag cache. Nag preferences and a fresh nag cache no longer mask the factual status of an explicit query.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent action implement --agent &amp;#x3C;tool:model:profile:role&gt;&lt;/code&gt; completes on first use instead of rejecting its own claim&lt;/strong&gt; (#4665). A fresh implementation claim with the documented compact agent identity created the lane, moved the WP to &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt;, then refused its own claim and printed no prompt. &lt;strong&gt;Before:&lt;/strong&gt; the compact-string workspace-create claim recorded the actor verbatim while the workflow claim recorded a structured dict; the ownership comparison projected the dict to its bare tool but the string verbatim, so the two representations of one agent compared unequal and raised &lt;code dir=&quot;auto&quot;&gt;WorkPackageClaimConflict&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the CLI-local claim-comparison layer (&lt;code dir=&quot;auto&quot;&gt;_actor_key&lt;/code&gt;) parses a compact-string actor to the same tool-scoped key a dict yields, so a first-time full-identity claim renders the prompt in one invocation; same-identity resume stays idempotent, a genuinely different agent is still refused, the generic-actor re-claim allowance is preserved, and the shared identity projection is left byte-unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An agent’s review verdict is attributed to the reviewing agent, not the configured Git user&lt;/strong&gt; (#4670). The generated review-completion command omitted &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt;, so running it recorded the verdict as &lt;code dir=&quot;auto&quot;&gt;actor.tool: user&lt;/code&gt; with null model/profile even though an independent agent performed the review. &lt;strong&gt;Before:&lt;/strong&gt; approvals and rejections were misattributed to the Git user whenever the generated command was used as printed. &lt;strong&gt;After:&lt;/strong&gt; an agent-driven completion that omits &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt; resolves the active claimed reviewer from the event log, and the generated completion commands (both approve and the &lt;code dir=&quot;auto&quot;&gt;--to planned&lt;/code&gt; rejection) carry the resolved identity through a single render seam; genuine human approvals stay attributed to the human, the review evidence is retained, and no historical event is rewritten.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A fix-mode implementation claim after a rejection records the new implementer, so the correction submits for review without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;&lt;/strong&gt; (#4673). After a reviewer rejected a WP and an implementer successfully claimed it in fix mode, the reduced ownership still pointed at the previous reviewer and the ordinary &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review --agent &amp;#x3C;implementer&gt;&lt;/code&gt; was refused. &lt;strong&gt;Before:&lt;/strong&gt; the rejection’s runtime delta re-stamped the reviewer into the very delta that released the claim (defeating the release), and the move-task ownership guard compared identities by raw string. &lt;strong&gt;After:&lt;/strong&gt; the rejection no longer re-stamps the reviewer when the same identity rolls the WP back (the release takes effect), the fix-mode claim’s owner folds through the same latest-wins per-transition channel the role slot already uses, and the move-task ownership guard reconciles identity representations through the tool-scoped key; a genuinely different agent is still refused.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;move-task --agent &amp;#x3C;identity&gt;&lt;/code&gt; persists the acting identity into the reduced ownership slot&lt;/strong&gt; (#3029, representation half — verified). The originally-reported “no agent key at all” symptom is stale on the 4.0.0rc4 line: the claim fold and the per-transition runtime delta already persist the acting identity, and a downstream ownership check enforces it (a differing agent is refused). A characterization regression pins the behavior; no code change was required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The session orientation block shows your real project name again instead of &lt;code dir=&quot;auto&quot;&gt;project: unknown&lt;/code&gt;&lt;/strong&gt; (#4706). The SessionStart banner read the project slug off &lt;code dir=&quot;auto&quot;&gt;AgentConfig&lt;/code&gt;, which has no such field, so it always fell back to &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt; (a regression introduced in 3.2.7). &lt;strong&gt;Before:&lt;/strong&gt; every session opened with &lt;code dir=&quot;auto&quot;&gt;project: unknown (healthy)&lt;/code&gt; regardless of the project you were in. &lt;strong&gt;After:&lt;/strong&gt; the banner reads &lt;code dir=&quot;auto&quot;&gt;project.slug&lt;/code&gt; through the canonical project-identity loader (&lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;) — the same source the rest of the CLI uses — and the dry-run preview now reads that same source too, so live and preview agree. A project without a persisted slug still renders &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;, which is the honest value.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shell-completion help text is refreshed, and a stale completion manifest can no longer sit red on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; unnoticed&lt;/strong&gt; (#4479; narrow part of #4374). The pre-generated completion manifest (&lt;code dir=&quot;auto&quot;&gt;_completion_manifest.json&lt;/code&gt;, shipped in the wheel so &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; shell completion serves command metadata without importing the whole CLI) had drifted from the live CLI help in four commands: &lt;code dir=&quot;auto&quot;&gt;agent tests stale-check&lt;/code&gt; was missing its &lt;code dir=&quot;auto&quot;&gt;info&lt;/code&gt; confidence level, &lt;code dir=&quot;auto&quot;&gt;context info&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;context mission-resolve&lt;/code&gt; still carried legacy &lt;code dir=&quot;auto&quot;&gt;feature&lt;/code&gt; wording and example slugs (&lt;code dir=&quot;auto&quot;&gt;010-feature-lane-a&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;057-my-feature&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;zeitgeist status&lt;/code&gt; showed an outdated one-line description. &lt;strong&gt;Before:&lt;/strong&gt; the drift only reddened under &lt;code dir=&quot;auto&quot;&gt;make test-full&lt;/code&gt; — the parity test’s directory is recorded out-of-matrix, so no per-PR lane selected it, and the sibling CLI-reference gate checks command-path presence but not help &lt;em&gt;text&lt;/em&gt; — so it sat red on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; unnoticed. &lt;strong&gt;After:&lt;/strong&gt; the manifest is regenerated to match the live help (which also clears the forbidden &lt;code dir=&quot;auto&quot;&gt;feature&lt;/code&gt; wording from a shipped file), and a new always-on architectural gate (&lt;code dir=&quot;auto&quot;&gt;test_completion_manifest_freshness.py&lt;/code&gt;) reds every PR the moment the manifest drifts, help text included. The full 128-directory out-of-matrix promotion/retire sweep (#4374) remains a separate mission.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Spec Kitty is usable on Windows again — every command stopped failing with &lt;code dir=&quot;auto&quot;&gt;[Errno 13] Permission denied&lt;/code&gt;&lt;/strong&gt; (#4703). On Windows &lt;code dir=&quot;auto&quot;&gt;msvcrt.locking()&lt;/code&gt; is a &lt;em&gt;mandatory&lt;/em&gt; lock, so when the runtime bootstrap held its own owner lock file (&lt;code dir=&quot;auto&quot;&gt;%LOCALAPPDATA%\spec-kitty\cache\.update.lock&lt;/code&gt;) and then re-read that same file during asset verification, the OS refused the read even to the locking process. &lt;strong&gt;Before:&lt;/strong&gt; on 4.0.0rc3/rc4 every command except &lt;code dir=&quot;auto&quot;&gt;--version&lt;/code&gt; aborted with &lt;code dir=&quot;auto&quot;&gt;RuntimeError: [Errno 13] Permission denied&lt;/code&gt; and exit 1 — &lt;code dir=&quot;auto&quot;&gt;ensure_runtime()&lt;/code&gt; runs before every command, so the tool was completely unusable on Windows (3.2.7 worked; the regression arrived with the #4017 re-assess-under-lock landing, whose under-lock recheck first read the held lock — POSIX &lt;code dir=&quot;auto&quot;&gt;flock&lt;/code&gt; is advisory so the read succeeds there, which is why CI never caught it). &lt;strong&gt;After:&lt;/strong&gt; the under-lock recheck no longer reads an owner lock file’s own bytes in any of the three places it was read — &lt;code dir=&quot;auto&quot;&gt;check_assets&lt;/code&gt; skips the lock node (its parent directory’s membership is still verified), and both the re-assessment’s &lt;code dir=&quot;auto&quot;&gt;finish()&lt;/code&gt; and the batch-owner &lt;code dir=&quot;auto&quot;&gt;include()&lt;/code&gt; fallback record the lock by &lt;code dir=&quot;auto&quot;&gt;lstat&lt;/code&gt; only (&lt;code dir=&quot;auto&quot;&gt;node_state(..., read_content=False)&lt;/code&gt;). A lock file is a self-managed, definitionally-empty artifact whose content is never verified or used, so source-drift and concurrent-peer detection are unchanged. All three sites are shared across owners (runtime, global skills, global commands), so the same one fix covers every asset owner.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A swallowed asset-read failure now names the file it could not read&lt;/strong&gt; (#4703). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;PermissionError&lt;/code&gt; during recheck surfaced as the bare &lt;code dir=&quot;auto&quot;&gt;[Errno 13] Permission denied&lt;/code&gt; — a Windows &lt;code dir=&quot;auto&quot;&gt;PermissionError&lt;/code&gt; drops &lt;code dir=&quot;auto&quot;&gt;exc.filename&lt;/code&gt;, so the diagnostic named no path and the failure was undiagnosable as shipped. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;check_assets&lt;/code&gt; annotates a read failure with the offending path (&lt;code dir=&quot;auto&quot;&gt;Could not read global asset &amp;#x3C;path&gt;: ...&lt;/code&gt;), which also sharpens diagnosis for the wider “Global asset input changed” recheck family (#3998, #4017).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty session-start&lt;/code&gt; honours its unconditional exit-0 contract again&lt;/strong&gt; (#4703). The Claude Code &lt;code dir=&quot;auto&quot;&gt;SessionStart&lt;/code&gt; hook documents that it must never fail a session, but its exit-0 guard could not catch a failure in &lt;code dir=&quot;auto&quot;&gt;main_callback&lt;/code&gt; &lt;em&gt;before&lt;/em&gt; dispatch. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;ensure_runtime()&lt;/code&gt; (the Windows crash above) or the startup schema gate (&lt;code dir=&quot;auto&quot;&gt;SystemExit&lt;/code&gt; on a stale project) aborted the hook with exit 1. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;session-start&lt;/code&gt; gets the same startup-fast-path posture as the live-work hook — neither the global runtime repair nor the startup project gates run before it — so &lt;code dir=&quot;auto&quot;&gt;session_start()&lt;/code&gt; alone owns the exit-0 guarantee.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Upgrade/repair can delete read-only managed assets on Windows&lt;/strong&gt; (#4703 cross-OS family). Managed content is materialized read-only (&lt;code dir=&quot;auto&quot;&gt;0o444&lt;/code&gt;); Windows &lt;code dir=&quot;auto&quot;&gt;DeleteFile&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;RemoveDirectory&lt;/code&gt; refuse a read-only target (POSIX ignores the mode). &lt;strong&gt;Before:&lt;/strong&gt; an upgrade or skill re-install that removed a stale managed asset could crash with &lt;code dir=&quot;auto&quot;&gt;PermissionError&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; every managed-asset delete (in &lt;code dir=&quot;auto&quot;&gt;runtime/asset_preparation.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;skills/installer.py&lt;/code&gt;) clears the write bit and retries — the same pattern already used for skill teardown, now applied to the delete sites that were missed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The owner lock is acquired through a writable handle&lt;/strong&gt; (#4703 cross-OS family). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;recheck_assets&lt;/code&gt; opened the lock read-only to lock it; POSIX &lt;code dir=&quot;auto&quot;&gt;flock&lt;/code&gt; allows that, but Windows &lt;code dir=&quot;auto&quot;&gt;msvcrt.locking()&lt;/code&gt; needs write access and is fragile on a read-only handle. &lt;strong&gt;After:&lt;/strong&gt; the recheck opens the existing lock &lt;code dir=&quot;auto&quot;&gt;r+&lt;/code&gt;, aligning with the apply path’s write handle.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cold installs serialize concurrent runs on Windows too&lt;/strong&gt; (#4703 cross-OS family). &lt;strong&gt;Before:&lt;/strong&gt; the cold-install serializer flock’d the anchor directory, which is POSIX-only — a first-time Windows install had no cross-process guard, so two concurrent cold installs could race. &lt;strong&gt;After:&lt;/strong&gt; on Windows a machine-temp sentinel keyed to the anchor (kept out of the managed asset tree) serializes cold installers; the exclusive owner-lock create remains the final arbiter. (A related symlink-creation fallback for Windows without developer-mode privilege is tracked as a follow-up: a naive symlink→copy in the managed-asset writer would make re-assessment see a file where it expects a symlink and re-apply forever, so it needs the assessor’s cooperation.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The cross-OS lock, safe-delete, and OS-detection primitives now have one canonical owner each — the recurring Windows &lt;code dir=&quot;auto&quot;&gt;PermissionError&lt;/code&gt; class (root of #4703) is closed by construction&lt;/strong&gt; (#4714). #4703 kept recurring because file-locking, managed-asset deletion, and Windows detection were forked across the runtime with no canonical owner, so any site could reintroduce the mandatory-lock read crash or a boundary-leaking delete. &lt;strong&gt;Before:&lt;/strong&gt; ~12 lock sites across three families (raw &lt;code dir=&quot;auto&quot;&gt;msvcrt&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fcntl&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;filelock&lt;/code&gt; library, a scoped &lt;code dir=&quot;auto&quot;&gt;fcntl&lt;/code&gt;); 3 duplicate safe-delete helpers with a silent contract split (one followed symlinks and cleared the &lt;em&gt;target’s&lt;/em&gt; write bit, a boundary leak); and 4 &lt;code dir=&quot;auto&quot;&gt;is_windows&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;os.name&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;sys.platform&lt;/code&gt; definitions. &lt;strong&gt;After:&lt;/strong&gt; (1) one sync+async, sidecar-model lock primitive in &lt;code dir=&quot;auto&quot;&gt;kernel/locks.py&lt;/code&gt; that &lt;strong&gt;structurally cannot expose a held lock for reading&lt;/strong&gt; — it yields only holder metadata, never a handle to the protected file, and derives/locks a dedicated &lt;code dir=&quot;auto&quot;&gt;.lock&lt;/code&gt; sidecar, so the #4703 read-your-own-held-lock shape is impossible by construction; (2) one &lt;code dir=&quot;auto&quot;&gt;specify_cli/core/safe_delete.py&lt;/code&gt; with the correct no-follow (&lt;code dir=&quot;auto&quot;&gt;lstat&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;S_IMODE&lt;/code&gt;, skip-symlink) contract; (3) one promoted &lt;code dir=&quot;auto&quot;&gt;kernel/paths.py::is_windows()&lt;/code&gt; seam that the routable OS-detection zoo now calls. Two non-vacuous DIRECTIVE_043 gates (&lt;code dir=&quot;auto&quot;&gt;test_lock_primitive_ban.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_os_detection_ban.py&lt;/code&gt;) ban raw locking and inline OS-detection outside their canonical modules and fail on any new site (empty allowlists). &lt;code dir=&quot;auto&quot;&gt;filelock&lt;/code&gt; is removed entirely — from runtime dependencies &lt;strong&gt;and&lt;/strong&gt; the four test-infrastructure users, which migrated onto &lt;code dir=&quot;auto&quot;&gt;kernel.locks&lt;/code&gt; (closes #4719). Also folded: &lt;code dir=&quot;auto&quot;&gt;tracker/credentials&lt;/code&gt; now locks a sidecar instead of the credential payload (closing the #4703 shape there too); the kernel lock primitive hardens only lock directories it creates (never a shared cache dir); and the cold-install serializer uses one uniform machine-temp sentinel on both Windows and POSIX. Follow-up: #4727 (&lt;code dir=&quot;auto&quot;&gt;windows_paths._current_platform&lt;/code&gt; 3-way normalizer, gate-tracked fail-closed).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consistent mission-handle resolution across CLI commands&lt;/strong&gt; (#4631, #4682). A nonexistent &lt;code dir=&quot;auto&quot;&gt;--mission &amp;#x3C;handle&gt;&lt;/code&gt; now produces one clear &lt;code dir=&quot;auto&quot;&gt;Mission not found: &amp;#x3C;handle&gt;&lt;/code&gt; across &lt;code dir=&quot;auto&quot;&gt;research&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;, and &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; (fresh and &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt;), matching the commands that were already correct. Previously &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; misreported it as a multi-mission “pass —mission to disambiguate” ambiguity, &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; blamed a missing &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, and — most seriously — &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; silently scaffolded a phantom &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;handle&gt;/&lt;/code&gt; mission directory. &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; (and every in-scope command) now refuses before writing anything; &lt;code dir=&quot;auto&quot;&gt;merge --abort&lt;/code&gt; stays tolerant of an unresolvable handle; the identity-aware “run &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-identity&lt;/code&gt;” remediation and &lt;code dir=&quot;auto&quot;&gt;reconcile&lt;/code&gt;’s distinct “dossier not found” wording are preserved. Bare &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; (no &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;) now discovers missions — auto-selecting the sole mission, listing available handles (&lt;code dir=&quot;auto&quot;&gt;slug (mid8) — name&lt;/code&gt;, legacy missions included) when several exist, or pointing to &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; when none do — instead of dead-ending on a &lt;code dir=&quot;auto&quot;&gt;--mission is required&lt;/code&gt; usage error.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An ambiguous &lt;code dir=&quot;auto&quot;&gt;--mission &amp;#x3C;handle&gt;&lt;/code&gt; now says so instead of “not found”&lt;/strong&gt; (#4723). When a bare human slug matches more than one mission (e.g. two &lt;code dir=&quot;auto&quot;&gt;payment-*&lt;/code&gt; missions, both typed as &lt;code dir=&quot;auto&quot;&gt;--mission payment&lt;/code&gt;), every command &lt;strong&gt;before&lt;/strong&gt; reported &lt;code dir=&quot;auto&quot;&gt;Mission not found: payment&lt;/code&gt; — telling you nothing matched when in fact several did, and pointing at a recovery command that could not reveal the collision. &lt;strong&gt;After:&lt;/strong&gt; the commands surface the ambiguity (&lt;code dir=&quot;auto&quot;&gt;Mission handle &apos;payment&apos; matches multiple missions: … — re-run with a more specific handle&lt;/code&gt;) and name the colliding handles, matching how an ambiguous &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt;/numeric handle already behaved. The misleading not-found hint also changed from &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission list&lt;/code&gt; (which lists mission &lt;em&gt;types&lt;/em&gt;) to &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor topology&lt;/code&gt; (which lists real mission handles).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-state&lt;/code&gt; now repairs a legacy &lt;code dir=&quot;auto&quot;&gt;change_mode&lt;/code&gt; instead of aborting, normalizing it to absent&lt;/strong&gt;; &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--teamspace-dry-run&lt;/code&gt; report per-mission detail in the terminal and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; (dry-run parity), so triage no longer requires reading a gitignored manifest; aligned the bulk-edit-gate reader so normalization is behavior-preserving (#4778, #4780, #4779).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The issue-matrix approval gate no longer forces a false work-outcome verdict on issues cited only for context or as PR references, and &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; now accepts the natural &lt;code dir=&quot;auto&quot;&gt;--actor&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--reason&lt;/code&gt; flag names&lt;/strong&gt; (#3469). &lt;strong&gt;Before:&lt;/strong&gt; every discovered &lt;code dir=&quot;auto&quot;&gt;#NNNN&lt;/code&gt; reference — including parent-epic citations, &lt;code dir=&quot;auto&quot;&gt;see #NNNN&lt;/code&gt; context markers, and &lt;code dir=&quot;auto&quot;&gt;PR #NNNN&lt;/code&gt; links — scaffolded a &lt;strong&gt;gating&lt;/strong&gt; row in &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt;, and the four-value verdict vocabulary (&lt;code dir=&quot;auto&quot;&gt;fixed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;verified-already-fixed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;deferred-with-followup&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt;) had no truthful value for “cited, no work owed” — forcing an operator to either stall the mission or record a false verdict into the audit artifact; separately, &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; accepted only &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt;, rejecting the &lt;code dir=&quot;auto&quot;&gt;--actor&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--reason&lt;/code&gt; names its sibling &lt;code dir=&quot;auto&quot;&gt;issue-verdict&lt;/code&gt; already uses, and its &lt;code dir=&quot;auto&quot;&gt;--assignee&lt;/code&gt; help text still described a stale &lt;code dir=&quot;auto&quot;&gt;doing&lt;/code&gt;-only restriction. &lt;strong&gt;After:&lt;/strong&gt; a single shared classification function — consumed identically by the approval blocker, &lt;code dir=&quot;auto&quot;&gt;merge_gates&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status/doctor&lt;/code&gt;, and the post-merge mission-review gate (one gating decision across every site, never re-derived per-site) — demotes a reference to non-gating only on an explicit signal (a &lt;code dir=&quot;auto&quot;&gt;PR &lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;pull&lt;/code&gt; token, a cross-repo URL, or a context-label marker: &lt;code dir=&quot;auto&quot;&gt;Follow-up:&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;baseline-red&lt;/code&gt;, a leading &lt;code dir=&quot;auto&quot;&gt;see #&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;parent&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;epic&lt;/code&gt; used as a citation label immediately before the reference) and defaults every unmarked bare &lt;code dir=&quot;auto&quot;&gt;#NNNN&lt;/code&gt; to gating (fail-safe preserved; a line that merely contains the ordinary word “parent”/“epic”/“see” around a real work target still gates; classification aggregates over all occurrences, so a reference cited once as context and once as an implementation target still gates); a new &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt;&lt;/strong&gt; verdict value (additive, zero migration for existing &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; files) records the truth for a non-gating row and is terminal — it passes the &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;/merge boundary unchanged, unlike &lt;code dir=&quot;auto&quot;&gt;in-mission&lt;/code&gt;, which is still rejected there; &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; now accepts &lt;code dir=&quot;auto&quot;&gt;--actor&lt;/code&gt; (alias of &lt;code dir=&quot;auto&quot;&gt;--agent&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;--reason&lt;/code&gt; (alias of &lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; — the last-given spelling wins when both are passed), and its &lt;code dir=&quot;auto&quot;&gt;--assignee&lt;/code&gt; help text now describes the actual any-lane behavior; &lt;code dir=&quot;auto&quot;&gt;issue-verdict --help&lt;/code&gt; documents both &lt;code dir=&quot;auto&quot;&gt;not-applicable&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;deferred-with-followup&lt;/code&gt; evidence-token rule (&lt;code dir=&quot;auto&quot;&gt;#NNN&lt;/code&gt; or a literal &lt;code dir=&quot;auto&quot;&gt;Follow-up:&lt;/code&gt; token); and the specify/plan/tasks/analyze prompts now carry a non-gating heads-up that approvals require issue-matrix verdicts for referenced implementation issues. See the &lt;a href=&quot;/development/reference/issue-matrix-verdicts/&quot;&gt;issue-matrix verdict reference&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;400rc3---2026-09-15&quot;&gt;[4.0.0rc3] - 2026-09-15&lt;/h2&gt;
&lt;p&gt;Third public release candidate for the Team Kitty 4.x line, cut from &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; for
the MVP launch cold-start walkthrough. This is a testing prerelease, not stable
launch acceptance. Install explicitly with &lt;code dir=&quot;auto&quot;&gt;uv tool install &apos;spec-kitty-cli==4.0.0rc3&apos;&lt;/code&gt;.&lt;/p&gt;
&lt;h3 id=&quot;changed-4&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Built-in minutes agent is now &lt;code dir=&quot;auto&quot;&gt;minutes-mahad&lt;/code&gt; (chat-first, dual format).&lt;/strong&gt; The profile formerly shipped as &lt;code dir=&quot;auto&quot;&gt;minutes-maker-mahad&lt;/code&gt; is renamed to &lt;code dir=&quot;auto&quot;&gt;minutes-mahad&lt;/code&gt; / Minutes Mahad. It asks whether to produce decision minutes or discussion notes, posts one validated Markdown response in the originating chat, and treats wiki/knowledge-base publication as optional human-operated reuse of that Markdown. Companion doctrine: &lt;code dir=&quot;auto&quot;&gt;ACTION_ITEM_ATTRIBUTION&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MINUTES_STAND_ALONE&lt;/code&gt;, paradigm &lt;code dir=&quot;auto&quot;&gt;extract-then-publish-separation&lt;/code&gt;, updated &lt;code dir=&quot;auto&quot;&gt;meeting-minutes-pipeline&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;meeting-minutes-format&lt;/code&gt;, and templates &lt;code dir=&quot;auto&quot;&gt;meeting-minutes.md&lt;/code&gt; plus &lt;code dir=&quot;auto&quot;&gt;meeting-discussion-notes.md&lt;/code&gt;. No Confluence, MCP, or vendor publisher is shipped in the built-in pack.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The release runbook now opens the next development cycle right after every tag&lt;/strong&gt; (#4314). &lt;code dir=&quot;auto&quot;&gt;RELEASE_CHECKLIST.md&lt;/code&gt; gains Release Process step 8, “Open the Next Development Cycle”, mirrored in the Release Process summary in &lt;code dir=&quot;auto&quot;&gt;docs/development/contributing.md&lt;/code&gt;. Branch-mode release validation requires &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;’s version to advance beyond the latest tag, so the scheduled Release Readiness Check went red after &lt;code dir=&quot;auto&quot;&gt;v4.0.0rc1&lt;/code&gt; and again after &lt;code dir=&quot;auto&quot;&gt;v4.0.0rc2&lt;/code&gt; until the next cycle opened (#4290, fixed for rc3 by #4313). The step lists the edits that open a cycle — the next version in &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;, the project entry in &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;, and a new &lt;code dir=&quot;auto&quot;&gt;## [Unreleased] - &amp;#x3C;next version&gt;&lt;/code&gt; heading — and a release test now pins it in both documents.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A green test run no longer counts as a typecheck when a mission changes typed sources (&lt;code dir=&quot;auto&quot;&gt;#4191&lt;/code&gt;; DIRECTIVE_030).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; the quality gate treated the test runner as the whole story, so a work package whose Vitest/Jest/pytest suite passed could be handed off and accepted even though the project’s compiler would have flagged unused locals/parameters or other diagnostics a runner never applies. &lt;strong&gt;After:&lt;/strong&gt; DIRECTIVE_030, the implement/review/accept skills, the quality-gate-verification tactic, and the software-dev work-package template all state that when typed sources change the implementer runs the project’s configured compiler typecheck (&lt;code dir=&quot;auto&quot;&gt;npm run typecheck&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tsc -b&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;tsc --noEmit&lt;/code&gt;, matching CI) and records its exit code, and a reviewer rejects a work package where that check was skipped, is red, or was masked by a fallback command. This is doctrine/prompt guidance only — no CLI behavior changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Every pull request now measures its tests once instead of twice&lt;/strong&gt; (#4334). The per-PR SonarCloud reporter in &lt;code dir=&quot;auto&quot;&gt;ci-quality.yml&lt;/code&gt; re-ran the fast test tier under coverage to build its own report — a median of &lt;strong&gt;22m32s&lt;/strong&gt; per pull request (n=12, 2026-09-10..14) duplicating work the &lt;code dir=&quot;auto&quot;&gt;CI Modules&lt;/code&gt; shard matrix had already done for the same commit. That job is retired; the per-change report is now a &lt;code dir=&quot;auto&quot;&gt;sonar-pr&lt;/code&gt; job in &lt;code dir=&quot;auto&quot;&gt;ci-aggregate.yml&lt;/code&gt; consuming the coverage the matrix already produced, on the existing &lt;code dir=&quot;auto&quot;&gt;workflow_run&lt;/code&gt; chain. &lt;code dir=&quot;auto&quot;&gt;ci-quality.yml&lt;/code&gt; drops from six jobs to five.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coverage measurement is no longer truncated at module boundaries&lt;/strong&gt; (#4334). Each shard measured only its own module’s package, so a line a test executed in &lt;em&gt;another&lt;/em&gt; module was silently &lt;strong&gt;dropped&lt;/strong&gt; rather than recorded as uncovered — leaving 58 of 72 &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; subpackages measured only through one broad-target row whose tests do not exercise them. Shards now measure the full top-level package set derived from &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;; one representative shard alone recovered &lt;strong&gt;30,226&lt;/strong&gt; cross-module covered statements. Registry &lt;code dir=&quot;auto&quot;&gt;cov_targets&lt;/code&gt; keep their meaning as census-derived ownership records and are unchanged. Measured cost is &lt;strong&gt;+7.8% to +11.6%&lt;/strong&gt; per shard with the reconciled artefact set growing roughly six-fold — traded deliberately for measurement accuracy.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;tests/unit&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/runtime&lt;/code&gt; are declared in the CI module registry&lt;/strong&gt; (#4334). They previously ran per-change only through the retired job’s fast tier, so retiring it would have removed their per-change execution.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Four census-count architectural gates that demanded manual re-pins on ordinary changes are retired, keeping only checks with a real defect-catch record&lt;/strong&gt; (#4315, adjudicated by ADR &lt;code dir=&quot;auto&quot;&gt;2026-09-14-1&lt;/code&gt;). The routed-&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;-read floor (&lt;code dir=&quot;auto&quot;&gt;ROUTED_LOAD_META_FLOOR&lt;/code&gt;) is deleted outright rather than re-pinned — it had been re-pinned 23 times in 63 days for zero catches, and once failed a build for reading &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; through the canonical reader the gate exists to reward; re-pinning it would only keep its vocabulary and ADR alive as load-bearing for the next person to move the count. The advisory golden-count gate is deleted outright, and its 381 &lt;code dir=&quot;auto&quot;&gt;# golden-count: cardinality-is-contract&lt;/code&gt; annotations are swept from 190 test files; the C-007 enforcement canon it sat beside is preserved. The &lt;code dir=&quot;auto&quot;&gt;arch_shard_*&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;next_shard_*&lt;/code&gt; marker family and its hand-maintained assignment tables are removed — no live CI job has selected those shards since the pre-programme workflows were deleted. The genuinely protective checks — the inline-&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;-read ceiling with its allowlist stale-entry detection, the tier-marker and module-shard completeness gates, and the four enforcement allowlists — are untouched and still blocking. Net: ~2,050 fewer lines of gate machinery and zero new pinned integers. Supersedes #3977 and #3927.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-5&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor bytecode&lt;/code&gt; flags a corrupt installed-package &lt;code dir=&quot;auto&quot;&gt;.pyc&lt;/code&gt; before it crashes every command&lt;/strong&gt; (#4130; complements #4124). A truncated &lt;code dir=&quot;auto&quot;&gt;pip&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;uv tool install&lt;/code&gt; write — common on Windows under file-locking or antivirus — can leave a &lt;code dir=&quot;auto&quot;&gt;__pycache__/*.pyc&lt;/code&gt; whose 16-byte header Python still trusts but whose body no longer unmarshals, so the next import dies with a raw &lt;code dir=&quot;auto&quot;&gt;bad marshal data&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;co_filename&lt;/code&gt; traceback that names no fix and takes down &lt;em&gt;every&lt;/em&gt; command, not just the one that touched the cache. The reactive self-heal from #4124 recovers at crash time; this adds the proactive counterpart — a read-only audit that scans the installed package and reports each corrupt cache file with a delete-the-&lt;code dir=&quot;auto&quot;&gt;.pyc&lt;/code&gt; hint (Python recompiles from source on the next import), in human or &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; form. A cache Python would recompile anyway (bad magic, stale timestamp/size) is deliberately not flagged, since it never bites. The command never deletes anything and exits 1 when a finding is present, so CI can gate on it.&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 decision list&lt;/code&gt; lists a mission’s recorded decision moments&lt;/strong&gt; (#3951). The &lt;code dir=&quot;auto&quot;&gt;agent decision&lt;/code&gt; subgroup previously had no read command — an orchestrating agent asking “what decisions exist for this mission” hit &lt;code dir=&quot;auto&quot;&gt;No such command&lt;/code&gt; and had to read &lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt; by hand. The new read-only subcommand resolves the mission through the same guarded read-path seam as &lt;code dir=&quot;auto&quot;&gt;verify&lt;/code&gt;, supports an optional &lt;code dir=&quot;auto&quot;&gt;--status open|resolved|deferred|canceled&lt;/code&gt; filter, and emits one JSON document (&lt;code dir=&quot;auto&quot;&gt;decision_list_v1&lt;/code&gt;) with the count and each decision’s id, status, question, and answer fields; a mission with no decisions yet lists cleanly with count 0.&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; publishes the six runtime moments to the team’s Zeitgeist relay&lt;/strong&gt; (#3929): mission run started/completed, step issued/auto-completed, and decision input requested/answered. A producer registered at the runtime emitter seam publishes each transition the runtime journals through the existing bounded lifecycle fan-out, under the journal record’s own timestamp and an &lt;code dir=&quot;auto&quot;&gt;event_id&lt;/code&gt; derived from that record, so a re-emitted transition is the same moment. Decision question, option and answer text stay out of moment attrs, and relay or credential failures never change local runtime state.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;LLxprt Code (&lt;code dir=&quot;auto&quot;&gt;--ai llxprt&lt;/code&gt;) is now a supported agent.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty init --ai llxprt&lt;/code&gt; installs the canonical Spec Kitty slash commands as TOML custom commands under &lt;code dir=&quot;auto&quot;&gt;.llxprt/commands/&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config add llxprt&lt;/code&gt; wires it into an existing project. LLxprt Code is a fork of Gemini CLI, so it reads the same command schema (&lt;code dir=&quot;auto&quot;&gt;prompt&lt;/code&gt;, optional &lt;code dir=&quot;auto&quot;&gt;description&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;{{args}}&lt;/code&gt; placeholder) and the commands appear as &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.*&lt;/code&gt;. User-global commands are installed to the envPaths(‘llxprt-code’) config root (&lt;code dir=&quot;auto&quot;&gt;~/Library/Preferences/llxprt-code/commands/&lt;/code&gt; on macOS, &lt;code dir=&quot;auto&quot;&gt;~/.config/llxprt-code/commands/&lt;/code&gt; on Linux, overridable via &lt;code dir=&quot;auto&quot;&gt;LLXPRT_CONFIG_HOME&lt;/code&gt;) — the legacy &lt;code dir=&quot;auto&quot;&gt;~/.llxprt/&lt;/code&gt; tree is migrated away by llxprt itself and is no longer read. LLxprt also consumes &lt;code dir=&quot;auto&quot;&gt;SKILL.md&lt;/code&gt; Agent Skills, so it is registered as a shared-root skill agent (&lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; plus its own &lt;code dir=&quot;auto&quot;&gt;.llxprt/skills/&lt;/code&gt;): an llxprt project now receives the Spec Kitty skill pack in the cross-tool &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; root, and skill upgrades also sweep &lt;code dir=&quot;auto&quot;&gt;.llxprt/skills/&lt;/code&gt;. Session presence writes to &lt;code dir=&quot;auto&quot;&gt;LLXPRT.md&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty verify-setup&lt;/code&gt; reports whether the &lt;code dir=&quot;auto&quot;&gt;llxprt&lt;/code&gt; binary is installed. The charter agent dispatch matrix now also instructs an agent to call &lt;code dir=&quot;auto&quot;&gt;todo_pause&lt;/code&gt; with the question as the reason before asking a user process question under llxprt, since the todo continuation auto-advances any turn that ends without a tool call.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter org init&lt;/code&gt; can now render an org doctrine pack from a local directory or git template, not just the fixed minimal scaffold&lt;/strong&gt; (#2719; closes #2718). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;org init&lt;/code&gt; only wrote the three-file skeleton (&lt;code dir=&quot;auto&quot;&gt;org-charter.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;README.md&lt;/code&gt;), so an operator standing up an organization’s doctrine from an existing template had to copy and rewrite the tree by hand. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter org init &amp;#x3C;path&gt; --template &amp;#x3C;src&gt; --org-name &amp;#x3C;name&gt;&lt;/code&gt; (also reachable through the deprecated &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine org init&lt;/code&gt;) copies a local or git template — HTTPS or SSH, selecting a branch via &lt;code dir=&quot;auto&quot;&gt;--branch&lt;/code&gt; or a &lt;code dir=&quot;auto&quot;&gt;#ref&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;@ref&lt;/code&gt; suffix — honouring &lt;code dir=&quot;auto&quot;&gt;.templateignore&lt;/code&gt; (and always excluding &lt;code dir=&quot;auto&quot;&gt;.git/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.templateignore&lt;/code&gt;) and substituting &lt;code dir=&quot;auto&quot;&gt;{{ORG_NAME}}&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;{{LOCAL_PATH}}&lt;/code&gt; into the rendered pack. Rendering is fail-closed and atomic: the org name and paths are validated up front, the tree is staged beside the destination and promoted with a same-filesystem rename, the prior pack is restored if a forced replacement fails, and overlapping source/output paths, destination symlinks, option-like git refs, and malformed template URLs are refused before anything is written. HTTPS template fetches do not inject &lt;code dir=&quot;auto&quot;&gt;GIT_TOKEN&lt;/code&gt;. Omitting &lt;code dir=&quot;auto&quot;&gt;--template&lt;/code&gt; keeps today’s minimal scaffold unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Discarding a mission with &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission close --discard&lt;/code&gt; now takes it off the dashboard&lt;/strong&gt; (#704). The command already deleted the mission’s branches and worktrees, but the mission kept showing on the dashboard as live work. It is now marked discarded and filtered from the dashboard’s mission list; its &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt; files stay on disk on purpose, so the abandonment retrospective survives.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A permanent fault-injection battery against duplicate suite execution&lt;/strong&gt; (#4334). &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_duplicate_suite_execution.py&lt;/code&gt; fails on every way the duplicate could return — canonical, inlined, behind a shell/script/make indirection, or in a net-new workflow file — and on removal of either declaration keeping the report advisory. The workflow-trigger classifier fails &lt;strong&gt;closed&lt;/strong&gt;: list-form, bare-scalar, &lt;code dir=&quot;auto&quot;&gt;pull_request_target&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge_group&lt;/code&gt;, malformed and absent &lt;code dir=&quot;auto&quot;&gt;on:&lt;/code&gt; blocks all count as change-triggered, so a duplicate cannot hide behind an ordinary trigger spelling.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A derived pinning-rule inventory&lt;/strong&gt; (#4334). &lt;code dir=&quot;auto&quot;&gt;scripts/ci/derive_pinning_inventory.py&lt;/code&gt; mechanically derives every rule pinning the CI job topology (102 sites, 43 real dependencies) into &lt;code dir=&quot;auto&quot;&gt;tests/release/pinning_rule_inventory.json&lt;/code&gt;, each with an explicit disposition, and a freshness gate re-derives and diffs it. Rules that go red are caught by CI; rules that go &lt;em&gt;greener by deletion&lt;/em&gt; previously were not.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A reproducible shard-timings capture script&lt;/strong&gt; (#4334). &lt;code dir=&quot;auto&quot;&gt;scripts/ci/capture_shard_timings.py&lt;/code&gt; replaces ad-hoc tooling that no longer existed in the tree, so &lt;code dir=&quot;auto&quot;&gt;.github/ci-shard-timings.json&lt;/code&gt; can be regenerated rather than reconstructed by archaeology.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Live Work harness capture: &lt;code dir=&quot;auto&quot;&gt;spec-kitty live-work&lt;/code&gt; publishes supported agent-harness activity (tools, files, tests, delegation) and retrospective outcomes as live Zeitgeist relay frames through the existing &lt;code dir=&quot;auto&quot;&gt;event.publish&lt;/code&gt; path&lt;/strong&gt; (#4268, re-scoped 2026-09-14 per planning#2269 — Zeitgeist carries NOW, Git carries DONE; no local journal, spool, or durable offsets anywhere). A new &lt;code dir=&quot;auto&quot;&gt;specify_cli.live_work&lt;/code&gt; package owns the canonical hook-adapter API (&lt;code dir=&quot;auto&quot;&gt;get_adapter&lt;/code&gt;), the Claude Code hook adapter (SessionStart/SessionEnd/PreToolUse/PostToolUse → session, tool, file, test, and delegation observations with exact session attribution), the Codex &lt;code dir=&quot;auto&quot;&gt;notify&lt;/code&gt; adapter (turn-level only — its tool/file/test non-observability is an explicit matrix row, never laundered), an executable capability matrix (&lt;code dir=&quot;auto&quot;&gt;live-work matrix&lt;/code&gt; exits non-zero when a configured harness has no capture hooks — no silent green), content-safety redaction (token-bearing arguments, secret files, env values, raw output, and private reasoning never enter a frame; repository-relative paths and sanitized command summaries do — including &lt;code dir=&quot;auto&quot;&gt;Bearer&lt;/code&gt;/JWT tokens in any &lt;code dir=&quot;auto&quot;&gt;-H&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--header&lt;/code&gt; form, basic-auth &lt;code dir=&quot;auto&quot;&gt;user:pass&lt;/code&gt; after &lt;code dir=&quot;auto&quot;&gt;-u&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--user&lt;/code&gt;, and URL userinfo, #4353 fix round), edit-burst coalescing (first edit publishes promptly; repeats coalesce into one count/interval/delta update), mission-worktree binding resolution (a mission is bound only from a worktree’s own confirmed identity, never guessed), the labeled repository-watcher fallback (&lt;code dir=&quot;auto&quot;&gt;live-work watch&lt;/code&gt; — changed files only, sampled attribution, never claims reads), and hook installation (&lt;code dir=&quot;auto&quot;&gt;live-work install/uninstall&lt;/code&gt;, reusing the canonical Claude settings registrar and a comment-preserving Codex config.toml merge). Frames carry the shared &lt;code dir=&quot;auto&quot;&gt;WorkObservation&lt;/code&gt; contract’s exact &lt;code dir=&quot;auto&quot;&gt;work.&amp;#x3C;kind&gt;.v1&lt;/code&gt; payload IDs (events 10.1.0, events#55/#56); the typed codec is capability-gated on the installed events version per that contract’s own COMPATIBILITY rule and planning#2000’s launch-train pin (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&gt;=9,&amp;#x3C;10&lt;/code&gt;), so the gate state is a visible matrix row, not a silent green. The retrospective captured/failed/skipped seam now publishes its outcome frame after the local append (the folded #4267 lifecycle continuity). The capability matrix also carries the whole-mission lifecycle family demanded by #4268’s 2026-09-14 clarification: first specify, plan, task generation, implementation, review/rework, acceptance/merge and retrospective, each mapped to the existing event contract, the concrete producer seam, and the live consumer — with the phases that have no live producer (review/rework, acceptance/merge) explicit &lt;code dir=&quot;auto&quot;&gt;not_observable&lt;/code&gt; rows, never silence. The bounded wake-up retry stays #4311’s shared mechanism — this publisher makes exactly one offer per frame and never builds a second retry loop. The &lt;code dir=&quot;auto&quot;&gt;live-work hook&lt;/code&gt; invocation takes the &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; command’s startup fast path (#4353 fix round): only the live-work group is registered, the init/charter import chain and the global runtime bootstrap stay unloaded, and neither startup gate runs (the schema gate’s &lt;code dir=&quot;auto&quot;&gt;SystemExit&lt;/code&gt; would break the hook’s own always-exit-0 contract) — so the 4 s hook budget bounds the capture work itself instead of a ~12 s command-registry import that preceded it.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-5&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Approving or rejecting a work package with a long review note no longer silently drops its Team Kitty status broadcast&lt;/strong&gt; (#3954). &lt;strong&gt;Before:&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;WPStatusChanged&lt;/code&gt; moment whose &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; carried a review note longer than 240 UTF-8 bytes made the events codec raise on the over-bound attr, so the CLI dropped the whole moment and the team relay never saw the transition — every approval or rejection with a real review note went unbroadcast. &lt;strong&gt;After:&lt;/strong&gt; the wire projection bounds only legacy-prose &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; (whitespace collapsed to one line, then capped at 240 UTF-8 bytes with a trailing &lt;code dir=&quot;auto&quot;&gt;…&lt;/code&gt;, codepoint-safe, byte-identical to the codec’s own truncation) so the moment broadcasts, while the canonical local status event log keeps the full note untouched; pointer-shaped values ride verbatim, and there is still exactly one publish offer per emitted event. This is the MVP interim fix — the structural replacement (a dedicated CLI-validated &lt;code dir=&quot;auto&quot;&gt;summary&lt;/code&gt; attr with &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; restored to pointer-only) stays tracked in #4327.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A corrupt &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; no longer bricks every &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; command&lt;/strong&gt; (cli-boundary-robustness; #4600, #4601, #4643, #4597, #4598, #4533, #4532). &lt;strong&gt;Before:&lt;/strong&gt; if the project config held non-UTF-8 bytes or malformed content, startup raised an uncaught error that took down &lt;strong&gt;every&lt;/strong&gt; command — including &lt;code dir=&quot;auto&quot;&gt;--version&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt;, the operator’s own repair path. &lt;strong&gt;After:&lt;/strong&gt; commands that do not need config content (&lt;code dir=&quot;auto&quot;&gt;--version&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt;) survive, and commands that genuinely need it fail with a message that names the offending file and the decode/encoding problem — never a raw traceback. Malformed-but-readable config degrades to a named domain error instead of a crash. Git-encoding and env-file reads on the same boundary were hardened alongside.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty … --json&lt;/code&gt; now emits valid JSON on every exit path&lt;/strong&gt; (cli-boundary-robustness; #4643, #4533). &lt;strong&gt;Before:&lt;/strong&gt; several commands printed human prose to stdout, or emitted a partial/empty envelope, on their error, empty, and zero-result paths — so a machine consumer parsing &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; received a broken payload (for example, a zero-work-package status exited non-zero instead of returning a well-formed empty result). &lt;strong&gt;After:&lt;/strong&gt; stdout is well-formed JSON on success, error, and empty paths alike, with human text routed to stderr, across the affected command surfaces (context, dashboard, doctor, doctrine, glossary, materialize, mission-type, archive, agent tasks).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Command defaults no longer leak an internal placeholder as a real value&lt;/strong&gt; (cli-boundary-robustness; #4601, #4597, #4598). &lt;strong&gt;Before:&lt;/strong&gt; on paths reached off the normal argument-binding flow, an internal &lt;code dir=&quot;auto&quot;&gt;OptionInfo&lt;/code&gt; sentinel could reach command output or logic as though it were a resolved value. &lt;strong&gt;After:&lt;/strong&gt; the resolved default is used and no internal placeholder reaches output or program logic.&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 mission-state --audit&lt;/code&gt; no longer flags a completed mission’s frozen snapshot as a TeamSpace blocker&lt;/strong&gt; (#4690). &lt;strong&gt;Before:&lt;/strong&gt; the audit raised a hard &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; teamspace-blocker whenever a mission’s committed &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; no longer matched the current status reducer — including for &lt;strong&gt;completed, archived&lt;/strong&gt; missions under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;, whose dossiers are immutable (the archive-preservation gate forbids editing them). The drift was therefore unfixable yet permanently red’d the corpus audit on every pull request. &lt;strong&gt;After:&lt;/strong&gt; for a mission whose every work package has reached &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; (the reducer’s own authoritative view), snapshot drift is reported as a non-blocking &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT_TERMINAL&lt;/code&gt; &lt;strong&gt;warning&lt;/strong&gt; instead of a blocking error — the drift stays visible but no longer gates TeamSpace readiness. Active (in-progress) missions still raise the hard &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; error for any lane/outcome/count drift (a live staleness bug — regenerating the snapshot before merge is the fix); a later refinement additionally tolerates &lt;em&gt;provenance-only&lt;/em&gt; drift regardless of lane (see the Unreleased &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT_PROVENANCE&lt;/code&gt; entry).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A blocked &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; decision now names where each unmet guard looked&lt;/strong&gt; (#3883). &lt;strong&gt;Before:&lt;/strong&gt; when &lt;code dir=&quot;auto&quot;&gt;next --result success&lt;/code&gt; blocked at review, the operator saw only &lt;code dir=&quot;auto&quot;&gt;Guards pending:&lt;/code&gt; with the guard names — even when the guard was looking for an artifact its own query mode reported present — leaving no way to see &lt;em&gt;what path&lt;/em&gt; the guard checked and no recovery signal (a #3883 P0 dead-end). &lt;strong&gt;After:&lt;/strong&gt; each pending guard renders &lt;code dir=&quot;auto&quot;&gt;- &amp;#x3C;name&gt;: looked for &amp;#x3C;path&gt;&lt;/code&gt;, so the operator can see the exact path the guard evaluated and reconcile it against what exists. The advance path (&lt;code dir=&quot;auto&quot;&gt;--result …&lt;/code&gt;) carries these paths; query mode is unchanged (see the PR note).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The mission dashboard no longer serves files from outside a mission’s artifact directory&lt;/strong&gt; (#4249). &lt;strong&gt;Before:&lt;/strong&gt; the dashboard’s artifact endpoints — the &lt;code dir=&quot;auto&quot;&gt;contracts&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;checklists&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; listing and file-download routes — confined a file request only to the mission root, so a &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt;-relative path could reach a file in a &lt;em&gt;different&lt;/em&gt; artifact directory of the same mission, and a symlinked artifact root (or an individual symlinked file inside one) could escape the mission tree entirely; a symlinked &lt;code dir=&quot;auto&quot;&gt;research/&lt;/code&gt; directory could even 500 the endpoint. &lt;strong&gt;After:&lt;/strong&gt; every listing entry and file read must resolve below &lt;strong&gt;both&lt;/strong&gt; the mission root &lt;strong&gt;and&lt;/strong&gt; the named artifact directory, reusing the canonical &lt;code dir=&quot;auto&quot;&gt;ensure_within_directory&lt;/code&gt; containment seam and failing closed on any unresolvable path (including a symlink loop) — a request that escapes either boundary now returns &lt;code dir=&quot;auto&quot;&gt;404&lt;/code&gt;. The same pass also rejects non-canonical &lt;code dir=&quot;auto&quot;&gt;.kittify/scripts/&lt;/code&gt; references in the packaging manifest (a &lt;code dir=&quot;auto&quot;&gt;..&lt;/code&gt; traversal in a command-template &lt;code dir=&quot;auto&quot;&gt;sh:&lt;/code&gt; frontmatter no longer enters the manifest), fixes a fragile invocation-log filter that hid any log whose name contained &lt;code dir=&quot;auto&quot;&gt;index&lt;/code&gt; (such as &lt;code dir=&quot;auto&quot;&gt;reindex.jsonl&lt;/code&gt;), and simplifies two upgrade-migration guards without changing their behaviour.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; no longer rejects a mission whose approved lane introduces the first &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; tree&lt;/strong&gt; (#4254). &lt;strong&gt;Before:&lt;/strong&gt; strict acceptance validated mission-declared build paths against the canonical &lt;strong&gt;primary checkout&lt;/strong&gt;, which is evaluated &lt;em&gt;before&lt;/em&gt; the approved lane’s source is integrated — so a lane that added the repository’s first &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; failed acceptance because those paths did not yet exist in the pre-integration tree. &lt;strong&gt;After:&lt;/strong&gt; acceptance also checks the tree actually being accepted (the approved lane’s &lt;code dir=&quot;auto&quot;&gt;candidate_source_roots&lt;/code&gt;), so a build path satisfied by the candidate tree passes; mission-artifact paths are still validated strictly and are never satisfied by a lane worktree.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate&lt;/code&gt; no longer silently deactivates everything else in force when a kind has no explicit activation set&lt;/strong&gt; (#4253). &lt;strong&gt;Before:&lt;/strong&gt; activating one artifact for a kind whose &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; activation key was absent treated the absent key as “start from the default pack” and wrote a bare one-element list — silently dropping every &lt;em&gt;effective&lt;/em&gt; artifact outside &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt; (observed: 15 directives and 11 procedures, including adversarial-squad-deployment, lost on a single unrelated activation). &lt;strong&gt;After:&lt;/strong&gt; an absent key is correctly read as the unrestricted state, so the first activation materializes everything currently in force (the resolver’s effective set, spanning the full declared org chain and in the keyspace it filters on) and appends the new artifact — nothing in force is deactivated. Unknown-id validation still runs first (nothing is written on a bad id), and an already-restricted key behaves exactly as before.&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 coordination --fix --mission &amp;#x3C;slug&gt;&lt;/code&gt; no longer rewrites every other mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;&lt;/strong&gt; (#4501; fixes #4050). &lt;strong&gt;Before:&lt;/strong&gt; a single mission-scoped invocation stamped &lt;code dir=&quot;auto&quot;&gt;topology&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;flattened&lt;/code&gt; into 77 missions’ &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, 76 of them unrelated to the selected mission — the flatten and its topology backfill walked the whole repository instead of the &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; scope, and the saas repo had to revert those files by hand (saas#1465). &lt;strong&gt;After:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; flatten and topology backfill are bounded to the selected mission; an unrelated mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; stays byte-unchanged while the scoped mission’s own topology is re-derived, and a regression test pins both directions.&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 acceptance-verdict&lt;/code&gt; now runs at the &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; level next to &lt;code dir=&quot;auto&quot;&gt;issue-verdict&lt;/code&gt;&lt;/strong&gt; (#3951). &lt;strong&gt;Before:&lt;/strong&gt; the two verdict commands lived at different nesting levels — &lt;code dir=&quot;auto&quot;&gt;agent issue-verdict&lt;/code&gt; but &lt;code dir=&quot;auto&quot;&gt;agent mission acceptance-verdict&lt;/code&gt; only — so an agent following the one-level pattern of &lt;code dir=&quot;auto&quot;&gt;agent --help&lt;/code&gt; hit &lt;code dir=&quot;auto&quot;&gt;No such command&lt;/code&gt; for the sibling. &lt;strong&gt;After:&lt;/strong&gt; both verdict commands resolve at the &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; level; the &lt;code dir=&quot;auto&quot;&gt;agent mission acceptance-verdict&lt;/code&gt; registration stays (mission-step prompts and the docs name it).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The issue-matrix approve-gate blocker now names the command that fills a verdict row&lt;/strong&gt; (#3951). &lt;strong&gt;Before:&lt;/strong&gt; the blocker said only “Fill in verdicts before approving”, so orchestrating agents guessed at &lt;code dir=&quot;auto&quot;&gt;agent mission issue-verdict&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;agent tasks issue-verdict&lt;/code&gt; — both &lt;code dir=&quot;auto&quot;&gt;No such command&lt;/code&gt; — and lost round-trips per mission. &lt;strong&gt;After:&lt;/strong&gt; both the unresolved-entries and the missing-artifact blocker carry the runnable remedy, &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent issue-verdict --mission &amp;#x3C;handle&gt; --issue &amp;#x3C;#NNN&gt; --verdict &amp;#x3C;fixed|verified-already-fixed|deferred-with-followup|in-mission&gt; --actor &amp;#x3C;actor&gt;&lt;/code&gt;, alongside the existing regenerate hint.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission-agnostic commands now accept-and-ignore &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; instead of exiting 2&lt;/strong&gt; (fixes #3953). &lt;strong&gt;Before:&lt;/strong&gt; the shipped mission-step skill text instructs agents to pass &lt;code dir=&quot;auto&quot;&gt;--mission &amp;#x3C;handle&gt;&lt;/code&gt; to &lt;em&gt;every&lt;/em&gt; spec-kitty command in multi-mission repos, but any command that is not mission-scoped rejected it — &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent profile list --mission …&lt;/code&gt; exited 2 with &lt;code dir=&quot;auto&quot;&gt;No such option: --mission&lt;/code&gt;, contradicting the skill text once per session. &lt;strong&gt;After:&lt;/strong&gt; every leaf command that does not declare a real &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; (matched by option name, since several declare it behind a &lt;code dir=&quot;auto&quot;&gt;feature&lt;/code&gt; parameter) gets a hidden, non-exposed &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; option: the value parses and is discarded, the callback never sees it, &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; output is unchanged, and &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; without a value still fails loudly rather than becoming a silent boolean flag. Both leaf shapes are covered — registered commands (&lt;code dir=&quot;auto&quot;&gt;agent profile list&lt;/code&gt;) via a &lt;code dir=&quot;auto&quot;&gt;MissionAgnosticCommand&lt;/code&gt; class and callback-owned sub-apps (&lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt;) via a &lt;code dir=&quot;auto&quot;&gt;MissionAgnosticGroup&lt;/code&gt; class — and a tree-wide guard test pins the invariant that no command a step prompt can name exits 2 on &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; alone. Mission-scoped commands are byte-identical: their real &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; still reaches the callback.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A machine login that cannot reach the SaaS now names the network fix instead of a generic auth error&lt;/strong&gt; (#4465; closes #4308). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty login --machine&lt;/code&gt; caught &lt;code dir=&quot;auto&quot;&gt;AuthenticationError&lt;/code&gt; before its subclass &lt;code dir=&quot;auto&quot;&gt;NetworkError&lt;/code&gt;, so a connection failure — DNS, a firewall, or a wrong &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt; on a CI runner — fell through to the generic “Network error exchanging machine credentials” line and never reached the tailored guidance; the operator was told nothing about checking the URL or network access, and the transport exception was rendered through Rich un-escaped. &lt;strong&gt;After:&lt;/strong&gt; the network branch is caught first, so a failure prints “Could not reach the SaaS: …” followed by “Check SPEC_KITTY_SAAS_URL and network access from this runner.”, with the exception text Rich-escaped like the adjacent authentication boundary. The flow still exits non-zero, writes no session, and keeps the client secret out of the output; a new end-to-end regression drives a real &lt;code dir=&quot;auto&quot;&gt;httpx.ConnectError&lt;/code&gt; through the CLI to prove the previously unreachable branch.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; no longer aborts when Git is missing or its local config is unusable&lt;/strong&gt; (#4481; closes #4159). &lt;strong&gt;Before:&lt;/strong&gt; init wired the custom merge drivers into git config as a best-effort step, but if the &lt;code dir=&quot;auto&quot;&gt;git&lt;/code&gt; binary had disappeared after detection, or a stale &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; entry made &lt;code dir=&quot;auto&quot;&gt;git config&lt;/code&gt; fail, that optional step raised and turned a nearly-complete scaffold into a hard init failure — leaving the operator with a half-initialized project. &lt;strong&gt;After:&lt;/strong&gt; the merge-driver wiring is caught as best-effort: init prints one warning (“Could not configure Spec Kitty merge drivers; continuing without local git configuration.”) and finishes, and the merge path self-heals the config the next time it runs. Only the optional git-config step is softened — provisioning and every other init failure still stop init as before.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A pull request that changes only test files no longer wears a red CI aggregate gate it did not cause&lt;/strong&gt; (#4512). &lt;strong&gt;Before:&lt;/strong&gt; a diff-scoped PR that selected zero modules (e.g. one touching only &lt;code dir=&quot;auto&quot;&gt;tests/performance/&lt;/code&gt;) correctly emptied &lt;code dir=&quot;auto&quot;&gt;ci-modules.yml&lt;/code&gt;’s shard matrix and skipped its test job by design — but GitHub Actions then emitted one placeholder job carrying the un-interpolated matrix template as its name (&lt;code dir=&quot;auto&quot;&gt;module-tests (${{ matrix.module }} shard ${{ matrix.shard }})&lt;/code&gt;), and the aggregate’s artefact selector (&lt;code dir=&quot;auto&quot;&gt;scripts/ci/select_source_artifacts.py&lt;/code&gt;) raised &lt;code dir=&quot;auto&quot;&gt;unrecognized module shard job name&lt;/code&gt; on it, aborting the collect job before the selection-aware reconciler — which already tolerates zero selection — could run. Every test-only-path PR therefore went red on &lt;code dir=&quot;auto&quot;&gt;ci-aggregate&lt;/code&gt; through no fault of its own. &lt;strong&gt;After:&lt;/strong&gt; the selector treats that un-interpolated placeholder as “no shard ran” and skips it, so a zero-selection PR aggregates green; genuinely malformed shard names still fail closed, and a regression test pins both directions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty moments off --help&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;moments status&lt;/code&gt; no longer name an internal command a user cannot run&lt;/strong&gt; (#4453; closes #4447). &lt;strong&gt;Before:&lt;/strong&gt; both surfaces spelled out &lt;code dir=&quot;auto&quot;&gt;spec-kitty zeitgeist mcp-serve&lt;/code&gt; — a hidden MCP-launcher entry point that is not a public CLI surface — teaching a command path that only ever looks broken when typed by hand. &lt;strong&gt;After:&lt;/strong&gt; they describe it as the internal agent-context bridge (&lt;code dir=&quot;auto&quot;&gt;moments off&lt;/code&gt;: “exits cleanly with one line”; &lt;code dir=&quot;auto&quot;&gt;moments status&lt;/code&gt;: “refuses to start while agents = off”), keeping the exact behaviour while keeping the hidden path out of user-facing output. This also restores the docs-freshness gate, which had gone red on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; because the hidden name leaked into the generated CLI reference without an Internal banner.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty mission close --discard&lt;/code&gt; no longer prints the mission ULID twice, and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;/review notices render instead of showing raw markup&lt;/strong&gt; (closes #4163, #4507). &lt;strong&gt;Before:&lt;/strong&gt; the “Coordination worktree torn down for …” line composed the identity as &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; even though the slug already embedded the mid8, so an operator saw the ULID doubled (&lt;code dir=&quot;auto&quot;&gt;relcheck-01M21R2T-01M21R2T&lt;/code&gt;); and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s three baseline notices plus the review-lock refusal were written with the builtin &lt;code dir=&quot;auto&quot;&gt;print&lt;/code&gt;, so Rich markup reached the terminal literally (&lt;code dir=&quot;auto&quot;&gt;[dim]Baseline: …[/dim]&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;[red]…[/red]&lt;/code&gt;). &lt;strong&gt;After:&lt;/strong&gt; the teardown line — and the coordination-worktree-missing error message — compose the identity through the idempotent &lt;code dir=&quot;auto&quot;&gt;coord_mission_dir_name&lt;/code&gt; seam, so the mid8 appears exactly once for slugs with or without it embedded; and every notice renders through the CLI console seam with its exception text escaped, so a git refusal like &lt;code dir=&quot;auto&quot;&gt;! [rejected] main -&gt; main&lt;/code&gt; is shown verbatim instead of losing its bracketed word or raising a misleading &lt;code dir=&quot;auto&quot;&gt;MarkupError&lt;/code&gt;. A regression guard also fails the build if a builtin &lt;code dir=&quot;auto&quot;&gt;print()&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;cli/&lt;/code&gt; ever carries Rich markup again. Output only; no behaviour, exit-code, or artifact change.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A workspace-allocation failure during &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; left the work package stuck, and the only way out was to invent a review rejection that never happened&lt;/strong&gt; (#4245; closes #3937). &lt;strong&gt;Before:&lt;/strong&gt; when allocation hit a dependency-lane or planning-commit merge conflict, the error handler moved the work package to &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; — even though it was still &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; and the allocator had already cleaned up after itself. &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; cannot legally go back to &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;, so every re-run printed “cannot start implementation” forever, and the one escape (&lt;code dir=&quot;auto&quot;&gt;move-task --to planned&lt;/code&gt;) demands a &lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt; that cannot be skipped with &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;. Clearing a tooling hiccup therefore meant writing a fake review finding, after which the claim ran in “Fix mode” as though a reviewer had rejected the work. &lt;strong&gt;After:&lt;/strong&gt; an allocation failure leaves the work package &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; and prints the conflict’s actual resolution step, so a plain re-run works once the cause is fixed — the same behaviour the orchestrator-api path already had. The escape hatch is no longer reached, so nobody has to fabricate a review finding; the review-feedback gate itself is deliberately left exactly as it is, and #3937 stays open for the separate question of how that refusal should read.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Refusing &lt;code dir=&quot;auto&quot;&gt;move-task --to planned&lt;/code&gt; on a &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; work package no longer tells the operator to fabricate review feedback&lt;/strong&gt; (blocked-planned-refusal-message; #4689, closes #3937). &lt;strong&gt;Before:&lt;/strong&gt; the refusal was source-blind — every lane got the same “Moving &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;WP&gt;&lt;/code&gt; to ‘planned’ requires review feedback” message, even &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;, where &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; is not a legal target at all. For a &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; work package (the common tooling-hiccup case, now that #4245 keeps allocation failures in &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;) that message pointed at the wrong recovery and trained operators to write a fake review file. &lt;strong&gt;After:&lt;/strong&gt; the refusal is source-aware, message-only. When &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; is a legal rollback target (&lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;genesis&lt;/code&gt;) the review-feedback message is unchanged; otherwise the message names the source lane’s real legal targets read from the state machine itself — &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; points at the honest one-hop resume &lt;code dir=&quot;auto&quot;&gt;--to in_progress&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; are reported terminal. The guard stays unconditional and force-proof: every &lt;code dir=&quot;auto&quot;&gt;--to planned&lt;/code&gt; move without valid feedback still refuses, for every source lane, with and without &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; — the source lane shapes only the words, never the decision. This closes the remaining F-51 half of #3937 (F-50 shipped in #4245).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;docs/development/reference/coverage-signals.md&lt;/code&gt; described a pipeline that does not exist&lt;/strong&gt; (#4011). It claimed this repository runs no GitHub Actions, that diff-coverage and &lt;code dir=&quot;auto&quot;&gt;sonar_project_version.py&lt;/code&gt; were retired, and gave the wrong nightly schedule. Corrected against the live tree.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The gate model could not see a suite invocation reached through a make target&lt;/strong&gt; (#4334). &lt;code dir=&quot;auto&quot;&gt;tests/architectural/_gate_coverage.py&lt;/code&gt; now resolves make targets by reading the Makefile, and a &lt;code dir=&quot;auto&quot;&gt;uv run --frozen pytest&lt;/code&gt; invocation is no longer parsed as “no pytest command here” — a defect that had been hiding every gate in &lt;code dir=&quot;auto&quot;&gt;ci-router.yml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;packs.yml&lt;/code&gt;. Before this, an assertion that &lt;code dir=&quot;auto&quot;&gt;ci-quality.yml&lt;/code&gt; ran no test suite passed while a 22-minute duplicate tier ran inside it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The issue-matrix approve gate now names the file it actually reads and shows the exact rule each row broke&lt;/strong&gt; (#4330). &lt;strong&gt;Before:&lt;/strong&gt; every approve-blocker message hardcoded &lt;code dir=&quot;auto&quot;&gt;ERROR: issue-matrix.md&lt;/code&gt;, but the gate reads the matrix JSON-first — so an operator on a JSON-format mission (every scaffolded and migrated mission) was sent hunting for an &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; their mission does not have; and an unknown-verdict row was flattened to a bare &lt;code dir=&quot;auto&quot;&gt;Unknown: #NNN&lt;/code&gt; id list that dropped the concrete rule it violated, findable only by reading the validator source. &lt;strong&gt;After:&lt;/strong&gt; the header names the artifact the gate resolves (&lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt;, or the legacy &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; only for an &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt;-only mission), and each failing row is surfaced verbatim with the rule it broke (e.g. &lt;code dir=&quot;auto&quot;&gt;verdict is &apos;deferred-with-followup&apos; but evidence_ref contains no follow-up handle&lt;/code&gt;). Diagnostics only — the conditions that block approval, the read surface, and every pass/fail outcome are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Built-in doctrine guidance no longer points at the retired &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&amp;#x3C;kind&gt;.graph.yaml&lt;/code&gt; fragment home&lt;/strong&gt; (#2715). The &lt;code dir=&quot;auto&quot;&gt;common-docs-find&lt;/code&gt; tactic and the &lt;code dir=&quot;auto&quot;&gt;brownfield-onboarding&lt;/code&gt; paradigm now name &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&amp;#x3C;kind&gt;.graph.yaml&lt;/code&gt;, and the agent-profile repository’s lineage-graph docstring no longer describes a monolith that is gone. The dead-path architectural gate now also flags &lt;code dir=&quot;auto&quot;&gt;doctrine/&amp;#x3C;kind&gt;.graph.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;doctrine/*.graph.yaml&lt;/code&gt; paths, not only the &lt;code dir=&quot;auto&quot;&gt;doctrine/graph.yaml&lt;/code&gt; monolith, and its failure message no longer recommends the dead path.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty specify&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; now refuse a silent duplicate of a live mission instead of creating a second mission under a different slug (&lt;code dir=&quot;auto&quot;&gt;#4033&lt;/code&gt;).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; running create twice for the same intent (same &lt;code dir=&quot;auto&quot;&gt;mission_slug&lt;/code&gt; &lt;strong&gt;and&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;) produced two missions, both &lt;code dir=&quot;auto&quot;&gt;{&quot;result&quot;:&quot;success&quot;}&lt;/code&gt;, both exit 0 — a trainee following the docs silently ended up with a duplicate. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;create_mission_core&lt;/code&gt; fails closed with &lt;code dir=&quot;auto&quot;&gt;MissionCreationError&lt;/code&gt; &lt;em&gt;before&lt;/em&gt; any scaffold or branch is written when a live same-key mission exists, naming the existing mission (slug + &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt;) and the &lt;code dir=&quot;auto&quot;&gt;--allow-duplicate&lt;/code&gt; override. An abandoned prior mission — explicitly canceled, or &lt;em&gt;genesis&lt;/em&gt;-abandoned (zero lifecycle events &lt;strong&gt;and&lt;/strong&gt; a spec that was never committed) — does not block a fresh create, so a bare never-used scaffold re-creates cleanly with no flag. The legitimate high-volume factory case is served by an explicit &lt;code dir=&quot;auto&quot;&gt;--allow-duplicate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;--allow-dup&lt;/code&gt; flag on both &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt;, threaded to &lt;code dir=&quot;auto&quot;&gt;create_mission_core(allow_duplicate=True)&lt;/code&gt;; abandonment detection fails closed, so an indeterminate prior mission is treated as live and refused.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; no longer lets an older mission-branch planning copy silently clobber a target-newer one during the squash&lt;/strong&gt; (#3942). The mission→target &lt;code dir=&quot;auto&quot;&gt;git merge --squash -X theirs&lt;/code&gt; step forces the source (mission branch) to win every add/add conflict, which is correct for source code and the driver-covered &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**&lt;/code&gt; bookkeeping classes but false for PRIMARY-partition planning artifacts (&lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt;) — those are authored on the primary/target surface, so the target can carry a legitimately newer copy. A merge driver cannot fix this (it sees only three blobs, no history), so target-newer recency is now resolved after the squash by a pure three-way rule (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/merge/planning_recency.py&lt;/code&gt;): a path is target-authoritative when the target diverged from the merge-base while the lane copy is base-or-ancestor, with committer-date (never mtime) as the tiebreak and the target winning on a tie. Preserved paths are amended into the single squash commit and reported to the operator, never silent (FR-002). Driver-covered reconcilers (#2709/#2804) are unchanged. Advances epic #2907.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The post-merge &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; completion marker has a production writer again, and the merged-state guard is reopen-aware&lt;/strong&gt; (#4090). The primary-wins guard that re-anchors post-merge reads to the PRIMARY surface (&lt;code dir=&quot;auto&quot;&gt;is_mission_merged&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;meta[&quot;merged_at&quot;]&lt;/code&gt;) had been dormant since its writer was deleted in #2258, so retrospect and doctor could still read a stale diverged coordination husk. The writer is restored as a sibling of &lt;code dir=&quot;auto&quot;&gt;record_baseline_merge_commit&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/merge/baseline.py&lt;/code&gt;), the meta-write authority — the executor is untouched — and &lt;code dir=&quot;auto&quot;&gt;is_mission_merged&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/lifecycle.py&lt;/code&gt;) is now event-sourced: a mission is merged iff &lt;code dir=&quot;auto&quot;&gt;merged_at&lt;/code&gt; is present and no later &lt;code dir=&quot;auto&quot;&gt;MissionReopened&lt;/code&gt; event postdates it, so a reopened mission correctly reads as not-merged and a re-merge re-stamps a fresh marker. Advances epic #2160 (keeps the single canonical post-merge authority on PRIMARY, overriding the husk rather than freshening it).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Characterization guard confirming post-merge &lt;code dir=&quot;auto&quot;&gt;event_count&lt;/code&gt; union consistency&lt;/strong&gt; (#4091, verified-already-fixed). &lt;code dir=&quot;auto&quot;&gt;event_count&lt;/code&gt; is by definition the count of unique &lt;code dir=&quot;auto&quot;&gt;WPStatusChanged&lt;/code&gt; transition events (annotations, lifecycle, and decision events are not transitions), and &lt;code dir=&quot;auto&quot;&gt;_project_status_bookkeeping_to_target&lt;/code&gt; already unions and re-reduces under a coordination husk. A red-first repro on a coord fixture confirmed the count is already correct on HEAD, so #4091 is closed with a regression-locking characterization test rather than a code change.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;known-limitations&quot;&gt;Known limitations&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The per-change Sonar report is &lt;strong&gt;wired but not yet publishing&lt;/strong&gt;. SonarCloud Automatic Analysis is enabled on the project and refuses every CI-side upload (#4350); the project currently holds no coverage metric at all. This change makes the suite run once and connects the report to the existing measurement — it does &lt;strong&gt;not&lt;/strong&gt; restore a published report, and a green pipeline is not evidence of publication. See also #4367 (further gate-model indirection forms), #4368 (packages with no declared routing group), #4351 and #4365 (pre-existing test gaps surfaced during the work).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;security&quot;&gt;Security&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The three release-critical GitHub Actions workflows are hardened per SonarCloud, closing the surface deferred from #4342&lt;/strong&gt; (#4352). &lt;code dir=&quot;auto&quot;&gt;release.yml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;release-readiness.yml&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;ci-nightly.yml&lt;/code&gt; are not exercised by PR CI, so they were split out of the primary hardening mission for a manual dry-run before merge. &lt;strong&gt;Before:&lt;/strong&gt; third-party actions floated on mutable tags (&lt;code dir=&quot;auto&quot;&gt;astral-sh/setup-uv@v8.1.0&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;softprops/action-gh-release@v3.0.0&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pypa/gh-action-pypi-publish@release/v1&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;dorny/paths-filter@v4&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;release.yml&lt;/code&gt; granted &lt;code dir=&quot;auto&quot;&gt;contents: write&lt;/code&gt; workflow-wide; the release-readiness &lt;code dir=&quot;auto&quot;&gt;workflow_dispatch&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;inputs.tag&lt;/code&gt; was interpolated straight into a shell &lt;code dir=&quot;auto&quot;&gt;run:&lt;/code&gt; body (a script-injection surface); and several installs were unpinned (&lt;code dir=&quot;auto&quot;&gt;twine==6.*&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tomli==2.*&lt;/code&gt;, a bare &lt;code dir=&quot;auto&quot;&gt;pip install pyyaml&lt;/code&gt;, a non-&lt;code dir=&quot;auto&quot;&gt;--frozen&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;uv sync&lt;/code&gt;, three non-&lt;code dir=&quot;auto&quot;&gt;--frozen&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;uv run pytest&lt;/code&gt; calls). &lt;strong&gt;After:&lt;/strong&gt; every flagged third-party action is pinned to a full 40-char commit SHA — the PyPI publish action to &lt;code dir=&quot;auto&quot;&gt;dc37677b&lt;/code&gt;, which is tag &lt;code dir=&quot;auto&quot;&gt;v1.14.2&lt;/code&gt; &lt;strong&gt;and&lt;/strong&gt; the current &lt;code dir=&quot;auto&quot;&gt;release/v1&lt;/code&gt; branch tip, so OIDC trusted publishing is preserved; write permissions are relocated to the jobs that need them (&lt;code dir=&quot;auto&quot;&gt;publish-pypi&lt;/code&gt; keeps &lt;code dir=&quot;auto&quot;&gt;contents: write&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;id-token: write&lt;/code&gt;, everything else drops to &lt;code dir=&quot;auto&quot;&gt;contents: read&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;inputs.tag&lt;/code&gt; flows through an &lt;code dir=&quot;auto&quot;&gt;env:&lt;/code&gt; binding instead of the script body; and the installs are exact-pinned (&lt;code dir=&quot;auto&quot;&gt;twine==6.2.0&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tomli==2.4.1&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pyyaml==6.0.3 --only-binary=:all:&lt;/code&gt;) with &lt;code dir=&quot;auto&quot;&gt;--frozen&lt;/code&gt; added to the release &lt;code dir=&quot;auto&quot;&gt;uv sync&lt;/code&gt; and the three nightly &lt;code dir=&quot;auto&quot;&gt;uv run pytest&lt;/code&gt; calls. Behavior-identical, security-only; the remaining first-party self-install / frozen-lock findings are adjudicated won’t-fix in the mission dossier (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/ghactions-sonar-hardening-01M2FYX1/adjudication.md&lt;/code&gt;, Section E).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;400rc2---2026-09-14&quot;&gt;[4.0.0rc2] - 2026-09-14&lt;/h2&gt;
&lt;p&gt;Second public release candidate for the Team Kitty 4.x line, cut from &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; for
the Team Kitty launch walkthroughs. This is a testing prerelease, not stable launch
acceptance. Install explicitly with &lt;code dir=&quot;auto&quot;&gt;uv tool install &apos;spec-kitty-cli==4.0.0rc2&apos;&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The CLI keeps the public shared-package targets: events 9.1.6 and tracker 0.5.2.
Live Work is not included in this candidate. Stable 4.0.0 launch acceptance is
tracked separately.&lt;/p&gt;
&lt;h3 id=&quot;added-6&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty auth login --machine&lt;/code&gt; authenticates CI runners and other unattended environments for hosted operations with no browser, TTY or device-flow approval&lt;/strong&gt; (#3277; #4306). It exchanges a ServicePrincipal client ID and secret, read from &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_MACHINE_CLIENT_ID&lt;/code&gt; plus &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_MACHINE_CLIENT_SECRET&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_MACHINE_CLIENT_SECRET_FILE&lt;/code&gt;, through the OAuth &lt;code dir=&quot;auto&quot;&gt;client_credentials&lt;/code&gt; grant. Missing or rejected credentials fail closed with one remediation message, never a prompt, and the secret is never printed. &lt;code dir=&quot;auto&quot;&gt;--machine&lt;/code&gt; cannot be combined with &lt;code dir=&quot;auto&quot;&gt;--headless&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;auth status&lt;/code&gt; labels the session &lt;code dir=&quot;auto&quot;&gt;Machine / CI (Client Credentials Grant)&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;auth doctor&lt;/code&gt; (text and &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;) reports the additive &lt;code dir=&quot;auto&quot;&gt;session.auth_method&lt;/code&gt; field. Browser and device-flow login remain the default for people; the runner setup and credential rotation runbook is &lt;code dir=&quot;auto&quot;&gt;docs/operations/ci-machine-auth.md&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 accept --mode pr --merge-commit &amp;#x3C;sha&gt;&lt;/code&gt; records the PR’s real merge as the mission’s post-merge review baseline&lt;/strong&gt; (#4231). A mission accepted through a GitHub PR never passes through &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt;, so its &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; never carried &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; — leaving &lt;code dir=&quot;auto&quot;&gt;spec-kitty review --mode post-merge&lt;/code&gt; unreachable (&lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_MODE_MISMATCH&lt;/code&gt;) and the lightweight dead-code gate failing a cleanly merged mission. The supplied commit is verified against git before anything is written (it must resolve, carry &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/meta.json&lt;/code&gt;, its first parent must not, and it must have landed on the target branch — an unmerged mission-branch commit satisfies every first-introduction check, so only the target-branch membership check separates it from a real landing); &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; is then recorded as that first parent, with the provenance pair &lt;code dir=&quot;auto&quot;&gt;pr_merge_commit&lt;/code&gt; (the landing commit) and &lt;code dir=&quot;auto&quot;&gt;pr_merge_evidence&lt;/code&gt; (what the anchor’s completeness rests on), through the same canonical seam &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; uses. Also exposed as &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission accept --merge-commit&lt;/code&gt;, and backfillable for missions whose PR already merged via the new &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-merge-commit --mission &amp;#x3C;handle&gt; --merge-commit &amp;#x3C;sha&gt;&lt;/code&gt; (idempotent; an already-recorded baseline is never overwritten). Both seams accept &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt; for the PR’s base branch, defaulting to the mission’s declared &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;, else the repository’s primary branch.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The PR-recorded anchor names its evidence class, and EVERY landing shape needs an explicit operator attestation&lt;/strong&gt; (#4231 fix rounds). Post-landing git history cannot prove a supplied landing commit’s first parent is the pre-landing target tip for ANY shape: an internal merge (the corpus branch merged into the implementation branch, the target then fast-forwarded to the result) is graph-identical to a merge performed on the target branch and its first parent is an implementation commit, and a single-parent landing (squash, or a corpus-first stack) whose implementation commits preceded the corpus has an earlier same-PR commit there — graph-identical to pre-existing target work. Recording an unattested anchor in either shape would silently under-scan the dead-code gate while the command’s reason string claimed git had proved the parent was the tip. Both shapes are therefore refused unless the operator passes &lt;code dir=&quot;auto&quot;&gt;--attest-first-landing-commit&lt;/code&gt; (for a two-parent merge: the merge was performed on the target branch; for a single-parent landing: the supplied commit was the first commit of the landing), and record as &lt;code dir=&quot;auto&quot;&gt;pr_merge_evidence: merge-commit-parent-attested&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;corpus-parent-attested&lt;/code&gt; respectively, so the anchor’s completeness rests on a recorded operator attestation, never on a claim git did not make; &lt;code dir=&quot;auto&quot;&gt;spec-kitty review --mode post-merge&lt;/code&gt; honours the field, surfacing &lt;code dir=&quot;auto&quot;&gt;MISSION_REVIEW_DEAD_CODE_EVIDENCE_INCOMPLETE&lt;/code&gt; instead of a green scan for any present value it does not recognize as complete. Full forge commit-list evidence, which would prove the tip outright, is tracked in #4277.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-6&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The lightweight review &lt;code dir=&quot;auto&quot;&gt;dead_code_baseline_missing&lt;/code&gt; finding now distinguishes a PR-accepted mission from one that never merged&lt;/strong&gt; (#4231). Both states previously produced the identical &lt;code dir=&quot;auto&quot;&gt;verdict: fail&lt;/code&gt;, so a cleanly PR-merged mission was indistinguishable from a real fidelity failure. The finding now carries a &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;pr_accepted_merge_unrecorded&lt;/code&gt; (with a remediation naming &lt;code dir=&quot;auto&quot;&gt;backfill-merge-commit&lt;/code&gt;) vs &lt;code dir=&quot;auto&quot;&gt;never_merged_via_spec_kitty_merge&lt;/code&gt; — while keeping the same hard-fail verdict weight, since the dead-code gate cannot run without an anchor either way.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An explicitly-set &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt; is a real opinion again, even when its value equals the packaged default &lt;code dir=&quot;auto&quot;&gt;https://team.spec-kitty.ai&lt;/code&gt;&lt;/strong&gt; (#4259). The 4.0.0rc1 resolver treated such a value as “no opinion”, so a stale &lt;code dir=&quot;auto&quot;&gt;config.toml [sync].server_url&lt;/code&gt; naming the retired first-party app endpoint &lt;code dir=&quot;auto&quot;&gt;https://app.spec-kitty.ai&lt;/code&gt; won resolution and login targeted dead infrastructure. An explicit env value now wins in a whole-process context (login) and fails closed as a split-brain against a different configured target in setup-only contexts, exactly like any other env/config disagreement.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A new 4.0.0 upgrade migration rewrites exactly the retired first-party address in &lt;code dir=&quot;auto&quot;&gt;config.toml [sync].server_url&lt;/code&gt; to the canonical hosted target&lt;/strong&gt; (#4259). Machine-scoped and idempotent; hostname-exact matching only (never substring), so custom and self-hosted endpoints, ports, paths, and every unrelated setting are untouched. A missing, unreadable, or unparseable &lt;code dir=&quot;auto&quot;&gt;config.toml&lt;/code&gt; is a no-op.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty auth login&lt;/code&gt; now shows the resolved target and its configuration source before any OAuth flow starts&lt;/strong&gt;, and warns — never rejects — when the target is the retired first-party endpoint or another noncanonical &lt;code dir=&quot;auto&quot;&gt;spec-kitty.ai&lt;/code&gt; host, naming the canonical endpoint and the upgrade remedy (#4259). A custom/self-hosted endpoint is labelled custom and left unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty auth login&lt;/code&gt; never relabels or forwards a stored session minted for a different endpoint&lt;/strong&gt; (#4259). Plain &lt;code dir=&quot;auto&quot;&gt;login&lt;/code&gt; on an issuer mismatch now refuses with the stale-session remedy instead of reporting “Already logged in”; only &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; re-authenticates, minting fresh credentials against the resolved target (the non-interactive bridge already enforced this boundary since #234).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker discover&lt;/code&gt; leaked a raw Python traceback instead of a clean CLI error whenever the SaaS control plane rejected the discovery request (observed on HTTP 403; &lt;code dir=&quot;auto&quot;&gt;#4233&lt;/code&gt;).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;discover&lt;/code&gt; guarded the service call with a hand-rolled &lt;code dir=&quot;auto&quot;&gt;except TrackerServiceError&lt;/code&gt; only, but a SaaS non-2xx surfaces as &lt;code dir=&quot;auto&quot;&gt;SaaSTrackerClientError&lt;/code&gt; — a &lt;em&gt;sibling&lt;/em&gt; of &lt;code dir=&quot;auto&quot;&gt;TrackerServiceError&lt;/code&gt; (both derive from &lt;code dir=&quot;auto&quot;&gt;RuntimeError&lt;/code&gt;, neither from the other) — so any 403/404/429/5xx propagated uncaught and printed a full Rich traceback exposing internal module paths (&lt;code dir=&quot;auto&quot;&gt;tracker/saas_client.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tracker/service.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;cli/commands/tracker.py&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;discover&lt;/code&gt; was the lone tracker command that did not route its service call through the shared &lt;code dir=&quot;auto&quot;&gt;_run_or_exit&lt;/code&gt; helper (which catches the &lt;code dir=&quot;auto&quot;&gt;RuntimeError&lt;/code&gt; family), which is exactly why every other tracker command was immune. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;discover&lt;/code&gt;’s service call goes through &lt;code dir=&quot;auto&quot;&gt;_run_or_exit&lt;/code&gt;, so any &lt;code dir=&quot;auto&quot;&gt;RuntimeError&lt;/code&gt;-family failure — the SaaS sibling included — renders as a single-line stderr message + &lt;code dir=&quot;auto&quot;&gt;Exit(1)&lt;/code&gt; with no traceback and no internal paths. The shared boundary now also preserves the structured server error data (the September #4233 extension): the error envelope parser reads the PRI-12 canonical &lt;code dir=&quot;auto&quot;&gt;code&lt;/code&gt; key (with the legacy &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt; and a string &lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; message field as fallbacks, coordinated with &lt;code dir=&quot;auto&quot;&gt;#2944&lt;/code&gt; rather than a second taxonomy), the raised error’s machine code now outranks the envelope category, and &lt;code dir=&quot;auto&quot;&gt;_run_or_exit&lt;/code&gt; renders the code, HTTP status and one actionable hint distinguishing disabled rollout (&lt;code dir=&quot;auto&quot;&gt;FEATURE_DISABLED&lt;/code&gt;), missing/stale binding, expired authorization, permission denial, rate limiting and server failure. Under &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;, the same failure is additionally emitted as a machine-readable object on stdout (&lt;code dir=&quot;auto&quot;&gt;{&quot;ok&quot;: false, &quot;error&quot;: ..., &quot;error_code&quot;: ..., &quot;http_status&quot;: ..., &quot;action&quot;: ...}&lt;/code&gt;) — failures are never converted into successful empty results, only whitelisted fields are rendered (no envelope internals, no credentials), and the exit code stays nonzero. Regression tests drive the real command with mocked HTTP error responses (not just injected service errors), including the exact observed &lt;code dir=&quot;auto&quot;&gt;FEATURE_DISABLED&lt;/code&gt; 403 payload, and assert no traceback, no leaked bearer token, and valid JSON on stdout in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; mode.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Starting a mission’s specify, plan or tasks phase publishes its moment to Team Kitty again&lt;/strong&gt; (#4214). The Zeitgeist bridge validated the persisted Started payload unchanged, so the local-only &lt;code dir=&quot;auto&quot;&gt;artifact_path&lt;/code&gt; it carries failed the strict canonical model and the moment was dropped before any publish. The bridge now projects that field off at the wire boundary through the lifecycle module’s canonical projection; the persisted event keeps it, any other undeclared field is still rejected, and Completed phases are unchanged. The issue’s final acceptance row — the accepted event demonstrated on a managed test relay and decodable for Team Kitty’s existing “Specify started” presentation — is pinned by a docker-local integration test (&lt;code dir=&quot;auto&quot;&gt;tests/status/test_zeitgeist_specify_started_moment_docker_local.py&lt;/code&gt;): a real &lt;code dir=&quot;auto&quot;&gt;create_mission_core&lt;/code&gt; run publishes through the registered lifecycle handler to a real &lt;code dir=&quot;auto&quot;&gt;dkr-m1-02-zeitgeist:contract&lt;/code&gt; relay container, and the accepted frame is read back through the real &lt;code dir=&quot;auto&quot;&gt;GET /managed/events&lt;/code&gt; pull path with the panel reader’s own two-header discipline, its attrs decoding through the exact &lt;code dir=&quot;auto&quot;&gt;from_zeitgeist_attrs&lt;/code&gt; call behind the lifecycle-beat presentation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; rewrites legacy string-form &lt;code dir=&quot;auto&quot;&gt;dependencies&lt;/code&gt; frontmatter (&lt;code dir=&quot;auto&quot;&gt;&quot;[]&quot;&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;&quot;WP01, WP02&quot;&lt;/code&gt;, bare &lt;code dir=&quot;auto&quot;&gt;WP01&lt;/code&gt;) to the canonical list form&lt;/strong&gt; (#3941). Previously a string value that coerced to the resolved dependencies was left on disk verbatim; &lt;code dir=&quot;auto&quot;&gt;--validate-only&lt;/code&gt; previews the normalization and still writes nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission record-analysis&lt;/code&gt; no longer refuses with &lt;code dir=&quot;auto&quot;&gt;DIRTY_WORKTREE&lt;/code&gt; after specify or plan opens Decision Moments&lt;/strong&gt; (#3928). The Decision Moment ledger (&lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;decisions/DM-*.md&lt;/code&gt;) is now classified as coordination-partition state, like the status event log.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; records the &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; identity in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; alongside &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;&lt;/strong&gt; (#3474), so readers take it from the canonical identity source instead of re-deriving it. The value is unchanged.&lt;/li&gt;
&lt;li&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;spec-kitty research&lt;/code&gt; reject a traversal-shaped &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; slug with a clean typed error instead of a raw &lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt; traceback&lt;/strong&gt; (#2878). Both commands now print the canonical safe-path-segment diagnostic as a single &lt;code dir=&quot;auto&quot;&gt;Error:&lt;/code&gt; line and exit 2; &lt;code dir=&quot;auto&quot;&gt;next --json&lt;/code&gt; emits a structured JSON error envelope.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-5&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Hosted references and examples use &lt;code dir=&quot;auto&quot;&gt;https://team.spec-kitty.ai&lt;/code&gt;&lt;/strong&gt; (#4258). The retired hostname is removed from checked-in material; historical records use a reserved example hostname.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;400rc1---2026-09-13&quot;&gt;[4.0.0rc1] - 2026-09-13&lt;/h2&gt;
&lt;p&gt;First public release candidate for the Team Kitty 4.x line. This is a testing
prerelease, not stable launch acceptance. Install explicitly with
&lt;code dir=&quot;auto&quot;&gt;uv tool install &apos;spec-kitty-cli==4.0.0rc1&apos;&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The CLI keeps the public shared-package targets: events 9.1.6 and tracker 0.5.2.
Hosted end-to-end qualification, independent cold starts and final launch sign-off
remain tracked in planning#1999 and spec-kitty/spec-kitty-saas#1381. RC publication
makes this exact package available for that qualification; it does not claim those
checks have passed.&lt;/p&gt;
&lt;p&gt;Runtime lookup now reports &lt;code dir=&quot;auto&quot;&gt;RUN_IDENTITY_MIGRATION_REQUIRED&lt;/code&gt; when identity backfill leaves an older run without a recorded mission ID. It preserves the existing cursor and journal instead of silently starting over. The error identifies the run and explains how to bind its index entry after verifying ownership.&lt;/p&gt;
&lt;h3 id=&quot;-breaking&quot;&gt;💥 Breaking&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.status&lt;/code&gt; no longer re-exports the raw event-log writers&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;append_event&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;append_event_verified&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;append_events_atomic_verified&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;append_event_stream_atomic_verified&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;append_annotations_atomic_verified&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;append_primary_checkout_event*&lt;/code&gt;) (mission &lt;code dir=&quot;auto&quot;&gt;fsm-write-path-integrity-01M1TZV6&lt;/code&gt;). Every status-event write now goes through the status-owned transition pipeline (&lt;code dir=&quot;auto&quot;&gt;specify_cli.status.transition_pipeline.prepare_transition&lt;/code&gt;) behind one of two shells — the flat &lt;code dir=&quot;auto&quot;&gt;emit_status_transition&lt;/code&gt; or the transactional &lt;code dir=&quot;auto&quot;&gt;coordination.status_transition&lt;/code&gt; — and holds the mission status lock for its duration. Raw writers live in &lt;code dir=&quot;auto&quot;&gt;specify_cli.status._unsafe&lt;/code&gt; behind an explicit allowlist that &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_status_unsafe_allowlist.py&lt;/code&gt; and the AST writes gate &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_status_events_writes_gate.py&lt;/code&gt; enforce; &lt;code dir=&quot;auto&quot;&gt;from specify_cli.status import append_event&lt;/code&gt; is now an &lt;code dir=&quot;auto&quot;&gt;ImportError&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;’s root surface shrinks from 42 to 31 names and &lt;code dir=&quot;auto&quot;&gt;ActionContext&lt;/code&gt; is gone&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;dead-port-disposition-01M1TZVN&lt;/code&gt;, WP03). Eleven test-only re-exports (&lt;code dir=&quot;auto&quot;&gt;ArtifactPlacementFragment&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;BranchRefFragment&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;IdentityFragment&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MissionArtifactContext&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;StatusSurfaceFragment&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;WorkspaceFragment&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MissionArtifactHome&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;artifact_home_for&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ResolvedSurface&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;SurfaceLocations&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;translate_surface&lt;/code&gt;) are still defined at their modules but no longer re-exported from &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;; the &lt;code dir=&quot;auto&quot;&gt;ActionContext = MissionExecutionContext&lt;/code&gt; alias and the &lt;code dir=&quot;auto&quot;&gt;specify_cli.team_projection&lt;/code&gt; tombstone package are deleted. Two more names dropped in the same pass are easy to miss here because they belong to different packages, not &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;get_packs_root_default&lt;/code&gt; is gone from &lt;code dir=&quot;auto&quot;&gt;kernel.paths.__all__&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;content_present_at_primary_tip&lt;/code&gt; is gone from &lt;code dir=&quot;auto&quot;&gt;mission_runtime.lifecycle_phase.__all__&lt;/code&gt;. Both remain importable by their own module path, so neither breaks a caller outright, but &lt;code dir=&quot;auto&quot;&gt;kernel&lt;/code&gt;’s public surface shrank alongside &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;’s. &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_mission_runtime_surface.py&lt;/code&gt; now asserts the exact public surface.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.mission_v1.read_events&lt;/code&gt; is gone — both &lt;code dir=&quot;auto&quot;&gt;from specify_cli.mission_v1 import read_events&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;from specify_cli.mission_v1.events import read_events&lt;/code&gt; are now &lt;code dir=&quot;auto&quot;&gt;ImportError&lt;/code&gt;&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;dead-port-disposition-01M1TZVN&lt;/code&gt;, WP01/WP04). The reader had no production caller left once &lt;code dir=&quot;auto&quot;&gt;runtime.next.decision&lt;/code&gt;’s legacy DSL readers were deleted; it is renamed to the private &lt;code dir=&quot;auto&quot;&gt;_read_events&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;specify_cli.mission_v1.__all__&lt;/code&gt; now lists only &lt;code dir=&quot;auto&quot;&gt;emit_event&lt;/code&gt;. No public reader remains.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.mission_v1.load_mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;load_mission_by_name&lt;/code&gt;, and the &lt;code dir=&quot;auto&quot;&gt;MissionProtocol&lt;/code&gt; runtime-checkable protocol are gone — importing any of the three from the package root is now an &lt;code dir=&quot;auto&quot;&gt;ImportError&lt;/code&gt;&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;dead-port-disposition-01M1TZVN&lt;/code&gt;, WP01). All three were defined directly in &lt;code dir=&quot;auto&quot;&gt;mission_v1/__init__.py&lt;/code&gt; itself (&lt;code dir=&quot;auto&quot;&gt;load_mission&lt;/code&gt; was documented there as the “Auto-detecting entry point (v0 vs v1)”), not in the &lt;code dir=&quot;auto&quot;&gt;compat&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;runner&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;guards&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;schema&lt;/code&gt; submodules named below — they went with the v1 DSL runtime they dispatched to, and had no production caller.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A third-party charter pack whose &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; still authors an &lt;code dir=&quot;auto&quot;&gt;orchestration:&lt;/code&gt; block now fails to load loudly instead of the field being silently dropped&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;dead-port-disposition-01M1TZVN&lt;/code&gt;, WP03 rider T014b). The dead &lt;code dir=&quot;auto&quot;&gt;MissionOrchestration&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;MissionStateObject&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;MissionTransition&lt;/code&gt; models and the required &lt;code dir=&quot;auto&quot;&gt;Mission.orchestration&lt;/code&gt; field are removed from the charter offering schema — &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/schemas/mission.schema.yaml&lt;/code&gt; is regenerated without the &lt;code dir=&quot;auto&quot;&gt;orchestration&lt;/code&gt; definition, and the matching inert-slot baseline rows are retired — but the &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; model still declares &lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt;, so a pack that kept authoring the key is refused at load rather than tolerated (&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/fixtures/mission/invalid/retired-orchestration-key.yaml&lt;/code&gt; pins the refusal). Nothing in this repo constructed these models. Unlike the 3.2.6 &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; removal (below), &lt;strong&gt;there is no upgrade migration&lt;/strong&gt; for this key — a pack author must delete the block by hand.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-6&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A stale or mistyped org-directive activation entry no longer resolves silently, and directive resolution does less repeated filesystem work (charter directive-resolution hardening; &lt;code dir=&quot;auto&quot;&gt;#4239&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#4240&lt;/code&gt;; epic &lt;code dir=&quot;auto&quot;&gt;#2519&lt;/code&gt;).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; when an &lt;code dir=&quot;auto&quot;&gt;activated_directives&lt;/code&gt; entry named no real directive, the delivered directives service best-effort normalized it (e.g. &lt;code dir=&quot;auto&quot;&gt;007-ghost&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_007&lt;/code&gt;) and could co-activate an unrelated directive with no signal — an operator got no indication their entry was unresolved. Separately, resolving a directive re-walked every doctrine layer once per candidate filename stem (O(directives×stems) filesystem scans per resolution). &lt;strong&gt;After:&lt;/strong&gt; the service emits a per-token WARNING naming the unresolved token and the form it fell back to, so a stale/typo’d entry is visible; and a single resolution pass now walks each doctrine layer at most once. Neither change alters which directives resolve — resolution outcomes and the layer-precedence authority are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Forward-port the 3.2.6.1 first-run recovery fixes.&lt;/strong&gt; Mission creation rejects an unborn write checkout before creating artifacts, cleans up disposable scaffolds on actual commit refusals, and delays lifecycle publication until creation succeeds. Main retains its existing protected-branch bootstrap success and uncommitted-file disclosure. The tutorials continue one mission through specification and planning, active repository links use the current organization, and release tooling accepts four-component hotfix versions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The plain batch status door (&lt;code dir=&quot;auto&quot;&gt;emit_status_transition_batch&lt;/code&gt;) is fail-closed again on &lt;code dir=&quot;auto&quot;&gt;claimed -&gt; in_progress&lt;/code&gt; without a &lt;code dir=&quot;auto&quot;&gt;workspace_context&lt;/code&gt;&lt;/strong&gt; (operator decision 2026-09-07; #946; mission &lt;code dir=&quot;auto&quot;&gt;fsm-write-path-integrity-01M1TZV6&lt;/code&gt; design note WP02 row D-2, mission-review DRIFT-3). WP02 had dropped the deliberate #946 skip for door parity, so a direct batch caller that omitted the context was handed a synthetic &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;execution_mode&gt;:&amp;#x3C;root&gt;&lt;/code&gt;. The skip is reinstated as an explicit pipeline policy knob, &lt;code dir=&quot;auto&quot;&gt;prepare_transition(default_workspace_context=...)&lt;/code&gt;: the plain batch door passes &lt;code dir=&quot;auto&quot;&gt;False&lt;/code&gt; and the guard refuses with the historical &lt;code dir=&quot;auto&quot;&gt;requires workspace context&lt;/code&gt; message, persisting nothing; the flat single door and both transactional doors keep applying the default. Production callers (&lt;code dir=&quot;auto&quot;&gt;status/work_package_lifecycle.py&lt;/code&gt;) always supply the context and are unaffected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dependency gating for &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt; now resolves readiness once, in-lock, with a tri-state verdict&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;fsm-write-path-integrity-01M1TZV6&lt;/code&gt;): a work package whose declared dependencies are not all &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; is refused at claim and implement time with the blocking WP ids named. Two cases behave differently, and the difference is deliberate: a work package with &lt;strong&gt;no&lt;/strong&gt; prompt file declares nothing, so the gate opens; a prompt file whose declarations cannot be &lt;strong&gt;read&lt;/strong&gt; — unparseable frontmatter, a &lt;code dir=&quot;auto&quot;&gt;dependencies&lt;/code&gt; value the metadata model would itself refuse, or two files matching the same WP id after a half-finished rename — yields an &lt;em&gt;unsatisfied&lt;/em&gt; verdict and fails &lt;strong&gt;closed&lt;/strong&gt;, refusing &lt;code dir=&quot;auto&quot;&gt;planned -&gt; claimed&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;claimed -&gt; in_progress&lt;/code&gt; with the reason logged. &lt;code dir=&quot;auto&quot;&gt;force&lt;/code&gt; plus an actor and a reason still overrides, and &lt;code dir=&quot;auto&quot;&gt;-&gt; blocked&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;-&gt; canceled&lt;/code&gt; and the review edges are never affected by a corrupt planning artifact. The verdict lives in &lt;code dir=&quot;auto&quot;&gt;specify_cli.status.dependency_verdict&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Status locks are keyed by the mission directory name and bounded&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;fsm-write-path-integrity-01M1TZV6&lt;/code&gt;): the mission status lock (&lt;code dir=&quot;auto&quot;&gt;BOUNDED_STATUS_LOCK_TIMEOUT_SECONDS&lt;/code&gt;, 10 s) now times out with the holder named instead of waiting forever; the run-state index is keyed by &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; and a missing entry raises &lt;code dir=&quot;auto&quot;&gt;RunStateMissing&lt;/code&gt; instead of silently re-seeding; the decision-log emitter and &lt;code dir=&quot;auto&quot;&gt;migrate rebuild-state&lt;/code&gt; take the same lock as every other status writer.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The glossary-runner registration story is documented as it actually works&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;dead-port-disposition-01M1TZVN&lt;/code&gt;, WP02): the kernel registry is populated lazily by &lt;code dir=&quot;auto&quot;&gt;charter.offering.missions.glossary_hook&lt;/code&gt; at first use (self-bootstrap), not “at import time by &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;”; the contract is pinned by &lt;code dir=&quot;auto&quot;&gt;tests/doctrine/missions/test_glossary_hook.py&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;execute_with_glossary&lt;/code&gt; remains documented-but-unwired (operator decision OD6; tracked on #1868).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;runtime.next.decision&lt;/code&gt; no longer carries the legacy DSL readers &lt;code dir=&quot;auto&quot;&gt;derive_mission_state&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;evaluate_guards&lt;/code&gt;&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;dead-port-disposition-01M1TZVN&lt;/code&gt;, WP04). See the &lt;code dir=&quot;auto&quot;&gt;read_events&lt;/code&gt; removal under Breaking, above.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The CLI release train no longer compares itself against a SaaS consumer (&lt;code dir=&quot;auto&quot;&gt;#3979&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;Check Shared Package Drift&lt;/code&gt; and the tag-time &lt;code dir=&quot;auto&quot;&gt;release.yml&lt;/code&gt; used to fetch &lt;code dir=&quot;auto&quot;&gt;spec-kitty-saas/pyproject.toml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;contracts/consumer-compatibility.json&lt;/code&gt; from a sibling repository and fail the CLI when that repository’s pins disagreed. The repository they read (&lt;code dir=&quot;auto&quot;&gt;Priivacy-ai/spec-kitty-saas&lt;/code&gt;) is retired, and the live Team Kitty repository pins both shared packages by exact git revision under its own constitution rather than consuming the public PyPI train, so there is no SaaS consumer contract for a CLI release to check against. &lt;strong&gt;Before:&lt;/strong&gt; every PR touching &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; reddened on a comparison with no valid target, and a tag push could not publish without a cross-repo read token. &lt;strong&gt;After:&lt;/strong&gt; the drift check validates the CLI’s own &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; and release manifest against each other; &lt;code dir=&quot;auto&quot;&gt;release.yml&lt;/code&gt; publishes on that evidence plus the existing build and exact-install gates. Removed with it: &lt;code dir=&quot;auto&quot;&gt;scripts/release/check_candidate_consumer_compat.py&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;--saas-pyproject&lt;/code&gt; option, the manifest’s &lt;code dir=&quot;auto&quot;&gt;consumers&lt;/code&gt; block, and the &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_READ_TOKEN&lt;/code&gt; requirement. Fork PRs gain real enforcement in the exchange — the drift job used to &lt;em&gt;skip&lt;/em&gt; entirely when that token was absent, so it now checks the CLI’s own manifest where it previously reported a green skip.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;downstream-consumer-verify&lt;/code&gt; release job is removed, so a tag push publishes without a manual waiver (&lt;code dir=&quot;auto&quot;&gt;#3979&lt;/code&gt;).&lt;/strong&gt; This one failed for a different reason than the SaaS comparison above, and the distinction matters: the job checked out &lt;code dir=&quot;auto&quot;&gt;${{ github.repository_owner }}/spec-kitty-end-to-end-testing&lt;/code&gt;, which resolved to a path that no longer exists after the end-to-end suite moved to the programme org. &lt;strong&gt;The scenario it ran is not retired&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;contract_drift_caught.py&lt;/code&gt; is alive in &lt;code dir=&quot;auto&quot;&gt;spec-kitty/EXPERIMENTAL-spec-kitty-end-to-end-testing&lt;/code&gt; and remains a &lt;strong&gt;hard gate at mission review&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-mission-review&lt;/code&gt; SKILL, FR-041; ADR &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-04-26-3-e2e-hard-gate.md&lt;/code&gt;, still Accepted). What is removed is the duplicate of that gate in the publish workflow, which had been 404-ing on every tag push and forcing a &lt;code dir=&quot;auto&quot;&gt;skip_downstream=true&lt;/code&gt; waiver to release at all. &lt;strong&gt;Before:&lt;/strong&gt; no release could publish without a maintainer waiver. &lt;strong&gt;After:&lt;/strong&gt; the tag path publishes on its build and exact-install evidence, and the e2e scenario keeps gating at mission review, where it is owned.&lt;/p&gt;
&lt;p&gt;Whether the CLI (&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; 9.x from PyPI) and Team Kitty (10.x by git rev) agree on the event wire contract is a shared-package publication question, not a CLI CI gate. The surface that owns it is that same e2e scenario at mission review — the removed workflow job never exercised a wire, only compared declared pins.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The mission-DSL v1 runtime and its &lt;code dir=&quot;auto&quot;&gt;transitions&lt;/code&gt; dependency are removed&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;dead-port-disposition-01M1TZVN&lt;/code&gt;, WP01). &lt;code dir=&quot;auto&quot;&gt;specify_cli.mission_v1.{compat,runner,guards,schema}&lt;/code&gt; — the &lt;code dir=&quot;auto&quot;&gt;transitions&lt;/code&gt;-backed state machine, guard compiler, JSON-Schema validator and v0 wrapper — had no production caller; the surviving module &lt;code dir=&quot;auto&quot;&gt;specify_cli.mission_v1.events&lt;/code&gt; keeps &lt;code dir=&quot;auto&quot;&gt;emit_event&lt;/code&gt; (used by the &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; runtime loop), but its reader is renamed to the private &lt;code dir=&quot;auto&quot;&gt;_read_events&lt;/code&gt; and the package no longer re-exports a public reader — see Breaking, above. The &lt;code dir=&quot;auto&quot;&gt;states:&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;transitions:&lt;/code&gt; blocks are deleted from both built-in &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; catalogs for &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; — the &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; tier-5 defaults and the &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt; catalog the v0 loader ships in the wheel — and a new architectural detector keeps them from returning to either; the keys stay tolerated in third-party and &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; files via &lt;code dir=&quot;auto&quot;&gt;MISSION_COMPAT_IGNORED_FIELDS&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;transitions&lt;/code&gt; (and the &lt;code dir=&quot;auto&quot;&gt;six&lt;/code&gt; it dragged in) no longer load when a mission event is emitted; the subprocess ratchet &lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/mission_v1/test_import_hygiene.py&lt;/code&gt; pins that invariant permanently. No version bump (the rc cycle is already open).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The Convergence (&lt;code dir=&quot;auto&quot;&gt;#3881&lt;/code&gt;, merged 2026-09-05) folded the EXPERIMENTAL development line onto public &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;.&lt;/strong&gt; The merge relocated the doctrine Python package &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/&lt;/code&gt; (mission &lt;code dir=&quot;auto&quot;&gt;charter-code-topology-01M152G1&lt;/code&gt;, CR-06; &lt;code dir=&quot;auto&quot;&gt;src/doctrine.py&lt;/code&gt; remains as a deprecation shim), retired the local CLI→SaaS sync transport, the &lt;code dir=&quot;auto&quot;&gt;delivery&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;event-journal&lt;/code&gt; emit stack, and the &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/saas/&lt;/code&gt; package (mission status is now ephemeral by design; team artifacts render server-side), and removed SonarCloud from CI (the &lt;code dir=&quot;auto&quot;&gt;sonarcloud&lt;/code&gt; job died with the old 4118-line &lt;code dir=&quot;auto&quot;&gt;ci-quality.yml&lt;/code&gt;). Architectural gates (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_retired_subsystems.py&lt;/code&gt; + a &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; TID251 ban block) keep the retired subsystems from silently returning. Living architecture docs and &lt;code dir=&quot;auto&quot;&gt;CLAUDE.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt; were realigned to the post-convergence topology in this cycle, and the self-declared module-ownership manifest &lt;code dir=&quot;auto&quot;&gt;docs/architecture/05_ownership_manifest.yaml&lt;/code&gt; was deleted (&lt;code dir=&quot;auto&quot;&gt;#3888&lt;/code&gt;) — it had drifted to naming trees the convergence removed, and its schema gate pinned that stale vocabulary, so correcting it reddened the gate. Module boundaries are now owned by the enforced pair (&lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; wheel packages + the &lt;code dir=&quot;auto&quot;&gt;test_layer_rules.py&lt;/code&gt; layer chain); &lt;code dir=&quot;auto&quot;&gt;05_ownership_map.md&lt;/code&gt; survives as a demoted narrative pointing at it.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-7&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Drupal work now has a specialist agent profile — Drupal Dries — so a Drupal mission gets an implementer that already knows the framework’s conventions instead of a generic one you have to coach.&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; a Drupal work package could only be routed to a generic implementer or a wrong-stack specialist (Java Jenny, Node Norris), so module structure, dependency injection, the Entity API, configuration management and Drupal’s test tiers had to be explained by hand on every task, and mistakes surfaced in review rather than being avoided. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;drupal-dries&lt;/code&gt; ships in the built-in pack as an implementer-role specialist covering Drupal 10.x/11.x backend work (modules, services and DI, Entity API, plugins, hooks, Forms API, routing, configuration management, Batch/Queue/Migration) and Drupal-native theming (Twig, &lt;code dir=&quot;auto&quot;&gt;*.libraries.yml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;Drupal.behaviors&lt;/code&gt;, render arrays, preprocess). It arrives with two styleguides — &lt;code dir=&quot;auto&quot;&gt;drupal-conventions&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;drupal-security-performance&lt;/code&gt;, carrying all fourteen of the community “never do this” anti-patterns as paired wrong/right examples — and a &lt;code dir=&quot;auto&quot;&gt;drupal-review-checks&lt;/code&gt; toolguide naming the phpcs, phpstan, drupal-check, composer audit and PHPUnit tier commands a reviewer should expect, written so they work whether or not the project runs in a container. Where its territory meets Frontend Freddy’s, both profiles now say so: Dries owns Drupal-native theming, and Freddy defers framework-native theming layers to the stack specialist for that framework. The profile ships &lt;strong&gt;inactive&lt;/strong&gt; — activate it with &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate agent-profile drupal-dries&lt;/code&gt; when you want it. Distilled from amazee.io’s community &lt;code dir=&quot;auto&quot;&gt;drupal-agents-md&lt;/code&gt; guide, with one factual error in that source corrected against Drupal’s own change record (implicit entity-query access checking was deprecated in 9.2.0 and throws from 10.0.0 — it is not, as the source states, deferred to Drupal 12).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;migrate-project-guidance-to-spec-kitty-charter&lt;/code&gt; procedure now captures the source’s vocabulary in the glossary&lt;/strong&gt; (#4103). A new step between classification and drafting extracts the terms the guidance defines or uses with a specific meaning, triages them through the &lt;code dir=&quot;auto&quot;&gt;glossary-maintenance-workflow&lt;/code&gt; procedure into the narrowest owning scope, and makes the accepted surfaces the vocabulary the drafted artifacts must use verbatim. The exit condition and the parity-comparison step now require every defined term to resolve in the glossary or be excluded with a reason, and the procedure references &lt;code dir=&quot;auto&quot;&gt;procedure:glossary-maintenance-workflow&lt;/code&gt; in the DRG.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The glossary skill now pressure-tests a contested or load-bearing domain-model term before recording it, instead of accepting the first plausible definition (&lt;code dir=&quot;auto&quot;&gt;#3835&lt;/code&gt;).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty-glossary-context&lt;/code&gt; curated terminology and checked drift, but had no step that challenged a proposed domain-model term against the actual code or a concrete edge case, and no guidance on when a term decision warranted an ADR — so a shaky model claim could be written into the glossary as if it were settled. &lt;strong&gt;After:&lt;/strong&gt; a new “Pressure-Test Domain Model Terms” step cross-checks the claim against the real domain types, API contracts, and tests (labelling it a hypothesis when code evidence is missing), challenges it with at least one concrete edge case, and raises an ADR only when the decision is hard to reverse, surprising without context, and a genuine trade-off. Two triggers (“shape a domain model’s terms”, “validate domain language against code”) route that work in, and &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-glossary&lt;/code&gt; now hands contested-term and domain-model work to the detailed workflow. The step points at the canonical &lt;code dir=&quot;auto&quot;&gt;domain-aware-decision-interview&lt;/code&gt; procedure and &lt;code dir=&quot;auto&quot;&gt;adr-drafting-workflow&lt;/code&gt; tactic it summarises. Instruction-only, and it skips cleanly for an ordinary canonical usage correction.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;GitHub CI is back on public &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; — every push and pull request runs a bounded, path-scoped test pipeline again, and SonarCloud analysis returns (&lt;code dir=&quot;auto&quot;&gt;#3995&lt;/code&gt;).&lt;/strong&gt; The Convergence (&lt;code dir=&quot;auto&quot;&gt;#3881&lt;/code&gt;) had removed the heavyweight CI and SonarCloud, leaving public &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; with only the archived EXPERIMENTAL Blacksmith producer — so a contributor’s pull request got no real test signal on GitHub and had to be validated externally. &lt;strong&gt;Before:&lt;/strong&gt; no shift-left test/coverage/quality signal on a pull request, and the sole producer pointed at a retired private repository. &lt;strong&gt;After:&lt;/strong&gt; a lean set of artifact-sharing GitHub Actions — a path router feeding a single gate-selection authority, a duration-balanced per-module test matrix, coverage/xunit aggregation with a diff-cover &gt;=90% changed-lines gate, a nightly full/performance/interpreter run, a packs lane, and a fork-safe SonarCloud workflow — runs on stock runners with no privileged token on public jobs. On a pull request the pipeline is fail-fast (a red predecessor short-circuits its successors, and a skipped job never counts as green); the nightly and manual runs execute everything. The reinstated pipeline is the sole/primary public producer, and machine oracles keep dead/retired code out of the selected suite and prove no test is selected by zero gates.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty routes&lt;/code&gt; tells you which team this checkout is connected to and where its activity goes — the question &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync routes&lt;/code&gt; used to answer, before the old sync transport was removed (Priivacy-ai/spec-kitty#10).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; once the CLI→SaaS sync transport (and its &lt;code dir=&quot;auto&quot;&gt;sync routes&lt;/code&gt; command) was removed, there was no way to check whether a checkout was actually connected to a team, or where its mission updates were going. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty routes&lt;/code&gt; reports, for this checkout, which team has admitted it and which relay — the server that carries a team’s live mission updates — receives its activity; if no team has admitted the checkout, it says so plainly, and that is a normal, expected answer, not a failure. It answers instantly from a local cache when it can (a previously stored authorization, or a remembered “not admitted” answer, both usable without being logged in) and only contacts Team Kitty over the network — to request, or “mint,” a fresh authorization — when nothing is cached. It always reports honestly which of those it found: admitted, confirmed not admitted, or “couldn’t get an answer this run” — never dressing up silence as “not admitted”.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty events tail&lt;/code&gt; streams a mission’s event log as JSON lines, so an external consumer (a dashboard, a CI watcher, a native driver) can follow status changes live and resume exactly where it left off (#3858; closes #3841).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; there was no supported way to observe a mission’s &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; incrementally — a consumer had to re-read the whole file and diff it, and because that log is &lt;em&gt;not&lt;/em&gt; append-only (it is truncated in place on a coordination rollback) a naive tailer silently desynced when the file shrank or was rewritten. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty events tail --mission &amp;#x3C;slug&gt; --json&lt;/code&gt; emits each event as a JSON line, injecting a &lt;code dir=&quot;auto&quot;&gt;tail_offset&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;tail_invariant&lt;/code&gt; cursor a consumer persists and supplies back with &lt;code dir=&quot;auto&quot;&gt;--from-offset&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--from-invariant&lt;/code&gt; to resume; a mismatched resume cursor is &lt;strong&gt;refused&lt;/strong&gt; (structured stderr, non-zero exit — never a silent reset). All three truncation shapes — a mid-append tear, a clean record-boundary shrink, and a truncate-then-regrow within one poll — are detected (size check + SHA-256 content invariant, evaluated independently every poll), so the stream stays correct across rollbacks. &lt;code dir=&quot;auto&quot;&gt;--once&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--max-events N&lt;/code&gt; bound the stream for scripted use. See &lt;a href=&quot;/api/cli-commands/#spec-kitty-events&quot;&gt;CLI reference § &lt;code dir=&quot;auto&quot;&gt;spec-kitty events&lt;/code&gt;&lt;/a&gt;. &lt;em&gt;(Moved here from the 3.2.6 section: this landed 2026-09-05, after the 2026-09-03 &lt;code dir=&quot;auto&quot;&gt;v3.2.6&lt;/code&gt; tag, and belongs to 3.2.7rc1.)&lt;/em&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-7&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor &amp;#x3C;cmd&gt; --json&lt;/code&gt; printed the human string &lt;code dir=&quot;auto&quot;&gt;Error: Not in a spec-kitty project&lt;/code&gt; on stdout (exit 1) instead of JSON whenever it ran outside a spec-kitty project, so &lt;code dir=&quot;auto&quot;&gt;doctor &amp;#x3C;cmd&gt; --json | jq&lt;/code&gt; got a parse error indistinguishable from a crash (&lt;code dir=&quot;auto&quot;&gt;#4242&lt;/code&gt;).&lt;/strong&gt; The not-in-project guard ran before the &lt;code dir=&quot;auto&quot;&gt;if json_output:&lt;/code&gt; branch and never consulted &lt;code dir=&quot;auto&quot;&gt;json_output&lt;/code&gt;, while the same commands’ success path emitted well-formed JSON — a contract inconsistency between exit paths. &lt;strong&gt;Before:&lt;/strong&gt; sixteen &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; doctor subcommands leaked prose on stdout on this path — twelve in &lt;code dir=&quot;auto&quot;&gt;doctor.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;state-roots&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;workspaces&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;identity&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;topology&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;shim-registry&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;contracts&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;invocation-pairing&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ops&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;cutover&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review-cycle-reconcile&lt;/code&gt;) and four in sibling modules (&lt;code dir=&quot;auto&quot;&gt;command-files&lt;/code&gt;, &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;coordination&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;mission-state --json&lt;/code&gt; leaked identically on its real not-in-project path (&lt;code dir=&quot;auto&quot;&gt;locate_project_root&lt;/code&gt; &lt;em&gt;returns&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; outside a project rather than raising, and the terminal error inside &lt;code dir=&quot;auto&quot;&gt;_resolve_audit_root&lt;/code&gt; ignored &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;); and &lt;code dir=&quot;auto&quot;&gt;tool-surfaces&lt;/code&gt;’ raise branch emitted the raw exception text as the error message instead of the canonical one. &lt;strong&gt;After:&lt;/strong&gt; every doctor &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; command routes its not-in-project error through one canonical renderer (&lt;code dir=&quot;auto&quot;&gt;_doctor_shared._emit_not_in_project&lt;/code&gt;), so &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; stdout is a machine-parseable &lt;code dir=&quot;auto&quot;&gt;{&quot;ok&quot;: false, &quot;error&quot;: {&quot;code&quot;: &quot;not_in_project&quot;, &quot;message&quot;: &quot;Not in a spec-kitty project&quot;}}&lt;/code&gt; object on both failure modes (raise and returned &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt;) and the human path keeps its Rich prose. &lt;code dir=&quot;auto&quot;&gt;mission-state&lt;/code&gt; threads &lt;code dir=&quot;auto&quot;&gt;json_output&lt;/code&gt; through to that renderer (a &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; root &lt;em&gt;with&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;--fixture-dir&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--include-fixtures&lt;/code&gt; is still the valid fixtures-only state; a &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; root &lt;em&gt;without&lt;/em&gt; fixtures is the terminal not-in-project error and now honors &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;). Each command keeps its own documented not-in-project exit code (1 for most; 2 for the config-error family &lt;code dir=&quot;auto&quot;&gt;shim-registry&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;contracts&lt;/code&gt; and for &lt;code dir=&quot;auto&quot;&gt;skills&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tool-surfaces&lt;/code&gt;). A parametrized class-closing gate (&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/cli/commands/test_doctor_json_not_in_project.py&lt;/code&gt;) pins the contract for every affected command on both the &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; and the raise path.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;interview&lt;/code&gt; could not adopt an org-pack directive whose declared ID differs from its filename — the very IDs &lt;code dir=&quot;auto&quot;&gt;doctor doctrine&lt;/code&gt; and the delivered &lt;code dir=&quot;auto&quot;&gt;DoctrineService.directives&lt;/code&gt; resolved fine (&lt;code dir=&quot;auto&quot;&gt;#4194&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#4185&lt;/code&gt;).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; the activation path matched directives by filename stem and legacy alias only, so a declared ID that did not resemble its stem was invisible to selection, promotion, and delivery; worse, when an ambiguous mandatory directive was selected, generation skipped it silently and still reported success, and an ambiguous ID could persist and later resolve to the &lt;em&gt;wrong&lt;/em&gt; org policy. &lt;strong&gt;After:&lt;/strong&gt; resolution accepts an exact declared directive ID after a filename-stem miss, selection prefers a declared ID over a coincident filename, interview promotion reports ambiguous selections while keeping valid siblings, and generation refuses an ambiguous mandatory org directive before it changes any charter/configuration state. A filename stem that two layers bind to different identities is rejected as unrepresentable, so an ambiguous ID fails closed instead of resolving to the wrong policy. Writers still persist identity-preserving filename stems; unknown IDs and non-directive kinds keep their existing validation.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Every shipped step contract’s governance-context bootstrap command failed to parse, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context&lt;/code&gt; exited 2 with &lt;code dir=&quot;auto&quot;&gt;No such option: --role&lt;/code&gt; for every mission action (&lt;code dir=&quot;auto&quot;&gt;#4049&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#4031&lt;/code&gt;).&lt;/strong&gt; The bootstrap step of all 17 built-in step contracts — specify, plan, tasks, implement, review, the five research steps and the seven documentation steps — declared &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --action &amp;#x3C;x&gt; --role &amp;#x3C;x&gt; --json&lt;/code&gt;, but the CLI has no &lt;code dir=&quot;auto&quot;&gt;--role&lt;/code&gt; option. &lt;strong&gt;Before:&lt;/strong&gt; an operator or agent host that ran the declared command verbatim (the governance-context bootstrap every mission action begins with) hit an exit-2 parse error, not the governance context; the flag was pure noise — its value was always identical to &lt;code dir=&quot;auto&quot;&gt;--action&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;--role&lt;/code&gt; flag is dropped from all 17 contracts (and the five research &lt;code dir=&quot;auto&quot;&gt;prompt.md&lt;/code&gt; mirrors); the command parses and returns governance context. A new corpus guard (&lt;code dir=&quot;auto&quot;&gt;tests/doctrine/mission_step_contracts/test_declared_commands_parse.py&lt;/code&gt;) walks the real Click tree and parses every command a shipped contract declares, so a contract can no longer advertise a flag the parser does not have.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Two &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; commands started at the same moment against a shared home directory could crash the second one with &lt;code dir=&quot;auto&quot;&gt;Global asset input changed&lt;/code&gt; instead of both succeeding (&lt;code dir=&quot;auto&quot;&gt;#4017&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#4174&lt;/code&gt;).&lt;/strong&gt; The first run of &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; on a machine (or the first after an upgrade) installs its runtime assets into &lt;code dir=&quot;auto&quot;&gt;~/.spec-kitty&lt;/code&gt;; a lock already serialized those cold installers so only one wrote at a time. &lt;strong&gt;Before:&lt;/strong&gt; the waiting run re-checked against the &lt;em&gt;stale&lt;/em&gt; empty-home picture it had captured before the lock, then tried to apply non-idempotent create steps (&lt;code dir=&quot;auto&quot;&gt;mkdir&lt;/code&gt;, exclusive-create) over files the winner had just written — and aborted with &lt;code dir=&quot;auto&quot;&gt;Global asset input changed&lt;/code&gt; (or, after a naive narrowing, &lt;code dir=&quot;auto&quot;&gt;File exists&lt;/code&gt;). Anyone running two agents, a CI fan-out, or two shells that shared one home hit it. &lt;strong&gt;After:&lt;/strong&gt; the waiting run re-assesses &lt;em&gt;under&lt;/em&gt; the lock against the now-warmed home, finds nothing left to do, and returns cleanly; a warm home still takes no lock and checks exactly once. A genuine change to the packaged asset &lt;em&gt;sources&lt;/em&gt; between check and apply is still caught and refused, so the fix narrows only harmless races, not real drift.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A corrupt &lt;code dir=&quot;auto&quot;&gt;__pycache__/*.pyc&lt;/code&gt; left by an interrupted &lt;code dir=&quot;auto&quot;&gt;pip&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;uv tool&lt;/code&gt; install crashed &lt;em&gt;every&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; command at startup with a raw traceback instead of self-healing (&lt;code dir=&quot;auto&quot;&gt;#4124&lt;/code&gt;; observed on a Windows training machine as &lt;code dir=&quot;auto&quot;&gt;AttributeError: &apos;bytes&apos; object has no attribute &apos;co_filename&apos;&lt;/code&gt; traced to &lt;code dir=&quot;auto&quot;&gt;specify_cli/upgrade/migrations/base.py&lt;/code&gt;).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;cli/commands/upgrade.py&lt;/code&gt; imports &lt;code dir=&quot;auto&quot;&gt;specify_cli.upgrade.runner&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;migrations.base&lt;/code&gt; at module level, so one truncated bytecode cache killed app assembly for every command — including &lt;code dir=&quot;auto&quot;&gt;spec-kitty dashboard&lt;/code&gt; — before any command ran, and the only recovery was insider knowledge (find the installed package, delete its &lt;code dir=&quot;auto&quot;&gt;__pycache__&lt;/code&gt;). &lt;strong&gt;After:&lt;/strong&gt; CLI app assembly, the compat-planner migration-registry load (the upgrade-nag hook on every command’s startup path), and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;’s discovery step each run through a bytecode self-heal seam (&lt;code dir=&quot;auto&quot;&gt;specify_cli.bytecode_heal&lt;/code&gt;): an import failure plausibly caused by a stale cache — &lt;code dir=&quot;auto&quot;&gt;ValueError: bad marshal data&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;EOFError: marshal data too short&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ImportError: Non-code object in &apos;…pyc&apos;&lt;/code&gt;, or the field &lt;code dir=&quot;auto&quot;&gt;co_filename&lt;/code&gt; AttributeError — purges the installed package’s derived &lt;code dir=&quot;auto&quot;&gt;*.pyc&lt;/code&gt; caches (always safe: Python recompiles from source), invalidates the import caches, and retries exactly once, with a one-line warning telling the operator what was repaired. Genuine failures still propagate: the planner seam degrades loudly to “migrations unavailable” (empty registry, upgrade nag/preview skipped, warning names the manual fix) instead of the old silent &lt;code dir=&quot;auto&quot;&gt;except: pass&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; still surfaces real discovery errors. Deleting a &lt;code dir=&quot;auto&quot;&gt;.pyc&lt;/code&gt; never deletes source; a fully-zeroed cache file was already self-healing via the bytecode magic-number check.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; froze &lt;code dir=&quot;auto&quot;&gt;planning_commit_sha&lt;/code&gt; with no refresh path, so a mission that amended its planning mid-execution needed &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; on every subsequent &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#4141&lt;/code&gt;; reported from a real 9-WP mission whose every WP required overrides).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; once execution began (any WP past &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt;), a re-finalize correctly PRESERVED the recorded planning SHA (#3311) — but preserve-only meant a legitimate planning amendment that landed afterward (a WP dependency-field fix, an &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.analyze&lt;/code&gt; remediation) could never advance it: every subsequently allocated lane merged the stale planning snapshot, the &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; branch-currency / &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;-contamination / uncommitted-changes gates fired on the resulting drift, and the only in-tool path was &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; (or hand-editing &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;). &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission finalize-tasks --refresh-planning-commit&lt;/code&gt; re-points the recorded SHA to the current target-branch tip so lanes merge the amended planning state at their next allocation — advance-only: it is refused, with &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; untouched, when the recorded SHA is not an &lt;em&gt;ancestor&lt;/em&gt; of the tip (a history rewrite, not an amendment). Without the flag the #3311 preserve behavior is unchanged, but a re-finalize that detects drift (recorded SHA ≠ branch tip) now says so on the console and names the flag, and the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; success payload carries the decision under &lt;code dir=&quot;auto&quot;&gt;planning_commit&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;sha&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;previous_sha&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;branch_tip&lt;/code&gt;); the orchestrator-api &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; verb passes it through (contract 1.5.0). See &lt;a href=&quot;/api/finalize-tasks-internals/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; internals §3&lt;/a&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 init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; crashed on Windows the first time they wrote a skill, command, or agent-rules file (&lt;code dir=&quot;auto&quot;&gt;#3173&lt;/code&gt;, and its siblings across the install path).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; the skills/tool-surface/session-presence writers and the coordination confined-write used POSIX-only primitives — &lt;code dir=&quot;auto&quot;&gt;os.fchmod&lt;/code&gt;, a bare &lt;code dir=&quot;auto&quot;&gt;os.O_NOFOLLOW&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;dir_fd&lt;/code&gt;-relative writes — that do not exist on Windows, so a fresh onboarding died with an &lt;code dir=&quot;auto&quot;&gt;AttributeError&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt; before the user reached a single mission. &lt;strong&gt;After:&lt;/strong&gt; every one of those writers routes through one shared capability check and falls back to a path-based write on platforms without &lt;code dir=&quot;auto&quot;&gt;dir_fd&lt;/code&gt;, preserving the same no-symlink-following and containment guarantees; on Linux/macOS the original fd-relative path is unchanged. A Windows user can now &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; a project.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty dashboard&lt;/code&gt; reported a running dashboard on Windows that was silently dead (&lt;code dir=&quot;auto&quot;&gt;#4125&lt;/code&gt;).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; the background server was launched with &lt;code dir=&quot;auto&quot;&gt;python -c &quot;&amp;#x3C;script&gt;&quot;&lt;/code&gt;, whose child crashes on import (Windows has no &lt;code dir=&quot;auto&quot;&gt;__main__.__file__&lt;/code&gt;), and its output went to a black hole (&lt;code dir=&quot;auto&quot;&gt;DEVNULL&lt;/code&gt;) with no check that it ever came up — so the CLI printed ”✅ Started” for a process that had already exited, and the ephemeral-port path additionally raised outright on Windows. &lt;strong&gt;After:&lt;/strong&gt; the server launches as a real module (&lt;code dir=&quot;auto&quot;&gt;python -m specify_cli.dashboard._server_main&lt;/code&gt;), its output goes to a log file under the runtime state dir, and the CLI now waits for the port to actually serve &lt;em&gt;this project’s&lt;/em&gt; dashboard identity over &lt;code dir=&quot;auto&quot;&gt;/api/health&lt;/code&gt; (resolved &lt;code dir=&quot;auto&quot;&gt;project_path&lt;/code&gt;, plus the token when one was handed to the child — the same contract the lifecycle health check enforces), reaping the child and surfacing its log tail if it dies, before reporting success; a foreign dashboard that won the same free-port race can never stand in for the spawn. The same &lt;code dir=&quot;auto&quot;&gt;python -c&lt;/code&gt; fix was applied to the background upgrade-check refresh.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Resynthesis resolves activated IDs across built-in, org and project layers&lt;/strong&gt; (#4101). Project profiles use the same precedence as profile inspection. Eager activation checks synthesis prerequisites and the proposed selection before writing activations; lookup errors identify the charter activation store and searched layers.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Agent-profile cascade reaches directly authored project guidance&lt;/strong&gt; (#4100). &lt;code dir=&quot;auto&quot;&gt;--cascade all&lt;/code&gt; activates referenced procedures, directives, tactics and styleguides from a clean deactivated state, and missing project references produce explicit warnings.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Directly authored project doctrine enters the project graph and provenance during activation&lt;/strong&gt; (#4097). Procedures and agent profiles are registered alongside directives, tactics and styleguides without rewriting their source files. Charter status counts all five kinds and the shipped authoring skill documents their paths.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Glossary show resolves seed-only terms&lt;/strong&gt; (#4102). When no compiled entity page exists, &lt;code dir=&quot;auto&quot;&gt;glossary show&lt;/code&gt; reads the same seed and event store as &lt;code dir=&quot;auto&quot;&gt;glossary list&lt;/code&gt;, rendering each scoped definition without requiring compilation.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Charter exposes project authoring and org pack commands&lt;/strong&gt; (#4098). &lt;code dir=&quot;auto&quot;&gt;charter new&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;validate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;org&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;fetch&lt;/code&gt; delegate to the existing doctrine handlers. Deprecation guidance identifies commands that remain under &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A coord-topology mission’s per-work-package completion check silently did nothing, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; would advance a mission out of &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; even when a work package had never been claimed (&lt;code dir=&quot;auto&quot;&gt;#3981&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3884&lt;/code&gt;).&lt;/strong&gt; &lt;strong&gt;Before:&lt;/strong&gt; for any mission that routes lifecycle through a coordination worktree, the per-WP completion gate looked for &lt;code dir=&quot;auto&quot;&gt;tasks/WP*.md&lt;/code&gt; under the coordination worktree’s own directory — files that only ever live on the PRIMARY partition — so the lookup always missed and the gate reported “all work packages done” unconditionally on &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, skipping the per-WP loop entirely regardless of any package’s lane. A work package that was scaffolded but never claimed (or merely in progress and not yet handed off) was never caught. &lt;strong&gt;After:&lt;/strong&gt; the completion check anchors its &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; read to the PRIMARY partition through the placement seam, and a never-claimed (&lt;code dir=&quot;auto&quot;&gt;uninitialized&lt;/code&gt;) or never-lifecycled (&lt;code dir=&quot;auto&quot;&gt;genesis&lt;/code&gt;) work package correctly blocks the &lt;code dir=&quot;auto&quot;&gt;implement -&gt; review&lt;/code&gt; advance; an ambiguous mission handle blocks with a structured message rather than silently falling through. &lt;strong&gt;Operator note:&lt;/strong&gt; any coord-topology mission currently sitting in &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; with a work package not yet handed off, blocked, or rejected-with-operator-provenance will newly — and correctly — block on its next advance, so spot-check in-flight coord-topology missions after upgrading.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A future runtime event producer could crash &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; at import time, or be silently replaced by a second one, instead of failing safely (&lt;code dir=&quot;auto&quot;&gt;#3983&lt;/code&gt;; follow-up to &lt;code dir=&quot;auto&quot;&gt;#3921&lt;/code&gt;, ADR &lt;code dir=&quot;auto&quot;&gt;2026-09-06-2&lt;/code&gt;).&lt;/strong&gt; The runtime emitter seam that &lt;code dir=&quot;auto&quot;&gt;#3921&lt;/code&gt; opened for a real event producer had two unguarded edges. &lt;strong&gt;Before:&lt;/strong&gt; registering a producer twice — which happens on an ordinary double import — raised an uncaught error that killed the command outright; two different producers registering resolved by import order, last one silently winning, with nothing logged to say which; and a producer whose constructor failed (missing config, an unreachable credential lookup) took &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; down with it. &lt;strong&gt;After:&lt;/strong&gt; re-registering the same producer is a no-op, a genuinely different second producer is refused with a message naming both, and a producer that fails to construct is logged at WARNING and degrades to the do-nothing seam — the run continues. No producer ships yet, so nothing changes for users today; this is the seam being made safe before the first one arrives.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Decision requests raised under the strict retrospective policy (&lt;code dir=&quot;auto&quot;&gt;before_completion&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;block&lt;/code&gt;) and on composition dispatch were never written to the mission’s &lt;code dir=&quot;auto&quot;&gt;decisions.events.jsonl&lt;/code&gt; (ADR &lt;code dir=&quot;auto&quot;&gt;2026-09-06-2&lt;/code&gt;; mission &lt;code dir=&quot;auto&quot;&gt;dead-port-disposition-01M1VRA2&lt;/code&gt;).&lt;/strong&gt; The runtime bridge buffered those decision events correctly but flushed them to the plain no-op emitter seam instead of the decision-log wrapper, and handed the same plain seam to the composition dispatch path, so the events were dropped in silence — the operator saw a decision gate with no record of the request behind it. &lt;strong&gt;Before:&lt;/strong&gt; the runtime’s decision log had gaps exactly where the strictest policy ran. &lt;strong&gt;After:&lt;/strong&gt; every buffered decision request is appended to the mission’s decision log exactly once, and the rollback on a refused gate is unchanged. The permanently no-op concrete &lt;code dir=&quot;auto&quot;&gt;RuntimeEventEmitter&lt;/code&gt; class (&lt;code dir=&quot;auto&quot;&gt;runtime.next.event_emitter&lt;/code&gt;) that shadowed the canonical runtime seam was deleted and consolidated onto the runtime Protocol / &lt;code dir=&quot;auto&quot;&gt;NullEmitter&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;runtime.next._internal_runtime.events&lt;/code&gt;, which now exposes a &lt;code dir=&quot;auto&quot;&gt;runtime_emitter_for_mission&lt;/code&gt; factory and a &lt;code dir=&quot;auto&quot;&gt;register_runtime_emitter_factory&lt;/code&gt; hook for a future real producer; an architectural guard (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_runtime_emitter_seam.py&lt;/code&gt;) keeps the single-class seam and the decision-log wiring from regressing.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A project could be handed the wrong governance — SPDD/REASONS guidance, org-required directives, tactics and paradigms — whenever its &lt;em&gt;active&lt;/em&gt; configuration had drifted from what it originally authored (&lt;code dir=&quot;auto&quot;&gt;#3871&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3838&lt;/code&gt;).&lt;/strong&gt; Four charter surfaces decided what doctrine to deliver by reading the authoring record (&lt;code dir=&quot;auto&quot;&gt;selected_*&lt;/code&gt;) instead of the resolved authority (&lt;code dir=&quot;auto&quot;&gt;activated_*&lt;/code&gt;), so a project whose activation differed from its authored set quietly received doctrine it never activated — and missed doctrine it did — with no error and no warning. Activation is now the single authority across all four surfaces: every directive, tactic and paradigm identifier is canonicalized at the moment it enters a union, an identifier whose form cannot be canonicalized fails loud instead of being silently dropped, and an absent activation set resolves to the documented built-in catalog default rather than collapsing to an empty set.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;326---2026-09-03&quot;&gt;[3.2.6] - 2026-09-03&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;The stabilization release: fail-loud honesty across the workflow, plus &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; 1.4.0 opening the full design pipeline to external hosts. Consolidated operator-facing notes: &lt;a href=&quot;/changelog/release-notes-3.2.6/&quot;&gt;release-notes-3.2.6.md&lt;/a&gt;.&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&quot;-breaking--️-removed&quot;&gt;💥 Breaking / 🗑️ Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Breaking — the redundant &lt;code dir=&quot;auto&quot;&gt;context-sources.*&lt;/code&gt; agent-profile surface is removed from the schema; profiles author references solely on the top-level &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt; fields&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-drg-silent-drop-boundary-01M0PE7E&lt;/code&gt;, WP02; #3629 p1). The &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; block (&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;) duplicated the canonical, DRG-provisioned &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; surface and was mostly inert; only &lt;code dir=&quot;auto&quot;&gt;context-sources.directives&lt;/code&gt; minted a DRG edge, and every shipped profile already carried the same ids on &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt;. &lt;strong&gt;Before:&lt;/strong&gt; two parallel reference surfaces, one of which was silently dropped on delivery. &lt;strong&gt;After:&lt;/strong&gt; one canonical surface — the model now declares &lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt; without a &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; field, so a profile still authoring the block &lt;strong&gt;fails to load loudly&lt;/strong&gt; rather than dropping it in silence. The extractor now projects &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; DRG edges from &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;directive-references&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic-references&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;, and &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;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;). A consumer project that authored custom profiles with &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; is migrated automatically by the &lt;code dir=&quot;auto&quot;&gt;3_3_1_context_sources_consolidation&lt;/code&gt; upgrade migration, which &lt;strong&gt;set-merges&lt;/strong&gt; every reference id onto the matching &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt; field (deduped, never appended) and drops the edge-less &lt;code dir=&quot;auto&quot;&gt;doctrine-layers&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;additional&lt;/code&gt; names with a logged note. Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; (the migration is idempotent and safe to re-run); free-text &lt;code dir=&quot;auto&quot;&gt;additional&lt;/code&gt; bindings with no artifact-id shape are reported, not silently discarded.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Breaking/removal — the legacy CLI→SaaS sync transport and its 22 subcommands are gone: &lt;code dir=&quot;auto&quot;&gt;routes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;share&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;unshare&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;opt-out&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;opt-in&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;import-history&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;workspace&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;server&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;now&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;gc&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;archive&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;purge&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project_store_preview&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project_store_migrate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project_store_status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project_store_quarantine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project_store_history&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;migrate&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mode&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;diagnose&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt;.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;delivery&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;event_journal&lt;/code&gt;, and legacy &lt;code dir=&quot;auto&quot;&gt;saas&lt;/code&gt; packages, the &lt;code dir=&quot;auto&quot;&gt;websockets&lt;/code&gt; runtime dependency, and &lt;code dir=&quot;auto&quot;&gt;doctor restart-daemon&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;doctor orphan-daemons&lt;/code&gt; are removed with it. &lt;code dir=&quot;auto&quot;&gt;auth doctor --reset&lt;/code&gt; and its sync-era diagnostic sweep are also gone; the narrowly scoped &lt;code dir=&quot;auto&quot;&gt;auth doctor --unstick-lock&lt;/code&gt; token-refresh repair remains live. The &lt;code dir=&quot;auto&quot;&gt;tracker&lt;/code&gt; command group is registered unconditionally and gated at invocation by &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC&lt;/code&gt;, while the plugin-facing &lt;code dir=&quot;auto&quot;&gt;disable_public_pypi_notifier&lt;/code&gt; rename to &lt;code dir=&quot;auto&quot;&gt;disable_no_upgrade_notifier&lt;/code&gt; is recorded below.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The D1 publish path is deleted: &lt;code dir=&quot;auto&quot;&gt;spec-kitty team-projection publish&lt;/code&gt;, the
&lt;code dir=&quot;auto&quot;&gt;.kittify/derived/&lt;/code&gt; team-index / team-snapshot / public-projection /
attestation-manifest artifacts, and the &lt;code dir=&quot;auto&quot;&gt;dossier/emitter_adapter.py&lt;/code&gt;
sync-emitter bridge (Epic E4, planning issue #6).&lt;/strong&gt; Consumers read the
tracked repository at an exact pushed commit instead of a published
gitignored projection, so nothing publishes one any more. The
&lt;code dir=&quot;auto&quot;&gt;team_projection&lt;/code&gt; package survives as its one ported seam,
&lt;code dir=&quot;auto&quot;&gt;TEAM_WP_ALLOWED_FIELDS&lt;/code&gt; (Team Kitty applies the same allowlist on read);
&lt;code dir=&quot;auto&quot;&gt;dossier/events.py&lt;/code&gt; emitters still validate their envelopes but drop them
locally — no transport consumes &lt;code dir=&quot;auto&quot;&gt;MissionDossier*&lt;/code&gt; events since the CLI→SaaS
sync transport’s deletion began. Full removal of the remaining emission
surface lands with the &lt;code dir=&quot;auto&quot;&gt;sync/dossier_pipeline.py&lt;/code&gt; deletion.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_TOKEN&lt;/code&gt; (env-supplied) session no longer picks up a SaaS URL from a repo-local &lt;code dir=&quot;auto&quot;&gt;.kittify/saas-auth.json&lt;/code&gt; — export &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt; (or set &lt;code dir=&quot;auto&quot;&gt;[sync].server_url&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;config.toml&lt;/code&gt;) alongside the token, or the CLI now fails closed with &lt;code dir=&quot;auto&quot;&gt;SaaS URL not configured&lt;/code&gt; (EXPERIMENTAL-spec-kitty#237, EXPERIMENTAL-spec-kitty#264).&lt;/strong&gt; Before, a token from the environment paired with a URL supplied only by the checkout-controlled auth file silently resolved — letting that file redirect a longer-lived, more broadly-scoped service token to a host of the checkout’s choosing. &lt;code dir=&quot;auto&quot;&gt;.kittify/saas-auth.json&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;saas_url&lt;/code&gt; is now honoured only alongside its own &lt;code dir=&quot;auto&quot;&gt;token&lt;/code&gt;, never paired with an env-resolved one; the separate, documented &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; trust surface remains unchanged (EXPERIMENTAL-spec-kitty#289).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Stale PyPI-era vocabulary on the upgrade-check path is renamed, with no compatibility aliases (EXPERIMENTAL-spec-kitty#245).&lt;/strong&gt; The upgrade-check path queries private GitHub Releases, not PyPI, and has for several releases — but it still carried four PyPI-named symbols from before that migration. Renamed: &lt;code dir=&quot;auto&quot;&gt;upgrade_probe.probe_pypi()&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;probe_github_releases()&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;UpgradeProbeResult.latest_pypi_version&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;latest_release_version&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;UpgradeChannel.AHEAD_OF_PYPI&lt;/code&gt; (value &lt;code dir=&quot;auto&quot;&gt;&quot;ahead_of_pypi&quot;&lt;/code&gt;) → &lt;code dir=&quot;auto&quot;&gt;AHEAD_OF_RELEASE&lt;/code&gt; (value &lt;code dir=&quot;auto&quot;&gt;&quot;ahead_of_release&quot;&lt;/code&gt;); and, on the plugin-facing &lt;code dir=&quot;auto&quot;&gt;DistributionProfile&lt;/code&gt; dataclass, &lt;code dir=&quot;auto&quot;&gt;disable_public_pypi_notifier&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;disable_no_upgrade_notifier&lt;/code&gt;. &lt;strong&gt;Migration for forks with a registered &lt;code dir=&quot;auto&quot;&gt;spec_kitty.distribution_profile&lt;/code&gt; entry point:&lt;/strong&gt; rename the keyword argument in your factory from &lt;code dir=&quot;auto&quot;&gt;disable_public_pypi_notifier&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;disable_no_upgrade_notifier&lt;/code&gt;; a factory still passing the old name now raises &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt; inside &lt;code dir=&quot;auto&quot;&gt;resolve_distribution_profile()&lt;/code&gt;, which logs the failure at &lt;code dir=&quot;auto&quot;&gt;ERROR&lt;/code&gt; (previously silent) and falls back to the stock profile rather than your fork’s configuration. &lt;strong&gt;On-disk cache compatibility:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;~/.cache/spec-kitty/upgrade-check.json&lt;/code&gt; written by an older build is still read — the deserializer falls back to the legacy &lt;code dir=&quot;auto&quot;&gt;latest_pypi_version&lt;/code&gt; key when &lt;code dir=&quot;auto&quot;&gt;latest_release_version&lt;/code&gt; is absent — but a cached &lt;code dir=&quot;auto&quot;&gt;&quot;channel&quot;: &quot;ahead_of_pypi&quot;&lt;/code&gt; value no longer matches any &lt;code dir=&quot;auto&quot;&gt;UpgradeChannel&lt;/code&gt; member, so that one entry is treated as a cache miss and re-probed (safe; not a crash).&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 fails (exit code &lt;code dir=&quot;auto&quot;&gt;1&lt;/code&gt;) for
three previously-passing org-pack shapes (mission
&lt;code dir=&quot;auto&quot;&gt;org-pack-authoring-diagnostics-01KZY463&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3387&lt;/code&gt;).&lt;/strong&gt; All three close a
silent-success authoring gap where a pack passed validation cleanly and only
failed — or silently misbehaved — at runtime or on adoption. Concretely: a
merge-time-skipped agent profile (a profile that individually passes schema
validation but fails to field-merge onto a same-ID built-in profile) now
surfaces as a &lt;code dir=&quot;auto&quot;&gt;profile_skipped&lt;/code&gt; error, sourced from
&lt;code dir=&quot;auto&quot;&gt;AgentProfileRepository.skipped_profiles()&lt;/code&gt; rather than requiring a separate
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine --json&lt;/code&gt; invocation. A nested
&lt;code dir=&quot;auto&quot;&gt;assets/&amp;#x3C;pack&gt;/x.asset.yaml&lt;/code&gt; manifest with a schema violation is now scanned
recursively, matching what &lt;code dir=&quot;auto&quot;&gt;AssetRepository&lt;/code&gt; loads at runtime (previously
invisible to validation). 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 produces a
&lt;code dir=&quot;auto&quot;&gt;drg_root_graph_missing&lt;/code&gt; error — the runtime
(&lt;code dir=&quot;auto&quot;&gt;src/charter/_drg_helpers.py:load_validated_graph&lt;/code&gt;) reads only the pack
root, never &lt;code dir=&quot;auto&quot;&gt;drg/&lt;/code&gt; fragments, so this shape previously validated cleanly and
then silently zeroed the pack’s DRG content on adoption (per sibling mission
&lt;code dir=&quot;auto&quot;&gt;org-pack-drg-root-graph-guard-01KZY0QT&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3384&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;validate_pack()&lt;/code&gt; gains a
keyword-only &lt;code dir=&quot;auto&quot;&gt;check_drg_root: bool = True&lt;/code&gt; parameter for the new DRG check;
&lt;code dir=&quot;auto&quot;&gt;pack_assembler.py&lt;/code&gt;’s internal round-trip validation of its own
drg/-fragments-only output passes &lt;code dir=&quot;auto&quot;&gt;check_drg_root=False&lt;/code&gt; unconditionally (a
structural carve-out — the assembler never writes a pack-root graph).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Breaking — &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; (no &lt;code dir=&quot;auto&quot;&gt;--profile&lt;/code&gt;) now always lets a canonical-verb match outrank a domain-keyword match, regardless of &lt;code dir=&quot;auto&quot;&gt;routing_priority&lt;/code&gt;.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;dispatch-dry-run-route-only-01M1HKV2&lt;/code&gt;, WP03; SK-08, SPEC-KITTY-LEDGER.md:2727; #3840; narrowed by operator ruling after the initial WP03 commit — see below) &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;ActionRouter.route()&lt;/code&gt; picked the auto-routed winner by &lt;code dir=&quot;auto&quot;&gt;routing_priority&lt;/code&gt; across &lt;em&gt;every&lt;/em&gt; matched candidate regardless of confidence tier, so a request whose tokens matched only a generic domain keyword for a high-&lt;code dir=&quot;auto&quot;&gt;routing_priority&lt;/code&gt; profile could outrank the request’s own canonical-verb match, opening an Op under a possibly-wrong profile at low confidence — this is SK-08’s reported defect. &lt;strong&gt;After:&lt;/strong&gt; a canonical-verb candidate always wins over a domain-keyword candidate, regardless of &lt;code dir=&quot;auto&quot;&gt;routing_priority&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;routing_priority&lt;/code&gt; still breaks ties &lt;em&gt;within&lt;/em&gt; the canonical-verb tier only, unchanged). &lt;strong&gt;Some previously-succeeding no-&lt;code dir=&quot;auto&quot;&gt;--profile&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch &quot;&amp;#x3C;request&gt;&quot;&lt;/code&gt; calls will now select a different profile than before&lt;/strong&gt; when their tokens matched both a canonical verb and a competing domain keyword; callers wanting a stable profile across a mission’s lifetime should pass an explicit &lt;code dir=&quot;auto&quot;&gt;--profile &amp;#x3C;id&gt;&lt;/code&gt; hint, which this change does not affect (&lt;code dir=&quot;auto&quot;&gt;tk-watch&lt;/code&gt;’s existing &lt;code dir=&quot;auto&quot;&gt;TK_WATCH_PROFILE&lt;/code&gt; pin continues to work unmodified, and becomes unnecessary as an SK-08-specific workaround for the competition case). The router’s already-computed candidate list is exposed on every successful route via &lt;code dir=&quot;auto&quot;&gt;RouterDecision.alternatives&lt;/code&gt; (mission WP02) so a consumer can inspect routing confidence directly, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch --dry-run&lt;/code&gt; (mission WP01) lets a consumer query the routing signal without opening governance history.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Narrowed after initial landing:&lt;/strong&gt; WP03’s first implementation also made the router raise &lt;code dir=&quot;auto&quot;&gt;ROUTER_AMBIGUOUS&lt;/code&gt; (exit 1) on &lt;em&gt;every&lt;/em&gt; zero-canonical-verb-candidate resolution, including a request whose tokens carried no canonical verb at all and matched only a lone or unopposed domain keyword — a &lt;strong&gt;no-competition&lt;/strong&gt; case SK-08 never reported (SK-08 is specifically about a domain keyword &lt;em&gt;outranking&lt;/em&gt; the request’s own verb). That broke a real shipped profile (&lt;code dir=&quot;auto&quot;&gt;diagram-daisy&lt;/code&gt;, routed via its &lt;code dir=&quot;auto&quot;&gt;chart&lt;/code&gt; domain-keyword signal) and was reverted by operator ruling: when zero canonical-verb candidates exist, &lt;code dir=&quot;auto&quot;&gt;route()&lt;/code&gt; now falls back to its pre-existing (pre-WP03) selection over the domain-keyword candidates — a unique keyword-tier match still auto-selects, and &lt;code dir=&quot;auto&quot;&gt;routing_priority&lt;/code&gt; still breaks ties among multiple keyword-tier-only candidates; &lt;code dir=&quot;auto&quot;&gt;ROUTER_AMBIGUOUS&lt;/code&gt; is reserved for a genuine tie at the top priority, exactly as before this fix. No previously-succeeding no-&lt;code dir=&quot;auto&quot;&gt;--profile&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;dispatch&lt;/code&gt; call newly exits 1 as a result of this fix — the only user-visible effect is the cross-tier rerank described above.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Breaking — the redundant &lt;code dir=&quot;auto&quot;&gt;context-sources.*&lt;/code&gt; agent-profile surface is removed from the schema; profiles author references solely on the top-level &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt; fields&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-drg-silent-drop-boundary-01M0PE7E&lt;/code&gt;, WP02; #3629 p1). The &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; block (&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;) duplicated the canonical, DRG-provisioned &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; surface and was mostly inert; only &lt;code dir=&quot;auto&quot;&gt;context-sources.directives&lt;/code&gt; minted a DRG edge, and every shipped profile already carried the same ids on &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt;. &lt;strong&gt;Before:&lt;/strong&gt; two parallel reference surfaces, one of which was silently dropped on delivery. &lt;strong&gt;After:&lt;/strong&gt; one canonical surface — the model now declares &lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt; without a &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; field, so a profile still authoring the block &lt;strong&gt;fails to load loudly&lt;/strong&gt; rather than dropping it in silence. The extractor now projects &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; DRG edges from &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;directive-references&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tactic-references&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;, and &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;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;). A consumer project that authored custom profiles with &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; is migrated automatically by the &lt;code dir=&quot;auto&quot;&gt;3_3_1_context_sources_consolidation&lt;/code&gt; upgrade migration, which &lt;strong&gt;set-merges&lt;/strong&gt; every reference id onto the matching &lt;code dir=&quot;auto&quot;&gt;*-references&lt;/code&gt; field (deduped, never appended) and drops the edge-less &lt;code dir=&quot;auto&quot;&gt;doctrine-layers&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;additional&lt;/code&gt; names with a logged note. Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; (the migration is idempotent and safe to re-run); free-text &lt;code dir=&quot;auto&quot;&gt;additional&lt;/code&gt; bindings with no artifact-id shape are reported, not silently discarded.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&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, so an agent operating from a task-owned Git worktree can run a mission end-to-end without a command targeting the wrong checkout.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;explicit-worktree-commands&lt;/code&gt;; #3843; extends #3346 / #3787 and ADR 2026-08-12-1) &lt;strong&gt;Before:&lt;/strong&gt; only &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; accepted &lt;code dir=&quot;auto&quot;&gt;--owned-checkout&lt;/code&gt;; the rest of the lifecycle — &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; — could only rediscover the repository-root checkout, so a valid single-branch worktree workflow either refused or silently wrote to the wrong mission surface. &lt;strong&gt;After:&lt;/strong&gt; all six commands accept &lt;code dir=&quot;auto&quot;&gt;--owned-checkout PATH&lt;/code&gt; and route mission reads, writes, status events, and commits through one validated owned root (the new &lt;code dir=&quot;auto&quot;&gt;core/owned_mission.py&lt;/code&gt; preflight), which fails closed on a foreign or nested path, a detached or mismatched branch, a pre-staged index, or an unsupported topology. Owned mode is deliberately &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 opted in is refused with a structured &lt;code dir=&quot;auto&quot;&gt;OWNED_TOPOLOGY_UNSUPPORTED&lt;/code&gt; rather than mis-routed. Flagless (non-opted-in) behavior is byte-for-byte unchanged. Design record: ADR &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-09-03-1-explicit-owned-checkout-single-branch-lifecycle.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A new architectural gate catches stale references to relocated &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; modules at construction time, so future package moves stop shipping dead import paths.&lt;/strong&gt; (enabler mission &lt;code dir=&quot;auto&quot;&gt;tidy-charter-cutover-surface&lt;/code&gt;; closes #3818, #3808) After a &lt;code dir=&quot;auto&quot;&gt;src/charter/**&lt;/code&gt; relocation, stale &lt;em&gt;string&lt;/em&gt; references to a module’s old path — arch-gate path-literal allowlist tuples, &lt;code dir=&quot;auto&quot;&gt;patch(&quot;charter.&amp;#x3C;old&gt;…&quot;)&lt;/code&gt; mock targets, and markdown relative links — used to survive the import rewrite and only surface as a red CI shard afterward. &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_stale_charter_path_literals.py&lt;/code&gt; now fails on any such literal or link in &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;, or live &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; (AST-driven, word-boundary-safe, historical archives excluded), giving the remaining &lt;code dir=&quot;auto&quot;&gt;retire-doctrine-term&lt;/code&gt; waves a guardrail. Riding along, the three always-on charter consistency-check gates now share &lt;strong&gt;one&lt;/strong&gt; DRG load and one fail-closed wrapper (was three independent loads) — behaviour-preserving, verdicts byte-identical (#3808).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; is now the canonical governing term in the Charter + glossary authority; the legacy &lt;code dir=&quot;auto&quot;&gt;governance.doctrine&lt;/code&gt; selection key still loads with a one-time deprecation warning.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;charter-authority-flip-01M14RB3&lt;/code&gt;, wave M1 of &lt;code dir=&quot;auto&quot;&gt;retire-doctrine-term-01M0JMK9&lt;/code&gt;; #3664, #3732) This is the first, authority-only wave of the doctrine→charter terminology retirement — the &lt;code dir=&quot;auto&quot;&gt;src/doctrine&lt;/code&gt; package, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; CLI, and the &lt;code dir=&quot;auto&quot;&gt;drg&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;doctrine artifact&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;doctrine pack&lt;/code&gt; domain vocabulary are deliberately unchanged and land in later waves. &lt;strong&gt;Before:&lt;/strong&gt; the glossary authorities carried both a &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; and a &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; term (with &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; even defined as synthesizing “…and doctrine”), and the charter selection key was &lt;code dir=&quot;auto&quot;&gt;governance.doctrine&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the three glossary authorities (seed YAML, built-in pack, &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; as the single governing term; a new &lt;code dir=&quot;auto&quot;&gt;### charter&lt;/code&gt; Terminology-Canon entry disambiguates its overloaded senses (Charter Bundle / Charter Pack / the &lt;code dir=&quot;auto&quot;&gt;src/charter/&lt;/code&gt; package / the &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter&lt;/code&gt; CLI group / Active-Inactive Charter artefact / &lt;strong&gt;Pack Default Charter&lt;/strong&gt;) with “do-NOT-use” guards. The selection key becomes &lt;code dir=&quot;auto&quot;&gt;governance.charter&lt;/code&gt;; a dict-level compat reader maps the legacy &lt;code dir=&quot;auto&quot;&gt;governance.doctrine&lt;/code&gt; key forward and warns once (&lt;code dir=&quot;auto&quot;&gt;LegacyGovernanceKeyWarning&lt;/code&gt;, public &lt;code dir=&quot;auto&quot;&gt;apply_legacy_governance_selection_key_compat&lt;/code&gt;), so existing projects keep loading. &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; migrates &lt;code dir=&quot;auto&quot;&gt;interview/answers.yaml&lt;/code&gt; via the new &lt;code dir=&quot;auto&quot;&gt;scripts/migrate_charter_interview_answers.py&lt;/code&gt; (preserves every answer, unknown key, and the historical &lt;code dir=&quot;auto&quot;&gt;doctrine-catfooding-2196&lt;/code&gt; slug; restores the pre-image on failure). A shrink-only architectural ratchet (&lt;code dir=&quot;auto&quot;&gt;test_transition_guard_shrink_only&lt;/code&gt;) and an archive-immutability gate (&lt;code dir=&quot;auto&quot;&gt;test_archive_root_byte_identical&lt;/code&gt;) prevent the governing term from being re-introduced.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Status moments now carry live presence/focus frames: every broadcast at the status fan-out seam also publishes one &lt;code dir=&quot;auto&quot;&gt;presence.publish&lt;/code&gt; frame (and, for a WP transition, one &lt;code dir=&quot;auto&quot;&gt;focus.start&lt;/code&gt; naming &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;mission&gt;.&amp;#x3C;WP&gt;&lt;/code&gt;), so Team Kitty’s live panel shows who is on which repo/WP (EXPERIMENTAL-spec-kitty#186).&lt;/strong&gt; The moment stream alone could never power the panel — zeitgeist treats &lt;code dir=&quot;auto&quot;&gt;event.publish&lt;/code&gt; as activity &lt;em&gt;about&lt;/em&gt; a session that extends nothing’s TTL — so GOAL.md’s MVP test (“presence shows the member on that repo/WP”) had nothing to render. Presence rides the stored &lt;code dir=&quot;auto&quot;&gt;presence&lt;/code&gt;-kind credential (the kind grants both ops); focus mints its own &lt;code dir=&quot;auto&quot;&gt;focus&lt;/code&gt;-kind lease via the new &lt;code dir=&quot;auto&quot;&gt;resolve_focus_capability&lt;/code&gt;, stored merged into the same credential-store entry (&lt;code dir=&quot;auto&quot;&gt;store_focus_capability&lt;/code&gt;) so a re-mint of either lease never drops the other. Presence binds repo/branch to git truth via &lt;code dir=&quot;auto&quot;&gt;ClientConfig.for_repository&lt;/code&gt;; a ref that cannot fit the relay’s 64-char ident grammar or a checkout whose identity cannot be verified drops only the liveness frame, never the moment, and a focus denial never writes a negative answer over the shared store entry.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;New &lt;code dir=&quot;auto&quot;&gt;spec-kitty moments off|on|status&lt;/code&gt; command gives agents an off switch and filters for Zeitgeist status moments (EXPERIMENTAL-spec-kitty#190, “Moments in agent context”).&lt;/strong&gt; A per-developer setting — global &lt;code dir=&quot;auto&quot;&gt;~/.kittify/config.toml&lt;/code&gt;, overridable per repo in &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;repo&gt;/.kittify/config.toml&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;[moments] agents = off | mine | team&lt;/code&gt;, defaulting to &lt;strong&gt;mine&lt;/strong&gt; (only moments about missions this checkout knows) and never “everything”: &lt;code dir=&quot;auto&quot;&gt;team&lt;/code&gt; requires an explicit opt-in, and an unreadable or unknown value fails closed to &lt;code dir=&quot;auto&quot;&gt;off&lt;/code&gt;. Filters ride the same table (&lt;code dir=&quot;auto&quot;&gt;repos&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;missions&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;teammates&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;kinds&lt;/code&gt;) and are applied client-side in the stream client (&lt;code dir=&quot;auto&quot;&gt;filtered_stream.FilteredStream&lt;/code&gt;’s new optional &lt;code dir=&quot;auto&quot;&gt;frame_filter&lt;/code&gt;) — the relay stays a per-team firehose. A rate cap (&lt;code dir=&quot;auto&quot;&gt;rate_per_minute&lt;/code&gt;, default 10) bounds what one MCP session surfaces per rolling minute; everything beyond it is summarised as “+k more”, never silently dropped. With &lt;code dir=&quot;auto&quot;&gt;agents = off&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty zeitgeist mcp-serve&lt;/code&gt; refuses to start: one line on stderr (stdout stays protocol-clean), exit 0. New &lt;code dir=&quot;auto&quot;&gt;specify_cli/zeitgeist_client/moments.py&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;New &lt;code dir=&quot;auto&quot;&gt;spec-kitty team-projection publish&lt;/code&gt; command produces read-only, byte-deterministic team-index and per-mission snapshot artifacts (plus an explicit-opt-in public variant and an attestation manifest) with exact-commit provenance (D1-T1).&lt;/strong&gt; Every artifact is a closed, allowlist-filtered projection of the existing status event log — orchestration-only runtime state (&lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt;, unbounded operator &lt;code dir=&quot;auto&quot;&gt;notes&lt;/code&gt;) never reaches a team or public consumer — and public output stays absent unless a project explicitly sets &lt;code dir=&quot;auto&quot;&gt;public_projection.enabled: true&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;. Refuses (non-zero exit, zero files written) on a dirty working tree, since the attestation manifest’s whole purpose is a truthful commit-to-content binding for downstream consumers. New &lt;code dir=&quot;auto&quot;&gt;specify_cli/team_projection/&lt;/code&gt; package; no new runtime dependency.&lt;/p&gt;
&lt;blockquote&gt;
&lt;p&gt;&lt;strong&gt;⚠️ Superseded within this same release.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;spec-kitty team-projection publish&lt;/code&gt; D1 publish path added here was &lt;strong&gt;deleted later in 3.2.6&lt;/strong&gt; — see the “The D1 publish path is deleted” entry under 💥 Breaking / 🗑️ Removed above. Consumers read the tracked repository at an exact pushed commit instead of a published projection; the &lt;code dir=&quot;auto&quot;&gt;team_projection&lt;/code&gt; package survives only as its &lt;code dir=&quot;auto&quot;&gt;TEAM_WP_ALLOWED_FIELDS&lt;/code&gt; seam. This Added entry is retained for historical fidelity but the command it describes does not exist in the shipped 3.2.6.&lt;/p&gt;
&lt;/blockquote&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;’s auto-commit no longer names the &lt;em&gt;old&lt;/em&gt; path of a staged rename.&lt;/strong&gt; (#2491 follow-up; salvaged from #2492) &lt;code dir=&quot;auto&quot;&gt;git_status_paths&lt;/code&gt; read &lt;code dir=&quot;auto&quot;&gt;git status --porcelain -z&lt;/code&gt; rename entries with the fields backwards — real git emits &lt;code dir=&quot;auto&quot;&gt;R  &amp;#x3C;new&gt;\0&amp;#x3C;old&gt;\0&lt;/code&gt; — so a staged rename put the pre-rename path into the commit-set. The unit-test fixture encoded the same wrong order, so the test passed against the bug. Fixed with a structured porcelain record that keeps the destination as the current path while retaining the source identity: clean renames stage both the destination and source deletion, and a source already dirty at baseline taints the destination so operator work is never swept. Covered through the real &lt;code dir=&quot;auto&quot;&gt;commit_touched_checkout&lt;/code&gt; seam, not only the parser.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now auto-commits root-level files it wrote during the run — &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.claudeignore&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;GEMINI.md&lt;/code&gt; — exactly as it already did for files in subdirectories; pre-existing edits to any file, root or not, are still never swept into the commit.&lt;/strong&gt; (#2491 follow-up; #2492 superseded by #3679; #2392 invariant) &lt;strong&gt;Before:&lt;/strong&gt; the commit-set filter skipped every root-level file except &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;, on the theory that root files are operator-owned. But upgrade’s own migrations write at the root — the merge-driver/diff-attribute migrations (&lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt;, seven of them, several in this rc cycle, and they run in worktrees too), &lt;code dir=&quot;auto&quot;&gt;m_3_2_8_provision_kitty_env&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;.claudeignore&lt;/code&gt;), and surface repair (&lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;GEMINI.md&lt;/code&gt;) — so a fully successful &lt;code dir=&quot;auto&quot;&gt;upgrade --yes&lt;/code&gt; routinely ended with &lt;code dir=&quot;auto&quot;&gt;M .gitattributes  M .claudeignore  ?? AGENTS.md  ?? GEMINI.md&lt;/code&gt;, and a modified &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; in every live worktree tripped the &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; dirty-worktree guard (the #2385 class again). The hand-kept exception list drifted four times in six months. &lt;strong&gt;After:&lt;/strong&gt; ownership is decided by the pre-run baseline alone — a file clean before the run and dirty after was written by the run and lands in the one auto-commit; a file already dirty at baseline stays out, whatever its depth. The path-depth rule is gone. Porcelain now requests per-file untracked paths, so a file the run creates beneath a pre-existing operator-owned untracked directory remains visible to the baseline diff instead of being collapsed into the same directory entry. Rename/copy identity and run-local filesystem mutation provenance carry source ownership across moves and transformed relocations; if that bounded provenance history is exhausted, auto-commit fails closed for manual review. Exact NUL-delimited path identity is preserved, including valid leading/trailing spaces. Two guards remain: paths outside the checkout (&lt;code dir=&quot;auto&quot;&gt;../&lt;/code&gt;) are never committed, and when the checkout &lt;strong&gt;is&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;$HOME&lt;/code&gt; (the #3652 hazard) neither &lt;code dir=&quot;auto&quot;&gt;~/.kittify&lt;/code&gt; nor any root-level file is committed — those are the operator’s dotfiles. A real-git test drives &lt;code dir=&quot;auto&quot;&gt;commit_touched_checkout&lt;/code&gt; end-to-end on a main checkout and a worktree and asserts the tree ends clean except for the pre-existing operator edit. Behaviour note for operators: if you edit a root file &lt;em&gt;while&lt;/em&gt; an upgrade is running (a seconds-long window), that edit can now land in the upgrade commit, as an edit to a subdirectory file always could; &lt;code dir=&quot;auto&quot;&gt;git reset --soft HEAD~1&lt;/code&gt; undoes it. Decided via an adversarial-squad review of the allowlist alternative (see #3686).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty zeitgeist operability&lt;/code&gt; gives the bundled Zeitgeist client a
payload-free self-report of its own liveness/connection/subscription/
outbox status, plus local failure drills (&lt;code dir=&quot;auto&quot;&gt;O1-C&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;operability report&lt;/code&gt;
is one snapshot of seven signals — offer/drop/lease/revoke/mcp/repair,
each carrying its own denominator where one applies (&lt;code dir=&quot;auto&quot;&gt;OfferSignal. budget_s&lt;/code&gt; is always the hard 750ms bound; &lt;code dir=&quot;auto&quot;&gt;LeaseSignal.ttl_s&lt;/code&gt; is always
the 90s current-focus ceiling, present even when no focus is active) —
built from state the already-landed &lt;code dir=&quot;auto&quot;&gt;transport&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;credentials&lt;/code&gt;/
&lt;code dir=&quot;auto&quot;&gt;outbox_approval&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mcp_stdio&lt;/code&gt; modules already own; there is no second
data store. A repo with no stored checkout gets an honestly stale/
inactive report rather than a fabricated live one. &lt;code dir=&quot;auto&quot;&gt;drill-timeout&lt;/code&gt;
(relay unreachable), &lt;code dir=&quot;auto&quot;&gt;drill-rotation&lt;/code&gt; (auth expiry — reads only the
stored &lt;code dir=&quot;auto&quot;&gt;token_issued_at&lt;/code&gt; timestamp, never the token), and
&lt;code dir=&quot;auto&quot;&gt;drill-rollback&lt;/code&gt; (proves &lt;code dir=&quot;auto&quot;&gt;outbox_approval.revoke()&lt;/code&gt; fails closed on a
never-approved item, without ever opening &lt;code dir=&quot;auto&quot;&gt;/dev/tty&lt;/code&gt;) are network-free
and deterministic. No sensitive field ever appears in a report — proven
by running it through &lt;code dir=&quot;auto&quot;&gt;sanitizer.py&lt;/code&gt;’s own forbidden-key gate, the same
one the rest of the client already trusts.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty zeitgeist outbox&lt;/code&gt; gives a human a bundled, outside-model
approval surface over locally queued Zeitgeist prose (&lt;code dir=&quot;auto&quot;&gt;Z8-C&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;list&lt;/code&gt;/
&lt;code dir=&quot;auto&quot;&gt;show&lt;/code&gt; inspect pending items (exact content is disclosed only via &lt;code dir=&quot;auto&quot;&gt;show&lt;/code&gt;
or the decision prompt itself — never in &lt;code dir=&quot;auto&quot;&gt;list&lt;/code&gt;’s redacted preview);
&lt;code dir=&quot;auto&quot;&gt;approve&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;reject&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;revoke&lt;/code&gt; require the human to type back a per-item
challenge at the real controlling terminal (&lt;code dir=&quot;auto&quot;&gt;outbox_approval.py&lt;/code&gt;’s
&lt;code dir=&quot;auto&quot;&gt;_capture_human_gesture&lt;/code&gt;), and raise &lt;code dir=&quot;auto&quot;&gt;HumanGestureRequired&lt;/code&gt; whenever none
is available — there is no &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--non-interactive&lt;/code&gt; flag on
any of the three, no environment-variable escape hatch, and the hidden
stdio MCP adapter (&lt;code dir=&quot;auto&quot;&gt;mcp_stdio.py&lt;/code&gt;) is untouched: a model talking over MCP
has no tool that reaches this surface. Pending items are content-addressed
(SHA-256 over repo/audience/content/context) and TTL-bounded
(default-deny: an expired item can never be approved); receipts are
content-addressed and idempotent on retry.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty zeitgeist status&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;watch&lt;/code&gt; and a hidden stdio MCP adapter give a
terminal or an MCP client bounded, read-only access to one team’s live
Zeitgeist presence/focus stream (&lt;code dir=&quot;auto&quot;&gt;Z7-C&lt;/code&gt;).&lt;/strong&gt; Both surfaces call the same
shared &lt;code dir=&quot;auto&quot;&gt;zeitgeist_client.subscription&lt;/code&gt; functions over the already-landed
&lt;code dir=&quot;auto&quot;&gt;filtered_stream.FilteredStream&lt;/code&gt; client — one team context per call (the
existing &lt;code dir=&quot;auto&quot;&gt;credentials.py&lt;/code&gt; checkout, never a &lt;code dir=&quot;auto&quot;&gt;--relay-url&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--token&lt;/code&gt; flag),
a &amp;#x3C;=90s honest reported-live timeout ceiling, a bounded frame count on
&lt;code dir=&quot;auto&quot;&gt;watch&lt;/code&gt;, and no payload ever written to disk. The MCP adapter
(&lt;code dir=&quot;auto&quot;&gt;zeitgeist_client/mcp_stdio.py&lt;/code&gt;) uses the official &lt;code dir=&quot;auto&quot;&gt;mcp&lt;/code&gt; SDK
(&lt;code dir=&quot;auto&quot;&gt;mcp&gt;=1.27.1,&amp;#x3C;2.0.0&lt;/code&gt;) and exposes the matching &lt;code dir=&quot;auto&quot;&gt;zeitgeist_status&lt;/code&gt;/
&lt;code dir=&quot;auto&quot;&gt;zeitgeist_watch&lt;/code&gt; tools.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The charter package is now a real two-module split — &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; (offer catalogue) and &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; (mutation/activation layer) — with the &lt;code dir=&quot;auto&quot;&gt;offering ↛ activation&lt;/code&gt; boundary enforced as a package wall.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;charter-activation-split-01M16ZSE&lt;/code&gt;, wave M2b of &lt;code dir=&quot;auto&quot;&gt;retire-doctrine-term-01M0JMK9&lt;/code&gt;; #3664) Completes the split M2 deferred: the activation-side charter modules (&lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;compiler&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolver&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;interview&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pack_context&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;context&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;cascade&lt;/code&gt;, the synthesizer, …) relocate from top-level &lt;code dir=&quot;auto&quot;&gt;charter.*&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;src/charter/activation/&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;charter/__init__.py&lt;/code&gt; becomes lazy (PEP-562) so importing &lt;code dir=&quot;auto&quot;&gt;charter.offering.*&lt;/code&gt; no longer transitively drags the activation layer. &lt;strong&gt;Before:&lt;/strong&gt; the offer/activate boundary was enforced against an interim explicit module list because &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; did not yet exist as a package. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter.activation&lt;/code&gt; is a real package and the C-004 architectural gate collapses to forbid &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;charter.activation.*&lt;/code&gt; directly. The 13 offering-facade re-export surfaces and the layer-neutral primitives (&lt;code dir=&quot;auto&quot;&gt;parser&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;bundle&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolution&lt;/code&gt;) intentionally stay at top-level &lt;code dir=&quot;auto&quot;&gt;charter.*&lt;/code&gt;; the &lt;code dir=&quot;auto&quot;&gt;charter.drg&lt;/code&gt; facade keeps its offering-type re-exports while the org-activation graph logic moves to &lt;code dir=&quot;auto&quot;&gt;charter.activation.drg_activation&lt;/code&gt;. Internal reorganization: the retired &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; compatibility shims from M1/M2 are unchanged, so no operator-facing surface changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The internal &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; code package is retired and relocated to &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt;; every operator-facing &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; surface keeps working with a one-time deprecation warning.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;charter-code-topology-01M152G1&lt;/code&gt;, wave M2 of &lt;code dir=&quot;auto&quot;&gt;retire-doctrine-term-01M0JMK9&lt;/code&gt;; #3664) M2 moves the 265-file &lt;code dir=&quot;auto&quot;&gt;src/doctrine/**&lt;/code&gt; catalogue to &lt;code dir=&quot;auto&quot;&gt;src/charter/offering/**&lt;/code&gt; — the pure offer-side catalogue under the charter package — and closes every importer. It is the code-topology continuation of the M1 authority flip. &lt;strong&gt;Before:&lt;/strong&gt; the offer catalogue was a separate top-level &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; package (&lt;code dir=&quot;auto&quot;&gt;import doctrine&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine …&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine.org.packs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine:&amp;#x3C;kind&gt;:&amp;#x3C;id&gt;&lt;/code&gt; URNs, &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt;, a tracker &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; ownership mode). &lt;strong&gt;After:&lt;/strong&gt; the canonical home is &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt;, and six compatibility shims (each read-both / canonical-wins / warn-once) keep the retired surfaces functional through the deprecation window: &lt;code dir=&quot;auto&quot;&gt;import doctrine&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;from doctrine import X&lt;/code&gt; (a module shim, submodule imports must move to &lt;code dir=&quot;auto&quot;&gt;charter.offering.X&lt;/code&gt;); the &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; CLI group (deprecated alias of &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter&lt;/code&gt;); the &lt;code dir=&quot;auto&quot;&gt;governance&lt;/code&gt;/tracker &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; mode → &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ownership&lt;/code&gt;&lt;/strong&gt;; &lt;code dir=&quot;auto&quot;&gt;doctrine.org.packs&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;charter_packs.org.packs&lt;/code&gt;; the &lt;code dir=&quot;auto&quot;&gt;doctrine:&lt;/code&gt; synthesizer URN prefix → &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; (durable event logs keep parsing both); and a &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;.kittify/charter-packs/&lt;/code&gt; dual-root reader. A new architectural gate enforces that &lt;code dir=&quot;auto&quot;&gt;charter.offering&lt;/code&gt; never imports the charter activation/mutation layer (C-004). &lt;strong&gt;Deferred (mission M2b):&lt;/strong&gt; the physical &lt;code dir=&quot;auto&quot;&gt;charter.offering ↔ charter.activation&lt;/code&gt; two-module split — the activation-side charter modules stay at their current top-level paths for now, and the C-004 gate is enforced against them until M2b relocates them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; now honors a project-declared source layout, so repos that do not use &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; (Django &lt;code dir=&quot;auto&quot;&gt;apps/&lt;/code&gt;, Go &lt;code dir=&quot;auto&quot;&gt;internal/&lt;/code&gt;) stop failing the accept gate — and stop being pushed to &lt;code dir=&quot;auto&quot;&gt;mkdir&lt;/code&gt; empty directories just to fake a green.&lt;/strong&gt; (#3016; folds #3785, #2330 Item 1) A project declares its real layout once in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;project.path_conventions&lt;/code&gt; (for example &lt;code dir=&quot;auto&quot;&gt;workspace: apps/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tests: tests/&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; remaps the directories it checks to match. &lt;strong&gt;Before:&lt;/strong&gt; the software-dev path convention hardcoded &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;, so &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; failed every mission in a non-&lt;code dir=&quot;auto&quot;&gt;src&lt;/code&gt; repo with &lt;em&gt;“These directories are required by the active mission. Create them before continuing.”&lt;/em&gt; — steering operators into fabricating empty directories or reaching for a blanket &lt;code dir=&quot;auto&quot;&gt;--lenient&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the project override takes precedence over the mission-type doctrine default (project override → doctrine default → unchanged blocking + &lt;code dir=&quot;auto&quot;&gt;--lenient&lt;/code&gt;), applies across all four mission types through one shared validation seam, and is remap-only — it never adds a new required path. The blocking-by-default policy from #3783 is deliberately unchanged: an override pointing at a directory that is still absent under strict mode still blocks. &lt;code dir=&quot;auto&quot;&gt;deliverables&lt;/code&gt; is excluded from the override vocabulary (its default value is a mission artifact token that routes &lt;code dir=&quot;auto&quot;&gt;feature_dir&lt;/code&gt;↔&lt;code dir=&quot;auto&quot;&gt;project_root&lt;/code&gt;), a malformed &lt;code dir=&quot;auto&quot;&gt;path_conventions&lt;/code&gt; section fails closed with a message naming the offending key, and a missing or corrupt &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; stays lenient. Layout auto-detection (&lt;code dir=&quot;auto&quot;&gt;manage.py&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;go.mod&lt;/code&gt; signals) is the deliberate next step (#2744). Design record: ADR &lt;code dir=&quot;auto&quot;&gt;docs/adr/3.x/2026-08-28-1-project-path-convention-override-precedes-doctrine.md&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;charter&lt;/code&gt; is now the canonical governing term in the Charter + glossary authority; the legacy &lt;code dir=&quot;auto&quot;&gt;governance.doctrine&lt;/code&gt; selection key still loads with a one-time deprecation warning.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;charter-authority-flip-01M14RB3&lt;/code&gt;, wave M1 of &lt;code dir=&quot;auto&quot;&gt;retire-doctrine-term-01M0JMK9&lt;/code&gt;; #3664, #3732) This is the first, authority-only wave of the doctrine→charter terminology retirement — the &lt;code dir=&quot;auto&quot;&gt;src/doctrine&lt;/code&gt; package, &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; CLI, and the &lt;code dir=&quot;auto&quot;&gt;drg&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;doctrine artifact&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;doctrine pack&lt;/code&gt; domain vocabulary are deliberately unchanged and land in later waves. &lt;strong&gt;Before:&lt;/strong&gt; the glossary authorities carried both a &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; and a &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; term (with &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; even defined as synthesizing “…and doctrine”), and the charter selection key was &lt;code dir=&quot;auto&quot;&gt;governance.doctrine&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; the three glossary authorities (seed YAML, built-in pack, &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; as the single governing term; a new &lt;code dir=&quot;auto&quot;&gt;### charter&lt;/code&gt; Terminology-Canon entry disambiguates its overloaded senses (Charter Bundle / Charter Pack / the &lt;code dir=&quot;auto&quot;&gt;src/charter/&lt;/code&gt; package / the &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter&lt;/code&gt; CLI group / Active-Inactive Charter artefact / &lt;strong&gt;Pack Default Charter&lt;/strong&gt;) with “do-NOT-use” guards. The selection key becomes &lt;code dir=&quot;auto&quot;&gt;governance.charter&lt;/code&gt;; a dict-level compat reader maps the legacy &lt;code dir=&quot;auto&quot;&gt;governance.doctrine&lt;/code&gt; key forward and warns once (&lt;code dir=&quot;auto&quot;&gt;LegacyGovernanceKeyWarning&lt;/code&gt;, public &lt;code dir=&quot;auto&quot;&gt;apply_legacy_governance_selection_key_compat&lt;/code&gt;), so existing projects keep loading. &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; migrates &lt;code dir=&quot;auto&quot;&gt;interview/answers.yaml&lt;/code&gt; via the new &lt;code dir=&quot;auto&quot;&gt;scripts/migrate_charter_interview_answers.py&lt;/code&gt; (preserves every answer, unknown key, and the historical &lt;code dir=&quot;auto&quot;&gt;doctrine-catfooding-2196&lt;/code&gt; slug; restores the pre-image on failure). A shrink-only architectural ratchet (&lt;code dir=&quot;auto&quot;&gt;test_transition_guard_shrink_only&lt;/code&gt;) and an archive-immutability gate (&lt;code dir=&quot;auto&quot;&gt;test_archive_root_byte_identical&lt;/code&gt;) prevent the governing term from being re-introduced.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --json&lt;/code&gt; now exposes a top-level &lt;code dir=&quot;auto&quot;&gt;directives_source&lt;/code&gt; provenance field, and directive resolution emits fail-loud diagnostics.&lt;/strong&gt; (#3728; mission &lt;code dir=&quot;auto&quot;&gt;directives-additive-resolution&lt;/code&gt;) &lt;code dir=&quot;auto&quot;&gt;charter context --action &amp;#x3C;action&gt; --json&lt;/code&gt; reports where the resolved directive set came from — for example &lt;code dir=&quot;auto&quot;&gt;catalog_fallback&lt;/code&gt; for a bare project, or &lt;code dir=&quot;auto&quot;&gt;catalog_fallback+project_local&lt;/code&gt; when a project-local &lt;code dir=&quot;auto&quot;&gt;directives:&lt;/code&gt; entry is merged onto the catalog default — carried by a &lt;code dir=&quot;auto&quot;&gt;CONTEXT_SCHEMA_VERSION&lt;/code&gt; bump. The human-readable &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; output now prints a diagnostic whenever the directive catalog-default fallback is used or project-local directives are merged, so the resolution branch is never silent.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Work-package cards in the dashboard kanban board now show a small colored avatar for the currently assigned agent profile.&lt;/strong&gt; (#647) &lt;strong&gt;Before:&lt;/strong&gt; the card only listed the profile/role/agent as text badges, so scanning a busy board for “who’s on what” meant reading every badge row. &lt;strong&gt;After:&lt;/strong&gt; each card renders a deterministic colored-circle avatar (initials derived from a hash of the identity string) next to its WP ID, falling back through &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;assignee&lt;/code&gt; and rendering nothing for a WP with none of those set (legacy shape, or the scanner’s encoding-error path) rather than a broken/empty circle. No image upload involved — the color and initials are generated client-side, so the same profile always gets the same avatar. Historical multi-participant avatars (Phase 2 of the issue) are out of scope here; they need explicit backend provenance support that doesn’t exist yet.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The operator-signal / fail-loud discipline is now a citable, named directive in the internal dogfooding pack.&lt;/strong&gt; (#3410, #3549) A new &lt;code dir=&quot;auto&quot;&gt;operator-signal-contract&lt;/code&gt; directive lives in &lt;code dir=&quot;auto&quot;&gt;packs/internal/directives/&lt;/code&gt; (registered in the internal DRG fragment; provenance &lt;code dir=&quot;auto&quot;&gt;org&lt;/code&gt;, layer 1) and codifies &lt;strong&gt;“a path that decides must also signal”&lt;/strong&gt;: whenever a code path reaches a correct machine-readable outcome — a correct &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt;, a byte-stable file, a truthy return, a completed state transition — it MUST also emit the human-readable half through an &lt;strong&gt;existing&lt;/strong&gt; operator-visible surface, never a new sink that can itself be swallowed. It adopts the existing #3410 (charter/doctrine silent-drop) and #3549 (event-log integrity) vocabulary rather than minting a new term, and it explicitly does &lt;strong&gt;not&lt;/strong&gt; ship to consumers (it stays out of &lt;code dir=&quot;auto&quot;&gt;packs/built-in&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine --json&lt;/code&gt; reports the internal pack healthy with the directive resolved through the DRG (&lt;code dir=&quot;auto&quot;&gt;artifact_counts.directives: 1&lt;/code&gt;, no skipped/inert artifact).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; / topology-drop class from #3571 now has a structural home: one shared allocation seam every route flows through, plus a CI guard that fails when a new route tries to bypass it — so the “override reaches only one of two routes” bug can’t silently recur.&lt;/strong&gt; (mission rc3-lane-allocation-single-seam; delivers #3460 / #3462 / #3536; #3571 recurrence-prevention) M1 (#3616) shipped the #3571 point-fix; M8 generalizes it. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; honoring lived in two independent helpers (a positive parent-chooser and a separate fail-loud guard), the read-side degrade was hand-rolled at each site, the topology-availability predicate had look-alike surrogate checks, and a &lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; mission refused a protected-branch bookkeeping commit with an &lt;strong&gt;un-followable&lt;/strong&gt; remedy (“target the coordination branch” — which that topology never mints). &lt;strong&gt;After:&lt;/strong&gt; (1) &lt;strong&gt;one seam&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;resolve_lane_base_or_refuse&lt;/code&gt; (honor-or-raise, never a silent degrade) is the sole computer of a lane’s parent ref across all four routes — fresh-coord, fresh-legacy, reuse, crash-recovery — with byte-identical parentage when no &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; is supplied (NFR-preserving); (2) a &lt;strong&gt;structural anti-bypass guard&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_lane_allocation_single_seam.py&lt;/code&gt;) fails, naming the offending &lt;code dir=&quot;auto&quot;&gt;file:line&lt;/code&gt;, when any new allocation route computes a parent ref outside the seam or a new read-degrade site skips the companion — proven non-vacuous by a synthetic-bypass fixture; (3) the topology-availability authority (&lt;code dir=&quot;auto&quot;&gt;_transaction_topology_available&lt;/code&gt;) is &lt;strong&gt;pinned by an anti-divergence guard&lt;/strong&gt; so no future site can gate on a &lt;code dir=&quot;auto&quot;&gt;coordination_branch is None&lt;/code&gt; surrogate (#3460 — the census found zero live surrogates to remove; the win is the guard, not a code change, and the #2939 off-axis-annotation exception is explicitly preserved); (4) a &lt;strong&gt;read-side degrade companion&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;resolve_read_dir_or_degrade&lt;/code&gt; mirrors the write-side helper and consolidates the genuine degrade-to-dir read sites (#3462), while the #1848 data-loss re-raise at &lt;code dir=&quot;auto&quot;&gt;status/aggregate.py&lt;/code&gt; is deliberately left bespoke (never collapsed); and (5) the &lt;strong&gt;#3536&lt;/strong&gt; protected-branch refusal now branches its remedy on real coord-availability — a coord topology keeps the coordination-transaction remedy, a no-coord (&lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;) topology gets a &lt;strong&gt;followable&lt;/strong&gt; one (commit to a non-protected branch, or declare the ref unprotected via &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS&lt;/code&gt;), never the impossible coordination-branch instruction; the ref-only commit guard (&lt;code dir=&quot;auto&quot;&gt;commit_guard.evaluate&lt;/code&gt;) stays topology-blind and the no-coord answer is sourced from the commit-router SSOT (converging with epic #2739). The anti-bypass guard’s read-degrade check is &lt;strong&gt;tree-wide&lt;/strong&gt; — it walks every coord-catch &lt;code dir=&quot;auto&quot;&gt;try/except&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;src/specify_cli&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;src/mission_runtime&lt;/code&gt; (27 sites classified: seam-routed, family-bespoke, or explicitly not-a-read-dir-degrade with a stated reason), so a new un-dispositioned coord read-degrade anywhere in the tree fails CI naming its &lt;code dir=&quot;auto&quot;&gt;file:line&lt;/code&gt;. (One borderline site, &lt;code dir=&quot;auto&quot;&gt;migrate/backfill_provenance.py&lt;/code&gt;, is documented as a residual: it degrades a read to a dir but deliberately skips &lt;em&gt;silently&lt;/em&gt; per AM-4, which the WARNING-emitting seam can’t yet express without a new silent-degrade strategy.)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Legacy missions now carry a canonical &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;, so upgrading past the M3/M5 mission-type changes no longer breaks them.&lt;/strong&gt; (#3614) A new &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-mission-type&lt;/code&gt; command mints a &lt;strong&gt;profile-resolving&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; into every legacy &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; whose only type signal is the deprecated &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt; field, and the existing &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-type --fail-on …&lt;/code&gt; census gate proves a project is safe before it upgrades. &lt;strong&gt;Before:&lt;/strong&gt; a project carrying &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt;-only missions resolved fine today, but would go type-unresolvable once M5 drops the legacy reader, then hard-fail once M3 rejects unresolvable types — breaking on upgrade with no migration path. &lt;strong&gt;After:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-mission-type&lt;/code&gt; (idempotent; never overwrites an existing &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;; a &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; surface; a value that resolves no governance profile at any layer is reported &lt;code dir=&quot;auto&quot;&gt;needs_manual_resolution&lt;/code&gt;, never masked into a broken state), then gate the release with &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor mission-type --fail-on legacy-key-only,typeless,error&lt;/code&gt; (the states that actually break under M3+M5). The write decision is keyed on the same activation-independent &lt;code dir=&quot;auto&quot;&gt;MissionTypeProfileRepository&lt;/code&gt; tolerance M3 uses, so a valid built-in type resolves and backfills even on a project that has not activated it. &lt;strong&gt;Program ordering:&lt;/strong&gt; this backfill must land and be run against a project &lt;strong&gt;before&lt;/strong&gt; the M3 (#3596/#3598) and M5 mission-type-reader changes reach it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CI now measures its own false-red rate weekly instead of relying on a manual squad re-derivation, and draft PRs iterate faster without weakening the ready-for-review signal (mission &lt;code dir=&quot;auto&quot;&gt;ci-flake-report-workflow-01M0M9D8&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;FR-002&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-006&lt;/code&gt;–&lt;code dir=&quot;auto&quot;&gt;FR-010&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-018&lt;/code&gt;).&lt;/strong&gt; A new scheduled &lt;code dir=&quot;auto&quot;&gt;ci-flake-report.yml&lt;/code&gt; workflow (weekly + &lt;code dir=&quot;auto&quot;&gt;workflow_dispatch&lt;/code&gt;) classifies every completed &lt;code dir=&quot;auto&quot;&gt;CI Quality&lt;/code&gt; failure into &lt;code dir=&quot;auto&quot;&gt;perf_timing_flake&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;infra_flake&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;real&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;needs_review&lt;/code&gt;, reports the false-red rate and per-test timing cost, and uploads the findings (&lt;code dir=&quot;auto&quot;&gt;metrics.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;durations.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;report.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;state.json&lt;/code&gt;) as artifacts only — it never commits to the repo, never edits docs, and is not a required status check. Separately, &lt;code dir=&quot;auto&quot;&gt;CI Quality&lt;/code&gt; now behaves differently by PR state: a &lt;strong&gt;draft&lt;/strong&gt; PR fails fast (a new &lt;code dir=&quot;auto&quot;&gt;draft-fail-fast-cancel&lt;/code&gt; job cancels the run the moment &lt;code dir=&quot;auto&quot;&gt;lint&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;kernel-tests&lt;/code&gt; fails, so you get the first failure cheaply — a red draft run is therefore inherently partial), while a &lt;strong&gt;ready&lt;/strong&gt; PR still runs every diff-relevant chain to completion so a reviewer sees the full &lt;em&gt;relevant&lt;/em&gt; failure list in one pass, with untouched domains staying un-triggered exactly as before. A new push to a previously-red PR also re-runs the previously-failed tests first (&lt;code dir=&quot;auto&quot;&gt;--ff&lt;/code&gt;) in the &lt;code dir=&quot;auto&quot;&gt;fast-tests-cli&lt;/code&gt; suite (a first-cut pilot; other suites are not yet reordered), so a still-broken fix surfaces fastest. The merge-gate is unchanged in both modes. See the CI contract for draft versus ready runs and green-before-RFR for the full contract and the “watch your draft run green before flipping to ready” rule contributors and agents now follow.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Wall-clock performance tests no longer run on the PR path — a dedicated, statistical performance pipeline runs them off-band instead, so a slow shared runner can never again turn &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; red or block an unrelated PR (contributor/maintainer DevEx; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-22-1&lt;/code&gt;).&lt;/strong&gt; A false-red audit found &lt;strong&gt;58.6% of CI failures were inactionable flake&lt;/strong&gt;, dominated by single-shot wall-clock budget asserts (&lt;code dir=&quot;auto&quot;&gt;assert elapsed &amp;#x3C; N&lt;/code&gt;) that trip on cold-start, not on real regressions. &lt;strong&gt;Before:&lt;/strong&gt; ~60 budget tests ran in contended parallel PR shards and a single-shot &lt;code dir=&quot;auto&quot;&gt;timing-nfr-serial&lt;/code&gt; gate blocked merge on them — the largest false-red source. &lt;strong&gt;After:&lt;/strong&gt; every wall-clock/CPU-budget test carries &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.performance&lt;/code&gt; and is held out of every PR/blocking run (env-gated via &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_RUN_PERFORMANCE&lt;/code&gt;); a new scheduled + &lt;code dir=&quot;auto&quot;&gt;workflow_dispatch&lt;/code&gt; &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;performance.yml&lt;/code&gt;&lt;/strong&gt; runs them &lt;strong&gt;per-domain&lt;/strong&gt; (mirroring &lt;code dir=&quot;auto&quot;&gt;CI Quality&lt;/code&gt;’s split) through &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;pytest-benchmark&lt;/code&gt;&lt;/strong&gt; — calibrated rounds with warmup discard, percentile reporting, and &lt;code dir=&quot;auto&quot;&gt;--benchmark-compare-fail&lt;/code&gt; against a committed per-domain baseline, so a regression is caught &lt;strong&gt;statistically off-band&lt;/strong&gt; and alerts on the scheduled run only, never a single-shot ceiling on a PR. The on-PR &lt;code dir=&quot;auto&quot;&gt;timing-nfr-serial&lt;/code&gt; gate is retired; the separate daemon-health &lt;code dir=&quot;auto&quot;&gt;restart-daemon-nfr-timing&lt;/code&gt; gate and genuine behavioral non-hang/timeout guards (ReDoS bounds, “didn’t block on the network” checks) deliberately &lt;strong&gt;stay&lt;/strong&gt; on the PR path — they assert correctness, not a budget. Never retry-to-green. This closes the long-term half of #3595 (the interim &lt;code dir=&quot;auto&quot;&gt;performance&lt;/code&gt; marker landed in #3593).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-changed&quot;&gt;♻️ Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;merge/baseline.py&lt;/code&gt;’s committed-&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; reader now shares the one kernel L1 malformed-JSON authority instead of re-implementing it.&lt;/strong&gt; (#3330, follow-up to #3259/#3319) &lt;code dir=&quot;auto&quot;&gt;_read_committed_meta_json&lt;/code&gt; decoded the &lt;code dir=&quot;auto&quot;&gt;git show &amp;#x3C;target&gt;:meta.json&lt;/code&gt; blob with its own &lt;code dir=&quot;auto&quot;&gt;json.loads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;isinstance&lt;/code&gt; pair — a second, gate-invisible re-implementation of the malformed contract #3259 consolidated everywhere else. &lt;strong&gt;Before:&lt;/strong&gt; two independent decoders could drift on what counts as malformed. &lt;strong&gt;After:&lt;/strong&gt; the same &lt;code dir=&quot;auto&quot;&gt;git show&lt;/code&gt;-blob text is decoded via &lt;code dir=&quot;auto&quot;&gt;kernel.meta_decode.decode_meta&lt;/code&gt;, matching the sibling git-plumbing site (&lt;code dir=&quot;auto&quot;&gt;git/ref_advance.py&lt;/code&gt;); the two &lt;code dir=&quot;auto&quot;&gt;BaselineMergeCommitError&lt;/code&gt; message shapes callers depend on are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Untangled the three-way &lt;code dir=&quot;auto&quot;&gt;ExecutionMode&lt;/code&gt; name/token collision — one class named &lt;code dir=&quot;auto&quot;&gt;ExecutionMode&lt;/code&gt; no longer means three different things.&lt;/strong&gt; (#3416, prereq for #3590) Three unrelated classes were all named &lt;code dir=&quot;auto&quot;&gt;ExecutionMode&lt;/code&gt;, and two collided on a &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; member that meant &lt;strong&gt;contradictory&lt;/strong&gt; things. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;mission_runtime.context.ExecutionMode&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;worktree&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt;) was a dead, never-consumed local duplicate of the external &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events.status.ExecutionMode&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;worktree&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;direct_repo&lt;/code&gt;) axis, while &lt;code dir=&quot;auto&quot;&gt;specify_cli.ownership.models.ExecutionMode&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt;) modelled the unrelated “what a WP produces” axis — so a reader of &lt;code dir=&quot;auto&quot;&gt;ExecutionMode.code_change&lt;/code&gt; could not tell which axis they were on. &lt;strong&gt;After:&lt;/strong&gt; the dead &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; enum is &lt;strong&gt;retired&lt;/strong&gt; (removed from the package &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt; and the canonical-surface ADR); the live ownership enum is &lt;strong&gt;renamed&lt;/strong&gt; to &lt;code dir=&quot;auto&quot;&gt;WorkProductKind&lt;/code&gt; (its member string values &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; are &lt;strong&gt;unchanged&lt;/strong&gt;, so WP frontmatter stays wire-compatible); and the external &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events.status.ExecutionMode&lt;/code&gt; is now the single live class of that name, owning the worktree-vs-direct axis. A re-drift guard (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_execution_mode_no_redrift.py&lt;/code&gt;) fails if a &lt;code dir=&quot;auto&quot;&gt;class ExecutionMode&lt;/code&gt; or a local &lt;code dir=&quot;auto&quot;&gt;worktree&lt;/code&gt;+&lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; enum reappears in &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;, while permitting &lt;code dir=&quot;auto&quot;&gt;WorkProductKind&lt;/code&gt; to gain future members. Behaviour-preserving: no lane, worktree, or status-payload behaviour changed. The five-&lt;code dir=&quot;auto&quot;&gt;Severity&lt;/code&gt;-enum ladder co-located under #3416 is a separate acceptance block and remains open.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;analysis_report&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;acceptance&lt;/code&gt;’s artifact-filename constants no longer fail at &lt;code dir=&quot;auto&quot;&gt;import&lt;/code&gt; time.&lt;/strong&gt; (#3622, follow-up to #3599/#3617) &lt;code dir=&quot;auto&quot;&gt;_HASH_INPUTS&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;analysis_report.py&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;SPEC_FILE&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;PLAN_FILE&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;TASKS_FILE&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;PRIMARY_ARTIFACT_FILES&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;acceptance/__init__.py&lt;/code&gt;) resolved their filenames from the &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt; authority as module-level constants, so a malformed built-in manifest would raise on &lt;code dir=&quot;auto&quot;&gt;import specify_cli.analysis_report&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;import specify_cli.acceptance&lt;/code&gt; — a broad blast radius for a data fault, for two widely-imported CLI modules. &lt;strong&gt;After:&lt;/strong&gt; resolution is deferred to first access via a module &lt;code dir=&quot;auto&quot;&gt;__getattr__&lt;/code&gt; (PEP 562) plus call-time helper functions at each former call site, preserving the existing &lt;code dir=&quot;auto&quot;&gt;from specify_cli.acceptance import SPEC_FILE&lt;/code&gt;-style API and byte-identical resolved values; the failure now surfaces at point-of-use instead of at import.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Spec Kitty now ships a &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-show-me&lt;/code&gt; skill that guides any agent to
explain work with compact, checkable visuals — the smallest diagram,
pseudocode, or tree that answers the question — recommended from the specify
and plan surfaces (&lt;code dir=&quot;auto&quot;&gt;#3528&lt;/code&gt;).&lt;/strong&gt; Before, agents had no shared doctrine for &lt;em&gt;when&lt;/em&gt;
a visual earns its place or &lt;em&gt;which&lt;/em&gt; shape fits the point (call tree, sequence,
state diagram, C4, or a &lt;code dir=&quot;auto&quot;&gt;diff&lt;/code&gt; over the matching tree), so visual explanations
were ad-hoc and often missing. The skill routes to Spec Kitty’s canonical
Mermaid, PlantUML, C4, and diagram-review sources — bundling byte-pinned
portable copies of the guides and themes so it keeps working once installed in
a consumer project — and documents faithful &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.status&lt;/code&gt; TUI rendering
from &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; (lifecycle lanes vs the five-group display, and done-progress vs
weighted-readiness, so a custom board never mislabels weighted readiness as
completed work). Adapted from HumanLayer’s MIT-licensed &lt;code dir=&quot;auto&quot;&gt;show-me&lt;/code&gt; skill with
full attribution and license notice preserved.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An organisation doctrine pack can now ship templates and mission-FSM
content, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; actually resolves them at runtime — before, an org
pack could declare a template or mission that no resolution path would ever
find (&lt;code dir=&quot;auto&quot;&gt;#3524&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3523&lt;/code&gt;).&lt;/strong&gt; The two forked template resolvers
(&lt;code dir=&quot;auto&quot;&gt;doctrine/resolver.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;specify_cli/runtime/resolver.py&lt;/code&gt;) and the FSM
mission-discovery walks consulted only the built-in, project-legacy, and
user-global tiers — &lt;code dir=&quot;auto&quot;&gt;resolve_org_roots()&lt;/code&gt; existed but nothing on those paths
called it, so a configured, validated, activated org pack stayed inert for
templates and mission discovery. Now an &lt;code dir=&quot;auto&quot;&gt;ORG&lt;/code&gt; tier sits between the
project-legacy and user-global tiers in the asset chain (6 tiers) and in FSM
discovery (8 tiers); the two resolvers’ tier-1 mission-scoped override probe is
reconverged (they had silently drifted, so the same lookup behaved differently
depending on which resolver ran); and &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt; now reports org-sourced
entries with the correct &lt;code dir=&quot;auto&quot;&gt;ORG&lt;/code&gt; origin instead of mislabelling them
&lt;code dir=&quot;auto&quot;&gt;GLOBAL_MISSION&lt;/code&gt; and reading them from the wrong directory. Projects with no
org pack are unaffected — &lt;code dir=&quot;auto&quot;&gt;resolve_org_roots()&lt;/code&gt; returns &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; and every new
lookup is a no-op.&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 mission-type&lt;/code&gt; reports whether every mission’s
&lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; actually resolves, so a broken or unregistered type is visible
before it misbehaves (mission &lt;code dir=&quot;auto&quot;&gt;mission-type-guard-registry&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3402&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3386&lt;/code&gt;).&lt;/strong&gt; Modelled on &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt;, it walks every mission under
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; and classifies each into one of six distinguishable states —
&lt;code dir=&quot;auto&quot;&gt;resolved&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;activated-unresolvable&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;typeless&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;legacy-key-only&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; — and supports &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; for machine output and
&lt;code dir=&quot;auto&quot;&gt;--fail-on &amp;#x3C;state,...&gt;&lt;/code&gt; for CI gating (e.g.
&lt;code dir=&quot;auto&quot;&gt;--fail-on unknown,activated-unresolvable&lt;/code&gt; exits non-zero when any mission
sits in those states). Before, a mission whose type failed to resolve gave no
signal until the runtime silently applied the wrong rules; now the condition
is inspectable on demand.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A pack — built-in, org, fetched, or a charter bundle — now has one canonical
&lt;code dir=&quot;auto&quot;&gt;pack-manifest.yaml&lt;/code&gt; schema instead of two divergent formats (mission
&lt;code dir=&quot;auto&quot;&gt;pack-metadata-manifest-unification-01M052PT&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3500&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3501&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3502&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3503&lt;/code&gt;, slice of keystone &lt;code dir=&quot;auto&quot;&gt;#2467&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-16-1&lt;/code&gt;).&lt;/strong&gt; Before, org packs’
&lt;code dir=&quot;auto&quot;&gt;pack-manifest.yaml&lt;/code&gt; stored per-kind &lt;code dir=&quot;auto&quot;&gt;artifact_counts&lt;/code&gt; (no lineage, and never
written for the built-in pack every pack extends), while charter bundles’
&lt;code dir=&quot;auto&quot;&gt;synthesis-manifest.yaml&lt;/code&gt; enumerated &lt;code dir=&quot;auto&quot;&gt;constituents[]&lt;/code&gt; in an unrelated shape —
two formats that could drift, with neither covering the reference pack. Now the
unified schema (enumerated &lt;code dir=&quot;auto&quot;&gt;constituents:[{kind,id,path,content_hash}]&lt;/code&gt;, stored
&lt;code dir=&quot;auto&quot;&gt;artifact_counts&lt;/code&gt; retired for a derived &lt;code dir=&quot;auto&quot;&gt;counts_by_kind&lt;/code&gt; view, charter-only
fields in an optional &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; profile block) is defined and the built-in pack
emits it: a generated manifest (265 constituents, wired into &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine regenerate-graph&lt;/code&gt;) plus new authored &lt;code dir=&quot;auto&quot;&gt;packs/built-in/pack.yaml&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;pack.md&lt;/code&gt;
carrying a stable, immutable ULID &lt;code dir=&quot;auto&quot;&gt;pack_id&lt;/code&gt; and declared &lt;code dir=&quot;auto&quot;&gt;parent_pack&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;accompanies_doctrine_pack&lt;/code&gt; lineage edges, resolved exclusively through the
existing &lt;code dir=&quot;auto&quot;&gt;org_extends.resolve_extends_order&lt;/code&gt; (no second lineage walker —
enforced by a non-vacuous architectural ratchet). &lt;code dir=&quot;auto&quot;&gt;pack_version&lt;/code&gt; is
derive-else-fallback: authored in &lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt; when present, else generated, so
fetched/org packs keep genuine fetch-time provenance. This slice lands the
schema, models, and the built-in-pack writer; org/fetched/charter manifest
writers and the &lt;code dir=&quot;auto&quot;&gt;pack_id&lt;/code&gt; resolver cutover are fast-follow, and the broader
“compound packs” slice of &lt;code dir=&quot;auto&quot;&gt;#2467&lt;/code&gt; remains future work.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A new &lt;code dir=&quot;auto&quot;&gt;spk-run-verdict-capture&lt;/code&gt; skill so every agent harness records a WP
review verdict the same way (&lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;).&lt;/strong&gt; The sole authority for a verdict is 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 &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt; render
is non-authoritative); the skill documents the deterministic CLI seam
(&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task &amp;#x3C;WP&gt; --to approved|planned --review-feedback-file&lt;/code&gt;) and its verdict vocabulary, and &lt;code dir=&quot;auto&quot;&gt;spk-run-review-wp&lt;/code&gt;
now references it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Committed doctrine provenance is now portable across machines, checkouts,
and wheels — no more baked-in absolute paths (mission
&lt;code dir=&quot;auto&quot;&gt;operator-config-ergonomics&lt;/code&gt;, WP01/WP03/WP04; &lt;code dir=&quot;auto&quot;&gt;#3494&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;FR-001&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-002&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-003&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-006&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-007&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-008&lt;/code&gt;).&lt;/strong&gt; Committed
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent_profiles_manifest.json&lt;/code&gt; used to record each
built-in doctrine pack under the authoring machine’s absolute filesystem
path, so the same files broke on a teammate’s checkout, an installed wheel,
or CI. Both provenance carriers now emit a portable
&lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_PACKS_ROOT}/built-in/...&lt;/code&gt; token through one shared normalizer
and &lt;strong&gt;never&lt;/strong&gt; a resolved path — even when &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; is already
exported to an absolute path at emit time (the re-bake case is
regression-guarded). A single kernel expansion seam (&lt;code dir=&quot;auto&quot;&gt;src/kernel/env_expand.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;expand_env_template&lt;/code&gt;) backs both this token and the &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; pointer
below, and &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; is its canonical packs-root authority. An
idempotent &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; migration (&lt;code dir=&quot;auto&quot;&gt;m_3_2_7_heal_provenance_paths&lt;/code&gt;)
rewrites any already-committed absolute built-in path back to the portable
token with zero manual steps — this repo’s own leaked paths in
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/agent_profiles_manifest.json&lt;/code&gt;
were healed the same way. A new &lt;code dir=&quot;auto&quot;&gt;doctor provenance&lt;/code&gt; facet reports any
remaining leak with a heal hint.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Operator environment (SaaS tokens, org slugs, path overrides) now has one
file to point at, loaded before anything else runs (mission
&lt;code dir=&quot;auto&quot;&gt;operator-config-ergonomics&lt;/code&gt;, WP02; &lt;code dir=&quot;auto&quot;&gt;#3495&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;FR-004&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-004a&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-005&lt;/code&gt;).&lt;/strong&gt;
Previously these values had to live in your real shell environment or be
re-typed per project. A two-tier &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; file — &lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_HOME}/.kitty.env&lt;/code&gt;
machine-wide, overridden by &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;repo&gt;/.kittify/.kitty.env&lt;/code&gt; per-repo — is now
loaded into &lt;code dir=&quot;auto&quot;&gt;os.environ&lt;/code&gt; &lt;strong&gt;before&lt;/strong&gt; any other &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; module is
imported, so even import-time-gated behaviour picks it up. Precedence is
&lt;strong&gt;real-env &gt; per-repo &gt; home&lt;/strong&gt;: an explicit shell value always wins, and a
per-repo file only arms the project it lives in (unlike a global &lt;code dir=&quot;auto&quot;&gt;export&lt;/code&gt;,
which arms every project the shell later touches). &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;
gains a single &lt;code dir=&quot;auto&quot;&gt;env_file&lt;/code&gt; pointer (default &lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_HOME}/.kitty.env&lt;/code&gt;).
Fail policy is explicit: an absent file is skipped (the default for almost
every project today); a present-but-unreadable &lt;code dir=&quot;auto&quot;&gt;env_file&lt;/code&gt; fails loud and
names the file, because it gates auth; a malformed &lt;code dir=&quot;auto&quot;&gt;KEY=VALUE&lt;/code&gt; line is
skipped; and a &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME=&lt;/code&gt; line inside the file is dropped with a
warning to prevent locator recursion. An idempotent &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;
migration (&lt;code dir=&quot;auto&quot;&gt;m_3_2_8_provision_kitty_env&lt;/code&gt;) seeds the per-repo scaffold,
registers the &lt;code dir=&quot;auto&quot;&gt;env_file&lt;/code&gt; pointer, and adds &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;.claudeignore&lt;/code&gt;
rules — seeding only values already present in the environment, never a live
secret (secret-shaped vars are written as commented, blank templates). A new
&lt;code dir=&quot;auto&quot;&gt;doctor env-file&lt;/code&gt; facet reports presence, tier, readability, pointer, and
ignore-rule health with every value redacted through a fail-closed allowlist.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Opt-in release-candidate channel — catfood an rc without ever nagging
operators who did not ask (mission &lt;code dir=&quot;auto&quot;&gt;operator-config-ergonomics&lt;/code&gt;, WP05;
&lt;code dir=&quot;auto&quot;&gt;#3496&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;FR-009&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-010&lt;/code&gt;).&lt;/strong&gt; A default-off &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PRERELEASE&lt;/code&gt;
preference makes every “latest version” surface — &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --agent-check&lt;/code&gt; and the throttled startup nag — pre-release-aware only when
explicitly opted in. Left unset (the default, unchanged for every existing
project), only the latest &lt;strong&gt;stable&lt;/strong&gt; release is ever surfaced, even when a
newer rc exists on the index. Opted in, the newest PEP 440 pre-release is
surfaced and the proposed upgrade is a &lt;strong&gt;pinned&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty-cli==&amp;#x3C;rc&gt;&lt;/code&gt;
install, never a floating &lt;code dir=&quot;auto&quot;&gt;--pre&lt;/code&gt; flag. A new &lt;code dir=&quot;auto&quot;&gt;doctor channel&lt;/code&gt; facet reports
the active channel. This ships the consumer half only; CI’s rc build/publish
cadence stays in &lt;code dir=&quot;auto&quot;&gt;#3047&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;New architecture references tie the SaaS opt-in, &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt;, and rc-channel
decisions together (mission &lt;code dir=&quot;auto&quot;&gt;operator-config-ergonomics&lt;/code&gt;, WP06; &lt;code dir=&quot;auto&quot;&gt;FR-011&lt;/code&gt;).&lt;/strong&gt;
Two ADRs record the decisions:
&lt;a href=&quot;/adr/3.x/2026-08-16-5-operator-config-env-expansion-seam/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-08-16-5-operator-config-env-expansion-seam.md&lt;/code&gt;&lt;/a&gt;
(the kernel env-expansion seam, token provenance, and &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; layering)
and
&lt;a href=&quot;/adr/3.x/2026-08-16-4-rc-release-channel/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-08-16-4-rc-release-channel.md&lt;/code&gt;&lt;/a&gt;
(the default-off rc channel). A new
&lt;a href=&quot;../architecture/team-kitty-saas.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;team-kitty-saas.md&lt;/code&gt;&lt;/a&gt; architecture doc
walks the full opt-in → project-store migration → admission/delivery-target →
auth → history-disclosure → &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; flow with an end-to-end Mermaid
interaction diagram. Consumption docs and the &lt;code dir=&quot;auto&quot;&gt;spk-team-{sync,auth,tracker}&lt;/code&gt;
skills now point operators at the durable &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; mechanism instead of a
per-shell &lt;code dir=&quot;auto&quot;&gt;export&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An agent working the mission lifecycle — hitting a merge-gate rejection,
an issue-matrix verdict, or an undrained SaaS sync — previously had to
already know the mechanics, because they lived only in a maintainer’s
private notes (mission &lt;code dir=&quot;auto&quot;&gt;self-documenting-repo&lt;/code&gt; Bucket 2; &lt;code dir=&quot;auto&quot;&gt;#3464&lt;/code&gt;, follows
&lt;code dir=&quot;auto&quot;&gt;#3448&lt;/code&gt;).&lt;/strong&gt; A second audit of that private memory routed the durable
workflow / CI / git / status-&amp;#x26;-sync mechanics into the repo’s canonical
homes: &lt;code dir=&quot;auto&quot;&gt;docs/development/how-to/review-gates.md&lt;/code&gt; now carries the
(event-sourced) review-cycle + merge-gate mechanics and the issue-matrix
discovery surface; a new &lt;code dir=&quot;auto&quot;&gt;docs/operations/sync-drain.md&lt;/code&gt; documents the real
3-gate drain (&lt;code dir=&quot;auto&quot;&gt;saas_disabled&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;missing_auth&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;missing_team&lt;/code&gt;) and the
&lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; false-green trap; &lt;code dir=&quot;auto&quot;&gt;coverage-signals.md&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;known-friction-points.md&lt;/code&gt; gain the critical-path-move coverage remedy and
the CI-label skip guard; &lt;code dir=&quot;auto&quot;&gt;pr-landing.md&lt;/code&gt; gains true-base/stale-stack
diagnostics and a new &lt;code dir=&quot;auto&quot;&gt;compress-mission-history.md&lt;/code&gt; how-to; the
architecture docs correct a &lt;strong&gt;live stale-doc regression&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt;
claimed a &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;-absent &lt;code dir=&quot;auto&quot;&gt;-WP##&lt;/code&gt; fallback the resolver actually raises
&lt;code dir=&quot;auto&quot;&gt;MissingLanesError&lt;/code&gt; for); three review-discipline heuristics enrich the
doctrine tactics, and the &lt;code dir=&quot;auto&quot;&gt;gh&lt;/code&gt; “Closes #A,#B links only #A” trap lands in
the tracker toolguide. A committed
&lt;code dir=&quot;auto&quot;&gt;agent-memory-workflow-migration-manifest.md&lt;/code&gt; (with a completeness test)
maps all 49 audited memories to a repo home, an already-home citation, a
learned-fact note, or “keep-private”. Dogfooding payoff: verifying against
current code caught several &lt;em&gt;stale&lt;/em&gt; memories — the review-gate frontmatter
mechanism was retired for an event-sourced one, and the drain’s second gate
was mis-remembered as &lt;code dir=&quot;auto&quot;&gt;sync migrate&lt;/code&gt; (retired).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An agent tripping a gate, hunting the right doctrine template source, or
recovering a split-brain mission previously had to already know the
answer — that knowledge lived only in a maintainer’s private notes, not in
the repo (mission &lt;code dir=&quot;auto&quot;&gt;self-documenting-repo&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3448&lt;/code&gt;).&lt;/strong&gt; A maintainer audit
found this tribal knowledge nowhere in the shipped repo. Now it does:
architectural/docs gate assertions (&lt;code dir=&quot;auto&quot;&gt;write-side re-derivation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;inert schema slots&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;relative-link fixer&lt;/code&gt;) print a &lt;strong&gt;content-anchored remedy
derived from the gate’s own logic&lt;/strong&gt;, so tripping a gate tells you how to
satisfy it; &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt; corrects the stale &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/…&lt;/code&gt;
template-source path to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/…&lt;/code&gt; (with a grep guard);
six operator recovery runbooks for coord/lane split-brain scenarios are
published under &lt;code dir=&quot;auto&quot;&gt;docs/operations/&lt;/code&gt;, each leading with the shipped
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor … --fix&lt;/code&gt; where one exists; and the docs-inventory
freshen, mission wrap-up, and env/tracker conventions are now findable in
&lt;code dir=&quot;auto&quot;&gt;docs/development/&lt;/code&gt;. A committed &lt;code dir=&quot;auto&quot;&gt;agent-memory-migration-manifest.md&lt;/code&gt;
(with a completeness test) maps every audited gap-filler to its new repo
home, its tracking issue, or an explicit “behaviour retired” — the audit
surfaced five memories that were already stale (e.g. the shard-registration
guidance retired by &lt;code dir=&quot;auto&quot;&gt;#2671&lt;/code&gt;’s auto-cover, and a &lt;code dir=&quot;auto&quot;&gt;mission-gate-artifact&lt;/code&gt;
gate that never existed). Deleting the matching entries from a
maintainer’s live &lt;code dir=&quot;auto&quot;&gt;MEMORY.md&lt;/code&gt; stays a manual, per-operator checklist
tracked in the manifest — this mission migrates the knowledge into the
repo, it does not touch anyone’s private memory file. Three behaviour
quirks found along the way were filed, not fixed (&lt;code dir=&quot;auto&quot;&gt;#3450&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3451&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3452&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CI now builds each shippable module as its own reusable workflow, and a new
&lt;code dir=&quot;auto&quot;&gt;spec-kitty regen&lt;/code&gt; lets contributors fix generated-asset drift themselves
(mission &lt;code dir=&quot;auto&quot;&gt;modular-per-package-ci-01M025GV&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3447&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3379&lt;/code&gt;).&lt;/strong&gt; The
monorepo already ships separately-packaged modules (&lt;code dir=&quot;auto&quot;&gt;src/kernel&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;src/doctrine&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;packs/built-in&lt;/code&gt; data pack), but CI ran them as
path-filtered jobs inside one monolithic &lt;code dir=&quot;auto&quot;&gt;ci-quality&lt;/code&gt; workflow, and the
generated agent-command baselines + codex/vibe skill snapshots drifted
silently when their source prompt templates changed — a contributor’s
one-line edit tripped a dozen parity gates a maintainer had to regenerate by
hand (&lt;code dir=&quot;auto&quot;&gt;#3379&lt;/code&gt;). Now &lt;code dir=&quot;auto&quot;&gt;kernel&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; (fast + integration legs), and
&lt;code dir=&quot;auto&quot;&gt;packs&lt;/code&gt; each build in an &lt;code dir=&quot;auto&quot;&gt;on: workflow_call&lt;/code&gt; module workflow invoked as a
&lt;code dir=&quot;auto&quot;&gt;uses:&lt;/code&gt; job inside &lt;code dir=&quot;auto&quot;&gt;ci-quality&lt;/code&gt;, so a module has its own build boundary while
its coverage still aggregates into the single run the Sonar reporter reads
(reusable workflows, not &lt;code dir=&quot;auto&quot;&gt;workflow_run&lt;/code&gt; — coverage never fragments across
runs). The architectural CI-model guards learned to resolve &lt;code dir=&quot;auto&quot;&gt;uses:&lt;/code&gt;
delegation through one seam so a reusable-workflow caller is modeled as if it
ran inline. &lt;code dir=&quot;auto&quot;&gt;spec-kitty regen [--check]&lt;/code&gt; regenerates the committed generated
fixtures from source, byte-identical to a &lt;code dir=&quot;auto&quot;&gt;PYTEST_UPDATE_SNAPSHOTS&lt;/code&gt; run, from
a single shared version pin; &lt;code dir=&quot;auto&quot;&gt;--check&lt;/code&gt; is the fork-safe freshness gate (it
fails with the exact command + diff, since a fork PR’s read-only token cannot
commit back). A trust-tiered &lt;code dir=&quot;auto&quot;&gt;regen-assets&lt;/code&gt; workflow runs check-only on every
PR, auto-commits on same-repo pushes, and offers a maintainer-label
privileged path that ships disabled pending a security review. The 12-agent ×
N byte grid that caused the churn is retired for structural invariants plus
one canonical byte snapshot per render branch (markdown + TOML), so a
source-prompt edit now regenerates at most one canonical fixture instead of
~14.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An org- or project-tier doctrine pack can now contribute a mission type
that works end to end (mission &lt;code dir=&quot;auto&quot;&gt;up-mission-type-seam-01KZY1JB&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3424&lt;/code&gt;,
closes &lt;code dir=&quot;auto&quot;&gt;#3397&lt;/code&gt;).&lt;/strong&gt; Before, a mission type shipped by an org or project pack
could be declared and activated but not used: &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt;, charter
activation, and action-sequence projection all resolved against a
built-in-only roster, so a custom type either hard-failed or — worse —
silently resolved to an empty action sequence that planned nothing yet
reported success. Now a layered, pack-aware lookup resolves built-in, org,
and project mission types in that precedence order with a genuine action
sequence and template set, and four operator-facing surfaces stop reporting
falsehoods: &lt;code dir=&quot;auto&quot;&gt;charter mission-type list&lt;/code&gt; shows the real source layer,
&lt;code dir=&quot;auto&quot;&gt;mission-type show&lt;/code&gt; succeeds for an activated non-built-in type, &lt;code dir=&quot;auto&quot;&gt;doctrine mission-type list&lt;/code&gt; actually layers, and &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;’s step-removal
warnings compare real sequences. Three previously silent degradations —
malformed mission-type YAML, an unreadable roster directory, and an empty
action sequence from a non-built-in layer — now fail loud, naming the
offending file and layer. This is the availability slice only; mission-type
is deliberately not promoted to a first-class doctrine artifact kind (ADR
&lt;code dir=&quot;auto&quot;&gt;2026-08-13-1&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Hosted-sync consent is now per-project: one immutable &lt;code dir=&quot;auto&quot;&gt;project_uuid&lt;/code&gt; owns
one physically separate sync store and one explicit consent decision
(mission &lt;code dir=&quot;auto&quot;&gt;per-project-sync-consent-ledgers-01KZKMQZ&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3262&lt;/code&gt;, pairs with
SaaS &lt;code dir=&quot;auto&quot;&gt;#585&lt;/code&gt;).&lt;/strong&gt; Before, a shared journal/ledger/queue mixed every project’s
rows and a filter defect could deliver another project’s data (the #3030
consent incident). Now each project’s consent, consent epochs, journal,
delivery results, body/offline queue, target binding, and migration state
live in a UUID-owned &lt;code dir=&quot;auto&quot;&gt;ProjectSyncStore&lt;/code&gt; no other project’s operation can
open; &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt; records the only local grant authority
(offline-capable, never inherited from login/URL/slug/path/env), opt-out is
an immediate epoch-sealing barrier that never deletes captured rows, and
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC&lt;/code&gt; is strictly deny-only — arming it grants
nothing. Local consent additionally pairs with an independent target-scoped
SaaS admission generation, and &lt;code dir=&quot;auto&quot;&gt;project_not_admitted&lt;/code&gt; refusals park
terminally instead of retrying. Operators migrate legacy shared state with
the new copy-only, resumable project-store cutover commands
(&lt;code dir=&quot;auto&quot;&gt;spec-kitty 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;); the retired shared-store &lt;code dir=&quot;auto&quot;&gt;sync migrate&lt;/code&gt;
refuses with guidance.
See &lt;a href=&quot;../guides/project-sync-consent.md&quot;&gt;Per-Project Sync Consent&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The declarative transition-gate design is now documented as architecture,
and two mission-doctrine docs point at the right paths again (&lt;code dir=&quot;auto&quot;&gt;#3378&lt;/code&gt;).&lt;/strong&gt;
Before, the settled model for how transition gates work — the declarative
&lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; artefact kind, where a gate executes, the trusted-publisher rule, and
the typed-severity outcome — lived only in scattered discussion, and
&lt;code dir=&quot;auto&quot;&gt;mission-type-resolution.md&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;doctrine-kinds.md&lt;/code&gt; still named the
pre-relocation &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/&lt;/code&gt; source of truth. Now six Proposed
ADRs plus a &lt;code dir=&quot;auto&quot;&gt;mission-gates.md&lt;/code&gt; explanation page (with three render-verified
diagrams) capture the design in one place, and those two docs are retargeted
to the live &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/&lt;/code&gt; paths.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Documentation can now be marked &lt;code dir=&quot;auto&quot;&gt;durable&lt;/code&gt; — a standing reference that is
never flagged as stale draft (mission &lt;code dir=&quot;auto&quot;&gt;docs-plans-closeout-01KZTK2J&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3368&lt;/code&gt;).&lt;/strong&gt; Before, a long-lived throughline doc could only be &lt;code dir=&quot;auto&quot;&gt;active&lt;/code&gt;, so the
freshness SLA eventually nagged it toward “review or retire” like any aging
draft. Now &lt;code dir=&quot;auto&quot;&gt;durable&lt;/code&gt; is a reserved &lt;code dir=&quot;auto&quot;&gt;doc_status&lt;/code&gt; across the whole authority
chain (the &lt;code dir=&quot;auto&quot;&gt;042-common-docs&lt;/code&gt; directive, the &lt;code dir=&quot;auto&quot;&gt;DocStatus&lt;/code&gt; enum, the common-docs
styleguide and tactics, and the never-stale freshness rule), so a deliberate
standing document is left alone. This closeout also retires ~60 shipped or
superseded working notes in place (content preserved, evidence-cited) and
gathers the domain plans under &lt;code dir=&quot;auto&quot;&gt;docs/plans/domains/&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 intake&lt;/code&gt; now recognises an optional v1 handoff packet so upstream
requirements tools can seed a mission without the agent re-inventing FR/AC
ids.&lt;/strong&gt; A packet is ordinary Markdown; YAML frontmatter with &lt;code dir=&quot;auto&quot;&gt;handoff_packet: 1&lt;/code&gt;
is additive. Unknown versions and malformed YAML degrade to today’s prose
intake. &lt;code dir=&quot;auto&quot;&gt;intake --auto&lt;/code&gt; also scans &lt;code dir=&quot;auto&quot;&gt;.handoff/*.md&lt;/code&gt;. Contract:
&lt;code dir=&quot;auto&quot;&gt;docs/contracts/handoff-packet-v1.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The doctrine documentation site now shows rendered schema diagrams of the
doctrine artefacts, drawn locally with no network egress (mission
&lt;code dir=&quot;auto&quot;&gt;doctrine-schema-diagrams-01KZTQTH&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3366&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3354&lt;/code&gt;).&lt;/strong&gt; Before, the doctrine
layer’s shape — the relationship graph, the mission-step contract and action
index, the cross-kind overview and the full agent-profile schema — lived only
in prose, and the docsite had no way to render PlantUML at all. Now
code-grounded &lt;code dir=&quot;auto&quot;&gt;@startyaml&lt;/code&gt; diagrams are authored for each and &lt;strong&gt;drift-guarded
against the live frozen models&lt;/strong&gt; (a diagram that falls out of sync with the
code reds the build), then rendered offline by a version+sha256-pinned
PlantUML running inside a network-isolated container — so building the docs
sends nothing off-machine. Each rendered figure carries derived alt/aria text
for accessibility.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A shrink-only census gate now guards the 40 test sites that pin
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME&lt;/code&gt;, so the collision can only get smaller from here (mission
&lt;code dir=&quot;auto&quot;&gt;isolated-home-pin-guard-r1a-01KZNMA3&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;).&lt;/strong&gt; Before, nothing stopped a
41st ad-hoc home pin from landing, and a naive “converge them all” cleanup
would silently delete the load-bearing isolation those fixtures carry. Now a
content-addressed census — pinned as debt at a frozen SHA — plus a canonical
&lt;code dir=&quot;auto&quot;&gt;canonical_home&lt;/code&gt; owner fixture, a falsifiability probe, and a halt gate red the
build if the pinned set grows. Contributor-facing test infrastructure only (no
&lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; change); this lands the &lt;em&gt;instrument&lt;/em&gt; ahead of the follow-on adoption
(R1b), so &lt;code dir=&quot;auto&quot;&gt;Refs #3121&lt;/code&gt; rather than &lt;code dir=&quot;auto&quot;&gt;Closes&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The dead-symbol allowlist’s provenance is now a machine-readable
&lt;code dir=&quot;auto&quot;&gt;source_module=&lt;/code&gt; field instead of a parsed comment, so refreshing a still-dead
allowlisted symbol no longer depends on comment hygiene (mission
&lt;code dir=&quot;auto&quot;&gt;symbolkey-source-module-01M0B0SF&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3552&lt;/code&gt;).&lt;/strong&gt; Before, a content-tier entry’s
originating module lived only in its free-form &lt;code dir=&quot;auto&quot;&gt;# module::Name&lt;/code&gt; comment,
which the refresh helper (&lt;code dir=&quot;auto&quot;&gt;_refresh_dead_symbol_hashes.py&lt;/code&gt;) had to
tokenize-parse to recover — a fragile source of truth that had drifted into
multiple comment formats, and same-name symbols from different modules
couldn’t be told apart structurally. Now every content-tier &lt;code dir=&quot;auto&quot;&gt;SymbolKey&lt;/code&gt;
carries an optional, provenance-only &lt;code dir=&quot;auto&quot;&gt;source_module=&lt;/code&gt; keyword as the single
canonical source; the &lt;code dir=&quot;auto&quot;&gt;# module::Name&lt;/code&gt; comment stays in place as
human-readable audit trail, but the machine comment-parsing path is retired,
and same-name entries disambiguate on the field rather than on comment
convention. Test infrastructure only, no &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; change (no version bump).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&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; output is now a single copyable line (mission &lt;code dir=&quot;auto&quot;&gt;copyable-version-output-01KW6N9V&lt;/code&gt;).&lt;/strong&gt; The version callback no longer renders the ASCII-art banner before the distribution-aware version string, ready to paste into an issue report. Community contribution by @zohar.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;merge/baseline.py&lt;/code&gt;’s committed-&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; reader now shares the one kernel L1 malformed-JSON authority instead of re-implementing it.&lt;/strong&gt; (#3330, follow-up to #3259/#3319) &lt;code dir=&quot;auto&quot;&gt;_read_committed_meta_json&lt;/code&gt; decoded the &lt;code dir=&quot;auto&quot;&gt;git show &amp;#x3C;target&gt;:meta.json&lt;/code&gt; blob with its own &lt;code dir=&quot;auto&quot;&gt;json.loads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;isinstance&lt;/code&gt; pair — a second, gate-invisible re-implementation of the malformed contract #3259 consolidated everywhere else. &lt;strong&gt;Before:&lt;/strong&gt; two independent decoders could drift on what counts as malformed. &lt;strong&gt;After:&lt;/strong&gt; the same &lt;code dir=&quot;auto&quot;&gt;git show&lt;/code&gt;-blob text is decoded via &lt;code dir=&quot;auto&quot;&gt;kernel.meta_decode.decode_meta&lt;/code&gt;, matching the sibling git-plumbing site (&lt;code dir=&quot;auto&quot;&gt;git/ref_advance.py&lt;/code&gt;); the two &lt;code dir=&quot;auto&quot;&gt;BaselineMergeCommitError&lt;/code&gt; message shapes callers depend on are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;One canonical mission-type reader; the legacy &lt;code dir=&quot;auto&quot;&gt;{&quot;mission&quot;: …}&lt;/code&gt; field is no longer resolved and the silent &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; default is gone — so 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;/strong&gt; (#3598, epic #3410) ~10–12 hand-rolled &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; mission-type readers each re-derived their own field order and default, and they disagreed: the charter path read only &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; while the CLI path also honored the legacy &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt; field (so &lt;code dir=&quot;auto&quot;&gt;{&quot;mission&quot;: &quot;software-dev&quot;}&lt;/code&gt; resolved &lt;em&gt;typeless&lt;/em&gt; one way and &lt;em&gt;software-dev&lt;/em&gt; the other), four readers silently defaulted &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; (masking typeless/typo’d missions), and a dashboard reader read &lt;strong&gt;only&lt;/strong&gt; the legacy field. &lt;strong&gt;Before:&lt;/strong&gt; a typeless or &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt;-only mission was silently shown/recorded as &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; across the dashboard, retrospective records, and mission-identity resolution (including the context/status/acceptance/merge-gate identity payloads, via a downstream normalizer that re-defaulted to &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;). &lt;strong&gt;After:&lt;/strong&gt; every runtime reader resolves through one shared &lt;code dir=&quot;auto&quot;&gt;read_mission_type(meta)&lt;/code&gt; seam (canonical &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; only — no legacy fallback, no default), and the machine-facing identity normalizer no longer re-masks the neutral result; a typeless mission surfaces as neutral typeless / &lt;code dir=&quot;auto&quot;&gt;Unknown (…)&lt;/code&gt; on the dashboard, records its true type (or empty) in retrospectives, and resolves neutrally in the identity/status/acceptance/merge payloads. A structural gate (&lt;code dir=&quot;auto&quot;&gt;test_mission_type_reader_invariants.py&lt;/code&gt;) pins every reader to the shared seam and fails the build on any new legacy read or &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; fallback (genuine create-time/upgrade writers and the field-aware audit tool carry encoded, rationale-bearing allow-list exemptions). &lt;strong&gt;Deliberate behavior change with blast radius:&lt;/strong&gt; a legacy mission carrying only &lt;code dir=&quot;auto&quot;&gt;{&quot;mission&quot;: …}&lt;/code&gt; &lt;strong&gt;stops resolving&lt;/strong&gt; (goes typeless), and this &lt;em&gt;compounds&lt;/em&gt; with M3’s per-type hard-fail (silently-resolving → typeless → hard-fail). The safety net is the M0 &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-mission-type&lt;/code&gt; command (#3614), which &lt;strong&gt;must be run against a project before this change reaches it&lt;/strong&gt; — it mints a profile-resolving &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; into legacy &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt;-only missions and never fabricates an unresolvable type. Folds: #2901 (WP-frontmatter tolerant reader — verified already landed) and #2477–#2480 (inline meta reads — already exempted in &lt;code dir=&quot;auto&quot;&gt;inline_meta_read_allowlist.yaml&lt;/code&gt;). See ADR 2026-08-22-1.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Every &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; CLI command no longer eagerly loads the full status-orchestration and workspace machinery at import time — restoring the cold-import boundary the explicit owned-checkout work had quietly broken.&lt;/strong&gt; (landing fix; restores the #1461 boundary regressed by #3843) &lt;strong&gt;Before:&lt;/strong&gt; the owned-checkout lifecycle wired &lt;code dir=&quot;auto&quot;&gt;core.owned_mission&lt;/code&gt; into the &lt;code dir=&quot;auto&quot;&gt;task_utils.support&lt;/code&gt; leaf that 37 CLI command modules cold-import, and &lt;code dir=&quot;auto&quot;&gt;owned_mission&lt;/code&gt;’s module-level imports pulled the entire &lt;code dir=&quot;auto&quot;&gt;specify_cli.status&lt;/code&gt; package (30+ submodules) plus &lt;code dir=&quot;auto&quot;&gt;workspace&lt;/code&gt; into every command’s import path — a needless startup cost and a re-entrancy hazard the boundary exists to prevent. It surfaced as a red guard on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;test_charter_package_cold_import_keeps_status_orchestration_out&lt;/code&gt;). &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;owned_mission&lt;/code&gt; defers those two status-heavy imports to the one function that uses them (&lt;code dir=&quot;auto&quot;&gt;resolve_owned_mission&lt;/code&gt;), so cold-importing any command loads zero status/workspace modules; runtime behavior is unchanged. A new architectural gate (&lt;code dir=&quot;auto&quot;&gt;test_cold_import_status_boundary.py&lt;/code&gt;) now enforces the boundary at &lt;em&gt;any&lt;/em&gt; edge across the charter package, the &lt;code dir=&quot;auto&quot;&gt;task_utils&lt;/code&gt; leaf, and &lt;code dir=&quot;auto&quot;&gt;owned_mission&lt;/code&gt;, so a future reconnection is caught at its source rather than only through one command.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coord-topology missions now agree on one authoritative commit surface across create-time, &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;commit_router&lt;/code&gt;, and the task commands — closing a class of stranded-coordination-branch and silent-misroute defects.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;coord-commit-surface-authority-01M1M553&lt;/code&gt;; parent epic #2160; closes #2533 and #2300; B16-clause-2 of #2739 investigated and disproven — folds into #2533) A single kind-aware rule (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/coordination/surface_authority.py&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;coord_topology_reachable&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;resolve_surface_authority&lt;/code&gt;) is now the canonical authority all three loci consult. &lt;strong&gt;Before:&lt;/strong&gt; three layers disagreed. (1) &lt;code dir=&quot;auto&quot;&gt;mission create --pr-bound --start-branch &amp;#x3C;feature&gt;&lt;/code&gt; unconditionally minted &lt;code dir=&quot;auto&quot;&gt;topology: coord&lt;/code&gt; (the &lt;code dir=&quot;auto&quot;&gt;pr_bound&lt;/code&gt; arm short-circuited before any protection check), stranding an empty coordination branch on an unprotected feature branch and driving &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt; into a split-brain “materialized but carries no mission dir” primary-fallback (#2533). (2) The three task commands diverged for the same coord+protected situation — &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; skipped the redundant primary commit (exit 0, correct), &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; refused (exit 1), and &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; had drifted to event-log-only (no commit) — with each hardcoding its own verdict (#2300). (3) &lt;code dir=&quot;auto&quot;&gt;commit_router&lt;/code&gt; had four silent &lt;code dir=&quot;auto&quot;&gt;→ primary&lt;/code&gt; fallbacks (unresolvable &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; and coord-worktree-resolution exceptions) that could misroute a coordination-kind write to the primary checkout without signalling. &lt;strong&gt;After:&lt;/strong&gt; create-time mints &lt;code dir=&quot;auto&quot;&gt;COORD&lt;/code&gt; only when coordination routing is actually reachable (&lt;code dir=&quot;auto&quot;&gt;pr_bound AND (primary_protected(target) OR current==primary)&lt;/code&gt;) — &lt;code dir=&quot;auto&quot;&gt;--pr-bound --start-branch &amp;#x3C;unprotected&gt;&lt;/code&gt; now yields &lt;code dir=&quot;auto&quot;&gt;SINGLE_BRANCH&lt;/code&gt; with no stranded coord branch (keyed on the primary &lt;strong&gt;target&lt;/strong&gt; branch’s protection, preserving the #2581 pr-bound-on-feature-branch-with-protected-target → coord contract); &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; derive their verdict from the shared rule (behavior preserved — lifecycle-kind routes to coordination at exit 0, planning-kind on a protected primary refuses at exit 1 with a unified remedy), and &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt; stays event-log-only by construction; and all four &lt;code dir=&quot;auto&quot;&gt;commit_router&lt;/code&gt; corrupt-state fallbacks now fail loud (&lt;code dir=&quot;auto&quot;&gt;CoordWorktreeResolutionError&lt;/code&gt;) instead of silently writing to primary, while the two legitimate primary-routing early-returns (primary-kind / coord-less topology) are preserved and documented. The shipped &lt;code dir=&quot;auto&quot;&gt;#2739&lt;/code&gt; typed no-op contract (&lt;code dir=&quot;auto&quot;&gt;unchanged&lt;/code&gt; → exit 0) is unaffected. The &lt;code dir=&quot;auto&quot;&gt;coordination/&lt;/code&gt; layer takes no new &lt;code dir=&quot;auto&quot;&gt;cli&lt;/code&gt; import (the rule module depends only on &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Custom mission types are now first-class across dispatch, the plan-substantiveness gate, and the CLI’s fallback signal — instead of quietly degrading or crashing.&lt;/strong&gt; (landing fold for mission &lt;code dir=&quot;auto&quot;&gt;custom-mission-type-second-class-citizens-01M1FQXD&lt;/code&gt;; #3830, #3831, #3832) &lt;strong&gt;Before:&lt;/strong&gt; three related gaps. (1) The composition-dispatch probe logged a full ERROR traceback via &lt;code dir=&quot;auto&quot;&gt;logger.exception&lt;/code&gt; for every custom-type dispatch, because &lt;code dir=&quot;auto&quot;&gt;UnknownMissionTypeError&lt;/code&gt; — the ordinary, expected outcome for any non-charter-activated custom type — was treated as a genuine resolution failure. (2) A pack-provided &lt;code dir=&quot;auto&quot;&gt;plan-field-declaration.yaml&lt;/code&gt; resolved through &lt;code dir=&quot;auto&quot;&gt;resolve_template&lt;/code&gt;’s mission-agnostic tiers (global override, legacy, global non-mission) would gate &lt;strong&gt;every&lt;/strong&gt; undeclared custom mission type’s plan against one unrelated type’s fields, and a present-but-broken declaration (unreadable, mis-encoded, or carrying an unknown/typo’d key) failed with an unguarded exception instead of a diagnosable error. (3) &lt;code dir=&quot;auto&quot;&gt;mission-type current&lt;/code&gt;’s CLI-visible software-dev fallback signal (#3831/FR-005) silently dropped any &lt;em&gt;other&lt;/em&gt; warning raised in the same captured block. &lt;strong&gt;After:&lt;/strong&gt; the dispatch probe logs &lt;code dir=&quot;auto&quot;&gt;UnknownMissionTypeError&lt;/code&gt; at DEBUG (still diagnosable, never an ERROR on the happy path) and reserves ERROR/&lt;code dir=&quot;auto&quot;&gt;logger.exception&lt;/code&gt; for genuine failures; &lt;code dir=&quot;auto&quot;&gt;_pack_provided_declaration&lt;/code&gt; only honors a mission-scoped resolution (path containing &lt;code dir=&quot;auto&quot;&gt;/missions/{mission_type}/&lt;/code&gt;) and the parser now fails loud (&lt;code dir=&quot;auto&quot;&gt;_PackDeclarationError&lt;/code&gt;) on an unreadable/mis-encoded file or an unknown key, mirroring &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt; posture; and &lt;code dir=&quot;auto&quot;&gt;mission-type current&lt;/code&gt; re-emits every non-fallback warning through &lt;code dir=&quot;auto&quot;&gt;warnings.warn_explicit&lt;/code&gt; instead of dropping it. A dead pre-#3832 helper (&lt;code dir=&quot;auto&quot;&gt;_has_substantive_technical_context&lt;/code&gt;) is also removed as a campsite fold, superseded by the generalized &lt;code dir=&quot;auto&quot;&gt;_is_plan_substantive_for_type&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 upgrade&lt;/code&gt; no longer silently drops skill-content migrations on Windows when the managed &lt;code dir=&quot;auto&quot;&gt;SKILL.md&lt;/code&gt; is read-only.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;upgrade-surface-durability&lt;/code&gt;; fixes #3771) &lt;strong&gt;Before:&lt;/strong&gt; managed skill trees are set read-only by &lt;code dir=&quot;auto&quot;&gt;_make_tree_read_only&lt;/code&gt;, and on Windows the atomic &lt;code dir=&quot;auto&quot;&gt;Path.replace&lt;/code&gt; inside &lt;code dir=&quot;auto&quot;&gt;write_text_within_directory&lt;/code&gt; fails with &lt;code dir=&quot;auto&quot;&gt;[WinError 5]&lt;/code&gt; when the target is read-only. The &lt;code dir=&quot;auto&quot;&gt;2.1.2_fix_*&lt;/code&gt; skill-content migrations (glossary-context, orchestrator-api, runtime-next) route through that write path, caught the &lt;code dir=&quot;auto&quot;&gt;PermissionError&lt;/code&gt; as an &lt;code dir=&quot;auto&quot;&gt;OSError&lt;/code&gt;, recorded the migration as &lt;code dir=&quot;auto&quot;&gt;failed&lt;/code&gt; in the ledger, and left the old skill content in place — the upgrade still reported overall success, so the stale content was invisible. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;write_text_within_directory&lt;/code&gt; restores the target’s write bit before the atomic replace (mirroring the already-blessed &lt;code dir=&quot;auto&quot;&gt;runtime/generated_writer&lt;/code&gt; pattern, skipping symlinks so it never chmods through a link), so the rewrite lands on Windows and every migration entry point on that path is fixed at once. The replaced file keeps the temp file’s writable mode exactly as on POSIX today. Regression coverage simulates the Windows &lt;code dir=&quot;auto&quot;&gt;os.replace&lt;/code&gt; failure on Linux CI (a bare &lt;code dir=&quot;auto&quot;&gt;chmod(0o444)&lt;/code&gt; does not reproduce it off Windows, since the rename keys on the directory bit) plus a native &lt;code dir=&quot;auto&quot;&gt;skipif(win32)&lt;/code&gt; contract test.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now refreshes a stale &lt;code dir=&quot;auto&quot;&gt;.claude/CLAUDE.md&lt;/code&gt; orientation surface (and every other harness context file) instead of leaving an outdated version string that contradicts the live &lt;code dir=&quot;auto&quot;&gt;SessionStart&lt;/code&gt; hook.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;upgrade-surface-durability&lt;/code&gt;; fixes #2265) &lt;strong&gt;Before:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;!-- spec-kitty:orientation --&gt;&lt;/code&gt; block was stamped at &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; and never re-emitted on an up-to-date upgrade — &lt;code dir=&quot;auto&quot;&gt;session-start&lt;/code&gt; is stdout-only, the one-shot &lt;code dir=&quot;auto&quot;&gt;rc39&lt;/code&gt; refresh migration is version-gated and never fires on the “already up to date” path, and the always-on surface-repair leg’s &lt;code dir=&quot;auto&quot;&gt;SessionPresenceProvider&lt;/code&gt; did only a bare marker-existence check (never reporting the block stale) while its repair actioned only missing files. An agent then loaded an orientation block frozen at the init-time version. &lt;strong&gt;After:&lt;/strong&gt; the provider is version-aware — &lt;code dir=&quot;auto&quot;&gt;probe()&lt;/code&gt; reports &lt;code dir=&quot;auto&quot;&gt;STATE_STALE&lt;/code&gt; for a present context file whose stamped &lt;code dir=&quot;auto&quot;&gt;**Spec Kitty v…**&lt;/code&gt; version differs from the installed CLI, and &lt;code dir=&quot;auto&quot;&gt;repair()&lt;/code&gt; actions &lt;code dir=&quot;auto&quot;&gt;STATE_STALE&lt;/code&gt; alongside missing, rewriting the block in place via the canonical &lt;code dir=&quot;auto&quot;&gt;SessionPresenceContent&lt;/code&gt; emitter. Because surface-repair runs on every &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; (including “already up to date”), the refresh is idempotent and version-independent, and it covers every version-stamped orientation surface uniformly — both context files (&lt;code dir=&quot;auto&quot;&gt;.claude/CLAUDE.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;GEMINI.md&lt;/code&gt;, copilot instructions) and rule/steering files (&lt;code dir=&quot;auto&quot;&gt;.cursor/rules/spec-kitty.mdc&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kiro/steering/spec-kitty.md&lt;/code&gt;). The version stamp is parsed only inside the &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;!-- spec-kitty:orientation --&gt;&lt;/code&gt; marker block (so a stray stamp elsewhere in the file cannot fool it), and the comparison is version-only, so a legitimate health-line change at the same version does not churn the block; a hand-edited block with no parseable stamp is left alone.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Adjudicated the #2316 uv-tool auto-upgrade “env/&lt;code dir=&quot;auto&quot;&gt;--python&lt;/code&gt; drift” as a stale-test artifact, not a product regression, and added the missing end-to-end coverage.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;upgrade-surface-durability&lt;/code&gt;; closes #2316) The issue asked to restore threading of a custom &lt;code dir=&quot;auto&quot;&gt;UV_TOOL_DIR&lt;/code&gt; and the receipt &lt;code dir=&quot;auto&quot;&gt;--python&lt;/code&gt; pin into the &lt;code dir=&quot;auto&quot;&gt;uv tool install&lt;/code&gt; auto-upgrade argv, and to un-skip two tests. Investigation as the upgrade owner found the behavior is &lt;strong&gt;not&lt;/strong&gt; lost: the argv/env assembly moved into &lt;code dir=&quot;auto&quot;&gt;compat.remediation&lt;/code&gt; during the god-module decomposition and is wired end-to-end through &lt;code dir=&quot;auto&quot;&gt;run_upgrade_ux&lt;/code&gt;; the two tests were deleted (in an ancestor of &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;) as inert bodies pinned to the retired inline seam. The genuine gap was end-to-end coverage — nothing proved the &lt;code dir=&quot;auto&quot;&gt;run_upgrade_ux → plan_remediation → _default_upgrade_runner → subprocess.run(env=…)&lt;/code&gt; chain still delivers both. A new hermetic regression pins it at the correct seam (patching &lt;code dir=&quot;auto&quot;&gt;detect_runtime&lt;/code&gt;), verified non-vacuous against the exact #2316 failure signature. No product change.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lifecycle commands on a protected-primary / coordination-topology mission no longer leave the working tree dirty, report false success, or refuse with un-followable guidance — the commit-router, the protected-primary refusal, and the create/discard commit boundaries now agree on where planning artifacts land.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;commit-boundary-router-integrity&lt;/code&gt;; epic #2739; fixes #3784, #2693, #3716; B02 of #2739 was already fixed on main) A single shared defect class — the commit-router’s file-kind filter, the protected-primary refusal path, and coordination-topology routing disagreeing on the primary/planning commit surface — surfaced as four distinct failures, each fixed red-first (&lt;code dir=&quot;auto&quot;&gt;@pytest.mark.regression&lt;/code&gt; reproduction through the real entry point, then relocated to a permanent guard):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3784&lt;/strong&gt; — On a coordination topology, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s claim-commit bundle dropped only the two &lt;code dir=&quot;auto&quot;&gt;STATUS_STATE&lt;/code&gt; files (&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;) from the primary-root commit but let the coordination-worktree &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; (a &lt;code dir=&quot;auto&quot;&gt;TASKS_INDEX&lt;/code&gt; kind) survive, so &lt;code dir=&quot;auto&quot;&gt;safe_commit(worktree_root=repo_root, …)&lt;/code&gt; tripped &lt;code dir=&quot;auto&quot;&gt;SafeCommitPathPolicyError&lt;/code&gt; (“refusing to stage path under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;”) and left the WP file uncommitted. &lt;strong&gt;After:&lt;/strong&gt; the bundle excludes &lt;strong&gt;any&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;-nested path (the real #2155 invariant — “no &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; path reaches a primary-surface &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt;”), via a single extracted &lt;code dir=&quot;auto&quot;&gt;_primary_surface_status_paths&lt;/code&gt; helper.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2693&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; committed only &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;; the step-8 event emission then mutated &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; &lt;strong&gt;after&lt;/strong&gt; the commit, and &lt;code dir=&quot;auto&quot;&gt;tasks/README.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tasks/.gitkeep&lt;/code&gt; were left untracked and unreported, so a create that “succeeded” left a dirty, undisclosed scaffold. &lt;strong&gt;After:&lt;/strong&gt; event emission runs &lt;strong&gt;before&lt;/strong&gt; one transactionally-complete commit of the create-owned scaffold (&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; scaffolding); &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; (deliberately owned by &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt;, per #846) stays uncommitted but is now &lt;strong&gt;disclosed&lt;/strong&gt; in the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; payload’s &lt;code dir=&quot;auto&quot;&gt;uncommitted_artifacts&lt;/code&gt; with its responsible command — nothing generated is ever untracked &lt;em&gt;and&lt;/em&gt; undisclosed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3716&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;mission close --discard&lt;/code&gt; reported success while leaving the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; flatten (popping &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;topology&lt;/code&gt;) uncommitted — it was the last write on the discard path and had no commit leg — and stamped the persisted retrospective &lt;code dir=&quot;auto&quot;&gt;provenance.kind: runtime_post_completion&lt;/code&gt; on an abandoned mission. &lt;strong&gt;After:&lt;/strong&gt; the flatten is committed to the &lt;strong&gt;primary&lt;/strong&gt; surface (the coordination branch is already deleted, so the primary &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; is both destination and degrade ref; the sibling retrospective commit degrade was fixed the same way, so &lt;code dir=&quot;auto&quot;&gt;--discard&lt;/code&gt; leaves a clean tree), and a new &lt;code dir=&quot;auto&quot;&gt;runtime_abandoned&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;ProvenanceKind&lt;/code&gt; is threaded through the discard leg so an abandoned mission is no longer recorded as completed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2739&lt;/strong&gt; — Protected-primary &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt; surfaced un-followable and misleading outcomes. &lt;strong&gt;After:&lt;/strong&gt; B01 — the command &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;no_op_wrong_surface&lt;/code&gt; remedy text drop the impossible “materialise the coordination worktree and retry” hint (primary/planning artifacts never route to coordination) and name the two real remedies (&lt;code dir=&quot;auto&quot;&gt;--start-branch &amp;#x3C;feature-branch&gt;&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS=1&lt;/code&gt;, the latter also added to the router diagnostic); B03 — an &lt;code dir=&quot;auto&quot;&gt;unchanged&lt;/code&gt; no-op now carries a machine-readable &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;no_op_already_committed&lt;/code&gt; vs &lt;code dir=&quot;auto&quot;&gt;no_op_no_changes&lt;/code&gt;) so a real success is distinguishable from a silent no-op; B11 — a directory argument is rejected early with a clear files-only message instead of the opaque staging-area backstop; B16 — a coordination-partition file written to the primary tree that routes to coordination where nothing stages is now refused as &lt;code dir=&quot;auto&quot;&gt;no_op_wrong_surface&lt;/code&gt; (via &lt;code dir=&quot;auto&quot;&gt;_paths_uncommitted_in_primary&lt;/code&gt;) instead of falsely reporting &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt; while landing nowhere.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter context --include directive:&amp;#x3C;id&gt;&lt;/code&gt; now resolves the exact directive IDs the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; surface advertises, at parity with the &lt;code dir=&quot;auto&quot;&gt;tactic:&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agent-profile:&lt;/code&gt; selectors.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;charter-command-honesty&lt;/code&gt;; fixes #3816; parent epic #3809) &lt;strong&gt;Before:&lt;/strong&gt; the directive selector returned &lt;code dir=&quot;auto&quot;&gt;EXIT 1 &quot;No directive found&quot;&lt;/code&gt; for a valid, active slug ID (&lt;code dir=&quot;auto&quot;&gt;025-boy-scout-rule&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;001-architectural-integrity-standard&lt;/code&gt;) — the very IDs &lt;code dir=&quot;auto&quot;&gt;charter context --action &amp;#x3C;x&gt; --json&lt;/code&gt; enumerates — while resolving only the &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_NNN&lt;/code&gt; form. The two identity spaces diverged: &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; advertises the file-stem &lt;strong&gt;slug&lt;/strong&gt;, but the directive lookup ran the id through a numeric-only formatter that let the slug fall through and miss the &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_NNN&lt;/code&gt;-keyed repository, so an injected directive ID was a dead end for the compaction path (#3811). &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;DirectiveRepository.get&lt;/code&gt; normalizes every identifier through the single canonical authority (&lt;code dir=&quot;auto&quot;&gt;normalize_directive_id&lt;/code&gt;) — slug, numeric shorthand, and &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_NNN&lt;/code&gt; all resolve the same directive — and the &lt;code dir=&quot;auto&quot;&gt;--include&lt;/code&gt; renderer hands the identifier through verbatim, echoing the resolved canonical id in its header. The same slug-vs-&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_NNN&lt;/code&gt; divergence also silently dropped &lt;strong&gt;every&lt;/strong&gt; directive from the gated &lt;code dir=&quot;auto&quot;&gt;DoctrineService.directives&lt;/code&gt; property whenever &lt;code dir=&quot;auto&quot;&gt;activated_directives&lt;/code&gt; was configured (item keys spoke &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_NNN&lt;/code&gt;, the activated set spoke slugs); it is closed by comparing both sides in canonical space. A close-by-construction regression test asserts every advertised built-in directive slug resolves &lt;code dir=&quot;auto&quot;&gt;EXIT 0&lt;/code&gt;. Verified red-first through the real &lt;code dir=&quot;auto&quot;&gt;charter context --include&lt;/code&gt; entry point.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate --from-interview&lt;/code&gt; now reports a present-but-corrupt &lt;code dir=&quot;auto&quot;&gt;answers.yaml&lt;/code&gt; honestly, instead of claiming no answers exist.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;charter-command-honesty&lt;/code&gt;; #2940) &lt;strong&gt;Before:&lt;/strong&gt; the read boundary degraded BOTH a genuinely-missing file AND a present-but-unreadable one (invalid YAML, or a top level that is not a mapping) to the same &lt;code dir=&quot;auto&quot;&gt;&quot;No charter interview answers found&quot;&lt;/code&gt; error — which sends the operator to re-run the interview, when the real fault is a corrupt file that a fresh interview would silently overwrite, masking the problem. &lt;strong&gt;After:&lt;/strong&gt; a present-but-malformed answers file produces a distinct diagnostic that names the file and its malformed shape and points at repair/&lt;code dir=&quot;auto&quot;&gt;--no-from-interview&lt;/code&gt;, while the genuinely-missing case keeps its original “run the interview” message. The interview→generate round-trip itself was already correct on current main; a close-by-construction regression test now pins it end-to-end (real &lt;code dir=&quot;auto&quot;&gt;charter interview&lt;/code&gt; write → &lt;code dir=&quot;auto&quot;&gt;charter generate --from-interview&lt;/code&gt; read, asserting the answers are consumed rather than silently replaced by defaults) so it can never regress. (The original report — Spec Kitty 3.2.6, macOS, &lt;code dir=&quot;auto&quot;&gt;uv tool&lt;/code&gt; install — could not be reproduced from source; the round-trip lock guards the contract regardless.)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter lint&lt;/code&gt;’s clean-working-tree contract is now pinned by a regression guard (no behavioral change) — the report it writes stays gitignored, so it never trips a downstream dirty-tree guard.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;charter-command-honesty&lt;/code&gt;; #3435) &lt;code dir=&quot;auto&quot;&gt;charter lint&lt;/code&gt; writes &lt;code dir=&quot;auto&quot;&gt;.kittify/lint-report.json&lt;/code&gt; — a load-bearing artifact the dashboard decay tile and the SaaS dossier read from disk — so the read-only-diagnostic honesty contract is met by shipping the gitignore entry (&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; authors it; a backfill migration heals upgraded projects), not by suppressing the write. That entry was already shipped on current main; this change adds a close-by-construction regression guard that runs the real engine write through the real init gitignore authoring and asserts the tree stays clean (with a control proving the same write would surface as untracked without the ignore entry), so a future regression that either stops writing the report or drops the ignore entry is caught.&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; no longer restarts a merged mission or stalls on an operator-canceled work package — the loop now decides from the committed status authority, not a stale coordination worktree or a lane-only predicate.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;next-committed-state-authority&lt;/code&gt;; #2947, #3780; milestone 3.2.6; parent epic #1619) &lt;strong&gt;Before:&lt;/strong&gt; two independent defects. (1) With a stale coordination worktree checkout left at an old commit, &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; ignored the committed &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; (all WPs &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;) and the assigned &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt;, fabricated a fresh runtime run from &lt;code dir=&quot;auto&quot;&gt;discovery&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; pointed at the stale checkout where the mission artifacts were missing, and &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; rolled the mission up all-&lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; — completed work looked unstarted (#2947). (2) The review-step advancement predicate &lt;code dir=&quot;auto&quot;&gt;_wp_blocks_step&lt;/code&gt; was lane-only (&lt;code dir=&quot;auto&quot;&gt;lane not in (DONE, APPROVED)&lt;/code&gt;), so an operator-canceled WP — an honest ending post-#3774 on the accept/merge axes — was treated as not-handed-off and stalled the loop (#3780). &lt;strong&gt;After:&lt;/strong&gt; (1) &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; resolves committed state &lt;strong&gt;before&lt;/strong&gt; selecting a coordination workspace: a merged mission (committed &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; assigned &lt;strong&gt;and&lt;/strong&gt; committed status all-accepted) returns &lt;code dir=&quot;auto&quot;&gt;kind: terminal&lt;/code&gt; in advancing mode (creating &lt;strong&gt;no&lt;/strong&gt; run) and &lt;code dir=&quot;auto&quot;&gt;kind: query&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;mission_state: done&lt;/code&gt; in read-only query mode; a merge/status conflict, or an actionable step whose workspace checkout lacks the mission’s artifacts, fails closed with a structured &lt;code dir=&quot;auto&quot;&gt;kind: blocked&lt;/code&gt;; and &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; reads committed lanes. The merge signal is the committed &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; only — never transient merge-state / an active &lt;code dir=&quot;auto&quot;&gt;MERGE_HEAD&lt;/code&gt;, which are absent precisely when a mission is finished. (2) &lt;code dir=&quot;auto&quot;&gt;_should_advance_wp_step&lt;/code&gt; threads the reduced snapshot’s provenance (derived from a &lt;strong&gt;single&lt;/strong&gt; status reduction that preserves the &lt;code dir=&quot;auto&quot;&gt;CanonicalStatusNotFoundError&lt;/code&gt; fail-loud contract) and routes the review/implement advancement predicate through the shipped &lt;code dir=&quot;auto&quot;&gt;is_acceptable_ending&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;has_operator_provenance&lt;/code&gt; authority — a canceled-&lt;strong&gt;with-operator-provenance&lt;/strong&gt; WP advances, a &lt;strong&gt;synthetic&lt;/strong&gt; cancellation stays blocking (fail-closed). Both surfaces consume one committed-authority module (&lt;code dir=&quot;auto&quot;&gt;src/runtime/next/committed_authority.py&lt;/code&gt;); the shipped acceptable-ending authority and the lane state machine are unchanged. Verified red-first through the real &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; entry points with live before/after execution. Two secondary observations from the surfacing squad (a redundant coordination read in &lt;code dir=&quot;auto&quot;&gt;merge/done_bookkeeping.py&lt;/code&gt;; a &lt;code dir=&quot;auto&quot;&gt;reason_source&lt;/code&gt; denylist gap in &lt;code dir=&quot;auto&quot;&gt;core/upstream_contract.json&lt;/code&gt;) are tracked as separate follow-ups.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&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 instead of silently deleting branches and worktrees a mission asked to keep.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;merge-honor-retention-policy-01M1CA0E&lt;/code&gt;; fixes #3131) &lt;strong&gt;Before:&lt;/strong&gt; post-merge cleanup was driven entirely by the &lt;code dir=&quot;auto&quot;&gt;--delete-branch&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--keep-branch&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--remove-worktree&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--keep-worktree&lt;/code&gt; flags, both defaulting to delete/remove; a mission had no machine-readable way to express “keep my branches and worktrees,” so a prose constraint in &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; was invisible to merge — on one observed mission, merge deleted six lane worktrees, six lane branches, and the mission branch with no warning that the cleanup contradicted the mission’s stated intent. &lt;strong&gt;After:&lt;/strong&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 effective cleanup via one resolver (&lt;code dir=&quot;auto&quot;&gt;resolve_merge_retention&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;core/paths.py&lt;/code&gt; — an I/O-performing resolver that reads the mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, like &lt;code dir=&quot;auto&quot;&gt;resolve_merge_target_branch&lt;/code&gt;) with precedence &lt;strong&gt;explicit CLI flag &gt; meta.json retention &gt; default&lt;/strong&gt;, failing closed toward retention on any ambiguity (a corrupt &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; aborts the merge; a malformed non-boolean value retains + warns, never truthiness-coerced to delete). An explicit CLI delete override still works but is never silent — it prints a recorded notice naming the contradicted policy. The coordination branch, worktree, and marker are torn down (or retained) as one coupled decision so partial retention can never leave a half-torn coordination state, and &lt;code dir=&quot;auto&quot;&gt;merge --abort&lt;/code&gt; honors the same coupled decision. The internal merge scratch worktree is unaffected and always cleans up. Retention is mintable at creation via &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission create --retain-branches --retain-worktrees&lt;/code&gt;. Non-retaining missions are unchanged — cleanup behavior stays byte-identical.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Adversarial review squads run &lt;em&gt;profiled&lt;/em&gt; again — the two doctrine lenses the squad relies on (&lt;code dir=&quot;auto&quot;&gt;doctrine-daphne&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;randy-reducer&lt;/code&gt;) are re-activated, so delegates stop silently dispatching with no profile, boundaries, or directives applied.&lt;/strong&gt; (enabler mission &lt;code dir=&quot;auto&quot;&gt;tidy-charter-cutover-surface&lt;/code&gt;; closes #3810) &lt;strong&gt;Before:&lt;/strong&gt; the shipped charter activation allowlist (&lt;code dir=&quot;auto&quot;&gt;src/charter/activation/packs/default.yaml&lt;/code&gt;) omitted exactly those two lenses, so the FR-014 activation gate returned &lt;code dir=&quot;auto&quot;&gt;EXIT 1 &quot;is not activated&quot;&lt;/code&gt; and a compliant delegate — whose only sanctioned raw-YAML fallback is for CLI-less harnesses — had no recovery and proceeded &lt;strong&gt;unprofiled, with nothing erroring at the orchestrator&lt;/strong&gt;. &lt;strong&gt;After:&lt;/strong&gt; both lenses are activated in the default pack (nothing deactivated), the gate resolves them cleanly, and a regression test pins the squad’s hardcoded lenses as a subset of the activated set. The near-term half of profile-load epic #3809; the durable orchestrator-inject seam remains #3811.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter bundle validate&lt;/code&gt; now catches byte-identical &lt;em&gt;doubled-leaf&lt;/em&gt; synthesis artifacts (&lt;code dir=&quot;auto&quot;&gt;.../provenance/provenance/*&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.../styleguide/styleguide/*&lt;/code&gt;) — a corruption class its name-keyed pairing checks previously missed.&lt;/strong&gt; (enabler mission &lt;code dir=&quot;auto&quot;&gt;tidy-charter-cutover-surface&lt;/code&gt;; closes #3819) Investigation found &lt;strong&gt;no reproducible defect in the current artifact writer&lt;/strong&gt; — every path-join is flat and a twice-run re-synthesis produces zero doubles, so the historical doubled files came from a superseded writer or manual tooling. The risk is therefore closed by a &lt;strong&gt;detection guard&lt;/strong&gt;, not a phantom code fix. Charter synthesis artifacts remain a &lt;strong&gt;trackable-by-design&lt;/strong&gt; surface (per the KD-2 commit-ready contract); they are &lt;em&gt;not&lt;/em&gt; gitignored.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coding agents — especially smaller models — no longer stall mid-implementation to demand human approval and build “prove every step was signed off” scaffolding; and the review/accept gates now capture real, bound evidence instead of unattributed notes.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;governance-at-the-gate&lt;/code&gt;; #3685, #3682) &lt;strong&gt;Before:&lt;/strong&gt; the decision-documentation directive (&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_003&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;required&lt;/code&gt;) was delivered into the &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; action bundle — directly, and transitively via an implement-scoped procedure whose &lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt; link the resolver promoted to an unconditional &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; — so a literal reader composing the &lt;code dir=&quot;auto&quot;&gt;required&lt;/code&gt; directives landed on “author a durable decision artifact, alternatives, rationale, traceable” &lt;em&gt;during implementation&lt;/em&gt; and stopped to ask a human. Compounding it, the doctrine-delivery resolver was enforcement-flat and tension-blind: the &lt;code dir=&quot;auto&quot;&gt;Enforcement&lt;/code&gt; levels had no ordering, and the tension arbiter (&lt;code dir=&quot;auto&quot;&gt;reconcile-change-scope-tensions&lt;/code&gt;, itself the weakest &lt;code dir=&quot;auto&quot;&gt;advisory&lt;/code&gt;) never reached the agent &lt;em&gt;as&lt;/em&gt; an arbiter — so a weak model had no signal that a brake outranked a do-more rule. Separately, at the deciding gates the evidence was thin — an &lt;code dir=&quot;auto&quot;&gt;in_review → approved&lt;/code&gt; transition recorded an unattributed prose note (no &lt;code dir=&quot;auto&quot;&gt;policy_metadata&lt;/code&gt;, no &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;), a first-pass approval wrote no &lt;code dir=&quot;auto&quot;&gt;review-cycle&lt;/code&gt; artifact at all, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; left &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt; an unfilled &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt; scaffold. &lt;strong&gt;After:&lt;/strong&gt; decision-documentation is delivered at the deciding gate (&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;) and removed from &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, with a class-level gate that fails if any &lt;code dir=&quot;auto&quot;&gt;required&lt;/code&gt; decision-documentation directive is ever scoped back onto implement (directly or transitively); the &lt;code dir=&quot;auto&quot;&gt;Enforcement&lt;/code&gt; levels carry an explicit rank and a structural gate forbids a &lt;code dir=&quot;auto&quot;&gt;reconciles_tension&lt;/code&gt; arbiter ranked below what it arbitrates (the arbiter is promoted to match its operands and is now delivered &lt;em&gt;as&lt;/em&gt; an arbiter, with co-delivered tensions annotated on the bundle); and the approve/accept gates capture real evidence — the approval event carries the reviewer’s &lt;code dir=&quot;auto&quot;&gt;policy_metadata&lt;/code&gt; (tool/profile/model/shell-pid) and a &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;, a first-pass approval auto-authors an &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;review-cycle&lt;/code&gt; carrying a reproduction command, and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; populates &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt; criterion rows from the recorded review evidence (only from a genuine &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; verdict — a stale rejection can never fabricate a pass). Follow-up #3805 tracks the durable resolver fix for the soft-&lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt;-as-&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; modeling that made the transitive leak possible.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;auth status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;auth doctor&lt;/code&gt; no longer hand-roll an all-clear beside contradicting token details.&lt;/strong&gt; A new typed &lt;code dir=&quot;auto&quot;&gt;HealthVerdict&lt;/code&gt; authority derives the headline from a closed &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; state and requires evidence for definite claims. Offline, an expired access token with an unproven refresh chain renders “Cannot verify”; &lt;code dir=&quot;auto&quot;&gt;auth doctor --server&lt;/code&gt; can resolve that same state to a real &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt;, and a present-but-unhealthy session raises F-008 instead of “No problems detected.”&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Auth readiness now evaluates the canonical stored session without leaking storage failures, and lifecycle emission separates local persistence from hosted fan-out.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;TokenManager.session_assessment&lt;/code&gt; records whether evaluation completed, whether the session is usable, and a closed non-empty reason; readiness consumes that assessment instead of treating an unreadable store as a simple logged-out state. Lifecycle artifact phases can now be persisted locally without fan-out, while the existing composed entry point still offers the same persisted envelope to registered hosted adapters. &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt; builds its gate and final result through side-effect-free local outcome objects, so local verification remains authoritative and reporting remains a separate final step.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;HTTPS doctrine bundle fetches now persist ETags separately from pack versions and safely resolve Artifactory &lt;code dir=&quot;auto&quot;&gt;version&lt;/code&gt; metadata.&lt;/strong&gt; Existing &lt;code dir=&quot;auto&quot;&gt;source_type: https&lt;/code&gt; URLs with a valid &lt;code dir=&quot;auto&quot;&gt;/artifactory/&amp;#x3C;repository&gt;/&amp;#x3C;item&gt;&lt;/code&gt; path are recognized automatically; &lt;code dir=&quot;auto&quot;&gt;source_type: artifactory&lt;/code&gt; is also available to enforce that intent. Successful downloads are buffered before one exact-item AQL response co-attests the &lt;code dir=&quot;auto&quot;&gt;version&lt;/code&gt; property and SHA-256, and the checksum must match those exact bytes before extraction or snapshot promotion. Conditional validators are reused only for the same query-free source and an intact local snapshot; query-bearing URLs always fetch unconditionally rather than collapsing distinct resources or persisting signed parameters. A 304 deliberately leaves the prior snapshot and sampled version byte-for-byte unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A checkout-controlled &lt;code dir=&quot;auto&quot;&gt;.kittify/saas-auth.json&lt;/code&gt; carrying only &lt;code dir=&quot;auto&quot;&gt;team_slug&lt;/code&gt; no longer scopes the operator’s stored OAuth session (EXPERIMENTAL-spec-kitty#765).&lt;/strong&gt; Before, with no service token in the environment or auth file, the file could choose the per-request team while &lt;code dir=&quot;auto&quot;&gt;load_auth_context&lt;/code&gt; supplied the personal OAuth bearer and canonical server target. &lt;code dir=&quot;auto&quot;&gt;team_slug&lt;/code&gt; from that file is now honoured only alongside the file’s own &lt;code dir=&quot;auto&quot;&gt;token&lt;/code&gt;; set &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_TEAM_SLUG&lt;/code&gt; to choose a team for an OAuth-backed session.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ZeitgeistClient.offer()&lt;/code&gt; now posts presence/focus/session control envelopes to a real relay’s &lt;code dir=&quot;auto&quot;&gt;/managed/control&lt;/code&gt; endpoint with the headers it actually requires, instead of a route that always rejected them (&lt;code dir=&quot;auto&quot;&gt;FIX-M2-10&lt;/code&gt;).&lt;/strong&gt; Every &lt;code dir=&quot;auto&quot;&gt;offer()&lt;/code&gt; call — &lt;code dir=&quot;auto&quot;&gt;presence()&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;focus_start/heartbeat/pause/end()&lt;/code&gt; — was POSTing its &lt;code dir=&quot;auto&quot;&gt;{op, request_id, args}&lt;/code&gt; envelope to &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;relay_url&gt;/events&lt;/code&gt;, the baseline Beacon-shaped route (&lt;code dir=&quot;auto&quot;&gt;zeitgeist/server.py&lt;/code&gt;), which has no &lt;code dir=&quot;auto&quot;&gt;op&lt;/code&gt; dispatch of any kind and structurally cannot process it; against a real, correctly-configured relay this was a 422 on every single call, discovered by &lt;code dir=&quot;auto&quot;&gt;DQA-M2-02&lt;/code&gt;’s Docker-local suite. &lt;code dir=&quot;auto&quot;&gt;offer()&lt;/code&gt; now targets &lt;code dir=&quot;auto&quot;&gt;/managed/control&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;zeitgeist/managed.py&lt;/code&gt;’s real presence/focus/session op dispatcher), includes the &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; field &lt;code dir=&quot;auto&quot;&gt;managed_control.schema.json&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;ControlEnvelope&lt;/code&gt; requires, and sends both gates a real relay enforces on that route: &lt;code dir=&quot;auto&quot;&gt;Authorization: Bearer &amp;#x3C;token&gt;&lt;/code&gt; (the outer, unconditional &lt;code dir=&quot;auto&quot;&gt;AuthenticationMiddleware&lt;/code&gt; gate every route but &lt;code dir=&quot;auto&quot;&gt;/health&lt;/code&gt; sits behind) and &lt;code dir=&quot;auto&quot;&gt;X-Zeitgeist-Capability: &amp;#x3C;token&gt;&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;managed.py&lt;/code&gt;’s own capability check, verified against a separate secret). Both headers carry the same single credential &lt;code dir=&quot;auto&quot;&gt;credentials.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;checkout&lt;/code&gt; flow already stores per repo — the same value &lt;code dir=&quot;auto&quot;&gt;subscription.py&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;operability.py&lt;/code&gt;’s already-landed callers already forward as the capability header — rather than introducing a second stored secret. Covered by a new protocol-faithful local double (&lt;code dir=&quot;auto&quot;&gt;tests/zeitgeist_client/conftest.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;ManagedControlDouble&lt;/code&gt;, mirroring &lt;code dir=&quot;auto&quot;&gt;managed_auth.SharedSecretCapabilityVerifier&lt;/code&gt;’s real HMAC wire shape and kind-scoped capability grants) in addition to the existing recording double.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;FilteredStream.watch()&lt;/code&gt; now sends &lt;code dir=&quot;auto&quot;&gt;Authorization: Bearer &amp;#x3C;token&gt;&lt;/code&gt; on its &lt;code dir=&quot;auto&quot;&gt;GET /managed/stream&lt;/code&gt; connection, not just &lt;code dir=&quot;auto&quot;&gt;X-Zeitgeist-Capability&lt;/code&gt; — the same header-omission class &lt;code dir=&quot;auto&quot;&gt;FIX-M2-10&lt;/code&gt; fixed for &lt;code dir=&quot;auto&quot;&gt;offer()&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;POST /managed/control&lt;/code&gt; path, discovered from that bead’s own &lt;code dir=&quot;auto&quot;&gt;HANDOFF.json&lt;/code&gt; open issues (&lt;code dir=&quot;auto&quot;&gt;FIX-M2-13&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;GET /managed/stream&lt;/code&gt; sits behind the SAME outer, unconditional &lt;code dir=&quot;auto&quot;&gt;AuthenticationMiddleware&lt;/code&gt; gate every route but &lt;code dir=&quot;auto&quot;&gt;/health&lt;/code&gt; sits behind (&lt;code dir=&quot;auto&quot;&gt;zeitgeist/auth.py&lt;/code&gt;, checked before &lt;code dir=&quot;auto&quot;&gt;managed.py&lt;/code&gt;’s own handler ever runs); sending only the capability header — the pre-fix behaviour — meant a real relay answered every &lt;code dir=&quot;auto&quot;&gt;watch()&lt;/code&gt; connection attempt 401, regardless of whether the capability credential itself was valid. Both headers now carry the same single stored credential (&lt;code dir=&quot;auto&quot;&gt;TeamStreamConfig.capability_credential&lt;/code&gt;, sourced from &lt;code dir=&quot;auto&quot;&gt;credentials.py&lt;/code&gt; via &lt;code dir=&quot;auto&quot;&gt;subscription.resolve_stream&lt;/code&gt; exactly as before), the identical “one credential, two headers” model &lt;code dir=&quot;auto&quot;&gt;transport.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;offer()&lt;/code&gt; already uses. Reconnect/backoff behaviour and &lt;code dir=&quot;auto&quot;&gt;TeamStreamConfig&lt;/code&gt;’s shape are unchanged. Covered by a new protocol-faithful local double for &lt;code dir=&quot;auto&quot;&gt;GET /managed/stream&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;tests/zeitgeist_client/conftest.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;ManagedStreamAuthDouble&lt;/code&gt;, enforcing the same two real gates in the same order/401-vs-403 split &lt;code dir=&quot;auto&quot;&gt;managed.py&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;managed_auth.py&lt;/code&gt; do) and a real &lt;code dir=&quot;auto&quot;&gt;dkr-m1-02-zeitgeist:contract&lt;/code&gt; container contract test proving a genuine frame is received when authorized and a wrong credential is genuinely, fail-closed 401’d.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The bundled Zeitgeist client now carries TWO independent credentials — a shared relay bearer and a per-actor capability JWT — instead of one value doing double duty for both &lt;code dir=&quot;auto&quot;&gt;Authorization&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;X-Zeitgeist-Capability&lt;/code&gt;, so the real CLI can finally publish presence/watch a REAL SaaS-provisioned per-team relay (&lt;code dir=&quot;auto&quot;&gt;FIX-M2-15&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;FIX-M2-10&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FIX-M2-13&lt;/code&gt;’s “one credential, two headers” fix only ever worked against a relay whose &lt;code dir=&quot;auto&quot;&gt;ZEITGEIST_TOKEN&lt;/code&gt; happened to equal the capability JWT presented — exactly how their own test suites (and a self-hosted, single-secret deployment) set things up, but NOT how &lt;code dir=&quot;auto&quot;&gt;spec-kitty-saas&lt;/code&gt; provisions a real per-team relay (&lt;code dir=&quot;auto&quot;&gt;apps.live_capability.provisioning_docker&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;ZEITGEIST_TOKEN&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;ZEITGEIST_CAPABILITY_KEY&lt;/code&gt; are two independently random secrets). &lt;code dir=&quot;auto&quot;&gt;DQA-M2-05&lt;/code&gt;’s real-container walkthrough reproduced this by hand: a capability JWT presented as &lt;code dir=&quot;auto&quot;&gt;Authorization&lt;/code&gt; gets a real &lt;code dir=&quot;auto&quot;&gt;401&lt;/code&gt;; the shared token presented as &lt;code dir=&quot;auto&quot;&gt;X-Zeitgeist-Capability&lt;/code&gt; gets a real &lt;code dir=&quot;auto&quot;&gt;403&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;transport.ClientConfig&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;capability_credential&lt;/code&gt; (optional, &lt;code dir=&quot;auto&quot;&gt;X-Zeitgeist-Capability&lt;/code&gt;) alongside its existing &lt;code dir=&quot;auto&quot;&gt;token&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;Authorization&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;filtered_stream.TeamStreamConfig&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;relay_token&lt;/code&gt; (optional, &lt;code dir=&quot;auto&quot;&gt;Authorization&lt;/code&gt;) alongside its existing &lt;code dir=&quot;auto&quot;&gt;capability_credential&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;X-Zeitgeist-Capability&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;credentials.py&lt;/code&gt;’s on-disk &lt;code dir=&quot;auto&quot;&gt;StoredCredential&lt;/code&gt; gains the identically-optional &lt;code dir=&quot;auto&quot;&gt;capability_credential&lt;/code&gt; field, threaded through by &lt;code dir=&quot;auto&quot;&gt;subscription.resolve_stream&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;cli/commands/zeitgeist.py&lt;/code&gt;’s operability probe client. &lt;strong&gt;Backward compatible by construction&lt;/strong&gt;: whichever new field is left at its &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; default, both headers fall back to the ONE configured value — every config/checkout written before this fix, and every self-hosted single-secret deployment, keeps working unchanged. &lt;code dir=&quot;auto&quot;&gt;spec-kitty-saas&lt;/code&gt; gained a new member-facing credential-issuance endpoint (&lt;code dir=&quot;auto&quot;&gt;apps.live_capability.views.mint_cli_credential&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;POST /api/v1/live/capability/cli/&lt;/code&gt;) returning &lt;code dir=&quot;auto&quot;&gt;relay_url&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;relay_token&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;capability_credential&lt;/code&gt; together — the shape a real team member’s CLI checkout now needs, closing the gap &lt;code dir=&quot;auto&quot;&gt;mint_actor_capability_tokens_probe.py&lt;/code&gt;’s ORM-bypass previously had to work around. Proven by new regression-pin unit tests against both fixed-secret local doubles (mirroring the exact &lt;code dir=&quot;auto&quot;&gt;_kinded_client&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;_authed_config&lt;/code&gt; shape those beads’ own tests used, but now with the double’s &lt;code dir=&quot;auto&quot;&gt;shared_token&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;capability_key&lt;/code&gt; genuinely different, never equal) AND a new real-container contract test (&lt;code dir=&quot;auto&quot;&gt;tests/zeitgeist_client/test_managed_relay_docker_local.py&lt;/code&gt;, own &lt;code dir=&quot;auto&quot;&gt;zg-fix15-*&lt;/code&gt; network/container/volume against the same &lt;code dir=&quot;auto&quot;&gt;dkr-m1-02-zeitgeist:contract&lt;/code&gt; image, provisioned exactly like &lt;code dir=&quot;auto&quot;&gt;spec-kitty-saas&lt;/code&gt;’s own driver) showing the real, unmodified &lt;code dir=&quot;auto&quot;&gt;offer()&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;watch()&lt;/code&gt; reach &lt;code dir=&quot;auto&quot;&gt;202&lt;/code&gt;/receive a real frame with two independent secrets, while the old single-credential shape genuinely, fail-closed 401s/403s against that same relay.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --cascade&lt;/code&gt; now follows an org-pack dependency edge no
matter which pack in the chain declares it, and activating from an org pack
that ships no dependency graph no longer crashes the command (&lt;code dir=&quot;auto&quot;&gt;#3534&lt;/code&gt;; closes
&lt;code dir=&quot;auto&quot;&gt;#3527&lt;/code&gt;).&lt;/strong&gt; Before, cascade activation, &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt;, and dossier
rebaseline each saw only the first configured org pack — a &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;
edge into or out of any second-or-later pack was silently ignored, so
&lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt; under-activated whenever doctrine lived across more than one org
pack. Now the full declaration-ordered org-pack chain is threaded through all
three, so an edge cascades regardless of which pack authored it. As part of
landing, activating a directive or profile from an org pack that carries
doctrine artifacts but no root-level DRG graph now degrades that pack to “no
DRG layer” and activates normally, instead of aborting with &lt;code dir=&quot;auto&quot;&gt;DRGLoadError: No DRG graph files found&lt;/code&gt; — each configured pack is handled on its own, so one
graphless pack no longer takes a healthy sibling down with it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Rejecting a work package no longer costs a wasted cycle: the feedback-file
path &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; prints in its rejection command is now one
&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; will actually accept (&lt;code dir=&quot;auto&quot;&gt;#3554&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3430&lt;/code&gt;).&lt;/strong&gt; Before, the
review prompt told the reviewer to write feedback to
&lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;wp&gt;/review-cycle-N.md&lt;/code&gt; and then pass that same file to &lt;code dir=&quot;auto&quot;&gt;move-task --review-feedback-file&lt;/code&gt; — but inside the WP’s own directory that exact
filename is the tool-authored verdict artifact, which the provenance guard
refuses as a feedback source. So the rejection command printed verbatim always
failed, and the reviewer only discovered it after burning a cycle. The
advertised path is now &lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;wp&gt;/review-feedback-N.md&lt;/code&gt; — still committed in
the WP’s own in-repo directory — and the name is owned in &lt;code dir=&quot;auto&quot;&gt;review/cycle.py&lt;/code&gt;
beside the guard that decides what is acceptable, so the printed path and the
accepted path cannot drift apart again.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The two &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; lane guards no longer disagree about a bulk-edit
mission’s own occurrence map, so it can be kept current from the implementing
lane without a manual unwind (&lt;code dir=&quot;auto&quot;&gt;#2980&lt;/code&gt;).&lt;/strong&gt; The pre-commit ownership guard warned
(and let the commit through) while &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; blocked the later transition,
so &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/occurrence_map.yaml&lt;/code&gt; — which DIRECTIVE_035 requires
the lane to update as the sweep proceeds — tripped the gate after the work was
committed. The exception is now expressed once (&lt;code dir=&quot;auto&quot;&gt;is_occurrence_map_path&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;core.constants&lt;/code&gt;) and honored by both guards: the map is permitted on the lane
at both, while every other &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; path stays governed (a sibling
&lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; on the lane is still blocked). The commit-guard &lt;code dir=&quot;auto&quot;&gt;mode&lt;/code&gt; semantics for
non-exception paths are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The lane “no kitty-specs on lane branches” &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; guard no longer
false-positives on inherited planning artifacts in &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; topology, so lane
transitions stop demanding &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; on every step (&lt;code dir=&quot;auto&quot;&gt;#3271&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#2274&lt;/code&gt;).&lt;/strong&gt;
The guard is a two-pass content delta (the shipped &lt;code dir=&quot;auto&quot;&gt;#2274&lt;/code&gt;/FR-007 fix), but
both passes keyed off the lane’s coordination/mission base ref, whose
merge-base predates the &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**&lt;/code&gt; a lane legitimately holds — prior
missions’ committed artifacts inherited from the base, plus this mission’s own
planning artifacts merged in via the recorded planning commit (ADR
&lt;code dir=&quot;auto&quot;&gt;2026-07-29-1&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#2993&lt;/code&gt;). Both are ancestors of the planning branch but not of
the coord base, so they surfaced as lane-introduced contamination and the
guard’s own “clean the branch” remedy would have deleted other missions’
artifacts — leaving &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;, documented as “not recommended”, as the only
safe path. The delta is now measured against the planning branch
(&lt;code dir=&quot;auto&quot;&gt;planning_base_branch&lt;/code&gt;, else the mission’s &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;), falling back to
the lane base ref only for legacy/flat missions without &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;. The
sibling branch-currency and implementation-commit gates keep the coordination
ref, which is correct for them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Three architectural-gate tolls that only ever fired in CI, on legitimate
additive change, are gone (mission &lt;code dir=&quot;auto&quot;&gt;frozen-baseline-toll-reduction&lt;/code&gt;; closes
&lt;code dir=&quot;auto&quot;&gt;#2853&lt;/code&gt;).&lt;/strong&gt; For a developer working in this repo: editing the body of an
allowlisted still-dead symbol no longer forces a hand-edited “rehashed WPxx”
baseline — a new fail-closed helper
(&lt;code dir=&quot;auto&quot;&gt;tests/architectural/_refresh_dead_symbol_hashes.py&lt;/code&gt;) refreshes the
&lt;code dir=&quot;auto&quot;&gt;body_hash&lt;/code&gt; for you and is structurally incapable of admitting a &lt;em&gt;new&lt;/em&gt; dead
symbol (it iterates the existing allowlist only and refuses on an
unrecoverable or ambiguous &lt;code dir=&quot;auto&quot;&gt;module_path&lt;/code&gt;, proven by a non-fakeable
regression). Adding a migration no longer needs a baseline bump: the
&lt;code dir=&quot;auto&quot;&gt;category_1_auto_discovered_migrations&lt;/code&gt; count now derives from the frozenset
authority in both loop arms, so the 105→107 file drift that a hard-pinned
count would red on passes clean. And a legitimate new skip no longer
hard-fails CI — &lt;code dir=&quot;auto&quot;&gt;skip_marker_blocks&lt;/code&gt; growth is now reviewable-with-teeth
(asserted via &lt;code dir=&quot;auto&quot;&gt;record_property&lt;/code&gt;, with the mandatory co-located skip-reason
line as the review signal) instead of a wall. Also drained the inert
&lt;code dir=&quot;auto&quot;&gt;test_no_dead_symbols&lt;/code&gt; baseline key (closing a silent re-entry hole) and
fast-marked the two sub-second gates for local pre-push runs. Every
load-bearing gate is untouched — P0-security boundaries, still-shrinking
burn-downs, zero-pins, and change-detectors all stay frozen behind the C-001
do-not-touch fence; 108 gates green, ruff + mypy &lt;code dir=&quot;auto&quot;&gt;--strict&lt;/code&gt; clean. Test
infrastructure only, no runtime or user-facing change (no version bump).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; no longer rejects a &lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; work package that
owns its &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; deliverables, so a decision checkpoint, freeze/measurement
snapshot, or bulk-edit occurrence map can be a first-class WP (mission
&lt;code dir=&quot;auto&quot;&gt;planning-artifact-kitty-specs-ownership&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3222&lt;/code&gt; and its repro &lt;code dir=&quot;auto&quot;&gt;#2643&lt;/code&gt;).&lt;/strong&gt;
The ownership model already blessed &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; ownership for
&lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;ownership.validation._PLANNING_PREFIXES&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;validate_execution_mode_consistency&lt;/code&gt;) and the lane layer already routes such
WPs to the repo-root planning lane — only the &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; ban disagreed,
rejecting any &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; owned file unconditionally (a later over-reach whose
own rationale was scoped to &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; lane branches). The ban is now
execution-mode-aware: it exempts a &lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; WP whose &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;
are &lt;strong&gt;all&lt;/strong&gt; confined to the planning surfaces (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt;), and
stays fail-closed for &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; and for any WP that also owns code — so a
mislabelled planning WP cannot become a backdoor to owning &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;. Planning-
artifact WPs never reach a lane branch, so the lane commit-guard and move-task
hygiene guards are unaffected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A spec that writes some requirements as plain prose sentences no longer
passes the coverage gate as if they were covered — &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 and name the uncounted ids (mission
&lt;code dir=&quot;auto&quot;&gt;bare-prose-requirements-uncounted&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3396&lt;/code&gt;).&lt;/strong&gt; When a spec declared
some requirements in a recognised shape (a table row, heading, bullet, or
bold-led paragraph) and wrote others as bare sentences, the plain ones were
silently mapped to nothing while both commands reported full coverage. Now
&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; refuses to advance past the tasks boundary and
&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; exits non-zero, each listing the bare-prose requirement ids;
&lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; surfaces them in its JSON (&lt;code dir=&quot;auto&quot;&gt;bare_prose_requirement_ids&lt;/code&gt;)
without gating, since it registers mappings rather than advancing. The
detector was measured against all 368 real &lt;code dir=&quot;auto&quot;&gt;kitty-specs/*/spec.md&lt;/code&gt; files — 1
flagged (0.27%), zero true positives — and that figure is frozen into a
shrink-only CI ratchet.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A mission whose &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; recorded &lt;code dir=&quot;auto&quot;&gt;target_branch: &quot;main&quot;&lt;/code&gt; no longer
wedges permanently at &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, and the &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt; escape
hatch now actually rescues it (&lt;code dir=&quot;auto&quot;&gt;#3482&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3466&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;specify --topology single_branch&lt;/code&gt; run from a checkout on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; writes
&lt;code dir=&quot;auto&quot;&gt;target_branch: &quot;main&quot;&lt;/code&gt;; finalize-tasks then resolved its WP-status
bookkeeping destination from that literal field, tripped the protected-branch
guard, and refused with &lt;code dir=&quot;auto&quot;&gt;PROTECTED_BRANCH_REFUSED&lt;/code&gt; — and passing
&lt;code dir=&quot;auto&quot;&gt;--target-branch &amp;#x3C;feature&gt;&lt;/code&gt; produced a byte-identical refusal still naming
&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, because the override never reached that consumer. There was no
sanctioned way out (no retarget migration, hand-editing &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is
prohibited). The override now persists into the canonical &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;
field before the commit pipeline, so every consumer converges on it and the
mission finalizes; a failed persist is reported to &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; callers instead
of silently returning false.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;retrospect synthesize&lt;/code&gt; now tells you the one thing that is actually
wrong with a retrospective instead of burying it under ~100 errors about a
schema the file was never meant to satisfy (&lt;code dir=&quot;auto&quot;&gt;#3537&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3533&lt;/code&gt;).&lt;/strong&gt; When
a hand-edited retrospective had a single invalid finding category, the
command printed a wall of Pydantic &lt;code dir=&quot;auto&quot;&gt;extra_forbidden&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;Field required&lt;/code&gt;
errors describing the nested reader’s schema — twice leading readers to
believe the tool contradicted itself when one enum value was wrong. It now
reports the generator reader’s accurate one-line diagnosis (e.g.
&lt;code dir=&quot;auto&quot;&gt;not_helpful[0].category is invalid&lt;/code&gt;) and appends the categories that field
actually allows — findings and proposals draw from different sets — so the
fix is obvious instead of a guess.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Writing an honest cardinality assertion in a test no longer costs you an
annotation toll: the golden-count architectural gate
(&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_golden_count_ban.py&lt;/code&gt;) stopped flagging
dynamic-result &lt;code dir=&quot;auto&quot;&gt;len(x) == N&lt;/code&gt; checks (mission
&lt;code dir=&quot;auto&quot;&gt;test-friction-ratchet-remediation&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3458&lt;/code&gt;).&lt;/strong&gt; Before, an ambiguous
&lt;code dir=&quot;auto&quot;&gt;len(result) == 3&lt;/code&gt; over a runtime-computed collection defaulted to &lt;code dir=&quot;auto&quot;&gt;convert&lt;/code&gt;,
so authors had to add &lt;code dir=&quot;auto&quot;&gt;# golden-count: cardinality-is-contract&lt;/code&gt; just to quiet
the gate — on PR #3456 that toll fired twice for zero real catches. The
classifier now treats an ambiguous dynamic-result count as &lt;code dir=&quot;auto&quot;&gt;keep&lt;/code&gt;, so genuine
cardinality asserts pass untouched. The gate’s real job is preserved:
enumerable-domain golden counts like &lt;code dir=&quot;auto&quot;&gt;len(Lane) == 10&lt;/code&gt;, which silently drift
when the domain grows, still convert. Companion guard added in the same slice:
a new CT7 recurrence check (&lt;code dir=&quot;auto&quot;&gt;test_ratchet_positional_anchor_ban.py&lt;/code&gt;) bans
reintroducing raw &lt;code dir=&quot;auto&quot;&gt;(&quot;file.py&quot;, &amp;#x3C;int&gt;)&lt;/code&gt; 2-tuple ratchet keys in
ratchet-substrate-importing seed containers, so the file:line-drift friction
engine cannot regrow. Dev-facing only — no runtime or user-visible behaviour
changes. (Also folds 12 dangling references to the retired
&lt;code dir=&quot;auto&quot;&gt;test_bridge_compat_surface.py&lt;/code&gt; across 9 files — campsite cleanup of the
already-landed #3285 deletion; refs &lt;code dir=&quot;auto&quot;&gt;#2853&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3285&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2633&lt;/code&gt;.)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A mission running under a non–software-dev workflow no longer gets blocked
by a guard about objects its workflow does not have — for example a &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;
mission’s &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; step demanding “Not all work packages are approved or done”
when a &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission has no work packages at all (mission
&lt;code dir=&quot;auto&quot;&gt;mission-type-guard-registry&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3402&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3386&lt;/code&gt;).&lt;/strong&gt; Before, runtime guard
dispatch branched explicitly on the &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt; mission
families and then silently fell through to the software-dev guard table for
everything else — including &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; and any unregistered mission type — so a
mission could be held back by a guard about artifacts it can never possess,
with nothing explaining why. Now guard dispatch is an explicit registry keyed
by mission family: &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; has its own guard table authored from its real state
machine, and an unregistered family fails loudly on the legacy path and
degrades to an explicit, logged neutral result on the composed extension path
— instead of inheriting the wrong rules by accident.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An organisation doctrine pack you registered, validated, and activated
delivered none of its step contracts, artifact requirements, or graph nodes to
&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; at runtime — it does now (&lt;code dir=&quot;auto&quot;&gt;#3520&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3516&lt;/code&gt;).&lt;/strong&gt; Before, the
runtime consumers (the step-contract executor and its review gate bindings, the
mission-type governance profile, runtime dispatch, and mission-load validation)
all resolved doctrine from the built-in pack plus the project tier only — they
had the org-tier parameter but the callers never passed it, so an org pack was
silently inert past activation. Now a shared &lt;code dir=&quot;auto&quot;&gt;resolve_org_dirs&lt;/code&gt; helper threads
the org tier through each of them; an org &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt; overrides the
governance artifact slot &lt;strong&gt;and&lt;/strong&gt; the dossier completeness index (so an
org-mandated artifact is actually enforced by the missing-artifact detector); and
a configured-but-broken org pack warns (a dropped path or a malformed manifest)
instead of failing silently. &lt;strong&gt;A chain of multiple org packs now works too&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;#3525&lt;/code&gt;): before, the DRG graph merged only the first org pack, so a second
pack’s step contracts loaded but their &lt;code dir=&quot;auto&quot;&gt;delegates_to&lt;/code&gt;/graph edges silently did
not resolve — the runtime now merges the full declared chain in order (later
pack wins on collision, matching the doctrine overlay), and a malformed pack in
the chain is dropped on its own without erasing the others. Projects with no org
pack are unaffected — every path is byte-identical without one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME&lt;/code&gt; pin census (&lt;code dir=&quot;auto&quot;&gt;arch-adversarial (arch_shard_3)&lt;/code&gt;) was red
on main because a legitimate new isolation pin (&lt;code dir=&quot;auto&quot;&gt;#3497&lt;/code&gt;) landed after the R1a
freeze, and the “shrink-only” ratchet — as landed — could not actually shrink
(&lt;code dir=&quot;auto&quot;&gt;#3509&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;).&lt;/strong&gt; The acute red is fixed by the design-sanctioned owner
adoption (the drifting test requests the exempt &lt;code dir=&quot;auto&quot;&gt;canonical_home&lt;/code&gt; fixture and
drops its own &lt;code dir=&quot;auto&quot;&gt;setenv&lt;/code&gt;), with no edit to any frozen artefact. Beyond that, R1b’s
tombstone burn-down is now wired end to end: &lt;code dir=&quot;auto&quot;&gt;t023&lt;/code&gt; subtracts the tombstoned
set from the anchor, and the production regeneration command
(&lt;code dir=&quot;auto&quot;&gt;_home_pin_scan.render_baseline&lt;/code&gt;) emits tombstones from a new auditable
manifest (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/census/spec_kitty_home_pin_tombstones.yaml&lt;/code&gt;) and
freezes the key-set hash over &lt;code dir=&quot;auto&quot;&gt;census ∪ tombstones&lt;/code&gt;. Regeneration fails closed
if a tombstoned member’s pin is still in the tree, and the ratchet still bites
(a spurious pin reds; a tombstone over a live pin reds). On that seam the
provable class was converged onto the canonical owner — census &lt;code dir=&quot;auto&quot;&gt;40 → 26&lt;/code&gt; — with
the ~23 genuinely-different seams documented out of scope (&lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;’s confirmed
thesis: a name collision, not a duplicated seam). The subsystem is a no-op while
the manifest is empty (committed artefacts byte-identical). The same convergence
also greens a second, separate gate — limb (g) of the §0.9 &lt;code dir=&quot;auto&quot;&gt;_home_pin_gate&lt;/code&gt;
verdict oracle (&lt;code dir=&quot;auto&quot;&gt;arch-adversarial (arch_shard_2)&lt;/code&gt;), which recomputes the
published end-SHA sites against the tree — by teaching it the same tombstone
term: a converged member’s site is excused only when it is in the manifest, and
the anti-vacuity floor now counts keys that recompute &lt;em&gt;live&lt;/em&gt; so the gate can’t be
bought off by tombstoning the population away.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Machines that never ran the layout migration silently captured zero sync
events while reporting success — now they capture for real (&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; Before, an un-migrated machine defaulted to a legacy capture
layout where live event/body writes were refused deep in the stack and
swallowed — a &lt;strong&gt;silent zero-capture&lt;/strong&gt; that never surfaced to the operator. A
&lt;code dir=&quot;auto&quot;&gt;#3293&lt;/code&gt; regression compounded this by also refusing authenticated hosts
entirely. Now a fresh root resolves to project-only capture &lt;em&gt;before&lt;/em&gt; any
legacy persist; a legacy-with-data root auto-migrates through the canonical
&lt;code dir=&quot;auto&quot;&gt;migrate_journal&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;project_store_migration&lt;/code&gt; engines under a deterministic,
crash-safe migration id (re-entry never bricks the root); the live emit path
completes its cutover via a resolve-before-unit-of-work seam so both emitter
swallow sites are observable instead of silent (never-raises contract kept
intact); and credential parsing is restored as a pure auth signal (never a
physical-store selector), so an already-authenticated host stops being
refused.&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;/&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; no longer block on a fully-absent or legacy
&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;-only charter — both are now advisory, matching &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;’s
existing tolerance (&lt;code dir=&quot;auto&quot;&gt;#3498&lt;/code&gt;).&lt;/strong&gt; The shared preflight hook
(&lt;code dir=&quot;auto&quot;&gt;run_preflight_or_abort&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;charter_runtime/preflight/hook.py&lt;/code&gt;) never
forwarded &lt;code dir=&quot;auto&quot;&gt;allow_missing_charter=True&lt;/code&gt; to the runner, so a brand-new project
with no &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/&lt;/code&gt; contents at all, or a pre-inversion project
carrying only &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; absent, #2831’s
shape), hard-blocked &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; even though the dashboard already
tolerated both states. &lt;code dir=&quot;auto&quot;&gt;run_charter_preflight()&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;charter_runtime/preflight/runner.py&lt;/code&gt;) gains a new &lt;code dir=&quot;auto&quot;&gt;_is_legacy_charter_bundle&lt;/code&gt;
wording selector and a distinct, more detailed warning constant for the
legacy-bundle case. Canonical layer state alone decides the exemption:
source and synced bundle must be &lt;code dir=&quot;auto&quot;&gt;missing&lt;/code&gt;, and synthesized DRG must be
&lt;code dir=&quot;auto&quot;&gt;missing&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;built_in_only&lt;/code&gt;; display-only &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; only selects warning
copy after that decision. Stale, invalid, or other partial residue therefore
keeps blocking even when &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; exists. Advancing/query and human/JSON
&lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; modes plus &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; emit the advisory to stderr without polluting
JSON stdout; dashboard persists/renders it. The canonical &lt;code dir=&quot;auto&quot;&gt;CHARTER_MD&lt;/code&gt; import
stays lazy so &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; does not pull the heavyweight charter graph at startup.
The legacy warning
names the executable migration command explicitly:
&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate --no-from-interview&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A reviewer running a different agent profile than the implementer can now
claim a completed work package for review — the false “WP already claimed for
review by &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;implementer&gt;&lt;/code&gt;” refusal is gone (&lt;code dir=&quot;auto&quot;&gt;#3455&lt;/code&gt;).&lt;/strong&gt; Before, claiming a WP
for review (&lt;code dir=&quot;auto&quot;&gt;for_review → in_review&lt;/code&gt;) compared the claim holder’s identity,
which at &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; is structurally the &lt;em&gt;implementer&lt;/em&gt; — so any cross-profile
reviewer (e.g. &lt;code dir=&quot;auto&quot;&gt;reviewer-renata&lt;/code&gt; reviewing &lt;code dir=&quot;auto&quot;&gt;python-pedro&lt;/code&gt;’s work) was rejected
as a self-review collision, and the block surfaced on the status aggregate
seam rather than the &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; command. Now the &lt;code dir=&quot;auto&quot;&gt;for_review → in_review&lt;/code&gt; edge
is allow-only, and a genuine reviewer-vs-reviewer collision is decided by a
single pure predicate at the &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; re-claim site (a real second reviewer
is still blocked, and the message names the holder). Role is read from the
reduced status slot, never by splitting the compact actor string (&lt;code dir=&quot;auto&quot;&gt;#2861&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coord/primary partition-authority residuals: out-of-loop callers now resolve
the correct partition surface, so coordination-topology missions stop deadlocking
and mis-reporting (mission &lt;code dir=&quot;auto&quot;&gt;partition-authority-residuals-01M021K9&lt;/code&gt;; epics &lt;code dir=&quot;auto&quot;&gt;#2160&lt;/code&gt;
/ &lt;code dir=&quot;auto&quot;&gt;#2720&lt;/code&gt;).&lt;/strong&gt; Under coordination topology a cluster of out-of-loop and
cross-function callers still read PRIMARY-partition artifacts off the &lt;code dir=&quot;auto&quot;&gt;-coord&lt;/code&gt;
husk, or wrote lifecycle evidence to the wrong partition — degrading silently or
&lt;strong&gt;deadlocking &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt;&lt;/strong&gt;. Eleven fixes, each a caller reroute through
the canonical &lt;code dir=&quot;auto&quot;&gt;mission_runtime.artifacts&lt;/code&gt; placement seam (STATUS reads stay on
COORD): the coord &lt;strong&gt;merge deadlock&lt;/strong&gt; is gone — the review-override write now lands
on the surface the merge gate reads, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; gains a
&lt;code dir=&quot;auto&quot;&gt;--skip-review-artifact-check&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; escape hatch that records the bypass as
durable override evidence (&lt;code dir=&quot;auto&quot;&gt;#2959&lt;/code&gt;); merge risk/dependency gates and the bulk-edit
diff base stop silently SKIPping / seeing an empty graph on coord missions
(&lt;code dir=&quot;auto&quot;&gt;#3439&lt;/code&gt;); the review handoff renders true per-WP lanes instead of a blanket stale
&lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#2698&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; commits its post-transition annotation atomically,
leaving a clean status tree (&lt;code dir=&quot;auto&quot;&gt;#2939&lt;/code&gt;); the 4th safe-commit target resolves through
the shared degrade helper with refusal-parity preserved (&lt;code dir=&quot;auto&quot;&gt;#2966&lt;/code&gt;); and
&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; versions &lt;code dir=&quot;auto&quot;&gt;wps.yaml&lt;/code&gt; so a finalized checkpoint reproduces its own
state (&lt;code dir=&quot;auto&quot;&gt;#2937&lt;/code&gt;). Diagnostic-output fidelity (&lt;code dir=&quot;auto&quot;&gt;#2720&lt;/code&gt;): &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt;
sources its inventory from canonical mission writer metadata (&lt;code dir=&quot;auto&quot;&gt;#2692&lt;/code&gt;); mission
doctors validate &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; against the writer schema — killing false
&lt;code dir=&quot;auto&quot;&gt;UNKNOWN_SHAPE&lt;/code&gt; findings — and &lt;code dir=&quot;auto&quot;&gt;doctor coordination&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; scoping
(&lt;code dir=&quot;auto&quot;&gt;#2696&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;retrospect summary&lt;/code&gt; discovers missions under the canonical
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/*&lt;/code&gt; root (&lt;code dir=&quot;auto&quot;&gt;#2717&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;status doctor&lt;/code&gt; no longer reports Healthy over
blanked runtime attribution (&lt;code dir=&quot;auto&quot;&gt;#2960&lt;/code&gt;); and mission-state repair stops quarantining
legacy &lt;code dir=&quot;auto&quot;&gt;WPStatusChanged&lt;/code&gt; lane transitions into a zero-WP &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3066&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Review rejections now reach the hosted dashboard instead of being silently
dropped by sync (&lt;code dir=&quot;auto&quot;&gt;#3307&lt;/code&gt; P0; &lt;code dir=&quot;auto&quot;&gt;#3444&lt;/code&gt;).&lt;/strong&gt; Before, when a reviewer sent a work
package back for rework — any backward review-rejection move (&lt;code dir=&quot;auto&quot;&gt;* → planned&lt;/code&gt;,
or &lt;code dir=&quot;auto&quot;&gt;in_review → in_progress&lt;/code&gt;) — the CLI stamped the status event &lt;code dir=&quot;auto&quot;&gt;force=False&lt;/code&gt;
and, for &lt;code dir=&quot;auto&quot;&gt;in_review → in_progress&lt;/code&gt;, left off the &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;. Those events
were accepted on your machine but violated the shared &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; wire
contract the hosted ingestion endpoint enforces, so hosted sync silently
rejected them: a rejection that looked applied locally never propagated to the
team dashboard (in the reported case a whole batch surfaced 11+ days later as
bulk sync failures). Root cause was two same-named &lt;code dir=&quot;auto&quot;&gt;validate_transition&lt;/code&gt;
functions giving opposite answers — the emit path consulted only the
CLI-local state machine, never the wire contract the server enforces. The
emit-force decision now gates on &lt;strong&gt;both&lt;/strong&gt;, so the review-rejection family
emits &lt;code dir=&quot;auto&quot;&gt;force=True&lt;/code&gt; (still carrying the structured rewind rationale) and threads
the &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; on the wire, producing events the project’s own vendored
contract accepts. Reviewers are now told — at the &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; tool surface and
in the review skills — that a rejection rationale (&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;) is mandatory, because it travels on the wire as that &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coordination-topology missions no longer wedge lane allocation by
committing PRIMARY planning artifacts onto the coordination branch (mission
&lt;code dir=&quot;auto&quot;&gt;write-path-integrity-01KZZD69&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3371&lt;/code&gt; P0, &lt;code dir=&quot;auto&quot;&gt;#2549&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3128&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3373&lt;/code&gt;;
advances &lt;code dir=&quot;auto&quot;&gt;#2160&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#1878&lt;/code&gt;).&lt;/strong&gt; Before, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s planning auto-commit routed
the whole batch verbatim to the coordination branch under coord topology, so a
PRIMARY &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; landed on coord and the lane allocator’s recorded-planning
merge hit an add/add conflict — blocking every work-package claim on a
PR-bound &lt;code dir=&quot;auto&quot;&gt;--start-branch&lt;/code&gt; + coord mission with no self-service recovery. Root
cause was one layer deeper than the commit site: &lt;code dir=&quot;auto&quot;&gt;BookkeepingTransaction.acquire&lt;/code&gt;
&lt;em&gt;unconditionally&lt;/em&gt; redirected writes to the coordination worktree, so this fix
adds an opt-in &lt;code dir=&quot;auto&quot;&gt;commit_to_primary_target&lt;/code&gt; that PRIMARY planning commits use to
land on the mission’s own target branch (every status/coord caller keeps the
default — zero regression to coord routing). A partition guard at the
planning-commit seam now fails loud on any PRIMARY→coord / COORD→lane
mis-route (excluding self-bookkeeping &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; co-travel), closing the same
class for &lt;code dir=&quot;auto&quot;&gt;move-task --force&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#2549&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s lane-state &lt;strong&gt;read&lt;/strong&gt; now
resolves &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; from that same PRIMARY partition (via the kind-aware
placement seam, matching its canonical &lt;code dir=&quot;auto&quot;&gt;LANE_STATE&lt;/code&gt; classification), so the
read and write agree for coord-topology missions — previously the read still
looked on the coordination surface, which broke &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; end-to-end.
Separately, 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 &lt;strong&gt;fail closed&lt;/strong&gt; when invoked from a checkout the
mission does not own (&lt;code dir=&quot;auto&quot;&gt;#3128&lt;/code&gt;): a &lt;code dir=&quot;auto&quot;&gt;write_intent&lt;/code&gt;-gated &lt;code dir=&quot;auto&quot;&gt;CheckoutIdentityError&lt;/code&gt;
at the real workspace chokepoint (&lt;code dir=&quot;auto&quot;&gt;workspace/context.py::resolve_workspace_for_wp&lt;/code&gt;)
refuses foreign-checkout writes without ever refusing reads or planning. The
four re-implementations of the git-common-dir/toplevel probe are unified behind
one primitive (&lt;code dir=&quot;auto&quot;&gt;#3373&lt;/code&gt;), and a static &lt;code dir=&quot;auto&quot;&gt;tests/architectural/&lt;/code&gt; gate plus a
cross-partition repo scan keep the P0 class from silently regressing. The
frontmatter/upgrade-wedge slice (&lt;code dir=&quot;auto&quot;&gt;#3372&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;#2702&lt;/code&gt; were confirmed already
closed (by mission &lt;code dir=&quot;auto&quot;&gt;#3383&lt;/code&gt; and prior work) and left out of scope.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Activating a charter directive no longer silently drops every org-pack
artifact from the doctrine graph (mission &lt;code dir=&quot;auto&quot;&gt;org-activation-scan-dirs-01KZY1PT&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3399&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3385&lt;/code&gt;).&lt;/strong&gt; Before, the charter activation allow-list scanned
org packs at a phantom &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;root&gt;/&amp;#x3C;plural&gt;/built-in&lt;/code&gt; layout that no org pack
actually uses, while the live doctrine loader reads the flat &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;root&gt;/&amp;#x3C;plural&gt;&lt;/code&gt;
layout. The two disagreed silently: the moment an operator ran
&lt;code dir=&quot;auto&quot;&gt;charter activate directive &amp;#x3C;stem&gt;&lt;/code&gt;, every org-pack URN failed to resolve and
was dropped from the filtered graph with no error — so a project’s own
directives, tactics, and profiles vanished from governance the first time
anyone activated a single artifact. Now the activation scan reads the same
flat layout the loader does (plus the legacy nested layout additively, with
the flat entry winning a same-name collision), so activating one artifact
leaves the rest of the org pack intact.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;researcher-robbie&lt;/code&gt; agent profile no longer introduces itself under the
wrong name (&lt;code dir=&quot;auto&quot;&gt;#3377&lt;/code&gt;).&lt;/strong&gt; Before, the profile’s &lt;code dir=&quot;auto&quot;&gt;purpose&lt;/code&gt; and
initialization-declaration prose still read “Researcher Rosa” — a leftover the
profile rename missed — so any agent that loaded &lt;code dir=&quot;auto&quot;&gt;researcher-robbie&lt;/code&gt; and
followed its initialization declaration announced itself as “Researcher Rosa”,
even though the profile’s own &lt;code dir=&quot;auto&quot;&gt;name&lt;/code&gt; field, its docs page, and every sibling
profile said “Researcher Robbie”. Now the prose matches the profile’s own
&lt;code dir=&quot;auto&quot;&gt;name&lt;/code&gt;, and a parametrized test asserts every shipped profile’s self-identity
prose equals its &lt;code dir=&quot;auto&quot;&gt;name&lt;/code&gt; field, so this class of identity drift cannot silently
recur.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;sync import-history&lt;/code&gt; now imports legacy work packages that carry retired
frontmatter fields, instead of skipping them (mission
&lt;code dir=&quot;auto&quot;&gt;first-sync-preflight-01KZZ9Q1&lt;/code&gt; FR-011; &lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;).&lt;/strong&gt; The import scan read WP
frontmatter with the strict authoring model (&lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt;), so a
historical WP carrying a field the current schema no longer knows (e.g.
&lt;code dir=&quot;auto&quot;&gt;estimated_lines&lt;/code&gt;) raised a validation error, was logged “unreadable”, and was
degraded to a bare back-fill — losing its real title and dependencies. The
import path now uses a lenient reader that drops unrecognised legacy keys
while still validating known fields, so genuinely-malformed frontmatter is
still skipped fail-loud. Authoring keeps the strict typo guard unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;sync status&lt;/code&gt; now flags an unreachable sync server and how to repoint it,
instead of reporting a bare “Unexpected status” (mission
&lt;code dir=&quot;auto&quot;&gt;first-sync-preflight-01KZZ9Q1&lt;/code&gt; FR-003; &lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;).&lt;/strong&gt; A configured server that
answers with a gateway-class status (&lt;code dir=&quot;auto&quot;&gt;502&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;503&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;504&lt;/code&gt;) — the signature of a
decommissioned platform env or a torn-down preview, which is exactly how a
first sync against a stale &lt;code dir=&quot;auto&quot;&gt;*.platformsh.site&lt;/code&gt; URL stranded — was folded into
the generic “Unexpected HTTP 502” branch, giving the operator no signal that
the URL itself might be the fault. The health probe now reports these as
&lt;strong&gt;Server unavailable&lt;/strong&gt;, reassuring that queued events are retained and will
drain on recovery (consistent with the offline queue’s transient-retry
handling), and — for the decommissioned case — naming the URL and the exact
recovery (&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync server &amp;#x3C;url&gt;&lt;/code&gt; then &lt;code dir=&quot;auto&quot;&gt;auth login --force&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;auth login&lt;/code&gt; now resolves the server the same way &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; does — env over
&lt;code dir=&quot;auto&quot;&gt;[sync].server_url&lt;/code&gt; over the documented default — instead of the env-only
accessor that errored when only &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync server&lt;/code&gt; had been set
(&lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;, FR-005).&lt;/strong&gt; Before, a user who set their server via &lt;code dir=&quot;auto&quot;&gt;sync server&lt;/code&gt;
still hit “SPEC_KITTY_SAAS_URL environment variable is not set” on login, so a
token could only be minted against one server while sync targeted another. It
still refuses (with a remedy naming both &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;sync server&lt;/code&gt;) when neither is set, rather than silently defaulting to the dev
URL. One of the ten-gate first-sync gauntlet fixes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; no longer reports “Sync is healthy” while the server probe
says otherwise (mission &lt;code dir=&quot;auto&quot;&gt;first-sync-preflight-01KZZ9Q1&lt;/code&gt; FR-002; &lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;).&lt;/strong&gt;
The health summary only escalated a server verdict of &lt;code dir=&quot;auto&quot;&gt;Unreachable&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Error&lt;/code&gt;;
a &lt;code dir=&quot;auto&quot;&gt;Permission denied&lt;/code&gt; (403), gateway-down (5xx), or unexpected-status verdict
printed a coloured row in the table but never entered the issue list, so the
doctor still declared everything healthy while the live drain was blocked —
the false-green that hid a broken first sync. Every non-healthy server verdict
(anything but &lt;code dir=&quot;auto&quot;&gt;Connected&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Disabled&lt;/code&gt;, excluding the auth states the
auth/session block already owns) now reaches the summary with the probe’s own
remediation note.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; now run correctly from a caller-owned linked
git worktree, and each worktree’s mission state stays isolated (mission
&lt;code dir=&quot;auto&quot;&gt;worktree-owned-root-3328-01KZRG01&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3346&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3328&lt;/code&gt;).&lt;/strong&gt; Before,
invoking &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; from an explicit linked checkout followed the
worktree’s &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; pointer back to the primary checkout and tried to drive the
mission there — failing with &lt;code dir=&quot;auto&quot;&gt;START_BRANCH_FAILED&lt;/code&gt; when that branch was
already checked out, and risking one worktree reading or writing another
worktree’s mission state. Now the invoking checkout root is validated with
fail-closed git-topology ownership checks and threaded through creation,
resolution, &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;, runtime state, refs, and commits, so two linked worktrees
can create and advance distinct missions concurrently with no
cross-contamination while the primary checkout is left untouched. Managed
Spec Kitty coordination and lane worktrees remain refused.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The ADR inventory freshener now targets the canonical &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt; era index
instead of the redirect README, so newly added ADRs are actually indexed
(&lt;code dir=&quot;auto&quot;&gt;#3346&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3345&lt;/code&gt;).&lt;/strong&gt; Before, the freshener pointed at the redirect
README and left the canonical era index stale, so a new ADR could pass docs
freshness without appearing in the index maintainers browse. Now it writes the
canonical era index directly.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Direct sync ingress no longer drifts to a shared/primary team when the
session read transiently returns None (&lt;code dir=&quot;auto&quot;&gt;#738&lt;/code&gt;/spec-kitty-saas &lt;code dir=&quot;auto&quot;&gt;#911&lt;/code&gt;).&lt;/strong&gt; The
fan-out handler resolved the producer scope as
&lt;code dir=&quot;auto&quot;&gt;read_queue_scope_from_session() or read_queue_scope_from_credentials()&lt;/code&gt;. The
session path is fail-closed to the user’s Private Teamspace, but the credentials
fallback returns whatever &lt;code dir=&quot;auto&quot;&gt;team_slug&lt;/code&gt; the credentials TOML last stored (often a
shared/primary team, e.g. &lt;code dir=&quot;auto&quot;&gt;stijn&lt;/code&gt; rather than &lt;code dir=&quot;auto&quot;&gt;stijn-private&lt;/code&gt;). During a token
refresh or a rehydrate miss the session read returns None and ingress silently
rerouted to that team — forking the producer-scoped journal (&lt;code dir=&quot;auto&quot;&gt;journal-&amp;#x3C;scope&gt;.db&lt;/code&gt;)
and materializing the project under the wrong team server-side, so the
private→shared share could never find it (the Kitty Prime “I can’t see the
team’s work” symptom). Ingress is now session-only: it honours the fail-closed
contract and skips queueing when the Private Teamspace can’t be resolved, rather
than attributing the event to the wrong scope. The credentials reader stays for
the diagnostic call sites (e.g. &lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt;/preflight, which compare the two
scopes to &lt;em&gt;detect&lt;/em&gt; exactly this drift).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Root README guide links point at the post-IA &lt;code dir=&quot;auto&quot;&gt;tutorials/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;how-to/&lt;/code&gt;
paths.&lt;/strong&gt; Fixes GitHub 404s from stale flat &lt;code dir=&quot;auto&quot;&gt;docs/guides/*.md&lt;/code&gt; hrefs after the
guides subdivision (e.g. Your First Mission).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Four operator-visible read/write-consistency defects, where a step trusted a
partial, pre-merge, or recomputed-from-scratch view of persisted state, are
fixed (mission &lt;code dir=&quot;auto&quot;&gt;mission-a-p0-consistency&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3320&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3231&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3334&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3311&lt;/code&gt;).&lt;/strong&gt;
Concretely: &lt;code dir=&quot;auto&quot;&gt;retrospect create --update&lt;/code&gt; reported and emitted the &lt;em&gt;pre-merge&lt;/em&gt;
record — the counts, JSON &lt;code dir=&quot;auto&quot;&gt;findings_status&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptured&lt;/code&gt; event
disagreed with what was written to disk; now they read the persisted record back
(&lt;code dir=&quot;auto&quot;&gt;#3320&lt;/code&gt;). A leftover &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; scaffold placeholder blocked acceptance
for a mission whose real criteria all passed; the verdict now exempts &lt;em&gt;only&lt;/em&gt; the
empty placeholder row, so a real still-pending criterion still blocks as before
(&lt;code dir=&quot;auto&quot;&gt;#3231&lt;/code&gt;). A failed &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; stripped &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; from
&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and wedged the project as unrecoverable &lt;code dir=&quot;auto&quot;&gt;LEGACY&lt;/code&gt;; project metadata
now round-trips the stamp so a failed migration stays recoverable (&lt;code dir=&quot;auto&quot;&gt;#3334&lt;/code&gt;).
Re-running &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; after implementation had begun clobbered the recorded
&lt;code dir=&quot;auto&quot;&gt;planning_commit_sha&lt;/code&gt;; it now preserves provenance once any work package has left
&lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3311&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Six upgrade-wedge failures, where a stuck migration left no self-service way
out, are fixed (&lt;code dir=&quot;auto&quot;&gt;#3383&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3335&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3336&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3337&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3338&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3339&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3372&lt;/code&gt;).&lt;/strong&gt; Concretely: a failed &lt;code dir=&quot;auto&quot;&gt;runtime_state_backfill&lt;/code&gt; aborted mid-walk with
no record of what it had already written, leaving the operator unable to tell
how far the migration got; it now enumerates every mission and file already
persisted before it stopped (&lt;code dir=&quot;auto&quot;&gt;#3335&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --dry-run&lt;/code&gt; (and
&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;) could report nothing pending while the real run went on to apply many
migrations, because the preview computed pending work through a different path
than the real run; the preview now drives off the same migration selector, so it
reports the true pending set (&lt;code dir=&quot;auto&quot;&gt;#3336&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;agent mission create --json&lt;/code&gt; returned a
bare &lt;code dir=&quot;auto&quot;&gt;CHARTER_PACK_CONFIG_INVALID&lt;/code&gt; error code with no fix steps, discarding the
human-readable remediation text a plain-text run would have shown; the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;
envelope now carries the remediation body alongside the code (&lt;code dir=&quot;auto&quot;&gt;#3337&lt;/code&gt;). The
&lt;code dir=&quot;auto&quot;&gt;migrate backfill-runtime-state ... --dry-run&lt;/code&gt; diagnostic a failed migration
told operators to run was itself blocked behind that same failed migration — a
catch-22 with no way out; the &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; form is now ungated (the mutating form
stays blocked) (&lt;code dir=&quot;auto&quot;&gt;#3338&lt;/code&gt;). A failed &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; left the operator’s checkout
switched onto the coordination branch it had just minted, and left that orphan
branch behind; it now restores the original checkout and deletes the branch it
created (&lt;code dir=&quot;auto&quot;&gt;#3339&lt;/code&gt;). The review cycle could append a duplicate &lt;code dir=&quot;auto&quot;&gt;review_feedback&lt;/code&gt;
frontmatter key, producing invalid YAML that later wedged upgrades trying to
parse it; the writer that appended on a miss is retired (it now fails closed),
duplicate-key artifacts are detected and can be repaired non-destructively, and
the frontmatter reader names every offending key (&lt;code dir=&quot;auto&quot;&gt;#3372&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coding agents — especially smaller models — no longer stall mid-implementation to demand human approval and build “prove every step was signed off” scaffolding; and the review/accept gates now capture real, bound evidence instead of unattributed notes.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;governance-at-the-gate&lt;/code&gt;; #3685, #3682) &lt;strong&gt;Before:&lt;/strong&gt; the decision-documentation directive (&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_003&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;required&lt;/code&gt;) was delivered into the &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; action bundle — directly, and transitively via an implement-scoped procedure whose &lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt; link the resolver promoted to an unconditional &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; — so a literal reader composing the &lt;code dir=&quot;auto&quot;&gt;required&lt;/code&gt; directives landed on “author a durable decision artifact, alternatives, rationale, traceable” &lt;em&gt;during implementation&lt;/em&gt; and stopped to ask a human. Compounding it, the doctrine-delivery resolver was enforcement-flat and tension-blind: the &lt;code dir=&quot;auto&quot;&gt;Enforcement&lt;/code&gt; levels had no ordering, and the tension arbiter (&lt;code dir=&quot;auto&quot;&gt;reconcile-change-scope-tensions&lt;/code&gt;, itself the weakest &lt;code dir=&quot;auto&quot;&gt;advisory&lt;/code&gt;) never reached the agent &lt;em&gt;as&lt;/em&gt; an arbiter — so a weak model had no signal that a brake outranked a do-more rule. Separately, at the deciding gates the evidence was thin — an &lt;code dir=&quot;auto&quot;&gt;in_review → approved&lt;/code&gt; transition recorded an unattributed prose note (no &lt;code dir=&quot;auto&quot;&gt;policy_metadata&lt;/code&gt;, no &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;), a first-pass approval wrote no &lt;code dir=&quot;auto&quot;&gt;review-cycle&lt;/code&gt; artifact at all, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; left &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt; an unfilled &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt; scaffold. &lt;strong&gt;After:&lt;/strong&gt; decision-documentation is delivered at the deciding gate (&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;) and removed from &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, with a class-level gate that fails if any &lt;code dir=&quot;auto&quot;&gt;required&lt;/code&gt; decision-documentation directive is ever scoped back onto implement (directly or transitively); the &lt;code dir=&quot;auto&quot;&gt;Enforcement&lt;/code&gt; levels carry an explicit rank and a structural gate forbids a &lt;code dir=&quot;auto&quot;&gt;reconciles_tension&lt;/code&gt; arbiter ranked below what it arbitrates (the arbiter is promoted to match its operands and is now delivered &lt;em&gt;as&lt;/em&gt; an arbiter, with co-delivered tensions annotated on the bundle); and the approve/accept gates capture real evidence — the approval event carries the reviewer’s &lt;code dir=&quot;auto&quot;&gt;policy_metadata&lt;/code&gt; (tool/profile/model/shell-pid) and a &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;, a first-pass approval auto-authors an &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;review-cycle&lt;/code&gt; carrying a reproduction command, and &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; populates &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt; criterion rows from the recorded review evidence (only from a genuine &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; verdict — a stale rejection can never fabricate a pass). Follow-up #3805 tracks the durable resolver fix for the soft-&lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt;-as-&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; modeling that made the transitive leak possible.&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; no longer re-parses the whole charter on every invocation, and a slow shared runner can no longer red-block an unrelated PR on &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; latency.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;next-latency-durable-fix&lt;/code&gt;; #3787, #3595; relates #2749, #3783) &lt;strong&gt;Before:&lt;/strong&gt; two problems compounded. (1) On any charter-bearing project, every &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; (the command the mission loop runs constantly) re-ran the charter freshness preflight from scratch — a full ruamel parse of the ~1600-line &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; — costing ~0.5s per call. (2) The check meant to guard &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; latency was a single-shot absolute wall-clock ceiling (&lt;code dir=&quot;auto&quot;&gt;scripts/check_nfr_003_latency.py&lt;/code&gt;) still running on the &lt;strong&gt;PR-blocking&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;clean-install-verification&lt;/code&gt; path; it false-redded on shared-runner variance and had been ratcheted up four times (1.00 → 1.05 → 1.60 → 2.20s), most recently during the #3783 landing. &lt;strong&gt;After:&lt;/strong&gt; (1) &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; serves the charter freshness verdict from a per-repo content-hash cache — keyed on the charter bundle &lt;strong&gt;plus&lt;/strong&gt; the synthesized-DRG graph and synthesis-manifest files, content-only (never mtime) and fail-closed, so it never serves a stale “fresh” governance verdict — skipping the parse on a hit. (2) The blocking wall-clock ceiling is retired: the &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; cold-start signal now runs statistically and off the PR path in &lt;code dir=&quot;auto&quot;&gt;performance.yml&lt;/code&gt; (the pipeline from ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-22-1&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;clean-install-verification&lt;/code&gt; keeps only the structural clean-wheel smoke check (that &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; runs at all). A &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;-path import-hygiene trim (deferring an import the no-op/startup path doesn’t use) rides along; the deeper real-query import-floor reduction is tracked separately in #3789.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; now tells you the honest way out of a path-convention mismatch instead of steering you into a fake green.&lt;/strong&gt; (#3730, #3085) &lt;strong&gt;Before:&lt;/strong&gt; when a mission’s layout did not match the active path convention, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; failed with &lt;em&gt;“These directories are required by the active mission. Create them before continuing.”&lt;/em&gt; — which pushed operators to &lt;code dir=&quot;auto&quot;&gt;mkdir&lt;/code&gt; empty directories just to pass the gate (a fake green), and never mentioned the real escape hatch. Separately, a token declared under both &lt;code dir=&quot;auto&quot;&gt;artifacts.optional&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;paths.deliverables&lt;/code&gt; (e.g. &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt;) was reported &lt;strong&gt;twice&lt;/strong&gt; — once as an optional warning and once as a blocking error — so the same missing path showed up at two severities. &lt;strong&gt;After:&lt;/strong&gt; the failure surfaces the real option — &lt;em&gt;“Run &lt;code dir=&quot;auto&quot;&gt;accept --lenient&lt;/code&gt; to treat these as warnings instead of blocking errors for this mission run”&lt;/em&gt; — and keeps the &lt;code dir=&quot;auto&quot;&gt;mkdir&lt;/code&gt; suggestions only as an explicit opt-in “adopt the convention” path, not the prescribed remedy (&lt;code dir=&quot;auto&quot;&gt;--lenient&lt;/code&gt;’s help text now says it also downgrades missing path-convention checks). The double-report is deduped structurally (the blocking severity wins) via an artifact-token membership check rather than fragile string matching, and remediation now names the &lt;strong&gt;resolved&lt;/strong&gt;, tested location rather than the bare declared token. Out of scope by design: the &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;-hardcoded non-&lt;code dir=&quot;auto&quot;&gt;src&lt;/code&gt; repo portability (#3016) is unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&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 — every CLI command works again.&lt;/strong&gt; (#3782) &lt;strong&gt;Before:&lt;/strong&gt; typer 0.27.2 (published 2026-08-28) removed &lt;code dir=&quot;auto&quot;&gt;Abort&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;Exit&lt;/code&gt; from its vendored &lt;code dir=&quot;auto&quot;&gt;typer._click.exceptions&lt;/code&gt; module. The orchestrator-API command layer resolved those exception classes with &lt;code dir=&quot;auto&quot;&gt;getattr(_CLICK, name, _CLICK.exceptions.&amp;#x3C;name&gt;)&lt;/code&gt;, whose fallback argument is evaluated eagerly — so on the new typer it raised &lt;code dir=&quot;auto&quot;&gt;AttributeError: module &apos;typer._click.exceptions&apos; has no attribute &apos;Abort&apos;&lt;/code&gt; at import time, and since that module loads on every invocation, &lt;em&gt;every&lt;/em&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; subprocess died with a traceback instead of running (&lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, …). &lt;strong&gt;After:&lt;/strong&gt; a single &lt;code dir=&quot;auto&quot;&gt;_resolve_click_exc()&lt;/code&gt; helper resolves each click/typer exception class defensively across the vendored module, its &lt;code dir=&quot;auto&quot;&gt;exceptions&lt;/code&gt; submodule, the &lt;code dir=&quot;auto&quot;&gt;typer&lt;/code&gt; top level, and the standalone &lt;code dir=&quot;auto&quot;&gt;click&lt;/code&gt; package, so a symbol relocation in a future typer release degrades gracefully to click-only instead of breaking the CLI. Pinned by focused unit tests plus the existing &lt;code dir=&quot;auto&quot;&gt;_JSONErrorGroup&lt;/code&gt; typer-surface smoke test.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Auth and sync diagnostics no longer report success while the session is broken — every status line is now derived from evidence, and a probe that cannot verify says &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;, never &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt;.&lt;/strong&gt; (#3723) &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;sync status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;auth status&lt;/code&gt; printed a green &lt;code dir=&quot;auto&quot;&gt;Authenticated&lt;/code&gt; banner directly above a contradicting &lt;code dir=&quot;auto&quot;&gt;Access token: expired&lt;/code&gt; detail, and &lt;code dir=&quot;auto&quot;&gt;auth doctor&lt;/code&gt; printed &lt;code dir=&quot;auto&quot;&gt;No problems detected.&lt;/code&gt; for an expired token whose refresh chain was failing — each surface &lt;em&gt;hand-rolled&lt;/em&gt; its own green claim alongside, never derived from, the detail it displayed, so there was no way to get from “broken” to a true statement about why without reading the source. &lt;strong&gt;After:&lt;/strong&gt; a single typed authority &lt;code dir=&quot;auto&quot;&gt;specify_cli.auth.verdict&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;HealthVerdict&lt;/code&gt; — a 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; whose &lt;code dir=&quot;auto&quot;&gt;headline&lt;/code&gt; is a computed property derived from &lt;code dir=&quot;auto&quot;&gt;state&lt;/code&gt;, never a settable field, with mandatory evidence for every definite claim) owns the decision, and all three surfaces render &lt;code dir=&quot;auto&quot;&gt;verdict.headline&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;verdict.evidence&lt;/code&gt; instead of a bare word. An expired access token whose refresh chain cannot be proven offline now resolves to &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt; (“Cannot verify”), never a false green; &lt;code dir=&quot;auto&quot;&gt;auth doctor&lt;/code&gt; prints “No problems detected.” &lt;strong&gt;only&lt;/strong&gt; when the verdict is a confirmed &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt; (an &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt; always raises a named finding), and its &lt;code dir=&quot;auto&quot;&gt;--server&lt;/code&gt; probe feeds the verdict so it can resolve &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fail&lt;/code&gt;. A new AST architectural ratchet (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_status_line_honesty.py&lt;/code&gt;) enforces the three honesty rules structurally: each surface must genuinely route through the authority, &lt;code dir=&quot;auto&quot;&gt;HealthVerdict&lt;/code&gt; must keep its 3-member Literal and property-derived headline, and no surface may hand-roll an authenticated-claim literal outside the one allowlisted verdict-gated render site.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A deliberately-canceled work package is now an honest mission ending, and the planner warns before authoring work that can never terminate&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;mission-completion-terminal-state-01M129MV&lt;/code&gt;; #2945 #3590). &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; refused a work package that was canceled during a documented replan — even though &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt; is a terminal lane — so a legitimate cancellation left the mission permanently non-terminal, forcing an operator to resurrect and falsely approve removed work; and &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; could author an “action” work package whose completion is only observable after integration, with no honest terminal state. Worse, the acceptance path kept its own accept-ready set (four parallel &lt;code dir=&quot;auto&quot;&gt;{approved,done}&lt;/code&gt;/canceled decisions across &lt;code dir=&quot;auto&quot;&gt;acceptance/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;dependency_graph.py&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;policy/merge_gates.py&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; auto-synthesized a non-empty cancellation &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;, so “canceled with a reason” could not distinguish a documented replan from a bare &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; cancellation provenance is a first-class, operator-authored &lt;code dir=&quot;auto&quot;&gt;reason_source&lt;/code&gt; field on the status event (captured at emit, projected into the reduced snapshot), and a single &lt;code dir=&quot;auto&quot;&gt;is_acceptable_ending(lane, *, has_provenance)&lt;/code&gt; authority — consumed by &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt;, both CLI claim gates (&lt;code dir=&quot;auto&quot;&gt;implement.py&lt;/code&gt; and the agent-action executor), and the dependency-readiness gate — admits a &lt;code dir=&quot;auto&quot;&gt;canceled&lt;/code&gt; work package &lt;strong&gt;only&lt;/strong&gt; when it carries operator provenance. &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; reports such work packages under a dedicated &lt;code dir=&quot;auto&quot;&gt;canceled_wps&lt;/code&gt; field, refuses a synthetic (undocumented) cancellation with a structured blocker, and still runs the acceptance-matrix and issue-matrix gates (canceled-terminal never short-circuits them). &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; excludes canceled work packages from its per-work-package done/review assertions at both derivations (never driving &lt;code dir=&quot;auto&quot;&gt;canceled → done&lt;/code&gt;) and skips a lane’s branch only when every work package in it is canceled. A canceled-with-provenance dependency no longer strands its dependent at claim or merge time. &lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt; gains an advisory &lt;code dir=&quot;auto&quot;&gt;check-terminability&lt;/code&gt; warning (never blocks) that flags a work package whose acceptance criteria can only be met after integration, so operators re-home that content at planning time. Backward-compatible: missions with no canceled work packages accept and merge identically, and legacy events with no &lt;code dir=&quot;auto&quot;&gt;reason_source&lt;/code&gt; are honored. The completion-contract redesign remains deferred to #3550.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The background sync daemon now resolves a &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;-capable interpreter before it spawns, instead of trusting a bare &lt;code dir=&quot;auto&quot;&gt;sys.executable&lt;/code&gt; that may die with &lt;code dir=&quot;auto&quot;&gt;ModuleNotFoundError&lt;/code&gt;.&lt;/strong&gt; (#3624) &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;_spawn_sync_daemon_process&lt;/code&gt; launched the daemon with &lt;code dir=&quot;auto&quot;&gt;subprocess.Popen([sys.executable, &quot;-c&quot;, …])&lt;/code&gt;. On a host where the interpreter that launched the spawner cannot import &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; — a macOS framework-Python re-exec, a pyenv shim, or a Homebrew &lt;code dir=&quot;auto&quot;&gt;python3&lt;/code&gt; first on &lt;code dir=&quot;auto&quot;&gt;PATH&lt;/code&gt; — the auto-spawned child died immediately with &lt;code dir=&quot;auto&quot;&gt;ModuleNotFoundError: No module named &apos;specify_cli&apos;&lt;/code&gt;, leaving only an opaque &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;string&gt;&lt;/code&gt; line-3 traceback in &lt;code dir=&quot;auto&quot;&gt;~/.spec-kitty/sync-daemon.log&lt;/code&gt;. The failure was intermittent: a daemon started via the correctly-shimmed &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor restart-daemon&lt;/code&gt;) ran the right interpreter, so it depended on who spawned it. &lt;strong&gt;After:&lt;/strong&gt; the spawn first probes the candidate interpreter (&lt;code dir=&quot;auto&quot;&gt;python -c &quot;import specify_cli&quot;&lt;/code&gt;); if it is incapable, it self-heals by prepending the running package’s path to the child’s &lt;code dir=&quot;auto&quot;&gt;PYTHONPATH&lt;/code&gt; and re-probes; if it is still incapable, it raises a loud, actionable &lt;code dir=&quot;auto&quot;&gt;DaemonSpawnError&lt;/code&gt; (telling the operator to restart via &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor restart-daemon&lt;/code&gt;) rather than spawning a doomed child that scribbles into the log. The reaper’s exec-identity argv marker is built from the resolved interpreter so cross-scope attribution stays accurate under self-heal.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty auth status&lt;/code&gt; now shows each team’s slug and &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync share&lt;/code&gt; accepts a team name, closing the gap where the CLI could never tell a user the slug that &lt;code dir=&quot;auto&quot;&gt;sync share&lt;/code&gt; requires.&lt;/strong&gt; (#3731) &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;auth status&lt;/code&gt; printed team &lt;em&gt;names&lt;/em&gt; only, while &lt;code dir=&quot;auto&quot;&gt;sync share&lt;/code&gt; took a required &lt;em&gt;slug&lt;/em&gt; the CLI never displayed anywhere — a user had no way to learn their own team slug from the tool. &lt;strong&gt;After:&lt;/strong&gt; the server-published &lt;code dir=&quot;auto&quot;&gt;slug&lt;/code&gt; (saas#986) is surfaced end-to-end. &lt;code dir=&quot;auto&quot;&gt;Team&lt;/code&gt; carries a &lt;code dir=&quot;auto&quot;&gt;slug&lt;/code&gt; field populated at both &lt;code dir=&quot;auto&quot;&gt;/api/v1/me&lt;/code&gt; ingress points (&lt;code dir=&quot;auto&quot;&gt;Team.from_dict&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;parse_me_teams&lt;/code&gt;), each falling back to the team &lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt; (the long-standing compatibility alias) for legacy sessions stored before the field existed. &lt;code dir=&quot;auto&quot;&gt;auth status&lt;/code&gt; prints &lt;code dir=&quot;auto&quot;&gt;slug: &amp;#x3C;slug&gt;&lt;/code&gt; beside every team and marks the Private Teamspace &lt;em&gt;not shareable&lt;/em&gt; (the server refuses it as a destination). &lt;code dir=&quot;auto&quot;&gt;sync share&lt;/code&gt; now accepts either the slug or the display name and resolves it through the new fail-closed &lt;code dir=&quot;auto&quot;&gt;resolve_team_slug&lt;/code&gt; helper — an unknown or ambiguous handle, or one targeting the Private Teamspace, prints the shareable teams and exits 1 without calling the server, rather than silently picking the wrong team. New logic lives in the &lt;code dir=&quot;auto&quot;&gt;auth.session&lt;/code&gt; authority (&lt;code dir=&quot;auto&quot;&gt;shareable_teams&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_team_slug&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;TeamSlugResolutionError&lt;/code&gt;), not the command layer.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync share &amp;#x3C;team&gt;&lt;/code&gt; no longer fails first-run with an unhandled traceback while it self-heals; the recoverable race now reports an actionable line and teardown is deterministic.&lt;/strong&gt; (#3699) On a checkout that is opted in but whose project the server has not yet seen, the &lt;code dir=&quot;auto&quot;&gt;share&lt;/code&gt; command’s 404 handler already materializes the project in Private Teamspace and retries — but the retry in &lt;code dir=&quot;auto&quot;&gt;cli/commands/sync.py&lt;/code&gt; sat &lt;strong&gt;outside any &lt;code dir=&quot;auto&quot;&gt;try&lt;/code&gt;&lt;/strong&gt;, so the second, transient 404 (the newly emitted &lt;code dir=&quot;auto&quot;&gt;BuildRegistered&lt;/code&gt; is not yet visible server-side) propagated as a raw &lt;code dir=&quot;auto&quot;&gt;RepositorySharingClientError&lt;/code&gt; stack trace, trailed by a &lt;code dir=&quot;auto&quot;&gt;Task was destroyed but it is pending!&lt;/code&gt; warning from the WebSocket disconnect being skipped on the aborted path. &lt;strong&gt;Before:&lt;/strong&gt; first-run &lt;code dir=&quot;auto&quot;&gt;sync share&lt;/code&gt; exited 1 with a Python traceback; the documented workaround was to run &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; and repeat the identical command. &lt;strong&gt;After:&lt;/strong&gt; the retry is wrapped in its own &lt;code dir=&quot;auto&quot;&gt;except RepositorySharingClientError&lt;/code&gt; that prints &lt;code dir=&quot;auto&quot;&gt;Registering this project in Private Teamspace. Run spec-kitty sync share &amp;#x3C;team&gt; again in a moment.&lt;/code&gt; and exits &lt;code dir=&quot;auto&quot;&gt;1&lt;/code&gt; cleanly (no traceback), and a &lt;code dir=&quot;auto&quot;&gt;finally&lt;/code&gt; drives &lt;code dir=&quot;auto&quot;&gt;SyncRuntime.stop()&lt;/code&gt; (idempotent; awaits the disconnect synchronously) on every exit path so orderly teardown runs on the error path too, removing the pending-task warning. The 404→materialize→retry policy is still inline in the command module; pushing it down into a typed &lt;code dir=&quot;auto&quot;&gt;ShareOutcome&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;sync/sync_authority.py&lt;/code&gt; is a deferred follow-up (the three interleaved command-layer render/exit paths make a clean extraction larger than the fix).&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, instead of always silently passing.&lt;/strong&gt; (#3704) &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt;’s guard evaluation for a mission family outside the four built-in types (&lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;) always returned &lt;code dir=&quot;auto&quot;&gt;guard_failures == []&lt;/code&gt; regardless of what artifacts existed on disk — a data-driven presence gate existed (&lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;path_pattern&lt;/code&gt;s), but nothing consumed the resulting presence set into a real &lt;code dir=&quot;auto&quot;&gt;guard_failures&lt;/code&gt; list for a family outside the built-in guard-table dispatch, so a custom mission could advance silently past a step whose declared, &lt;code dir=&quot;auto&quot;&gt;blocking: true&lt;/code&gt; artifact was never produced. &lt;strong&gt;After:&lt;/strong&gt; the same evaluation layer used by the built-ins now genuinely checks a custom family’s declared manifest — present artifacts pass, a missing &lt;code dir=&quot;auto&quot;&gt;blocking: true&lt;/code&gt; artifact blocks with a real failure message and a &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;Decision.kind&lt;/code&gt;, at any of the three call sites (CLI pre-check, WP-iteration pre-check, composed-action guard) and at both the built-in and org-tier (&lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;org_root&gt;/missions/&amp;#x3C;type&gt;/expected-artifacts.yaml&lt;/code&gt;) manifest locations. The four built-in families are unaffected — their &lt;code dir=&quot;auto&quot;&gt;guard_failures&lt;/code&gt; output is byte-identical before and after. An unregistered family with &lt;strong&gt;no&lt;/strong&gt; manifest declared anywhere still runs to completion exactly as before (&lt;code dir=&quot;auto&quot;&gt;UnregisteredMissionFamilyError&lt;/code&gt; for strict dispatch, tolerant callers still degrade to &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt;). &lt;strong&gt;Operator-visible behavior change:&lt;/strong&gt; an in-flight custom mission previously advancing silently past a step with an unmet &lt;code dir=&quot;auto&quot;&gt;blocking: true&lt;/code&gt; requirement may, on its next evaluation, correctly BLOCK where it previously would not — this is the intended fix. In-flight missions are not retroactively re-evaluated: past &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; entries and &lt;code dir=&quot;auto&quot;&gt;Decision&lt;/code&gt;s are never rewritten; only the mission’s next evaluation after deploy uses the corrected logic.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter activate mission-type &amp;#x3C;T&gt;&lt;/code&gt; now refuses a mission type that resolves an empty action sequence, instead of reporting success and leaving the project unable to plan anything.&lt;/strong&gt; (#3717; closes #3702) &lt;strong&gt;Before:&lt;/strong&gt; the &lt;em&gt;first&lt;/em&gt; activation of such a type exited &lt;code dir=&quot;auto&quot;&gt;0&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;Activated: &amp;#x3C;T&gt;&lt;/code&gt; and wrote it into &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt;, so an operator who followed the documented order — declare the org pack, then activate — got a success message and a bricked project; every later governed entry point then failed, including &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; itself on a second run (&lt;code dir=&quot;auto&quot;&gt;exit 1: mission type ... has an empty action sequence&lt;/code&gt;). The right validation already existed but only ran on the &lt;em&gt;read&lt;/em&gt; path (#3386), never on activation — the one operation whose whole job is deciding whether a type is usable. &lt;strong&gt;After:&lt;/strong&gt; a fail-closed preflight at the CLI seam runs that same resolution &lt;em&gt;before&lt;/em&gt; any write, so the first run refuses with the same message the read path produces and &lt;strong&gt;nothing is written&lt;/strong&gt;. The single-level &lt;code dir=&quot;auto&quot;&gt;extends&lt;/code&gt; fallback is honored (a type whose own sequence is empty but whose parent resolves a non-empty one still activates); the read-path &lt;code dir=&quot;auto&quot;&gt;is_registered&lt;/code&gt; short-circuit is unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A single project-local &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;directives:&lt;/code&gt; entry is now additive instead of silently replacing the entire resolved directive set.&lt;/strong&gt; (#3728; mission &lt;code dir=&quot;auto&quot;&gt;directives-additive-resolution&lt;/code&gt;) &lt;strong&gt;Before:&lt;/strong&gt; on a project that resolved its directives via the built-in catalog, adding even one directive under &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;directives:&lt;/code&gt; section wiped the whole resolved set — &lt;code dir=&quot;auto&quot;&gt;charter context --action plan --json&lt;/code&gt; dropped from the catalog’s full directive count to just the one local entry, with exit 0, nothing on stderr, and &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; still reporting FRESH/VALID. &lt;strong&gt;After:&lt;/strong&gt; a project-local directive is unioned onto the base set the project already resolves (catalog default, charter activation, or an explicit &lt;code dir=&quot;auto&quot;&gt;governance.doctrine.selected_directives&lt;/code&gt; selection), so &lt;code dir=&quot;auto&quot;&gt;N&lt;/code&gt; base directives plus &lt;code dir=&quot;auto&quot;&gt;K&lt;/code&gt; &lt;strong&gt;new&lt;/strong&gt; local ones resolve to &lt;code dir=&quot;auto&quot;&gt;N+K&lt;/code&gt; (a local id already in the base is de-duplicated, never a loss), with zero baseline lost.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Three release-blocking P0 workflow defects fixed as one mission (&lt;code dir=&quot;auto&quot;&gt;p0-reliability-triad&lt;/code&gt;; #3282, #3579, #3281).&lt;/strong&gt; Each left a project broken-but-”healthy”-reporting during a core workflow. &lt;strong&gt;#3282 — upgrade:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; wrote &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; unconditionally, but a pointer-based charter project reads them from the pointed-at &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, so the seeded key was never read and mission creation kept failing closed after a “successful” upgrade; the provisioner now routes through the pointer-aware &lt;code dir=&quot;auto&quot;&gt;charter.compiler.provision_mission_type_activations&lt;/code&gt; writer (legacy projects still write &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt;), and the dry-run pending predicate keys on key-presence in the resolved write target (preserving authored-empty-&lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; parity, non-crashing on a dangling pointer). No new migration. &lt;strong&gt;#3579 — merge:&lt;/strong&gt; a stale-lane halt routed the operator to a raw &lt;code dir=&quot;auto&quot;&gt;git&lt;/code&gt; merge that conflicts on the derived &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;, naming neither of the tool’s own remedies; &lt;code dir=&quot;auto&quot;&gt;_stale_remediation&lt;/code&gt; now names &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status materialize&lt;/code&gt; (rebuild from the event log) — no &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; merge driver is introduced (it stays intentionally driver-exempt). &lt;strong&gt;#3281 — implement:&lt;/strong&gt; a retry after a recorded-planning-commit merge conflict skipped dependency propagation because &lt;code dir=&quot;auto&quot;&gt;ensure_workspace_materialized&lt;/code&gt; short-circuited on &lt;code dir=&quot;auto&quot;&gt;workspace.exists&lt;/code&gt;; the retry now re-enters an idempotent self-heal, fresh-path allocation is atomic (no orphaned worktree on conflict), and a &lt;strong&gt;post-materialize&lt;/strong&gt; ancestry gate — enforced on both the CLI and &lt;code dir=&quot;auto&quot;&gt;orchestrator_api&lt;/code&gt; claim paths — refuses claiming a WP against a lane missing its dependencies &lt;strong&gt;without&lt;/strong&gt; deadlocking a legitimately-approved same-mission dependency.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.dossier&lt;/code&gt; no longer re-exports seven &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt; types — one canonical import path per type instead of two.&lt;/strong&gt; (#3677) &lt;code dir=&quot;auto&quot;&gt;ArtifactIdentity&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ContentHashRef&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;LocalNamespaceTuple&lt;/code&gt;, and the four &lt;code dir=&quot;auto&quot;&gt;MissionDossier*Payload&lt;/code&gt; types (&lt;code dir=&quot;auto&quot;&gt;MissionDossierArtifactIndexedPayload&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MissionDossierArtifactMissingPayload&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MissionDossierSnapshotComputedPayload&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MissionDossierParityDriftDetectedPayload&lt;/code&gt;) were re-exported from both &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt; (their canonical home) and &lt;code dir=&quot;auto&quot;&gt;specify_cli.dossier&lt;/code&gt;, violating the charter’s single-canonical-authority principle for this surface; no &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt; caller used the second path. &lt;strong&gt;After:&lt;/strong&gt; the seven names are removed from &lt;code dir=&quot;auto&quot;&gt;dossier/__init__.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;from .events import (...)&lt;/code&gt; statement and &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt;; the four &lt;code dir=&quot;auto&quot;&gt;emit_*&lt;/code&gt; function re-exports (&lt;code dir=&quot;auto&quot;&gt;emit_artifact_indexed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;emit_artifact_missing&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;emit_snapshot_computed&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;emit_parity_drift_detected&lt;/code&gt;) are untouched, and &lt;code dir=&quot;auto&quot;&gt;events.py&lt;/code&gt; itself has zero diff. A regression test (&lt;code dir=&quot;auto&quot;&gt;tests/dossier/test_reexport_trim.py&lt;/code&gt;) pins both halves: the seven names are unreachable via &lt;code dir=&quot;auto&quot;&gt;specify_cli.dossier&lt;/code&gt;, and the four &lt;code dir=&quot;auto&quot;&gt;emit_*&lt;/code&gt; names remain reachable. &lt;strong&gt;User-visible API change:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;from specify_cli.dossier import ArtifactIdentity&lt;/code&gt; (and the other six) now raises &lt;code dir=&quot;auto&quot;&gt;ImportError&lt;/code&gt;; import these types directly from &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt; instead.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Concurrent review-verdict saves can no longer race each other into a silently-lost or silently-uncommitted commit — the actual &lt;code dir=&quot;auto&quot;&gt;git add&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt; for a review-cycle artifact now runs behind a checkout-wide serialization queue instead of unprotected.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;durable-concurrent-review-cycle-records-01M0QRX7&lt;/code&gt;; closes #3235) &lt;code dir=&quot;auto&quot;&gt;_commit_review_cycle_artifact&lt;/code&gt;’s git invocation lived deliberately outside &lt;code dir=&quot;auto&quot;&gt;feature_status_lock&lt;/code&gt; (per NFR-006), with no protection against two OS processes racing &lt;code dir=&quot;auto&quot;&gt;git add&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt; in the same working tree — &lt;code dir=&quot;auto&quot;&gt;tests/integration/test_review_durability_matrix.py::test_sc004_two_concurrent_processes_never_clobber_a_verdict_over_50_iterations&lt;/code&gt; reproduced the race under genuine multi-process concurrency, observing a &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; staging-area refusal or a reported-but-missing artifact. &lt;strong&gt;After:&lt;/strong&gt; a new checkout-wide &lt;code dir=&quot;auto&quot;&gt;FileLock&lt;/code&gt;-backed queue (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/review/verdict_commit_queue.py&lt;/code&gt;, keyed on &lt;code dir=&quot;auto&quot;&gt;git_common_dir()&lt;/code&gt; so linked worktrees and missions converge on one lock while independent clones stay independent) wraps the whole allocate→write→commit→verify sequence; a save that can’t complete within its bounded window fails the command explicitly (&lt;code dir=&quot;auto&quot;&gt;verdict_durably_persisted: false&lt;/code&gt;, a truthful busy result) rather than reporting success while the verdict silently disappears. &lt;code dir=&quot;auto&quot;&gt;feature_status_lock&lt;/code&gt; for event/status mutation remains a separate, narrower lock (distinct lock file, distinct re-entrancy, distinct timeout error): the two are only ever acquired queue-outer→status-inner and never in the reverse order, so there is no lock-ordering deadlock. The &lt;strong&gt;whole&lt;/strong&gt; save is time-bounded, not just queue acquisition — while the queue is held the in-critical-section &lt;code dir=&quot;auto&quot;&gt;feature_status_lock&lt;/code&gt; wait is bounded too (a wedged holder can no longer hang every verdict save in the checkout); off the queue (the &lt;code dir=&quot;auto&quot;&gt;--no-auto-commit&lt;/code&gt; / local-only feedback paths) the historical unbounded wait is retained. Retained evidence and identical-adoption handling were hardened alongside so a commit-infra exception no longer unlinks a recoverable artifact, and a revert-compensator failure surfaces the same structured durability envelope instead of a bare error (mission &lt;code dir=&quot;auto&quot;&gt;durable-concurrent-review-cycle-records-01M0QRX7&lt;/code&gt;; #3773).&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; no longer refuses to run when a host is unauthenticated, and its auth check now reads the real session state instead of a queue-scope proxy.&lt;/strong&gt; (#3621) Two defects, both fixed. &lt;strong&gt;Before:&lt;/strong&gt; with &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC=1&lt;/code&gt;, setup-plan (a) decided the host was unauthenticated by checking &lt;code dir=&quot;auto&quot;&gt;read_queue_scope_from_session()&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;read_queue_scope_from_credentials()&lt;/code&gt; — a queue-scope file read, not an auth check — so a genuinely logged-in host with a valid refresh token but no materialized &lt;code dir=&quot;auto&quot;&gt;queue_scope&lt;/code&gt; (e.g. encrypted session storage, expired access token) was reported &lt;code dir=&quot;auto&quot;&gt;SAAS_SYNC_UNAUTHENTICATED&lt;/code&gt; and refused with &lt;strong&gt;exit 2&lt;/strong&gt; before any local verification ran; and (b) even a correctly-detected logged-out host was refused the same way, blocking the read-only phase-completion check the caller actually wanted. &lt;strong&gt;After:&lt;/strong&gt; authentication comes from the canonical &lt;code dir=&quot;auto&quot;&gt;TokenManager.session_assessment&lt;/code&gt; (a refresh-capable session reads as authenticated regardless of queue-scope materialization); local verification always runs and is authoritative — the command now &lt;strong&gt;exits 0&lt;/strong&gt; whenever local verification succeeds, and hosted-sync unavailability (auth, structural boundary, or route) is reported as a nonfatal &lt;code dir=&quot;auto&quot;&gt;warnings[]&lt;/code&gt; diagnostic in &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; (a &lt;code dir=&quot;auto&quot;&gt;Warning:&lt;/code&gt; line otherwise), matching the sibling mission commands’ logged-out severity policy. Local dossier capture (&lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt; mission-dossier sync) is unaffected by hosted-sync availability — it is project-isolated local capture and was never gated by the SaaS flag or auth state, matching every other mission command. &lt;strong&gt;Breaking for automation:&lt;/strong&gt; a caller that branched on setup-plan’s old exit code 2 / &lt;code dir=&quot;auto&quot;&gt;SAAS_SYNC_UNAUTHENTICATED&lt;/code&gt; error for an unauthenticated host must now read &lt;code dir=&quot;auto&quot;&gt;warnings[].code&lt;/code&gt; on exit 0 instead.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now gitignores the &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; execution-worktrees root, and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; backfills the entry into existing projects.&lt;/strong&gt; (#3689) &lt;strong&gt;Before:&lt;/strong&gt; the only code that ever excluded &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; was the 0.13.1 migration, which writes the local-only &lt;code dir=&quot;auto&quot;&gt;.git/info/exclude&lt;/code&gt; and never runs for projects stamped ≥ 0.13.1 — so on every project initialised since then, the first mission worktree made the main checkout’s &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; show &lt;code dir=&quot;auto&quot;&gt;?? .worktrees/&lt;/code&gt; permanently, and a stray &lt;code dir=&quot;auto&quot;&gt;git add -A&lt;/code&gt; staged an entire nested checkout; several code paths (&lt;code dir=&quot;auto&quot;&gt;agent/workflow.py&lt;/code&gt; FR-002(b), &lt;code dir=&quot;auto&quot;&gt;workflow_executor.py&lt;/code&gt;) already assumed the root was ignored. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; is a first-class &lt;code dir=&quot;auto&quot;&gt;IGNORED&lt;/code&gt; surface in the state contract (&lt;code dir=&quot;auto&quot;&gt;worktrees_root&lt;/code&gt;), so fresh &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; writes it to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; through the existing &lt;code dir=&quot;auto&quot;&gt;get_runtime_gitignore_entries()&lt;/code&gt; path, and a new &lt;code dir=&quot;auto&quot;&gt;3.2.6rc3_worktrees_gitignore_backfill&lt;/code&gt; migration (sibling to the #3435 lint-report backfill, firing even on projects already stamped 3.2.6rc3) adds it to already-initialised projects — including via &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; rather than &lt;code dir=&quot;auto&quot;&gt;info/exclude&lt;/code&gt;, so the coverage travels with clones. A real-git regression test pins the observable: after the backfill, a checkout under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; is invisible to &lt;code dir=&quot;auto&quot;&gt;git status&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 upgrade --dry-run&lt;/code&gt; on a project that is already up to date now reports the &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt; seed it would still perform, instead of only saying “Project is already up to date!”&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-drg-silent-drop-boundary&lt;/code&gt;) A real upgrade seeds a missing &lt;code dir=&quot;auto&quot;&gt;mission_type_activations&lt;/code&gt; key on both the migration and the no-migrations path, but the dry-run preview only announced it when migrations were also pending. &lt;strong&gt;Before:&lt;/strong&gt; an operator dry-running an already-current project that was missing the key saw “already up to date” and no hint of the pending seed — then a real upgrade silently changed the config. &lt;strong&gt;After:&lt;/strong&gt; the dry-run previews the pending provisioning on the up-to-date path too, so the preview matches what a real upgrade does (the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; surface and non-dry runs are unaffected).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A malformed &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt; in one org pack of a multi-pack chain no longer drops the &lt;em&gt;other&lt;/em&gt; packs’ fragments.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-drg-silent-drop-boundary&lt;/code&gt;; #3629 second-opinion follow-up) The mission-step executor tolerated a malformed &lt;em&gt;optional&lt;/em&gt; org fragment by degrading it, but did so for the whole chain at once — one bad pack silently evicted its healthy siblings’ fragments too. &lt;strong&gt;After:&lt;/strong&gt; the degrade is &lt;strong&gt;per-pack&lt;/strong&gt; — only the offending pack’s fragment is skipped, with an operator-visible &lt;code dir=&quot;auto&quot;&gt;WARNING&lt;/code&gt; naming it, and the healthy siblings still compose. &lt;code dir=&quot;auto&quot;&gt;strict&lt;/code&gt; callers (the diagnostic APIs and the fail-loud composition path) are unchanged and still raise on any malformed pack.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --cascade&lt;/code&gt; no longer silently drops asset- and template-kind nodes from its cascade report — it now names every one it did not cascade, and says so identically in all three places a cascade is reported.&lt;/strong&gt; (#3705; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-20-1&lt;/code&gt;) &lt;strong&gt;Before:&lt;/strong&gt; a cascade filtered out every node whose kind is not charter-activatable (&lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt;) and then never mentioned them, so a pack whose executable check hung off an asset was both unreachable and unreported — the operator saw a successful cascade with no hint that anything had been left out, and nothing in the output distinguished “there was nothing to cascade” from “everything was dropped”. &lt;strong&gt;After:&lt;/strong&gt; each filtered node gets its own line — &lt;code dir=&quot;auto&quot;&gt;Not cascaded: &amp;#x3C;kind&gt;/&amp;#x3C;config-id&gt; (kind not charter-activatable)&lt;/code&gt; — resolved to the config-stem id, never capped or truncated; and when a cascade resolves &lt;em&gt;zero&lt;/em&gt; activatable targets because every referenced node was kind-filtered, that is stated explicitly rather than presented as a successful no-op. The same wording comes from one shared helper in all three consumers — the &lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt; report, the no-cascade warning, and &lt;code dir=&quot;auto&quot;&gt;charter deactivate --cascade&lt;/code&gt; — so the three can’t drift. Kind-filtering stays distinct from scope-narrowing: a node excluded by &lt;code dir=&quot;auto&quot;&gt;--cascade-scope&lt;/code&gt; still reports as &lt;code dir=&quot;auto&quot;&gt;Skipped (out of scope)&lt;/code&gt;, never as not-cascaded. &lt;strong&gt;This is a visibility fix only.&lt;/strong&gt; Which kinds are charter-activatable is unchanged and deliberately not reopened: the exclusion of &lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; remains the recorded policy of ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-20-1&lt;/code&gt;. Actually invoking a pack-shipped code asset as a gate handler stays tracked separately as #2599.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now gitignores the &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; execution-worktrees root, and &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; backfills the entry into existing projects.&lt;/strong&gt; (#3689) &lt;strong&gt;Before:&lt;/strong&gt; the only code that ever excluded &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; was the 0.13.1 migration, which writes the local-only &lt;code dir=&quot;auto&quot;&gt;.git/info/exclude&lt;/code&gt; and never runs for projects stamped ≥ 0.13.1 — so on every project initialised since then, the first mission worktree made the main checkout’s &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; show &lt;code dir=&quot;auto&quot;&gt;?? .worktrees/&lt;/code&gt; permanently, and a stray &lt;code dir=&quot;auto&quot;&gt;git add -A&lt;/code&gt; staged an entire nested checkout; several code paths (&lt;code dir=&quot;auto&quot;&gt;agent/workflow.py&lt;/code&gt; FR-002(b), &lt;code dir=&quot;auto&quot;&gt;workflow_executor.py&lt;/code&gt;) already assumed the root was ignored. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; is a first-class &lt;code dir=&quot;auto&quot;&gt;IGNORED&lt;/code&gt; surface in the state contract (&lt;code dir=&quot;auto&quot;&gt;worktrees_root&lt;/code&gt;), so fresh &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; writes it to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; through the existing &lt;code dir=&quot;auto&quot;&gt;get_runtime_gitignore_entries()&lt;/code&gt; path, and a new &lt;code dir=&quot;auto&quot;&gt;3.2.6rc3_worktrees_gitignore_backfill&lt;/code&gt; migration (sibling to the #3435 lint-report backfill, firing even on projects already stamped 3.2.6rc3) adds it to already-initialised projects — including via &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; rather than &lt;code dir=&quot;auto&quot;&gt;info/exclude&lt;/code&gt;, so the coverage travels with clones. A real-git regression test pins the observable: after the backfill, a checkout under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; is invisible to &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The off-PR &lt;code dir=&quot;auto&quot;&gt;performance.yml&lt;/code&gt; pipeline no longer red-fails every domain that has no perf tests yet (or no committed baseline) — a &lt;code dir=&quot;auto&quot;&gt;set -e&lt;/code&gt; footgun defeated its own tolerance guard (&lt;code dir=&quot;auto&quot;&gt;#3669&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-22-1&lt;/code&gt;).&lt;/strong&gt; The per-domain compare step ran &lt;code dir=&quot;auto&quot;&gt;pytest … ; ec=$?; if …&lt;/code&gt; under the Actions default shell (&lt;code dir=&quot;auto&quot;&gt;bash -e -o pipefail&lt;/code&gt;). Under &lt;code dir=&quot;auto&quot;&gt;set -e&lt;/code&gt;, a bare &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt; line exiting non-zero &lt;strong&gt;aborts the step before &lt;code dir=&quot;auto&quot;&gt;ec=$?&lt;/code&gt; runs&lt;/strong&gt;, so the intended allow-list for exit 5 (no &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.performance&lt;/code&gt; tests under the domain’s paths — expected during the ADR’s incremental per-domain migration) and exit 4 (&lt;code dir=&quot;auto&quot;&gt;pytest-benchmark&lt;/code&gt; USAGE_ERROR when no baseline exists to compare against) never took effect. A first manual &lt;code dir=&quot;auto&quot;&gt;workflow_dispatch&lt;/code&gt; proved it: 5 of 17 legs (&lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;missions&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;dashboard&lt;/code&gt;) — exactly the domains with zero perf-marked tests — failed on pytest exit 5. &lt;strong&gt;Fix:&lt;/strong&gt; keep the pytest invocation in an AND-OR list (&lt;code dir=&quot;auto&quot;&gt;… || ec=$?&lt;/code&gt;, with &lt;code dir=&quot;auto&quot;&gt;ec&lt;/code&gt; pre-initialized to 0) so &lt;code dir=&quot;auto&quot;&gt;set -e&lt;/code&gt; can’t abort it and the true exit code reaches the guard. Empty/no-baseline domains now pass as designed; a genuine statistical regression (exit 1) still fails its leg. The sibling &lt;code dir=&quot;auto&quot;&gt;--benchmark-save&lt;/code&gt; step was already correctly guarded with &lt;code dir=&quot;auto&quot;&gt;|| test $? -eq 5&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A custom mission family no longer crashes the work-package CLI guard, and a governance profile that selects an artifact that doesn’t exist now fails loudly instead of silently vanishing.&lt;/strong&gt; (#3658, closes #3627, closes #3633, addresses #3629) Two doctrine-authoring footguns are closed. &lt;strong&gt;Before:&lt;/strong&gt; (1) running a &lt;em&gt;custom&lt;/em&gt; mission family that named a step &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; hit the WP-iteration guard, which raised an uncaught &lt;code dir=&quot;auto&quot;&gt;UnregisteredMissionFamilyError&lt;/code&gt; and aborted the command — an unregistered family has no guard table to enforce, so the crash was pure collateral; and (2) a &lt;code dir=&quot;auto&quot;&gt;governance-profile.yaml&lt;/code&gt; whose &lt;code dir=&quot;auto&quot;&gt;selected_*&lt;/code&gt; list named a nonexistent artifact was &lt;em&gt;silently&lt;/em&gt; projected into a phantom auto-minted graph node at generation time, so a typo in a governance selection disappeared without a word instead of being caught. &lt;strong&gt;After:&lt;/strong&gt; the WP-iteration guard catches that one exception narrowly and degrades to “no guard failures” for unregistered families (registered families — &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;, … — keep byte-identical guard coverage); and DRG generation now fails loud with a &lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt; naming any unresolved governance scope-edge target, before the phantom-mint step, mirroring the existing operating-procedure fail-loud precedent. Also documents the &lt;code dir=&quot;auto&quot;&gt;Relation.SCOPE&lt;/code&gt; two-grain overload as deliberate accepted debt (ADR amendment) rather than a bug to split. The remaining #3629 item (deprecating the dead &lt;code dir=&quot;auto&quot;&gt;context-sources&lt;/code&gt; profile fields) was subsequently completed in mission &lt;code dir=&quot;auto&quot;&gt;doctrine-drg-silent-drop-boundary&lt;/code&gt; — the block is now removed from the agent-profile schema (see the Breaking entry above).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The weekly flake-report workflow no longer crashes on its first live run — it requested two &lt;code dir=&quot;auto&quot;&gt;gh run list&lt;/code&gt; JSON fields that don’t exist (mission &lt;code dir=&quot;auto&quot;&gt;ci-flake-report-workflow-01M0M9D8&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;scripts/ci/flake_report_cli.py&lt;/code&gt; asked &lt;code dir=&quot;auto&quot;&gt;gh run list --json&lt;/code&gt; for &lt;code dir=&quot;auto&quot;&gt;pullRequests&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;isDraft&lt;/code&gt;, which are exposed by &lt;code dir=&quot;auto&quot;&gt;gh run view&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;gh pr&lt;/code&gt; but &lt;strong&gt;not&lt;/strong&gt; by &lt;code dir=&quot;auto&quot;&gt;gh run list&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;gh&lt;/code&gt; exits non-zero with &lt;code dir=&quot;auto&quot;&gt;Unknown JSON field: &quot;pullRequests&quot;&lt;/code&gt;, aborting the whole report. The golden fixture tests never caught it because they read a recorded &lt;code dir=&quot;auto&quot;&gt;runs.json&lt;/code&gt; side-channel instead of shelling out to live &lt;code dir=&quot;auto&quot;&gt;gh&lt;/code&gt;. &lt;strong&gt;Fix:&lt;/strong&gt; drop the two unsupported fields from the live request — &lt;code dir=&quot;auto&quot;&gt;pr_number&lt;/code&gt; stays &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; on the live path and &lt;code dir=&quot;auto&quot;&gt;pr_identity&lt;/code&gt; falls back to &lt;code dir=&quot;auto&quot;&gt;headBranch&lt;/code&gt; exactly as its push-event branch was already designed to, and &lt;code dir=&quot;auto&quot;&gt;draft&lt;/code&gt; was never read anywhere. The recorded fixture keeps both keys and &lt;code dir=&quot;auto&quot;&gt;_run_from_entry&lt;/code&gt; still reads them tolerantly via &lt;code dir=&quot;auto&quot;&gt;.get()&lt;/code&gt;, so all 111 golden tests stay green; only the live &lt;code dir=&quot;auto&quot;&gt;gh run list&lt;/code&gt; call changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Legacy PR-bound missions no longer try to finalize planning artifacts onto protected &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;.&lt;/strong&gt; (#2938) &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; now recognizes the legacy shape that conflated a protected final target with its planning branch and requires the operator to name the otherwise-unprovable planning ref with &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt;. From the owning checkout it atomically persists that ref as &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; while retaining the protected destination as &lt;code dir=&quot;auto&quot;&gt;merge_target_branch&lt;/code&gt;; foreign linked-worktree writes fail closed. Linked-worktree branch context is still read through the canonical checkout-identity seam, and &lt;code dir=&quot;auto&quot;&gt;--validate-only&lt;/code&gt; remains byte-, index-, HEAD-, status-, and ref-stable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The pre-review gate can no longer pass a work package on an unverified or mis-captured test baseline — closing two false-green paths that let a real regression slip through review.&lt;/strong&gt; (#3657, closes #3611, closes #3612) The gate compares a work package’s tests against a baseline before it can move to review; two defects made that comparison unsound. &lt;strong&gt;Before:&lt;/strong&gt; (1) the baseline and the head side resolved &lt;code dir=&quot;auto&quot;&gt;review.test_command&lt;/code&gt; from &lt;em&gt;different&lt;/em&gt; checkouts — capture read it from the planning root while the head gate read it from the lane worktree, whose &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; can lack the setting — so the two sides silently picked different scope sources and the &lt;code dir=&quot;auto&quot;&gt;SOURCE_MISMATCH&lt;/code&gt; safety check never fired; and (2) a declared-command baseline was captured without a shell and without substituting &lt;code dir=&quot;auto&quot;&gt;{output_file}&lt;/code&gt; (so &lt;code dir=&quot;auto&quot;&gt;$VAR&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;~&lt;/code&gt; and the artifact path never resolved), then stored a failure count as if it were the suite size — fabricating a plausible-but-wrong baseline that could read as a clean pass. &lt;strong&gt;After:&lt;/strong&gt; scope-source &lt;em&gt;selection&lt;/em&gt; always resolves from the single planning root (tests still &lt;em&gt;run&lt;/em&gt; in the worktree), so both sides agree or the mismatch is caught; declared-command capture now runs through the same &lt;code dir=&quot;auto&quot;&gt;sh -c&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;{output_file}&lt;/code&gt; substitution the head runner uses, reaps the whole process group on timeout, and &lt;em&gt;refuses to store&lt;/em&gt; an ambiguous clean/no-artifact run — degrading to an honest &lt;code dir=&quot;auto&quot;&gt;UNVERIFIED_BASELINE&lt;/code&gt; instead of a false pass. A stored declared-command baseline’s &lt;code dir=&quot;auto&quot;&gt;total&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;passed&lt;/code&gt; counts are still derived from failure identities rather than real JUnit suite sizes (documented in-code; it does not affect gate verdicts, which diff by failing-test identity) — worth a follow-up if a reporting consumer needs true counts.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync now&lt;/code&gt; no longer strands the whole event journal when the server answers HTTP 412 (CLI/server sync-protocol skew) — it halts the pass, keeps every event retryable, and prints the server’s own upgrade/pin guidance.&lt;/strong&gt; (#1553; supersedes the first cut in PR #3637) The SaaS batch endpoint’s compatibility handshake (keyed on &lt;code dir=&quot;auto&quot;&gt;X-SpecKitty-Protocol-Version&lt;/code&gt;) returns 412 with &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt; ∈ {&lt;code dir=&quot;auto&quot;&gt;client-too-old&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;client-too-new&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;client-protocol-unparseable&lt;/code&gt;}, an &lt;code dir=&quot;auto&quot;&gt;error_description&lt;/code&gt;, and a single &lt;code dir=&quot;auto&quot;&gt;sync_protocol.upgrade_guidance&lt;/code&gt; string. &lt;strong&gt;Before:&lt;/strong&gt; a 412 fell into the generic transient bucket, so one &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; pass POSTed every batch in the journal and got the same 412 each time, with no operator-visible explanation; the first fix attempt (PR #3637) instead mapped 412 to &lt;code dir=&quot;auto&quot;&gt;terminal_failed&lt;/code&gt;, which &lt;em&gt;parked&lt;/em&gt; every event the pass touched — and because parked rows are excluded from selection forever and the delivery &lt;code dir=&quot;auto&quot;&gt;target_id&lt;/code&gt; does not change on upgrade, the journal would never have been redelivered after the operator upgraded, while the drain loop still counted the parking as progress and POSTed (and parked) the entire backlog in one pass. It also hardcoded “upgrade … pip install —upgrade spec-kitty-cli”, which is the wrong instruction for a too-&lt;em&gt;new&lt;/em&gt; client (the server says pin), and mis-described the trigger header. &lt;strong&gt;After:&lt;/strong&gt; each correlated 412 maps to &lt;code dir=&quot;auto&quot;&gt;transient&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;known_no_effect&lt;/code&gt; (retained, re-selected on the next run) carrying the server’s &lt;code dir=&quot;auto&quot;&gt;sync_protocol.upgrade_guidance&lt;/code&gt; (then &lt;code dir=&quot;auto&quot;&gt;error_description&lt;/code&gt;, then a neutral fallback) as the error and its &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt; as the error category; the batch driver halts the pass on the first 412 even when another selected row failed locally before transport, instead of advancing to the next batch; &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; prints the halt notice plus the server’s guidance right after the counts, and the wholesale-transient exit message names the protocol skew instead of blaming auth or batch size. Parking (&lt;code dir=&quot;auto&quot;&gt;terminal_failed&lt;/code&gt;) stays reserved for per-event-permanent failures (oversized, refused). The CLI does not yet send &lt;code dir=&quot;auto&quot;&gt;X-SpecKitty-Protocol-Version&lt;/code&gt; (it sends the legacy &lt;code dir=&quot;auto&quot;&gt;X-Spec-Kitty-Sync-Protocol&lt;/code&gt;, which the handshake fails open on), so this change is the recovery path for when it does — advertising the new header is deliberately out of scope here.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Docs-freshness metadata gates are now diff-scoped on pull requests, so a docs PR is no longer failed by violations on pages it never touched.&lt;/strong&gt; (#3316) The &lt;code dir=&quot;auto&quot;&gt;audience:&lt;/code&gt;-reference resolver (&lt;code dir=&quot;auto&quot;&gt;scripts/docs/audience_resolver.py&lt;/code&gt;) and the &lt;code dir=&quot;auto&quot;&gt;description&lt;/code&gt; metadata gate (&lt;code dir=&quot;auto&quot;&gt;scripts/docs/description_length_check.py&lt;/code&gt;) both ran whole-tree in strict mode on every PR. &lt;strong&gt;Before:&lt;/strong&gt; any pre-existing dangling persona reference or out-of-band/duplicate &lt;code dir=&quot;auto&quot;&gt;description&lt;/code&gt; anywhere under &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; redded an unrelated PR’s docs-freshness job, and the only way through was to fix someone else’s page. &lt;strong&gt;After:&lt;/strong&gt; on &lt;code dir=&quot;auto&quot;&gt;pull_request&lt;/code&gt; both gates take &lt;code dir=&quot;auto&quot;&gt;--changed-from &amp;#x3C;base-sha&gt;&lt;/code&gt; and report violations only for changed, published &lt;code dir=&quot;auto&quot;&gt;docs/**/*.md&lt;/code&gt; pages; the &lt;code dir=&quot;auto&quot;&gt;push:main&lt;/code&gt; run stays whole-tree (it is the backstop for persona deletions/renames that touch no referrer, the same accepted limitation as #3312). Description uniqueness stays corpus-aware — a changed page that duplicates an &lt;em&gt;unchanged&lt;/em&gt; peer still fails and names the peer — and the diff-scoped path re-asserts the published-corpus non-vacuity floor exactly as the whole-tree path does, so a collapsed &lt;code dir=&quot;auto&quot;&gt;docfx.json&lt;/code&gt; page set is still a gate malfunction (exit 2) on a PR. An unresolvable base ref fails closed (exit 2); a resolved diff touching no published docs is a clean pass.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; no longer gitignores all of &lt;code dir=&quot;auto&quot;&gt;.cursor/&lt;/code&gt; for teams that version-control their own Cursor rules.&lt;/strong&gt; (#2498) &lt;code dir=&quot;auto&quot;&gt;GitignoreManager.protect_all_agents()&lt;/code&gt; wrote a blanket &lt;code dir=&quot;auto&quot;&gt;.cursor/&lt;/code&gt; entry for every project, regardless of which agents were selected. &lt;strong&gt;Before:&lt;/strong&gt; a repo that tracked &lt;code dir=&quot;auto&quot;&gt;.cursor/rules/contributing.mdc&lt;/code&gt; (or any other file under &lt;code dir=&quot;auto&quot;&gt;.cursor/&lt;/code&gt;) alongside Spec Kitty’s own &lt;code dir=&quot;auto&quot;&gt;.cursor/rules/spec-kitty.mdc&lt;/code&gt; found the whole directory gitignored after &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;, making the team’s own rules unstageable. &lt;strong&gt;After:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;cursor&lt;/code&gt; entry in &lt;code dir=&quot;auto&quot;&gt;AGENT_DIRECTORIES&lt;/code&gt; is narrowed to only the paths Spec Kitty itself generates (&lt;code dir=&quot;auto&quot;&gt;.cursor/rules/spec-kitty.mdc&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.cursor/commands/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.cursor/skills/&lt;/code&gt;), matching the existing &lt;code dir=&quot;auto&quot;&gt;.github/copilot/&lt;/code&gt; precedent; &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; removes only the exact legacy &lt;code dir=&quot;auto&quot;&gt;.cursor/&lt;/code&gt; row proven to sit in Spec Kitty’s auto-managed block and backfills the three narrow entries. Unmarked or otherwise unattributable blanket variants are preserved with manual-remediation guidance so an upgrade never deletes operator security policy by filename heuristic. The migration and manager also reject symlinked or non-UTF-8 &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; files without modifying them, including dangling links, so upgrade cannot write outside the project or silently discard bytes. &lt;code dir=&quot;auto&quot;&gt;protect_selected_agents()&lt;/code&gt; also had a latent bug where an agent name owning more than one registry entry silently kept only the last one — fixed alongside, since narrowing &lt;code dir=&quot;auto&quot;&gt;cursor&lt;/code&gt; to three rows would otherwise have surfaced it. &lt;code dir=&quot;auto&quot;&gt;.cursor/skills/&lt;/code&gt; stays ignored as a &lt;em&gt;declared&lt;/em&gt; Spec Kitty skill root (&lt;code dir=&quot;auto&quot;&gt;AGENT_SKILL_CONFIG&lt;/code&gt;, not yet populated by the installer); &lt;code dir=&quot;auto&quot;&gt;.cursor/hooks.json&lt;/code&gt; is intentionally &lt;strong&gt;not&lt;/strong&gt; ignored (team-owned; only written on explicit &lt;code dir=&quot;auto&quot;&gt;agent config set lint_on_edit&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 upgrade&lt;/code&gt; now backfills &lt;code dir=&quot;auto&quot;&gt;.kittify/lint-report.json&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; on already-initialised projects.&lt;/strong&gt; (#3435) &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter lint&lt;/code&gt; writes &lt;code dir=&quot;auto&quot;&gt;.kittify/lint-report.json&lt;/code&gt; as a side effect (the dashboard lint tile and &lt;code dir=&quot;auto&quot;&gt;sync/lint_report_staging.py&lt;/code&gt; read it back, so ignoring — not suppressing — the file is the right remedy). &lt;strong&gt;Before:&lt;/strong&gt; fresh &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; projects got the entry via the gitignore contract, but projects initialised earlier were left with an untracked file that tripped &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt;’s dirty-tree guard. &lt;strong&gt;After:&lt;/strong&gt; the new &lt;code dir=&quot;auto&quot;&gt;3.2.6rc3_lint_report_gitignore_backfill&lt;/code&gt; migration (&lt;code dir=&quot;auto&quot;&gt;m_3_2_6rc3_lint_report_gitignore_backfill&lt;/code&gt;) adds the entry idempotently on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;, sibling to the 3.2.4/3.2.5 gitignore backfills.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker sync push&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;sync run&lt;/code&gt; now show which authority a SaaS-backed sync used, matching &lt;code dir=&quot;auto&quot;&gt;sync pull&lt;/code&gt;.&lt;/strong&gt; (#1221) &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;sync pull&lt;/code&gt;’s human-readable output already rendered the SaaS envelope’s &lt;code dir=&quot;auto&quot;&gt;identity_path&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;- provider: …&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;- type: …&lt;/code&gt;) so a user could tell whether an operation ran under workspace installation authority or their own linked provider account, but &lt;code dir=&quot;auto&quot;&gt;sync push&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;sync run&lt;/code&gt; silently dropped the same field from their human output even though the SaaS client returns it identically for all three operations — a user debugging a permission failure on push/run had no CLI-visible way to see which authority was used, only readable by re-running with &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;sync push&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;sync run&lt;/code&gt; render &lt;code dir=&quot;auto&quot;&gt;identity_path&lt;/code&gt; the same way &lt;code dir=&quot;auto&quot;&gt;sync pull&lt;/code&gt; does; JSON output (&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;) was already unaffected since it echoes the raw envelope.&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 command-files&lt;/code&gt; no longer false-positives 15 “missing” errors on every globalized project.&lt;/strong&gt; (#1794) The check still resolved each agent’s command files at the project-local &lt;code dir=&quot;auto&quot;&gt;.claude/commands/&lt;/code&gt;-style path, but the &lt;code dir=&quot;auto&quot;&gt;3.1.2_globalize_commands&lt;/code&gt; migration (and &lt;code dir=&quot;auto&quot;&gt;3.2.0a4_safe_globalize_commands&lt;/code&gt; after it) moved the canonical files to the user-global command dir and intentionally leaves the project-local files absent — &lt;code dir=&quot;auto&quot;&gt;doctor skills&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Slash Commands&lt;/code&gt; was updated for this globalized layout, &lt;code dir=&quot;auto&quot;&gt;doctor command-files&lt;/code&gt; was not. &lt;strong&gt;Before:&lt;/strong&gt; every configured agent’s 15 consumer command files reported &lt;code dir=&quot;auto&quot;&gt;&quot;missing&quot;&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; on a correctly globalized project, drowning out any real command-file regression signal. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;check_command_file_health&lt;/code&gt; resolves each agent’s files via &lt;code dir=&quot;auto&quot;&gt;get_global_command_dir&lt;/code&gt; (the same helper the healthy &lt;code dir=&quot;auto&quot;&gt;Slash Commands&lt;/code&gt; audit already uses), so a globalized project with healthy global files reports zero issues; the &lt;code dir=&quot;auto&quot;&gt;file&lt;/code&gt; field in table/&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output now reports the absolute global path rather than a project-relative one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Hosted event-sync delivers again for consented projects: &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; no longer rejects the server’s own preflight success.&lt;/strong&gt; (#3564, closes #3620) &lt;strong&gt;Before:&lt;/strong&gt; #3293 shipped a hard, unconditional client-side admission gate whose writer (&lt;code dir=&quot;auto&quot;&gt;AdmissionOperationService.perform&lt;/code&gt;) has no production caller and whose server endpoint (&lt;code dir=&quot;auto&quot;&gt;PUT …/sync-admission/&lt;/code&gt;) returns 404 in production — so every consented project had &lt;code dir=&quot;auto&quot;&gt;delivery_target = None&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; gated on &lt;code dir=&quot;auto&quot;&gt;admission_not_current&lt;/code&gt; (misreported as “not authenticated”), and &lt;code dir=&quot;auto&quot;&gt;delivery_results&lt;/code&gt; stayed 0 despite thousands of queued entries; separately, &lt;code dir=&quot;auto&quot;&gt;import-history --apply&lt;/code&gt; required a correlated per-event &lt;code dir=&quot;auto&quot;&gt;results[]&lt;/code&gt; the deployed preflight never sends, classifying a server success as a rejection and masking the real server diagnostic behind always-zero (non-mutating) reconciliation counters. &lt;strong&gt;After:&lt;/strong&gt; the admission gate is conditioned on server capability — it defaults non-strict and mints a labeled local self-admission (&lt;code dir=&quot;auto&quot;&gt;local-nonstrict:&amp;#x3C;origin&gt;&lt;/code&gt;) so a consented, authenticated project delivers via the existing local-consent-gated path, enforcing strict admission only on an explicit signal (a dormant hook for when the paired server half &lt;code dir=&quot;auto&quot;&gt;spec-kitty-saas#795&lt;/code&gt; lands); the misleading auth message is replaced by the real gate reason; and &lt;code dir=&quot;auto&quot;&gt;import-history --apply&lt;/code&gt; honors a &lt;code dir=&quot;auto&quot;&gt;{accepted: true}&lt;/code&gt; preflight with no &lt;code dir=&quot;auto&quot;&gt;results[]&lt;/code&gt; (staying fail-closed on any malformed or partial verdict) while surfacing the server’s structured diagnostic. The self-admission it carries on the wire is honestly self-labeled (&lt;code dir=&quot;auto&quot;&gt;local-nonstrict:…&lt;/code&gt;) and never poses as a server-issued proof — a future strict server rejects it cleanly at ingest (degrade, not corruption) rather than being fooled — and the consent boundary is unchanged. Live end-to-end delivery may still be bounded by independent server-side event-shape validation (schema drift, historical transition semantics &lt;code dir=&quot;auto&quot;&gt;#3017&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3001&lt;/code&gt;), tracked separately.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement --base &amp;#x3C;ref&gt;&lt;/code&gt; now actually roots the lane on the ref you pass — and hard-errors instead of faking success when it can’t — closing the P0 (#3571) that silently pulled unrelated work into a supposedly independent lane.&lt;/strong&gt; (#3616, closes #3571) &lt;strong&gt;Before:&lt;/strong&gt; on a coordination-topology mission (the default), &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; printed a green &lt;code dir=&quot;auto&quot;&gt;→ Using explicit base ref&lt;/code&gt; line while the lane descended from an entirely unrelated branch and did &lt;strong&gt;not&lt;/strong&gt; contain your base as an ancestor — the override was smuggled through a field the dominant allocation path never read, so it was silently a no-op that also misreported success; unrelated pending work leaked into the lane, invalidating review scope. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; is threaded as an explicit parameter into the topology-aware allocator, so a fresh no-dependency lane descends from &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;ref&gt;&lt;/code&gt; alone. On any route that cannot honor the base — reusing an existing lane worktree, re-attaching a crash-recovered lane branch, a dependency-bearing lane whose coord-descended tips would need re-parenting, or a base detached from the recorded planning commit — the command now &lt;strong&gt;hard-errors&lt;/strong&gt; (typed &lt;code dir=&quot;auto&quot;&gt;UnhonorableBaseError&lt;/code&gt;, machine-readable in the orchestrator envelope) with a message naming the route, work package, and unhonored base, rather than printing a fabricated success line. The success line prints only after the lane has actually been parented on the ref. The &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; gate measures against the lane’s real recorded base, and the legacy (&lt;code dir=&quot;auto&quot;&gt;#1684&lt;/code&gt;) &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; route is preserved byte-for-byte. The broader two-route unification that prevents this class of drift from recurring is tracked as follow-up (#3460 / #3462 / #3536).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Charter/runtime gates now honor the mission entity you actually declared, so non-canonical actions and types stop being silently starved and typo’d types fail loud.&lt;/strong&gt; (#3596, #3598, #3599, #3597, #3407, #3615) Five charter/runtime surfaces were deciding delivery, tolerance, and gating by membership in a hardcoded 4-token set or a project-wide flag instead of the declared entity. &lt;strong&gt;Before:&lt;/strong&gt; a declared non-bootstrap action (&lt;code dir=&quot;auto&quot;&gt;tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;retrospect&lt;/code&gt;) short-circuited to an empty &lt;code dir=&quot;auto&quot;&gt;compact&lt;/code&gt; bundle even though it ships doctrine grain; a typo’d &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;softwaer-dev&lt;/code&gt;) resolved silently with fabricated provenance; a custom mission type could not gate on its own artifact filenames; a &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission’s &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; step aliased into software-dev’s WP-iteration guard. &lt;strong&gt;After:&lt;/strong&gt; an action delivers &lt;code dir=&quot;auto&quot;&gt;bootstrap&lt;/code&gt; iff the merged doctrine graph declares its &lt;code dir=&quot;auto&quot;&gt;action:&amp;#x3C;type&gt;/&amp;#x3C;step&gt;&lt;/code&gt; node (the 4-token fast path and single-graph-load budget preserved); an unregistered &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; with no matching per-type &lt;code dir=&quot;auto&quot;&gt;governance-profile.yaml&lt;/code&gt; at the project or org layer raises &lt;code dir=&quot;auto&quot;&gt;UnknownMissionTypeError&lt;/code&gt; (your mission-type &lt;em&gt;activation&lt;/em&gt; restriction is unchanged — a canonical type you did not activate still hard-fails); artifact filenames resolve from the single per-type &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;path_pattern&lt;/code&gt; authority (the four built-ins byte-identical) and the stray empty &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; that satisfied existence gates is gone; and the CLI-guard path routes to the mission’s real guard family. &lt;strong&gt;Program ordering:&lt;/strong&gt; requires the M0 &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-mission-type&lt;/code&gt; gate (above) to have run first. Governance and the four named red-by-design test reversals are recorded in ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-21-1-charter-gate-predicate-inversion&lt;/code&gt;. (PR #3617)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A mission type’s type-wide governance now reaches the agent, and a procedure’s authored rationale is no longer silently dropped — closing the DRG projection gaps where authored doctrine validated, loaded, then vanished before delivery (#3604 / #3605 / #3488).&lt;/strong&gt; (#3628; mission rc3-drg-projection-completeness; closes #3604, #3605) &lt;strong&gt;Before:&lt;/strong&gt; a mission type’s &lt;code dir=&quot;auto&quot;&gt;governance-profile.yaml&lt;/code&gt; selections (its directives/tactics/paradigms/styleguides) were never projected into the doctrine reachability graph, so a &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;&lt;/strong&gt; mission — which authors &lt;em&gt;only&lt;/em&gt; type-wide governance — cascaded to &lt;strong&gt;nothing&lt;/strong&gt;; separately, a procedure reference’s authored &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt; rationale was dropped at the graph extractor while directive/tactic/paradigm references kept theirs. &lt;strong&gt;After:&lt;/strong&gt; type-wide governance projects as &lt;code dir=&quot;auto&quot;&gt;mission_type --scope--&gt; &amp;#x3C;governance&gt;&lt;/code&gt; edges for every built-in mission type that declares type-wide selections — documentation, plan, and research (software-dev selects none at the type level and is unchanged) — so a &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission now cascades to its directive, 9 tactics, 3 paradigms, and styleguide, procedure references carry their &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt; into the graph, and a new structural test &lt;strong&gt;binds the projection (emit) and profile-rendering (delivery) seams&lt;/strong&gt; so a channel wired into one but not the other fails a test instead of silently diverging. The profile-delivery path itself needed no code change (verified already correct on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; — the fix is the anti-divergence guard, not a re-fix). The canonical &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; relation authority was updated in lockstep to reflect that scope edges now also originate from mission-type nodes. &lt;strong&gt;Operator note:&lt;/strong&gt; because previously-dropped governance is now reachable, activating a mission type through the charter cascade surfaces a larger activation set than before (e.g. &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; grows from an empty cascade to its full governance closure).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;implement --base &amp;#x3C;ref&gt;&lt;/code&gt; now records the correct base provenance even when &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;ref&gt;&lt;/code&gt; diverges from the mission’s coordination line — hardening the #3571 fix so the &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; gate can’t silently fall back to the wrong base on exactly those lanes.&lt;/strong&gt; (#3571 follow-up) &lt;strong&gt;Before:&lt;/strong&gt; a freshly-created lane rooted on a divergent &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; was misdetected as a &lt;em&gt;reuse&lt;/em&gt; of an existing lane (the recorded planning-commit merge landing on top counted as “commits beyond base”), so its &lt;code dir=&quot;auto&quot;&gt;base_commit&lt;/code&gt; provenance was never written — and the &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; gate’s recorded-honored-base lookup then found nothing and fell back to the topology guess, mis-scoping the review of that lane. &lt;strong&gt;After:&lt;/strong&gt; lane reuse is detected structurally (the lane worktree or branch already exists), which is immune to base divergence — a fresh &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; lane is correctly recorded with its honored base, a genuine second work package in the same lane still reuses it, and a crash-recovered lane still re-attaches.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Fail-loud sweep: six code paths that decided correctly but told the operator nothing now emit a legible signal.&lt;/strong&gt; (#3578, #3548, #3517, #3412, #2991; interim #3590) A recurring silent-drop defect class — the machine-readable half of a contract intact (correct &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt;, byte-stable file, truthy return) while the human-readable half that tells an operator what happened is dropped — is closed at six ground-level sites. Each emits through an &lt;strong&gt;existing&lt;/strong&gt; operator-visible surface (no new swallowable sink) and lands an issue-pinned red-first regression that asserts on the &lt;em&gt;signal&lt;/em&gt;, not merely a code or shape:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#3578&lt;/strong&gt; — a rollback to &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; now surfaces &lt;code dir=&quot;auto&quot;&gt;subtasks_reset_count&lt;/code&gt; as &lt;strong&gt;both&lt;/strong&gt; a human line &lt;strong&gt;and&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; field, and names the two co-applied siblings (runtime-claim release, review-override clear) that were previously silent. The subtask roster now distinguishes a subtask &lt;strong&gt;completed in an earlier cycle&lt;/strong&gt; from one &lt;strong&gt;never started&lt;/strong&gt;, so the flat reset no longer conflates work-state with review-state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3548&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;orchestrator_api&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;_fail()&lt;/code&gt; no longer drops the human-readable &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 (16 of 33 call sites had been silently losing their explanation, preferentially on the most actionable errors); both halves now reach the operator in the envelope.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3517&lt;/strong&gt; — the sync emitter no longer returns a durably-unqueued event as truthy and publication-eligible: &lt;code dir=&quot;auto&quot;&gt;_emit&lt;/code&gt; consumes &lt;code dir=&quot;auto&quot;&gt;_route_event&lt;/code&gt;’s durability bool, warns, and returns &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; so the &lt;code dir=&quot;auto&quot;&gt;events.py&lt;/code&gt; publish gates skip it. The never-raise contract is preserved; the bounded-retry redesign stays with #3549’s sync owners.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3412&lt;/strong&gt; — a YAML-syntax-malformed &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt; now fails loud (a typed &lt;code dir=&quot;auto&quot;&gt;MalformedManifestError&lt;/code&gt; naming the path) &lt;strong&gt;distinct from “absent”&lt;/strong&gt;, instead of degrading to &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; and masquerading as “not found”; a genuinely missing/unreadable file still reads as absent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2991&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; now warns when an &lt;code dir=&quot;auto&quot;&gt;SC-###&lt;/code&gt; success-criteria ref in a WP’s &lt;code dir=&quot;auto&quot;&gt;requirement_refs&lt;/code&gt; is discarded by the &lt;code dir=&quot;auto&quot;&gt;(?:FR|NFR|C)&lt;/code&gt; graph scanner, so an author never believes traceability exists when the ref silently vanished. &lt;code dir=&quot;auto&quot;&gt;SC&lt;/code&gt; is &lt;strong&gt;not&lt;/strong&gt; admitted as a first-class ref (the graph is unchanged) — the discard is merely signalled through the existing advisory-warning channel.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#3590 (interim, warn-only)&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; now emits an authoring-time, non-blocking warning when a &lt;strong&gt;code&lt;/strong&gt; work package’s acceptance criteria are observable only &lt;strong&gt;post-integration&lt;/strong&gt; (an action, not a diff) — so a WP that cannot be honestly reviewed while its lane is open is flagged at planning time. It &lt;strong&gt;never&lt;/strong&gt; blocks finalize and touches no terminal state, gate, or lane exit; the deep terminal-state fix is Mission M6 (#3550 / #3432 / #3433 / #2745).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer disobeys the operator’s own &lt;code dir=&quot;auto&quot;&gt;auto_commit&lt;/code&gt; opt-out, can no longer be blocked by its own generated files, and stops misreporting a successful or aborted run.&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;upgrade-command-hardening-01M0N5N4&lt;/code&gt;; #3651, #3654, #3653, #3392, #3376, #3393, #3390, #2491) A cluster of confirmed defects in the ~1,300-line &lt;code dir=&quot;auto&quot;&gt;cli/commands/upgrade.py&lt;/code&gt; — two duplicated orchestration branches with no shared seams — made upgrade fail on its own re-run, ignore the operator’s committed configuration, silently over-authorize a destructive repair, and misreport both success and failure. &lt;strong&gt;Before:&lt;/strong&gt; a project with previously-written read-only generated command files hit ~30 &lt;code dir=&quot;auto&quot;&gt;Errno 13 (Permission denied)&lt;/code&gt; errors on the next upgrade with no in-product remedy; &lt;code dir=&quot;auto&quot;&gt;auto_commit: false&lt;/code&gt; was ignored — upgrade committed its churn on the main checkout and every worktree regardless, one of ~8 other command paths that honor the setting; &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; also silently authorized &lt;code dir=&quot;auto&quot;&gt;offer_teamspace_mission_state_migration&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;repair_repo&lt;/code&gt;, a mutating repo rewrite) with no distinct prompt; a fully successful &lt;code dir=&quot;auto&quot;&gt;upgrade --project --yes&lt;/code&gt; could exit 1 and print no outcome (#3392); a worktree that failed mid-migration still stamped &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt;, misreporting readiness (#3376); the gitignore-backfill migration could gitignore paths it left tracked, leaving the tree permanently dirty (#3393); a &lt;code dir=&quot;auto&quot;&gt;PlacementMismatchError&lt;/code&gt; abort under-reported the mismatch and could leave phantom writes under &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; (#3390); and post-commit surface-repair writes could land after the single upgrade-churn commit, leaving dirty residue (#2491). &lt;strong&gt;After:&lt;/strong&gt; every generated/rewritable-but-read-only file routes through one canonical restore→write→strip-permission-bit writer, so a re-run over its own prior output completes and re-applies the read-only bit instead of erroring; the commit decision for both the main checkout and every worktree defers to &lt;code dir=&quot;auto&quot;&gt;get_auto_commit_default&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;core/agent_config.py&lt;/code&gt;), and when the config disables it and real churn exists, the command now says so in human-mode output (&lt;code dir=&quot;auto&quot;&gt;⚠ Changes were left uncommitted (auto_commit is disabled) — commit them yourself.&lt;/code&gt;) instead of staying silent; &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; authorizes only the invoked migrations — the mission-state repair is a separately-scoped, default-deny consent gate whose own failure can never sink an otherwise-completed upgrade; the two orchestration branches share a single post-migration finalizer that derives the exit code exactly once from one &lt;code dir=&quot;auto&quot;&gt;UpgradeOutcome&lt;/code&gt;, so a fully-successful run reliably exits 0 with a printed completion outcome and a worktree migration failure is surfaced honestly in the top-line result and exit code rather than downgraded to an invisible warning; and the placement-mismatch abort path and &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; report honestly with no phantom writes. A behavior-preserving characterization net (&lt;code dir=&quot;auto&quot;&gt;tests/upgrade/test_upgrade_char_net.py&lt;/code&gt;) pins the default (&lt;code dir=&quot;auto&quot;&gt;auto_commit&lt;/code&gt; unset/true) commit behavior byte-for-byte across the refactor.&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; now emits a commitlint-compliant commit subject for the &lt;code dir=&quot;auto&quot;&gt;analysis-report.md&lt;/code&gt; commit.&lt;/strong&gt; (#3678) The prior subject, &lt;code dir=&quot;auto&quot;&gt;&quot;Add analysis report for mission {slug}&quot;&lt;/code&gt;, carried no &lt;code dir=&quot;auto&quot;&gt;type(scope):&lt;/code&gt; prefix and failed &lt;code dir=&quot;auto&quot;&gt;commitlint.config.cjs&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;type-empty&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;subject-empty&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;type-enum&lt;/code&gt; rules outright. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;mission_record_analysis.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt; call now emits &lt;code dir=&quot;auto&quot;&gt;docs(record-analysis): record analysis report for mission {slug}&lt;/code&gt;, pinning &lt;code dir=&quot;auto&quot;&gt;type&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;docs&lt;/code&gt; per this repo’s own convention for tool-authored analyze/review commits (fixing the emitted subject rather than widening commitlint’s ignore regex).&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; frontmatter now records repo-relative &lt;code dir=&quot;auto&quot;&gt;input_artifacts.*.path&lt;/code&gt; values instead of absolute ones.&lt;/strong&gt; (ledger SK-63, FR-007/NFR-001/NFR-002) Hash-input paths (&lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;) were recorded as absolute filesystem paths, leaking a contributor’s local checkout layout (&lt;code dir=&quot;auto&quot;&gt;/home/&amp;#x3C;user&gt;/...&lt;/code&gt;) into a file every mission commits to git history — a problem on a public repo. &lt;strong&gt;After:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;analysis_report.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;_relativize_or_raise&lt;/code&gt; relativizes every hash-input path against its governing root (the repo root for spec/plan/tasks, the resolved canonical root for the charter) before it is written; a path that cannot be relativized against its governing root (e.g. a symlink escaping it) raises a typed &lt;code dir=&quot;auto&quot;&gt;PathRelativizationError&lt;/code&gt; instead of silently recording an absolute path. &lt;strong&gt;Format change:&lt;/strong&gt; any tooling that parses &lt;code dir=&quot;auto&quot;&gt;input_artifacts.*.path&lt;/code&gt; from a committed &lt;code dir=&quot;auto&quot;&gt;analysis-report.md&lt;/code&gt; must now expect a repo-relative path, not an absolute one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The dossier-emitter positional-call guard now catches attribute-chain and aliased-import call shapes it previously missed — test-only, no runtime behavior change.&lt;/strong&gt; (#3676) The guard’s own docstring had framed the gap as an accepted design boundary (“this guard does simple Name-based matching only… widening the detector to handle aliasing is explicitly deferred until a real aliased call site exists”), but a gate a caller can silently route around by either call shape isn’t evidence of anything for those shapes. &lt;strong&gt;Before:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_dossier_emitter_positional_guard.py&lt;/code&gt;’s detector matched only bare-&lt;code dir=&quot;auto&quot;&gt;Name&lt;/code&gt; positional calls to the guarded &lt;code dir=&quot;auto&quot;&gt;emit_*&lt;/code&gt; functions, so &lt;code dir=&quot;auto&quot;&gt;module.emit_artifact_indexed(...)&lt;/code&gt; (attribute-chain) and &lt;code dir=&quot;auto&quot;&gt;ei(...)&lt;/code&gt; where &lt;code dir=&quot;auto&quot;&gt;ei&lt;/code&gt; came from &lt;code dir=&quot;auto&quot;&gt;from ... import emit_artifact_indexed as ei&lt;/code&gt; (aliased-import) both passed through unflagged. &lt;strong&gt;After:&lt;/strong&gt; the detector resolves an attribute-chain call to its final attribute name, and resolves a same-file &lt;code dir=&quot;auto&quot;&gt;ImportFrom&lt;/code&gt; alias back to its original imported name via a syntactic alias map built once per file (attributing an aliased violation to the resolved original name, not the alias); two new positive-control fixtures — a planted attribute-chain call and a planted aliased-import call — fail (RED) against the pre-widening detector and pass (GREEN) against the post-widening one. No &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; file is touched; the guard lives entirely in &lt;code dir=&quot;auto&quot;&gt;tests/architectural/&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Expected-artifacts loading now uses one cached charter authority.&lt;/strong&gt; (#3770,
#3412) Runtime, resolver, dossier, and charter consumers share org-first
precedence and schema validation. Present malformed or unreadable manifests
fail loudly; only genuinely absent manifests degrade to &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt;. An
architectural gate forbids new direct model construction outside the
authority. See ADR 2026-08-31-1.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;326rc2---2026-08-20&quot;&gt;[3.2.6rc2] - 2026-08-20&lt;/h2&gt;
&lt;p&gt;&lt;em&gt;The 3.2.6rc2 candidate shipped 2026-08-20 (rc1 shipped 2026-08-12).&lt;/em&gt;&lt;/p&gt;
&lt;h3 id=&quot;-added-1&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Spec Kitty now ships a &lt;code dir=&quot;auto&quot;&gt;spk-doctrine-show-me&lt;/code&gt; skill that guides any agent to
explain work with compact, checkable visuals — the smallest diagram,
pseudocode, or tree that answers the question — recommended from the specify
and plan surfaces (&lt;code dir=&quot;auto&quot;&gt;#3528&lt;/code&gt;).&lt;/strong&gt; Before, agents had no shared doctrine for &lt;em&gt;when&lt;/em&gt;
a visual earns its place or &lt;em&gt;which&lt;/em&gt; shape fits the point (call tree, sequence,
state diagram, C4, or a &lt;code dir=&quot;auto&quot;&gt;diff&lt;/code&gt; over the matching tree), so visual explanations
were ad-hoc and often missing. The skill routes to Spec Kitty’s canonical
Mermaid, PlantUML, C4, and diagram-review sources — bundling byte-pinned
portable copies of the guides and themes so it keeps working once installed in
a consumer project — and documents faithful &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.status&lt;/code&gt; TUI rendering
from &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; (lifecycle lanes vs the five-group display, and done-progress vs
weighted-readiness, so a custom board never mislabels weighted readiness as
completed work). Adapted from HumanLayer’s MIT-licensed &lt;code dir=&quot;auto&quot;&gt;show-me&lt;/code&gt; skill with
full attribution and license notice preserved.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An organisation doctrine pack can now ship templates and mission-FSM
content, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; actually resolves them at runtime — before, an org
pack could declare a template or mission that no resolution path would ever
find (&lt;code dir=&quot;auto&quot;&gt;#3524&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3523&lt;/code&gt;).&lt;/strong&gt; The two forked template resolvers
(&lt;code dir=&quot;auto&quot;&gt;doctrine/resolver.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;specify_cli/runtime/resolver.py&lt;/code&gt;) and the FSM
mission-discovery walks consulted only the built-in, project-legacy, and
user-global tiers — &lt;code dir=&quot;auto&quot;&gt;resolve_org_roots()&lt;/code&gt; existed but nothing on those paths
called it, so a configured, validated, activated org pack stayed inert for
templates and mission discovery. Now an &lt;code dir=&quot;auto&quot;&gt;ORG&lt;/code&gt; tier sits between the
project-legacy and user-global tiers in the asset chain (6 tiers) and in FSM
discovery (8 tiers); the two resolvers’ tier-1 mission-scoped override probe is
reconverged (they had silently drifted, so the same lookup behaved differently
depending on which resolver ran); and &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt; now reports org-sourced
entries with the correct &lt;code dir=&quot;auto&quot;&gt;ORG&lt;/code&gt; origin instead of mislabelling them
&lt;code dir=&quot;auto&quot;&gt;GLOBAL_MISSION&lt;/code&gt; and reading them from the wrong directory. Projects with no
org pack are unaffected — &lt;code dir=&quot;auto&quot;&gt;resolve_org_roots()&lt;/code&gt; returns &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; and every new
lookup is a no-op.&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 mission-type&lt;/code&gt; reports whether every mission’s
&lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; actually resolves, so a broken or unregistered type is visible
before it misbehaves (mission &lt;code dir=&quot;auto&quot;&gt;mission-type-guard-registry&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3402&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3386&lt;/code&gt;).&lt;/strong&gt; Modelled on &lt;code dir=&quot;auto&quot;&gt;doctor identity&lt;/code&gt;, it walks every mission under
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; and classifies each into one of six distinguishable states —
&lt;code dir=&quot;auto&quot;&gt;resolved&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;activated-unresolvable&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;typeless&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;legacy-key-only&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; — and supports &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; for machine output and
&lt;code dir=&quot;auto&quot;&gt;--fail-on &amp;#x3C;state,...&gt;&lt;/code&gt; for CI gating (e.g.
&lt;code dir=&quot;auto&quot;&gt;--fail-on unknown,activated-unresolvable&lt;/code&gt; exits non-zero when any mission
sits in those states). Before, a mission whose type failed to resolve gave no
signal until the runtime silently applied the wrong rules; now the condition
is inspectable on demand.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A pack — built-in, org, fetched, or a charter bundle — now has one canonical
&lt;code dir=&quot;auto&quot;&gt;pack-manifest.yaml&lt;/code&gt; schema instead of two divergent formats (mission
&lt;code dir=&quot;auto&quot;&gt;pack-metadata-manifest-unification-01M052PT&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3500&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3501&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3502&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3503&lt;/code&gt;, slice of keystone &lt;code dir=&quot;auto&quot;&gt;#2467&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-16-1&lt;/code&gt;).&lt;/strong&gt; Before, org packs’
&lt;code dir=&quot;auto&quot;&gt;pack-manifest.yaml&lt;/code&gt; stored per-kind &lt;code dir=&quot;auto&quot;&gt;artifact_counts&lt;/code&gt; (no lineage, and never
written for the built-in pack every pack extends), while charter bundles’
&lt;code dir=&quot;auto&quot;&gt;synthesis-manifest.yaml&lt;/code&gt; enumerated &lt;code dir=&quot;auto&quot;&gt;constituents[]&lt;/code&gt; in an unrelated shape —
two formats that could drift, with neither covering the reference pack. Now the
unified schema (enumerated &lt;code dir=&quot;auto&quot;&gt;constituents:[{kind,id,path,content_hash}]&lt;/code&gt;, stored
&lt;code dir=&quot;auto&quot;&gt;artifact_counts&lt;/code&gt; retired for a derived &lt;code dir=&quot;auto&quot;&gt;counts_by_kind&lt;/code&gt; view, charter-only
fields in an optional &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt; profile block) is defined and the built-in pack
emits it: a generated manifest (265 constituents, wired into &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine regenerate-graph&lt;/code&gt;) plus new authored &lt;code dir=&quot;auto&quot;&gt;packs/built-in/pack.yaml&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;pack.md&lt;/code&gt;
carrying a stable, immutable ULID &lt;code dir=&quot;auto&quot;&gt;pack_id&lt;/code&gt; and declared &lt;code dir=&quot;auto&quot;&gt;parent_pack&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;accompanies_doctrine_pack&lt;/code&gt; lineage edges, resolved exclusively through the
existing &lt;code dir=&quot;auto&quot;&gt;org_extends.resolve_extends_order&lt;/code&gt; (no second lineage walker —
enforced by a non-vacuous architectural ratchet). &lt;code dir=&quot;auto&quot;&gt;pack_version&lt;/code&gt; is
derive-else-fallback: authored in &lt;code dir=&quot;auto&quot;&gt;pack.yaml&lt;/code&gt; when present, else generated, so
fetched/org packs keep genuine fetch-time provenance. This slice lands the
schema, models, and the built-in-pack writer; org/fetched/charter manifest
writers and the &lt;code dir=&quot;auto&quot;&gt;pack_id&lt;/code&gt; resolver cutover are fast-follow, and the broader
“compound packs” slice of &lt;code dir=&quot;auto&quot;&gt;#2467&lt;/code&gt; remains future work.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A new &lt;code dir=&quot;auto&quot;&gt;spk-run-verdict-capture&lt;/code&gt; skill so every agent harness records a WP
review verdict the same way (&lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;).&lt;/strong&gt; The sole authority for a verdict is 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 &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt; render
is non-authoritative); the skill documents the deterministic CLI seam
(&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task &amp;#x3C;WP&gt; --to approved|planned --review-feedback-file&lt;/code&gt;) and its verdict vocabulary, and &lt;code dir=&quot;auto&quot;&gt;spk-run-review-wp&lt;/code&gt;
now references it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Committed doctrine provenance is now portable across machines, checkouts,
and wheels — no more baked-in absolute paths (mission
&lt;code dir=&quot;auto&quot;&gt;operator-config-ergonomics&lt;/code&gt;, WP01/WP03/WP04; &lt;code dir=&quot;auto&quot;&gt;#3494&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;FR-001&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-002&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-003&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-006&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-007&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-008&lt;/code&gt;).&lt;/strong&gt; Committed
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent_profiles_manifest.json&lt;/code&gt; used to record each
built-in doctrine pack under the authoring machine’s absolute filesystem
path, so the same files broke on a teammate’s checkout, an installed wheel,
or CI. Both provenance carriers now emit a portable
&lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_PACKS_ROOT}/built-in/...&lt;/code&gt; token through one shared normalizer
and &lt;strong&gt;never&lt;/strong&gt; a resolved path — even when &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; is already
exported to an absolute path at emit time (the re-bake case is
regression-guarded). A single kernel expansion seam (&lt;code dir=&quot;auto&quot;&gt;src/kernel/env_expand.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;expand_env_template&lt;/code&gt;) backs both this token and the &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; pointer
below, and &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; is its canonical packs-root authority. An
idempotent &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; migration (&lt;code dir=&quot;auto&quot;&gt;m_3_2_7_heal_provenance_paths&lt;/code&gt;)
rewrites any already-committed absolute built-in path back to the portable
token with zero manual steps — this repo’s own leaked paths in
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/agent_profiles_manifest.json&lt;/code&gt;
were healed the same way. A new &lt;code dir=&quot;auto&quot;&gt;doctor provenance&lt;/code&gt; facet reports any
remaining leak with a heal hint.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Operator environment (SaaS tokens, org slugs, path overrides) now has one
file to point at, loaded before anything else runs (mission
&lt;code dir=&quot;auto&quot;&gt;operator-config-ergonomics&lt;/code&gt;, WP02; &lt;code dir=&quot;auto&quot;&gt;#3495&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;FR-004&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-004a&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-005&lt;/code&gt;).&lt;/strong&gt;
Previously these values had to live in your real shell environment or be
re-typed per project. A two-tier &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; file — &lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_HOME}/.kitty.env&lt;/code&gt;
machine-wide, overridden by &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;repo&gt;/.kittify/.kitty.env&lt;/code&gt; per-repo — is now
loaded into &lt;code dir=&quot;auto&quot;&gt;os.environ&lt;/code&gt; &lt;strong&gt;before&lt;/strong&gt; any other &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; module is
imported, so even import-time-gated behaviour picks it up. Precedence is
&lt;strong&gt;real-env &gt; per-repo &gt; home&lt;/strong&gt;: an explicit shell value always wins, and a
per-repo file only arms the project it lives in (unlike a global &lt;code dir=&quot;auto&quot;&gt;export&lt;/code&gt;,
which arms every project the shell later touches). &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;
gains a single &lt;code dir=&quot;auto&quot;&gt;env_file&lt;/code&gt; pointer (default &lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_HOME}/.kitty.env&lt;/code&gt;).
Fail policy is explicit: an absent file is skipped (the default for almost
every project today); a present-but-unreadable &lt;code dir=&quot;auto&quot;&gt;env_file&lt;/code&gt; fails loud and
names the file, because it gates auth; a malformed &lt;code dir=&quot;auto&quot;&gt;KEY=VALUE&lt;/code&gt; line is
skipped; and a &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME=&lt;/code&gt; line inside the file is dropped with a
warning to prevent locator recursion. An idempotent &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;
migration (&lt;code dir=&quot;auto&quot;&gt;m_3_2_8_provision_kitty_env&lt;/code&gt;) seeds the per-repo scaffold,
registers the &lt;code dir=&quot;auto&quot;&gt;env_file&lt;/code&gt; pointer, and adds &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;.claudeignore&lt;/code&gt;
rules — seeding only values already present in the environment, never a live
secret (secret-shaped vars are written as commented, blank templates). A new
&lt;code dir=&quot;auto&quot;&gt;doctor env-file&lt;/code&gt; facet reports presence, tier, readability, pointer, and
ignore-rule health with every value redacted through a fail-closed allowlist.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Opt-in release-candidate channel — catfood an rc without ever nagging
operators who did not ask (mission &lt;code dir=&quot;auto&quot;&gt;operator-config-ergonomics&lt;/code&gt;, WP05;
&lt;code dir=&quot;auto&quot;&gt;#3496&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;FR-009&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;FR-010&lt;/code&gt;).&lt;/strong&gt; A default-off &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PRERELEASE&lt;/code&gt;
preference makes every “latest version” surface — &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --agent-check&lt;/code&gt; and the throttled startup nag — pre-release-aware only when
explicitly opted in. Left unset (the default, unchanged for every existing
project), only the latest &lt;strong&gt;stable&lt;/strong&gt; release is ever surfaced, even when a
newer rc exists on the index. Opted in, the newest PEP 440 pre-release is
surfaced and the proposed upgrade is a &lt;strong&gt;pinned&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty-cli==&amp;#x3C;rc&gt;&lt;/code&gt;
install, never a floating &lt;code dir=&quot;auto&quot;&gt;--pre&lt;/code&gt; flag. A new &lt;code dir=&quot;auto&quot;&gt;doctor channel&lt;/code&gt; facet reports
the active channel. This ships the consumer half only; CI’s rc build/publish
cadence stays in &lt;code dir=&quot;auto&quot;&gt;#3047&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;New architecture references tie the SaaS opt-in, &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt;, and rc-channel
decisions together (mission &lt;code dir=&quot;auto&quot;&gt;operator-config-ergonomics&lt;/code&gt;, WP06; &lt;code dir=&quot;auto&quot;&gt;FR-011&lt;/code&gt;).&lt;/strong&gt;
Two ADRs record the decisions:
&lt;a href=&quot;/adr/3.x/2026-08-16-5-operator-config-env-expansion-seam/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-08-16-5-operator-config-env-expansion-seam.md&lt;/code&gt;&lt;/a&gt;
(the kernel env-expansion seam, token provenance, and &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; layering)
and
&lt;a href=&quot;/adr/3.x/2026-08-16-4-rc-release-channel/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;2026-08-16-4-rc-release-channel.md&lt;/code&gt;&lt;/a&gt;
(the default-off rc channel). A new
&lt;a href=&quot;../architecture/team-kitty-saas.md&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;team-kitty-saas.md&lt;/code&gt;&lt;/a&gt; architecture doc
walks the full opt-in → project-store migration → admission/delivery-target →
auth → history-disclosure → &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; flow with an end-to-end Mermaid
interaction diagram. Consumption docs and the &lt;code dir=&quot;auto&quot;&gt;spk-team-{sync,auth,tracker}&lt;/code&gt;
skills now point operators at the durable &lt;code dir=&quot;auto&quot;&gt;.kitty.env&lt;/code&gt; mechanism instead of a
per-shell &lt;code dir=&quot;auto&quot;&gt;export&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An agent working the mission lifecycle — hitting a merge-gate rejection,
an issue-matrix verdict, or an undrained SaaS sync — previously had to
already know the mechanics, because they lived only in a maintainer’s
private notes (mission &lt;code dir=&quot;auto&quot;&gt;self-documenting-repo&lt;/code&gt; Bucket 2; &lt;code dir=&quot;auto&quot;&gt;#3464&lt;/code&gt;, follows
&lt;code dir=&quot;auto&quot;&gt;#3448&lt;/code&gt;).&lt;/strong&gt; A second audit of that private memory routed the durable
workflow / CI / git / status-&amp;#x26;-sync mechanics into the repo’s canonical
homes: &lt;code dir=&quot;auto&quot;&gt;docs/development/how-to/review-gates.md&lt;/code&gt; now carries the
(event-sourced) review-cycle + merge-gate mechanics and the issue-matrix
discovery surface; a new &lt;code dir=&quot;auto&quot;&gt;docs/operations/sync-drain.md&lt;/code&gt; documents the real
3-gate drain (&lt;code dir=&quot;auto&quot;&gt;saas_disabled&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;missing_auth&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;missing_team&lt;/code&gt;) and the
&lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; false-green trap; &lt;code dir=&quot;auto&quot;&gt;coverage-signals.md&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;known-friction-points.md&lt;/code&gt; gain the critical-path-move coverage remedy and
the CI-label skip guard; &lt;code dir=&quot;auto&quot;&gt;pr-landing.md&lt;/code&gt; gains true-base/stale-stack
diagnostics and a new &lt;code dir=&quot;auto&quot;&gt;compress-mission-history.md&lt;/code&gt; how-to; the
architecture docs correct a &lt;strong&gt;live stale-doc regression&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt;
claimed a &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;-absent &lt;code dir=&quot;auto&quot;&gt;-WP##&lt;/code&gt; fallback the resolver actually raises
&lt;code dir=&quot;auto&quot;&gt;MissingLanesError&lt;/code&gt; for); three review-discipline heuristics enrich the
doctrine tactics, and the &lt;code dir=&quot;auto&quot;&gt;gh&lt;/code&gt; “Closes #A,#B links only #A” trap lands in
the tracker toolguide. A committed
&lt;code dir=&quot;auto&quot;&gt;agent-memory-workflow-migration-manifest.md&lt;/code&gt; (with a completeness test)
maps all 49 audited memories to a repo home, an already-home citation, a
learned-fact note, or “keep-private”. Dogfooding payoff: verifying against
current code caught several &lt;em&gt;stale&lt;/em&gt; memories — the review-gate frontmatter
mechanism was retired for an event-sourced one, and the drain’s second gate
was mis-remembered as &lt;code dir=&quot;auto&quot;&gt;sync migrate&lt;/code&gt; (retired).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An agent tripping a gate, hunting the right doctrine template source, or
recovering a split-brain mission previously had to already know the
answer — that knowledge lived only in a maintainer’s private notes, not in
the repo (mission &lt;code dir=&quot;auto&quot;&gt;self-documenting-repo&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3448&lt;/code&gt;).&lt;/strong&gt; A maintainer audit
found this tribal knowledge nowhere in the shipped repo. Now it does:
architectural/docs gate assertions (&lt;code dir=&quot;auto&quot;&gt;write-side re-derivation&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;inert schema slots&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;relative-link fixer&lt;/code&gt;) print a &lt;strong&gt;content-anchored remedy
derived from the gate’s own logic&lt;/strong&gt;, so tripping a gate tells you how to
satisfy it; &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt; corrects the stale &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/…&lt;/code&gt;
template-source path to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/…&lt;/code&gt; (with a grep guard);
six operator recovery runbooks for coord/lane split-brain scenarios are
published under &lt;code dir=&quot;auto&quot;&gt;docs/operations/&lt;/code&gt;, each leading with the shipped
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor … --fix&lt;/code&gt; where one exists; and the docs-inventory
freshen, mission wrap-up, and env/tracker conventions are now findable in
&lt;code dir=&quot;auto&quot;&gt;docs/development/&lt;/code&gt;. A committed &lt;code dir=&quot;auto&quot;&gt;agent-memory-migration-manifest.md&lt;/code&gt;
(with a completeness test) maps every audited gap-filler to its new repo
home, its tracking issue, or an explicit “behaviour retired” — the audit
surfaced five memories that were already stale (e.g. the shard-registration
guidance retired by &lt;code dir=&quot;auto&quot;&gt;#2671&lt;/code&gt;’s auto-cover, and a &lt;code dir=&quot;auto&quot;&gt;mission-gate-artifact&lt;/code&gt;
gate that never existed). Deleting the matching entries from a
maintainer’s live &lt;code dir=&quot;auto&quot;&gt;MEMORY.md&lt;/code&gt; stays a manual, per-operator checklist
tracked in the manifest — this mission migrates the knowledge into the
repo, it does not touch anyone’s private memory file. Three behaviour
quirks found along the way were filed, not fixed (&lt;code dir=&quot;auto&quot;&gt;#3450&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3451&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3452&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CI now builds each shippable module as its own reusable workflow, and a new
&lt;code dir=&quot;auto&quot;&gt;spec-kitty regen&lt;/code&gt; lets contributors fix generated-asset drift themselves
(mission &lt;code dir=&quot;auto&quot;&gt;modular-per-package-ci-01M025GV&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3447&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3379&lt;/code&gt;).&lt;/strong&gt; The
monorepo already ships separately-packaged modules (&lt;code dir=&quot;auto&quot;&gt;src/kernel&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;src/doctrine&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;packs/built-in&lt;/code&gt; data pack), but CI ran them as
path-filtered jobs inside one monolithic &lt;code dir=&quot;auto&quot;&gt;ci-quality&lt;/code&gt; workflow, and the
generated agent-command baselines + codex/vibe skill snapshots drifted
silently when their source prompt templates changed — a contributor’s
one-line edit tripped a dozen parity gates a maintainer had to regenerate by
hand (&lt;code dir=&quot;auto&quot;&gt;#3379&lt;/code&gt;). Now &lt;code dir=&quot;auto&quot;&gt;kernel&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; (fast + integration legs), and
&lt;code dir=&quot;auto&quot;&gt;packs&lt;/code&gt; each build in an &lt;code dir=&quot;auto&quot;&gt;on: workflow_call&lt;/code&gt; module workflow invoked as a
&lt;code dir=&quot;auto&quot;&gt;uses:&lt;/code&gt; job inside &lt;code dir=&quot;auto&quot;&gt;ci-quality&lt;/code&gt;, so a module has its own build boundary while
its coverage still aggregates into the single run the Sonar reporter reads
(reusable workflows, not &lt;code dir=&quot;auto&quot;&gt;workflow_run&lt;/code&gt; — coverage never fragments across
runs). The architectural CI-model guards learned to resolve &lt;code dir=&quot;auto&quot;&gt;uses:&lt;/code&gt;
delegation through one seam so a reusable-workflow caller is modeled as if it
ran inline. &lt;code dir=&quot;auto&quot;&gt;spec-kitty regen [--check]&lt;/code&gt; regenerates the committed generated
fixtures from source, byte-identical to a &lt;code dir=&quot;auto&quot;&gt;PYTEST_UPDATE_SNAPSHOTS&lt;/code&gt; run, from
a single shared version pin; &lt;code dir=&quot;auto&quot;&gt;--check&lt;/code&gt; is the fork-safe freshness gate (it
fails with the exact command + diff, since a fork PR’s read-only token cannot
commit back). A trust-tiered &lt;code dir=&quot;auto&quot;&gt;regen-assets&lt;/code&gt; workflow runs check-only on every
PR, auto-commits on same-repo pushes, and offers a maintainer-label
privileged path that ships disabled pending a security review. The 12-agent ×
N byte grid that caused the churn is retired for structural invariants plus
one canonical byte snapshot per render branch (markdown + TOML), so a
source-prompt edit now regenerates at most one canonical fixture instead of
~14.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An org- or project-tier doctrine pack can now contribute a mission type
that works end to end (mission &lt;code dir=&quot;auto&quot;&gt;up-mission-type-seam-01KZY1JB&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3424&lt;/code&gt;,
closes &lt;code dir=&quot;auto&quot;&gt;#3397&lt;/code&gt;).&lt;/strong&gt; Before, a mission type shipped by an org or project pack
could be declared and activated but not used: &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt;, charter
activation, and action-sequence projection all resolved against a
built-in-only roster, so a custom type either hard-failed or — worse —
silently resolved to an empty action sequence that planned nothing yet
reported success. Now a layered, pack-aware lookup resolves built-in, org,
and project mission types in that precedence order with a genuine action
sequence and template set, and four operator-facing surfaces stop reporting
falsehoods: &lt;code dir=&quot;auto&quot;&gt;charter mission-type list&lt;/code&gt; shows the real source layer,
&lt;code dir=&quot;auto&quot;&gt;mission-type show&lt;/code&gt; succeeds for an activated non-built-in type, &lt;code dir=&quot;auto&quot;&gt;doctrine mission-type list&lt;/code&gt; actually layers, and &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;’s step-removal
warnings compare real sequences. Three previously silent degradations —
malformed mission-type YAML, an unreadable roster directory, and an empty
action sequence from a non-built-in layer — now fail loud, naming the
offending file and layer. This is the availability slice only; mission-type
is deliberately not promoted to a first-class doctrine artifact kind (ADR
&lt;code dir=&quot;auto&quot;&gt;2026-08-13-1&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Hosted-sync consent is now per-project: one immutable &lt;code dir=&quot;auto&quot;&gt;project_uuid&lt;/code&gt; owns
one physically separate sync store and one explicit consent decision
(mission &lt;code dir=&quot;auto&quot;&gt;per-project-sync-consent-ledgers-01KZKMQZ&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3262&lt;/code&gt;, pairs with
SaaS &lt;code dir=&quot;auto&quot;&gt;#585&lt;/code&gt;).&lt;/strong&gt; Before, a shared journal/ledger/queue mixed every project’s
rows and a filter defect could deliver another project’s data (the #3030
consent incident). Now each project’s consent, consent epochs, journal,
delivery results, body/offline queue, target binding, and migration state
live in a UUID-owned &lt;code dir=&quot;auto&quot;&gt;ProjectSyncStore&lt;/code&gt; no other project’s operation can
open; &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt; records the only local grant authority
(offline-capable, never inherited from login/URL/slug/path/env), opt-out is
an immediate epoch-sealing barrier that never deletes captured rows, and
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC&lt;/code&gt; is strictly deny-only — arming it grants
nothing. Local consent additionally pairs with an independent target-scoped
SaaS admission generation, and &lt;code dir=&quot;auto&quot;&gt;project_not_admitted&lt;/code&gt; refusals park
terminally instead of retrying. Operators migrate legacy shared state with
the new copy-only, resumable project-store cutover commands
(&lt;code dir=&quot;auto&quot;&gt;spec-kitty 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;); the retired shared-store &lt;code dir=&quot;auto&quot;&gt;sync migrate&lt;/code&gt;
refuses with guidance.
See &lt;a href=&quot;../guides/project-sync-consent.md&quot;&gt;Per-Project Sync Consent&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The declarative transition-gate design is now documented as architecture,
and two mission-doctrine docs point at the right paths again (&lt;code dir=&quot;auto&quot;&gt;#3378&lt;/code&gt;).&lt;/strong&gt;
Before, the settled model for how transition gates work — the declarative
&lt;code dir=&quot;auto&quot;&gt;gate&lt;/code&gt; artefact kind, where a gate executes, the trusted-publisher rule, and
the typed-severity outcome — lived only in scattered discussion, and
&lt;code dir=&quot;auto&quot;&gt;mission-type-resolution.md&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;doctrine-kinds.md&lt;/code&gt; still named the
pre-relocation &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/&lt;/code&gt; source of truth. Now six Proposed
ADRs plus a &lt;code dir=&quot;auto&quot;&gt;mission-gates.md&lt;/code&gt; explanation page (with three render-verified
diagrams) capture the design in one place, and those two docs are retargeted
to the live &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/&lt;/code&gt; paths.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Documentation can now be marked &lt;code dir=&quot;auto&quot;&gt;durable&lt;/code&gt; — a standing reference that is
never flagged as stale draft (mission &lt;code dir=&quot;auto&quot;&gt;docs-plans-closeout-01KZTK2J&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3368&lt;/code&gt;).&lt;/strong&gt; Before, a long-lived throughline doc could only be &lt;code dir=&quot;auto&quot;&gt;active&lt;/code&gt;, so the
freshness SLA eventually nagged it toward “review or retire” like any aging
draft. Now &lt;code dir=&quot;auto&quot;&gt;durable&lt;/code&gt; is a reserved &lt;code dir=&quot;auto&quot;&gt;doc_status&lt;/code&gt; across the whole authority
chain (the &lt;code dir=&quot;auto&quot;&gt;042-common-docs&lt;/code&gt; directive, the &lt;code dir=&quot;auto&quot;&gt;DocStatus&lt;/code&gt; enum, the common-docs
styleguide and tactics, and the never-stale freshness rule), so a deliberate
standing document is left alone. This closeout also retires ~60 shipped or
superseded working notes in place (content preserved, evidence-cited) and
gathers the domain plans under &lt;code dir=&quot;auto&quot;&gt;docs/plans/domains/&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 intake&lt;/code&gt; now recognises an optional v1 handoff packet so upstream
requirements tools can seed a mission without the agent re-inventing FR/AC
ids.&lt;/strong&gt; A packet is ordinary Markdown; YAML frontmatter with &lt;code dir=&quot;auto&quot;&gt;handoff_packet: 1&lt;/code&gt;
is additive. Unknown versions and malformed YAML degrade to today’s prose
intake. &lt;code dir=&quot;auto&quot;&gt;intake --auto&lt;/code&gt; also scans &lt;code dir=&quot;auto&quot;&gt;.handoff/*.md&lt;/code&gt;. Contract:
&lt;code dir=&quot;auto&quot;&gt;docs/contracts/handoff-packet-v1.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The doctrine documentation site now shows rendered schema diagrams of the
doctrine artefacts, drawn locally with no network egress (mission
&lt;code dir=&quot;auto&quot;&gt;doctrine-schema-diagrams-01KZTQTH&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3366&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3354&lt;/code&gt;).&lt;/strong&gt; Before, the doctrine
layer’s shape — the relationship graph, the mission-step contract and action
index, the cross-kind overview and the full agent-profile schema — lived only
in prose, and the docsite had no way to render PlantUML at all. Now
code-grounded &lt;code dir=&quot;auto&quot;&gt;@startyaml&lt;/code&gt; diagrams are authored for each and &lt;strong&gt;drift-guarded
against the live frozen models&lt;/strong&gt; (a diagram that falls out of sync with the
code reds the build), then rendered offline by a version+sha256-pinned
PlantUML running inside a network-isolated container — so building the docs
sends nothing off-machine. Each rendered figure carries derived alt/aria text
for accessibility.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A shrink-only census gate now guards the 40 test sites that pin
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME&lt;/code&gt;, so the collision can only get smaller from here (mission
&lt;code dir=&quot;auto&quot;&gt;isolated-home-pin-guard-r1a-01KZNMA3&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;).&lt;/strong&gt; Before, nothing stopped a
41st ad-hoc home pin from landing, and a naive “converge them all” cleanup
would silently delete the load-bearing isolation those fixtures carry. Now a
content-addressed census — pinned as debt at a frozen SHA — plus a canonical
&lt;code dir=&quot;auto&quot;&gt;canonical_home&lt;/code&gt; owner fixture, a falsifiability probe, and a halt gate red the
build if the pinned set grows. Contributor-facing test infrastructure only (no
&lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; change); this lands the &lt;em&gt;instrument&lt;/em&gt; ahead of the follow-on adoption
(R1b), so &lt;code dir=&quot;auto&quot;&gt;Refs #3121&lt;/code&gt; rather than &lt;code dir=&quot;auto&quot;&gt;Closes&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-changed-1&quot;&gt;♻️ Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The dead-symbol allowlist’s provenance is now a machine-readable
&lt;code dir=&quot;auto&quot;&gt;source_module=&lt;/code&gt; field instead of a parsed comment, so refreshing a still-dead
allowlisted symbol no longer depends on comment hygiene (mission
&lt;code dir=&quot;auto&quot;&gt;symbolkey-source-module-01M0B0SF&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3552&lt;/code&gt;).&lt;/strong&gt; Before, a content-tier entry’s
originating module lived only in its free-form &lt;code dir=&quot;auto&quot;&gt;# module::Name&lt;/code&gt; comment,
which the refresh helper (&lt;code dir=&quot;auto&quot;&gt;_refresh_dead_symbol_hashes.py&lt;/code&gt;) had to
tokenize-parse to recover — a fragile source of truth that had drifted into
multiple comment formats, and same-name symbols from different modules
couldn’t be told apart structurally. Now every content-tier &lt;code dir=&quot;auto&quot;&gt;SymbolKey&lt;/code&gt;
carries an optional, provenance-only &lt;code dir=&quot;auto&quot;&gt;source_module=&lt;/code&gt; keyword as the single
canonical source; the &lt;code dir=&quot;auto&quot;&gt;# module::Name&lt;/code&gt; comment stays in place as
human-readable audit trail, but the machine comment-parsing path is retired,
and same-name entries disambiguate on the field rather than on comment
convention. Test infrastructure only, no &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; change (no version bump).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-1&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt;’s error contract on an unresolvable/ambiguous &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; handle already changed in #167 without being recorded: exit code 2→1, and non-&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; diagnostics moved from stderr to stdout (documentation follow-up, #174, controller-qa MINOR on #167).&lt;/strong&gt; Before #167, &lt;code dir=&quot;auto&quot;&gt;resolve_context&lt;/code&gt; called &lt;code dir=&quot;auto&quot;&gt;resolve_mission_handle&lt;/code&gt; directly, which — on &lt;code dir=&quot;auto&quot;&gt;MissionNotFoundError&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;AmbiguousHandleError&lt;/code&gt; — printed to &lt;code dir=&quot;auto&quot;&gt;err_console&lt;/code&gt; (stderr) and called &lt;code dir=&quot;auto&quot;&gt;sys.exit(2)&lt;/code&gt; in non-JSON mode, bypassing this command’s own &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; envelope entirely (the root cause of #160’s quarantined strict-JSON test). #167 fixed that bypass by catching both exceptions and re-raising them as this command’s own &lt;code dir=&quot;auto&quot;&gt;ActionContextError&lt;/code&gt;, which its existing handler renders through &lt;code dir=&quot;auto&quot;&gt;console&lt;/code&gt; (stdout) with &lt;code dir=&quot;auto&quot;&gt;raise typer.Exit(1)&lt;/code&gt; for both JSON and non-JSON output. Net effect for &lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt; (only — no other &lt;code dir=&quot;auto&quot;&gt;resolve_mission_handle&lt;/code&gt; caller is affected): a not-found/ambiguous &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; handle now exits &lt;strong&gt;1&lt;/strong&gt; (was 2) and, in non-JSON mode, prints its &lt;code dir=&quot;auto&quot;&gt;[red]Error:[/red] ...&lt;/code&gt; line to &lt;strong&gt;stdout&lt;/strong&gt; (was stderr). Exit 1 is the correct, intended contract — this entry records the change for callers that depended on exit 2 or on scraping stderr.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission-handle JSON &lt;code dir=&quot;auto&quot;&gt;error_code&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;outcome&lt;/code&gt; values are now UPPER_SNAKE (&lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_FOUND&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MISSION_AMBIGUOUS_SELECTOR&lt;/code&gt;) across every emitter, matching the sibling convention already used elsewhere (&lt;code dir=&quot;auto&quot;&gt;decisions/models.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;MISSION_NOT_FOUND&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_read_path_resolver.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;MISSION_AMBIGUOUS_SELECTOR&lt;/code&gt;) (#174, controller-qa MINOR follow-up on #167).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;resolve_mission_handle&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; envelope (&lt;code dir=&quot;auto&quot;&gt;selector_resolution.py&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;AmbiguousHandleError.to_dict()&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission_resolver.py&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;agent context resolve&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;ActionContextError&lt;/code&gt; codes, and &lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize --json&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;outcome&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;error&lt;/code&gt; fields previously emitted lowercase &lt;code dir=&quot;auto&quot;&gt;mission_not_found&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;ambiguous_mission_handle&lt;/code&gt; — inconsistent with every sibling code in the same functions. &lt;strong&gt;This is a breaking JSON-contract change&lt;/strong&gt; for any caller that string-matched the old lowercase values (&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status --json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent issue-verdict --json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implement --json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctor review-cycle-reconcile --json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent context resolve --json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize --json&lt;/code&gt;); the &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt;/exit-code/stdout-vs-stderr shape is unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ZeitgeistClient.offer()&lt;/code&gt; now posts presence/focus/session control envelopes to a real relay’s &lt;code dir=&quot;auto&quot;&gt;/managed/control&lt;/code&gt; endpoint with the headers it actually requires, instead of a route that always rejected them (&lt;code dir=&quot;auto&quot;&gt;FIX-M2-10&lt;/code&gt;).&lt;/strong&gt; Every &lt;code dir=&quot;auto&quot;&gt;offer()&lt;/code&gt; call — &lt;code dir=&quot;auto&quot;&gt;presence()&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;focus_start/heartbeat/pause/end()&lt;/code&gt; — was POSTing its &lt;code dir=&quot;auto&quot;&gt;{op, request_id, args}&lt;/code&gt; envelope to &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;relay_url&gt;/events&lt;/code&gt;, the baseline Beacon-shaped route (&lt;code dir=&quot;auto&quot;&gt;zeitgeist/server.py&lt;/code&gt;), which has no &lt;code dir=&quot;auto&quot;&gt;op&lt;/code&gt; dispatch of any kind and structurally cannot process it; against a real, correctly-configured relay this was a 422 on every single call, discovered by &lt;code dir=&quot;auto&quot;&gt;DQA-M2-02&lt;/code&gt;’s Docker-local suite. &lt;code dir=&quot;auto&quot;&gt;offer()&lt;/code&gt; now targets &lt;code dir=&quot;auto&quot;&gt;/managed/control&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;zeitgeist/managed.py&lt;/code&gt;’s real presence/focus/session op dispatcher), includes the &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; field &lt;code dir=&quot;auto&quot;&gt;managed_control.schema.json&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;ControlEnvelope&lt;/code&gt; requires, and sends both gates a real relay enforces on that route: &lt;code dir=&quot;auto&quot;&gt;Authorization: Bearer &amp;#x3C;token&gt;&lt;/code&gt; (the outer, unconditional &lt;code dir=&quot;auto&quot;&gt;AuthenticationMiddleware&lt;/code&gt; gate every route but &lt;code dir=&quot;auto&quot;&gt;/health&lt;/code&gt; sits behind) and &lt;code dir=&quot;auto&quot;&gt;X-Zeitgeist-Capability: &amp;#x3C;token&gt;&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;managed.py&lt;/code&gt;’s own capability check, verified against a separate secret). Both headers carry the same single credential &lt;code dir=&quot;auto&quot;&gt;credentials.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;checkout&lt;/code&gt; flow already stores per repo — the same value &lt;code dir=&quot;auto&quot;&gt;subscription.py&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;operability.py&lt;/code&gt;’s already-landed callers already forward as the capability header — rather than introducing a second stored secret. Covered by a new protocol-faithful local double (&lt;code dir=&quot;auto&quot;&gt;tests/zeitgeist_client/conftest.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;ManagedControlDouble&lt;/code&gt;, mirroring &lt;code dir=&quot;auto&quot;&gt;managed_auth.SharedSecretCapabilityVerifier&lt;/code&gt;’s real HMAC wire shape and kind-scoped capability grants) in addition to the existing recording double.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Windows skill-content migrations no longer fail with &lt;code dir=&quot;auto&quot;&gt;WinError 5&lt;/code&gt; when replacing a managed read-only &lt;code dir=&quot;auto&quot;&gt;SKILL.md&lt;/code&gt; (#802; upstream #3771).&lt;/strong&gt; The shared bounded-directory writer clears the destination’s write attribute before its atomic replace and restores the previous mode afterward, so migrations update read-only skill files without weakening their managed state. A POSIX unit regression simulates Windows’ read-only-destination replacement failure, so the defect is covered without a Windows runner.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;HTTPS doctrine bundle fetches now persist ETags separately from pack versions and safely resolve Artifactory &lt;code dir=&quot;auto&quot;&gt;version&lt;/code&gt; metadata.&lt;/strong&gt; Existing &lt;code dir=&quot;auto&quot;&gt;source_type: https&lt;/code&gt; URLs with a valid &lt;code dir=&quot;auto&quot;&gt;/artifactory/&amp;#x3C;repository&gt;/&amp;#x3C;item&gt;&lt;/code&gt; path are recognized automatically; &lt;code dir=&quot;auto&quot;&gt;source_type: artifactory&lt;/code&gt; is also available to enforce that intent. Successful downloads are buffered before one exact-item AQL response co-attests the &lt;code dir=&quot;auto&quot;&gt;version&lt;/code&gt; property and SHA-256, and the checksum must match those exact bytes before extraction or snapshot promotion. Conditional validators are reused only for the same query-free source and an intact local snapshot; query-bearing URLs always fetch unconditionally rather than collapsing distinct resources or persisting signed parameters. A 304 deliberately leaves the prior snapshot and sampled version byte-for-byte unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;safe-commit&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt; and work-package prompts now print commands you
can actually run — before, they named invocations that error out when
copy-pasted (&lt;code dir=&quot;auto&quot;&gt;#3577&lt;/code&gt;).&lt;/strong&gt; The protected-branch commit refusals told operators to
run &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission create --start-branch …&lt;/code&gt; and the WP task-prompt
templates showed &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status&lt;/code&gt;, but neither is real: &lt;code dir=&quot;auto&quot;&gt;--start-branch&lt;/code&gt;
lives only on &lt;code dir=&quot;auto&quot;&gt;agent mission create&lt;/code&gt;, and the status board is &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;agent status&lt;/code&gt; is a command group with no board). Both are corrected
at the source, so a printed command runs as-is.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A warn-mode commit-guard warning is no longer swallowed on a successful
&lt;code dir=&quot;auto&quot;&gt;safe-commit&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt; — operators now see the guard’s warning instead of
it vanishing (&lt;code dir=&quot;auto&quot;&gt;#3580&lt;/code&gt;).&lt;/strong&gt; Before, a successful commit discarded the guard’s
warn-mode output, so a warning the guard emitted never reached the operator.
Now the guard’s stderr is surfaced on the success path, while git’s routine
stdout summary is routed to debug so an ordinary commit no longer emits a
spurious warning on the same channel.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Activating a mission type now cascades to the governance its steps depend on,
and the cascade proposes only kinds you can actually activate (&lt;code dir=&quot;auto&quot;&gt;#2829&lt;/code&gt;; M5 of
the charter-resolution program).&lt;/strong&gt; Before, the charter cascade followed only
&lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;refines&lt;/code&gt;, so the forward closure from a &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;
dead-ended at the intermediate &lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt; node — every built-in mission type
cascaded to &lt;strong&gt;zero&lt;/strong&gt; artifacts, and the governance an operator switched on
reached nobody. The followed set now also walks the action hop (&lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; +
&lt;code dir=&quot;auto&quot;&gt;instantiates&lt;/code&gt;), so the three governance-bearing built-in mission types cascade
to their directives/tactics/styleguides (measured 31/23/160, was 0). At the same
time, cascade candidacy is filtered to the canonical &lt;code dir=&quot;auto&quot;&gt;CHARTER_ACTIVATABLE_KINDS&lt;/code&gt;
authority, so it no longer proposes non-activatable &lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; targets
(which surfaced as spurious “could not cascade-activate” warnings for 137
existing sources). &lt;code dir=&quot;auto&quot;&gt;mission_type:plan&lt;/code&gt; correctly cascades empty — its step
contracts scope no governance, so the traversal dead-end is closed for it too but
there is nothing to reach (tracked as a follow-up to author plan-step
governance). The relation-set decision is recorded in ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-20-1&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The last five charter-activated doctrine artefacts that no consumer could reach
are now wired to a single authority or honestly marked direct-activation-only
(residual of &lt;code dir=&quot;auto&quot;&gt;#3009&lt;/code&gt;; M5).&lt;/strong&gt; Four had a defensible source expressed only as a
hand-authored overlay edge; each is promoted to a real reference in its owning
directive’s frontmatter (DIRECTIVE_034 → &lt;code dir=&quot;auto&quot;&gt;given-when-then-authoring&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;gherkin&lt;/code&gt;,
DIRECTIVE_030 → &lt;code dir=&quot;auto&quot;&gt;sonar&lt;/code&gt;, DIRECTIVE_041 → &lt;code dir=&quot;auto&quot;&gt;quadruple-a-test-format&lt;/code&gt;), so the pure
doctrine graph explains their reachability without a secondary overlay patch and
the shipped graph stays byte-identical. The fifth, &lt;code dir=&quot;auto&quot;&gt;deployable-skill-authoring&lt;/code&gt;,
has no defensible source and is recorded direct-activation-only rather than given
a guessed edge. Promoting the metadata surfaced — and fixed at root — a second
validation authority: the catalog &lt;code dir=&quot;auto&quot;&gt;DirectiveReference&lt;/code&gt; model and
&lt;code dir=&quot;auto&quot;&gt;directive.schema.yaml&lt;/code&gt; both rejected the &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt; keys under
&lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt;, which would have silently dropped a promoted directive and
degraded the profile renderer to a &lt;code dir=&quot;auto&quot;&gt;CharterCatalogMissWarning&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A procedure named in an agent profile’s &lt;code dir=&quot;auto&quot;&gt;operating-procedures&lt;/code&gt; field now
becomes a real, cascade-reachable dependency of that profile — and a fictional
or wrong-kind entry fails the doctrine build loudly instead of drifting in
silence (&lt;code dir=&quot;auto&quot;&gt;#2994&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3352&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3488&lt;/code&gt;; M3 of the operating-procedures program).&lt;/strong&gt;
Before, those edges were hand-pinned one-by-one in the DRG extractor (drift-prone
and easy to forget), while 44 dead references — 36 pointing at procedures that
never existed and 8 pointing at the wrong kind — sat unresolved and invisible.
Now the field is the single authority: &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; harvests it into
&lt;code dir=&quot;auto&quot;&gt;agent_profile --requires--&gt; procedure&lt;/code&gt; graph edges, refuses to build when a
built-in entry does not resolve to a real procedure node (naming the offender),
and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine&lt;/code&gt; surfaces any unresolved entries. The 44 dead
references were triaged (delete / repoint / migrate) so the shipped population
is 100% resolvable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Charter preflight remediations can now actually clear the check they name,
including for a legacy-bundle project, instead of sending the operator in a
circle (&lt;code dir=&quot;auto&quot;&gt;#2831&lt;/code&gt;).&lt;/strong&gt; An operator on a project carrying the pre-consolidation
legacy bundle (&lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;directives.yaml&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt;/
&lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt;, no &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;) was told to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter sync&lt;/code&gt; — a documented pure staleness reporter (&lt;code dir=&quot;auto&quot;&gt;src/charter/sync.py&lt;/code&gt;: “it
always reports &lt;code dir=&quot;auto&quot;&gt;synced=False&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;files_written=[]&lt;/code&gt;”) that clears nothing, so
the gate refused identically with no way out. Three fixes: (1) the blocking
&lt;code dir=&quot;auto&quot;&gt;charter_source&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;synced_bundle&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;missing&lt;/code&gt;-state remediation now names
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --yes&lt;/code&gt; for a real legacy bundle — which reaches
&lt;code dir=&quot;auto&quot;&gt;ConsolidateCharterBundleMigration&lt;/code&gt; and composes &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; FROM the
legacy content — instead of the content-discarding &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate --no-from-interview&lt;/code&gt; both shapes previously shared; a project with
no charter at all still gets the generate command, since there is nothing to
preserve. (2) &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter preflight --auto-refresh&lt;/code&gt;’s refresh
sequence no longer opens with a hardcoded &lt;code dir=&quot;auto&quot;&gt;charter sync&lt;/code&gt; — step one now runs
whichever of the above commands the freshness computer already derived,
so auto-refresh can genuinely repair a missing/legacy charter source instead
of failing on step one every time. (3) &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt;/preflight now
reports a &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; that parses as YAML but is not a real charter
bundle — an empty mapping, or a &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; outside the supported
&lt;code dir=&quot;auto&quot;&gt;2.x.x&lt;/code&gt; series — as &lt;code dir=&quot;auto&quot;&gt;invalid&lt;/code&gt; rather than &lt;code dir=&quot;auto&quot;&gt;fresh&lt;/code&gt;, so a downstream consumer
that would reject the same file no longer sees preflight green it first.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A hand-authored project-tier agent profile now becomes a reference-graph node
the charter cascade can reach — before, it loaded and validated but was
silently invisible to cascade (&lt;code dir=&quot;auto&quot;&gt;#3038&lt;/code&gt;; M6 of the charter-resolution program;
asset half deferred to &lt;code dir=&quot;auto&quot;&gt;#3037&lt;/code&gt;).&lt;/strong&gt; The project doctrine tier admitted only
three kinds (directive / tactic / styleguide) as DRG nodes, so a profile
authored under &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/agent_profiles/&lt;/code&gt; reported healthy yet reached
no dispatched agent. Spec Kitty now walks the authored project profiles and
emits an &lt;code dir=&quot;auto&quot;&gt;agent_profile:&amp;#x3C;id&gt;&lt;/code&gt; node into the project overlay &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt; the
cascade reads — through the existing additive-only guards, and failing loud
(naming the file) on a malformed, URN-unsafe, or duplicate &lt;code dir=&quot;auto&quot;&gt;profile-id&lt;/code&gt; rather
than silently skipping it. The kind→node-kind admission map is now
&lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;-keyed and covered by the totality gate, so a future kind cannot
silently escape project-tier node admission.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Loaded doctrine now actually reaches the dispatched agent — glossary packs,
procedure/tactic step descriptions, project-overlay agent profiles, and
&lt;code dir=&quot;auto&quot;&gt;procedures&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; are no longer silently dropped
(&lt;code dir=&quot;auto&quot;&gt;#3489&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3176&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3389&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3488&lt;/code&gt; render half; M4 of the charter-resolution
program).&lt;/strong&gt; Before, four delivery/render paths validated clean yet delivered
nothing: &lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt; had &lt;code dir=&quot;auto&quot;&gt;slot=None&lt;/code&gt; in the action-bundle delivery table
(one of two &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; rows lacking the module’s required stated reason) and no
renderer, so glossary packs were structurally unreachable in every config;
procedure/tactic step &lt;code dir=&quot;auto&quot;&gt;description&lt;/code&gt; was dead code (&lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt; is required, so
&lt;code dir=&quot;auto&quot;&gt;title or description&lt;/code&gt; never reached it — ~63% of step content undeliverable);
&lt;code dir=&quot;auto&quot;&gt;build_activation_aware_doctrine_service&lt;/code&gt; derived its project root from three
fixed candidates, none of which was &lt;code dir=&quot;auto&quot;&gt;.kittify/agent_profiles&lt;/code&gt;, so a
project-overlay profile silently vanished when resolved through the
activation-aware service; and &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; omitted the
&lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt; array the text render already shipped. Now &lt;code dir=&quot;auto&quot;&gt;GLOSSARY_PACK&lt;/code&gt; has a
real &lt;code dir=&quot;auto&quot;&gt;ACTIVATED&lt;/code&gt; delivery slot with a term-name surface list plus a
&lt;code dir=&quot;auto&quot;&gt;--include glossary-pack:&amp;#x3C;id&gt;&lt;/code&gt; fetch pointer (names only — the full
definitions stay behind the pointer so the NFR-001 token budget is respected),
&lt;strong&gt;every&lt;/strong&gt; remaining &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; delivery-table row carries a machine-checkable
stated reason (closing the class, including &lt;code dir=&quot;auto&quot;&gt;ANTI_PATTERN&lt;/code&gt;), step
&lt;code dir=&quot;auto&quot;&gt;description&lt;/code&gt; renders alongside &lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt; on both the action-bundle and profile
channels, the styleguide/toolguide pointer-only choice is a documented
deliberate budget decision rather than an unlabeled no-op, an optional
&lt;code dir=&quot;auto&quot;&gt;agent_profile_overlay_dir&lt;/code&gt; threaded through the doctrine-service builders
(default &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt;, byte-identical unset) lets &lt;code dir=&quot;auto&quot;&gt;default_profile_repository&lt;/code&gt;
resolve &lt;code dir=&quot;auto&quot;&gt;.kittify/agent_profiles&lt;/code&gt; through the sole sanctioned builder, and
&lt;code dir=&quot;auto&quot;&gt;context --json&lt;/code&gt; ships a typed &lt;code dir=&quot;auto&quot;&gt;procedures[]&lt;/code&gt; array under a deliberately
bumped &lt;code dir=&quot;auto&quot;&gt;context_schema_version&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;1.0.0&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;1.1.0&lt;/code&gt;) with &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; documented as
reference-only (its typed-array promotion deferred behind &lt;code dir=&quot;auto&quot;&gt;#3037&lt;/code&gt;). The
&lt;code dir=&quot;auto&quot;&gt;--include glossary-pack:&amp;#x3C;id&gt;&lt;/code&gt; fetch the pointer advertises inherits the same
activation gate as the delivery slot (a de-activated pack is a structured miss,
never a definition leak), and a delivered glossary pack is surfaced in the
&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; payload’s &lt;code dir=&quot;auto&quot;&gt;references[]&lt;/code&gt; link set rather than being silently absent.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Doctrine authored in an org pack or project overlay now loads and activates
with the same completeness as the built-in corpus — nested subdirectories are
no longer silently dropped, and the charter kind vocabulary is derived from a
single authority so drifted copies can’t render the wrong token or blind kind
inference (&lt;code dir=&quot;auto&quot;&gt;#3490&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3426&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2981&lt;/code&gt;; M1 of the charter-resolution program).&lt;/strong&gt;
Before, org/project discovery scanned non-recursively while built-in used
&lt;code dir=&quot;auto&quot;&gt;rglob&lt;/code&gt;, and the doctrine &lt;em&gt;loader&lt;/em&gt; and the charter-activation &lt;em&gt;resolver&lt;/em&gt; each
decided recursion independently — so a tactic, styleguide, or agent profile
authored one directory deep (e.g. &lt;code dir=&quot;auto&quot;&gt;styleguides/writing/&lt;/code&gt;) loaded at runtime and
showed in &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt;, yet the activation resolver silently skipped it
(measured 71% tactic undercount; nested org styleguides un-activatable). Now a
single doctrine-layer recursion authority (&lt;code dir=&quot;auto&quot;&gt;doctrine.discovery_recursion&lt;/code&gt;) is
read by both the loader (&lt;code dir=&quot;auto&quot;&gt;base._project_scan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent_profiles._load&lt;/code&gt; — the two
redundant &lt;code dir=&quot;auto&quot;&gt;rglob&lt;/code&gt; overrides removed) and the resolver
(&lt;code dir=&quot;auto&quot;&gt;kind_vocabulary._org_scan_dirs&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_layer_scan_dirs&lt;/code&gt;), so org/project
discovery is unconditionally recursive and the two agree by construction;
kind-specific globs keep &lt;code dir=&quot;auto&quot;&gt;.provenance/*.yaml&lt;/code&gt; sidecars and &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt; files out, and
the recursive flat-org scan excludes the reserved &lt;code dir=&quot;auto&quot;&gt;built-in/&lt;/code&gt; subtree so
flat-wins-over-legacy precedence is preserved. The plural↔singular charter
kind vocabulary is now derived from one &lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;-backed authority
(&lt;code dir=&quot;auto&quot;&gt;CHARTER_ACTIVATABLE_*&lt;/code&gt;, the 10 activatable kinds including &lt;code dir=&quot;auto&quot;&gt;anti_pattern&lt;/code&gt;),
collapsing the hand-copied maps in &lt;code dir=&quot;auto&quot;&gt;charter.activation.activations&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;charter.activation._activation_render&lt;/code&gt; — the two drifted copies that had fallen two kinds
behind, so &lt;code dir=&quot;auto&quot;&gt;glossary_pack&lt;/code&gt; rendered as its plural and &lt;code dir=&quot;auto&quot;&gt;glossary_packs&lt;/code&gt;
inference was blind, are fixed. &lt;code dir=&quot;auto&quot;&gt;charter context --include glossary_pack:&amp;#x3C;id&gt;&lt;/code&gt;
now renders and &lt;code dir=&quot;auto&quot;&gt;--include anti_pattern:&amp;#x3C;id&gt;&lt;/code&gt; resolves to a normal not-found
instead of erroring on an “unsupported selector kind”. A new falsifiable
parity/totality gate binds loader↔resolver recursion agreement and covers the
string-keyed kind authorities the previous enum-keyed guard could not see, so
this class of silent drift fails loudly if reintroduced. No cascade-reach or
golden-count change.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --cascade&lt;/code&gt; now follows a &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edge an org
pack authors in its canonical &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;pack validate&lt;/code&gt; no longer
contradicts the runtime about whether that fragment is read (&lt;code dir=&quot;auto&quot;&gt;#3572&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3573&lt;/code&gt;).&lt;/strong&gt;
Before, those fragment edges were parsed only by the diagnostic path (&lt;code dir=&quot;auto&quot;&gt;doctor doctrine&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;charter list&lt;/code&gt;) and were never bridged into the graph cascade walks —
which read root-level &lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; only — so activating an artifact silently
cascaded nothing for org-authored fragment dependencies, even though diagnostics
showed the edge. The companion &lt;code dir=&quot;auto&quot;&gt;drg_root_graph_missing&lt;/code&gt; validator globbed
&lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; and never flagged a &lt;code dir=&quot;auto&quot;&gt;fragment.yaml&lt;/code&gt;-only pack, so &lt;code dir=&quot;auto&quot;&gt;pack validate&lt;/code&gt;
exited 0 on the same gap. Now &lt;code dir=&quot;auto&quot;&gt;load_validated_graph&lt;/code&gt; folds org fragments through
the existing three-layer merge (reusing its endpoint-resolution and edge
de-duplication — no second code path), so a fragment &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; edge cascades;
the graphless-pack warning fires only when a pack ships &lt;strong&gt;neither&lt;/strong&gt; a root graph
&lt;strong&gt;nor&lt;/strong&gt; a &lt;code dir=&quot;auto&quot;&gt;drg/fragment.yaml&lt;/code&gt;; and the validator finding is reconciled in the
same change, so &lt;code dir=&quot;auto&quot;&gt;pack validate&lt;/code&gt; and the runtime tell one story. The diagnostic
path is unchanged (the bridge adds a consumer), and build-time callers that pass
no org fragments are unaffected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate --cascade&lt;/code&gt; now follows an org-pack dependency edge no
matter which pack in the chain declares it, and activating from an org pack
that ships no dependency graph no longer crashes the command (&lt;code dir=&quot;auto&quot;&gt;#3534&lt;/code&gt;; closes
&lt;code dir=&quot;auto&quot;&gt;#3527&lt;/code&gt;).&lt;/strong&gt; Before, cascade activation, &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt;, and dossier
rebaseline each saw only the first configured org pack — a &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;
edge into or out of any second-or-later pack was silently ignored, so
&lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt; under-activated whenever doctrine lived across more than one org
pack. Now the full declaration-ordered org-pack chain is threaded through all
three, so an edge cascades regardless of which pack authored it. As part of
landing, activating a directive or profile from an org pack that carries
doctrine artifacts but no root-level DRG graph now degrades that pack to “no
DRG layer” and activates normally, instead of aborting with &lt;code dir=&quot;auto&quot;&gt;DRGLoadError: No DRG graph files found&lt;/code&gt; — each configured pack is handled on its own, so one
graphless pack no longer takes a healthy sibling down with it.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A command run from a linked lane worktree no longer silently acts on the
primary checkout: root/workspace resolution is now honest under worktrees and
clones, and the review-verdict CLI path is unified across both surfaces
(&lt;code dir=&quot;auto&quot;&gt;#3129&lt;/code&gt; umbrella; Epics &lt;code dir=&quot;auto&quot;&gt;#2624&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3549&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3044&lt;/code&gt;).&lt;/strong&gt; A family of commands keyed
off the ambient invoking location (&lt;code dir=&quot;auto&quot;&gt;find_repo_root&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;locate_project_root&lt;/code&gt;) and
re-anchored a foreign lane worktree to the primary — producing silent
cross-checkout writes and false-green guards. A single checkout-identity guard
(&lt;code dir=&quot;auto&quot;&gt;core/checkout_identity.py&lt;/code&gt;) now distinguishes an owned invocation from a
foreign lane worktree (parsing &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; directly, carrying read/write intent so
the deliberate primary-read anchors from &lt;code dir=&quot;auto&quot;&gt;#2320&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3328&lt;/code&gt; are preserved), and
in-scope commands adopt a fail-closed refusal (&lt;code dir=&quot;auto&quot;&gt;#3128&lt;/code&gt;) that names the target
checkout instead of redirecting: &lt;code dir=&quot;auto&quot;&gt;intake&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3540&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces --fix&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#2613&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;doctor mission-state&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3051&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3541&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;migrate backfill-runtime-state&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3049&lt;/code&gt;), &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt; branch-match (&lt;code dir=&quot;auto&quot;&gt;#3124&lt;/code&gt;), and the
&lt;code dir=&quot;auto&quot;&gt;find_repo_root&lt;/code&gt; nested-clone boundary (&lt;code dir=&quot;auto&quot;&gt;#2610&lt;/code&gt;). On the verdict seam,
&lt;code dir=&quot;auto&quot;&gt;_parse_review_result_json&lt;/code&gt; and the &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; commit-gate are hoisted to a
shared, topology-aware leaf that &lt;strong&gt;both&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;agent status emit&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;orchestrator-api transition&lt;/code&gt; now enforce identically — on real lane commit
state, not a topology guess — closing a gap where a work package with no
commit on its lane could reach &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; (and onward to &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;) through
&lt;code dir=&quot;auto&quot;&gt;emit&lt;/code&gt; alone (&lt;code dir=&quot;auto&quot;&gt;#3547&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#1734&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;agent status emit&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;--review-result-json&lt;/code&gt;
so a work package can be walked to &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; through &lt;code dir=&quot;auto&quot;&gt;emit&lt;/code&gt; alone with a
structured verdict, and its misleading &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; example is corrected. &lt;code dir=&quot;auto&quot;&gt;review_result&lt;/code&gt; is registered in the &lt;code dir=&quot;auto&quot;&gt;status_event_row&lt;/code&gt; audit shape
with a value-equality snapshot round-trip (&lt;code dir=&quot;auto&quot;&gt;#3543&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#3461&lt;/code&gt;). The
standalone-clone re-anchor described in the triggering issues was verified a
phantom (clones already resolve to self); the real, decidable defect is the
linked-worktree/nested-clone invoking location, and each slice ships an
issue-pinned red-first regression.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Rejecting a work package no longer costs a wasted cycle: the feedback-file
path &lt;code dir=&quot;auto&quot;&gt;agent action review&lt;/code&gt; prints in its rejection command is now one
&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; will actually accept (&lt;code dir=&quot;auto&quot;&gt;#3554&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3430&lt;/code&gt;).&lt;/strong&gt; Before, the
review prompt told the reviewer to write feedback to
&lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;wp&gt;/review-cycle-N.md&lt;/code&gt; and then pass that same file to &lt;code dir=&quot;auto&quot;&gt;move-task --review-feedback-file&lt;/code&gt; — but inside the WP’s own directory that exact
filename is the tool-authored verdict artifact, which the provenance guard
refuses as a feedback source. So the rejection command printed verbatim always
failed, and the reviewer only discovered it after burning a cycle. The
advertised path is now &lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;wp&gt;/review-feedback-N.md&lt;/code&gt; — still committed in
the WP’s own in-repo directory — and the name is owned in &lt;code dir=&quot;auto&quot;&gt;review/cycle.py&lt;/code&gt;
beside the guard that decides what is acceptable, so the printed path and the
accepted path cannot drift apart again.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The two &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; lane guards no longer disagree about a bulk-edit
mission’s own occurrence map, so it can be kept current from the implementing
lane without a manual unwind (&lt;code dir=&quot;auto&quot;&gt;#2980&lt;/code&gt;).&lt;/strong&gt; The pre-commit ownership guard warned
(and let the commit through) while &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; blocked the later transition,
so &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/occurrence_map.yaml&lt;/code&gt; — which DIRECTIVE_035 requires
the lane to update as the sweep proceeds — tripped the gate after the work was
committed. The exception is now expressed once (&lt;code dir=&quot;auto&quot;&gt;is_occurrence_map_path&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;core.constants&lt;/code&gt;) and honored by both guards: the map is permitted on the lane
at both, while every other &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; path stays governed (a sibling
&lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; on the lane is still blocked). The commit-guard &lt;code dir=&quot;auto&quot;&gt;mode&lt;/code&gt; semantics for
non-exception paths are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The lane “no kitty-specs on lane branches” &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; guard no longer
false-positives on inherited planning artifacts in &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt; topology, so lane
transitions stop demanding &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; on every step (&lt;code dir=&quot;auto&quot;&gt;#3271&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#2274&lt;/code&gt;).&lt;/strong&gt;
The guard is a two-pass content delta (the shipped &lt;code dir=&quot;auto&quot;&gt;#2274&lt;/code&gt;/FR-007 fix), but
both passes keyed off the lane’s coordination/mission base ref, whose
merge-base predates the &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**&lt;/code&gt; a lane legitimately holds — prior
missions’ committed artifacts inherited from the base, plus this mission’s own
planning artifacts merged in via the recorded planning commit (ADR
&lt;code dir=&quot;auto&quot;&gt;2026-07-29-1&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#2993&lt;/code&gt;). Both are ancestors of the planning branch but not of
the coord base, so they surfaced as lane-introduced contamination and the
guard’s own “clean the branch” remedy would have deleted other missions’
artifacts — leaving &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt;, documented as “not recommended”, as the only
safe path. The delta is now measured against the planning branch
(&lt;code dir=&quot;auto&quot;&gt;planning_base_branch&lt;/code&gt;, else the mission’s &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;), falling back to
the lane base ref only for legacy/flat missions without &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;. The
sibling branch-currency and implementation-commit gates keep the coordination
ref, which is correct for them.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Three architectural-gate tolls that only ever fired in CI, on legitimate
additive change, are gone (mission &lt;code dir=&quot;auto&quot;&gt;frozen-baseline-toll-reduction&lt;/code&gt;; closes
&lt;code dir=&quot;auto&quot;&gt;#2853&lt;/code&gt;).&lt;/strong&gt; For a developer working in this repo: editing the body of an
allowlisted still-dead symbol no longer forces a hand-edited “rehashed WPxx”
baseline — a new fail-closed helper
(&lt;code dir=&quot;auto&quot;&gt;tests/architectural/_refresh_dead_symbol_hashes.py&lt;/code&gt;) refreshes the
&lt;code dir=&quot;auto&quot;&gt;body_hash&lt;/code&gt; for you and is structurally incapable of admitting a &lt;em&gt;new&lt;/em&gt; dead
symbol (it iterates the existing allowlist only and refuses on an
unrecoverable or ambiguous &lt;code dir=&quot;auto&quot;&gt;module_path&lt;/code&gt;, proven by a non-fakeable
regression). Adding a migration no longer needs a baseline bump: the
&lt;code dir=&quot;auto&quot;&gt;category_1_auto_discovered_migrations&lt;/code&gt; count now derives from the frozenset
authority in both loop arms, so the 105→107 file drift that a hard-pinned
count would red on passes clean. And a legitimate new skip no longer
hard-fails CI — &lt;code dir=&quot;auto&quot;&gt;skip_marker_blocks&lt;/code&gt; growth is now reviewable-with-teeth
(asserted via &lt;code dir=&quot;auto&quot;&gt;record_property&lt;/code&gt;, with the mandatory co-located skip-reason
line as the review signal) instead of a wall. Also drained the inert
&lt;code dir=&quot;auto&quot;&gt;test_no_dead_symbols&lt;/code&gt; baseline key (closing a silent re-entry hole) and
fast-marked the two sub-second gates for local pre-push runs. Every
load-bearing gate is untouched — P0-security boundaries, still-shrinking
burn-downs, zero-pins, and change-detectors all stay frozen behind the C-001
do-not-touch fence; 108 gates green, ruff + mypy &lt;code dir=&quot;auto&quot;&gt;--strict&lt;/code&gt; clean. Test
infrastructure only, no runtime or user-facing change (no version bump).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; no longer rejects a &lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; work package that
owns its &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; deliverables, so a decision checkpoint, freeze/measurement
snapshot, or bulk-edit occurrence map can be a first-class WP (mission
&lt;code dir=&quot;auto&quot;&gt;planning-artifact-kitty-specs-ownership&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3222&lt;/code&gt; and its repro &lt;code dir=&quot;auto&quot;&gt;#2643&lt;/code&gt;).&lt;/strong&gt;
The ownership model already blessed &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; ownership for
&lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;ownership.validation._PLANNING_PREFIXES&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;validate_execution_mode_consistency&lt;/code&gt;) and the lane layer already routes such
WPs to the repo-root planning lane — only the &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; ban disagreed,
rejecting any &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; owned file unconditionally (a later over-reach whose
own rationale was scoped to &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; lane branches). The ban is now
execution-mode-aware: it exempts a &lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; WP whose &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;
are &lt;strong&gt;all&lt;/strong&gt; confined to the planning surfaces (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt;), and
stays fail-closed for &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; and for any WP that also owns code — so a
mislabelled planning WP cannot become a backdoor to owning &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;. Planning-
artifact WPs never reach a lane branch, so the lane commit-guard and move-task
hygiene guards are unaffected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A spec that writes some requirements as plain prose sentences no longer
passes the coverage gate as if they were covered — &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 and name the uncounted ids (mission
&lt;code dir=&quot;auto&quot;&gt;bare-prose-requirements-uncounted&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3396&lt;/code&gt;).&lt;/strong&gt; When a spec declared
some requirements in a recognised shape (a table row, heading, bullet, or
bold-led paragraph) and wrote others as bare sentences, the plain ones were
silently mapped to nothing while both commands reported full coverage. Now
&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; refuses to advance past the tasks boundary and
&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; exits non-zero, each listing the bare-prose requirement ids;
&lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; surfaces them in its JSON (&lt;code dir=&quot;auto&quot;&gt;bare_prose_requirement_ids&lt;/code&gt;)
without gating, since it registers mappings rather than advancing. The
detector was measured against all 368 real &lt;code dir=&quot;auto&quot;&gt;kitty-specs/*/spec.md&lt;/code&gt; files — 1
flagged (0.27%), zero true positives — and that figure is frozen into a
shrink-only CI ratchet.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A mission whose &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; recorded &lt;code dir=&quot;auto&quot;&gt;target_branch: &quot;main&quot;&lt;/code&gt; no longer
wedges permanently at &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, and the &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt; escape
hatch now actually rescues it (&lt;code dir=&quot;auto&quot;&gt;#3482&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3466&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;specify --topology single_branch&lt;/code&gt; run from a checkout on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; writes
&lt;code dir=&quot;auto&quot;&gt;target_branch: &quot;main&quot;&lt;/code&gt;; finalize-tasks then resolved its WP-status
bookkeeping destination from that literal field, tripped the protected-branch
guard, and refused with &lt;code dir=&quot;auto&quot;&gt;PROTECTED_BRANCH_REFUSED&lt;/code&gt; — and passing
&lt;code dir=&quot;auto&quot;&gt;--target-branch &amp;#x3C;feature&gt;&lt;/code&gt; produced a byte-identical refusal still naming
&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, because the override never reached that consumer. There was no
sanctioned way out (no retarget migration, hand-editing &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is
prohibited). The override now persists into the canonical &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;
field before the commit pipeline, so every consumer converges on it and the
mission finalizes; a failed persist is reported to &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; callers instead
of silently returning false.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;retrospect synthesize&lt;/code&gt; now tells you the one thing that is actually
wrong with a retrospective instead of burying it under ~100 errors about a
schema the file was never meant to satisfy (&lt;code dir=&quot;auto&quot;&gt;#3537&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3533&lt;/code&gt;).&lt;/strong&gt; When
a hand-edited retrospective had a single invalid finding category, the
command printed a wall of Pydantic &lt;code dir=&quot;auto&quot;&gt;extra_forbidden&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;Field required&lt;/code&gt;
errors describing the nested reader’s schema — twice leading readers to
believe the tool contradicted itself when one enum value was wrong. It now
reports the generator reader’s accurate one-line diagnosis (e.g.
&lt;code dir=&quot;auto&quot;&gt;not_helpful[0].category is invalid&lt;/code&gt;) and appends the categories that field
actually allows — findings and proposals draw from different sets — so the
fix is obvious instead of a guess.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Writing an honest cardinality assertion in a test no longer costs you an
annotation toll: the golden-count architectural gate
(&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_golden_count_ban.py&lt;/code&gt;) stopped flagging
dynamic-result &lt;code dir=&quot;auto&quot;&gt;len(x) == N&lt;/code&gt; checks (mission
&lt;code dir=&quot;auto&quot;&gt;test-friction-ratchet-remediation&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3458&lt;/code&gt;).&lt;/strong&gt; Before, an ambiguous
&lt;code dir=&quot;auto&quot;&gt;len(result) == 3&lt;/code&gt; over a runtime-computed collection defaulted to &lt;code dir=&quot;auto&quot;&gt;convert&lt;/code&gt;,
so authors had to add &lt;code dir=&quot;auto&quot;&gt;# golden-count: cardinality-is-contract&lt;/code&gt; just to quiet
the gate — on PR #3456 that toll fired twice for zero real catches. The
classifier now treats an ambiguous dynamic-result count as &lt;code dir=&quot;auto&quot;&gt;keep&lt;/code&gt;, so genuine
cardinality asserts pass untouched. The gate’s real job is preserved:
enumerable-domain golden counts like &lt;code dir=&quot;auto&quot;&gt;len(Lane) == 10&lt;/code&gt;, which silently drift
when the domain grows, still convert. Companion guard added in the same slice:
a new CT7 recurrence check (&lt;code dir=&quot;auto&quot;&gt;test_ratchet_positional_anchor_ban.py&lt;/code&gt;) bans
reintroducing raw &lt;code dir=&quot;auto&quot;&gt;(&quot;file.py&quot;, &amp;#x3C;int&gt;)&lt;/code&gt; 2-tuple ratchet keys in
ratchet-substrate-importing seed containers, so the file:line-drift friction
engine cannot regrow. Dev-facing only — no runtime or user-visible behaviour
changes. (Also folds 12 dangling references to the retired
&lt;code dir=&quot;auto&quot;&gt;test_bridge_compat_surface.py&lt;/code&gt; across 9 files — campsite cleanup of the
already-landed #3285 deletion; refs &lt;code dir=&quot;auto&quot;&gt;#2853&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3285&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2633&lt;/code&gt;.)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A misspelled key in an &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt; completeness manifest was
silently discarded — the requirement simply vanished while the manifest still
loaded “successfully” — and the shipped manifests disagreed with the guards
that actually enforce completeness in eight places, while the &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission
type had no manifest at all (&lt;code dir=&quot;auto&quot;&gt;#3413&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3388&lt;/code&gt;).&lt;/strong&gt; Before, a typo’d or
unrecognized key was dropped without a word, so a manifest could quietly
describe a completeness contract different from the one the runtime enforced.
Now &lt;code dir=&quot;auto&quot;&gt;ExpectedArtifactSpec&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ExpectedArtifactManifest&lt;/code&gt; reject unknown keys
(&lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt;) and the loader raises on a schema-invalid manifest instead
of swallowing it; the three shipped &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;
manifests were reconciled to match their guards exactly; &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; gained an
(explicitly descriptive) manifest; and a cross-cutting parity test now catches
the next manifest-vs-guard drift. The schema failure is also actionable and
consistent: it raises a distinguishable &lt;code dir=&quot;auto&quot;&gt;ManifestSchemaError&lt;/code&gt; that names the
offending manifest file, surfaced the same way across &lt;code dir=&quot;auto&quot;&gt;spec-kitty reconcile&lt;/code&gt;,
the background dossier sync (a clear warning in the sync result, not a
swallowed stack trace), and manifest-version resolution — and it now covers
org-authored manifests too, not just the built-in ones (&lt;code dir=&quot;auto&quot;&gt;#3542&lt;/code&gt;). A genuine
internal indexing error is no longer misreported as “fix your manifest”. This
covers &lt;em&gt;schema&lt;/em&gt; violations; a YAML-&lt;em&gt;syntax&lt;/em&gt;-broken manifest still degrades
silently upstream (tracked in &lt;code dir=&quot;auto&quot;&gt;#3412&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A mission running under a non–software-dev workflow no longer gets blocked
by a guard about objects its workflow does not have — for example a &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;
mission’s &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; step demanding “Not all work packages are approved or done”
when a &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; mission has no work packages at all (mission
&lt;code dir=&quot;auto&quot;&gt;mission-type-guard-registry&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3402&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3386&lt;/code&gt;).&lt;/strong&gt; Before, runtime guard
dispatch branched explicitly on the &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;documentation&lt;/code&gt; mission
families and then silently fell through to the software-dev guard table for
everything else — including &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; and any unregistered mission type — so a
mission could be held back by a guard about artifacts it can never possess,
with nothing explaining why. Now guard dispatch is an explicit registry keyed
by mission family: &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; has its own guard table authored from its real state
machine, and an unregistered family fails loudly on the legacy path and
degrades to an explicit, logged neutral result on the composed extension path
— instead of inheriting the wrong rules by accident.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An organisation doctrine pack you registered, validated, and activated
delivered none of its step contracts, artifact requirements, or graph nodes to
&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; at runtime — it does now (&lt;code dir=&quot;auto&quot;&gt;#3520&lt;/code&gt;; closes &lt;code dir=&quot;auto&quot;&gt;#3516&lt;/code&gt;).&lt;/strong&gt; Before, the
runtime consumers (the step-contract executor and its review gate bindings, the
mission-type governance profile, runtime dispatch, and mission-load validation)
all resolved doctrine from the built-in pack plus the project tier only — they
had the org-tier parameter but the callers never passed it, so an org pack was
silently inert past activation. Now a shared &lt;code dir=&quot;auto&quot;&gt;resolve_org_dirs&lt;/code&gt; helper threads
the org tier through each of them; an org &lt;code dir=&quot;auto&quot;&gt;expected-artifacts.yaml&lt;/code&gt; overrides the
governance artifact slot &lt;strong&gt;and&lt;/strong&gt; the dossier completeness index (so an
org-mandated artifact is actually enforced by the missing-artifact detector); and
a configured-but-broken org pack warns (a dropped path or a malformed manifest)
instead of failing silently. &lt;strong&gt;A chain of multiple org packs now works too&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;#3525&lt;/code&gt;): before, the DRG graph merged only the first org pack, so a second
pack’s step contracts loaded but their &lt;code dir=&quot;auto&quot;&gt;delegates_to&lt;/code&gt;/graph edges silently did
not resolve — the runtime now merges the full declared chain in order (later
pack wins on collision, matching the doctrine overlay), and a malformed pack in
the chain is dropped on its own without erasing the others. Projects with no org
pack are unaffected — every path is byte-identical without one.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME&lt;/code&gt; pin census (&lt;code dir=&quot;auto&quot;&gt;arch-adversarial (arch_shard_3)&lt;/code&gt;) was red
on main because a legitimate new isolation pin (&lt;code dir=&quot;auto&quot;&gt;#3497&lt;/code&gt;) landed after the R1a
freeze, and the “shrink-only” ratchet — as landed — could not actually shrink
(&lt;code dir=&quot;auto&quot;&gt;#3509&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;).&lt;/strong&gt; The acute red is fixed by the design-sanctioned owner
adoption (the drifting test requests the exempt &lt;code dir=&quot;auto&quot;&gt;canonical_home&lt;/code&gt; fixture and
drops its own &lt;code dir=&quot;auto&quot;&gt;setenv&lt;/code&gt;), with no edit to any frozen artefact. Beyond that, R1b’s
tombstone burn-down is now wired end to end: &lt;code dir=&quot;auto&quot;&gt;t023&lt;/code&gt; subtracts the tombstoned
set from the anchor, and the production regeneration command
(&lt;code dir=&quot;auto&quot;&gt;_home_pin_scan.render_baseline&lt;/code&gt;) emits tombstones from a new auditable
manifest (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/census/spec_kitty_home_pin_tombstones.yaml&lt;/code&gt;) and
freezes the key-set hash over &lt;code dir=&quot;auto&quot;&gt;census ∪ tombstones&lt;/code&gt;. Regeneration fails closed
if a tombstoned member’s pin is still in the tree, and the ratchet still bites
(a spurious pin reds; a tombstone over a live pin reds). On that seam the
provable class was converged onto the canonical owner — census &lt;code dir=&quot;auto&quot;&gt;40 → 26&lt;/code&gt; — with
the ~23 genuinely-different seams documented out of scope (&lt;code dir=&quot;auto&quot;&gt;#3121&lt;/code&gt;’s confirmed
thesis: a name collision, not a duplicated seam). The subsystem is a no-op while
the manifest is empty (committed artefacts byte-identical). The same convergence
also greens a second, separate gate — limb (g) of the §0.9 &lt;code dir=&quot;auto&quot;&gt;_home_pin_gate&lt;/code&gt;
verdict oracle (&lt;code dir=&quot;auto&quot;&gt;arch-adversarial (arch_shard_2)&lt;/code&gt;), which recomputes the
published end-SHA sites against the tree — by teaching it the same tombstone
term: a converged member’s site is excused only when it is in the manifest, and
the anti-vacuity floor now counts keys that recompute &lt;em&gt;live&lt;/em&gt; so the gate can’t be
bought off by tombstoning the population away.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Machines that never ran the layout migration silently captured zero sync
events while reporting success — now they capture for real (&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; Before, an un-migrated machine defaulted to a legacy capture
layout where live event/body writes were refused deep in the stack and
swallowed — a &lt;strong&gt;silent zero-capture&lt;/strong&gt; that never surfaced to the operator. A
&lt;code dir=&quot;auto&quot;&gt;#3293&lt;/code&gt; regression compounded this by also refusing authenticated hosts
entirely. Now a fresh root resolves to project-only capture &lt;em&gt;before&lt;/em&gt; any
legacy persist; a legacy-with-data root auto-migrates through the canonical
&lt;code dir=&quot;auto&quot;&gt;migrate_journal&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;project_store_migration&lt;/code&gt; engines under a deterministic,
crash-safe migration id (re-entry never bricks the root); the live emit path
completes its cutover via a resolve-before-unit-of-work seam so both emitter
swallow sites are observable instead of silent (never-raises contract kept
intact); and credential parsing is restored as a pure auth signal (never a
physical-store selector), so an already-authenticated host stops being
refused.&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;/&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; no longer block on a fully-absent or legacy
&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;-only charter — both are now advisory, matching &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt;’s
existing tolerance (&lt;code dir=&quot;auto&quot;&gt;#3498&lt;/code&gt;).&lt;/strong&gt; The shared preflight hook
(&lt;code dir=&quot;auto&quot;&gt;run_preflight_or_abort&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;charter_runtime/preflight/hook.py&lt;/code&gt;) never
forwarded &lt;code dir=&quot;auto&quot;&gt;allow_missing_charter=True&lt;/code&gt; to the runner, so a brand-new project
with no &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/&lt;/code&gt; contents at all, or a pre-inversion project
carrying only &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; absent, #2831’s
shape), hard-blocked &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; even though the dashboard already
tolerated both states. &lt;code dir=&quot;auto&quot;&gt;run_charter_preflight()&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;charter_runtime/preflight/runner.py&lt;/code&gt;) gains a new &lt;code dir=&quot;auto&quot;&gt;_is_legacy_charter_bundle&lt;/code&gt;
wording selector and a distinct, more detailed warning constant for the
legacy-bundle case. Canonical layer state alone decides the exemption:
source and synced bundle must be &lt;code dir=&quot;auto&quot;&gt;missing&lt;/code&gt;, and synthesized DRG must be
&lt;code dir=&quot;auto&quot;&gt;missing&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;built_in_only&lt;/code&gt;; display-only &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; only selects warning
copy after that decision. Stale, invalid, or other partial residue therefore
keeps blocking even when &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; exists. Advancing/query and human/JSON
&lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; modes plus &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; emit the advisory to stderr without polluting
JSON stdout; dashboard persists/renders it. The canonical &lt;code dir=&quot;auto&quot;&gt;CHARTER_MD&lt;/code&gt; import
stays lazy so &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; does not pull the heavyweight charter graph at startup.
The legacy warning
names the executable migration command explicitly:
&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter generate --no-from-interview&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A reviewer running a different agent profile than the implementer can now
claim a completed work package for review — the false “WP already claimed for
review by &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;implementer&gt;&lt;/code&gt;” refusal is gone (&lt;code dir=&quot;auto&quot;&gt;#3455&lt;/code&gt;).&lt;/strong&gt; Before, claiming a WP
for review (&lt;code dir=&quot;auto&quot;&gt;for_review → in_review&lt;/code&gt;) compared the claim holder’s identity,
which at &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; is structurally the &lt;em&gt;implementer&lt;/em&gt; — so any cross-profile
reviewer (e.g. &lt;code dir=&quot;auto&quot;&gt;reviewer-renata&lt;/code&gt; reviewing &lt;code dir=&quot;auto&quot;&gt;python-pedro&lt;/code&gt;’s work) was rejected
as a self-review collision, and the block surfaced on the status aggregate
seam rather than the &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; command. Now the &lt;code dir=&quot;auto&quot;&gt;for_review → in_review&lt;/code&gt; edge
is allow-only, and a genuine reviewer-vs-reviewer collision is decided by a
single pure predicate at the &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; re-claim site (a real second reviewer
is still blocked, and the message names the holder). Role is read from the
reduced status slot, never by splitting the compact actor string (&lt;code dir=&quot;auto&quot;&gt;#2861&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coord/primary partition-authority residuals: out-of-loop callers now resolve
the correct partition surface, so coordination-topology missions stop deadlocking
and mis-reporting (mission &lt;code dir=&quot;auto&quot;&gt;partition-authority-residuals-01M021K9&lt;/code&gt;; epics &lt;code dir=&quot;auto&quot;&gt;#2160&lt;/code&gt;
/ &lt;code dir=&quot;auto&quot;&gt;#2720&lt;/code&gt;).&lt;/strong&gt; Under coordination topology a cluster of out-of-loop and
cross-function callers still read PRIMARY-partition artifacts off the &lt;code dir=&quot;auto&quot;&gt;-coord&lt;/code&gt;
husk, or wrote lifecycle evidence to the wrong partition — degrading silently or
&lt;strong&gt;deadlocking &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt;&lt;/strong&gt;. Eleven fixes, each a caller reroute through
the canonical &lt;code dir=&quot;auto&quot;&gt;mission_runtime.artifacts&lt;/code&gt; placement seam (STATUS reads stay on
COORD): the coord &lt;strong&gt;merge deadlock&lt;/strong&gt; is gone — the review-override write now lands
on the surface the merge gate reads, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; gains a
&lt;code dir=&quot;auto&quot;&gt;--skip-review-artifact-check&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--note&lt;/code&gt; escape hatch that records the bypass as
durable override evidence (&lt;code dir=&quot;auto&quot;&gt;#2959&lt;/code&gt;); merge risk/dependency gates and the bulk-edit
diff base stop silently SKIPping / seeing an empty graph on coord missions
(&lt;code dir=&quot;auto&quot;&gt;#3439&lt;/code&gt;); the review handoff renders true per-WP lanes instead of a blanket stale
&lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#2698&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; commits its post-transition annotation atomically,
leaving a clean status tree (&lt;code dir=&quot;auto&quot;&gt;#2939&lt;/code&gt;); the 4th safe-commit target resolves through
the shared degrade helper with refusal-parity preserved (&lt;code dir=&quot;auto&quot;&gt;#2966&lt;/code&gt;); and
&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; versions &lt;code dir=&quot;auto&quot;&gt;wps.yaml&lt;/code&gt; so a finalized checkpoint reproduces its own
state (&lt;code dir=&quot;auto&quot;&gt;#2937&lt;/code&gt;). Diagnostic-output fidelity (&lt;code dir=&quot;auto&quot;&gt;#2720&lt;/code&gt;): &lt;code dir=&quot;auto&quot;&gt;check-prerequisites&lt;/code&gt;
sources its inventory from canonical mission writer metadata (&lt;code dir=&quot;auto&quot;&gt;#2692&lt;/code&gt;); mission
doctors validate &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; against the writer schema — killing false
&lt;code dir=&quot;auto&quot;&gt;UNKNOWN_SHAPE&lt;/code&gt; findings — and &lt;code dir=&quot;auto&quot;&gt;doctor coordination&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; scoping
(&lt;code dir=&quot;auto&quot;&gt;#2696&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;retrospect summary&lt;/code&gt; discovers missions under the canonical
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/*&lt;/code&gt; root (&lt;code dir=&quot;auto&quot;&gt;#2717&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;status doctor&lt;/code&gt; no longer reports Healthy over
blanked runtime attribution (&lt;code dir=&quot;auto&quot;&gt;#2960&lt;/code&gt;); and mission-state repair stops quarantining
legacy &lt;code dir=&quot;auto&quot;&gt;WPStatusChanged&lt;/code&gt; lane transitions into a zero-WP &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3066&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Review rejections now reach the hosted dashboard instead of being silently
dropped by sync (&lt;code dir=&quot;auto&quot;&gt;#3307&lt;/code&gt; P0; &lt;code dir=&quot;auto&quot;&gt;#3444&lt;/code&gt;).&lt;/strong&gt; Before, when a reviewer sent a work
package back for rework — any backward review-rejection move (&lt;code dir=&quot;auto&quot;&gt;* → planned&lt;/code&gt;,
or &lt;code dir=&quot;auto&quot;&gt;in_review → in_progress&lt;/code&gt;) — the CLI stamped the status event &lt;code dir=&quot;auto&quot;&gt;force=False&lt;/code&gt;
and, for &lt;code dir=&quot;auto&quot;&gt;in_review → in_progress&lt;/code&gt;, left off the &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;. Those events
were accepted on your machine but violated the shared &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; wire
contract the hosted ingestion endpoint enforces, so hosted sync silently
rejected them: a rejection that looked applied locally never propagated to the
team dashboard (in the reported case a whole batch surfaced 11+ days later as
bulk sync failures). Root cause was two same-named &lt;code dir=&quot;auto&quot;&gt;validate_transition&lt;/code&gt;
functions giving opposite answers — the emit path consulted only the
CLI-local state machine, never the wire contract the server enforces. The
emit-force decision now gates on &lt;strong&gt;both&lt;/strong&gt;, so the review-rejection family
emits &lt;code dir=&quot;auto&quot;&gt;force=True&lt;/code&gt; (still carrying the structured rewind rationale) and threads
the &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt; on the wire, producing events the project’s own vendored
contract accepts. Reviewers are now told — at the &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; tool surface and
in the review skills — that a rejection rationale (&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;) is mandatory, because it travels on the wire as that &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coordination-topology missions no longer wedge lane allocation by
committing PRIMARY planning artifacts onto the coordination branch (mission
&lt;code dir=&quot;auto&quot;&gt;write-path-integrity-01KZZD69&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3371&lt;/code&gt; P0, &lt;code dir=&quot;auto&quot;&gt;#2549&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3128&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3373&lt;/code&gt;;
advances &lt;code dir=&quot;auto&quot;&gt;#2160&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;#1878&lt;/code&gt;).&lt;/strong&gt; Before, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s planning auto-commit routed
the whole batch verbatim to the coordination branch under coord topology, so a
PRIMARY &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; landed on coord and the lane allocator’s recorded-planning
merge hit an add/add conflict — blocking every work-package claim on a
PR-bound &lt;code dir=&quot;auto&quot;&gt;--start-branch&lt;/code&gt; + coord mission with no self-service recovery. Root
cause was one layer deeper than the commit site: &lt;code dir=&quot;auto&quot;&gt;BookkeepingTransaction.acquire&lt;/code&gt;
&lt;em&gt;unconditionally&lt;/em&gt; redirected writes to the coordination worktree, so this fix
adds an opt-in &lt;code dir=&quot;auto&quot;&gt;commit_to_primary_target&lt;/code&gt; that PRIMARY planning commits use to
land on the mission’s own target branch (every status/coord caller keeps the
default — zero regression to coord routing). A partition guard at the
planning-commit seam now fails loud on any PRIMARY→coord / COORD→lane
mis-route (excluding self-bookkeeping &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; co-travel), closing the same
class for &lt;code dir=&quot;auto&quot;&gt;move-task --force&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#2549&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;’s lane-state &lt;strong&gt;read&lt;/strong&gt; now
resolves &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; from that same PRIMARY partition (via the kind-aware
placement seam, matching its canonical &lt;code dir=&quot;auto&quot;&gt;LANE_STATE&lt;/code&gt; classification), so the
read and write agree for coord-topology missions — previously the read still
looked on the coordination surface, which broke &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; end-to-end.
Separately, 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 &lt;strong&gt;fail closed&lt;/strong&gt; when invoked from a checkout the
mission does not own (&lt;code dir=&quot;auto&quot;&gt;#3128&lt;/code&gt;): a &lt;code dir=&quot;auto&quot;&gt;write_intent&lt;/code&gt;-gated &lt;code dir=&quot;auto&quot;&gt;CheckoutIdentityError&lt;/code&gt;
at the real workspace chokepoint (&lt;code dir=&quot;auto&quot;&gt;workspace/context.py::resolve_workspace_for_wp&lt;/code&gt;)
refuses foreign-checkout writes without ever refusing reads or planning. The
four re-implementations of the git-common-dir/toplevel probe are unified behind
one primitive (&lt;code dir=&quot;auto&quot;&gt;#3373&lt;/code&gt;), and a static &lt;code dir=&quot;auto&quot;&gt;tests/architectural/&lt;/code&gt; gate plus a
cross-partition repo scan keep the P0 class from silently regressing. The
frontmatter/upgrade-wedge slice (&lt;code dir=&quot;auto&quot;&gt;#3372&lt;/code&gt;) and &lt;code dir=&quot;auto&quot;&gt;#2702&lt;/code&gt; were confirmed already
closed (by mission &lt;code dir=&quot;auto&quot;&gt;#3383&lt;/code&gt; and prior work) and left out of scope.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Activating a charter directive no longer silently drops every org-pack
artifact from the doctrine graph (mission &lt;code dir=&quot;auto&quot;&gt;org-activation-scan-dirs-01KZY1PT&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3399&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3385&lt;/code&gt;).&lt;/strong&gt; Before, the charter activation allow-list scanned
org packs at a phantom &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;root&gt;/&amp;#x3C;plural&gt;/built-in&lt;/code&gt; layout that no org pack
actually uses, while the live doctrine loader reads the flat &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;root&gt;/&amp;#x3C;plural&gt;&lt;/code&gt;
layout. The two disagreed silently: the moment an operator ran
&lt;code dir=&quot;auto&quot;&gt;charter activate directive &amp;#x3C;stem&gt;&lt;/code&gt;, every org-pack URN failed to resolve and
was dropped from the filtered graph with no error — so a project’s own
directives, tactics, and profiles vanished from governance the first time
anyone activated a single artifact. Now the activation scan reads the same
flat layout the loader does (plus the legacy nested layout additively, with
the flat entry winning a same-name collision), so activating one artifact
leaves the rest of the org pack intact.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;researcher-robbie&lt;/code&gt; agent profile no longer introduces itself under the
wrong name (&lt;code dir=&quot;auto&quot;&gt;#3377&lt;/code&gt;).&lt;/strong&gt; Before, the profile’s &lt;code dir=&quot;auto&quot;&gt;purpose&lt;/code&gt; and
initialization-declaration prose still read “Researcher Rosa” — a leftover the
profile rename missed — so any agent that loaded &lt;code dir=&quot;auto&quot;&gt;researcher-robbie&lt;/code&gt; and
followed its initialization declaration announced itself as “Researcher Rosa”,
even though the profile’s own &lt;code dir=&quot;auto&quot;&gt;name&lt;/code&gt; field, its docs page, and every sibling
profile said “Researcher Robbie”. Now the prose matches the profile’s own
&lt;code dir=&quot;auto&quot;&gt;name&lt;/code&gt;, and a parametrized test asserts every shipped profile’s self-identity
prose equals its &lt;code dir=&quot;auto&quot;&gt;name&lt;/code&gt; field, so this class of identity drift cannot silently
recur.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;sync import-history&lt;/code&gt; now imports legacy work packages that carry retired
frontmatter fields, instead of skipping them (mission
&lt;code dir=&quot;auto&quot;&gt;first-sync-preflight-01KZZ9Q1&lt;/code&gt; FR-011; &lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;).&lt;/strong&gt; The import scan read WP
frontmatter with the strict authoring model (&lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt;), so a
historical WP carrying a field the current schema no longer knows (e.g.
&lt;code dir=&quot;auto&quot;&gt;estimated_lines&lt;/code&gt;) raised a validation error, was logged “unreadable”, and was
degraded to a bare back-fill — losing its real title and dependencies. The
import path now uses a lenient reader that drops unrecognised legacy keys
while still validating known fields, so genuinely-malformed frontmatter is
still skipped fail-loud. Authoring keeps the strict typo guard unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;sync status&lt;/code&gt; now flags an unreachable sync server and how to repoint it,
instead of reporting a bare “Unexpected status” (mission
&lt;code dir=&quot;auto&quot;&gt;first-sync-preflight-01KZZ9Q1&lt;/code&gt; FR-003; &lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;).&lt;/strong&gt; A configured server that
answers with a gateway-class status (&lt;code dir=&quot;auto&quot;&gt;502&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;503&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;504&lt;/code&gt;) — the signature of a
decommissioned platform env or a torn-down preview, which is exactly how a
first sync against a stale &lt;code dir=&quot;auto&quot;&gt;*.platformsh.site&lt;/code&gt; URL stranded — was folded into
the generic “Unexpected HTTP 502” branch, giving the operator no signal that
the URL itself might be the fault. The health probe now reports these as
&lt;strong&gt;Server unavailable&lt;/strong&gt;, reassuring that queued events are retained and will
drain on recovery (consistent with the offline queue’s transient-retry
handling), and — for the decommissioned case — naming the URL and the exact
recovery (&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync server &amp;#x3C;url&gt;&lt;/code&gt; then &lt;code dir=&quot;auto&quot;&gt;auth login --force&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;auth login&lt;/code&gt; now resolves the server the same way &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; does — env over
&lt;code dir=&quot;auto&quot;&gt;[sync].server_url&lt;/code&gt; over the documented default — instead of the env-only
accessor that errored when only &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync server&lt;/code&gt; had been set
(&lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;, FR-005).&lt;/strong&gt; Before, a user who set their server via &lt;code dir=&quot;auto&quot;&gt;sync server&lt;/code&gt;
still hit “SPEC_KITTY_SAAS_URL environment variable is not set” on login, so a
token could only be minted against one server while sync targeted another. It
still refuses (with a remedy naming both &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;sync server&lt;/code&gt;) when neither is set, rather than silently defaulting to the dev
URL. One of the ten-gate first-sync gauntlet fixes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; no longer reports “Sync is healthy” while the server probe
says otherwise (mission &lt;code dir=&quot;auto&quot;&gt;first-sync-preflight-01KZZ9Q1&lt;/code&gt; FR-002; &lt;code dir=&quot;auto&quot;&gt;#3406&lt;/code&gt;).&lt;/strong&gt;
The health summary only escalated a server verdict of &lt;code dir=&quot;auto&quot;&gt;Unreachable&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Error&lt;/code&gt;;
a &lt;code dir=&quot;auto&quot;&gt;Permission denied&lt;/code&gt; (403), gateway-down (5xx), or unexpected-status verdict
printed a coloured row in the table but never entered the issue list, so the
doctor still declared everything healthy while the live drain was blocked —
the false-green that hid a broken first sync. Every non-healthy server verdict
(anything but &lt;code dir=&quot;auto&quot;&gt;Connected&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;Disabled&lt;/code&gt;, excluding the auth states the
auth/session block already owns) now reaches the summary with the probe’s own
remediation note.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; now run correctly from a caller-owned linked
git worktree, and each worktree’s mission state stays isolated (mission
&lt;code dir=&quot;auto&quot;&gt;worktree-owned-root-3328-01KZRG01&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3346&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3328&lt;/code&gt;).&lt;/strong&gt; Before,
invoking &lt;code dir=&quot;auto&quot;&gt;create&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; from an explicit linked checkout followed the
worktree’s &lt;code dir=&quot;auto&quot;&gt;.git&lt;/code&gt; pointer back to the primary checkout and tried to drive the
mission there — failing with &lt;code dir=&quot;auto&quot;&gt;START_BRANCH_FAILED&lt;/code&gt; when that branch was
already checked out, and risking one worktree reading or writing another
worktree’s mission state. Now the invoking checkout root is validated with
fail-closed git-topology ownership checks and threaded through creation,
resolution, &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;, runtime state, refs, and commits, so two linked worktrees
can create and advance distinct missions concurrently with no
cross-contamination while the primary checkout is left untouched. Managed
Spec Kitty coordination and lane worktrees remain refused.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The ADR inventory freshener now targets the canonical &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt; era index
instead of the redirect README, so newly added ADRs are actually indexed
(&lt;code dir=&quot;auto&quot;&gt;#3346&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3345&lt;/code&gt;).&lt;/strong&gt; Before, the freshener pointed at the redirect
README and left the canonical era index stale, so a new ADR could pass docs
freshness without appearing in the index maintainers browse. Now it writes the
canonical era index directly.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Direct sync ingress no longer drifts to a shared/primary team when the
session read transiently returns None (&lt;code dir=&quot;auto&quot;&gt;#738&lt;/code&gt;/spec-kitty-saas &lt;code dir=&quot;auto&quot;&gt;#911&lt;/code&gt;).&lt;/strong&gt; The
fan-out handler resolved the producer scope as
&lt;code dir=&quot;auto&quot;&gt;read_queue_scope_from_session() or read_queue_scope_from_credentials()&lt;/code&gt;. The
session path is fail-closed to the user’s Private Teamspace, but the credentials
fallback returns whatever &lt;code dir=&quot;auto&quot;&gt;team_slug&lt;/code&gt; the credentials TOML last stored (often a
shared/primary team, e.g. &lt;code dir=&quot;auto&quot;&gt;stijn&lt;/code&gt; rather than &lt;code dir=&quot;auto&quot;&gt;stijn-private&lt;/code&gt;). During a token
refresh or a rehydrate miss the session read returns None and ingress silently
rerouted to that team — forking the producer-scoped journal (&lt;code dir=&quot;auto&quot;&gt;journal-&amp;#x3C;scope&gt;.db&lt;/code&gt;)
and materializing the project under the wrong team server-side, so the
private→shared share could never find it (the Kitty Prime “I can’t see the
team’s work” symptom). Ingress is now session-only: it honours the fail-closed
contract and skips queueing when the Private Teamspace can’t be resolved, rather
than attributing the event to the wrong scope. The credentials reader stays for
the diagnostic call sites (e.g. &lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt;/preflight, which compare the two
scopes to &lt;em&gt;detect&lt;/em&gt; exactly this drift).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Root README guide links point at the post-IA &lt;code dir=&quot;auto&quot;&gt;tutorials/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;how-to/&lt;/code&gt;
paths.&lt;/strong&gt; Fixes GitHub 404s from stale flat &lt;code dir=&quot;auto&quot;&gt;docs/guides/*.md&lt;/code&gt; hrefs after the
guides subdivision (e.g. Your First Mission).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Four operator-visible read/write-consistency defects, where a step trusted a
partial, pre-merge, or recomputed-from-scratch view of persisted state, are
fixed (mission &lt;code dir=&quot;auto&quot;&gt;mission-a-p0-consistency&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3320&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3231&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3334&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3311&lt;/code&gt;).&lt;/strong&gt;
Concretely: &lt;code dir=&quot;auto&quot;&gt;retrospect create --update&lt;/code&gt; reported and emitted the &lt;em&gt;pre-merge&lt;/em&gt;
record — the counts, JSON &lt;code dir=&quot;auto&quot;&gt;findings_status&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptured&lt;/code&gt; event
disagreed with what was written to disk; now they read the persisted record back
(&lt;code dir=&quot;auto&quot;&gt;#3320&lt;/code&gt;). A leftover &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; scaffold placeholder blocked acceptance
for a mission whose real criteria all passed; the verdict now exempts &lt;em&gt;only&lt;/em&gt; the
empty placeholder row, so a real still-pending criterion still blocks as before
(&lt;code dir=&quot;auto&quot;&gt;#3231&lt;/code&gt;). A failed &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; stripped &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; from
&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; and wedged the project as unrecoverable &lt;code dir=&quot;auto&quot;&gt;LEGACY&lt;/code&gt;; project metadata
now round-trips the stamp so a failed migration stays recoverable (&lt;code dir=&quot;auto&quot;&gt;#3334&lt;/code&gt;).
Re-running &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; after implementation had begun clobbered the recorded
&lt;code dir=&quot;auto&quot;&gt;planning_commit_sha&lt;/code&gt;; it now preserves provenance once any work package has left
&lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#3311&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Six upgrade-wedge failures, where a stuck migration left no self-service way
out, are fixed (&lt;code dir=&quot;auto&quot;&gt;#3383&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3335&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3336&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3337&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3338&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3339&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3372&lt;/code&gt;).&lt;/strong&gt; Concretely: a failed &lt;code dir=&quot;auto&quot;&gt;runtime_state_backfill&lt;/code&gt; aborted mid-walk with
no record of what it had already written, leaving the operator unable to tell
how far the migration got; it now enumerates every mission and file already
persisted before it stopped (&lt;code dir=&quot;auto&quot;&gt;#3335&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --dry-run&lt;/code&gt; (and
&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;) could report nothing pending while the real run went on to apply many
migrations, because the preview computed pending work through a different path
than the real run; the preview now drives off the same migration selector, so it
reports the true pending set (&lt;code dir=&quot;auto&quot;&gt;#3336&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;agent mission create --json&lt;/code&gt; returned a
bare &lt;code dir=&quot;auto&quot;&gt;CHARTER_PACK_CONFIG_INVALID&lt;/code&gt; error code with no fix steps, discarding the
human-readable remediation text a plain-text run would have shown; the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;
envelope now carries the remediation body alongside the code (&lt;code dir=&quot;auto&quot;&gt;#3337&lt;/code&gt;). The
&lt;code dir=&quot;auto&quot;&gt;migrate backfill-runtime-state ... --dry-run&lt;/code&gt; diagnostic a failed migration
told operators to run was itself blocked behind that same failed migration — a
catch-22 with no way out; the &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; form is now ungated (the mutating form
stays blocked) (&lt;code dir=&quot;auto&quot;&gt;#3338&lt;/code&gt;). A failed &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; left the operator’s checkout
switched onto the coordination branch it had just minted, and left that orphan
branch behind; it now restores the original checkout and deletes the branch it
created (&lt;code dir=&quot;auto&quot;&gt;#3339&lt;/code&gt;). The review cycle could append a duplicate &lt;code dir=&quot;auto&quot;&gt;review_feedback&lt;/code&gt;
frontmatter key, producing invalid YAML that later wedged upgrades trying to
parse it; the writer that appended on a miss is retired (it now fails closed),
duplicate-key artifacts are detected and can be repaired non-destructively, and
the frontmatter reader names every offending key (&lt;code dir=&quot;auto&quot;&gt;#3372&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-breaking-changes&quot;&gt;💥 Breaking Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&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 fails (exit code &lt;code dir=&quot;auto&quot;&gt;1&lt;/code&gt;) for
three previously-passing org-pack shapes (mission
&lt;code dir=&quot;auto&quot;&gt;org-pack-authoring-diagnostics-01KZY463&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3387&lt;/code&gt;).&lt;/strong&gt; All three close a
silent-success authoring gap where a pack passed validation cleanly and only
failed — or silently misbehaved — at runtime or on adoption. Concretely: a
merge-time-skipped agent profile (a profile that individually passes schema
validation but fails to field-merge onto a same-ID built-in profile) now
surfaces as a &lt;code dir=&quot;auto&quot;&gt;profile_skipped&lt;/code&gt; error, sourced from
&lt;code dir=&quot;auto&quot;&gt;AgentProfileRepository.skipped_profiles()&lt;/code&gt; rather than requiring a separate
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine --json&lt;/code&gt; invocation. A nested
&lt;code dir=&quot;auto&quot;&gt;assets/&amp;#x3C;pack&gt;/x.asset.yaml&lt;/code&gt; manifest with a schema violation is now scanned
recursively, matching what &lt;code dir=&quot;auto&quot;&gt;AssetRepository&lt;/code&gt; loads at runtime (previously
invisible to validation). 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 produces a
&lt;code dir=&quot;auto&quot;&gt;drg_root_graph_missing&lt;/code&gt; error — the runtime
(&lt;code dir=&quot;auto&quot;&gt;src/charter/_drg_helpers.py:load_validated_graph&lt;/code&gt;) reads only the pack
root, never &lt;code dir=&quot;auto&quot;&gt;drg/&lt;/code&gt; fragments, so this shape previously validated cleanly and
then silently zeroed the pack’s DRG content on adoption (per sibling mission
&lt;code dir=&quot;auto&quot;&gt;org-pack-drg-root-graph-guard-01KZY0QT&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3384&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;validate_pack()&lt;/code&gt; gains a
keyword-only &lt;code dir=&quot;auto&quot;&gt;check_drg_root: bool = True&lt;/code&gt; parameter for the new DRG check;
&lt;code dir=&quot;auto&quot;&gt;pack_assembler.py&lt;/code&gt;’s internal round-trip validation of its own
drg/-fragments-only output passes &lt;code dir=&quot;auto&quot;&gt;check_drg_root=False&lt;/code&gt; unconditionally (a
structural carve-out — the assembler never writes a pack-root graph).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;326rc1---2026-08-12&quot;&gt;[3.2.6rc1] - 2026-08-12&lt;/h2&gt;
&lt;aside aria-label=&quot;Warning&quot; class=&quot;starlight-aside starlight-aside--caution&quot;&gt;&lt;p class=&quot;starlight-aside__title&quot; aria-hidden=&quot;true&quot;&gt;&lt;svg viewBox=&quot;0 0 24 24&quot; width=&quot;16&quot; height=&quot;16&quot; fill=&quot;currentColor&quot; class=&quot;starlight-aside__icon&quot;&gt;&lt;path d=&quot;M12 16a1 1 0 1 0 0 2 1 1 0 0 0 0-2Zm10.67 1.47-8.05-14a3 3 0 0 0-5.24 0l-8 14A3 3 0 0 0 3.94 22h16.12a3 3 0 0 0 2.61-4.53Zm-1.73 2a1 1 0 0 1-.88.51H3.94a1 1 0 0 1-.88-.51 1 1 0 0 1 0-1l8-14a1 1 0 0 1 1.78 0l8.05 14a1 1 0 0 1 .05 1.02v-.02ZM12 8a1 1 0 0 0-1 1v4a1 1 0 0 0 2 0V9a1 1 0 0 0-1-1Z&quot;&gt;&lt;/path&gt;&lt;/svg&gt;Warning&lt;/p&gt;&lt;div class=&quot;starlight-aside__content&quot;&gt;&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;3.2.6rc1&lt;/code&gt; is a Release Candidate — an internal, delta build published for validation, NOT an official &lt;code dir=&quot;auto&quot;&gt;3.2.6&lt;/code&gt; release.&lt;/strong&gt; It ships as a GitHub &lt;em&gt;prerelease&lt;/em&gt; and to PyPI as a PEP 440 prerelease, so ordinary installers skip it unless you explicitly opt in with &lt;code dir=&quot;auto&quot;&gt;--pre&lt;/code&gt;. Do &lt;strong&gt;not&lt;/strong&gt; use it for production or general rollout. The last official release remains &lt;code dir=&quot;auto&quot;&gt;v3.2.5&lt;/code&gt;; when &lt;code dir=&quot;auto&quot;&gt;3.2.6&lt;/code&gt; is finalized its changelog section supersedes this one.&lt;/p&gt;&lt;/div&gt;&lt;/aside&gt;
&lt;p&gt;&lt;strong&gt;Install for testing (opt-in only):&lt;/strong&gt;&lt;/p&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:#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:#82AAFF;--1:#3B61B0&quot;&gt;--pre&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==3.2.6rc1&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:#919F9F;--1:#5F636F&quot;&gt;# or, inside an existing environment:&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;pip&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:#82AAFF;--1:#3B61B0&quot;&gt;--pre&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==3.2.6rc1&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;strong&gt;Highlights since &lt;code dir=&quot;auto&quot;&gt;v3.2.5&lt;/code&gt;&lt;/strong&gt; — the operator-facing changes worth exercising in this candidate:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Breaking — built-in doctrine content relocated 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;). Repoint any reference that still targets the old &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&amp;#x3C;kind&gt;/built-in/&lt;/code&gt; path.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Breaking — local &lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt; tracker sync now requires a recorded egress decision&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;tracker-egress-refusal-3108&lt;/code&gt;). A binding that never recorded hosted-sync consent stops syncing on upgrade until you record &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Breaking — the &lt;code dir=&quot;auto&quot;&gt;rtk-search-tooling&lt;/code&gt; toolguide is removed&lt;/strong&gt;, and the &lt;code dir=&quot;auto&quot;&gt;3.2.6_retire_rtk_search_tooling&lt;/code&gt; upgrade migration strips it from projects that had it activated (it runs automatically on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; and is safe to re-run).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Breaking — org packs with an unrecognised agent-profile or DRG key now fail to load&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-silence-guards&lt;/code&gt;). Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine --json&lt;/code&gt; and check &lt;code dir=&quot;auto&quot;&gt;skipped_profiles&lt;/code&gt; before you upgrade.&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&lt;/strong&gt; — it preserves backed governance content by default, with &lt;code dir=&quot;auto&quot;&gt;--prune&lt;/code&gt; as the explicit opt-in and &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; to preview (mission &lt;code dir=&quot;auto&quot;&gt;charter-synthesize-reconciliation&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3270&lt;/code&gt; P0, folds &lt;code dir=&quot;auto&quot;&gt;#2777&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#3052&lt;/code&gt;). The &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; boundary no longer hard-blocks until you resynthesize.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Approving a work package after a rejection now sticks with no override flag required&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;review-verdict-write-integrity&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3044&lt;/code&gt;) — the reject → fix → approve cycle no longer forces &lt;code dir=&quot;auto&quot;&gt;--skip-review-artifact-check&lt;/code&gt;.&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 (mission &lt;code dir=&quot;auto&quot;&gt;kernel-clock-single-door&lt;/code&gt;; &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;li&gt;&lt;strong&gt;CLI UX: 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 no behavior change to existing commands.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The complete, factual list of changes for this candidate follows in the entries below.&lt;/p&gt;
&lt;h3 id=&quot;-added-2&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Multi-Agent Parallel Development and Orchestrator Quickstart tutorials now open
with illustrated Mission Kitty splashes (&lt;code dir=&quot;auto&quot;&gt;#3331&lt;/code&gt;).&lt;/strong&gt; Each page adds a decorative hero and
a one-line caption that points to the authoritative workflow steps in the prose
below, matching the pattern introduced in &lt;code dir=&quot;auto&quot;&gt;#3276&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Governed Charter Workflow, Claude Code Integration, and Claude Code Workflow
tutorials now open with illustrated Mission Kitty splashes, plus TIP cross-links
and hub &lt;code dir=&quot;auto&quot;&gt;related:&lt;/code&gt; edges (&lt;code dir=&quot;auto&quot;&gt;#3333&lt;/code&gt;).&lt;/strong&gt; Each page adds a decorative hero and a one-line
caption; the Charter tour points at the governance how-tos, and the two Claude
Code tutorials link each other for slash-command vs CLI/dashboard paths.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Three #3276 Mission Kitty heroes are regenerated as decorative-only splashes
(missions overview, your first mission, when-to-use-modes alternate art) (&lt;code dir=&quot;auto&quot;&gt;#3341&lt;/code&gt;).&lt;/strong&gt;
Replaces caption-mitigated board labels with abstract art; each PNG compressed
to ≤500 KB. Memphis, four-paths, and corporate-comics assets on when-to-use-modes
are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The DRG now carries a whole-graph, action-only reachability companion guard, and six genuine residual
orphans are wired into the graph (mission &lt;code dir=&quot;auto&quot;&gt;drg-reachability-metric-wiring-01KZS5VR&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3009&lt;/code&gt; point 3,
&lt;code dir=&quot;auto&quot;&gt;#1923&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;TestReachabilityCompanionGuard&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;tests/doctrine/drg/test_reachability.py&lt;/code&gt; asserts every
activatable-kind node reachable from &lt;strong&gt;neither&lt;/strong&gt; the action channel nor the profile channel’s
&lt;code dir=&quot;auto&quot;&gt;{requires, specializes_from, suggests}&lt;/code&gt; web is correctly partitioned into “both-channel dead” vs
“profile-delivered” — live totality/disjointness assertions against the graph measured at test time, not
an exact-membership pin (the ever-growing frozenset-literal pin was softened out during PR #3342 landing,
consistent with mission &lt;code dir=&quot;auto&quot;&gt;assertive-test-suite-sanitation-01KZME3P&lt;/code&gt;’s “test plausible graph behavior, not
exact ever-growing membership”). A fixed anti-gaming gate (&lt;code dir=&quot;auto&quot;&gt;TestActionUnreachableShippedLedgerCoverage&lt;/code&gt;)
independently proves the thirteen URNs this mission wires are genuinely action-reachable and named in a
wiring-table ledger row, so a node with outbound edges but no inbound path still cannot pass silently. Six
traced inbound edges (&lt;code dir=&quot;auto&quot;&gt;procedure:refactoring → DISCIPLINED_REFACTORING&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_024&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_025&lt;/code&gt; →
&lt;code dir=&quot;auto&quot;&gt;RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_030&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;USE_MUTATION_TESTING_TO_VALIDATE_TEST_QUALITY&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;researcher-robbie → spike-timebox-policy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lexical-larry → glossary-maintenance-workflow&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;minutes-maker-mahad → meeting-minutes-pipeline&lt;/code&gt;) move the action-only whole-graph residual &lt;strong&gt;88 → 75&lt;/strong&gt; and
the both-channel-dead subset &lt;strong&gt;38 → 34&lt;/strong&gt; (descriptive measurements at time of wiring, not pinned
assertions). The &lt;code dir=&quot;auto&quot;&gt;#1923&lt;/code&gt; DRG orphan-residual record
(&lt;code dir=&quot;auto&quot;&gt;kitty-specs/mission-lifecycle-dispatch-drg-closeout-01KV0S99/drg-orphan-residual.md&lt;/code&gt;) is truth-upped
against the wired graph: every one of the 75 residual members now carries an individual or group
disposition, &lt;code dir=&quot;auto&quot;&gt;toolguide:rtk-search-tooling&lt;/code&gt; is retired (already removed from disk), and only the genuinely
action-reachable members of the prior “6 promoted” claim are recorded as promoted.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Documentation pages can now declare who they are for: a canonical &lt;code dir=&quot;auto&quot;&gt;audience:&lt;/code&gt;
frontmatter field, plus a Common Docs styleguide and gates, ship in the built-in
doctrine pack (mission &lt;code dir=&quot;auto&quot;&gt;common-docs-convergence&lt;/code&gt;).&lt;/strong&gt; Each page states its
intended reader and Divio type, and projects that activate the pack inherit the
same Common Docs conventions — the single-root structure and audience/type
discipline — out of the box.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; is now non-destructive — it preserves backed governance
content by default (mission &lt;code dir=&quot;auto&quot;&gt;charter-synthesize-reconciliation&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3270&lt;/code&gt; P0,
folds &lt;code dir=&quot;auto&quot;&gt;#2777&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#3052&lt;/code&gt;).&lt;/strong&gt; Previously an authoring-only charter edit forced
operators to run &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;, which silently deleted doctrine graph
nodes and edges whose backing artifacts still existed on disk — and &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;
/ &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; hard-blocked until you ran it. Now synthesize &lt;strong&gt;reconciles&lt;/strong&gt; against
the on-disk graph: backed content is retained and the command reports what it
kept (exit 0); &lt;code dir=&quot;auto&quot;&gt;--prune&lt;/code&gt; is the explicit opt-in that removes divergent content
and lists every deletion; &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; previews exactly what &lt;code dir=&quot;auto&quot;&gt;--prune&lt;/code&gt; would
remove and writes nothing; and a non-zero refusal is reserved for genuinely
unpreservable states (orphaned removal without &lt;code dir=&quot;auto&quot;&gt;--prune&lt;/code&gt;, or an unparseable
overlay). The &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; boundary auto-refresh now self-heals
non-destructively and clears the stale signal so you are never trapped, and
&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt; go through the same preserve path. Consumer-pack
synthesis also emits charter-relevant edges from declared interview evidence
(&lt;code dir=&quot;auto&quot;&gt;#3052&lt;/code&gt;) — no more orphaned just-generated directives, and no fabricated edges.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept --json&lt;/code&gt; now surfaces stranded-verdict advisories in a
top-level &lt;code dir=&quot;auto&quot;&gt;advisories&lt;/code&gt; array (mission &lt;code dir=&quot;auto&quot;&gt;verdict-seam-boundary-hardening&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3255&lt;/code&gt;).&lt;/strong&gt; When a mission carries a review verdict that no longer has a home
(an SC-008 “stranded verdict”), &lt;code dir=&quot;auto&quot;&gt;accept --json&lt;/code&gt; reports it as a structured,
non-error advisory alongside the normal payload instead of staying silent — so
operators and automation can see and act on it without scraping human-readable
output.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Spec Kitty’s own charter now activates the writing-comms &amp;#x26; diagramming
doctrine set - this repository only; no downstream impact (builds on &lt;code dir=&quot;auto&quot;&gt;#2918&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;#3225&lt;/code&gt;).&lt;/strong&gt;
Spec Kitty now dogfoods “The Magnificent 7” writing-comms doctrine in its own
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/&lt;/code&gt;: audience-oriented writing (&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_047&lt;/code&gt; +
&lt;code dir=&quot;auto&quot;&gt;writing-audience-catalog&lt;/code&gt; + the &lt;code dir=&quot;auto&quot;&gt;plain-language&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;professional-communications&lt;/code&gt; styleguides), the documentation-structure
styleguides (&lt;code dir=&quot;auto&quot;&gt;divio-type-discipline&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs-accessibility&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs-freshness-sla&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;publication-authority&lt;/code&gt;), C4 diagramming (&lt;code dir=&quot;auto&quot;&gt;USE_C4_MODEL_TECHNIQUES&lt;/code&gt;, alongside the
already-active Mermaid/PlantUML toolguides), the communication-governance
directives (&lt;code dir=&quot;auto&quot;&gt;048&lt;/code&gt; version-governance, &lt;code dir=&quot;auto&quot;&gt;049&lt;/code&gt; agent self-introduction, &lt;code dir=&quot;auto&quot;&gt;050&lt;/code&gt;
credential-handling), the &lt;code dir=&quot;auto&quot;&gt;glossary-maintenance-workflow&lt;/code&gt; procedure and
&lt;code dir=&quot;auto&quot;&gt;research-citation-discipline&lt;/code&gt; styleguide, and the seven writing-comms agent
profiles (&lt;code dir=&quot;auto&quot;&gt;comms-cleo&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;diagram-daisy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;analyst-annie&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lexical-larry&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;minutes-maker-mahad&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;scribe-sally&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;synthesizer-sam&lt;/code&gt;). It also activates
&lt;code dir=&quot;auto&quot;&gt;RECONCILE_CHANGE_SCOPE_TENSIONS&lt;/code&gt; to bridge the smallest-viable-diff / Boy Scout /
locality-of-change tension, explained in a new &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; section.
&lt;strong&gt;Scope:&lt;/strong&gt; this changes Spec Kitty’s &lt;em&gt;own&lt;/em&gt; project governance only. The doctrine
artifacts already ship in &lt;code dir=&quot;auto&quot;&gt;packs/built-in&lt;/code&gt;; projects created or upgraded by the
CLI are unaffected and keep their own charter activations.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A new “When to use Spec Kitty modes” guide helps you pick the lightest path
for the work at hand (&lt;code dir=&quot;auto&quot;&gt;#3238&lt;/code&gt;).&lt;/strong&gt;
&lt;a href=&quot;/guides/when-to-use-modes/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/guides/when-to-use-modes.md&lt;/code&gt;&lt;/a&gt; lays out
four entry points - skip Spec Kitty for a trivial edit, dispatch an ad-hoc
specialist for a short task, run a bounded adversarial squad at an SDD
checkpoint, or drive a full mission when acceptance criteria and structured
review matter - with an illustrated overview, so you match effort to the
change instead of paying full-mission overhead on every edit.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack apply --compile&lt;/code&gt; now applies a pack and compiles
its bundle in one step (mission &lt;code dir=&quot;auto&quot;&gt;charter-pack-usage-journey&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3105&lt;/code&gt;).&lt;/strong&gt;
Previously &lt;code dir=&quot;auto&quot;&gt;apply&lt;/code&gt; only merged activations into &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; and left you to
discover that a separate &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; was still needed; the default
&lt;code dir=&quot;auto&quot;&gt;apply&lt;/code&gt; output now names that exact next command, and &lt;code dir=&quot;auto&quot;&gt;--compile&lt;/code&gt; does both at
once (inheriting &lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt;’s git-worktree requirement). &lt;code dir=&quot;auto&quot;&gt;charter context --include section:terminology-canon&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;section:code-review-checklist&lt;/code&gt; also no
longer dead-end when the section is unauthored - they resolve to an honest
placeholder pointing you at the file to edit (&lt;code dir=&quot;auto&quot;&gt;#3095&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3094&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2552&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Empty/unconfigured charter now dispatches to a warned generic agent instead
of silently applying every built-in doctrine artefact (mission
&lt;code dir=&quot;auto&quot;&gt;charter-delivery-finish-context-degod&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3064&lt;/code&gt;).&lt;/strong&gt; Previously, running a
dispatch in a repository with no charter activated silently fell back to
“all built-ins” - the entire shipped doctrine catalogue was applied in both
routing and the governance context injected into the prompt. Now, when
nothing is activated (a composite check across every charter-activatable
dimension), auto-routing resolves to a &lt;strong&gt;generic agent using no charter
doctrine&lt;/strong&gt; - verified across both routing &lt;strong&gt;and&lt;/strong&gt; the governance block, so no
directive canon leaks into the prompt - and the user gets a &lt;strong&gt;clear warning&lt;/strong&gt;
to activate a charter first. The &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; mission type stays
always-available, and explicitly passing &lt;code dir=&quot;auto&quot;&gt;--profile &amp;#x3C;name&gt;&lt;/code&gt; still resolves the
specialist even under an empty charter (only the no-hint auto-route path
changes; the shared activation gate is untouched).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A minimal starter charter now ships as a first-class, on-demand charter
pack (mission &lt;code dir=&quot;auto&quot;&gt;charter-delivery-finish-context-degod&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3064&lt;/code&gt;).&lt;/strong&gt; It ships
as &lt;code dir=&quot;auto&quot;&gt;src/charter/packs/minimal.yaml&lt;/code&gt;, alongside &lt;code dir=&quot;auto&quot;&gt;default.yaml&lt;/code&gt;. Run
&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack list&lt;/code&gt; to see the shipped built-in packs,
&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack path minimal&lt;/code&gt; to resolve the file, or
&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack apply minimal&lt;/code&gt; to merge its small, curated
activation set into &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; instead of authoring one from
scratch - it is additive by default and never silently overwrites an
existing activation (&lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; to overwrite explicitly).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Profile-channel &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt;-edge delivery is now live - the inert &lt;code dir=&quot;auto&quot;&gt;#3063&lt;/code&gt;
doctrine topology actually delivers (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-activation&lt;/code&gt;,
fast-follow to &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-reachability&lt;/code&gt;).&lt;/strong&gt; The profile-channel
reachability walk now follows &lt;code dir=&quot;auto&quot;&gt;suggests&lt;/code&gt; edges (in addition to &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;specializes_from&lt;/code&gt;) and surfaces each edge’s &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; clause as the delivered
doctrine’s applicability condition - as &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt;-labelled links, not eager
bodies (respecting the context-bloat budget). Architect and implementer
profiles now receive their linked paradigms, tactics, techniques, and
canvases: e.g. &lt;code dir=&quot;auto&quot;&gt;architect-alphonso&lt;/code&gt; reaches &lt;code dir=&quot;auto&quot;&gt;domain-driven-design&lt;/code&gt;, the C4
model techniques, and the REASONS-canvas guidance; implementer profiles reach
the &lt;code dir=&quot;auto&quot;&gt;DISCIPLINED_REFACTORING&lt;/code&gt; refactoring tactics. Companion authoring: a C4
&lt;code dir=&quot;auto&quot;&gt;template:instantiates&lt;/code&gt; edge from &lt;code dir=&quot;auto&quot;&gt;action:documentation/design&lt;/code&gt;, and
refactoring code-smell &lt;code dir=&quot;auto&quot;&gt;anti_pattern&lt;/code&gt; nodes wired via &lt;code dir=&quot;auto&quot;&gt;REJECTS&lt;/code&gt; (grounded in
each tactic’s attested &lt;code dir=&quot;auto&quot;&gt;problem&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt;). The reachability pins, the delivery
wiring table, and the forward-API dead-symbol allowlist are reconciled to the
now-live topology, each moved count carrying a composition-ledger entry. (#3063)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; doctrine kind is now reachable end to end - resolve, deliver,
and author it (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-reachability&lt;/code&gt;).&lt;/strong&gt; Previously a
shipped asset (executable logic or any blob a pack hands to a downstream repo)
had no operator surface and no followable how-to, so the documented remedy
“ship it as an asset” was not actually followable (#3037). Now:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine asset list&lt;/code&gt;&lt;/strong&gt; enumerates every resolvable asset with
its source tier (built-in / org / project), and &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine asset path &amp;#x3C;id&gt;&lt;/code&gt;&lt;/strong&gt; resolves one identifier to a filesystem path - exit &lt;code dir=&quot;auto&quot;&gt;0&lt;/code&gt; on
success, non-zero with the id named on an unknown id or a containment
refusal. Nothing is installed into the consumer repo; assets resolve from
packaged data plus the project/org overlays (no auto-install). The one
built-in asset, &lt;code dir=&quot;auto&quot;&gt;common-docs-structural-lint&lt;/code&gt;, resolves from any
installation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine new --kind asset &amp;#x3C;name&gt;&lt;/code&gt;&lt;/strong&gt; scaffolds an asset with
the same parity as &lt;code dir=&quot;auto&quot;&gt;validate&lt;/code&gt;, writing into the directory the resolver reads
(&lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/assets/&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The action doctrine bundle now delivers every resolved kind&lt;/strong&gt;, including
procedures and assets. The delivery gate is a total function over kinds:
activation-gated kinds deliver &lt;code dir=&quot;auto&quot;&gt;activated ∩ reachable&lt;/code&gt;, while assets are
&lt;strong&gt;delivered-but-not-activation-gated&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;gate = ALL&lt;/code&gt;) - a reachable source
pulls them in without an activation list. This closes the defect where
&lt;code dir=&quot;auto&quot;&gt;asset_ids = []&lt;/code&gt; was the silently-conforming outcome forever.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Docs&lt;/strong&gt;: &lt;a href=&quot;/development/how-to/create-a-doctrine-artifact/&quot;&gt;Create a doctrine artifact&lt;/a&gt;
gains an executable asset how-to (author a manifest, place the blob, resolve
it), and &lt;a href=&quot;/architecture/doctrine-kinds/&quot;&gt;Doctrine artifact kinds&lt;/a&gt; documents
the shipped built-in asset and the three delivery categories.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;New checks that catch a change which looks like it worked and did nothing
(mission &lt;code dir=&quot;auto&quot;&gt;doctrine-silence-guards&lt;/code&gt;).&lt;/strong&gt; Four additions, all aimed at the same
failure mode - a declaration that loads, validates, reports success, and then
has no effect:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;strong&gt;zero-producer lint&lt;/strong&gt; fails the build when a schema field is declared but
no code path ever writes it. Three such fields had shipped in this
repository, one of them inert for months behind passing tests. The findings
that already exist are frozen as a shrink-only baseline; the list can only
get smaller, every entry names an owner and the fix it is waiting on, and a
test refuses to let an entry outlive the work that was meant to remove it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;scripts/generate_schemas.py --check&lt;/code&gt; now runs in CI&lt;/strong&gt;, in the always-on
&lt;code dir=&quot;auto&quot;&gt;lint&lt;/code&gt; job rather than behind a path filter, so a model change that leaves
its generated YAML schema behind fails immediately. Seven schemas were
already stale and are reconciled here.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine&lt;/code&gt; now reports org-pack edges that point at
nothing&lt;/strong&gt; (see Breaking Changes).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Occurrence maps can protect a single field inside a file that is otherwise
migrating.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;do_not_change&lt;/code&gt; classification used to accept only
whole-file path globs, so a file containing both governed keys and keys that
should be renamed could not be described. It now accepts a YAML field path.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CLI UX: shell autocompletion, a &lt;code dir=&quot;auto&quot;&gt;-h&lt;/code&gt; short-help alias, and alphabetical
command listing (#2232, #2234, #2235).&lt;/strong&gt; Three additive quality-of-life
improvements to the &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; command surface, with no behavior change to
existing commands:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Shell autocompletion&lt;/strong&gt; is now enabled (&lt;code dir=&quot;auto&quot;&gt;--install-completion&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;--show-completion&lt;/code&gt;), with a latency-safe fast path: every TAB press serves
command/subcommand candidates from a small committed manifest
(&lt;code dir=&quot;auto&quot;&gt;_completion_manifest.json&lt;/code&gt;) instead of importing the whole command tree,
cutting completion invocation latency from roughly 812 ms to about 76 ms. A
drift-guard test keeps the manifest in sync with the live command tree.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;-h&lt;/code&gt; is accepted as an alias for &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt;&lt;/strong&gt; across the root command and
every subcommand.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The root &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; command list is now sorted alphabetically&lt;/strong&gt;, and a bare
&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; invocation renders the same ordered help.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync import-history&lt;/code&gt; materializes existing local mission history
into the SaaS projection (#2262).&lt;/strong&gt; A first sync registers a remote
project/build but leaves it with zero materialized missions - the SaaS
materializer refuses to fabricate a work package from a status event with no
prior create. The new command synthesizes the missing
&lt;code dir=&quot;auto&quot;&gt;MissionCreated -&gt; WPCreated[] -&gt; WPStatusChanged[]&lt;/code&gt; prefix (INV-3) from local
history so historical work populates the projection. &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; (default)
runs the whole read-only pipeline and previews the stream; &lt;code dir=&quot;auto&quot;&gt;--apply&lt;/code&gt; attaches
a sha256 provenance manifest, runs the offline envelope contract gate, then
server-preflights the entire stream before uploading anything (fail-closed -
a rejection leaves the projection untouched) and uploads in chunks.
Deterministic event ids make re-runs idempotent (the server dedups on
&lt;code dir=&quot;auto&quot;&gt;event_id&lt;/code&gt;). Buildable slices Y1-Y5 ship here; Y6/Y7/Y8 remain gated.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Doctrine packs can now ship supporting files to consumer repos - the first
is a docs structural-lint that keeps a project’s documentation organized
(#2302, #2864-#2867).&lt;/strong&gt; A doctrine pack can now carry an arbitrary
addressable file (a script, a blob, a &lt;code dir=&quot;auto&quot;&gt;.docx&lt;/code&gt;) that travels with the pack and
resolves in a consumer repo with no access to our source tree - the new
built-in &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt; doctrine kind, shipping its first member. That inaugural
asset, &lt;code dir=&quot;auto&quot;&gt;common-docs-structural-lint&lt;/code&gt;, checks that docs land in the right
section, that redirect stubs and frontmatter follow the house contract, and
that retired shadow doc-trees don’t reappear; it is wired into the
&lt;code dir=&quot;auto&quot;&gt;docs-freshness&lt;/code&gt; CI workflow as a blocking gate and is pulled in automatically
whenever a common-docs artifact is activated. Alongside it, a one-time
structural-sanity sweep redistributed nine misfiled &lt;code dir=&quot;auto&quot;&gt;architecture/&lt;/code&gt; notes,
retired the &lt;code dir=&quot;auto&quot;&gt;plans/notes/&lt;/code&gt; 1.x shadow tree, and repointed every referrer with
zero dead links; the common-docs styleguide gains a machine-parseable
&lt;code dir=&quot;auto&quot;&gt;structural_lint_config&lt;/code&gt; block (with a &lt;code dir=&quot;auto&quot;&gt;redirect_stub_description_prefix&lt;/code&gt;
exemption key) as the lint’s single source of truth; and the docs
reference-rewrite helper no longer doubles a destination path (&lt;code dir=&quot;auto&quot;&gt;.../x.md/x.md&lt;/code&gt;)
on a file-level move. No CLI product code (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli&lt;/code&gt;) changed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Fork packaging hooks (entry-point plugins + &lt;code dir=&quot;auto&quot;&gt;DistributionProfile&lt;/code&gt;).&lt;/strong&gt;
Renamed / private-index forks can customize CLI package identity, upgrade
providers (including built-in PEP 503 &lt;code dir=&quot;auto&quot;&gt;SimpleIndexProvider&lt;/code&gt;), remediation
index URLs, data-freshness TTL, and the public-PyPI notifier via
&lt;code dir=&quot;auto&quot;&gt;spec_kitty.cli_package&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec_kitty.upgrade_provider&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;spec_kitty.distribution_profile&lt;/code&gt; - without overlaying &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/**&lt;/code&gt;.
Stock public-PyPI / &lt;code dir=&quot;auto&quot;&gt;spec-kitty-cli&lt;/code&gt; installs with no hooks are unchanged.
Packager guide: &lt;a href=&quot;/guides/how-to/installation/fork-packaging-hooks/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/guides/fork-packaging-hooks.md&lt;/code&gt;&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Doctrine-controlled transition gates - the &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; pre-review gate is now
declared by the repo’s active doctrine, not hardcoded to Spec Kitty’s own repo
shape (#2595, #2596, #2598; epic #2535 half A).&lt;/strong&gt; Scope resolution moves behind a
layout-agnostic &lt;code dir=&quot;auto&quot;&gt;ScopeSource&lt;/code&gt; port (&lt;code dir=&quot;auto&quot;&gt;GateCoverageScopeSource&lt;/code&gt; preserves the
incumbent pytest/JUnit path byte-identically; &lt;code dir=&quot;auto&quot;&gt;DeclaredCommandScopeSource&lt;/code&gt; runs a
consumer’s declared &lt;code dir=&quot;auto&quot;&gt;review.test_command&lt;/code&gt; with baseline-relative verdicts). A
named &lt;code dir=&quot;auto&quot;&gt;GATE_REGISTRY&lt;/code&gt; registers the pre-review engine as the first handler; a
versioned &lt;code dir=&quot;auto&quot;&gt;gates&lt;/code&gt; binding on the &lt;code dir=&quot;auto&quot;&gt;mission_step_contract&lt;/code&gt; review contract (with an
inert &lt;code dir=&quot;auto&quot;&gt;handler_kind&lt;/code&gt; seam for future executable-asset gates) is resolved through
charter activation and dispatched by the inverted &lt;code dir=&quot;auto&quot;&gt;_mt_run_transition_gates&lt;/code&gt;
hook with deterministic aggregation and per-handler fail-open (two hard-stops
preserved). A new built-in &lt;code dir=&quot;auto&quot;&gt;mission_step_contract.graph.yaml&lt;/code&gt; DRG fragment makes
the gate fire on the source repo. Behaviour parity is enforced by a golden
captured from the pre-refactor base. &lt;strong&gt;Closes the pre-review facet of #2534&lt;/strong&gt; (the
always-on &lt;code dir=&quot;auto&quot;&gt;tests.architectural._gate_coverage&lt;/code&gt; consumer-repo import is removed -
a consumer never reaches it, even under erroneous activation) &lt;strong&gt;and #2330&lt;/strong&gt; (the
pytest-layout papercut). Half B (executable gate assets, #2599) is out of scope.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The pre-review test gate now works correctly for projects that use a custom
test command, not just pytest (#2873, follow-up to #2535 half A).&lt;/strong&gt; When a work
package moves to &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;, Spec Kitty runs the project’s tests and flags any
failure the change &lt;em&gt;newly&lt;/em&gt; introduced - comparing against a baseline captured
before the work started. Previously the baseline side and the review side could
run those tests two different ways, so a project configured with its own
&lt;code dir=&quot;auto&quot;&gt;review.test_command&lt;/code&gt; (anything other than pytest) got unreliable results: it
could be wrongly blocked on failures that were already there, or - worse - a
genuinely new test failure could slip through unflagged on a clean baseline. Now
both sides run and interpret the tests through one shared path, so the
comparison is apples-to-apples and a new failure is reliably caught. When the
two sides genuinely &lt;em&gt;can’t&lt;/em&gt; be compared (for example, the test command was
changed in between), the gate now says so with a clear, non-blocking warning
(shown as &lt;code dir=&quot;auto&quot;&gt;SOURCE_MISMATCH&lt;/code&gt;) instead of guessing - it never silently passes and
never hard-blocks on that case. The captured baseline is now always saved, so
review no longer gets stuck on an uncommitted baseline file. Internally, ~450
lines of dead, duplicated test-scoping code left over from an earlier design
were removed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;WP runtime-state evicted into the append-only event log (#2684, #2093).&lt;/strong&gt;
Runtime-mutable work-package state - &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt;, subtask completion,
&lt;code dir=&quot;auto&quot;&gt;## Activity Log&lt;/code&gt; notes, &lt;code dir=&quot;auto&quot;&gt;tracker_refs&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;assignee&lt;/code&gt;, and review-cycle
fields - is folded through a single off-axis &lt;code dir=&quot;auto&quot;&gt;InnerStateChanged&lt;/code&gt; event and read
from the reduced status snapshot, so &lt;code dir=&quot;auto&quot;&gt;tasks/WP##.md&lt;/code&gt; stops mutating on runtime
events (byte-stable dossier content hash, AC-5). &lt;strong&gt;Shipped as dual-write behind
the phase-1 flag&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;_phase1_dual_write_enabled&lt;/code&gt;, default off): the event log is
the authority at &lt;code dir=&quot;auto&quot;&gt;status_phase: 1&lt;/code&gt;, while legacy frontmatter remains the default,
sanctioned migration-window fallback. The corpus &lt;code dir=&quot;auto&quot;&gt;backfill -&gt; verify -&gt; cutover&lt;/code&gt;,
the unconditional flag flip, and the legacy-fallback deletion are deferred to
follow-up #2816.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Charter bundle consolidated into an authoritative &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; (#2773).&lt;/strong&gt;
The four compiled bundle files (&lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directives.yaml&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt;) plus &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;activated_*&lt;/code&gt; keys
fold into a single git-tracked, authorable &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; that becomes the
project’s authoritative structured charter; &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; becomes a curated
companion. The bundle manifest bumps to schema &lt;code dir=&quot;auto&quot;&gt;2.0.0&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; is the
sole content-hash input), and &lt;code dir=&quot;auto&quot;&gt;config.yaml&lt;/code&gt; gains a one-line &lt;code dir=&quot;auto&quot;&gt;charter:&lt;/code&gt;
pointer. A deterministic, idempotent, fail-loud &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; migration performs
the fold, sequenced strictly after the &lt;code dir=&quot;auto&quot;&gt;3.2.6&lt;/code&gt; activation-seed migrations
(verbatim activation copy; the seeds’ post-state - &lt;code dir=&quot;auto&quot;&gt;config&lt;/code&gt; carries
&lt;code dir=&quot;auto&quot;&gt;activated_*&lt;/code&gt; - is the fold’s pre-state).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;deactivate --resynthesize&lt;/code&gt; opt-in eager refresh (FR-007, #2761).&lt;/strong&gt;
Since the config↔derived freshness seam (#2759) made &lt;code dir=&quot;auto&quot;&gt;charter activate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;deactivate&lt;/code&gt;
visible to the &lt;code dir=&quot;auto&quot;&gt;synthesized_drg&lt;/code&gt; freshness signal, a routine activation now reports
&lt;code dir=&quot;auto&quot;&gt;stale&lt;/code&gt; until the operator reconciles it. The new &lt;code dir=&quot;auto&quot;&gt;--resynthesize&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;--no-resynthesize&lt;/code&gt;
flag (default &lt;strong&gt;off&lt;/strong&gt;) gives operators an escape hatch: passing it re-runs the existing
&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; pipeline right after the config write, so the
derived bundle/DRG - and the freshness signal - are fresh immediately, without building
a second reconciliation pipeline. The default (no-flag) path is unchanged: a fast,
config-only write that spawns &lt;strong&gt;zero&lt;/strong&gt; synthesis calls, locked in by a call-count spy
regression test (NFR-001); the &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; migration and &lt;code dir=&quot;auto&quot;&gt;org_charter&lt;/code&gt;
&lt;code dir=&quot;auto&quot;&gt;promote_activations&lt;/code&gt; paths are untouched and remain synthesis-free (NFR-003).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Development-assist test cleanup is now a standing wrap-up procedure (#2557).&lt;/strong&gt;
A new built-in &lt;code dir=&quot;auto&quot;&gt;development-assist-test-cleanup&lt;/code&gt; procedure codifies a proactive,
judge-the-test pass at mission close (identify -&gt; judge -&gt; execute -&gt; scope-the-residue)
that retires or splits the scaffolding tests a mission wrote to drive its own
slices - characterization/parity oracles, before/after timing gates, per-WP
shape / &lt;code dir=&quot;auto&quot;&gt;__module__&lt;/code&gt; / delegate assertions - before they land as permanent suite
bloat. It applies &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_041&lt;/code&gt;’s keep-vs-delete axis and its
duplicate-test-knowledge-has-one-source rule as the &lt;em&gt;proactive&lt;/em&gt; companion to that
&lt;em&gt;reactive&lt;/em&gt; failing-test rubric, and is scoped distinct from &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_025&lt;/code&gt;
(pre-existing debt in touched areas). It is wired into &lt;code dir=&quot;auto&quot;&gt;mission-wrap-up-sequence&lt;/code&gt;
as a new “retire or split the mission’s development-assist tests” step after
acceptance (DRG: +1 node, +5 edges), and the wrap-up hand-off / notes summary now
records which tests were retired / split / kept-and-renamed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Relocation-hardened architectural dead-code scanners + content-addressed
ratchet allow-lists (#2546, #2547, #2072, #2548, #2077).&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;tests/architectural/&lt;/code&gt;
ratchet allow-lists are re-keyed off &lt;em&gt;position&lt;/em&gt; anchors (line numbers, &lt;code dir=&quot;auto&quot;&gt;module::Name&lt;/code&gt;)
onto &lt;strong&gt;content descriptors&lt;/strong&gt;, and the 394-entry dead-symbol allow-list onto a
&lt;strong&gt;relocation-tolerant &lt;code dir=&quot;auto&quot;&gt;SymbolKey&lt;/code&gt;&lt;/strong&gt; - content-only by default, escalating a
byte-identical same-name collision to a &lt;code dir=&quot;auto&quot;&gt;module_path&lt;/code&gt; tier (or fail-closing) via a
&lt;strong&gt;live, gate-time collision classifier&lt;/strong&gt; - so a behaviour-preserving relocation no
longer forces a hand-edit &lt;strong&gt;without re-blinding the T004 no-false-negative
invariant&lt;/strong&gt;. Adds a standing int-to-line-sink meta-guard, a tier-specific
dangling-entry ratchet, and the full production-path bite battery. The relocation
promise is honestly downscoped: relocation-proof for simple single-definition
entries; re-export/facade/fan-out entries stay &lt;code dir=&quot;auto&quot;&gt;module_path&lt;/code&gt;-keyed (documented, not
a bug). Ships with a CaaCS change-coupling analysis of the test suite (epic #2071).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;First-class TEMPLATE + loose-contract ASSET doctrine kinds (#2495, #2469).&lt;/strong&gt;
Org-pack &lt;strong&gt;templates&lt;/strong&gt; are now first-class, graph-addressable, edge-wireable
DRG nodes, and a new loose-contract &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;&lt;/strong&gt; doctrine kind lets a pack ship
and reference arbitrary addressable files (image, &lt;code dir=&quot;auto&quot;&gt;.docx&lt;/code&gt;, blob) via a sidecar
&lt;code dir=&quot;auto&quot;&gt;*.asset.yaml&lt;/code&gt; manifest (&lt;code dir=&quot;auto&quot;&gt;id&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mime&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;path&lt;/code&gt;, no blob schema). A single canonical
&lt;code dir=&quot;auto&quot;&gt;_NON_AUGMENTATION_ELIGIBLE_KINDS&lt;/code&gt; set makes both kinds node-declarable but not
augmentation-eligible or charter-activatable - closing the silent-leak defect
class by construction. Safety is enforced from day one: &lt;strong&gt;global URN-uniqueness&lt;/strong&gt;
for &lt;code dir=&quot;auto&quot;&gt;asset:&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;template:&lt;/code&gt; (a single post-merge scan -&gt; &lt;code dir=&quot;auto&quot;&gt;duplicate_asset_id&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;duplicate_template_id&lt;/code&gt;), &lt;strong&gt;path-containment&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;asset_path_escape&lt;/code&gt;), and &lt;strong&gt;mime
validation&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;asset_mime_invalid&lt;/code&gt;). A new totality guard asserts every
&lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;NodeKind&lt;/code&gt;-keyed mapping table stays exhaustive. The 9 existing
kinds are unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;External orchestrators can submit structured review outcomes without
forcing lane transitions.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;orchestrator-api transition&lt;/code&gt; now accepts
&lt;code dir=&quot;auto&quot;&gt;--review-result-json&lt;/code&gt; with reviewer, verdict, and reference fields, allowing
guarded &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; exits to remain fully host-enforced. The additive contract
change bumps the orchestrator API to 1.3.0.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dashboard WP cards show subtask progress (#2504).&lt;/strong&gt; Cards (and the WP
detail view) previously showed a bare frontmatter count (&lt;code dir=&quot;auto&quot;&gt;4 subtasks&lt;/code&gt;);
they now show &lt;code dir=&quot;auto&quot;&gt;2/4 subtasks&lt;/code&gt; (with a ✓ at n/n), counted from the canonical
checkbox rows in the WP body - the same rows the lane-transition guard
blocks on, via a new shared single definition
(&lt;code dir=&quot;auto&quot;&gt;core/subtask_rows.py&lt;/code&gt;, now consumed by both the guard and the dashboard
so the two can’t drift). WPs that don’t track completion via checkboxes
keep the plain count badge (no false &lt;code dir=&quot;auto&quot;&gt;0/N&lt;/code&gt;). The kanban task payload gains
additive &lt;code dir=&quot;auto&quot;&gt;subtasks_done&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;subtasks_total&lt;/code&gt; fields; the typed-contract
baseline is regenerated accordingly.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Seven activated governance artefacts are now reachable from the doctrine
graph, so &lt;code dir=&quot;auto&quot;&gt;charter activate --cascade&lt;/code&gt; pulls them in.&lt;/strong&gt; Each of these was
shipped active in the default charter pack but had no inbound edge from
anything, which meant no cascade, no traversal, and no way for an agent to
arrive at it except by naming it directly. The authored edges are:
&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_035&lt;/code&gt; -&gt; occurrence-classification-workflow, &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_003&lt;/code&gt; -&gt;
decision-marker-capture, &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_030&lt;/code&gt; -&gt; no-parallel-duplicate-test-runs,
&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_030&lt;/code&gt; -&gt; red-main-release-discipline, &lt;code dir=&quot;auto&quot;&gt;python-conventions&lt;/code&gt; -&gt;
python-review-checks, &lt;code dir=&quot;auto&quot;&gt;atomic-design-review-checklist&lt;/code&gt; -&gt; atomic-design, and
&lt;code dir=&quot;auto&quot;&gt;structured-prompt-driven-development&lt;/code&gt; -&gt; reasons-canvas-writing. &lt;strong&gt;This
changes what a cascade brings in for your project:&lt;/strong&gt; activating one of the
seven source artefacts with &lt;code dir=&quot;auto&quot;&gt;--cascade&lt;/code&gt; now also activates the target that
was previously stranded. If you have been relying on a cascade to produce a
specific, narrow set, re-check it after upgrading - the sets are now larger
by design, because the targets were always meant to travel with their
sources.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-2&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A corrupt, truncated, or wrong-authority &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is now rejected loudly by
every mission read path instead of being silently accepted (mission
&lt;code dir=&quot;auto&quot;&gt;meta-json-fail-closed-routing&lt;/code&gt;; closes epic &lt;code dir=&quot;auto&quot;&gt;#3259&lt;/code&gt; — &lt;code dir=&quot;auto&quot;&gt;#3228&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#3229&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;#3230&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#3240&lt;/code&gt;).&lt;/strong&gt; A mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is its canonical identity and
VCS-lock record. Several internal read paths — git ref-advance, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, and
the acceptance-matrix merge-driver — still decoded it through hand-rolled parsers
that would quietly accept a malformed or wrong-authority file, exactly the
split-brain / wrong-authority failure the metadata-authority work exists to close.
Before, a bad &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; could let a mission proceed on corrupt identity state
and surface later as a confusing, hard-to-trace failure; now every remaining read
routes through one fail-closed decode seam and fails immediately with a clear,
path-named error. The duplicated VCS-lock comparison — two copies that could
return contradictory verdicts on the same file — is also unified into a single
authority.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Two blocking CI gates now reflect what a PR actually changed (mission
&lt;code dir=&quot;auto&quot;&gt;ci-scoping-gate-reliability&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3008&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3147&lt;/code&gt;).&lt;/strong&gt; &lt;em&gt;Corpus data no longer ships
unguarded (&lt;code dir=&quot;auto&quot;&gt;#3008&lt;/code&gt;):&lt;/em&gt; a PR that changed only non-source corpus data — shipped
doctrine under &lt;code dir=&quot;auto&quot;&gt;packs/**&lt;/code&gt;, a mission’s planning artifacts under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**&lt;/code&gt;,
or charter config under &lt;code dir=&quot;auto&quot;&gt;.kittify/**&lt;/code&gt; — never triggered the quality workflow at
all, so every corpus-reading suite was silently skipped pre- and post-merge and a
regression in shipped data shipped invisibly. Narrow, discrete trigger globs now
start the workflow on such changes, and a new blocking &lt;code dir=&quot;auto&quot;&gt;fast-tests-corpus&lt;/code&gt; job
runs the corpus-reading suites (selected by a &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.corpus&lt;/code&gt; marker, so
already-covered suites are not re-run) and gates the merge. The trigger
deliberately excludes lifecycle churn (&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, notes, trace) so it
does not fire on every mission PR. &lt;em&gt;Docs dead-link gate no longer over-fires
(&lt;code dir=&quot;auto&quot;&gt;#3147&lt;/code&gt;):&lt;/em&gt; the blocking dead-link / related-edge check scanned the whole tree and
failed a docs PR for pre-existing broken links in files it never touched. The
blocking check is now scoped to the PR’s own changed files (fail-closed on an
unresolvable base ref — a shallow clone or unfetched base errors rather than
passing trivially), while the unfiltered whole-tree scan is retained as the
non-blocking &lt;code dir=&quot;auto&quot;&gt;push: main&lt;/code&gt; backstop so genuine repo-wide rot is still surfaced.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; modules are cleared of their Sonar maintainability
backlog, including a super-linear-backtracking regex (mission
&lt;code dir=&quot;auto&quot;&gt;charter-sync-sonar-remediation&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3232&lt;/code&gt;-adjacent).&lt;/strong&gt; 80 SonarCloud findings
across the two modules — 27 over-complex functions, 15 duplicate literals, 20
malformed suppression comments, unused parameters, too-many-parameter
signatures, and one ReDoS-class regex flagged &lt;code dir=&quot;auto&quot;&gt;BLOCKER&lt;/code&gt; — were resolved with
&lt;strong&gt;behavior-preserving&lt;/strong&gt; refactors and &lt;strong&gt;no new suppressions&lt;/strong&gt;. Over-complex
functions were brought to the ≤15 cognitive-complexity ceiling via tested
helper extraction (each helper carries a focused test); duplicate literals
became named constants; the &lt;code dir=&quot;auto&quot;&gt;token_budget&lt;/code&gt; heading regex was rewritten to
remove its &lt;code dir=&quot;auto&quot;&gt;.&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;\s&lt;/code&gt; ambiguity (proven match-equivalent by a characterization
test); and the two too-many-parameter event emitters (&lt;code dir=&quot;auto&quot;&gt;emit_wp_status_changed&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;emit_token_usage_recorded&lt;/code&gt;) were slimmed by bundling their optional tail
fields into typed params objects (&lt;code dir=&quot;auto&quot;&gt;WPStatusChangeMetadata&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;TokenUsageMetadata&lt;/code&gt;), with every call site migrated to the params object so
the tail stays fully type-checked rather than routed through an untyped
&lt;code dir=&quot;auto&quot;&gt;**kwargs&lt;/code&gt; bag. Two findings are Sonar false-positives (a Pydantic
&lt;code dir=&quot;auto&quot;&gt;PrivateAttr&lt;/code&gt; and an already-single-return method) with no clean code fix;
they remain for a SonarCloud UI won’t-fix. No runtime behavior changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Signature change for out-of-tree callers of two exported event emitters
(mission &lt;code dir=&quot;auto&quot;&gt;charter-sync-sonar-remediation&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3317&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;emit_wp_status_changed&lt;/code&gt;
and &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) no longer
accept their optional tail fields (&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 keyword arguments. 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 instead. All in-tree callers are already migrated; only
external plugins that called these helpers with the old keyword tail are
affected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Restored an honest red CI gate: &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;’s two standing reds now go green for
the right reason, and &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;’s pre-review gate stops crying wolf
(test-layer only; epic &lt;code dir=&quot;auto&quot;&gt;#3260&lt;/code&gt; — “a red gate must mean a real regression”).&lt;/strong&gt;
This is a CI/gate-correctness pass with &lt;strong&gt;no runtime or behavior change&lt;/strong&gt; — no
&lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; change, no &lt;code dir=&quot;auto&quot;&gt;__init__.py&lt;/code&gt; touch, no version bump — so nothing you install
or run changes. What changes is that the project’s own signal is trustworthy
again:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;The blocking &lt;code dir=&quot;auto&quot;&gt;regression tests&lt;/code&gt; job goes green&lt;/strong&gt; because the last resident
red-first reproduction (&lt;code dir=&quot;auto&quot;&gt;#2782&lt;/code&gt;) was retired. That repro asserted &lt;code dir=&quot;auto&quot;&gt;agent mission create --json&lt;/code&gt; synchronously emits a &lt;code dir=&quot;auto&quot;&gt;direct ingress skipped&lt;/code&gt;
diagnostic on stderr — a contract the deferred/offline sync architecture
cannot satisfy (mission-create queues its lifecycle event and dossier bodies
to the offline outbox and returns without an in-process ingress attempt, so
the diagnostic never fires there, even with consent recorded). It was
redesigned into a green functional test of the architecturally-honest
mission-create contract (&lt;code dir=&quot;auto&quot;&gt;rc=0&lt;/code&gt; + strict-JSON stdout + no diagnostic prose on
stdout + the &lt;code dir=&quot;auto&quot;&gt;#2254&lt;/code&gt; drift guard), moved back beside its strict-JSON siblings,
and un-marked &lt;code dir=&quot;auto&quot;&gt;regression&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;-m regression&lt;/code&gt; now collects nothing, so the
blocking job passes. (The diagnostic’s real firing is still proven at the
resolver seam by a separate test.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;integration-tests-cli&lt;/code&gt; job goes green&lt;/strong&gt; because a drifted test was
locking a since-corrected contract at the &lt;code dir=&quot;auto&quot;&gt;commit_to_branch&lt;/code&gt; seam. Following
&lt;code dir=&quot;auto&quot;&gt;#3269&lt;/code&gt; / commit &lt;code dir=&quot;auto&quot;&gt;793872a19&lt;/code&gt;, only a genuine empty changeset maps to
&lt;code dir=&quot;auto&quot;&gt;unchanged&lt;/code&gt;; a rejecting pre-commit hook is a real failure. The test was
rewritten to assert the corrected contract (hook rejection re-raises and
leaves the artifact dirty).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;’s pre-review gate stops reporting phantom “new failures”&lt;/strong&gt; —
two false reds that made the reliability gate untrustworthy (both children of
epic &lt;code dir=&quot;auto&quot;&gt;#3260&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;tests/doctrine/test_hatch_build.py&lt;/code&gt; now guards its transitive
import with &lt;code dir=&quot;auto&quot;&gt;pytest.importorskip(&quot;hatchling&quot;)&lt;/code&gt;, so the pre-review gate’s
ephemeral baseline venv (which lacks &lt;code dir=&quot;auto&quot;&gt;hatchling&lt;/code&gt; outside the &lt;code dir=&quot;auto&quot;&gt;test&lt;/code&gt; extra)
skips it cleanly instead of hard-failing collection; the normal test job
installs the extra and still runs every test (&lt;code dir=&quot;auto&quot;&gt;#3224&lt;/code&gt;). And
&lt;code dir=&quot;auto&quot;&gt;test_inline_meta_read_gate&lt;/code&gt; now relativizes scanned paths against the scanned
tree’s own root rather than the gate file’s location, so a cross-tree
(git-worktree baseline) scan no longer produces absolute paths that silently
over-count &lt;code dir=&quot;auto&quot;&gt;mission_metadata.py&lt;/code&gt; as a violation (&lt;code dir=&quot;auto&quot;&gt;#3241&lt;/code&gt;, PART 2).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The #2804 gate-artifact merge invariant is guarded again at the driver level,
and the doctrine module’s Sonar maintainability debt is cleared (mission
&lt;code dir=&quot;auto&quot;&gt;gate-artifact-merge-driver-unit-gate&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3232&lt;/code&gt;).&lt;/strong&gt; A prior refactor (&lt;code dir=&quot;auto&quot;&gt;b04da00e1&lt;/code&gt;)
deleted the unit test that pinned “a merge must never reset a filled acceptance/
issue gate artifact back to a scaffold placeholder”, and it was never restored
because it had been written for a whole-file heuristic the row-union authority
model (&lt;code dir=&quot;auto&quot;&gt;#3076&lt;/code&gt;) replaced. This restores that guard as a fast, in-memory unit gate
over the shipped row-union reconcilers: a filled/accepted criterion is never reset
to the scaffold marker, the accepted evidence handle survives a merge (including
inside a structured conflict marker), and the merged verdict stays in its
admissible domain — each with a falsifying control. Bundled opportunistically:
the &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt; Sonar backlog is cleared — 37 duplicate-literal findings hoisted
to named constants, 7 over-complex functions reduced to the ≤15 cognitive-complexity
ceiling via tested helper extraction, and 3 minor smells resolved — all
behavior-preserving with no new suppressions. (One 183-complexity function is
deferred to a dedicated mission.)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty auth login&lt;/code&gt; (and any caller of the SaaS URL helper) now points
you at the real hosted service when &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt; is unset, not a fake
placeholder (&lt;code dir=&quot;auto&quot;&gt;#3297&lt;/code&gt;, closes &lt;code dir=&quot;auto&quot;&gt;#3296&lt;/code&gt;).&lt;/strong&gt; Previously, running the command
without that variable set told you to &lt;code dir=&quot;auto&quot;&gt;Set it to your spec-kitty-saas instance URL (e.g. https://api.spec-kitty.example.com)&lt;/code&gt; — a &lt;code dir=&quot;auto&quot;&gt;.example.com&lt;/code&gt; placeholder
that does not resolve, so a first-time user who copied it got a dead URL. The
guidance named the then-current hosted URL (now &lt;code dir=&quot;auto&quot;&gt;https://team.spec-kitty.ai&lt;/code&gt;), so the
example is copy-paste-usable; self-hosted instances still override via the env
var exactly as before.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Timestamps that Spec Kitty writes into your project no longer record local
time while labelling it UTC (mission &lt;code dir=&quot;auto&quot;&gt;kernel-clock-single-door&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3305&lt;/code&gt;,
closes &lt;code dir=&quot;auto&quot;&gt;#3289&lt;/code&gt;, owns the closed &lt;code dir=&quot;auto&quot;&gt;#3288&lt;/code&gt;).&lt;/strong&gt; Roughly twenty places across the
tool — charter backup filenames, status-event stamps, auth-doctor report times,
and other persisted “now” values — read the machine’s &lt;em&gt;local&lt;/em&gt; clock and then
tagged the result as UTC. On any machine not set to UTC the stored time was
simply wrong: a backup taken at 09:00 CET was filed as &lt;code dir=&quot;auto&quot;&gt;…T09-00-00&lt;/code&gt; and read
back as 09:00 UTC, an hour or two off. Every such value now comes from one
canonical aware-UTC producer, so stamps are correct and consistent regardless
of the host timezone. Under the hood all wall-clock reads now go through a
single &lt;code dir=&quot;auto&quot;&gt;kernel.clock&lt;/code&gt; “door” that every package can import, and a repo-wide CI
gate blocks any new raw &lt;code dir=&quot;auto&quot;&gt;datetime.now()&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;time.time()&lt;/code&gt; read from
reintroducing the drift — but the change you can observe is simply: the
timestamps are right now.&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 auth --fix&lt;/code&gt; now reports a real disk failure instead of
quietly claiming “nothing removed” (mission &lt;code dir=&quot;auto&quot;&gt;sonar-bug-blocker-remediation&lt;/code&gt;).&lt;/strong&gt;
When breaking a stale auth lock hit a genuine I/O error — a full or failing
disk — &lt;code dir=&quot;auto&quot;&gt;force_release&lt;/code&gt; mislabeled it as ordinary lock contention, so the
command told you nothing was wrong while the real fault went unseen. It now
lets genuine filesystem errors propagate while true lock contention still
returns cleanly, matching the rest of the locking layer.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Activating a slug-named hub directive (e.g. &lt;code dir=&quot;auto&quot;&gt;use-c4-model-techniques&lt;/code&gt;) in a
charter now resolves to the real doctrine node instead of a dangling
identifier (&lt;code dir=&quot;auto&quot;&gt;#3009&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3298&lt;/code&gt;).&lt;/strong&gt; The directive-id normalizer folded numbered
slugs (&lt;code dir=&quot;auto&quot;&gt;024-...&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_024&lt;/code&gt;) but left slug-named directives hyphenated
and uppercased (&lt;code dir=&quot;auto&quot;&gt;use-c4-model-techniques&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;USE-C4-MODEL-TECHNIQUES&lt;/code&gt;), which
is not the artifact’s canonical node id (&lt;code dir=&quot;auto&quot;&gt;USE_C4_MODEL_TECHNIQUES&lt;/code&gt;). So
activating or referencing such a directive by its slug silently pointed at
nothing. The normalizer now folds hyphens to underscores, matching the
canonical node id — so slug-hub directives activate and cascade like any other.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker sync publish&lt;/code&gt; on a local (&lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;) binding now
prints a clear error instead of crashing with a Python traceback (&lt;code dir=&quot;auto&quot;&gt;#3168&lt;/code&gt;).&lt;/strong&gt;
Local providers have no snapshot-publish transport, but the command delegated
to the backend unconditionally and hit an uncaught &lt;code dir=&quot;auto&quot;&gt;AttributeError&lt;/code&gt;, which the
CLI let escape as a raw traceback. It now exits with a clean
“not supported for local providers — use &lt;code dir=&quot;auto&quot;&gt;tracker sync push&lt;/code&gt; instead” message.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; is now idempotent — a second run no longer degrades the
compiled catalog (&lt;code dir=&quot;auto&quot;&gt;#3292&lt;/code&gt;).&lt;/strong&gt; Two independent &lt;code dir=&quot;auto&quot;&gt;active_languages&lt;/code&gt; computations
fed a feedback loop: &lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt; stamped &lt;code dir=&quot;auto&quot;&gt;catalog.languages: []&lt;/code&gt; for a
language-agnostic charter, and the language-scope gate then read that empty list
back as an authoritative “admit no languages”, degrading language-scoped
styleguide/toolguide titles and summaries to a &lt;code dir=&quot;auto&quot;&gt;&quot;Definition unavailable in bundled doctrine&quot;&lt;/code&gt; placeholder on the next run. &lt;code dir=&quot;auto&quot;&gt;active_languages&lt;/code&gt; now has a
single authority and an empty result means “no signal → admit all” (round-tripped
as an absent field, not a persisted &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt;), so repeated generates are byte-stable.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The reason &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync doctor&lt;/code&gt; gives for a refused tracker egress can
no longer disagree with what the gate actually enforced (&lt;code dir=&quot;auto&quot;&gt;#3287&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3291&lt;/code&gt;).&lt;/strong&gt;
The gate decided whether to refuse from one source but re-derived the &lt;em&gt;why&lt;/em&gt; —
and the remedy shown to you — from a second, independent consent lookup that
could drift from the enforced answer, and it repeated a full git-identity
resolution on every gated sync. The reason now comes from the same evaluation
that enforces the decision: a refusal’s explanation always matches the
refusal, a consent record that cannot be read is reported as its own state
instead of masquerading as “no consent recorded”, and a gated
&lt;code dir=&quot;auto&quot;&gt;tracker sync&lt;/code&gt; resolves your project’s consent once instead of twice.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A spec commit that genuinely FAILS is no longer silently reported as
“unchanged” (&lt;code dir=&quot;auto&quot;&gt;#3269&lt;/code&gt;).&lt;/strong&gt; When a &lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt; failed for a real reason — a
rejecting pre-commit hook, a lock error — &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; collapsed every
non-zero exit onto the same “nothing to commit” path, so &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt; printed
&lt;em&gt;“Spec artifact(s) unchanged, no commit needed”&lt;/em&gt; and the spec silently never
landed. Emptiness is now decided by the &lt;strong&gt;staged tree&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;git diff --cached&lt;/code&gt;),
not by matching git’s output text: a genuine no-op is still reported as
unchanged, while a real failure surfaces as an error carrying git’s own
diagnostic — even when a failing hook prints its own “nothing to
commit”-shaped message.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; no longer crashes when an arbiter override lands on a
conflict-marked review-cycle file (mission &lt;code dir=&quot;auto&quot;&gt;verdict-seam-boundary-hardening&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3244&lt;/code&gt;).&lt;/strong&gt; An arbiter override written against a &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt; that
still carried unresolved merge-conflict markers used to raise instead of
resolving the latest cycle; the cycle number is now read from the filename
alone, so the override applies cleanly.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;SaaS tracker retry/poll tests no longer flake on CI, and a new gate keeps
the whole bug class out (mission &lt;code dir=&quot;auto&quot;&gt;sync-sleep-count-3136&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3136&lt;/code&gt;).&lt;/strong&gt; These
tests asserted on &lt;code dir=&quot;auto&quot;&gt;time.sleep&lt;/code&gt; call counts and failed non-deterministically
with errors like &lt;code dir=&quot;auto&quot;&gt;Expected &apos;sleep&apos; to be called once. Called 179 times.&lt;/code&gt; on
test nodes a change never touched — because patching the shared stdlib
&lt;code dir=&quot;auto&quot;&gt;time.sleep&lt;/code&gt; recorded sleeps from anything else running in the same test
worker. Building on &lt;code dir=&quot;auto&quot;&gt;#3187&lt;/code&gt; (which gave &lt;code dir=&quot;auto&quot;&gt;SaaSTrackerClient&lt;/code&gt; its own
&lt;code dir=&quot;auto&quot;&gt;self._sleep&lt;/code&gt; seam), the client now also binds &lt;code dir=&quot;auto&quot;&gt;self._monotonic&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;self._randbelow&lt;/code&gt;, so its retry/poll timing and jitter are fully isolated from
process-global state. A new architectural gate
(&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_shared_module_object_patches.py&lt;/code&gt;) refuses any future
test that patches a shared module object read by a count/equality assertion, so
this class of flake fails review instead of shipping.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Restored green CI on two suites that regressed after the single-&lt;code dir=&quot;auto&quot;&gt;PACKS_ROOT&lt;/code&gt;
/ charter-activation unification (mission &lt;code dir=&quot;auto&quot;&gt;resolution-activation-foundation&lt;/code&gt;).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;tests/review/test_pre_review_gate_integration.py&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;tests/merge/test_profile_charter_e2e.py&lt;/code&gt; still built bare fixtures that never
provisioned the default charter / mission-type activations, so once resolution
moved to a single fail-closed &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; read the pre-review gate
degraded to &lt;code dir=&quot;auto&quot;&gt;no_coverage&lt;/code&gt; (never blocking) and mission-template resolution
raised &lt;code dir=&quot;auto&quot;&gt;MissionsRootNotFound&lt;/code&gt;. The fixtures now seed the default activations
via the production provisioner and mirror the built-in &lt;code dir=&quot;auto&quot;&gt;missions&lt;/code&gt; leaf under
the packs root. Test-harness only - no product behaviour changed; the
fail-closed resolution the sibling mission introduced is intentional.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Commands run on a merged coordination mission no longer crash (&lt;code dir=&quot;auto&quot;&gt;#3086&lt;/code&gt;).&lt;/strong&gt;
Once a coordination mission was merged, later commands against it - creating a
retrospective, resuming implementation, or checking its status - failed
outright, and this hit every merged coordination mission. Merging now
finalizes the mission cleanly, so it stays usable afterward.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;decision widen&lt;/code&gt; no longer lets one mission’s decision travel under
another mission’s identity (mission &lt;code dir=&quot;auto&quot;&gt;egress-refusal-consolidation-3110&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3111&lt;/code&gt;).&lt;/strong&gt; Previously, ownership was resolved from whatever the decision
ledger it was handed reported rather than from the mission you actually
named, so a decision owned by mission A could be widened under a request
naming mission B and have the egress consent gate treat it as consented -
laundering A’s identifying text out under B’s team/token. Widening now
refuses whenever the acting mission and the decision’s recorded owner
disagree. The governing rule: identity is a detector, never an actuator.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The consent-refusal gate deciding whether project-identifying text may
leave your machine now has one definition site instead of two
near-identical copies that could drift apart (&lt;code dir=&quot;auto&quot;&gt;#3110&lt;/code&gt;).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;saas_client/egress_consent.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tracker/egress_consent.py&lt;/code&gt; are
replaced by &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/egress.py&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Listing missions on Python 3.14 no longer reports a permission error as
“no missions found” (&lt;code dir=&quot;auto&quot;&gt;#3177&lt;/code&gt;).&lt;/strong&gt; An unreadable mission directory was
silently dropped instead of being recorded, so the CLI told you to &lt;code dir=&quot;auto&quot;&gt;git pull&lt;/code&gt; for what was actually an &lt;code dir=&quot;auto&quot;&gt;EACCES&lt;/code&gt;. It now reports the directory as
unreadable; unaffected on the CLI’s supported 3.11-3.13 interpreters.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Internal: a stale docstring in the saas-client/egress invocation adapters
no longer claims re-registration only replaces a factory or resolver “when
the qualified name matches” (&lt;code dir=&quot;auto&quot;&gt;#3109&lt;/code&gt;).&lt;/strong&gt; Both always replaced
unconditionally; only the documentation was wrong, and only the control
flow used to reach the same assignment differed. Behavior is unchanged.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;UnknownMissionTypeError&lt;/code&gt; no longer labels an activated mission type both
“unknown” and “registered” (mission
&lt;code dir=&quot;auto&quot;&gt;doctrine-consumer-surface-missions-extraction&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3183&lt;/code&gt;).&lt;/strong&gt; When a mission
type is activated but has no loadable profile, the error now states that
distinctly, instead of the contradictory “Unknown mission type &apos;&lt;x&gt;&apos;.
Registered types: &lt;x&gt;”.&lt;/x&gt;&lt;/x&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The built-in-doctrine dead-path architectural gates no longer silently lose
coverage when a gate file is split, and the shipped &lt;code dir=&quot;auto&quot;&gt;doctrine-daphne&lt;/code&gt; profile
no longer carries a repo-local &lt;code dir=&quot;auto&quot;&gt;src/doctrine/graph.yaml&lt;/code&gt; reference (mission
&lt;code dir=&quot;auto&quot;&gt;doctrine-consumer-surface-missions-extraction&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3036&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3182&lt;/code&gt;).&lt;/strong&gt; The
&lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;-wide gates and the doctrine-content gate are split by actual scope with
their discriminator proofs driven from planted synthetic fixtures, and the
relocated-tree cross-link scan now covers both shipped roots.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The dashboard’s Charter page no longer misreports a compiled-only project
as having no charter (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-charter-split-unification&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3150&lt;/code&gt;).&lt;/strong&gt; Before this fix, a project with a compiled
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; but no display-only &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; companion
showed “no charter” in the dashboard sidebar and its API - both the artifact
scanner and the charter API endpoint still keyed presence on the legacy
&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; file. Presence resolution now prefers &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; (the read
authority) and falls back to &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; when &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; has not been
compiled yet, across the dashboard, analysis-report, and
retrospective-policy surfaces - so a &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;-only project that never
ran &lt;code dir=&quot;auto&quot;&gt;charter sync&lt;/code&gt;/compile still reports a charter, and a compiled project
still survives &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; deletion; the prose body the Charter page
displays still comes from &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; when one exists. Two exceptions are
intentionally pinned, not
residual gaps: &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt;’s prose-presence gate (documented, C-003)
and &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt;’s legacy &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;-only fallback for
pre-consolidation bundles (&lt;code dir=&quot;auto&quot;&gt;_status_collectors.py&lt;/code&gt;, pinned by
&lt;code dir=&quot;auto&quot;&gt;test_status_collectors_legacy_md_shape.py&lt;/code&gt;, FR-006).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A corrupt or malformed &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; now always fails closed with a clear
error, never a raw crash (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-charter-split-unification&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3140&lt;/code&gt;).&lt;/strong&gt; Previously, dozens of call sites across mission-status,
coordination, migration, and CLI commands could leak an unhandled
&lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt; when a mission’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; was corrupted or shaped
unexpectedly, surfacing as an opaque traceback instead of an actionable
error. Every one of those readers now routes through a single typed
&lt;code dir=&quot;auto&quot;&gt;MissionMetaReadError&lt;/code&gt; (or a documented silent-empty fallback where that was
always the contract), so a broken mission’s metadata degrades predictably
instead of crashing the command you ran.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Internal: &lt;code dir=&quot;auto&quot;&gt;doctrine-charter-tests.yml&lt;/code&gt; CI now actually covers the charter
CLI command layer, and the CLI-reference parity check runs instead of
silently skipping (&lt;code dir=&quot;auto&quot;&gt;#3149&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3107&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3102&lt;/code&gt;).&lt;/strong&gt; A change under
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/charter/**&lt;/code&gt; previously wouldn’t trigger the
workflow named for it; the docs-parity gate had pointed at a reference file
that no longer existed, so it never actually ran.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Approving a work package after a rejection now actually sticks - no
override flag required (mission &lt;code dir=&quot;auto&quot;&gt;review-verdict-write-integrity&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3044&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#2275&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2996&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#990&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2697&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2646&lt;/code&gt;).&lt;/strong&gt; Before this fix,
&lt;code dir=&quot;auto&quot;&gt;move-task --to approved&lt;/code&gt; on a previously-rejected WP advanced the lane but
wrote no record of the approval - the stale &lt;code dir=&quot;auto&quot;&gt;rejected&lt;/code&gt; verdict stayed
authoritative, so &lt;code dir=&quot;auto&quot;&gt;move-task --to done&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; kept blocking
on it, forcing &lt;code dir=&quot;auto&quot;&gt;--skip-review-artifact-check&lt;/code&gt; (an arbiter-override flag) on
every ordinary reject -&gt; fix -&gt; approve cycle. Separately, the rejection
writer accepted any file as “feedback” without checking it wasn’t itself a
prior cycle’s own review artifact (by path or by a renamed copy), so a
mistaken re-submission (a reviewer accidentally re-pasting the same feedback
text) could silently duplicate an old review under fresh, fabricated
frontmatter. Neither writer ever git-committed its output under any
topology, so even a successful write could land untracked. Now: approving a
rejected WP through the normal path persists and commits a real
&lt;code dir=&quot;auto&quot;&gt;verdict: approved&lt;/code&gt; review-cycle artifact with a genuine reviewer identity;
the override flag still works for actual arbiter decisions but is no longer
&lt;em&gt;needed&lt;/em&gt; for an ordinary approval; a rejection’s feedback source is refused
if it’s the same or a duplicate of a prior cycle’s own artifact (a check
that a deliberate one-character edit still defeats - it targets accidental
duplication, not a determined actor); and both &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; write paths now
commit their review-cycle artifact when auto-commit is resolved on
(&lt;code dir=&quot;auto&quot;&gt;--auto-commit&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;auto_commit: true&lt;/code&gt;/default in &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;),
surfacing a clear error if the commit itself fails rather than silently
discarding it. Under &lt;code dir=&quot;auto&quot;&gt;--no-auto-commit&lt;/code&gt;, or with &lt;code dir=&quot;auto&quot;&gt;auto_commit: false&lt;/code&gt;
configured, the write still lands but is not committed. A third writer,
&lt;code dir=&quot;auto&quot;&gt;_persist_review_feedback&lt;/code&gt;, does not yet thread a commit router at all.
&lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt;’s stale-verdict display (&lt;code dir=&quot;auto&quot;&gt;#2646&lt;/code&gt;) is confirmed to close
as a side effect of the durable writer, with no separate code change needed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A work package’s current verdict now has a single authority that wins on
disagreement - the status event log, not a review artifact’s frontmatter
(mission &lt;code dir=&quot;auto&quot;&gt;review-cycle-verdict-seam-rebuild-01KZ2W7W&lt;/code&gt;; ADR
&lt;code dir=&quot;auto&quot;&gt;2026-08-03-1&lt;/code&gt;).&lt;/strong&gt; Before this fix, “is this WP approved?” had no single
answer: some readers (the kanban board, &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;’s review-readiness
check) parsed a &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt; artifact’s &lt;code dir=&quot;auto&quot;&gt;verdict:&lt;/code&gt; frontmatter field
directly, so a reader could disagree with the event log about which verdict
was current if the two ever drifted. Now the event-sourced verdict wins on
any such disagreement; frontmatter reads remain in place as a fallback for
the case where the event log carries no opinion (for example, legacy
coord-topology missions that predate this seam), and no new
frontmatter-reading path was added - the merge gate still drives its
readiness loop off a frontmatter reader for that no-opinion case, by design.
The review-cycle artifact remains authoritative for &lt;em&gt;what the reviewer
said&lt;/em&gt; - the reviewer’s prose, affected files, reproduction command - never
for &lt;em&gt;which verdict is current&lt;/em&gt; once the event log has an opinion to give.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An arbiter’s override decision now durably persists and clears the merge
gate on its own - no separate flag or manual step required afterward
(mission &lt;code dir=&quot;auto&quot;&gt;review-cycle-verdict-seam-rebuild-01KZ2W7W&lt;/code&gt;; ADR
&lt;code dir=&quot;auto&quot;&gt;2026-08-03-1&lt;/code&gt;).&lt;/strong&gt; Before this fix, the arbiter override writer never
git-committed its output under any topology, so an override could be
present in a working tree and still vanish from a fresh clone or a
branch switch - the exact gap that made &lt;code dir=&quot;auto&quot;&gt;--skip-review-artifact-check&lt;/code&gt;
feel unreliable even when it had “worked.” Now the override is committed
through the same seam every other verdict-relevant write uses, so it
survives a fresh clone and the merge gate accepts it without repeating the
override flag.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An arbiter override can no longer be mistaken for, or silently absorbed
into, a genuine reviewer approval (mission
&lt;code dir=&quot;auto&quot;&gt;review-cycle-verdict-seam-rebuild-01KZ2W7W&lt;/code&gt;; ADR &lt;code dir=&quot;auto&quot;&gt;2026-08-03-1&lt;/code&gt;).&lt;/strong&gt; Before
this fix, nothing distinguished a knowingly-overridden standing rejection
from an approval a reviewer actually performed - both could present the
same way to a consumer reading only the latest verdict. Now the override is
recorded and read back as its own first-class outcome (a stated actor and
reason, event-sourced on the same partition as the record it annotates),
never fabricated as an approval review nobody performed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Applying a charter pack no longer leaves your project worse off than doing
nothing (mission &lt;code dir=&quot;auto&quot;&gt;charter-pack-usage-journey&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3104&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3105&lt;/code&gt;).&lt;/strong&gt; Before
this fix, &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter pack apply &amp;#x3C;pack&gt;&lt;/code&gt; on an unconfigured project
disabled the safe generic-agent dispatch fallback - so the next unmatched
&lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; hard-failed with &lt;code dir=&quot;auto&quot;&gt;ROUTER_NO_MATCH&lt;/code&gt; - and &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; still reported the charter as “not found” because
they gated on the display-only &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; that &lt;code dir=&quot;auto&quot;&gt;apply&lt;/code&gt; never writes. Now:
applying a pack &lt;strong&gt;without&lt;/strong&gt; compiling keeps the warned generic-agent net
engaged (an unmatched request still falls back, never &lt;code dir=&quot;auto&quot;&gt;ROUTER_NO_MATCH&lt;/code&gt;), and
checking that adds no extra doctrine-catalog load to the dispatch hot path
(&lt;code dir=&quot;auto&quot;&gt;#3118&lt;/code&gt;); &lt;code dir=&quot;auto&quot;&gt;apply --compile&lt;/code&gt; does the apply and compile in one step; after you
compile, &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; reflect the pack’s activated
governance and keep working even if &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; is deleted (the read
authority is the compiled &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;); and the governance resolver reports
the &lt;em&gt;activated&lt;/em&gt; directive set rather than silently falling back to all
built-in directives. The documented &lt;code dir=&quot;auto&quot;&gt;spec-kitty analyze&lt;/code&gt; surface and the CLI
are now guarded to stay in agreement (&lt;code dir=&quot;auto&quot;&gt;#3096&lt;/code&gt;). &lt;strong&gt;Deliberate behaviour
change:&lt;/strong&gt; the dispatch net now keys purely on whether a compiled bundle or a
routable profile/org pack exists, not on every activated doctrine dimension -
so a project that has activated only glossary packs, directives, or other
non-routing doctrine (no bundle, no routable profile) now falls back to the
generic-agent net too. This narrows the broader composite-dimension check the
&lt;code dir=&quot;auto&quot;&gt;#3064&lt;/code&gt; fix introduced above; it is a tested, recorded change, not a silent
regression.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Contract note - &lt;code dir=&quot;auto&quot;&gt;charter context --json&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;project_charter.present&lt;/code&gt;).&lt;/strong&gt; The
read authority for the JSON charter-presence surface moved from the
display-only &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; to the compiled &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;: a project that has a
&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; but never compiled now reports &lt;code dir=&quot;auto&quot;&gt;project_charter.present: false&lt;/code&gt;
(the new &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 expose the display file
separately, so the information is additive, not lost). The payload also now
carries a top-level &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;context_schema_version&lt;/code&gt;&lt;/strong&gt; stamp (a versioned &lt;em&gt;tracking&lt;/em&gt;
contract; a full shape freeze + deprecation policy stays deferred to the
&lt;code dir=&quot;auto&quot;&gt;#2519&lt;/code&gt; activation-surface work) so an external consumer can detect a shape
change instead of breaking silently. External &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; consumers should read
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; as the authority-of-record and pin &lt;code dir=&quot;auto&quot;&gt;context_schema_version&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;#2787&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A non-terminating test now fails loudly instead of hanging the CI job
(mission &lt;code dir=&quot;auto&quot;&gt;verification-trust-3115&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3115&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3113&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;pytest.ini&lt;/code&gt;
registered a &lt;code dir=&quot;auto&quot;&gt;timeout&lt;/code&gt; marker but set no timeout, so a test that never
returned stalled its whole shard rather than failing - a mechanism reporting
nothing where it should report a failure. The fast-test CI jobs now carry a
default per-test timeout (&lt;code dir=&quot;auto&quot;&gt;--timeout&lt;/code&gt; with the signal method), and a new
architectural gate (&lt;code dir=&quot;auto&quot;&gt;test_ci_fast_jobs_have_timeout.py&lt;/code&gt;) keeps the flag from
being silently dropped, with two documented exemptions (the real-wheel docs
build and the &lt;code dir=&quot;auto&quot;&gt;-n0&lt;/code&gt; real-port orphan-sweep, where a signal mid-teardown is
unsafe). Also hardens the terminal-render width fold, the egress-consent
boundary, and the &lt;code dir=&quot;auto&quot;&gt;tests/sync&lt;/code&gt; leak-guard so each is provable rather than
asserted. &lt;strong&gt;No product code (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli&lt;/code&gt;) changed&lt;/strong&gt; - this is a
test-trust and CI change; Windows and local runs still get no per-test
timeout (tracked by &lt;code dir=&quot;auto&quot;&gt;#3143&lt;/code&gt;). (&lt;code dir=&quot;auto&quot;&gt;#3130&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3136&lt;/code&gt; referenced.)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Fixed: &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; could deliver one project’s events to another project’s
workspace, including projects that never opted in (#3030).&lt;/strong&gt; A machine
keeps one shared local event journal across every Spec Kitty checkout on
it. Sync’s consent check only asked “is sync enabled for &lt;em&gt;this&lt;/em&gt; checkout?”&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;once yes, it delivered the &lt;em&gt;entire&lt;/em&gt; journal, so a single opted-in
project could ship another, unrelated project’s events and metadata to the
hosted server. Every path that reads from the journal for delivery is now
gated per-project, consent is checked before events leave the machine
rather than only at the checkout level, and an unresolvable consent check
now fails closed (refuses to send) instead of failing open. If you use
hosted sync for more than one local project, only the project(s) you
explicitly opted in now have their data sent.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Generated agent guidance reads grammatically again (mission
&lt;code dir=&quot;auto&quot;&gt;charter-delivery-finish-context-degod&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3082&lt;/code&gt;).&lt;/strong&gt; The “verbatim-or-fetch”
disclosure lines every agent receives in charter context were frequently
ungrammatical - e.g. &lt;code dir=&quot;auto&quot;&gt;When you designing or reviewing significant code changes, run this command&lt;/code&gt;. The authored &lt;code dir=&quot;auto&quot;&gt;when&lt;/code&gt; clause is now normalized into
the closed contract lead-in set (&lt;code dir=&quot;auto&quot;&gt;When you are about to ...&lt;/code&gt;) for every clause
shape, and the prompt-governance contract is asserted &lt;strong&gt;per stanza&lt;/strong&gt; so a
regression can’t hide behind another matching line. (A second, independent
render surface in &lt;code dir=&quot;auto&quot;&gt;section_bodies.py&lt;/code&gt; is tracked separately as &lt;code dir=&quot;auto&quot;&gt;#3093&lt;/code&gt;.)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;DRG document-writer blind spot closed (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-delivery-activation&lt;/code&gt;;
&lt;code dir=&quot;auto&quot;&gt;#3075&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2977&lt;/code&gt;).&lt;/strong&gt; All three &lt;code dir=&quot;auto&quot;&gt;DRGGraph&lt;/code&gt; document-emit sites
(&lt;code dir=&quot;auto&quot;&gt;rewrite_opposed_by&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;charter.synthesizer.project_drg&lt;/code&gt;, and the
&lt;code dir=&quot;auto&quot;&gt;pack_assembler&lt;/code&gt; force-dedup path) now route through the canonical
&lt;code dir=&quot;auto&quot;&gt;graph_document_to_dict&lt;/code&gt; and are registered &lt;code dir=&quot;auto&quot;&gt;DocumentWriter&lt;/code&gt; members, guarded
by a new non-vacuous writer-discovery gate that fails on either an
unregistered dict-literal or a &lt;code dir=&quot;auto&quot;&gt;.model_dump()&lt;/code&gt;-shaped emitter. The
&lt;code dir=&quot;auto&quot;&gt;pack_assembler&lt;/code&gt; path was additionally crashing &lt;code dir=&quot;auto&quot;&gt;yaml.safe_dump&lt;/code&gt; on the
&lt;code dir=&quot;auto&quot;&gt;Relation&lt;/code&gt; enum (and leaking withheld fields). The repository surfaces are
typed via a new &lt;code dir=&quot;auto&quot;&gt;ArtifactRepository&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;Protocol&lt;/code&gt;, removing 12
&lt;code dir=&quot;auto&quot;&gt;# type: ignore[attr-defined]&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;DRGGraphSchemaError&lt;/code&gt; now surfaces as a structured &lt;code dir=&quot;auto&quot;&gt;doctrine validate&lt;/code&gt;
issue instead of an uncaught traceback&lt;/strong&gt;, and &lt;code dir=&quot;auto&quot;&gt;AssetRepository.source_path&lt;/code&gt;
no longer disagrees with &lt;code dir=&quot;auto&quot;&gt;get&lt;/code&gt; for a manifest that failed validation (a base
&lt;code dir=&quot;auto&quot;&gt;_post_validate&lt;/code&gt; success-path hook records the source path only after
validation) (&lt;code dir=&quot;auto&quot;&gt;#3062&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;test_every_load_delivery&lt;/code&gt; fixture is now hermetic&lt;/strong&gt; to an ambient
gitignored &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/context-state.json&lt;/code&gt;, eliminating a local-only
false-red on the &lt;code dir=&quot;auto&quot;&gt;first_load&lt;/code&gt;/bootstrap assertions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Read-side placement seam: mission reads route through the kind-aware seam and
new bypasses are structurally impossible (#2922, #1878; also #2921, #2966
part-1).&lt;/strong&gt; The write side already failed loud when an artifact’s coordination
partition was gone, but ~50 modules still read mission artifacts through the
low-level kind-blind resolvers, so a read could silently substitute the primary
checkout for a deleted coord branch:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Every fail-loud-appropriate caller (72 sites, per a per-site classification
ledger) now reads via &lt;code dir=&quot;auto&quot;&gt;PlacementSeam.read_dir(&amp;#x3C;kind&gt;)&lt;/code&gt; with the correct
artifact kind. Coord-partition reads - a lane-based merge’s event log, the
decision-log companion read, the doctrine synthesizer - now fail loud instead
of treating a deleted coordination branch as healthy.&lt;/li&gt;
&lt;li&gt;16 diagnostic/audit/SaaS-facing readers (dashboard scan, dossier API,
retrospective summary, status aggregation, and friends) stay &lt;strong&gt;lenient by
design&lt;/strong&gt; and are recorded as justified allow-list entries - reporting surfaces
must not start raising.&lt;/li&gt;
&lt;li&gt;A new whole-tree AST gate reds on any future direct kind-blind read in a
non-sanctioned module, reusing the same scanner as the write-side gate. The
allow-list is shrink-only: a staleness twin-guard reds until an entry that is
no longer needed is deleted.&lt;/li&gt;
&lt;li&gt;Behavior is unchanged for the healthy case; &lt;code dir=&quot;auto&quot;&gt;repair_lane_mismatch&lt;/code&gt; no longer
duplicates frontmatter into the document body (#2921), and
&lt;code dir=&quot;auto&quot;&gt;backfill_runtime_state&lt;/code&gt;’s mission-id read is anchored on the PRIMARY leg.&lt;/li&gt;
&lt;li&gt;Fail-loud does &lt;strong&gt;not&lt;/strong&gt; mean crash on the paths that exist to recover from a
broken coordination branch. &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement --recover&lt;/code&gt; now reports a
&lt;code dir=&quot;auto&quot;&gt;COORDINATION&lt;/code&gt; finding carrying the &lt;code dir=&quot;auto&quot;&gt;doctor coordination --fix&lt;/code&gt; remediation
instead of tracebacking, &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; aborts with a readable message
before any state change rather than mid-merge, and &lt;code dir=&quot;auto&quot;&gt;agent workflow review&lt;/code&gt;
degrades to an advisory warning instead of aborting while computing one.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty verify&lt;/code&gt;’s mission-directory probe is now CWD-invariant: invoked
from a lane worktree it resolves the main repository’s &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; rather
than reporting the mission as absent. Both production callers already
anchored on the main repo, so this is observationally a no-op for them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; no longer rewinds finished work packages to
&lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt; (#3013, #2985).&lt;/strong&gt; The birth-cutover seed anchored its
&lt;code dir=&quot;auto&quot;&gt;planned -&gt; claimed&lt;/code&gt; carrier on a work package’s &lt;em&gt;earliest&lt;/em&gt; transition,
which for a force-jumped or pruned WP is its &lt;strong&gt;terminal&lt;/strong&gt; one. The seed
then collided on timestamp, and because the reducer sorts by
&lt;code dir=&quot;auto&quot;&gt;(at, event_id)&lt;/code&gt; the hash-derived seed id outranked the real ULID - folding
a &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; WP back to &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt;, so a second &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; on an unchanged tree
did not converge. (This corrects the mechanism recorded on #2985: it is the
sort key, not append order.) &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; is also now event-count neutral on
missions whose runtime state is already canonical. &lt;strong&gt;Already-corrupted logs
do not self-heal&lt;/strong&gt; - they still need the #3003 corpus regenerate, which
this unblocks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt; no longer destroys &lt;code dir=&quot;auto&quot;&gt;review_result&lt;/code&gt;, log
order, or dropped duplicates (#3003).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;_build_canonical_row&lt;/code&gt; is a closed
allowlist that omitted &lt;code dir=&quot;auto&quot;&gt;review_result&lt;/code&gt; - a first-class &lt;code dir=&quot;auto&quot;&gt;StatusEvent&lt;/code&gt; field
&lt;em&gt;and&lt;/em&gt; a hard FSM guard, since every transition out of &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; is
rejected without it. Repairing a corpus therefore converted valid history
into events the reducer could no longer validate: 268 transitions across 44
missions, with none failing beforehand. The loss was worst-shaped, because
&lt;code dir=&quot;auto&quot;&gt;DoneEvidence.review&lt;/code&gt; mirrors the payload only on approval - so the
&lt;code dir=&quot;auto&quot;&gt;changes_requested&lt;/code&gt; rows were the irrecoverable ones. The allowlist is now
gated against &lt;code dir=&quot;auto&quot;&gt;StatusEvent.__dataclass_fields__&lt;/code&gt; so a newly added model
field cannot be dropped the same way. Two further fixes: rows now sort on
&lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; &lt;strong&gt;or&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;timestamp&lt;/code&gt; (lifecycle and retrospective rows date themselves
with the latter, so 839 of them were collapsing to &lt;code dir=&quot;auto&quot;&gt;&quot;&quot;&lt;/code&gt; and being hoisted to
the head of an append-only log), and a dropped duplicate &lt;code dir=&quot;auto&quot;&gt;event_id&lt;/code&gt; row is
quarantined rather than only hashed.&lt;/li&gt;
&lt;li&gt;The classification ledger is now the &lt;em&gt;mechanical&lt;/em&gt; authority for the
stay-lenient allow-list - the gate parses it, so the doc and the gate cannot
drift apart silently. The gate additionally resolves import aliases, and its
coverage bounds (including the unpoliced &lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt;)
are stated explicitly rather than implied.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Almost the entire test suite was being skipped on pushes to &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; (#2957).&lt;/strong&gt;
CI decides which test jobs to start by looking at which paths a change
touched. That is a sensible optimisation for a pull request, but it was
applied to pushes to the protected branch as well - so a merge whose diff
happened to match none of the path filters started &lt;strong&gt;10 of 50&lt;/strong&gt; test jobs and
left &lt;strong&gt;31,547 of 33,822&lt;/strong&gt; test cases (93.3%) running nowhere. This was not
theoretical: four test files that pin frozen contracts were failing on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;
while &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; CI reported green, because the only jobs that would have run them
were filtered out. Path filtering is now a pull-request optimisation only. A
push to a protected branch starts 49 of the 50 suite jobs and leaves no test
uncollected; pull requests are unchanged. A new check
(&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_ci_collection_completeness.py&lt;/code&gt;) fails if any
collected test is left with no job that would run it on a push to &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;. It
has no baseline and no allowlist - the only way to satisfy it is to make a job
actually run the test.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Doctrine packs could declare things that quietly had no effect (mission
&lt;code dir=&quot;auto&quot;&gt;doctrine-silence-guards&lt;/code&gt;; ADRs &lt;a href=&quot;/adr/3.x/2026-07-26-1-drg-edges-are-the-canonical-relationship-authority/&quot;&gt;2026-07-26-1&lt;/a&gt;,
&lt;a href=&quot;/adr/3.x/2026-07-26-2-doctrine-artefact-pack-layout-convention/&quot;&gt;2026-07-26-2&lt;/a&gt;,
&lt;a href=&quot;/adr/3.x/2026-07-26-3-impacts-edge-subsumes-in-tension-with/&quot;&gt;2026-07-26-3&lt;/a&gt;).&lt;/strong&gt;
The doctrine layer’s characteristic failure was silence rather than error: a
declaration was accepted, validated, reported as loaded, and then dropped. Every
case below now either works or fails with a message naming what was wrong.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Five of the sixteen artifact kinds were missing from the doctrine-graph
extractor&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;anti_pattern&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;glossary&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;glossary_pack&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;glossary_scope&lt;/code&gt; were dropped whenever the graph was rebuilt. All sixteen are
handled, and the mapping is now checked for completeness instead of being
maintained by hand.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two of the twelve org-pack directory names crashed the merge outright&lt;/strong&gt;
with a bare &lt;code dir=&quot;auto&quot;&gt;KeyError&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission_types/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;glossary_packs/&lt;/code&gt;). One consequence
worth naming: the shipped test fixture called &lt;code dir=&quot;auto&quot;&gt;augment-all-kinds-pack&lt;/code&gt; could
not be merged at all, so the “all kinds” fixture never exercised all kinds.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Edges derived automatically from an org pack’s agent-profile fields never
reached the graph.&lt;/strong&gt; The producer emitted fully-qualified &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;kind&gt;:&amp;#x3C;id&gt;&lt;/code&gt;
endpoints; the code that consumed them looked up bare ids. Nothing matched,
so 100% of that path’s output was discarded, silently.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;An edge from a built-in artifact to a pack artifact was dropped&lt;/strong&gt; with
neither a warning nor an error. It now resolves, or reports a typed error
naming the endpoint it could not resolve.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A bare name that referred to a styleguide was turned into a made-up
&lt;code dir=&quot;auto&quot;&gt;directive:&amp;#x3C;name&gt;&lt;/code&gt; node&lt;/strong&gt; rather than the &lt;code dir=&quot;auto&quot;&gt;styleguide:&amp;#x3C;name&gt;&lt;/code&gt; the author
meant.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Unrecognised keys in agent profiles and in graph nodes and edges were
silently ignored&lt;/strong&gt;, so a typo or a retired key left an artifact that read
one way and behaved another (see Breaking Changes).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Activating the &lt;code dir=&quot;auto&quot;&gt;doctrine-daphne&lt;/code&gt; agent profile pulled in 76 related
artifacts but not the one procedure the profile itself says it runs.&lt;/strong&gt; The
edge to that procedure used a relation type (&lt;code dir=&quot;auto&quot;&gt;applies&lt;/code&gt;) that nothing
traverses, and it was the procedure’s only inbound edge, so the profile’s own
operating procedure was unreachable. The edge is retyped to &lt;code dir=&quot;auto&quot;&gt;requires&lt;/code&gt;, and
authoring an &lt;code dir=&quot;auto&quot;&gt;applies&lt;/code&gt; edge into the shipped tree is now rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Error messages sent operators to files that do not exist&lt;/strong&gt; - an inline
reference rejection pointed at &lt;code dir=&quot;auto&quot;&gt;src/doctrine/graph.yaml&lt;/code&gt;, split into per-kind
fragments long ago, and two operator-facing skill documents told authors to
read a &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&amp;#x3C;kind&gt;/shipped/&lt;/code&gt; layer that has never existed on disk.
Both are corrected and both are now guarded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The generated schema for the docs structural lint had widened to “any
object”&lt;/strong&gt;, so a malformed lint configuration validated cleanly and the lint
ran on settings nobody had checked. The generator now emits the real
ten-key contract.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The documented example for declaring agent-profile lineage used a syntax
that exists nowhere in the vocabulary&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;urn:profile:...&lt;/code&gt;). Anyone who copied
it got a declaration that merged without complaint and produced no edge. The
example is corrected in &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;CLAUDE.md&lt;/code&gt; and in
&lt;a href=&quot;/guides/how-to/governance/create-an-org-doctrine-pack/&quot;&gt;the org-pack authoring guide&lt;/a&gt;, and
the accepted forms are now enforced at merge time.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks mark-status&lt;/code&gt; could not find subtask ids written the
way the shipped template tells you to write them (#2962).&lt;/strong&gt; The command
resolved a subtask id by matching a row shape in &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; - a checkbox, a
pipe-table row, or an inline &lt;code dir=&quot;auto&quot;&gt;Subtasks: T001, T002&lt;/code&gt; list. The shipped
&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; template instructs authors that subtask rows are reference
rows and explicitly &lt;em&gt;not&lt;/em&gt; checkboxes, so a &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; that follows the
template matched none of those shapes and every id came back &lt;code dir=&quot;auto&quot;&gt;NOT_FOUND&lt;/code&gt;.
That blocked the review workflow on every work package of every mission using
that template. The command now falls back to the authored &lt;code dir=&quot;auto&quot;&gt;subtasks:&lt;/code&gt; roster
in work-package frontmatter - the same list the lane-transition guard already
treats as canonical, so the two surfaces agree on what a work package’s
subtasks are. The fallback runs last, so every row shape that worked before
resolves exactly as before.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Placement-port residuals: partition routing is now enforced by the port, not
by caller discipline (#2923, #2924, #2926, #2932; epic #2931).&lt;/strong&gt; Closes the
residuals deferred from the coord-write-placement-closure merge (PR #2920):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The sole &lt;code dir=&quot;auto&quot;&gt;status_phase&lt;/code&gt; writer (&lt;code dir=&quot;auto&quot;&gt;_flip_phase&lt;/code&gt;) resolves its write target
through the placement port and &lt;strong&gt;fails closed&lt;/strong&gt; with a typed
&lt;code dir=&quot;auto&quot;&gt;PlacementMismatchError&lt;/code&gt; (writing nothing) if the resolved PRIMARY home
disagrees with the caller’s directory - coincidental correctness becomes an
enforced invariant.&lt;/li&gt;
&lt;li&gt;The two-target legacy cutover reads &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; frontmatter from the PRIMARY leg
while the status event write stays on COORD.&lt;/li&gt;
&lt;li&gt;Three hand-rolled “resolve write target, else degrade” copies collapse into
one &lt;code dir=&quot;auto&quot;&gt;resolve_write_target_or_degrade&lt;/code&gt; helper (each caller keeps its own
fail-open / fail-closed policy), and the retrospective trace loader degrades
to &lt;code dir=&quot;auto&quot;&gt;[]&lt;/code&gt; on a deleted coordination branch. A latent bug is fixed along the way:
a caller-supplied coordination branch that was silently discarded in the
pre-&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; bootstrap window is now honored.&lt;/li&gt;
&lt;li&gt;The write-side placement scan no longer blanket-exempts the &lt;code dir=&quot;auto&quot;&gt;migration/&lt;/code&gt;
subtree, restoring whole-tree precision. The remaining deferred gate/contract
reds were already green on the current base and are verified in-mission.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The merge review-readiness check no longer writes a stray &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;
during a merge (#2934).&lt;/strong&gt; The check that looks for a rejected review before
merge was reducing mission status through the &lt;em&gt;writing&lt;/em&gt; materializer, so it
left a &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; snapshot on disk as a side effect. On a mission with no
status events yet, that snapshot had no matching &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; (the
append-only event log that is the real source of truth), and the merge could
commit the orphaned snapshot on its own - the invalid “snapshot without its
event log” state the status doctor flags. The check now reads status without
writing anything; a gate reads, it does not persist. Includes the regression
test and a de-mocked planning-only merge test that exposed the shape.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Running Spec Kitty non-interactively (agents, CI, piped input) no longer
hangs waiting for a prompt that will never be answered (#2876; extended in
#2912; landed by #2910).&lt;/strong&gt; Under &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_NON_INTERACTIVE=1&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty plan&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; reached their discovery interviews and called a blocking prompt with
no non-interactive gate anywhere in the call graph, so an open-but-silent
stdin pipe made them wait forever. The interviews now honor the contract: they
still open every Decision Moment and write the decision index, but take
defaults and record each question as deferred instead of prompting - no prompt
is ever emitted non-interactively. A single authority, &lt;code dir=&quot;auto&quot;&gt;core/env.is_interactive()&lt;/code&gt;
(precedence &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_FORCE_INTERACTIVE&lt;/code&gt; &gt; &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_NON_INTERACTIVE&lt;/code&gt; &gt; a
real TTY), now backs that decision, and #2912 routed the four other divergent
prompt-gates - &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; hollow-review confirm, the &lt;code dir=&quot;auto&quot;&gt;intake&lt;/code&gt;
candidate picker, and &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; - through it too, so every prompt obeys the
same rule (with &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; keeping its CI-environment veto layered on top). Also
fixes the garbled interview hint menu where Rich was eating &lt;code dir=&quot;auto&quot;&gt;[enter]&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;[text]&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;[d]&lt;/code&gt;
as style tags.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Merging an accepted mission no longer discards the acceptance and
issue-matrix evidence recorded when it was accepted (#2804; scorer hardening
#2912; landed by #2910).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; are filled on the
target at accept time while the mission branch keeps empty scaffolds; the
squash integration ran &lt;code dir=&quot;auto&quot;&gt;git merge --squash -X theirs&lt;/code&gt;, so the empty scaffold
won the add/add conflict and the merged history kept blank gate artifacts -
losing the audit trail exactly when a reviewer needs it. Two new custom merge
drivers (&lt;code dir=&quot;auto&quot;&gt;merge-driver-acceptance-matrix&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;merge-driver-issue-matrix&lt;/code&gt;) now
keep whichever side actually carries evidence - scored, not fixed-side, so it
is correct whether the fill happened on the target or in a lane, with ties
going to the target where accept ran. The scorers were then hardened (#2912) to
read the scaffold marker from the field the scaffolder actually writes, and to
resolve verdict/title columns by canonical header rather than fixed position,
so a reordered or minimal matrix scores correctly. Seeded into &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt;,
the &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; seed, and an upgrade migration for already-initialized repos -
following the same pattern as the #2709 meta/traces drivers.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lifecycle gates no longer emit a confident-but-wrong verdict when run from
the wrong worktree, and a misclassified lock write no longer blocks a claim or
merge (#1834, #2885, #2882, #2795).&lt;/strong&gt; Every lifecycle gate now receives an
explicit execution context - which tree, which ref, which phase - and refuses,
recording a clear cannot-evaluate diagnostic instead of a pass/fail, when that
context is missing or inconsistent, rather than silently inheriting the
caller’s working directory and judging a fact about one worktree against
another. Separately, &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; no longer wrongly report a
work package as blocked because Spec Kitty mistook its own planning-partition
lock write for a dirty tree (the #2795 claim-blocker, now topology-agnostic).
Internally, eleven scattered gate-exemption predicates are retired onto one
owner guarded by an exemption-registry ratchet, and the accept gate now
asserts ref-agreement before it judges the acceptance matrix.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt; missing-file errors now name the regenerate command.&lt;/strong&gt;
Both files are already scaffolded automatically during &lt;code dir=&quot;auto&quot;&gt;spec-kitty tasks&lt;/code&gt; (finalize-tasks); the failure messages an operator actually sees when one is missing (at &lt;code dir=&quot;auto&quot;&gt;move-task --to approved&lt;/code&gt; and at &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt;) previously said nothing about that, so a missing file read as “no tooling exists for this” rather than “re-run finalize-tasks.” Both messages now name &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission finalize-tasks --mission &amp;#x3C;slug&gt;&lt;/code&gt;, and the issue-matrix message also points at its schema/worked-example doc (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/review/ERROR_CODES.md&lt;/code&gt;). The &lt;code dir=&quot;auto&quot;&gt;spec-kitty-mission-review&lt;/code&gt; skill’s Gate 4 section gained the same pointer.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Windows backslash in git tree-path misreported committed specs as uncommitted (#2836).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;_git_commit_check_context&lt;/code&gt; built the git tree path with &lt;code dir=&quot;auto&quot;&gt;str(Path(...))&lt;/code&gt;, which
renders using the OS-native separator - a backslash (&lt;code dir=&quot;auto&quot;&gt;\&lt;/code&gt;) on Windows. Git’s
&lt;code dir=&quot;auto&quot;&gt;HEAD:&amp;#x3C;path&gt;&lt;/code&gt; object syntax and &lt;code dir=&quot;auto&quot;&gt;ls-files&lt;/code&gt; pathspec require forward slashes, so
both subprocess checks failed and &lt;code dir=&quot;auto&quot;&gt;is_committed()&lt;/code&gt; reported genuinely-committed
spec files as uncommitted, blocking the setup-plan workflow (e.g.
&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt; refusing to proceed). Both return sites now resolve through a
single worktree-aware kernel seam (&lt;code dir=&quot;auto&quot;&gt;kernel.paths.repo_tree_path&lt;/code&gt;) that renders
forward slashes on every host via &lt;code dir=&quot;auto&quot;&gt;PurePosixPath&lt;/code&gt;. Invisible on POSIX
(macOS/Linux/CI) where &lt;code dir=&quot;auto&quot;&gt;os.sep&lt;/code&gt; is already &lt;code dir=&quot;auto&quot;&gt;/&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Posix path-separator normalization consolidated into one kernel seam.&lt;/strong&gt;
The &lt;code dir=&quot;auto&quot;&gt;str(x).replace(&quot;\\&quot;, &quot;/&quot;)&lt;/code&gt; idiom behind #2836 was scattered across ~17
sites in &lt;code dir=&quot;auto&quot;&gt;charter&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; (review, upgrade +
migrations, merge, git, skills, status, paths, bulk_edit) - each an independent
chance to reintroduce the Windows backslash defect. All now route through the
behaviour-agnostic &lt;code dir=&quot;auto&quot;&gt;kernel.paths.to_posix(path: Path | str)&lt;/code&gt; seam (kernel being
the zero-dependency root every layer can import downward), leaving the seam
definition as the only &lt;code dir=&quot;auto&quot;&gt;replace(&quot;\\&quot;, &quot;/&quot;)&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/&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;merge&lt;/code&gt;’s hollow-review warning no longer flags a WP with a genuinely independent reviewer.&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;force_count &gt;= 2&lt;/code&gt; alone can’t distinguish “the reviewer used &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; to bypass an unrelated gate false-positive” from “no independent review happened” - both increment the same counter. When the event log positively confirms a different actor logged the approving transition than the one that most recently implemented the WP, the warning no longer fires; absence of that evidence still warns as before (fail-safe default, never suppressed on uncertain data).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Honest force-provenance on evidence-gated backward edges (#2684, #2736, #2810).&lt;/strong&gt;
Persisted &lt;code dir=&quot;auto&quot;&gt;StatusEvent.force&lt;/code&gt; is now truthful - falsy on the evidence-gated
review-rejection edges (&lt;code dir=&quot;auto&quot;&gt;build_transition_plan&lt;/code&gt; asks the FSM instead of
auto-promoting &lt;code dir=&quot;auto&quot;&gt;force&lt;/code&gt;) and truthful on genuine guard-bypasses (leaving a
terminal &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;). Fixes the false-force stamp found during #2736 / PR #2810.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Off-axis emit sites resolve their write target from stored topology, never &lt;code dir=&quot;auto&quot;&gt;Path.cwd()&lt;/code&gt; (#2647).&lt;/strong&gt;
Runtime-state events can no longer be written against the wrong feature
directory when the CLI runs from a foreign working directory.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Rollback to &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; releases the prior claim (#2512).&lt;/strong&gt;
A rolled-back work package no longer retains a stale &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; in the
reduced snapshot, so the next resume/re-claim is not blocked by a dead claim.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Runtime-state backfill verify is now genuinely fail-closed on value tampering (#2684).&lt;/strong&gt;
The parity check could silently pass a tampered value when a correcting seed annotation
happened to sort last in a same-timestamp reduce fold (a content-hash-ULID coin-flip); it
now flags any two annotations assigning different values to one slot as corruption,
regardless of fold order. (The backfill CLI wiring itself remains deferred to #2816.)
The runtime-state eviction also hardens the dual-write end-state: bypass frontmatter reads
routed onto the gated snapshot seam, the phase-1 authority predicate split from the legacy
lane-mirror, and the #2093 authority invariant asserted by imported-symbol identity.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Fresh-project &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; no longer crashes after the &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; inversion (#2800, #2773).&lt;/strong&gt;
Post-#2773, &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; stopped writing &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;, but the fresh-project
synthesize intercept still gated on &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; being present - so on a real fresh
project the intercept never fired and &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; fell through to the production
adapter, exiting 1 with &lt;code dir=&quot;auto&quot;&gt;&apos;str&apos; object has no attribute &apos;get&apos;&lt;/code&gt;. The intercept now gates on
the authoritative &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; (what &lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt; writes), restoring the fresh-project seed
path and aligning with the inversion invariant that &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; is display-only, never a
resolving signal.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Pre-review regression gate no longer silently skipped by a leaked sync toggle in the parallel suite (#2800, #2794).&lt;/strong&gt;
The gate reuses the sync layer’s process-wide &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SYNC_MINIMAL_IMPORT&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SYNC_DISABLE&lt;/code&gt; opt-outs; in a whole-tree &lt;code dir=&quot;auto&quot;&gt;-n auto&lt;/code&gt; run one could leak into an
xdist worker and skip the gate, turning the gate-observability tests red. An autouse fixture now
unsets both toggles before every agent test, making them worker- and order-independent. No
production behaviour change; the deliberate gate↔sync coupling is tracked for a dedicated
opt-out in #2801.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CI test-suite remediation: stale fixtures from two recent merges brought back to green (#2800).&lt;/strong&gt;
The &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; consolidation (#2773) and the coord-rollback transactionality mission
(#2786) merged with un-flagged test-fixture debt a CI path-filter hid until #2800 surfaced
it: charter selection/bundle/synthesize/freshness fixtures still seeding the retired
&lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt; triad; arch-gate remainders (golden-count, tmp-literal,
marker drift); a #2709 regression fixture missing the canonical &lt;code dir=&quot;auto&quot;&gt;force&lt;/code&gt; event field; and 89
mechanical &lt;code dir=&quot;auto&quot;&gt;mypy --strict&lt;/code&gt; errors in the agent test package. Fixtures re-pointed onto
&lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;, gates re-based, and tests whose premise encoded a retired flow removed
outright per the standing-order §4 remediation framework (now amended to codify
&lt;em&gt;superseded-design -&gt; remove&lt;/em&gt;). The legacy-topology bootstrap CWD gap a strict-xfail guards
is now tracked in #2802.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Sync batch-400 poison isolation - one invalid event no longer strands its whole batch (#2736; closes #2755).&lt;/strong&gt;
A whole-batch HTTP 400 with no per-event &lt;code dir=&quot;auto&quot;&gt;details&lt;/code&gt; made the CLI fan the batch-level error onto &lt;strong&gt;every&lt;/strong&gt;
event as &lt;code dir=&quot;auto&quot;&gt;rejected&lt;/code&gt; (non-terminal), so the culprit re-poisoned every subsequent drain and the innocents
never delivered - the upstream cause of the &lt;code dir=&quot;auto&quot;&gt;wp_status_event_without_create&lt;/code&gt; projection anomaly. The
receiver now recursively &lt;strong&gt;bisects&lt;/strong&gt; a poison batch (&lt;code dir=&quot;auto&quot;&gt;delivery/receivers.py&lt;/code&gt;): split -&gt; re-POST both halves
-&gt; recurse to singletons, isolating the culprit (kept &lt;code dir=&quot;auto&quot;&gt;rejected&lt;/code&gt;/retryable, never force-parked) and
delivering every innocent, with create-before-status ordering preserved by sequential left-before-right
recursion (and a split-point clamp so a same-&lt;code dir=&quot;auto&quot;&gt;wp_id&lt;/code&gt; create+status pair still terminates). The live
offline-queue path (&lt;code dir=&quot;auto&quot;&gt;sync/batch.py&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;_parse_error_response&lt;/code&gt; no-&lt;code dir=&quot;auto&quot;&gt;details&lt;/code&gt; branch) now dispositions a
batch-level 400 as &lt;code dir=&quot;auto&quot;&gt;failed_transient&lt;/code&gt; (no &lt;code dir=&quot;auto&quot;&gt;retry_count&lt;/code&gt; bump) instead of poisoning innocents. A single
shared &lt;code dir=&quot;auto&quot;&gt;core/batch_partition.py&lt;/code&gt; primitive (&lt;code dir=&quot;auto&quot;&gt;split_in_half&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;create_aware_midpoint&lt;/code&gt;) de-duplicates the
batch-splitting math and &lt;strong&gt;closes #2755&lt;/strong&gt; by retrofitting the 413 byte-shrink onto it, guarded by a
behavioral + AST single-authority test. CLI-side only, no server-contract change; the SaaS
transition-matrix and reducer alignment are tracked cross-repo (spec-kitty-saas#509 / #510).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission squash merge no longer clobbers target-newer acceptance provenance or traces (#2709).&lt;/strong&gt;
The supported squash merge ran &lt;code dir=&quot;auto&quot;&gt;git merge --squash -X theirs&lt;/code&gt; on every conflicting file,
silently reverting target-newer &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; acceptance/VCS fields (and &lt;code dir=&quot;auto&quot;&gt;traces/*.md&lt;/code&gt;
sections) to the older mission-branch copies, and the coord-&gt;target projection
blind-overwrote the durable event log and &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;. Merges now reconcile &lt;strong&gt;per
artifact class&lt;/strong&gt;: planning artifacts stay mission-authoritative (&lt;code dir=&quot;auto&quot;&gt;-X theirs&lt;/code&gt; intent from
#1732 preserved), while &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; acceptance/VCS keys field-merge target-authoritative
with &lt;code dir=&quot;auto&quot;&gt;acceptance_history&lt;/code&gt; unioned and &lt;code dir=&quot;auto&quot;&gt;traces/*.md&lt;/code&gt; do a line-level union - via new
&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge-driver-meta&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;merge-driver-traces&lt;/code&gt; git drivers whose activation is
scoped to the ephemeral squash merge (they no longer leak into a later &lt;code dir=&quot;auto&quot;&gt;auto_rebase&lt;/code&gt;). The
projection unions the event log via &lt;code dir=&quot;auto&quot;&gt;merge_event_payloads&lt;/code&gt; and rematerializes &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;
from the reduced log instead of a blind copy. Seeded by migration &lt;code dir=&quot;auto&quot;&gt;m_3_2_6&lt;/code&gt;. Ships with a
red-first reproduction and two class-closing architectural lints (no-blind-copy over the
projection path + driver-registry completeness sourced from the canonical artifact-kind
registry).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Merge rollback and &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; stay coherent after a failed target advance (#2711).&lt;/strong&gt;
When target advancement failed after &lt;code dir=&quot;auto&quot;&gt;approved -&gt; done&lt;/code&gt; events were committed to the
coordination branch, rollback reverted only working-tree bytes - leaving a committed &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;
opposed to a reverted working &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; - and &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge --resume&lt;/code&gt; re-emitted a
fresh &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; (non-idempotent). Rollback now reverts the coordination &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; commit
(coord-worktree &lt;code dir=&quot;auto&quot;&gt;git revert&lt;/code&gt;, sourced from the canonical write-target ref; never a raw
&lt;code dir=&quot;auto&quot;&gt;update-ref&lt;/code&gt;), and &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; derives progress from the durable committed event log with
&lt;code dir=&quot;auto&quot;&gt;MergeState.completed_wps&lt;/code&gt; demoted to an advisory hint - so committed and working status
stay coherent and resume is &lt;code dir=&quot;auto&quot;&gt;event_id&lt;/code&gt;-stable. INV-5 (#1827) merge-phase ordering is
preserved. Ships with a red-first reproduction and a resume non-reemission property guard.
Tracked follow-ups: &lt;strong&gt;#2786&lt;/strong&gt; (write a durable reconcile marker when the rollback revert
itself fails) and &lt;strong&gt;#2794&lt;/strong&gt; (a &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SYNC_MINIMAL_IMPORT&lt;/code&gt; test-isolation leak that
skips the pre-review gate under the parallel CI suite).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A failed coordination-&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; revert during rollback no longer silently re-opens the
#2711 split-brain (#2786), and the coordination write-set rolls back transactionally
(#2367 Mechanism B).&lt;/strong&gt; When the rollback’s coord-&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;git revert&lt;/code&gt; itself &lt;em&gt;failed&lt;/em&gt; (#2786),
or when a merge aborted mid-way through &lt;code dir=&quot;auto&quot;&gt;_record_merged_wps_done_for_merge&lt;/code&gt; before any revert
ran (#2367-B), rollback restored only working-tree bytes and left a committed &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; opposed to
a reverted working &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; - a silently-stranded split-brain. Rollback now &lt;strong&gt;marks-not-raises&lt;/strong&gt;:
a durable &lt;code dir=&quot;auto&quot;&gt;MergeState.pending_coord_reconcile&lt;/code&gt; marker records the stranded WP(s) - derived from
the &lt;strong&gt;committed&lt;/strong&gt; coordination ref (the reliable authority; a working-tree diff is empty at the
revert-failure point) over &lt;em&gt;this merge’s own&lt;/em&gt; pre-target &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; write-set, so a legitimately
pre-existing-&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; WP is never re-stranded. &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge --resume&lt;/code&gt; heals via a strand-gated,
idempotent &lt;code dir=&quot;auto&quot;&gt;git revert&lt;/code&gt; (byte-stable on re-run), and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor coordination&lt;/code&gt; detects the
strand (re-verifying incoherence from the committed ref, not marker-presence) with a &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt;. A
behavioral class-closing guard reds if any of the seven &lt;code dir=&quot;auto&quot;&gt;_restore_final_bookkeeping_snapshots&lt;/code&gt;
rollback sites (incl. the previously-unenumerated coord-reachable site) strands without marking.
INV-5 (#1827) ordering preserved; happy-path merge byte-identical. Ships red-first repros for both
mechanisms. Deferred with follow-ups: &lt;strong&gt;#2797&lt;/strong&gt; (unify the two &lt;code dir=&quot;auto&quot;&gt;git revert&lt;/code&gt; transport legs into
one shared helper). (&lt;strong&gt;#2795&lt;/strong&gt;, #2367 Mechanism A - claim-time VCS-lock resync, was deferred here
and has since landed in #2906, above.)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output is now plain regardless of terminal colour; CLI tests are colour-deterministic (#2632).&lt;/strong&gt;
Under a colour-forcing harness (e.g. &lt;code dir=&quot;auto&quot;&gt;FORCE_COLOR=3&lt;/code&gt;) Rich syntax-highlighted &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;
output - splicing ANSI escapes into the payload so &lt;code dir=&quot;auto&quot;&gt;json.loads&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;| jq&lt;/code&gt; choked - and
split literal substrings in styled human output, red-ing ~81 pre-existing tests. All CLI
output now routes through a single canonical &lt;code dir=&quot;auto&quot;&gt;CliConsole&lt;/code&gt; seam
(&lt;code dir=&quot;auto&quot;&gt;specify_cli.cli.console&lt;/code&gt;) whose machine-output methods (&lt;code dir=&quot;auto&quot;&gt;emit_json&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;print_json&lt;/code&gt;) are
plain by construction, so &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; is safe under any colour environment. Test determinism
comes from toggling colour on that one shared object (&lt;code dir=&quot;auto&quot;&gt;set_plain&lt;/code&gt;), never from mutating
&lt;code dir=&quot;auto&quot;&gt;os.environ&lt;/code&gt;. The whole CLI layer (~77 ad-hoc &lt;code dir=&quot;auto&quot;&gt;Console()&lt;/code&gt; constructions) was moved onto the
seam - no shim - and an architectural guard forbids a raw &lt;code dir=&quot;auto&quot;&gt;Console()&lt;/code&gt; under
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/&lt;/code&gt;. Deferred non-CLI consoles (including an active &lt;code dir=&quot;auto&quot;&gt;retrospective/cli.py&lt;/code&gt;
&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; corruption vector) are tracked in #2634. ADR: &lt;code dir=&quot;auto&quot;&gt;2026-07-14-1-canonical-cli-console-seam&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Implement-loop friction quick-wins II (#2570, #2493, #2555, #2566, #2589, #2533, #2580).&lt;/strong&gt;
Eight fixes that make lifecycle guards no-op-stable against their own runtime writes and the
pre-review gate return real verdicts, each preserving the guard’s true-positive:
the lane allocator ignores the &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;base_*&lt;/code&gt; WP frontmatter it just wrote (batch lane
allocation needs no inter-commit); the analysis-report freshness check ignores pipe-table
&lt;code dir=&quot;auto&quot;&gt;[D]&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;[P]&lt;/code&gt; status-marker churn from &lt;code dir=&quot;auto&quot;&gt;mark-status&lt;/code&gt;; the pre-review gate resolves &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt; via
&lt;code dir=&quot;auto&quot;&gt;uv run&lt;/code&gt; (a real verdict instead of a spurious &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; on a green tree) and serializes
concurrent runs behind a machine-wide lock whose acquire-timeout is decoupled from the run
timeout; the &lt;code dir=&quot;auto&quot;&gt;agent_profiles&lt;/code&gt; manifest stores &lt;code dir=&quot;auto&quot;&gt;output_path&lt;/code&gt; repo-relative so &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; is cross-machine deterministic; the issue-matrix approval error names the offending
schema-drift column instead of a misleading “Missing rows”; bulk-edit inference no longer
trips on ordinary refactor verbs while genuine bulk edits still trip; &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;’s first
scaffold write returns &lt;code dir=&quot;auto&quot;&gt;success&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;scaffold_only&lt;/code&gt; (mirroring the specify twin) instead of
reading as &lt;code dir=&quot;auto&quot;&gt;blocked&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; routes coord-lane planning-artifact staging through the
commit-router authority path (no lane &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; commit, STATUS_STATE placement
byte-unchanged) and closes the 4th divergent &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt; writer; and a solo PR-bound coord
mission routes its empty-coord status surface cleanly to primary instead of tripping a
split-brain warning. Successor to the loop-friction fast-follow; follow-ups filed for the
topology-derivation revisit (#2602), de-god debt (#2603, #2604), the &lt;code dir=&quot;auto&quot;&gt;implement --json&lt;/code&gt;
output contract (#2605), and worktree-aware &lt;code dir=&quot;auto&quot;&gt;doctor tool-surfaces --fix&lt;/code&gt; (#2613).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Implement-loop friction quick-wins (#2581, #2573, #2549, #2577).&lt;/strong&gt; Four independent
loop-friction fixes: &lt;code dir=&quot;auto&quot;&gt;mission create&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;spec-kitty specify&lt;/code&gt; now derive the create-time
topology from context - a non-primary feature branch without &lt;code dir=&quot;auto&quot;&gt;--pr-bound&lt;/code&gt; defaults to
&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt; instead of minting a coordination branch the operator must manually flatten
(primary branch, &lt;code dir=&quot;auto&quot;&gt;--pr-bound&lt;/code&gt;, and explicit &lt;code dir=&quot;auto&quot;&gt;--topology&lt;/code&gt; still default to &lt;code dir=&quot;auto&quot;&gt;coord&lt;/code&gt;);
&lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; gains a &lt;code dir=&quot;auto&quot;&gt;--skip-pre-review-gate&lt;/code&gt; flag, honors the
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SYNC_DISABLE&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SYNC_MINIMAL_IMPORT&lt;/code&gt; disable env, and surfaces a
progress notice so the scoped-test gate no longer reads as a hang (the full async redesign
stays deferred on #2573); &lt;code dir=&quot;auto&quot;&gt;finalize-tasks --json&lt;/code&gt; reports per-branch commit hashes
(&lt;code dir=&quot;auto&quot;&gt;commit_hashes&lt;/code&gt;) for the two-branch coord-topology commit set instead of a single
&lt;code dir=&quot;auto&quot;&gt;commit_hash&lt;/code&gt; that omitted the coordination-branch commit (#2549 facet B; facet A deferred);
and &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; no longer fails closed on an empty/first-run config demanding a
companion tactic for every built-in directive - first-run parity restored (#2526 regression).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coord-shadows follow-ups: canonical-source consolidation + gate/liveness robustness
(#2574, #2575, #2576, #2567, #2568).&lt;/strong&gt; The triplicated subtask-gate-dir resolver is unified
onto one &lt;code dir=&quot;auto&quot;&gt;resolve_subtasks_gate_dir&lt;/code&gt; seam with the strong git-ancestry fallback (the weak
&lt;code dir=&quot;auto&quot;&gt;status_transition&lt;/code&gt; site no longer reads a stale coordination husk); &lt;code dir=&quot;auto&quot;&gt;core/process_liveness&lt;/code&gt;
guards against PID reuse via a persisted creation-time baseline co-written at every claim site
(a recycled PID no longer reads as a live claim); the rollback-uncheck write routes through the
house path-guard and surfaces failures instead of silently leaving checked rows; the acceptance
gate’s stray checkbox parser is migrated onto the canonical &lt;code dir=&quot;auto&quot;&gt;core/subtask_rows&lt;/code&gt;; and the review
lock folds onto the canonical &lt;code dir=&quot;auto&quot;&gt;is_process_alive&lt;/code&gt; (last stray &lt;code dir=&quot;auto&quot;&gt;os.kill&lt;/code&gt; liveness probe removed).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coord-shadows-primary read/gate arm closed (#2502, #2504, #2510, #2512, #2513, #1231).&lt;/strong&gt;
The &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; subtask gate no longer fails open: &lt;code dir=&quot;auto&quot;&gt;_infer_subtasks_complete&lt;/code&gt; reads the
PRIMARY planning surface at every emit-layer caller and blocks on unchecked rows on both the
native &lt;code dir=&quot;auto&quot;&gt;agent status&lt;/code&gt; and orchestrator-api paths (the redundant #2511 per-door pre-derivation
is retired). A single canonical &lt;code dir=&quot;auto&quot;&gt;core/subtask_rows._walk_wp_section&lt;/code&gt; now defines a WP subtask
row for the guard, the dashboard count, and rollback-uncheck (the writer no longer re-enters a
re-appearing &lt;code dir=&quot;auto&quot;&gt;## WPnn&lt;/code&gt; heading). A recovered coordination-topology lane re-registers its
sparse-checkout and leaks no &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;. Process liveness is promoted
to &lt;code dir=&quot;auto&quot;&gt;core/process_liveness.is_process_alive&lt;/code&gt; (with a &lt;code dir=&quot;auto&quot;&gt;sync/daemon&lt;/code&gt; re-export alias) so the
stale-WP indicator suppresses false-stale for a live claim. Freshness-hash checkbox-insensitivity
(#1764) is pinned by a regression guard; #1862 is verified-already-fixed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Arch-suite warnings remediated at root (#2553, #2554).&lt;/strong&gt; Report-only diagnostics
(migration patch-skips, duplicate-gate selection, ratchet shrinkage, legacy-contract
backfill) are routed off the &lt;code dir=&quot;auto&quot;&gt;warnings&lt;/code&gt; channel via &lt;code dir=&quot;auto&quot;&gt;record_property&lt;/code&gt; (signal
preserved, no blanket &lt;code dir=&quot;auto&quot;&gt;filterwarnings=ignore&lt;/code&gt;); a Toolguide model-vs-schema drift is
fixed so &lt;code dir=&quot;auto&quot;&gt;terminology-guard.toolguide.yaml&lt;/code&gt; validates (clearing the &lt;code dir=&quot;auto&quot;&gt;base.py&lt;/code&gt; skip
warning); and three agent profiles now cite &lt;code dir=&quot;auto&quot;&gt;bdd-scenario-lifecycle&lt;/code&gt; as a &lt;em&gt;procedure&lt;/em&gt;
rather than a tactic (clearing &lt;code dir=&quot;auto&quot;&gt;CharterCatalogMissWarning&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coord-authority &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; misfired on a coordination-husk identity read
(#2508).&lt;/strong&gt; Identity-meta was read off the coordination husk rather than the primary
checkout, so &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; could target the wrong tree; the read now anchors on the
primary checkout (&lt;code dir=&quot;auto&quot;&gt;_load_coord_branch_meta&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_commit_workflow_change&lt;/code&gt;). Pinned
red-first by a dedicated regression that fails against the pre-fix code.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;orchestrator-api &lt;code dir=&quot;auto&quot;&gt;transition&lt;/code&gt; no longer lets WPs into &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; with
unchecked subtasks (#2510).&lt;/strong&gt; The command trusted a caller-asserted
&lt;code dir=&quot;auto&quot;&gt;--subtasks-complete&lt;/code&gt;; left unset, emit-time inference read &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; off
the STATUS feature dir - the coordination worktree husk mid-mission, where
the PRIMARY-partition &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; never exists - and &lt;strong&gt;failed open&lt;/strong&gt;,
silently bypassing the subtask guard native &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt; enforces (field
evidence: four WPs reached &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; with 0/16 rows ticked, &lt;code dir=&quot;auto&quot;&gt;force=false&lt;/code&gt;).
Mirroring the command’s own commit-gate precedent, the API now derives the
value server-side from the PRIMARY planning surface when the caller doesn’t
assert it; explicit assertions keep working and &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; keeps its bypass.
Fifth member of the coord-shadows-primary class
(#2331/#2430/#2502/#2508).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dashboard artifact viewers no longer render empty for in-flight
coordination missions (#2502).&lt;/strong&gt; #2431 re-anchored the mission &lt;em&gt;list&lt;/em&gt; and
&lt;em&gt;kanban&lt;/em&gt; to read planning artifacts primary-first, but the viewer endpoint
family (&lt;code dir=&quot;auto&quot;&gt;/api/research&lt;/code&gt;, contracts/checklists listings, the spec/plan file
server) still resolved the feature dir through the coord-first resolver -
landing on the status-only coord husk, so clicking spec/plan/research on a
running mission showed nothing while the board showed the work. A new
&lt;code dir=&quot;auto&quot;&gt;resolve_feature_planning_dir()&lt;/code&gt; composes the coord-first resolver with the
primary-first planning re-anchor; all viewer endpoints use it, and
&lt;code dir=&quot;auto&quot;&gt;handle_kanban&lt;/code&gt;’s split reads are made explicit (legacy-format check =
planning surface; weighted-progress read stays on the coord-first status
surface). Finished missions were unaffected (their coord worktrees are
gone), which is why the gap only showed mid-run - the same “broken precisely
while running” shape as #2430.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Agent context payloads no longer lose their &lt;code dir=&quot;auto&quot;&gt;Profile-Cited Directives&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;Tactics&lt;/code&gt; anchors when the token budget trims a section (mission
&lt;code dir=&quot;auto&quot;&gt;charter-sole-door-bypass-closure&lt;/code&gt;).&lt;/strong&gt; When the token-budget algorithm
substituted a section for a shorter fetch-command stanza, it deleted the
section’s own header line along with its body - so a governance payload
that ran over budget could silently lose the
&lt;code dir=&quot;auto&quot;&gt;Profile-Cited Directives (&amp;#x3C;profile&gt;):&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;Tactics:&lt;/code&gt; anchors an agent
reading the payload needs to find the section it wants. The budget
algorithm now keeps each populated kind’s header intact and swaps out only
its body.&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 tasks status&lt;/code&gt; no longer silently degrades the board on
a malformed &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; (mission
&lt;code dir=&quot;auto&quot;&gt;charter-sole-door-bypass-closure&lt;/code&gt;).&lt;/strong&gt; Previously, a broken activation
config (for example, &lt;code dir=&quot;auto&quot;&gt;activated_agent_profiles&lt;/code&gt; set to something other
than a list) was swallowed by a blanket exception handler, and the
command rendered a status board with no human-in-charge marker and no
indication anything was wrong. It now surfaces the underlying
&lt;code dir=&quot;auto&quot;&gt;CharterPackConfigError&lt;/code&gt; as a structured error instead of degrading
silently - you’ll notice this as a new, explicit failure where the
command previously ran quietly with missing markers.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bump &lt;code dir=&quot;auto&quot;&gt;cryptography&lt;/code&gt; floor to &lt;code dir=&quot;auto&quot;&gt;&gt;=50.0.0&lt;/code&gt;, fixing CVE-2026-69247 (&lt;code dir=&quot;auto&quot;&gt;#3181&lt;/code&gt;).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;cryptography&lt;/code&gt; is the dependency behind AES-256-GCM + scrypt KDF encrypted
auth session storage; the previously locked &lt;code dir=&quot;auto&quot;&gt;49.0.0&lt;/code&gt; was affected. There is
no user-facing behavior change - encrypted session storage keeps working
exactly as before, just on a patched dependency version. Run
&lt;code dir=&quot;auto&quot;&gt;spec-kitty auth status&lt;/code&gt; after upgrading if you want to confirm your stored
session is still recognized; &lt;em&gt;no re-login is required&lt;/em&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-changed-2&quot;&gt;♻️ Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The test suite is leaner and its CI ownership is explicit (mission
&lt;code dir=&quot;auto&quot;&gt;assertive-test-suite-sanitation&lt;/code&gt;).&lt;/strong&gt; Removed permanently inert tests,
dominated duplicates, historical shape/count pins, stale scaffolds, and
non-causal structural scanners while preserving reviewed live-path and
planted-fault guards. The shared pytest environment now publishes a validated
staged build with lease heartbeats, eliminating the &lt;code dir=&quot;auto&quot;&gt;#3283&lt;/code&gt; sibling timeout
cascade. Regression remains a generic blocking marker route with honest
empty-set handling; quarantine remains an empty Tier-3 visibility route whose
owner manifest is checked against repository-wide marker discovery. The
original &lt;code dir=&quot;auto&quot;&gt;doctor restart-daemon&lt;/code&gt; NFR-002 ≤10-second shared-runner wall-clock
claim is explicitly retired; its controlled Linux lane now enforces
distinct-PID restart and healthy-control-plane behavior under bounded
operation timeouts. Hosted-macOS performance evidence is deferred to a
controlled developer/canary harness rather than shared-runner wall clock.
The integrated census records 36,013 nodes / 2,667 Python test files versus
the frozen 37,444 / 2,731 baseline, with every frozen candidate terminally
owned.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; module now has a curated, enforced public API surface, so
runtime code imports it through stable doors instead of reaching into its
internals (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-public-api-surface&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3179&lt;/code&gt;, closes the
runtime→doctrine half of &lt;code dir=&quot;auto&quot;&gt;#2986&lt;/code&gt;).&lt;/strong&gt; A new &lt;code dir=&quot;auto&quot;&gt;doctrine.api&lt;/code&gt; manifest names the
symbols the future &lt;code dir=&quot;auto&quot;&gt;spec-kitty-doctrine&lt;/code&gt; wheel will export, the &lt;code dir=&quot;auto&quot;&gt;charter.*&lt;/code&gt;
facades re-export them by object identity, and ~34 &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; modules move
off direct &lt;code dir=&quot;auto&quot;&gt;doctrine.*&lt;/code&gt; imports onto those facades. A lazy-import ratchet plus a
source-side laundering guard keep new reach-through from creeping back in. This
is an internal architecture boundary only — no CLI command, output, or runtime
behavior changes — and it unblocks the &lt;code dir=&quot;auto&quot;&gt;#3101&lt;/code&gt; doctrine wheel cutover.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The contributor planning surface (&lt;code dir=&quot;auto&quot;&gt;docs/plans/&lt;/code&gt;) gains durable, version-spanning
&lt;em&gt;domain plans&lt;/em&gt; and a curated index (&lt;code dir=&quot;auto&quot;&gt;#3324&lt;/code&gt;).&lt;/strong&gt; Two domain throughlines — SaaS &amp;#x26; hosted sync,
and doctrine &amp;#x26; charter — now hold the standing strategy and invariants for their
surface across releases, distinct from the release-scoped &lt;code dir=&quot;auto&quot;&gt;3.2.x&lt;/code&gt; plans that retire
once distilled. The plans index is reorganized into domain throughlines, portfolio &amp;#x26;
milestone planning, and a single working-collections list; loose top-level notes are
filed into their subject subdirectories; and subdirectory landing files are
standardized on &lt;code dir=&quot;auto&quot;&gt;index.md&lt;/code&gt;. This is an internal contributor-facing change — the CLI
and templates are unaffected.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The beginner guides now open with illustrated Mission Kitty splashes, and the
Spec-Driven Development page carries a real diagram instead of ASCII art
(&lt;code dir=&quot;auto&quot;&gt;#3276&lt;/code&gt;).&lt;/strong&gt; Getting Started, Understanding Missions, Your First Mission, and
When to use Spec Kitty modes each gain a hero illustration; When to use modes
adds a four-path comparison board; and the SDD workflow — previously a plain
ASCII box diagram — is now a styled SVG flowchart that renders cleanly in light
and dark mode. The guide prose also switches to native DocFX alerts
(&lt;code dir=&quot;auto&quot;&gt;&gt; [!NOTE]&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;&gt; [!TIP]&lt;/code&gt;) so callouts stand out on the published site. Where a
stylized splash shows a workflow-like board, a one-line caption points to the
authoritative steps, modes, or mission types on the same page, so the artwork
reads as illustration and the page text stays the source of truth. The written
content and structure are unchanged; the pages are just easier to scan.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Spec Kitty’s documentation now lives under one predictable &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; root with
canonical sections, so you can find a page by where it logically belongs
(mission &lt;code dir=&quot;auto&quot;&gt;common-docs-convergence&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#2215&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#2887&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3273&lt;/code&gt;).&lt;/strong&gt; The scattered
root folders (&lt;code dir=&quot;auto&quot;&gt;research/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;examples/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;glossary/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;media/&lt;/code&gt;) and the duplicate
&lt;code dir=&quot;auto&quot;&gt;reference/&lt;/code&gt; vs &lt;code dir=&quot;auto&quot;&gt;api/&lt;/code&gt; split are gone. How-tos are now organised by audience —
user how-tos under &lt;code dir=&quot;auto&quot;&gt;guides/&lt;/code&gt;, contributor how-tos under &lt;code dir=&quot;auto&quot;&gt;development/&lt;/code&gt; — each
subdivided by concern behind a single landing page, so you reach what you need
in fewer clicks. Old documentation URLs redirect to their new homes, so existing
links and bookmarks keep working. Every page now declares its intended reader
and Divio type, and the architecture docs present one living design with prior
versions filed as ADRs.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dead queue-backed event-drain code removed from &lt;code dir=&quot;auto&quot;&gt;sync/batch.py&lt;/code&gt;, closing a
latent consent-bypass path (mission &lt;code dir=&quot;auto&quot;&gt;chain-b-consent-bypass-3167&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3167&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;#3190&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3187&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3220&lt;/code&gt;).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;batch_sync&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;sync_all_queued_events&lt;/code&gt; had no
production caller - the journal dispatcher remains the only event drain Spec
Kitty actually uses - but if either were ever reconnected, they could send a
project’s events without checking that project’s consent first. Both are
deleted, along with 31 supporting symbols and 91 test nodes that existed only
to serve them, and the now-inert &lt;code dir=&quot;auto&quot;&gt;E15&lt;/code&gt; egress-allowlist entry is removed. A
&lt;code dir=&quot;auto&quot;&gt;tests/sync&lt;/code&gt; autouse fixture that had been silently granting “consent” to
almost every test in the folder - which is why this gate went uncovered for
as long as it did - no longer patches the removed seam. No behaviour changes
for existing projects.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Doctrine-pack resolution and charter activation now run through a single
authority (mission &lt;code dir=&quot;auto&quot;&gt;resolution-activation-foundation&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#2657&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;#3210&lt;/code&gt;).&lt;/strong&gt;
One kernel primitive resolves the packs root and honours
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_PACKS_ROOT&lt;/code&gt; for every reader - the duplicate runtime &lt;code dir=&quot;auto&quot;&gt;home.py&lt;/code&gt;
resolver is collapsed onto it - so resolution can no longer diverge between
call sites. Fresh &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; provisions the default charter by
deterministic copy instead of re-scanning, so a freshly initialised project
and a migrated one start from an identical charter. The provisioned charter
is the sole authority for what is activated, and an unresolved mission-type
now fails closed at the create/use boundary instead of resolving implicitly.
Existing projects need no action.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The event log is now the single authority for a work package’s review
verdict; the review-cycle &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt; no longer carries one (mission
&lt;code dir=&quot;auto&quot;&gt;verdict-seam-write-unification-01KZ9Q35&lt;/code&gt;).&lt;/strong&gt; Every verdict reader and merge/
review gate resolves the event-sourced &lt;code dir=&quot;auto&quot;&gt;review_result&lt;/code&gt; slot in
&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;; the &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt; frontmatter &lt;code dir=&quot;auto&quot;&gt;verdict&lt;/code&gt; field is
retired, and durability moved to the event log (the &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt; write is now
best-effort). To keep existing projects safe across this reader collapse, a
new auto-discovered upgrade migration (&lt;code dir=&quot;auto&quot;&gt;verdict_provenance_backfill&lt;/code&gt;) runs on
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; and backfills each mission’s stranded terminal &lt;code dir=&quot;auto&quot;&gt;.md&lt;/code&gt;
verdict into the event log (FR-012/SC-008); it is idempotent (keyed on a
deterministic ULID) so re-running &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt; is safe. &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt;
carries a non-blocking diagnostic that names any still-stranded WP and points
at &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;. Runbook:
&lt;a href=&quot;/migrations/verdict-provenance-backfill/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/migrations/verdict-provenance-backfill.md&lt;/code&gt;&lt;/a&gt;.
&lt;em&gt;No &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;__init__.py&lt;/code&gt; version bump accompanies this entry: the
mission changed only the &lt;code dir=&quot;auto&quot;&gt;status/__init__.py&lt;/code&gt; facade, not the CLI entry
point, so a CHANGELOG entry without a version bump is correct here.&lt;/em&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Built-in mission data now ships under &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/&lt;/code&gt;, alongside
every other built-in doctrine kind (mission
&lt;code dir=&quot;auto&quot;&gt;doctrine-consumer-surface-missions-extraction&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3091&lt;/code&gt;).&lt;/strong&gt; The mission-type
profiles, step prompts, step contracts, and per-type content that previously
lived embedded in the &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; Python package at &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/&lt;/code&gt;
now resolve from the shippable &lt;code dir=&quot;auto&quot;&gt;packs/built-in/missions/&lt;/code&gt; location; the 11
&lt;code dir=&quot;auto&quot;&gt;.py&lt;/code&gt; logic modules stay in place as an ordinary package. Every reader -
across kernel, doctrine, charter, &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;, and the upgrade migrations -
was repointed in one atomic change, and mission-asset resolution now targets
the pack location explicitly so it can no longer silently fall back to the
(now data-less) package directory in a built/wheel layout. No user action is
required: &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; and mission resolution behave exactly as before,
and the regenerated DRG graph fragments are byte-identical.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission-asset resolution is now a single doctrine-agnostic kernel primitive
(mission &lt;code dir=&quot;auto&quot;&gt;doctrine-consumer-surface-missions-extraction&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3091&lt;/code&gt;).&lt;/strong&gt; The
kernel’s built-in-content lookup no longer hard-codes the &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; package
name or mission-type vocabulary; &lt;code dir=&quot;auto&quot;&gt;doctrine/pack_paths.py&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;MissionTemplateRepository.default_missions_root()&lt;/code&gt; converge onto that one
primitive, guarded by a kernel-scoped architectural test that fails on any
reintroduced &lt;code dir=&quot;auto&quot;&gt;kernel -&gt; doctrine&lt;/code&gt; edge.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Retrospective policy set in &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; now takes precedence over
&lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; frontmatter (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-charter-split-unification&lt;/code&gt;).&lt;/strong&gt;
If both files configure retrospective behaviour and they disagree, the
compiled &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; value now wins - matching how every other
charter-governed decision already resolves. Projects that configure
retrospective policy only via &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; frontmatter (no &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;
retrospective block) are unaffected and keep resolving from the markdown as
before.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Internal: doctrine/charter changes now get a dedicated, path-filtered CI
workflow (mission &lt;code dir=&quot;auto&quot;&gt;charter-pack-usage-journey&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#3102&lt;/code&gt;).&lt;/strong&gt; A PR that touches
only &lt;code dir=&quot;auto&quot;&gt;src/doctrine/**&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;src/charter/**&lt;/code&gt; (or touches neither) now runs the
DRG-freshness, charter-context-resolution, and architectural/adversarial
checks for that layer in an isolated workflow instead of paying for the full
suite - faster, more targeted feedback for doctrine/charter work, no change
for unrelated PRs. The &lt;code dir=&quot;auto&quot;&gt;charter pack apply&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; two-step and
the empty-charter dispatch-safety-net behaviour are also now documented in
the charter journey guides (&lt;code dir=&quot;auto&quot;&gt;#3107&lt;/code&gt;).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The &lt;code dir=&quot;auto&quot;&gt;charter/context.py&lt;/code&gt; god-module was decomposed 3243 -&gt; 570 lines (mission
&lt;code dir=&quot;auto&quot;&gt;charter-delivery-finish-context-degod&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;#2532&lt;/code&gt;).&lt;/strong&gt; The charter-context
engine - previously a single 3243-line module - is now a thin orchestration
surface delegating to 16 focused sibling modules under &lt;code dir=&quot;auto&quot;&gt;src/charter/&lt;/code&gt;
(catalog diagnosis, token budget, artifact bodies, selection rendering,
activation, bootstrap text, compact governance, JSON builder, profile
resolution, doctrine-service builder, …), and a long-standing internal import
cycle is dissolved. This is a pure maintainability change: a byte-for-byte
parity fixture over the three public entry points (&lt;code dir=&quot;auto&quot;&gt;build_charter_context&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;_include&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_json&lt;/code&gt;) is green before and after, and a completion gate asserts
each seam is really used. No behaviour or output changes.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Glossary-term casing gate is prose-only; the baseline ratchet is retired (#2830, #2823).&lt;/strong&gt;
All pre-existing non-canonical glossary-term casing across &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; prose was paid down and the
frozen baseline (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/glossary_canonical_terms_baseline.txt&lt;/code&gt;) deleted, so
&lt;code dir=&quot;auto&quot;&gt;test_glossary_canonical_terms.py&lt;/code&gt; now enforces &lt;strong&gt;zero&lt;/strong&gt; non-canonical occurrences in scanned
prose instead of freezing an escape hatch. The gate skips fenced code blocks and inline-code
spans (captured CLI &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; output and emitted-string literals keep their real casing) and
exempts the historical &lt;code dir=&quot;auto&quot;&gt;docs/adr/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;docs/changelog/&lt;/code&gt; trees. Also refreshes the &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt;
Canonical Kind Vocabulary table: charter-activatable tokens now list &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; (not
&lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt;) and add &lt;code dir=&quot;auto&quot;&gt;glossary-pack&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;template&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;asset&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;anti_pattern&lt;/code&gt; remain
&lt;code dir=&quot;auto&quot;&gt;ArtifactKind&lt;/code&gt; members but are &lt;strong&gt;not&lt;/strong&gt; charter-activatable (excluded via
&lt;code dir=&quot;auto&quot;&gt;_NON_AUGMENTATION_ELIGIBLE_KINDS&lt;/code&gt; - this is a governance clarification, not a kind
rename). Retires the Contextive generated-file staleness test.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The docs anti-sprawl structure ratchet (R1) is retired (#2851 follow-up).&lt;/strong&gt; The per-PR
blocking &lt;code dir=&quot;auto&quot;&gt;anti_sprawl_ratchet.py --strict&lt;/code&gt; step is removed from &lt;code dir=&quot;auto&quot;&gt;docs-freshness.yml&lt;/code&gt;, and
the script plus its orphaned &lt;code dir=&quot;auto&quot;&gt;doctrine.directives.common_docs&lt;/code&gt; constant (its only consumer)
and self-test are deleted. &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_042&lt;/code&gt;’s single-root / 13-section / no-shadow-tree policy
is unchanged - it remains a red-line integrity rule - but is now maintained by periodic bulk
curation rather than a per-PR CI gate, matching the operator’s bulk-remediation ops intent and
trimming a blocking CI step. The other docs rulers (R2 related-edge validator, R3 lockfile
freshness, description-length and body-link gates) are unaffected and stay blocking.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Runtime-state corpus cutover completed; the phase-1 dual-write flag is deleted (#2816, #2848).&lt;/strong&gt;
Completes the #2684 / #2093 eviction. WP runtime state - lane, claim, &lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;assignee&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt;, subtask completion, &lt;code dir=&quot;auto&quot;&gt;tracker_refs&lt;/code&gt;, review-cycle fields, and resolved
role/profile/model bindings - is now &lt;strong&gt;unconditionally&lt;/strong&gt; reconstructed from the append-only
event log through a single reader (&lt;code dir=&quot;auto&quot;&gt;reconstruct_wp_view&lt;/code&gt;); the &lt;code dir=&quot;auto&quot;&gt;_phase1_dual_write_enabled&lt;/code&gt;
flag and the legacy frontmatter-runtime fallback are removed, so &lt;code dir=&quot;auto&quot;&gt;tasks/WP##.md&lt;/code&gt; frontmatter
is no longer a runtime authority. The existing corpus was migrated (per-mission &lt;code dir=&quot;auto&quot;&gt;backfill -&gt; verify -&gt; status_phase&lt;/code&gt; flip). Adds &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-runtime-state&lt;/code&gt;&lt;/strong&gt;, which
seeds a mission’s legacy runtime as events, verifies the reduced snapshot against the old
reader by count + value (fail-closed - never flips a mission that fails verify; per-mission
best-effort), and flips &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;status_phase&lt;/code&gt; to snapshot-authority only for verified
missions; the same seed-&gt;verify-&gt;flip path ships as an auto-discovered upgrade migration for
consumer repos.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Skill projection delivers copies, never absolute symlinks (#2412, ADR 2026-07-19-1).&lt;/strong&gt;
Projected skill files under &lt;code dir=&quot;auto&quot;&gt;.claude/skills/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt;, etc. used to be
absolute symlinks into the user-global canonical root - which dangle when the repo
is mounted into a dev-container or synced to a remote box, are unreadable to agent
harnesses sandboxed to the repo root, and all break at once if the global root
moves. &lt;code dir=&quot;auto&quot;&gt;_project_skill_file&lt;/code&gt; now always delivers a real copy (the pre-existing
Windows fallback path, promoted): hash-equal destinations are left untouched
(idempotent re-runs), legacy symlinks are replaced with copies organically on each
project’s next init/upgrade/repair run (no migration needed), and &lt;code dir=&quot;auto&quot;&gt;repair_skills&lt;/code&gt;
always repairs to a copy, healing pre-existing &lt;code dir=&quot;auto&quot;&gt;delivery_mode: symlink&lt;/code&gt; manifest
entries as it goes. Freshness is preserved because every install run re-projects
the full skill set; copies inherit the canonical root’s read-only mode. Supersedes
the per-project-symlink half of ADR 2026-04-08-3 (the global canonical root is
unchanged).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; seeds a starter &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; companion when absent (#2800).&lt;/strong&gt;
After the #2773 inversion &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; produced no &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; at all, leaving a
fresh project without the display-only rationale companion and no signal one should exist.
&lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt; now writes a minimal starter &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; &lt;strong&gt;only when the file is absent&lt;/strong&gt;
(create-if-absent); an existing curated companion is left byte-for-byte untouched,
preserving the #2772 never-clobber invariant. &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; remains display-only, never a
resolving input. ADR 2026-07-18-1 amended.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Internal: the &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; aware-UTC clock contract is now enforced structurally
(#2496).&lt;/strong&gt; Follow-up to #2494’s clock-consolidation sweep. Routes the remaining
byte-identical &lt;code dir=&quot;auto&quot;&gt;datetime.now(UTC).isoformat()&lt;/code&gt; “now”-stamp call sites in &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;
onto the single canonical &lt;code dir=&quot;auto&quot;&gt;now_utc_iso()&lt;/code&gt; helper, the canonical producer of that form.
Behaviour-preserving: the &lt;code dir=&quot;auto&quot;&gt;UTC&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;timezone.utc&lt;/code&gt; spellings serialize byte-identically
under &lt;code dir=&quot;auto&quot;&gt;requires-python &gt;=3.11&lt;/code&gt;. Adds an &lt;strong&gt;AST negative gate&lt;/strong&gt; over the whole
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli&lt;/code&gt; tree (&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/test_clock_consolidation.py&lt;/code&gt;), alongside
the pre-existing owned-file inventory, so a module added later is covered the moment it
lands rather than silently regressing while the suite stays green; the gate ships a
self-mutant non-vacuity test and a stale-exemption check. It targets the fluent
single-expression &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;x&gt;.now(&amp;#x3C;aware-UTC&gt;).isoformat()&lt;/code&gt; idiom (import aliases resolved);
distinct contracts are deliberately out of scope and not flagged: the second-precision
&lt;code dir=&quot;auto&quot;&gt;%Y-%m-%dT%H:%M:%SZ&lt;/code&gt; stamp family, &lt;code dir=&quot;auto&quot;&gt;isoformat(timespec=...)&lt;/code&gt;, naive &lt;code dir=&quot;auto&quot;&gt;now()&lt;/code&gt;, the
datetime-returning family, and non-fluent forms (a variable-split or a space-separated
&lt;code dir=&quot;auto&quot;&gt;str()&lt;/code&gt; of an aware instant).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Internal: the coord-authority trio is decomposed into ports + pure cores
(#2464, #2465).&lt;/strong&gt; The three coord-authority god-modules are restructured
behaviour-preservingly into the shipped Typer-shell + request-dataclass + pure-cores
(ports injected) + executor pattern - following &lt;code dir=&quot;auto&quot;&gt;MissionResolver&lt;/code&gt; (#2494) and
&lt;code dir=&quot;auto&quot;&gt;tasks.py&lt;/code&gt; (#2308): &lt;code dir=&quot;auto&quot;&gt;workflow.py&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;workflow_cores.py&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;workflow_executor.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;implement.py&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;implement_cores.py&lt;/code&gt; (a &lt;code dir=&quot;auto&quot;&gt;GitPort&lt;/code&gt; injected and two &lt;code dir=&quot;auto&quot;&gt;# noqa: C901&lt;/code&gt;
suppressions removed), and &lt;code dir=&quot;auto&quot;&gt;acceptance/&lt;/code&gt; -&gt; &lt;code dir=&quot;auto&quot;&gt;summary_core.py&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;gates_core.py&lt;/code&gt;. The
trio’s leaf resolvers now consume the kind-aware placement seam, preserving all three
(lenient) read contracts (#2465). No user-facing behaviour change; pinned by
seam-only + cores-no-I/O architectural tests and a characterization safety net over
implement / review / accept / next.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Read-side placement seam closure: the last unpoliced primitive is gone
(#2886, #3014; closes the read-side placement-seam migration opened by
#2922/#2921).&lt;/strong&gt; The #2922 migration above left one gap on purpose - its own
gate coverage bounds named &lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt; as unpoliced,
because the wrapper itself, and the ~34 call sites still composing a
mission’s primary directory by calling it directly, hadn’t been routed
through the seam yet. They are now: every one of those call sites asks
&lt;code dir=&quot;auto&quot;&gt;placement_seam(root, slug).read_dir(&amp;#x3C;kind&gt;)&lt;/code&gt; for the artifact kind it
actually wants, instead of asking a topology-blind wrapper to guess a path
from a slug. The terminal &lt;code dir=&quot;auto&quot;&gt;KITTY_SPECS_DIR&lt;/code&gt; assembler survives as the
seam’s own module-private leaf - the one place still allowed to compose a
path, because something has to. One behavioural nuance was accepted rather
than papered over: on a backfilled mission where the old blind composition
returned a directory that does not exist, the seam now recovers the real
bare-&lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;&lt;/code&gt; directory instead of repeating the miss (identity-confirmed,
not just path-shaped). A new architecture reference,
&lt;a href=&quot;/architecture/artifact-placement-seam/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/architecture/artifact-placement-seam.md&lt;/code&gt;&lt;/a&gt;,
documents the L0-L4 read-placement layering end to end; &lt;code dir=&quot;auto&quot;&gt;branch-target-routing.md&lt;/code&gt;
is narrowed to the branch-target sense now that placement has its own home.
Governed by ADR
&lt;a href=&quot;/adr/3.x/2026-06-24-1-kind-and-topology-aware-artifact-placement/&quot;&gt;2026-06-24-1&lt;/a&gt;
and ADR
&lt;a href=&quot;/adr/3.x/2026-07-23-1-surface-vocabulary-two-domains-and-topology-surface-rename/&quot;&gt;2026-07-23-1&lt;/a&gt;;
no new architectural decision was needed.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Activating a subset of directives, tactics, styleguides, toolguides,
mission-step contracts, or glossary packs now actually narrows what your
project sees - it didn’t before (mission &lt;code dir=&quot;auto&quot;&gt;charter-sole-door-bypass-closure&lt;/code&gt;).&lt;/strong&gt;
If your &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt;/pack config selects only some of a pack’s
directives (or tactics, styleguides, toolguides, mission-step contracts,
glossary packs), the runtime, CLI, and rendered context now consistently
show only the selected set for those 6 kinds. Previously this filtering
only worked for &lt;code dir=&quot;auto&quot;&gt;paradigm&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;agent_profile&lt;/code&gt; - the other 6
kinds fell through unfiltered, so a deactivated pack could still show up.
Mission-type selection was already honoured before this mission; it is
now covered by regression tests confirming that. &lt;strong&gt;If you haven’t
configured any activation selection, nothing changes&lt;/strong&gt; - a
bare/unconfigured project’s result set is unaffected. One deliberate
exception: &lt;code dir=&quot;auto&quot;&gt;.kittify/profiles&lt;/code&gt; (a local-override directory outside the
doctrine activation model) is explicitly still unfiltered by this
change - a scope call, not a missed site; that area is slated for
separate future rework.&lt;/p&gt;
&lt;p&gt;Under the hood, this closes every &lt;strong&gt;enumerated direct-construction and
&lt;code dir=&quot;auto&quot;&gt;._inner&lt;/code&gt; bypass&lt;/strong&gt; around the charter’s &lt;code dir=&quot;auto&quot;&gt;DoctrineService&lt;/code&gt; factory and
extends activation gating from 3 kinds to all 9 charter-activatable kinds
plus the &lt;code dir=&quot;auto&quot;&gt;mission-type&lt;/code&gt; token. It does &lt;strong&gt;not&lt;/strong&gt; close the full ~20-door
list: &lt;code dir=&quot;auto&quot;&gt;doctrine.template_catalog.resolve_template_by_id&lt;/code&gt; (5 importers),
&lt;code dir=&quot;auto&quot;&gt;specify_cli/runtime/resolver.py&lt;/code&gt;’s tier-1-4 reimplementation,
&lt;code dir=&quot;auto&quot;&gt;runtime/home.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;importlib.resources&lt;/code&gt; root lookup, three
root-relative missions-root duplicates, and one escalated
&lt;code dir=&quot;auto&quot;&gt;AgentProfileRepository&lt;/code&gt; site (&lt;code dir=&quot;auto&quot;&gt;tool_surface/profiles/projection.py&lt;/code&gt;)
remain - each named in the mission spec and tracked as its own follow-on
(#3176 for the last). This mission also promotes
&lt;code dir=&quot;auto&quot;&gt;MissionTemplateRepository.default_missions_root()&lt;/code&gt; as the single shared
missions-root authority and retargets two duplicate hardcoded path
constructions onto it, but that consolidation does &lt;strong&gt;not&lt;/strong&gt; claim
convergence with &lt;code dir=&quot;auto&quot;&gt;doctrine.pack_paths.built_in_dir&lt;/code&gt; - full convergence
remains &lt;code dir=&quot;auto&quot;&gt;#3091&lt;/code&gt;’s to deliver.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;One more consumer-visible narrowing, for projects that declare
languages.&lt;/strong&gt; If your project’s compiled &lt;code dir=&quot;auto&quot;&gt;charter.yaml&lt;/code&gt; records a
&lt;code dir=&quot;auto&quot;&gt;catalog.languages&lt;/code&gt; answer (i.e. you already went through the charter
interview or &lt;code dir=&quot;auto&quot;&gt;charter sync&lt;/code&gt;), language-scoped agent profiles now filter
consistently through the factory - previously, one of the two
divergent builder paths this mission unifies did not apply that filter
at all, so a language-scoped profile could show up even for a language
your project doesn’t use. Measured on this repository’s own root
(&lt;code dir=&quot;auto&quot;&gt;catalog.languages: [python]&lt;/code&gt;): the built-in agent-profile catalog
narrows from 18 profiles to 15 - &lt;code dir=&quot;auto&quot;&gt;frontend-freddy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;java-jenny&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;node-norris&lt;/code&gt; no longer resolve, because they’re scoped to languages
this project doesn’t declare. &lt;code dir=&quot;auto&quot;&gt;python-pedro&lt;/code&gt; still resolves. This is
intended, not a regression (FR-008’s “fuller behaviour on each axis”):
if you relied on an off-language profile resolving anyway, activate it
explicitly rather than depending on the prior inconsistency. Projects
with no compiled &lt;code dir=&quot;auto&quot;&gt;languages&lt;/code&gt; answer are unaffected - see above.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-breaking-changes-1&quot;&gt;💥 Breaking Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Built-in doctrine content moved out of &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt; into a top-level
&lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; pack root (mission &lt;code dir=&quot;auto&quot;&gt;relocate-builtin-doctrine-packs&lt;/code&gt;).&lt;/strong&gt;
The shipped built-in artefact &lt;em&gt;data&lt;/em&gt; (directives, tactics, procedures,
paradigms, styleguides, toolguides, agent profiles, glossary packs, assets,
and the per-kind &lt;code dir=&quot;auto&quot;&gt;*.graph.yaml&lt;/code&gt; DRG fragments) no longer lives inside the
&lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; Python package. The layout is &lt;strong&gt;flattened&lt;/strong&gt;: the old
&lt;code dir=&quot;auto&quot;&gt;src/doctrine/&amp;#x3C;kind&gt;/built-in/&amp;#x3C;file&gt;&lt;/code&gt; home loses its inner &lt;code dir=&quot;auto&quot;&gt;built-in/&lt;/code&gt; segment
and becomes &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&amp;#x3C;kind&gt;/&amp;#x3C;file&gt;&lt;/code&gt;; the sharded fragments move from
&lt;code dir=&quot;auto&quot;&gt;src/doctrine/&amp;#x3C;kind&gt;.graph.yaml&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&amp;#x3C;kind&gt;.graph.yaml&lt;/code&gt;. All
three tiers now resolve the built-in root through a single fail-closed seam,
&lt;code dir=&quot;auto&quot;&gt;resolve_pack_root(&quot;built-in&quot;)&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/doctrine/pack_paths.py&lt;/code&gt;); the DRG seam
&lt;code dir=&quot;auto&quot;&gt;built_in_graph_source()&lt;/code&gt; yields the &lt;code dir=&quot;auto&quot;&gt;packs/built-in/&lt;/code&gt; directory. 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 the &lt;code dir=&quot;auto&quot;&gt;missions/&lt;/code&gt; tree do
&lt;strong&gt;not&lt;/strong&gt; move and remain under &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt;. There is &lt;strong&gt;no compatibility
shim&lt;/strong&gt; - repoint any reference to the new path (drop the inner &lt;code dir=&quot;auto&quot;&gt;built-in/&lt;/code&gt;).
The wheel/sdist ship &lt;code dir=&quot;auto&quot;&gt;packs/&lt;/code&gt; as a site-packages sibling of &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt;.
Follow-ons are tracked: Phase 1b relocates &lt;code dir=&quot;auto&quot;&gt;missions/&lt;/code&gt; (#3091); Phase 2
converges the built-in loader/schema onto the org-pack contract. See
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/blob/main/docs/migrations/relocate-builtin-doctrine-packs.md&quot;&gt;docs/migrations/relocate-builtin-doctrine-packs.md&lt;/a&gt;.&lt;/p&gt;
&lt;/li&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 now raises
&lt;code dir=&quot;auto&quot;&gt;ImportError&lt;/code&gt; (#2886, #3014).&lt;/strong&gt; It was the last kind-blind wrapper left over
from before the read-side placement seam (#2922): callers passed it a slug
and it guessed a mission’s primary directory by path composition, with no
artifact-kind awareness and no way to fail loud when the guess was wrong. The
invariant “reads go through the seam” is now structural rather than
counted - there is no bypass left to police, so the gate that used to name it
as an accepted gap has nothing left to accept. If you imported this function
directly (an internal API, but importable), 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
actually need; see the Changed entry above and
&lt;a href=&quot;/architecture/artifact-placement-seam/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/architecture/artifact-placement-seam.md&lt;/code&gt;&lt;/a&gt;
for the read-placement layering it now goes through.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;An org doctrine pack whose agent profile carries an unrecognised key now
fails to load (mission &lt;code dir=&quot;auto&quot;&gt;doctrine-silence-guards&lt;/code&gt;).&lt;/strong&gt; Agent profiles and DRG
nodes and edges used to accept keys the code did not know about and drop them,
so a typo or a key retired in an earlier release produced an artifact that
looked complete and behaved differently from how it read. Those keys are now
rejected outright. Silently dropping them is the defect being closed, so this
is deliberate - but &lt;strong&gt;if you maintain an org pack, check it before you
upgrade&lt;/strong&gt;: run &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor doctrine --json&lt;/code&gt; and read the
&lt;code dir=&quot;auto&quot;&gt;skipped_profiles&lt;/code&gt; list. A pack containing an invalid profile is reported
unhealthy rather than crashing the command or passing as healthy. The
blast-radius check for this change covered this repository only; packs outside
it were not surveyed.&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; An edge
endpoint in a pack’s &lt;code dir=&quot;auto&quot;&gt;drg/&lt;/code&gt; fragment is either &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 a bare id declared in that same fragment’s own
&lt;code dir=&quot;auto&quot;&gt;nodes:&lt;/code&gt; block. A bare id no longer resolves against a &lt;em&gt;different&lt;/em&gt; pack in the
same merge. That old behaviour made the resulting graph depend on the order
packs happen to be listed in &lt;code dir=&quot;auto&quot;&gt;organisation_packs:&lt;/code&gt;: the same two packs in two
orders produced two different graphs, and nothing was reported either way. An
endpoint that cannot be resolved is now refused at merge time with an
&lt;code dir=&quot;auto&quot;&gt;unresolved_edge_endpoint&lt;/code&gt; conflict naming the token, instead of being dropped
or silently re-pointed at an invented node. See
&lt;a href=&quot;/guides/how-to/governance/create-an-org-doctrine-pack/&quot;&gt;the org-pack authoring guide&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A push to a protected branch now starts 49 of 50 test jobs instead of about
10.&lt;/strong&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: filtering is a pull-request optimisation, and the protected branch
is precisely where the frozen contracts have to actually run. See the #2957
entry under Fixed.&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 fails when an org pack declares an edge
endpoint that resolves to nothing.&lt;/strong&gt; The dangling endpoints are listed in the
report and the command exits non-zero. &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 - it is a
reporting surface, not a gate, and scripts that treat its exit code as a pass
or fail signal 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, including from the default
charter pack - an upgrade migration cleans up projects that already have it
activated.&lt;/strong&gt; RTK is fiddly to set up correctly and can materially change how
a project’s tests execute, so shipping it as an artefact every new project
activates by default was a liability rather than a service. The toolguide,
its guide document, and its node in the doctrine graph are gone, and it no
longer appears in &lt;code dir=&quot;auto&quot;&gt;src/charter/packs/default.yaml&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;This is a breaking removal for existing projects because of how the entry got
there. The 3.2.0rc35 default-pack migration copied the pack’s
&lt;code dir=&quot;auto&quot;&gt;activated_toolguides&lt;/code&gt; list verbatim into each project’s
&lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;, and by design only ever writes keys that are
&lt;em&gt;absent&lt;/em&gt; - so no later upgrade would have taken a retired member back out.
Charter compilation is deliberately fail-closed and refuses to quietly skip a
reference it cannot resolve, so a project left holding the stale entry would
hard-fail on the next compile with &lt;code dir=&quot;auto&quot;&gt;UnknownArtifactIdError: No toolguide artifact with config ID &apos;rtk-search-tooling&apos; found&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;The new &lt;code dir=&quot;auto&quot;&gt;3.2.6_retire_rtk_search_tooling&lt;/code&gt; migration removes the entry from
&lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; and strips the matching compiled blocks from
&lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/references.yaml&lt;/code&gt;, which
would otherwise still name a source file that no longer exists. It runs
automatically on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;, does nothing on a project that never
had the entry, and is safe to run more than once. If you deliberately want
RTK guidance, keep it in your own org doctrine pack.&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, and absence of both channels denies (mission
&lt;code dir=&quot;auto&quot;&gt;tracker-egress-refusal-3108&lt;/code&gt;).&lt;/strong&gt; Every &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker 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; on a local binding used to ship issue titles, bodies,
labels, and assignees as &lt;code dir=&quot;auto&quot;&gt;argv&lt;/code&gt; of an operator-named executable
(&lt;code dir=&quot;auto&quot;&gt;tracker/factory.py&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;command&lt;/code&gt; key, defaulting to &lt;code dir=&quot;auto&quot;&gt;bd&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;) with no
consent check at all — a committed &lt;code dir=&quot;auto&quot;&gt;sync.enabled: false&lt;/code&gt; did not stop it.
It is now gated by a join of two independently-recorded consent channels:
&lt;strong&gt;Channel 1&lt;/strong&gt;, the existing hosted-sync consent chain (&lt;code dir=&quot;auto&quot;&gt;sync.enabled&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt;), and &lt;strong&gt;Channel 2&lt;/strong&gt;, a new &lt;code dir=&quot;auto&quot;&gt;tracker.egress&lt;/code&gt; key
(&lt;code dir=&quot;auto&quot;&gt;refused&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;permitted&lt;/code&gt;) in the project’s own committed
&lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;. At this destination Channel 2 is two-way: a
recorded &lt;code dir=&quot;auto&quot;&gt;permitted&lt;/code&gt; grants local sync independently of Channel 1, because
the subprocess involved is the operator’s own machine, never spec-kitty’s
hosted service; a recorded &lt;code dir=&quot;auto&quot;&gt;refused&lt;/code&gt;, or absence at &lt;em&gt;both&lt;/em&gt; channels,
denies. &lt;strong&gt;This is the breaking change:&lt;/strong&gt; an existing &lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt; binding
that has 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 until one of the two is recorded — record
&lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt; to keep syncing without consenting to hosted
sync at all, or run &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync opt-in&lt;/code&gt; / record &lt;code dir=&quot;auto&quot;&gt;sync.enabled: true&lt;/code&gt;
to consent to hosted sync instead. Absence denies by design, but the
two-way local grant is the deliberate escape from a coercion the old,
ungated behaviour otherwise implied: without it, “consent to hosted sync or
lose your local tracker” would be the only way to keep a &lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;
binding working, and recording &lt;code dir=&quot;auto&quot;&gt;tracker.egress: permitted&lt;/code&gt; is never a
de facto opt-in to hosted sync — it grants the local subprocess path only.
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;tracker 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;,
and &lt;code dir=&quot;auto&quot;&gt;map add&lt;/code&gt; stay available on a refusing project, and a local &lt;code dir=&quot;auto&quot;&gt;beads&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;fp&lt;/code&gt;
&lt;code dir=&quot;auto&quot;&gt;bind&lt;/code&gt; no longer needs hosted authentication to run — an unauthenticated
project can still bind and use a local tracker. The refusal is also raised
before any network probe, so a refused hosted sync makes no HTTP request to
the tracker host at all. See
&lt;a href=&quot;/migrations/tracker-egress-refusal/&quot;&gt;the upgrade note&lt;/a&gt; for the full
remediation paths.&lt;/p&gt;

&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;325---2026-07-08&quot;&gt;[3.2.5] - 2026-07-08&lt;/h2&gt;
&lt;h3 id=&quot;-added-3&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Coord/primary placement-partition lock - one topology-aware seam owns where
every mission artifact is stored and read (#1716, #1878/G2).&lt;/strong&gt; Formalizes
&lt;code dir=&quot;auto&quot;&gt;PlacementSeam.write_target(kind)&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;read_dir(kind)&lt;/code&gt; as the single thin
authority over the existing &lt;code dir=&quot;auto&quot;&gt;resolve_action_context&lt;/code&gt; SSOT and routes every
remaining write site through it - &lt;strong&gt;fail-closed&lt;/strong&gt; via &lt;code dir=&quot;auto&quot;&gt;PlacementResolutionRequired&lt;/code&gt;
(a real resolution failure raises rather than silently committing to the
operator’s checkout). An architectural ratchet forbids the
&lt;code dir=&quot;auto&quot;&gt;CommitTarget(ref=&amp;#x3C;checkout&gt;)&lt;/code&gt; grammar (a self-test proves it bites), and an
end-to-end characterization test locks the behaviour. Canonical partition:
coord branch = lifecycle (status/notes/trace/issue-matrix/move-task); primary
= stable planning (spec/plan/WP outlines); no-coordination topology → all
primary. RETROSPECTIVE delegates to the existing &lt;code dir=&quot;auto&quot;&gt;resolve_retrospective_home&lt;/code&gt;
(no second authority). Also &lt;strong&gt;fixes #2091&lt;/strong&gt; (an empty &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; no longer builds a
malformed &lt;code dir=&quot;auto&quot;&gt;kitty/mission-&amp;#x3C;slug&gt;-&lt;/code&gt; coordination branch → &lt;code dir=&quot;auto&quot;&gt;git worktree add&lt;/code&gt;
exit-128; the &lt;code dir=&quot;auto&quot;&gt;CoordinationWorkspace&lt;/code&gt; composition seam fail-loud-guards it) and
&lt;strong&gt;#2250&lt;/strong&gt; (a never-coordinated mission no longer reports
&lt;code dir=&quot;auto&quot;&gt;COORDINATION_BRANCH_DELETED&lt;/code&gt;). &lt;strong&gt;The read side is now locked too (#1716
closeout):&lt;/strong&gt; every remaining coordination-surface &lt;em&gt;read&lt;/em&gt; - the kind-blind
&lt;code dir=&quot;auto&quot;&gt;resolve_feature_dir_for_mission&lt;/code&gt; sweep (#2453) and the inline &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;
reads (#2100) - routes through the same topology-aware seam kind-correctly, so
&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; no longer reads a stale &lt;code dir=&quot;auto&quot;&gt;-coord&lt;/code&gt; acceptance matrix (#2404)
and planning artifacts always resolve to their canonical surface regardless of
the working directory. A non-vacuous architectural ratchet keeps the routed
read classes from silently regrowing. Closes epic &lt;strong&gt;#1716&lt;/strong&gt; and #2453 / #2100
/ #2088 / #2404.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Doctrine/charter pack paths support environment-variable indirection
(#2437).&lt;/strong&gt; Pack-location fields (e.g. an org-pack’s &lt;code dir=&quot;auto&quot;&gt;local_path&lt;/code&gt;) previously
had to be hardcoded absolute paths, so a shared, committed &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt; config
resolved only on the machine of the developer who wrote it and broke for every
teammate and CI runner. Pack-path templates now expand &lt;code dir=&quot;auto&quot;&gt;${VAR}&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;$VAR&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;~&lt;/code&gt;
at read time (via &lt;code dir=&quot;auto&quot;&gt;os.path.expandvars&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;expanduser&lt;/code&gt;), so a portable form
like &lt;code dir=&quot;auto&quot;&gt;${SPEC_KITTY_PACK_HOME}/acme-doctrine&lt;/code&gt; can be committed once and each
environment resolves it against its own base. Expansion is &lt;strong&gt;fail-closed&lt;/strong&gt;: an
unset/empty env token raises rather than silently collapsing to a wrong path
(e.g. &lt;code dir=&quot;auto&quot;&gt;${UNSET}/acme&lt;/code&gt; → repo root). Purely additive - literal absolute paths
keep working.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review-time regression gate at &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; (#572).&lt;/strong&gt; When a
work package moves to &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;, Spec Kitty now auto-scopes the CI shards
that cover the WP’s changed files and re-runs them, so a WP that broke a
shared contract pinned by a test &lt;em&gt;outside&lt;/em&gt; its &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt; is caught at
review time instead of only at merge. Warn-only by default; opt in to a hard
block with &lt;code dir=&quot;auto&quot;&gt;review.fail_on_pre_review_regression&lt;/code&gt; (enforced only when
&lt;code dir=&quot;auto&quot;&gt;review.test_command&lt;/code&gt; is set; &lt;code dir=&quot;auto&quot;&gt;move-task --force&lt;/code&gt; overrides), and override the
scope per-WP via frontmatter &lt;code dir=&quot;auto&quot;&gt;pre_review_test_scope&lt;/code&gt;. See
&lt;a href=&quot;/development/how-to/review-gates/&quot;&gt;review-gates.md&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty review --check-residual&lt;/code&gt; + environment-parity preflight
(#2283).&lt;/strong&gt; The new &lt;code dir=&quot;auto&quot;&gt;--check-residual&lt;/code&gt; flag runs CI’s always-on
&lt;code dir=&quot;auto&quot;&gt;unit-contract-residual&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;-m&lt;/code&gt; selection over &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt; locally - the &lt;code dir=&quot;auto&quot;&gt;-m&lt;/code&gt;
expression is read &lt;strong&gt;live&lt;/strong&gt; from &lt;code dir=&quot;auto&quot;&gt;.github/workflows/ci-quality.yml&lt;/code&gt;, so a
previously CI-only marker-orphan failure can be reproduced before pushing. The
&lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt; preflight also detects local-vs-CI environment skew
(installed package versions diverging from &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt;, plus typer/click
lock-parity), warning by default and failing closed under
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENV_SKEW_FAIL_CLOSED&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-3&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Post-merge stale-assertion analyzer stops false-positive storms on
behavior-preserving refactors (#2031, #2343).&lt;/strong&gt; A relocation/re-export (a
WP05 extraction produced 180 false findings and tripped the drift ceiling)
and generic-literal noise both flagged as stale assertions. The analyzer now
(a) suppresses a removed identifier only when the origin file’s &lt;strong&gt;module-level
head&lt;/strong&gt; still re-exports/imports it (keyed on head-importability - not
bare-name-anywhere, so a genuine deletion of a common name like &lt;code dir=&quot;auto&quot;&gt;run&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;
is still flagged; a nested &lt;code dir=&quot;auto&quot;&gt;import parse&lt;/code&gt; does not mask a real &lt;code dir=&quot;auto&quot;&gt;def parse()&lt;/code&gt;
deletion), and (b) suppresses literal-only noise by &lt;strong&gt;genuineness&lt;/strong&gt; (a pinned
generic-token set / all-punctuation), never by length (a short literal like
&lt;code dir=&quot;auto&quot;&gt;&quot;E001&quot;&lt;/code&gt; can be assert-critical). Both paths suppress rather than
info-downgrade, so render surfaces and the FP ceiling are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review-prompt files no longer accumulate unbounded; coverage-allowlist
repointed off a removed module (#2439, #2443).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;write_review_prompt_with_metadata()&lt;/code&gt; now prunes review-prompt files to a
newest-preserving cap after each write - fail-safe, and never pruning the
current invocation’s own file - closing the LC-7 retention residual of #1842.
Separately, the &lt;code dir=&quot;auto&quot;&gt;diff-coverage&lt;/code&gt; critical-path &lt;code dir=&quot;auto&quot;&gt;--include&lt;/code&gt; allowlist still
referenced the stale &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/mission_detection.py&lt;/code&gt; (removed in a
rename); it is repointed to &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/lanes/branch_naming.py&lt;/code&gt; in &lt;strong&gt;both&lt;/strong&gt;
the CI workflow and its test authority in lockstep, with a glob-aware existence
guard so a phantom allowlist entry reds instead of silently covering nothing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission finalize-tasks&lt;/code&gt; accepts glob-only &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;
(#2446).&lt;/strong&gt; A work package whose &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt; used a filename glob (e.g.
&lt;code dir=&quot;auto&quot;&gt;src/foo/*.py&lt;/code&gt;) with no explicit &lt;code dir=&quot;auto&quot;&gt;authoritative_surface&lt;/code&gt; was rejected because
&lt;code dir=&quot;auto&quot;&gt;infer_authoritative_surface&lt;/code&gt; produced an invalid &lt;code dir=&quot;auto&quot;&gt;src/foo/*.py/&lt;/code&gt; path. It now
reduces a glob-bearing final path segment to its directory, so glob-only
ownership infers a valid authoritative surface. (Fix landing via PR #2454.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A retired skill’s projected files are now drained by surface repair instead
of orphaned forever (#2409).&lt;/strong&gt; When a skill was retired from the registry,
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --project&lt;/code&gt; could not reconcile its leftover projections:
the repair path warned &lt;code dir=&quot;auto&quot;&gt;Cannot repair … skill not found in registry&lt;/code&gt; on every
subsequent upgrade and left the files in place (committed, where the repo
tracks skill surfaces; a dangling symlink, where the global root had dropped
the skill). Repair now reconciles retirements &lt;strong&gt;manifest-driven&lt;/strong&gt;: entries in
&lt;code dir=&quot;auto&quot;&gt;.kittify/skills-manifest.json&lt;/code&gt; whose skill no longer exists in a &lt;em&gt;live&lt;/em&gt;
registry have their projected files removed - symlinks unlinked, hash-clean
copies deleted, user-&lt;strong&gt;modified&lt;/strong&gt; copies archived to
&lt;code dir=&quot;auto&quot;&gt;.kittify/.migration-backup/agent-skills/&lt;/code&gt; instead of deleted - emptied skill
dirs pruned, and the manifest entries dropped, silencing the repeat warning.
Only ledger-recorded paths are ever touched (a user-authored skill sharing
the projection root is never scanned), and an &lt;strong&gt;empty&lt;/strong&gt; registry never
retires anything (a broken canonical source must not mass-drain the
manifest).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test-session state leaks closed: per-mission prompt-tmp namespace +
workspace-context tombstone (#1842, #2032).&lt;/strong&gt; Runtime prompt files are now
written under a per-repo/per-mission namespaced temp directory
(&lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;tmp&gt;/spec-kitty-prompts/&amp;#x3C;repo-id&gt;/…&lt;/code&gt;) instead of a shared flat &lt;code dir=&quot;auto&quot;&gt;/tmp&lt;/code&gt;
path, and a lane’s workspace-context sidecar is now tombstoned when its
worktree is torn down at merge (or when the lane is canceled) - clearing the
stale-context and prompt-litter residue flagged by the #1931 &lt;code dir=&quot;auto&quot;&gt;/tmp&lt;/code&gt;-hygiene
audit. A session-scoped pytest reaper (controller-gated, run-uid-scoped, and
never touching the real &lt;code dir=&quot;auto&quot;&gt;~/.spec-kitty&lt;/code&gt;) now fails the suite if a test leaks
repo-root residue, so new leaks are caught at their source.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard: PR-bound missions planned on a feature branch are visible again
(#2430).&lt;/strong&gt; The dashboard scanner resolved ONE directory per mission,
coord-worktree-first - but under coordination topology the two partitions
live on different surfaces: &lt;code dir=&quot;auto&quot;&gt;spec-commit&lt;/code&gt; lands planning artifacts
(&lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;) on the &lt;strong&gt;primary&lt;/strong&gt;
surface, while the live event log lives on the &lt;strong&gt;coordination&lt;/strong&gt; branch. The
scanned &lt;code dir=&quot;auto&quot;&gt;-coord&lt;/code&gt; copy therefore held only status writes, so the legacy
existence filter (numeric prefix or &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; present) silently dropped any
in-flight post-083 mission from &lt;code dir=&quot;auto&quot;&gt;/api/features&lt;/code&gt;, and artifact viewers/kanban
read the wrong surface. The scanner now splits the read per partition —
planning artifacts primary-first through the same kind-aware read seam the
#2331 identity fix uses (&lt;code dir=&quot;auto&quot;&gt;resolve_planning_read_dir&lt;/code&gt;), live lane state from
the gather-resolved coord surface - so an in-flight coordination mission
lists with its real spec/plan/tasks AND live kanban lanes. Same
coord-shadows-primary class as #2331; the accept-side sibling is #2404.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Session banner no longer recommends a downgrade (#2413).&lt;/strong&gt; The
session-presence health check decided “upgrade-available” with a bare
inequality (&lt;code dir=&quot;auto&quot;&gt;avail != current&lt;/code&gt;), so any machine whose installed CLI was
&lt;em&gt;newer&lt;/em&gt; than the cached PyPI latest - a fresh release not yet in the 1-hour
cache, or an rc/dev install - got ”⚠ Upgrade available: 3.2.2” while running
3.2.4. Both health branches now use &lt;code dir=&quot;auto&quot;&gt;packaging.Version&lt;/code&gt; ordering
(&lt;code dir=&quot;auto&quot;&gt;avail &gt; current&lt;/code&gt;); unparseable versions are treated as no-upgrade so
session start never breaks on a weird cache value.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The shared Agent-Skills projection root and the per-machine skill install
ledger are now gitignored (#2412).&lt;/strong&gt; The skills installer projects global
canonical skills into &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; (codex/vibe/pi/letta) preferring
&lt;strong&gt;absolute symlinks&lt;/strong&gt; into the user-global root - machine-local content by
construction - but unlike &lt;code dir=&quot;auto&quot;&gt;.claude/&lt;/code&gt; and the other agent dirs (gitignored
wholesale at init), bare &lt;code dir=&quot;auto&quot;&gt;.agents/&lt;/code&gt; was never covered by any init path,
registry entry, or migration, so the &lt;code dir=&quot;auto&quot;&gt;/Users/&amp;#x3C;name&gt;/...&lt;/code&gt; symlink blobs were
committable (and the upgrade auto-commit would land them automatically).
&lt;code dir=&quot;auto&quot;&gt;.kittify/skills-manifest.json&lt;/code&gt; (per-machine timestamps/hashes/delivery
modes) had the same gap. Both are now registered &lt;code dir=&quot;auto&quot;&gt;IGNORED&lt;/code&gt; state surfaces
(fresh &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; gitignores them, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt;’s
present-but-not-gitignored warning covers them), and a sibling backfill
migration (&lt;code dir=&quot;auto&quot;&gt;3.2.5_agents_skills_gitignore_backfill&lt;/code&gt;) adds the entries on
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; for already-initialised projects. The symlink-vs-copy
delivery question (ask 3 of #2412) is tracked separately on the issue.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now commits worktree churn on every checkout, not just
main (#2392, closes #2385/#1873, pins #2105).&lt;/strong&gt; The upgrade auto-commit
captured a porcelain baseline for the main checkout only, so migration writes
it made in sibling worktrees were left uncommitted - dirtying them and
blocking coordination-topology merges (NFR-002). The porcelain-baseline commit
routine is extracted into a canonical per-checkout seam
(&lt;code dir=&quot;auto&quot;&gt;upgrade/autocommit.py::commit_touched_checkout&lt;/code&gt;); the migration runner now
snapshots each worktree &lt;em&gt;before&lt;/em&gt; its writes and commits only that new churn on
the worktree’s own branch (in-flight WP edits are never swept in;
&lt;code dir=&quot;auto&quot;&gt;manual_review_required&lt;/code&gt; migrations skip the commit with a warning;
detached-HEAD skips instead of guessing a ref; &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; stays a strict
no-op). #1873’s self-healing path is restored (metadata synthesized from
&lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; is marked dirty so it’s saved even when detected version == target).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Legacy-topology warning no longer over-fires on intentional
coordination-less missions (#2351).&lt;/strong&gt; The once-per-mission warning keyed on
&lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt; absence, so it fired for genuinely deliberate
&lt;code dir=&quot;auto&quot;&gt;single_branch&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;lanes&lt;/code&gt; shapes (#2218) as well as truly pre-SSOT missions. A
new warning-only classifier gates just the emit on the canonical stored
&lt;code dir=&quot;auto&quot;&gt;MissionTopology&lt;/code&gt; + flattened flag (warn iff coordination branch absent AND
stored topology null AND not flattened; malformed still warns); the shared
&lt;code dir=&quot;auto&quot;&gt;_is_legacy_mission&lt;/code&gt; predicate that drives worktree routing and write-contract
selection is left byte-for-byte unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/migrations/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/logs/&lt;/code&gt; are gitignored and backfilled
(#2384, completes the #2369 sweep).&lt;/strong&gt; Two more generated &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; subtrees
(mission-state repair manifests + quarantine backups; orchestrator per-WP
logs) were neither IGNORED state surfaces nor backfilled, so they dirtied the
tree and failed &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;’s git-dirty check. Both are now registered IGNORED
local-runtime surfaces (fresh &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; gitignores them) with a sibling
backfill migration for already-initialised projects on upgrade.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;saas_client&lt;/code&gt; no longer defaults to a hardcoded &lt;code dir=&quot;auto&quot;&gt;api.spec-kitty.io&lt;/code&gt;; it
fails closed (#2248).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;load_auth_context&lt;/code&gt; fell back to a baked-in SaaS URL
when neither &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt; nor &lt;code dir=&quot;auto&quot;&gt;.kittify/saas-auth.json&lt;/code&gt; supplied one,
risking silently pointing the client at the wrong server. With the #2146
target-authority decision in place, the default is removed and a no-URL
resolution now raises &lt;code dir=&quot;auto&quot;&gt;SaasAuthError&lt;/code&gt; (caught where the no-token path already
was).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sync runtime callers route through the canonical resolved target authority
(#2146).&lt;/strong&gt; The tracker client, sharing client, and background sync read the
raw &lt;code dir=&quot;auto&quot;&gt;SyncConfig.get_server_url()&lt;/code&gt; (config-only, hardcoded default) instead of
&lt;code dir=&quot;auto&quot;&gt;resolve_runtime_target().resolved_server_url&lt;/code&gt;, so with &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_URL&lt;/code&gt;
set, auth/readiness hit the env target while these surfaces silently posted to
the config target (the SC-008 split-brain). All three now resolve the same
target as auth/readiness, and &lt;code dir=&quot;auto&quot;&gt;sync status&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; report the resolved
URL. Separately, &lt;code dir=&quot;auto&quot;&gt;sync server &amp;#x3C;url&gt;&lt;/code&gt; now accepts loopback HTTP
(&lt;code dir=&quot;auto&quot;&gt;http://localhost&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;127.0.0.1&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;::1&lt;/code&gt;) for the documented local-Docker-SaaS
dev workflow while still requiring HTTPS for remote hosts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;compat-planner contract checks are revived (#2419).&lt;/strong&gt; Two test surfaces
validated &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;render_json&lt;/code&gt; payloads against the committed
&lt;code dir=&quot;auto&quot;&gt;compat-planner.json&lt;/code&gt; contract but silently no-op’d in CI since 2026-04-27
(each resolved the contract via a maintainer-worktree-only path, so it was
&lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt; and validation was skipped). Both now anchor on the repo root, load
unconditionally, and fail hard on a missing/unreadable contract - which caught
one real drift (a migration description trimmed to satisfy &lt;code dir=&quot;auto&quot;&gt;maxLength&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;migration_id contract pattern widened to admit the dotted convention
(#2339).&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;compat-planner.json&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;migration_id&lt;/code&gt; pattern
(&lt;code dir=&quot;auto&quot;&gt;^[a-z0-9_]{1,128}$&lt;/code&gt;) rejected 83 of 89 real dotted ids (e.g.
&lt;code dir=&quot;auto&quot;&gt;3.2.0rc45_...&lt;/code&gt;) - a contract-authoring bug that let #2339-class drift slip
through unnoticed. Widened to &lt;code dir=&quot;auto&quot;&gt;^[a-z0-9_.]{1,128}$&lt;/code&gt; (a backward-compatible
widening; no shipped &lt;code dir=&quot;auto&quot;&gt;migration_id&lt;/code&gt; renamed, so persisted per-project ledgers
keep validating).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-changed-3&quot;&gt;♻️ Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Internal: version-comparison primitives consolidated into one canonical module (#2417, landing via PR #2414).&lt;/strong&gt;
Landing the #2413 fix surfaced three independent “is version A newer than
version B” implementations that had drifted apart in edge-case handling:
&lt;code dir=&quot;auto&quot;&gt;cli/commands/upgrade.py::_version_is_newer&lt;/code&gt; (caught the broad &lt;code dir=&quot;auto&quot;&gt;Exception&lt;/code&gt;
instead of the specific parse failure), &lt;code dir=&quot;auto&quot;&gt;core/upgrade_probe.py::_classify&lt;/code&gt;’s
inline comparison, and the &lt;code dir=&quot;auto&quot;&gt;_upgrade_is_available&lt;/code&gt; helper #2413 had just
added to &lt;code dir=&quot;auto&quot;&gt;session_presence/manager.py&lt;/code&gt;. All three now delegate to a new
pure module, &lt;code dir=&quot;auto&quot;&gt;specify_cli.core.version_compare&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;try_parse_version&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;is_version_newer&lt;/code&gt;), with no CLI/click/typer
imports so it is safe to import from any layer; the two duplicate boolean
helpers are deleted outright, no aliases left behind. No user-facing
behavior change.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Internal: CI-topology census freshness gate is now LOC-insensitive
(#2416).&lt;/strong&gt; The gate compared each worklist entry’s exact line count and an
LOC-derived sort order, so any PR that shifted the line count of a worklist
directory went red regardless of touching CI routing - a maintenance tax two
PRs paid inside 24h. It now checks membership + committed routing plan only
(an order/LOC-insensitive index at the shared derivation), fixing both the
pytest gate and the &lt;code dir=&quot;auto&quot;&gt;--verify-census&lt;/code&gt; CLI by construction. Zero &lt;code dir=&quot;auto&quot;&gt;src&lt;/code&gt; changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Internal: test-suite &lt;code dir=&quot;auto&quot;&gt;/tmp&lt;/code&gt; hygiene sweep (#1842, epic #1931).&lt;/strong&gt; 97
grandfathered test files were converted off literal &lt;code dir=&quot;auto&quot;&gt;/tmp&lt;/code&gt; paths to
&lt;code dir=&quot;auto&quot;&gt;tmp_path&lt;/code&gt;/sentinels, and the empty-&lt;code dir=&quot;auto&quot;&gt;/tmp&lt;/code&gt; ratchet was flipped to a
self-consistent hard gate so new literal-&lt;code dir=&quot;auto&quot;&gt;/tmp&lt;/code&gt; leaks fail fast. Also fixed a
test-only &lt;code dir=&quot;auto&quot;&gt;--output=&lt;/code&gt; parser leak that could write an invalid Windows filename
(breaking the Windows critical CI job), with a new arch guard blocking
Windows-illegal names and shell-expansion-leak telltales across tracked files
(#2169).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-breaking-changes-2&quot;&gt;💥 Breaking Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Pre-3.2.x legacy (meta-less) missions are no longer supported for
coordination operations (#2091 / #2462).&lt;/strong&gt; A mission with no resolvable
mission identity - no &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, the pre-3.2.x
mission-identity model - can no longer drive coordination operations (status
transitions, &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;, review/merge coordination writes). Such a mission
now &lt;strong&gt;fails loud&lt;/strong&gt; with a customer-actionable error instead of silently
composing a malformed &lt;code dir=&quot;auto&quot;&gt;kitty/mission-&amp;#x3C;slug&gt;-&lt;/code&gt; ref (the old #2091 defect that
surfaced only as an opaque &lt;code dir=&quot;auto&quot;&gt;git worktree add&lt;/code&gt; exit-128). This intentionally
drops the dual-era legacy-bridge fallback: legacy missions are dwindling and
the dual-support path was a persistent source of split-brain routing bugs.
&lt;strong&gt;Migration:&lt;/strong&gt; run &lt;code dir=&quot;auto&quot;&gt;spec-kitty migrate backfill-identity&lt;/code&gt; to mint a ULID
&lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; (and derive its &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt;) for any affected mission - audit first
with &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor identity&lt;/code&gt;. See
&lt;a href=&quot;/migrations/mission-id-canonical-identity/&quot;&gt;mission-id-canonical-identity.md&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;324---2026-07-05&quot;&gt;[3.2.4] - 2026-07-05&lt;/h2&gt;
&lt;p&gt;Spec Kitty 3.2.4 is a reliability-and-trust release. It fixes a batch of
everyday mission-lifecycle friction points, closes a real gap in the bulk-edit
safety net, makes SaaS sync reporting honest, and - behind the scenes —
reshapes the CI pipeline and decomposes a large internal command module for
faster feedback and lower regression risk going forward.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Smoother day-to-day mission lifecycle.&lt;/strong&gt; A batch of guard/gate fixes
removes friction from the implement-review-accept loop: a subtask guard no
longer misattributes a later work package’s unchecked boxes to an earlier
one, a mission fully implemented by &lt;code dir=&quot;auto&quot;&gt;spec-kitty-orchestrator&lt;/code&gt; can now pass
&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; (two false-positive blockers removed), &lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; recovers a killed implementer’s uncommitted work instead of
dead-ending, closing a mission now reliably commits its auto-captured
retrospective, the dashboard no longer hides an in-flight coordination
mission behind a synthetic “orphan” entry, and a stale &lt;code dir=&quot;auto&quot;&gt;.kittify/derived/&lt;/code&gt;
view or Op-index cache file can no longer dirty &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; or block
&lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; also now explains exactly &lt;em&gt;why&lt;/em&gt; a requirement
reference is stale instead of looking like data corruption.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission-state repair no longer risks data loss.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt; (and the automatic repair &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; runs) previously could
empty a healthy mission’s event log of its canonical lifecycle history; it
now preserves every reader-canonical event class and anchors on the primary
checkout so repairs actually take effect.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Bulk-edit safety net closed.&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;occurrence_map.yaml&lt;/code&gt; gate that blocks
an incomplete bulk-edit classification at finalize-tasks now covers &lt;em&gt;both&lt;/em&gt;
finalize-tasks command surfaces, not just one - closing a path where a
bulk-edit mission could slip through with an inadmissible occurrence map.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Honest SaaS sync reporting.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;sync opt-in&lt;/code&gt; no longer implies remote
enablement it didn’t perform, and &lt;code dir=&quot;auto&quot;&gt;sync status --check --json&lt;/code&gt; reports real
(or honestly &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;) remote/import state instead of staying silent.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; capability.&lt;/strong&gt; A read-only &lt;code dir=&quot;auto&quot;&gt;resolve-workspace&lt;/code&gt;
command lets an external orchestrator recover a work package’s lane
workspace without accidentally re-triggering a lifecycle transition.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;em&gt;Behind the scenes:&lt;/em&gt; the CI pipeline was reshaped - path-filtered job groups, a
split core-misc shard, and an always-on, de-serialized architectural-adversarial
pole - so most PRs get faster, more targeted feedback without losing any
coverage; and the sprawling &lt;code dir=&quot;auto&quot;&gt;agent tasks&lt;/code&gt; command module was decomposed into
small, independently-tested, behavior-preserving pieces. Neither changes any
user-visible behavior, but both reduce the odds of the next regression and
speed up how fast we catch one.&lt;/p&gt;
&lt;h3 id=&quot;-breaking-changes-3&quot;&gt;💥 Breaking Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Deprecated compatibility shim packages removed (mission &lt;code dir=&quot;auto&quot;&gt;unshim-wave2-01KWMCAX&lt;/code&gt;, #2291 / #2290 / #2326 under #1797).&lt;/strong&gt; The following re-export shim import paths are &lt;strong&gt;deleted&lt;/strong&gt; - code that imported them must switch to the canonical path:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.next&lt;/code&gt; → &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;runtime.next&lt;/code&gt;&lt;/strong&gt; (the canonical &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; runtime/control-loop package; antecedent #612)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.glossary&lt;/code&gt; → &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;glossary&lt;/code&gt;&lt;/strong&gt; (antecedent #613)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_lint&lt;/code&gt; → &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_runtime.lint&lt;/code&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_freshness&lt;/code&gt; → &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_runtime.freshness&lt;/code&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_preflight&lt;/code&gt; → &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_runtime.preflight&lt;/code&gt;&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All in-tree callers were re-pointed to the canonical modules before deletion. The shim registry (&lt;code dir=&quot;auto&quot;&gt;docs/migrations/shim-registry.yaml&lt;/code&gt;, the file read by &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor shim-registry&lt;/code&gt;) is drained to &lt;code dir=&quot;auto&quot;&gt;shims: []&lt;/code&gt;, and the ownership manifest (&lt;code dir=&quot;auto&quot;&gt;docs/architecture/05_ownership_manifest.yaml&lt;/code&gt;) mirrors the drain for these slices. The user-facing CLI surface is unchanged - &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter lint/preflight/freshness&lt;/code&gt; behave identically. &lt;strong&gt;No version bump accompanies this entry:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/__init__.py&lt;/code&gt; is untouched by the mission (verified against the mission lane history), so the public CLI package version is unaffected; only internal deprecated import paths are removed.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-changed-4&quot;&gt;♻️ Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CI health: charter-path doc hotfix + arch-adversarial matrix shard (mission &lt;code dir=&quot;auto&quot;&gt;ci-health-charter-path-and-arch-shard-01KWRTB2&lt;/code&gt;, closes #2397).&lt;/strong&gt; Two independent CI-health fixes bundled by operator decision: (a) &lt;code dir=&quot;auto&quot;&gt;docs/guides/contributing.md&lt;/code&gt; still published the retired legacy charter path &lt;code dir=&quot;auto&quot;&gt;memory/charter.md&lt;/code&gt;, redding &lt;code dir=&quot;auto&quot;&gt;fast-tests-docs&lt;/code&gt; on every open PR - replaced with the canonical &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt;; (b) the &lt;code dir=&quot;auto&quot;&gt;arch-adversarial&lt;/code&gt; job (already de-serialized from the core-misc critical path by the CI-topology-shrink mission above) remained a single unsharded ~14.4-min bottleneck - matrix-sharded into always-on, group-less shards (same pattern as &lt;code dir=&quot;auto&quot;&gt;fast-tests-core-misc&lt;/code&gt;), still running on 100% of source changes with no test dropped or double-counted across shards, dropping the slowest shard below the ~13.6-min sub-target.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One canonical &lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; payload builder (#2270, PR #2398).&lt;/strong&gt; Three independent code paths derived &lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; defaults and had drifted apart: &lt;code dir=&quot;auto&quot;&gt;core/mission_creation.py&lt;/code&gt;, a verbatim-duplicate helper in &lt;code dir=&quot;auto&quot;&gt;sync/emitter.py&lt;/code&gt;, and a third, divergent inline fallback in &lt;code dir=&quot;auto&quot;&gt;status/lifecycle_events.py&lt;/code&gt; (raw slug vs. titleized &lt;code dir=&quot;auto&quot;&gt;friendly_name&lt;/code&gt;, absent vs. now &lt;code dir=&quot;auto&quot;&gt;created_at&lt;/code&gt;, differing None-field wire shape). A new pure CORE module, &lt;code dir=&quot;auto&quot;&gt;core/mission_payload.py::build_mission_created_payload&lt;/code&gt;, is now the single source; both the local lifecycle-event path and the SaaS &lt;code dir=&quot;auto&quot;&gt;EventEmitter&lt;/code&gt; route through it, preserving the CORE↛INTEGRATION boundary (no sync import in core). &lt;strong&gt;Behavioral note:&lt;/strong&gt; the local mission log’s default &lt;code dir=&quot;auto&quot;&gt;friendly_name&lt;/code&gt; (when not passed explicitly) now titleizes the slug instead of using it raw, matching what the SaaS emitter already produced.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI topology shrink + shard split + always-on architectural pole (mission &lt;code dir=&quot;auto&quot;&gt;ci-topology-shrink-01KWQAVX&lt;/code&gt;, #2378 / #1933 / #2383 under #1931).&lt;/strong&gt; The &lt;code dir=&quot;auto&quot;&gt;ci-quality.yml&lt;/code&gt; PR pipeline is reshaped so a single-area PR runs only its focused shard(s) plus the always-on gates, not a full-matrix run:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Group-side shrink (#1933).&lt;/strong&gt; The previously-unmapped &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/*&lt;/code&gt; directories are folded into six named composite &lt;code dir=&quot;auto&quot;&gt;dorny/paths-filter&lt;/code&gt; groups (&lt;code dir=&quot;auto&quot;&gt;auth_audit_git&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lifecycle&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;agent_surface&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;closeout&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;governance&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;platform&lt;/code&gt;), each registered atomically across all five surfaces (filters block, &lt;code dir=&quot;auto&quot;&gt;changes.outputs.*&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;unmatched&lt;/code&gt; enumeration, and the &lt;code dir=&quot;auto&quot;&gt;JOB_GROUPS&lt;/code&gt; needs-lists). All 32 worklist dirs are now routed. This is the &lt;strong&gt;shrink&lt;/strong&gt; interpretation of #1933 (fast, targeted PR CI), not the literal nightly-scheduled full suite (deferred per C-006); the escape hatches (&lt;code dir=&quot;auto&quot;&gt;workflow_dispatch&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;run_all&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;run_extended&lt;/code&gt;, the nightly &lt;code dir=&quot;auto&quot;&gt;schedule&lt;/code&gt; cron, the &lt;code dir=&quot;auto&quot;&gt;unmatched&lt;/code&gt; fail-closed catch-all) and the nightly &lt;code dir=&quot;auto&quot;&gt;run_all&lt;/code&gt; over-cover of every worklist dir remain intact - no new blind spot (FR-009).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shard-side split (#2378).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;fast-tests-core-misc&lt;/code&gt; is subdivided into two disjoint, non-empty matrix shards (ignore-mirror kept consistent), so a core-misc change no longer drags the whole misc bucket.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Architectural un-blind, de-serialized (#2383, NFR-002).&lt;/strong&gt; The architectural + adversarial guard job (&lt;code dir=&quot;auto&quot;&gt;arch-adversarial&lt;/code&gt;) runs always-on (&lt;code dir=&quot;auto&quot;&gt;if: always()&lt;/code&gt;, group-less) over 100% of &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;, and is &lt;strong&gt;de-serialized&lt;/strong&gt; from &lt;code dir=&quot;auto&quot;&gt;fast-tests-core-misc&lt;/code&gt; (its &lt;code dir=&quot;auto&quot;&gt;needs&lt;/code&gt; edge is dropped) so it no longer sits on the core-misc critical path - the path collapses from &lt;code dir=&quot;auto&quot;&gt;sum&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;max&lt;/code&gt;, structurally under the ≤13.6-min next-lane ceiling (NFR-001; live &lt;code dir=&quot;auto&quot;&gt;measured_source_run_id&lt;/code&gt; backfilled by the operator from the PR’s first post-shrink CI run).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Coverage-consumer integrity by construction (C-005).&lt;/strong&gt; New architectural invariants assert coverage-emitting jobs ⊆ &lt;code dir=&quot;auto&quot;&gt;sonarcloud.needs&lt;/code&gt; and critical-path emitters ⊆ &lt;code dir=&quot;auto&quot;&gt;diff-coverage.needs&lt;/code&gt;; in the process the pre-existing production &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission-loader-coverage&lt;/code&gt; coverage-drop is fixed&lt;/strong&gt; - it emits &lt;code dir=&quot;auto&quot;&gt;--cov=src/specify_cli/mission_loader&lt;/code&gt; yet was absent from &lt;code dir=&quot;auto&quot;&gt;sonarcloud.needs&lt;/code&gt;, so its coverage XML was silently dropped from the Sonar gate. The full 8-invariant #2368 substrate suite plus the new NFR-002/003/005 and C-005 relations stay green (NFR-007), and the gate-coverage ratchet baseline is refreshed (&lt;code dir=&quot;auto&quot;&gt;orphan_test_count&lt;/code&gt; 0; &lt;code dir=&quot;auto&quot;&gt;total_tests&lt;/code&gt; rises with the added invariants; &lt;code dir=&quot;auto&quot;&gt;duplicate_test_count&lt;/code&gt; falls with the same-tier consolidation).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Root &lt;code dir=&quot;auto&quot;&gt;CHANGELOG.md&lt;/code&gt; is now a symlink to the canonical &lt;code dir=&quot;auto&quot;&gt;docs/changelog/CHANGELOG.md&lt;/code&gt; - the generated mirror is retired.&lt;/strong&gt; The two-file model (canonical + frontmatter-stripped root copy kept in sync by &lt;code dir=&quot;auto&quot;&gt;scripts/docs/sync_changelog.py&lt;/code&gt;) made contributors edit the root copy and trip docs-freshness on every external PR. There is now exactly one changelog file; &lt;code dir=&quot;auto&quot;&gt;sync_changelog.py --check&lt;/code&gt; guards the symlink (and &lt;code dir=&quot;auto&quot;&gt;--write&lt;/code&gt; restores it), and release tooling (&lt;code dir=&quot;auto&quot;&gt;extract_changelog.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;validate_release.py&lt;/code&gt;) reads the canonical text through the link - both scan &lt;code dir=&quot;auto&quot;&gt;## [...]&lt;/code&gt; headings and tolerate the YAML frontmatter.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; contract 1.1.0 → 1.2.0: new read-only &lt;code dir=&quot;auto&quot;&gt;resolve-workspace&lt;/code&gt; command (#2337).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;resolve-workspace --mission --wp&lt;/code&gt; returns a work package’s lane &lt;code dir=&quot;auto&quot;&gt;workspace_path&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;prompt_path&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;lane_branch&lt;/code&gt; for its &lt;strong&gt;existing&lt;/strong&gt; lane, resolved via the canonical naming seams &lt;strong&gt;without&lt;/strong&gt; allocating, creating, validating-clean, or transitioning. It’s the read-only companion of &lt;code dir=&quot;auto&quot;&gt;start-implementation&lt;/code&gt; (which does a &lt;code dir=&quot;auto&quot;&gt;planned→claimed→in_progress&lt;/code&gt; composite transition): an external orchestrator resuming a WP already past implementation (e.g. one parked in &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; after an interrupted run) can obtain its workspace to dispatch a reviewer without mis-transitioning it. Purely additive - existing commands and payloads are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Internal: the &lt;code dir=&quot;auto&quot;&gt;agent tasks&lt;/code&gt; god-command is decomposed into pure decision cores behind injected ports (mission &lt;code dir=&quot;auto&quot;&gt;tasks-py-degod-01KWF08S&lt;/code&gt;, #2116 under #2173).&lt;/strong&gt; Behavior-preserving - the full &lt;code dir=&quot;auto&quot;&gt;agent tasks&lt;/code&gt; CLI contract (all subcommands, flags, exit codes, &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; envelopes, including the coord skip-exit-0 arm and the refuse-exit-1 arms) is &lt;strong&gt;byte-identical&lt;/strong&gt;, frozen by a golden characterization harness. The decision/aggregation logic of the five fat command bodies (&lt;code dir=&quot;auto&quot;&gt;move_task&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;map_requirements&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mark_status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;finalize_tasks&lt;/code&gt;) now lives in pure, independently-tested sibling modules (&lt;code dir=&quot;auto&quot;&gt;tasks_transition_core&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks_mapping_core&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks_status_view&lt;/code&gt;) behind an injected &lt;code dir=&quot;auto&quot;&gt;TasksPorts&lt;/code&gt; seam (&lt;code dir=&quot;auto&quot;&gt;FsReader&lt;/code&gt; coord-READ authority + a two-capability &lt;code dir=&quot;auto&quot;&gt;CoordCommitRouter&lt;/code&gt; coord-WRITE authority); each command body is a ≤150-LOC thin orchestrator. Also folds the pre-3.0 coord read-authority split-brain onto the kind-aware authority (guard-only sites) and drains the resolution-authority census (shrink-only). &lt;strong&gt;No user-facing behavior change.&lt;/strong&gt; The Render-seam unification and the whole-file &lt;code dir=&quot;auto&quot;&gt;tasks.py&lt;/code&gt; shim relocation are deferred to a follow-up mission (see &lt;code dir=&quot;auto&quot;&gt;docs/plans/tasks-py-degod-followup-mission-debrief.md&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-4&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bulk-edit occurrence-map gate now also enforced on the legacy &lt;code dir=&quot;auto&quot;&gt;agent tasks finalize-tasks&lt;/code&gt; command (#2345, PR #2386).&lt;/strong&gt; The PR that gates &lt;code dir=&quot;auto&quot;&gt;occurrence_map.yaml&lt;/code&gt; at finalize-tasks (rather than at first &lt;code dir=&quot;auto&quot;&gt;implement WP##&lt;/code&gt;) only wired the check into &lt;code dir=&quot;auto&quot;&gt;agent mission finalize-tasks&lt;/code&gt;; the older, still-live &lt;code dir=&quot;auto&quot;&gt;agent tasks finalize-tasks&lt;/code&gt; command family could complete finalize-tasks for a bulk-edit mission with a missing, schema-invalid, or inadmissible occurrence map with zero gate friction - found by the pre-merge adversarial squad during landing. &lt;code dir=&quot;auto&quot;&gt;_ft_validate_occurrence_map_ready&lt;/code&gt; mirrors the mission-command gate and runs first in &lt;code dir=&quot;auto&quot;&gt;_ft_validate&lt;/code&gt; (fail-fast, before dependency parsing); the shared error message and JSON payload are de-duplicated into &lt;code dir=&quot;auto&quot;&gt;bulk_edit/gate.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;finalize_tasks_gate_error_payload&lt;/code&gt;) so the two command surfaces can’t drift apart again.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Honest SaaS sync opt-in reporting + typed &lt;code dir=&quot;auto&quot;&gt;remote_sync&lt;/code&gt; status fields (#2264 slice, PR #2396).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;sync opt-in&lt;/code&gt; printed &lt;code dir=&quot;auto&quot;&gt;✓ Enabled SaaS sync for this checkout&lt;/code&gt; even though it only writes local routing flags - implying remote enablement that never happened; the message now states only that a local preference was recorded. &lt;code dir=&quot;auto&quot;&gt;sync status --check --json&lt;/code&gt; gains a typed &lt;code dir=&quot;auto&quot;&gt;remote_sync&lt;/code&gt; block (&lt;code dir=&quot;auto&quot;&gt;remote_project_state&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;materialized_at&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;historical_import_state&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;last_blocker_sample&lt;/code&gt;), honestly &lt;code dir=&quot;auto&quot;&gt;unknown&lt;/code&gt;/null until the import engine (#2262) populates it - &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt; semantics are unchanged, so existing consumers are unaffected and new consumers read remote state from &lt;code dir=&quot;auto&quot;&gt;remote_sync&lt;/code&gt;, not &lt;code dir=&quot;auto&quot;&gt;ok&lt;/code&gt;. Also folded in: &lt;code dir=&quot;auto&quot;&gt;opt-in&lt;/code&gt; now exits non-zero (was a dim exit-0 message) when the SaaS-sync rollout flag is disabled, since opt-in cannot take effect with the flag off.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/migrations/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/logs/&lt;/code&gt; are now gitignored - completing
the #2369 derived-views fix (#2384).&lt;/strong&gt; Two more generated &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; subtrees
of the same class as &lt;code dir=&quot;auto&quot;&gt;.kittify/derived/&lt;/code&gt; were neither registered &lt;code dir=&quot;auto&quot;&gt;IGNORED&lt;/code&gt;
state surfaces nor added by any backfill, so they showed up untracked and
failed &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt;’s &lt;code dir=&quot;auto&quot;&gt;git_dirty&lt;/code&gt; check: &lt;code dir=&quot;auto&quot;&gt;.kittify/migrations/&lt;/code&gt;
(mission-state repair manifests + quarantine backups) and &lt;code dir=&quot;auto&quot;&gt;.kittify/logs/&lt;/code&gt;
(orchestrator per-WP implementation/review logs). Both are now registered
&lt;code dir=&quot;auto&quot;&gt;IGNORED&lt;/code&gt; surfaces (fresh &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; gitignores them), and a sibling
backfill migration (&lt;code dir=&quot;auto&quot;&gt;3.2.4_runtime_dirs_gitignore_backfill&lt;/code&gt;) adds them on
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; for already-initialised projects.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upgrade-worktree coherence: one canonical per-checkout auto-commit seam
(epic #2392 spine - closes #2385, #1873; regression-pins #2105).&lt;/strong&gt; The
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; commit routine (porcelain-baseline-derived commit-set,
directory expansion, eligibility filter) is extracted from the CLI into
&lt;code dir=&quot;auto&quot;&gt;specify_cli.upgrade.autocommit.commit_touched_checkout()&lt;/code&gt; and applied
symmetrically to &lt;strong&gt;every checkout the run touches&lt;/strong&gt; over the runner’s single
worktree enumeration:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#2385&lt;/strong&gt; - worktree migration churn was never committed (auto-commit ran on
the main checkout only), so each coord/lane worktree was left dirty and a
later &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; tripped the #1826/NFR-002 guard. The runner now
captures a per-worktree porcelain baseline before that worktree’s writes and
commits its &lt;em&gt;new&lt;/em&gt; churn on its own branch; pre-existing uncommitted work
(e.g. in-flight WP edits) is never swept in, and per-worktree
&lt;code dir=&quot;auto&quot;&gt;manual_review_required&lt;/code&gt; migrations skip that worktree’s commit with a
warning. Root &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; churn - exactly what the gitignore-backfill
migrations write - is now commit-eligible instead of being dropped by the
root-level-file filter.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#1873&lt;/strong&gt; - freshly synthesized worktree metadata is persisted (and
committed) even when the detected version already equals the target,
restoring the #1857 self-healing path.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#2105&lt;/strong&gt; - already porcelain-derived in this tree; now regression-pinned by
a test asserting manifest updates and newly-installed skills land in the
commit-set (guards against regressing to a hardcoded file list).&lt;/li&gt;
&lt;li&gt;A detached-HEAD checkout skips the auto-commit with a warning instead of
guessing a ref. &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; remains a strict no-op per checkout. An
invariant test asserts that after &lt;code dir=&quot;auto&quot;&gt;upgrade&lt;/code&gt;, no touched checkout carries
porcelain dirt beyond what pre-existed. &lt;strong&gt;#2367’s two mechanisms are
deliberately NOT routed through this seam&lt;/strong&gt; (per the #2392 architect
design): the implement-claim VCS-lock policy (#2222/C-003 race decision)
and the merge-rollback snapshot capture set are separate seams sharing the
same invariant.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Guard/gate friction hotfixes (#2346 / #2324, #1834).&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Subtask guard no longer misattributes a later WP’s checkboxes (#2346, also closes #2324).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;_check_unchecked_subtasks&lt;/code&gt; entered a WP’s section on &lt;em&gt;any&lt;/em&gt; heading that merely mentioned its id, so a dependent heading like &lt;code dir=&quot;auto&quot;&gt;### WP03 - … (depends: WP01, WP02)&lt;/code&gt; re-entered WP01/WP02’s section and harvested WP03’s unchecked &lt;code dir=&quot;auto&quot;&gt;- [ ] T0xx&lt;/code&gt; rows as the earlier WP’s blockers - spuriously blocking that WP’s lane transition. A heading now belongs to the WP named by its &lt;strong&gt;first&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;WPxx&lt;/code&gt; token, not any mention.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;grep_absence&lt;/code&gt; negative invariants accept an optional path-scope (#1834).&lt;/strong&gt; The acceptance gate ran &lt;code dir=&quot;auto&quot;&gt;grep -r &amp;#x3C;pattern&gt; .&lt;/code&gt; over the whole repo, so a negative-invariant pattern that a mission’s own spec/plan/WP prose mentioned false-positived as &lt;code dir=&quot;auto&quot;&gt;still_present&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;NegativeInvariant&lt;/code&gt; now carries an optional &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; (whitespace-separated repo-relative search roots); when set, the grep runs only under those paths. Default (unscoped) preserves the whole-repo search, and &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; is omitted from serialization when unset so existing matrices are untouched.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Documented merge-before-accept for merged-post-state invariants (#1834).&lt;/strong&gt; The accept runbook (&lt;code dir=&quot;auto&quot;&gt;docs/guides/accept-and-merge.md&lt;/code&gt;) now records that the accept gate re-runs each negative-invariant &lt;code dir=&quot;auto&quot;&gt;verification_command&lt;/code&gt; &lt;strong&gt;live&lt;/strong&gt; (so a hand-set &lt;code dir=&quot;auto&quot;&gt;overall_verdict&lt;/code&gt; does not stick), and that a mission whose invariants assert the &lt;em&gt;merged&lt;/em&gt; post-state must run &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; (local) before &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;A mission fully implemented by &lt;code dir=&quot;auto&quot;&gt;spec-kitty-orchestrator&lt;/code&gt; can now pass
&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; - two mechanical false-positives removed (#2369).&lt;/strong&gt; The
accept gate is the mission-level readiness check (all-done, subtasks,
clarifications, artifacts, clean tree, paths), but two checks always failed on
orchestrator-completed missions, forcing operators to bypass accept entirely:
(a) the strict-metadata check required &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt; on &lt;strong&gt;every&lt;/strong&gt; WP, including
terminal ones - but &lt;code dir=&quot;auto&quot;&gt;shell_pid&lt;/code&gt; is an interactive-&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; artifact the
orchestrator never stamps; it is now &lt;strong&gt;lane-gated to active lanes exactly like
&lt;code dir=&quot;auto&quot;&gt;assignee&lt;/code&gt;&lt;/strong&gt;, so a done/approved WP no longer needs it (an active WP still does).
(b) &lt;code dir=&quot;auto&quot;&gt;spec-kitty materialize&lt;/code&gt; writes regenerable views to &lt;code dir=&quot;auto&quot;&gt;.kittify/derived/&lt;/code&gt;,
which was &lt;strong&gt;not&lt;/strong&gt; in the runtime gitignore set (unlike sibling &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;
paths), so it dirtied the tree and failed accept’s &lt;code dir=&quot;auto&quot;&gt;git_dirty&lt;/code&gt; check - the
&lt;code dir=&quot;auto&quot;&gt;derived/&lt;/code&gt; views are now a registered &lt;code dir=&quot;auto&quot;&gt;IGNORED&lt;/code&gt; state surface (so fresh
&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; gitignores it), and a dedicated backfill migration
(&lt;code dir=&quot;auto&quot;&gt;3.2.4_derived_mission_views_gitignore_backfill&lt;/code&gt;) adds &lt;code dir=&quot;auto&quot;&gt;.kittify/derived/&lt;/code&gt;
to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; for already-initialised projects
(the runtime-hygiene migrations previously only knew a hardcoded subset of
entries). The six meaningful accept checks still gate.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission-state repair no longer empties &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; of a healthy
mission (#2376).&lt;/strong&gt; The repair (run by &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; via the TeamSpace
mission-state gate, and by &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt;) quarantined &lt;em&gt;every&lt;/em&gt;
&lt;code dir=&quot;auto&quot;&gt;event_type&lt;/code&gt; row except retrospective ones - including the canonical lifecycle
events (&lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;SpecifyStarted&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;WPCreated&lt;/code&gt;, …) that
&lt;code dir=&quot;auto&quot;&gt;status/lifecycle_events.py&lt;/code&gt; writes and whose &lt;strong&gt;only&lt;/strong&gt; per-mission home is
&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;. A completed mission whose log was all lifecycle events
was emptied to 0 bytes. Repair now &lt;strong&gt;preserves every reader-canonical non-lane
class&lt;/strong&gt; in place - canonical lifecycle events (those in
&lt;code dir=&quot;auto&quot;&gt;LIFECYCLE_EVENT_TYPES&lt;/code&gt;), retrospective lifecycle rows (the &lt;code dir=&quot;auto&quot;&gt;type&lt;/code&gt; envelope),
&lt;strong&gt;and the &lt;code dir=&quot;auto&quot;&gt;retrospective.*&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;event_name&lt;/code&gt; envelope) stream written by
&lt;code dir=&quot;auto&quot;&gt;emit_retrospective_event&lt;/code&gt;&lt;/strong&gt; - so the repair predicate matches the durable
reader (&lt;code dir=&quot;auto&quot;&gt;status/store.py::is_non_lane_event&lt;/code&gt;) exactly. Before this, a mixed log
containing a &lt;code dir=&quot;auto&quot;&gt;retrospective.completed&lt;/code&gt; row still silently stripped it (the same
#2376 data-loss class in a different event format). A backstop also refuses to
write a 0-byte log when the source was non-empty. Decision-Moment
(&lt;code dir=&quot;auto&quot;&gt;DecisionPoint*&lt;/code&gt;) rows are still pruned: their canonical store is
&lt;code dir=&quot;auto&quot;&gt;decisions/index.json&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;DM-*.md&lt;/code&gt;, so the copy here is a mirror (unchanged,
tested behavior). Rows preserved verbatim in the quarantine dir remain
recoverable.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Repair now anchors on the primary checkout so &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; actually
converges and stale coordination worktrees are left untouched (#2320).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt; already re-materializes &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; from
&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, but when invoked from inside a worktree the
invocation root pointed at that worktree, so the materialize landed there:
the &lt;strong&gt;primary&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; stayed frozen (a re-&lt;code dir=&quot;auto&quot;&gt;--audit&lt;/code&gt; reported the
same &lt;code dir=&quot;auto&quot;&gt;SNAPSHOT_DRIFT&lt;/code&gt; blocker) and uncommitted repairs were written into a
possibly-stale coordination worktree. Repair now re-anchors to the canonical
primary main-checkout via the single worktree-pointer parser
(&lt;code dir=&quot;auto&quot;&gt;resolve_canonical_root&lt;/code&gt;), so it always targets the primary
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;&lt;/code&gt; (drift converges) and never dirties &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;. The
read-only &lt;code dir=&quot;auto&quot;&gt;--audit&lt;/code&gt; path is now anchored on the &lt;strong&gt;same&lt;/strong&gt; authority at the
&lt;code dir=&quot;auto&quot;&gt;run_mission_state&lt;/code&gt; dispatch seam, so audit and fix resolve to the identical
canonical root from any cwd (a worktree-invoked &lt;code dir=&quot;auto&quot;&gt;--audit&lt;/code&gt; reads the primary,
matching &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt;) instead of diverging onto a stale worktree.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The Op-index performance cache is now gitignored (#2341).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/ops-index.jsonl&lt;/code&gt; - the machine-local reverse-scan cache that powers
&lt;code dir=&quot;auto&quot;&gt;spec-kitty invocations list&lt;/code&gt; - was never added to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;, so a
freshly-generated index showed up in &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; indefinitely (and could be
accidentally committed). It is now registered as an &lt;code dir=&quot;auto&quot;&gt;IGNORED&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;LOCAL_RUNTIME&lt;/code&gt;
surface in the state contract (&lt;code dir=&quot;auto&quot;&gt;op_invocation_index&lt;/code&gt;), which flows into fresh
&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; protection automatically. Existing projects are repaired by
the runtime git-hygiene migration, which also &lt;code dir=&quot;auto&quot;&gt;git rm --cached&lt;/code&gt;s a
previously-committed index. Durable per-Op audit records
(&lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;op_id&gt;.jsonl&lt;/code&gt;, the new &lt;code dir=&quot;auto&quot;&gt;op_invocation_record&lt;/code&gt; surface) stay
&lt;strong&gt;tracked&lt;/strong&gt; - only the index is ignored.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;The dashboard no longer orphans a valid in-flight (mid-orchestration)
mission (#2331).&lt;/strong&gt; While a coordination-topology mission had live worktrees
checked out, &lt;code dir=&quot;auto&quot;&gt;spec-kitty dashboard&lt;/code&gt; registered it under a synthetic
&lt;code dir=&quot;auto&quot;&gt;orphan:&amp;#x3C;slug&gt;&lt;/code&gt; key - hiding it from the mission dropdown - because the
registry read mission identity (&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;) from the coordination worktree,
which lacks it (&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; is a PRIMARY-partition artifact that lives on the
primary checkout). Identity now resolves through the kind-aware
&lt;code dir=&quot;auto&quot;&gt;resolve_planning_read_dir(..., PRIMARY_METADATA)&lt;/code&gt; seam, so a mission mid-run
shows under its real title and canonical ULID; status/board display still uses
the coordination surface. &lt;code dir=&quot;auto&quot;&gt;lifecycle.json&lt;/code&gt; now also carries &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;. No
change for merged/idle missions.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;move-task --to for_review&lt;/code&gt; recovers a killed implementer’s uncommitted lane
deliverables instead of dead-ending (#2335).&lt;/strong&gt; When an implementer finished its
files but was interrupted before committing, moving the work package to
&lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; failed with a message demanding a manual &lt;code dir=&quot;auto&quot;&gt;git add&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;git commit&lt;/code&gt;
&lt;em&gt;inside the lane worktree&lt;/em&gt; - violating the “spec-kitty drives commits” rule. On
the &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; transition, when the auto-commit policy is enabled (the
default), spec-kitty now commits the finished lane deliverables via the tool
(&lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; on the lane branch) before the readiness guard runs, so recovery
completes without touching lane git by hand. Scoped to &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; only
(&lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; deliverables are already committed); &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; still
bypasses, and &lt;code dir=&quot;auto&quot;&gt;--no-auto-commit&lt;/code&gt; defers to the existing guard.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission close&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; now commit the retrospective they
auto-generate, instead of leaving the durable event log dirty.&lt;/strong&gt; Closing a
mission that was merged via the legacy plain-git/GitHub path (so merge-time
teardown never ran) auto-captured &lt;code dir=&quot;auto&quot;&gt;retrospective.yaml&lt;/code&gt; and appended a
&lt;code dir=&quot;auto&quot;&gt;RetrospectiveCaptured&lt;/code&gt; event to &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, but left both
uncommitted with no notice - violating the atomic-event-log discipline
(FR-016), since an uncommitted append can be lost. The shared post-merge
retrospective postcondition now commits the captured record + its event-log
append via the merge-bookkeeping commit path, so &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission close&lt;/code&gt;
behave identically and the working tree is left clean. If the commit cannot be
made (detached HEAD / not a worktree), it fails open but reports the
uncommitted artifacts and the exact command to commit them. &lt;code dir=&quot;auto&quot;&gt;mission close --help&lt;/code&gt; no longer describes the non-&lt;code dir=&quot;auto&quot;&gt;--discard&lt;/code&gt; path as a pure “no-op”.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; now explains &lt;em&gt;why&lt;/em&gt; a WP &lt;code dir=&quot;auto&quot;&gt;requirement_refs&lt;/code&gt; entry is stale
instead of looking like data corruption (#2066).&lt;/strong&gt; When the stale/invalid-refs
gate trips, the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; payload (and console output) now surface the FR-ID set
parsed from &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;parsed_spec_ids&lt;/code&gt;), classify each offending ref per WP into
&lt;code dir=&quot;auto&quot;&gt;malformed&lt;/code&gt; (violates the &lt;code dir=&quot;auto&quot;&gt;FR-NNN&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;NFR-NNN&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;C-NNN&lt;/code&gt; format - e.g. a
letter-suffixed &lt;code dir=&quot;auto&quot;&gt;FR-003a&lt;/code&gt; or an unfilled &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;FR-XXX&gt;&lt;/code&gt; placeholder) vs
&lt;code dir=&quot;auto&quot;&gt;unknown_spec_id&lt;/code&gt; (well-formed but not declared in the spec), and the hint names
the format rule. A one-character ID-format mismatch is now obvious rather than
reading like invented/orphaned IDs.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;323---2026-06-29&quot;&gt;[3.2.3] - 2026-06-29&lt;/h2&gt;
&lt;p&gt;Spec Kitty 3.2.3 is a stabilization-and-foundations release. It hardens how the
toolkit behaves 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.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Improved branch topology support.&lt;/strong&gt; Coordination-topology missions now read
and write every artifact from the correct surface - planning artifacts
(&lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, work-package &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; identity) 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 &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; no longer stall,
mis-route, or report phantom early state on coordination missions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Usability upgrades.&lt;/strong&gt; A batch of mission-lifecycle tooling-loop friction
fixes, clearer global-install guidance, and safer everyday operation:
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME&lt;/code&gt; now isolates &lt;em&gt;all&lt;/em&gt; local state, &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output is safe to
capture with &lt;code dir=&quot;auto&quot;&gt;2&gt;&amp;#x26;1&lt;/code&gt;, worktree discard can no longer delete a sibling mission,
and a stale tool environment can no longer brick the CLI.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Doctrine additions.&lt;/strong&gt; The Common Docs consolidation lands a governed
documentation foundation - a documentation directive, a styleguide, and
curation / scaffold / write / find tactics wired into the doctrine graph —
alongside the structural move to a 13-section Divio &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; tree: 117
architecture decision records converted to metadata-in-file records under
&lt;code dir=&quot;auto&quot;&gt;docs/adr/&lt;/code&gt;, redirect coverage for every moved page, and documentation rulers
promoted to blocking gates.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Doctrine/charter extension improvements.&lt;/strong&gt; Charter activation now gates
org-pack agent availability across dispatch, context, and projection; the
generated charter interpolates the project documentation policy; and
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt; reports unsanctioned built-in doctrine-graph overrides.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added-4&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Retrospectives now have a durable home and survive coordination teardown (#2119).&lt;/strong&gt;
A new &lt;code dir=&quot;auto&quot;&gt;RETROSPECTIVE&lt;/code&gt; primary-artifact kind routes &lt;code dir=&quot;auto&quot;&gt;retrospective.yaml&lt;/code&gt; to the
tracked &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt; mission folder for every topology, instead of the
ephemeral coordination worktree that is deleted on teardown.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Governed documentation foundation - the Common Docs doctrine (#2210, #2165).&lt;/strong&gt;
A built-in documentation directive (&lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_042&lt;/code&gt;), a documentation styleguide,
and &lt;code dir=&quot;auto&quot;&gt;curation&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;scaffold&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;write&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;find&lt;/code&gt; tactics are now wired into the
doctrine graph, plus three documentation rulers (a &lt;code dir=&quot;auto&quot;&gt;related:&lt;/code&gt; link validator, a
page-inventory lockfile generator, and an anti-sprawl ratchet), each shipped with
its own self-test.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Common Docs structural move - a 13-section Divio &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; tree (#2165, #2054).&lt;/strong&gt;
The split-brain &lt;code dir=&quot;auto&quot;&gt;architecture/&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt; trees are consolidated into one Divio
layout. 117 unique architecture decision records are converted from the legacy
table/bold/dash formats into metadata-in-file (MADR) records under
&lt;code dir=&quot;auto&quot;&gt;docs/adr/&amp;#x3C;era&gt;/&lt;/code&gt; with byte-invariant decision bodies; redirect stubs preserve
every moved published URL; page frontmatter is the single source of truth for the
page-inventory lockfile; and the documentation rulers are promoted to blocking
gates. The canonical changelog now lives at &lt;code dir=&quot;auto&quot;&gt;docs/changelog/CHANGELOG.md&lt;/code&gt; with
root &lt;code dir=&quot;auto&quot;&gt;CHANGELOG.md&lt;/code&gt; retained for release tooling.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter-activation-gated org-pack agents (#2211, #2156, #2166).&lt;/strong&gt; Agents
contributed by an organization doctrine pack are surfaced in dispatch, context,
and projection only when their charter artifact is active - org overlays are
applied through the charter, never raw &lt;code dir=&quot;auto&quot;&gt;org_dirs&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Single-Authority Resolution Gates - Phase 1 (#2181, #2173).&lt;/strong&gt; New architectural
gates enforce a single resolution authority for surface placement, preventing
kind-blind or primary-anchored resolvers from re-introducing split-brain reads.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-breaking-changes-4&quot;&gt;💥 Breaking Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Removed&lt;/strong&gt;: Hidden &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; alias hard-removed from 8 user-facing CLI commands
(&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;context&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;lifecycle plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lifecycle tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission-type current&lt;/code&gt;).
Passing &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; on any of these commands now yields exit code 2 with
“No such option: —feature”. Use &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; instead. (#1060)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fixed&lt;/strong&gt;: No-selector guard on all 8 commands now exits with code 2 and a readable
error message instead of a potential &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt; traceback.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-5&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME&lt;/code&gt; now isolates &lt;em&gt;all&lt;/em&gt; local Spec Kitty state, not just runtime
assets (fixes #2171).&lt;/strong&gt; Previously the variable governed runtime/Mission assets
while global sync state - sync &lt;code dir=&quot;auto&quot;&gt;config.toml&lt;/code&gt;, hosted-auth session and refresh
lock, event queues and the active queue scope, the Lamport clock, the sync
daemon (state/log/lock), and tracker credentials/cache - still resolved to the
shared default home (&lt;code dir=&quot;auto&quot;&gt;~/.spec-kitty&lt;/code&gt; on POSIX). An operator who exported
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME&lt;/code&gt; to target a separate hosted environment would silently read
and write their everyday dev session. Every global-state surface now derives
from a single authoritative root (&lt;code dir=&quot;auto&quot;&gt;specify_cli.paths.get_runtime_root&lt;/code&gt;) that
honors &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_HOME&lt;/code&gt; on Linux, macOS, and Windows. When the variable is
unset the POSIX default (&lt;code dir=&quot;auto&quot;&gt;~/.spec-kitty&lt;/code&gt;) is byte-identical to prior releases;
on Windows the surfaces that previously leaked to &lt;code dir=&quot;auto&quot;&gt;~/.spec-kitty&lt;/code&gt; are
normalized onto the platformdirs app-data base. No automatic migration of
existing &lt;code dir=&quot;auto&quot;&gt;~/.spec-kitty&lt;/code&gt; data is performed - setting the variable selects a
(possibly fresh) separate root and leaves existing default-home data in place.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; output is now safe to capture with &lt;code dir=&quot;auto&quot;&gt;2&gt;&amp;#x26;1&lt;/code&gt;.&lt;/strong&gt; The CLI correctly puts
the JSON object on stdout and diagnostics on stderr, but agents commonly invoke
&lt;code dir=&quot;auto&quot;&gt;spec-kitty … --json 2&gt;&amp;#x26;1&lt;/code&gt; and parse the &lt;em&gt;merged&lt;/em&gt; stream - so any warning/log line
on stderr (e.g. &lt;code dir=&quot;auto&quot;&gt;CharterCatalogMissWarning&lt;/code&gt;, deprecation notices) corrupted the
JSON. In &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; mode the logging bootstrap now runs in a silent mode: every root
log handler is raised above real records and a &lt;code dir=&quot;auto&quot;&gt;NullHandler&lt;/code&gt; is installed when none
exist, so Python’s &lt;code dir=&quot;auto&quot;&gt;lastResort&lt;/code&gt; WARNING→stderr fallback never fires and
&lt;code dir=&quot;auto&quot;&gt;captureWarnings&lt;/code&gt;-routed warnings are dropped too. A successful &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; run emits
only the JSON object on both stdout and the merged &lt;code dir=&quot;auto&quot;&gt;2&gt;&amp;#x26;1&lt;/code&gt; stream; genuine command
errors are still emitted as JSON on stdout by the commands themselves. (Typer
&lt;em&gt;usage&lt;/em&gt; errors for genuinely malformed invocations still print to stderr - a
separate, pre-dispatch surface.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; no longer false-positives on a mission’s &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; path
convention.&lt;/strong&gt; The accept gate’s path-convention check (&lt;code dir=&quot;auto&quot;&gt;validate_mission_paths&lt;/code&gt;)
resolved every mission-declared path against the repo root, so a mission-artifact
path like software-dev’s &lt;code dir=&quot;auto&quot;&gt;deliverables: contracts/&lt;/code&gt; (also an &lt;code dir=&quot;auto&quot;&gt;artifacts.optional&lt;/code&gt;
entry) was sought at &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;repo_root&gt;/contracts/&lt;/code&gt; and reported missing - telling the
operator to &lt;code dir=&quot;auto&quot;&gt;mkdir -p contracts/&lt;/code&gt; even though &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; existed and was committed
at &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/contracts/&lt;/code&gt;. A declared path that is a mission artifact
(member of &lt;code dir=&quot;auto&quot;&gt;mission.config.artifacts&lt;/code&gt;) is now resolved against the mission’s primary
feature dir via the canonical &lt;code dir=&quot;auto&quot;&gt;planning_read_dir&lt;/code&gt; surface (the same one
&lt;code dir=&quot;auto&quot;&gt;_missing_artifacts&lt;/code&gt; uses) - no repo-root fallback; build paths (&lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;/
&lt;code dir=&quot;auto&quot;&gt;docs/&lt;/code&gt;) stay repo-root. A residual of the #1716 / #2113 “no resolution to the repo
primary for mission artifacts” cluster.&lt;/li&gt;
&lt;li&gt;Retired the unsupported &lt;code dir=&quot;auto&quot;&gt;specify_cli.mission_read_path&lt;/code&gt; backcompat import path (#2048),
after its last production caller had moved to &lt;code dir=&quot;auto&quot;&gt;specify_cli.missions._read_path_resolver&lt;/code&gt;.
Supported callers should use &lt;code dir=&quot;auto&quot;&gt;resolve_handle_to_read_path&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;resolve_feature_dir_for_mission&lt;/code&gt;; white-box tests that need the 3-argument worker may
import &lt;code dir=&quot;auto&quot;&gt;_resolve_mission_read_path&lt;/code&gt; directly.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Retrospectives are persisted before any coordination teardown (#2119, #1771).&lt;/strong&gt;
The merge and &lt;code dir=&quot;auto&quot;&gt;close --discard&lt;/code&gt; paths now write the retrospective to its durable
home &lt;em&gt;before&lt;/em&gt; destroying the coordination worktree (persist-before-destroy, run
outside the best-effort swallow), via one shared &lt;code dir=&quot;auto&quot;&gt;coordination/teardown.py&lt;/code&gt; seam
that consolidates the previously-duplicated teardown call sites. The 6 retrospective
home-resolution sites are unified onto a single primary-anchored authority.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Handle-blind PRIMARY reads are canonicalized at the seam entry (#2136).&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;resolve_planning_read_dir&lt;/code&gt; now canonicalizes a bare &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;slug&lt;/code&gt; handle on the
caller side (keeping the &lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt; primitive blind to avoid
recursion), so a bare handle no longer resolves to a different directory than a
pre-resolved &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; one; ambiguous handles raise rather than silently pick.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Phantom &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent worktree repair&lt;/code&gt; recovery guidance replaced with the
real &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces --fix&lt;/code&gt; (#1890)&lt;/strong&gt;, enforced by a &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;-scoped,
count-agnostic grep-guard.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Coordination-topology missions read and write every artifact from the correct
surface (#2160, #2226, #2212, #2194).&lt;/strong&gt; Identity reads (&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;), merge/lane
reads (&lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;, work-package &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt;), and the implement / review / merge
loop now resolve coordination-topology planning artifacts on the primary surface
through the kind-aware resolution seam, while status stays on the coordination
worktree (closes #2185, #2186, #2187, #2115, #2140, #2183). Gate-authority
hardening stops a coordination mission from reading early/empty state and routing
an agent to the wrong next step (closes #2197, #2198, #2199, #2214).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission close --discard&lt;/code&gt; now actually tears down coordination-topology
missions (#2121)&lt;/strong&gt; instead of leaving the coordination worktree and branch behind.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission close --discard&lt;/code&gt; targets worktrees by exact name, not a &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-*&lt;/code&gt;
prefix (#2129)&lt;/strong&gt; - a sibling mission whose slug shared a prefix could previously be
discarded too (data loss).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The accept gate resolves &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; / ULID mission handles for its primary-partition
reads (#2126)&lt;/strong&gt; instead of only the fully-qualified &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; form.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;The generated charter now interpolates the project documentation policy into its
directive (#2153)&lt;/strong&gt; rather than emitting an unresolved placeholder.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt; reports unsanctioned built-in doctrine-graph overrides
(#2082)&lt;/strong&gt; and the dead override-policy symbol debt is retired.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tooling robustness:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;uv tool upgrade&lt;/code&gt; is no longer pinned to a stale rc release
(#2143); &lt;code dir=&quot;auto&quot;&gt;tomli_w&lt;/code&gt; is imported lazily so a stale environment can no longer brick the
CLI (#2132); &lt;code dir=&quot;auto&quot;&gt;run_tests&lt;/code&gt; detects the host Python interpreter (#2137); and lane
auto-rebase restores managed-artifact (&lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;WP*&lt;/code&gt;) take-theirs
classification (#2147).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-changed-5&quot;&gt;♻️ Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Extracted a shared atomic-YAML writer in &lt;code dir=&quot;auto&quot;&gt;retrospective/writer.py&lt;/code&gt; (#2125)&lt;/strong&gt;,
de-duplicating the write-temp-then-rename logic across the record-write sites, and
hoisted the &lt;code dir=&quot;auto&quot;&gt;retrospective.yaml&lt;/code&gt; filename to a single named constant.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Orchestrator no longer stalls on a coord/&lt;code dir=&quot;auto&quot;&gt;pr_bound&lt;/code&gt; mission rooted on a writable
target branch (#2118).&lt;/strong&gt; Continuing the split-brain remediation: the &lt;code dir=&quot;auto&quot;&gt;#2090&lt;/code&gt;
write-surface change routes planning artifacts (&lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;LANE_STATE&lt;/code&gt;, WP
&lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;WORK_PACKAGE_TASK&lt;/code&gt;) to the primary &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;, but the
&lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; read path still read them off the coordination worktree (which
carries only status). Under coordination topology the dependency graph came back
empty, so &lt;code dir=&quot;auto&quot;&gt;list-ready&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;mission-state&lt;/code&gt; saw no schedulable work and the orchestrator
stalled with every WP stuck at &lt;code dir=&quot;auto&quot;&gt;lane=planned&lt;/code&gt;. The orchestrator’s PRIMARY-partition
reads (&lt;code dir=&quot;auto&quot;&gt;require_lanes_json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;read_lanes_json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;build_dependency_graph&lt;/code&gt;, WP
&lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; lookup) now resolve through the kind-aware &lt;code dir=&quot;auto&quot;&gt;resolve_planning_read_dir&lt;/code&gt;
seam (primary surface for all topologies), mirroring the existing &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;
treatment in &lt;code dir=&quot;auto&quot;&gt;_resolve_merge_target_branch&lt;/code&gt;; STATUS reads (&lt;code dir=&quot;auto&quot;&gt;read_events&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;materialize&lt;/code&gt;) stay on the coordination worktree. Related: #2115 (the
implement/review/merge read-surface twin), #1716 / #1878 (coordination-topology
coherence).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission-lifecycle tooling friction batch (#2224, #2217–#2223).&lt;/strong&gt; A set of
fixes to the planning and implementation loop’s tooling surfaces, sliced from the
Doctrine-Fidelity retrospective follow-ups.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Clearer global CLI install guidance (#2231)&lt;/strong&gt; for installing &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; as a
global tool.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Internal maintainability.&lt;/strong&gt; Several god-modules were decomposed into focused
seams - &lt;code dir=&quot;auto&quot;&gt;cli/commands/doctor.py&lt;/code&gt; (#2059), &lt;code dir=&quot;auto&quot;&gt;agent/mission.py&lt;/code&gt; (#2056),
&lt;code dir=&quot;auto&quot;&gt;cli/commands/merge.py&lt;/code&gt; (#2057), and &lt;code dir=&quot;auto&quot;&gt;agent/tasks.py&lt;/code&gt; (#2058); the dead-symbol
architectural gate was hardened with a parser fix, detectors, and a teeth
self-test (#2158); and the pre-3.0 read-path shims were retired (#1057, #2048).&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;322---2026-06-24&quot;&gt;[3.2.2] - 2026-06-24&lt;/h2&gt;
&lt;p&gt;Patch release continuing the post-3.2.0 stabilization, focused on the
&lt;strong&gt;coordination/primary surface-resolution (“split-brain” / file-location)
remediation&lt;/strong&gt;. Remediation of these recent file-location issues is &lt;strong&gt;ongoing&lt;/strong&gt;, but
progress is significant enough to warrant a new release - we will continue stabilizing
the functionality. This release also adopts a coherent test-flakiness policy, hardens
CI test coverage, and decomposes the &lt;code dir=&quot;auto&quot;&gt;agent/tasks.py&lt;/code&gt; god-module.&lt;/p&gt;
&lt;h3 id=&quot;-added-5&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Single, kind- and topology-aware artifact-surface authority (split-brain remediation).&lt;/strong&gt;
Mission planning artifacts and reads/writes now resolve through one canonical surface
authority instead of drifting between the coordination worktree and the primary checkout:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;MissionTopology&lt;/code&gt; SSOT + &lt;code dir=&quot;auto&quot;&gt;routes_through_coordination&lt;/code&gt; route every decision site through
one classifier; a single read-surface resolver and a single &lt;strong&gt;write-surface&lt;/strong&gt; authority
replace the parallel derivations (#2070, single-authority topology cleanup).&lt;/li&gt;
&lt;li&gt;Planning + identity artifacts are placed by a kind-aware &lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind&lt;/code&gt; partition —
planning/identity kinds land on the primary &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; for all topologies; status/
bookkeeping stays on coordination (#2090 write-surface coherence; ADR for kind- and
topology-aware placement, #2101).&lt;/li&gt;
&lt;li&gt;The planning-lifecycle &lt;strong&gt;gate/verify commands&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, and the &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; commit) now read/commit planning
artifacts via that seam - closing the case where a coord-topology mission authored on
primary but verified from coordination (#2113; closes #2107, #2085, #2102). A default-deny
architectural literal-ban ratchet prevents the class from regrowing.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI test-coverage hardening.&lt;/strong&gt; A static gate-coverage checker + orphan ratchet flags tests
selected by zero CI gates and ratchets the backlog down (#2067, folds #1933); hot
churn-magnet orphans and &lt;code dir=&quot;auto&quot;&gt;tests/runtime/&lt;/code&gt; are now gated and run on every PR (#2108, #2109, #2111).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Maintainability:&lt;/strong&gt; the 4633-LOC &lt;code dir=&quot;auto&quot;&gt;agent/tasks.py&lt;/code&gt; god-module is decomposed into five cohesive,
one-way-import seam modules with a byte-identical CLI surface; the three planning-commit tails
are centralized through &lt;code dir=&quot;auto&quot;&gt;commit_for_mission&lt;/code&gt; (#2058 / #2114; follow-up body-thinning + FR-007
consolidation tracked in #2116).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test-flakiness handling policy (#2038):&lt;/strong&gt; a suite-wide policy (&lt;code dir=&quot;auto&quot;&gt;docs/guides/testing-flakiness.md&lt;/code&gt;)
&lt;ul&gt;
&lt;li&gt;never retry-to-green; three tiers (budget / correctness / environmental), each with one sanctioned
response - plus an env-gated, &lt;strong&gt;non-blocking&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;quarantine&lt;/code&gt; pytest marker (held out of every normal/
blocking run unless &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_RUN_QUARANTINE=1&lt;/code&gt;), distinct from the mutmut-deselection &lt;code dir=&quot;auto&quot;&gt;flaky&lt;/code&gt; marker.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-6&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Surface-resolution “split-brain” / file-location fixes (coordination vs primary).&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Mission-identity reads (mid8 / &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;) are anchored on the &lt;strong&gt;primary&lt;/strong&gt; surface, so a
coord-topology mission no longer builds a malformed coordination branch from an empty mid8 (#2091).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; aligns on the primary planning surface and the ownership-overlap validator is
&lt;strong&gt;lane/dependency-aware&lt;/strong&gt; - dependency-ordered WPs that legitimately share &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt; are no
longer falsely rejected (#2087, #2088).&lt;/li&gt;
&lt;li&gt;The read path no longer returns a stale coordination “husk” for a flattened/single-branch mission:
the stored topology gates the husk short-circuit (#2062); &lt;code dir=&quot;auto&quot;&gt;map-requirements&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;
share one WP-frontmatter read surface (#2064).&lt;/li&gt;
&lt;li&gt;Write-branch resolvers (&lt;code dir=&quot;auto&quot;&gt;get_feature_target_branch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_target_branch&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;
commit) read &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; on the &lt;strong&gt;primary&lt;/strong&gt; surface, so commits no longer silently fall back to the
repo default &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; under coordination topology.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Coord-topology orchestration: WPs reached &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; with nothing committed or integrated.&lt;/strong&gt; Three fixes,
all on the external &lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; path for coordination-topology missions:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;start-implementation&lt;/code&gt; no longer crashed with &lt;code dir=&quot;auto&quot;&gt;TypeError: transactional status batch only supports one feature/mission/wp&lt;/code&gt; - the transactional batch guard now anchors the per-request consistency check on the
first request’s canonicalized dir (matching the non-transactional sibling) instead of the resolved primary
anchor, which legitimately differs from the coord-worktree request surface.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;append-history&lt;/code&gt; now commits the WP prompt file from the coordination worktree (via the canonical
&lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt; target) instead of the primary checkout, fixing a &lt;code dir=&quot;auto&quot;&gt;SAFE_COMMIT_PATH_POLICY&lt;/code&gt;
refusal that stalled the orchestrate loop.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;start-implementation&lt;/code&gt; now allocates the &lt;strong&gt;real lane worktree&lt;/strong&gt; (lane branch on the coordination branch,
with dependency-lane tips merged) instead of returning a bare legacy path, so &lt;code dir=&quot;auto&quot;&gt;merge-mission&lt;/code&gt; has a lane
branch to integrate and dependent WPs see their dependencies’ code. Its response now carries &lt;code dir=&quot;auto&quot;&gt;lane_id&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;lane_branch&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;lane_base_ref&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;workspace_path&lt;/code&gt; now means that lane worktree. The &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;
transition is gated on a real commit existing beyond the lane base (shared with the native &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;
gate), so “done without a commit” is impossible via the API too.&lt;/li&gt;
&lt;li&gt;Both &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;orchestrator-api merge-mission&lt;/code&gt; now resolve the target branch from the
&lt;strong&gt;primary-checkout&lt;/strong&gt; meta.json (&lt;code dir=&quot;auto&quot;&gt;merge_target_branch&lt;/code&gt; then &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt;) via one shared resolver
(&lt;code dir=&quot;auto&quot;&gt;core.paths.resolve_merge_target_branch&lt;/code&gt;), instead of the coord-aware read surface - which under
coordination topology has no meta.json and made the resolver silently fall back to the repo default
(&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;), merging the mission into the wrong branch (and tripping a downstream &lt;code dir=&quot;auto&quot;&gt;SafeCommitHeadMismatch&lt;/code&gt;).
Explicit &lt;code dir=&quot;auto&quot;&gt;--target&lt;/code&gt; still wins; the repo default is only used when no mission target is set.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Non-deterministic xdist collection in &lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/shims/test_registry.py&lt;/code&gt; (#2038):&lt;/strong&gt; the
frozenset-derived parametrize sets are now &lt;code dir=&quot;auto&quot;&gt;sorted()&lt;/code&gt;, so workers collect an identical order
(root-cause fix - no retry).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-contract&quot;&gt;⚠️ Contract&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;orchestrator-api&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;CONTRACT_VERSION&lt;/code&gt; bumped to &lt;strong&gt;1.1.0&lt;/strong&gt;: additive &lt;code dir=&quot;auto&quot;&gt;start-implementation&lt;/code&gt; response fields
(&lt;code dir=&quot;auto&quot;&gt;lane_id&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lane_branch&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lane_base_ref&lt;/code&gt;) and a changed meaning for &lt;code dir=&quot;auto&quot;&gt;workspace_path&lt;/code&gt; (now the lane
worktree). New error code &lt;code dir=&quot;auto&quot;&gt;LANE_ALLOCATION_FAILED&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;321---2026-06-18&quot;&gt;[3.2.1] - 2026-06-18&lt;/h2&gt;
&lt;p&gt;Patch release stabilizing the scaffolds around the functionality introduced in 3.2.0. Remediates
blocking issues witnessed after 3.2.0; not every discovered issue is remediated here, and further
patch releases are expected in quick succession.&lt;/p&gt;
&lt;h3 id=&quot;-fixed-7&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Orchestrator coord-read of coord-only missions (#2016):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;orchestrator_api&lt;/code&gt; now resolves a mission that
exists only as a coordination worktree (no primary &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;) by adopting the canonical mid8 cascade
(&lt;code dir=&quot;auto&quot;&gt;meta.mid8&lt;/code&gt; → declared &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; tail) instead of a strict-only reimplementation that
returned &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt;. Legacy non-coord missions keep their primary-read path; genuinely unresolvable handles still
fail closed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter status/sync/preflight coherence (#2009, epic #2007/C2):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;charter status --json&lt;/code&gt; no longer crashes on
a non-JSON-safe &lt;code dir=&quot;auto&quot;&gt;datetime&lt;/code&gt; in the bundle metadata; the DRG “&lt;code dir=&quot;auto&quot;&gt;built_in_only&lt;/code&gt; + stale &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt; residue” state
is now a non-blocking read-time diagnostic instead of a preflight-blocking &lt;code dir=&quot;auto&quot;&gt;invalid&lt;/code&gt;; and a BOM/CRLF hash
divergence between &lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;/freshness (which produced a &lt;code dir=&quot;auto&quot;&gt;noop&lt;/code&gt;-despite-stale &lt;code dir=&quot;auto&quot;&gt;charter sync&lt;/code&gt;) is fixed
by canonicalizing line endings/BOM in the single &lt;code dir=&quot;auto&quot;&gt;charter.hasher.hash_content&lt;/code&gt; seam. Regression tests pin the
already-landed status side-effect-free and hash-unification fixes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Green the architectural CI gate (#2025):&lt;/strong&gt; corrected pytest markers on a subprocess/git test, removed a
mission-diff-scoped test that did not belong on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, and made the architectural ratchet composite keys
interpreter-stable (Python 3.11 ↔ 3.12 f-string tokenization), re-greening the &lt;code dir=&quot;auto&quot;&gt;tests/architectural/**&lt;/code&gt; shard
that went red when 3.2.0’s gate-un-mask first ran on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;merge.py decomposition, slice 1 (#2027, epic #2026):&lt;/strong&gt; extracted the &lt;code dir=&quot;auto&quot;&gt;baseline_merge_commit&lt;/code&gt; record/verify
cluster from the oversized &lt;code dir=&quot;auto&quot;&gt;cli/commands/merge.py&lt;/code&gt; into a dedicated &lt;code dir=&quot;auto&quot;&gt;specify_cli/merge/baseline.py&lt;/code&gt;,
behavior-preserving with back-compat re-exports (public + legacy private names).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter constant single-sourced:&lt;/strong&gt; the &lt;code dir=&quot;auto&quot;&gt;_GRAPH_FILENAME&lt;/code&gt; value, previously duplicated across three modules,
now resolves from one leaf &lt;code dir=&quot;auto&quot;&gt;charter.synthesizer._constants&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-security-follow-up&quot;&gt;🐛 Fixed (security follow-up)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;SonarCloud + Dependabot:&lt;/strong&gt; re-exported the charter package helper named in &lt;code dir=&quot;auto&quot;&gt;__all__&lt;/code&gt;, hardened merge
bookkeeping projection so status-surface paths cannot resolve outside trusted repo roots, and refreshed locked
crypto/tooling dependencies to patched releases (&lt;code dir=&quot;auto&quot;&gt;cryptography 49.0.0&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;pip 26.1.2&lt;/code&gt;) so the security gates stay
clean.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320---2026-06-16&quot;&gt;[3.2.0] - 2026-06-16&lt;/h2&gt;
&lt;h3 id=&quot;-added---changed&quot;&gt;✨ Added / 🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Stable 3.2.0 release of the mission-runtime, profile-invocation, tool-surface,
branch-authority, and coordination-worktree line after the rc45 validation cycle.
This promotes the accumulated 3.2.0 release-candidate fixes to the default PyPI
channel.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc45---2026-06-15&quot;&gt;[3.2.0rc45] - 2026-06-15&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-8&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Agent profile projection plugin production follow-through (PR #1975):&lt;/strong&gt; Claude Code plugin bundles now emit
strict-validator-compatible &lt;code dir=&quot;auto&quot;&gt;skills&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;agents&lt;/code&gt; component paths and a valid empty hooks record; init/upgrade
auto-repair no longer builds optional disabled plugin bundle artifacts or silently writes Amazon Q user-global
agent profiles; docs inventory, lockfile, and Roo-deprecation test expectations are refreshed for the CI gates.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc44---2026-06-14&quot;&gt;[3.2.0rc44] - 2026-06-14&lt;/h2&gt;
&lt;h3 id=&quot;-added-6&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;ToolSurfaceContract unified registry (mission &lt;code dir=&quot;auto&quot;&gt;tool-surface-contract-01KV2K2P&lt;/code&gt;, PR #1948):&lt;/strong&gt;
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/tool_surface/&lt;/code&gt; is now the bounded context for configured tool surface policy.
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor tool-surfaces --json&lt;/code&gt; reports stable findings and repair commands across command
skills, doctrine skills, session/context surfaces, native agent profile projections, and plugin
bundle surfaces. &lt;code dir=&quot;auto&quot;&gt;doctor skills --json&lt;/code&gt; remains backward-compatible, legacy &lt;code dir=&quot;auto&quot;&gt;agent config&lt;/code&gt; flows
still work through the new contract, and fresh clones now get actionable generated-surface repair
plans instead of silent missing &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt; drift.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Branch-strategy recommendation in &lt;code dir=&quot;auto&quot;&gt;/specify&lt;/code&gt; (issue #765):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission branch-context&lt;/code&gt;
now resolves the repository’s primary branch and emits a recommendation payload (&lt;code dir=&quot;auto&quot;&gt;primary_branch&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;current_is_primary&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;recommended_strategy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;). The software-dev specify prompt consumes it to
&lt;strong&gt;proactively&lt;/strong&gt; recommend starting on a dedicated feature branch; &lt;code dir=&quot;auto&quot;&gt;mission create --start-branch&lt;/code&gt; now
creates/switches before any mission artifacts are written when the operator is on the primary branch and
expects a later PR; staying on the current branch remains an explicit, supported choice (wiring &lt;code dir=&quot;auto&quot;&gt;--pr-bound&lt;/code&gt;
branch-strategy gate into the operator flow). The recommendation fields are additive and opt-in: callers
that do not resolve a primary branch receive the byte-identical legacy branch contract.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-9&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Docs: corrected the retired &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow implement&lt;/code&gt; command (issue #1874):&lt;/strong&gt; the
&lt;code dir=&quot;auto&quot;&gt;agent workflow&lt;/code&gt; command group no longer exists (the canonical form is &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;… review&lt;/code&gt;). Updated the user-facing &lt;code dir=&quot;auto&quot;&gt;docs/how-to/implement-work-package.md&lt;/code&gt; and the
&lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt; testing note. (The same stale command also appears in the PowerShell toolguide and the
documentation/research per-WP task-prompt templates; those are rendered into the twelve-agent command
snapshots, whose baselines are already drifted on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;, so that replacement is left to the
cli-reference-audit sweep which can regenerate the baselines in one pass.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; no longer churns &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt; on a no-op (issue #1871):&lt;/strong&gt; the “stamp
&lt;code dir=&quot;auto&quot;&gt;last_upgraded_at&lt;/code&gt; only on material change” rule lived in three divergent idioms, and the migrations-applied
root path plus &lt;code dir=&quot;auto&quot;&gt;_stamp_schema_version&lt;/code&gt; rewrote &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt; (and advanced the timestamp / mtime) even when
every migration was already recorded. &lt;code dir=&quot;auto&quot;&gt;ProjectMetadata.save()&lt;/code&gt; now does a &lt;strong&gt;masked compare-before-write&lt;/strong&gt;
(skipping the write when only the volatile &lt;code dir=&quot;auto&quot;&gt;last_upgraded_at&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; would change) and
&lt;code dir=&quot;auto&quot;&gt;_stamp_schema_version&lt;/code&gt; skips its re-dump when the rendered bytes already match disk. A genuine
version/migration/environment change still writes with a fresh timestamp; a no-op upgrade - including across a
fully-recorded version range, on both the root and worktree paths - is now zero writes. This closes the class
at the write boundary for upgrade/doctor/regeneration instead of adding a fourth per-path guard.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;agent tasks map-requirements --json&lt;/code&gt; no longer crashes on auto-commit (issue #1891, Finding 1):&lt;/strong&gt; the
command stored the &lt;code dir=&quot;auto&quot;&gt;CommitResult&lt;/code&gt; returned by &lt;code dir=&quot;auto&quot;&gt;safe_commit()&lt;/code&gt; directly in the &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; payload, so on the
auto-commit success path &lt;code dir=&quot;auto&quot;&gt;json.dumps&lt;/code&gt; failed with &lt;em&gt;“Object of type CommitResult is not JSON serializable”&lt;/em&gt; —
the mapping succeeded but agents got an unparseable error instead of the result. &lt;code dir=&quot;auto&quot;&gt;committed&lt;/code&gt; is now a bool
and the resulting &lt;code dir=&quot;auto&quot;&gt;commit_sha&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;null&lt;/code&gt;) is exposed alongside it. (Findings 2 and 3 - &lt;code dir=&quot;auto&quot;&gt;agent action implement --json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; JSON preamble - are tracked separately.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;accept --lenient&lt;/code&gt; now relaxes mission path conventions (issue #1892):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;agent mission accept&lt;/code&gt; validated a mission’s declared &lt;code dir=&quot;auto&quot;&gt;paths&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;contracts/&lt;/code&gt; for software-dev)
unconditionally, so repos with a non-default layout (e.g. a Go service using &lt;code dir=&quot;auto&quot;&gt;internal/&lt;/code&gt; with no top-level
&lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;) failed acceptance even with &lt;code dir=&quot;auto&quot;&gt;--lenient&lt;/code&gt; - the only workaround was creating throwaway empty
directories. Path conventions now block only in strict mode; under &lt;code dir=&quot;auto&quot;&gt;--lenient&lt;/code&gt; an unmet convention is
surfaced as a non-blocking warning. (A per-project &lt;code dir=&quot;auto&quot;&gt;paths&lt;/code&gt; override remains a possible follow-up.)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Name-vs-authority remediation (mission #133; closes #1889, #1860, #1865, #1866, #1867, #1863, #1896, #1898, #1904, #1684, #1906):&lt;/strong&gt; (#1884/#1883/#1885 were independently fixed by PR #1910 and are verified-already-fixed here, not re-closed)
binds the two remaining “a name/string shape is trusted as authority without cross-checking the declared authority”
seams and ratchets them closed, and clears the live 3.2.0 release-blocker P0s rooted in that class. Topology
authority seam (&lt;code dir=&quot;auto&quot;&gt;WorktreeTopology&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;classify_worktree_topology&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;is_registered_coord_worktree&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;coordination/surface_resolver.py&lt;/code&gt;, wrapping the &lt;code dir=&quot;auto&quot;&gt;git worktree list --porcelain&lt;/code&gt; registry) and branch-identity
authority seam (&lt;code dir=&quot;auto&quot;&gt;mission_branch_name_required&lt;/code&gt; + structured &lt;code dir=&quot;auto&quot;&gt;BranchIdentityUnresolved&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;lanes/branch_naming.py&lt;/code&gt;,
dual-era: legacy &lt;code dir=&quot;auto&quot;&gt;\d{3}-&lt;/code&gt; AND mid8 names both resolve) replace the convention predicates at their consumer sites;
the &lt;code dir=&quot;auto&quot;&gt;(slug.replace(&apos;-&apos;,&apos;&apos;)+&quot;00000000&quot;)[:8]&lt;/code&gt; mid8-fabrication idiom is eradicated (routed through
&lt;code dir=&quot;auto&quot;&gt;resolve_transaction_mid8&lt;/code&gt;, fail-closed). &lt;strong&gt;P0s fixed:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;setup-plan&lt;/code&gt;’s committed-spec gate verifies against the
placement authority’s ref not primary HEAD (#1884); the accept gate is idempotent across all modes via
accept-owned-path exclusion (#1883); unresolvable mission handles raise a structured &lt;code dir=&quot;auto&quot;&gt;MissionNotFoundError&lt;/code&gt;
(code + next_step, #1911) instead of a silent &lt;code dir=&quot;auto&quot;&gt;mission=unknown&lt;/code&gt; stub (#1885 residual). #1889’s coordination-branch-deleted
case becomes a distinct loud &lt;code dir=&quot;auto&quot;&gt;CoordinationBranchDeleted&lt;/code&gt; (decision-table row R3). An architectural ratchet
(&lt;code dir=&quot;auto&quot;&gt;test_topology_resolution_boundary.py&lt;/code&gt;) keeps coord predicates, unbackstopped &lt;code dir=&quot;auto&quot;&gt;kitty/mission-{slug}&lt;/code&gt; composes, and
the fabrication idiom from regrowing outside the blessed seam modules. Doctrine refinements (#1865/#1866/#1867) and
the DRG extractor styleguide/toolguide &lt;code dir=&quot;auto&quot;&gt;references&lt;/code&gt; walk (#1863) ride along; the authority-path default flips
&lt;code dir=&quot;auto&quot;&gt;architecture/2.x/adr&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;3.x/adr&lt;/code&gt;. &lt;strong&gt;Cross-lane dependency code propagation (#1684):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;allocate_lane_worktree&lt;/code&gt;
now merges approved dependency-lane tips (fresh creation + lane re-entry) so a dependent WP in a sibling lane sees
its approved dependency’s code, instead of branching from the bare mission branch.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_branch_exists&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;ref_exists&lt;/code&gt; consolidation (#1904):&lt;/strong&gt; the duplicated &lt;code dir=&quot;auto&quot;&gt;git rev-parse --verify&lt;/code&gt; branch/ref
existence idiom across &lt;code dir=&quot;auto&quot;&gt;coordination/status_transition.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;missions/_create.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lanes/worktree_allocator.py&lt;/code&gt;,
and &lt;code dir=&quot;auto&quot;&gt;lanes/merge.py&lt;/code&gt; is unified into &lt;code dir=&quot;auto&quot;&gt;lanes/_git.py&lt;/code&gt; (env-parameterized so the merge path’s environment composes).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-maintenance&quot;&gt;🧹 Maintenance&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;SonarCloud hygiene on mission #133 surfaces:&lt;/strong&gt; raised new-code coverage on the authored seam/allocator/query
files; reduced cognitive-complexity (extract-method) and duplicate-literal smells across &lt;code dir=&quot;auto&quot;&gt;doctrine.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;sync/daemon.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;sync/owner.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;drg/validator.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;org_charter.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_read_path_resolver.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;core/worktree.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;agent/workflow.py&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;upgrade.py&lt;/code&gt; (all behavior-preserving); regenerated stale codex/vibe command-skill
snapshots to match the advanced templates (PR #1897 finding).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upgrade no longer re-records not-applicable migrations (issue #1872):&lt;/strong&gt; a migration whose &lt;code dir=&quot;auto&quot;&gt;detect()&lt;/code&gt;
is &lt;code dir=&quot;auto&quot;&gt;False&lt;/code&gt; was re-appended as a &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt; / “Not applicable” &lt;code dir=&quot;auto&quot;&gt;MigrationRecord&lt;/code&gt; on every &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;
run over the same version range, growing &lt;code dir=&quot;auto&quot;&gt;applied_migrations&lt;/code&gt; without bound and - for worktrees, after
#1857 - bumping &lt;code dir=&quot;auto&quot;&gt;last_upgraded_at&lt;/code&gt; on no-op runs. &lt;code dir=&quot;auto&quot;&gt;ProjectMetadata.record_migration()&lt;/code&gt; is now idempotent
(an identical &lt;code dir=&quot;auto&quot;&gt;(id, result)&lt;/code&gt; record is not re-appended) and the worktree upgrade path only marks metadata
dirty when a new record was actually written, restoring stable &lt;code dir=&quot;auto&quot;&gt;last_upgraded_at&lt;/code&gt; for no-op re-runs. A
genuine &lt;code dir=&quot;auto&quot;&gt;failed → success&lt;/code&gt; transition still records the new result.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Coordination &amp;#x26; Merge stabilization (mission 131; closes #1826, #1861 Part 1, residuals of #1833/#1814/#1736/#1735):&lt;/strong&gt;
merge-pipeline ref advances now resync any worktree checked out on the advanced branch (shared
&lt;code dir=&quot;auto&quot;&gt;git/ref_advance.py&lt;/code&gt; helper with a no-raw-&lt;code dir=&quot;auto&quot;&gt;update-ref&lt;/code&gt; architectural ratchet), refusing loudly - never
resetting - when the worktree holds uncommitted state; the safe-commit backstop message names the diverged
worktree/ref/state; &lt;code dir=&quot;auto&quot;&gt;finalize-tasks --validate-only&lt;/code&gt; no longer switches the git checkout; task finalization
cleans its own primary-checkout residue (operator files untouched); workspace resolution treats non-worktree
“husk” directories under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; as structured failures instead of silently running git against the
primary repo, with a new &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces [--fix]&lt;/code&gt; check for self-serve recovery - &lt;strong&gt;note:&lt;/strong&gt;
pre-existing husks that previously failed silently now produce explicit errors; run
&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor workspaces --fix&lt;/code&gt; once to clean them; retrospective gating reads route through the
canonical status surface (AC10 ratchet); &lt;code dir=&quot;auto&quot;&gt;upgrade --dry-run&lt;/code&gt; no longer prints a success line implying
changes were applied; merge-driver hardening (single &lt;code dir=&quot;auto&quot;&gt;_make_merge_env()&lt;/code&gt; authority, narrowed exception
mask, deterministic mixed-timestamp event-log sort).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Protected-branch guard capability honesty (PR #1850 review):&lt;/strong&gt; the bool→capability conversion had
re-opened protected-ref commits from production flows - three sites asserted &lt;code dir=&quot;auto&quot;&gt;GuardCapability.TEST_MODE&lt;/code&gt;
(legacy workflow commit, baseline-artifact commit, finalize-tasks bootstrap) and six non-merge flows
borrowed &lt;code dir=&quot;auto&quot;&gt;MERGE_BOOKKEEPING&lt;/code&gt; (move-task, mark-status, map-requirements, decision-log, op-record). All
now assert &lt;code dir=&quot;auto&quot;&gt;STANDARD&lt;/code&gt;; protected destinations refuse, and refusals degrade gracefully (decision events
and Op records are preserved on disk, nothing lands on the protected ref). &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_TEST_MODE&lt;/code&gt; no
longer waives the command-level protected-branch prechecks - only the documented operator hatch
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS&lt;/code&gt; does - and the coordination gate now computes the same
hatch-aware &lt;code dir=&quot;auto&quot;&gt;ProtectionState&lt;/code&gt; as &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt;, so the two can no longer disagree. Ratcheted by
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_guard_capability_call_sites.py&lt;/code&gt; (capability→flow allowlist; &lt;code dir=&quot;auto&quot;&gt;TEST_MODE&lt;/code&gt; has
zero &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; callers) and &lt;code dir=&quot;auto&quot;&gt;tests/git/test_guard_capability_regression.py&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission handle canonicalization completes at every CLI write boundary (PR #1850 review):&lt;/strong&gt; bare mid8,
numeric-prefix, and full-ULID handles now resolve to the identical canonical &lt;code dir=&quot;auto&quot;&gt;mission_slug&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;, status surfaces, and placement (ref and kind) as the full slug - across
&lt;code dir=&quot;auto&quot;&gt;resolve_status_surface_with_anchor&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve_placement_only&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MissionStatus.load&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;_find_mission_slug&lt;/code&gt; (agent tasks/status/workflow), &lt;code dir=&quot;auto&quot;&gt;agent decision open&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge --mission&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;spec-kitty next --mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;plan --mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission run/close --mission&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;research --mission&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;context resolve&lt;/code&gt; (persisted &lt;code dir=&quot;auto&quot;&gt;authoritative_ref&lt;/code&gt;). No more
wrong-but-plausible &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mid8&gt;/&lt;/code&gt; paths, &lt;code dir=&quot;auto&quot;&gt;legacy-&amp;#x3C;mid8&gt;&lt;/code&gt; identities, split-brain runtime
runs or SaaS sync namespaces keyed by the raw handle, or &lt;code dir=&quot;auto&quot;&gt;close --discard&lt;/code&gt; silently leaving lane
branches/worktrees behind. Pinned by
&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/missions/test_handle_equivalence_matrix.py&lt;/code&gt; (78 parity tests).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Sync daemon reaper is scoped to its daemon root, not just the interpreter (PR #1850 review):&lt;/strong&gt; the
spawner embeds the resolved daemon state root and spawn-time interpreter identity as inert argv markers;
the reaper kills only on marker + spawn-signature + interpreter-identity match and conservatively skips
unmarked or unidentifiable processes. Fixes both the cross-&lt;code dir=&quot;auto&quot;&gt;$HOME&lt;/code&gt; over-kill and the macOS
framework-Python inertness (where the re-exec rewrites &lt;code dir=&quot;auto&quot;&gt;exe()&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;argv[0]&lt;/code&gt; to the &lt;code dir=&quot;auto&quot;&gt;Python.app&lt;/code&gt; stub).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CI &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; filter covers the canonical runtime:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;src/runtime/next/**&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/**&lt;/code&gt;
now trigger the next suites and count toward diff-coverage critical paths (previously only the
deprecated &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/next/&lt;/code&gt; shim was mapped, so &lt;code dir=&quot;auto&quot;&gt;integration-tests-next&lt;/code&gt; skipped on
canonical-runtime changes).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;StatusReadPathNotFound&lt;/code&gt; no longer escapes &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt;’s single-error contract:&lt;/strong&gt; the fail-closed
refusal is translated to &lt;code dir=&quot;auto&quot;&gt;ActionContextError&lt;/code&gt; (error code and message preserved) at all three resolution
boundaries and handled in the transactional status path; &lt;code dir=&quot;auto&quot;&gt;MissionStatus.load&lt;/code&gt; keeps its established
&lt;code dir=&quot;auto&quot;&gt;CoordAuthorityUnavailable&lt;/code&gt; shape for every handle form in the fail-closed coordination window.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Repo hygiene:&lt;/strong&gt; per-machine &lt;code dir=&quot;auto&quot;&gt;.kittify/legacy-warning-shown-*&lt;/code&gt; marker files untracked and gitignored.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc43---2026-06-11&quot;&gt;[3.2.0rc43] - 2026-06-11&lt;/h2&gt;
&lt;h3 id=&quot;-added---changed-1&quot;&gt;✨ Added / 🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Tooling stability &amp;#x26; guard coherence (mission 01KTRC04, slice of #1619, closes the #1796 cluster):&lt;/strong&gt;
the safe-commit / protected-branch guard is ONE mechanism - a pure Shared-Kernel policy module
(&lt;code dir=&quot;auto&quot;&gt;core/commit_guard.evaluate(target, protection_state, capability) -&gt; GuardVerdict&lt;/code&gt;) behind the single
&lt;code dir=&quot;auto&quot;&gt;git/commit_helpers.safe_commit&lt;/code&gt; facade. The five legacy privilege channels (message-prefix allowlist,
&lt;code dir=&quot;auto&quot;&gt;allow_protected_branch_in_test_mode&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;allow_completed_op_on_protected_branch&lt;/code&gt;, op-record file-content
exception, env hatches) are DELETED; protected flows assert an explicit &lt;code dir=&quot;auto&quot;&gt;GuardCapability&lt;/code&gt; at the call
site (never derived from message/file/env). Operator escape hatch &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ALLOW_PROTECTED_BRANCH_COMMITS&lt;/code&gt;
retained. Permanently ratcheted by &lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_safe_commit_import_boundary.py&lt;/code&gt; (#1355).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Planning placement single authority (#1777/#1784/#1631/#1334):&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;mission_runtime.resolve_placement_only&lt;/code&gt;
is the one commit-destination authority for planning paths; &lt;code dir=&quot;auto&quot;&gt;_resolve_planning_branch&lt;/code&gt; destination
authority retired. Legit spec/plan commits on protected branches route to the resolved destination with
ZERO guard relaxation; the finalize-tasks branch catch-22 is gone (idempotent re-runs).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;safe-commit ergonomics (#1820/#1330):&lt;/strong&gt; directory arguments expand to contained dirty files with a
per-file report; explicit &lt;code dir=&quot;auto&quot;&gt;--to-branch&lt;/code&gt; honored; &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_INFER_DESTINATION_REF&lt;/code&gt; retired.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt; verdict derived from the structured &lt;code dir=&quot;auto&quot;&gt;analysis-findings/v1&lt;/code&gt; frontmatter table - prose
substring counting removed (#1819); severity vocabulary reuses &lt;code dir=&quot;auto&quot;&gt;SEVERITY_ORDER&lt;/code&gt; (no parallel model).&lt;/li&gt;
&lt;li&gt;Carried &lt;code dir=&quot;auto&quot;&gt;StatusSurfaceFragment&lt;/code&gt; threaded through &lt;code dir=&quot;auto&quot;&gt;MissionStatus.load&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;status_transition&lt;/code&gt; (#1821).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;doctor.py&lt;/code&gt; doctrine profile-health rendering extracted to &lt;code dir=&quot;auto&quot;&gt;_profile_health_render.py&lt;/code&gt; (#1623 slice).&lt;/li&gt;
&lt;li&gt;DRG provenance is a declared typed field on &lt;code dir=&quot;auto&quot;&gt;DRGNode&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;DRGEdge&lt;/code&gt;; the &lt;code dir=&quot;auto&quot;&gt;object.__setattr__&lt;/code&gt; sidecar is
deleted; &lt;code dir=&quot;auto&quot;&gt;graph.yaml&lt;/code&gt; byte-stable (#1624).&lt;/li&gt;
&lt;li&gt;ADR 2026-06-03-2 addendum: Strangler &lt;strong&gt;Step 7 delivered&lt;/strong&gt; (CommitTarget consumed by safe_commit).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc42---2026-06-11&quot;&gt;[3.2.0rc42] - 2026-06-11&lt;/h2&gt;
&lt;h3 id=&quot;-changed-1&quot;&gt;💥 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Op record schema v2 (WP01, do-dispatch-open-op-lifecycle)&lt;/strong&gt;: the dual-purpose
&lt;code dir=&quot;auto&quot;&gt;InvocationRecord&lt;/code&gt; model is split into frozen &lt;code dir=&quot;auto&quot;&gt;OpStartedEvent&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;OpCompletedEvent&lt;/code&gt; Pydantic v2 models. Completed events now require &lt;code dir=&quot;auto&quot;&gt;outcome&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;closed_by&lt;/code&gt; and carry no started-only fields; blank-default records are
unrepresentable. Readers of &lt;code dir=&quot;auto&quot;&gt;kitty-ops/*.jsonl&lt;/code&gt; warn-and-skip legacy (pre-v2)
lines, pointing at &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;parse_op_event&lt;/code&gt; raises a catchable
&lt;code dir=&quot;auto&quot;&gt;LegacyRecordError&lt;/code&gt; for them. &lt;code dir=&quot;auto&quot;&gt;spec-kitty invocations list&lt;/code&gt; now shows
&lt;code dir=&quot;auto&quot;&gt;outcome&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;closed_by&lt;/code&gt; for closed Ops. &lt;code dir=&quot;auto&quot;&gt;artifact_link&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;commit_link&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;glossary_checked&lt;/code&gt; event shapes are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Breaking - standalone dispatch no longer auto-closes its Op as &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt;
(dispatch-open-op-lifecycle)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty dispatch&lt;/code&gt; opens the Op and loads
governance context; the working agent closes it via
&lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete --invocation-id &amp;#x3C;id&gt; --outcome &amp;#x3C;done|failed|abandoned&gt;&lt;/code&gt; (completed-event schema v2: &lt;code dir=&quot;auto&quot;&gt;outcome&lt;/code&gt;
required, new &lt;code dir=&quot;auto&quot;&gt;closed_by&lt;/code&gt; field). New &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops --close-stale&lt;/code&gt;
sweeps stale open Ops closed as &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;closed_by: doctor_sweep&lt;/code&gt;).
Legacy &lt;code dir=&quot;auto&quot;&gt;kitty-ops&lt;/code&gt; records are migrated (rewrite-or-delete) by
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;. Claude Code session presence now lists open Ops at
session start, a new &lt;code dir=&quot;auto&quot;&gt;Stop&lt;/code&gt; hook (&lt;code dir=&quot;auto&quot;&gt;spec-kitty session-stop&lt;/code&gt;) reminds at
session end, and the doctrine skill pack / standalone command templates
document the open→work→close contract.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-10&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Hardened the v2 Op migration and readers: &lt;code dir=&quot;auto&quot;&gt;spec-kitty invocations list&lt;/code&gt; skips
dangling &lt;code dir=&quot;auto&quot;&gt;ops-index.jsonl&lt;/code&gt; rows after unsalvageable Op files are deleted, and
migration idempotency now treats only v2-parseable &lt;code dir=&quot;auto&quot;&gt;mode_of_work&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;closed_by&lt;/code&gt;
values as already migrated.&lt;/li&gt;
&lt;li&gt;Preserved machine-readable output for standalone dispatch &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; by
suppressing post-payload inline glossary notices on JSON paths; rich output
still shows the notices.&lt;/li&gt;
&lt;li&gt;Updated the rich standalone-dispatch close hint to include the now-required
&lt;code dir=&quot;auto&quot;&gt;--outcome &amp;#x3C;done|failed|abandoned&gt;&lt;/code&gt; flag.&lt;/li&gt;
&lt;li&gt;Replaced stale short profile aliases in shipped mission-runtime templates
(&lt;code dir=&quot;auto&quot;&gt;researcher&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;architect&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;planner&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implementer&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reviewer&lt;/code&gt;) with the
canonical shipped profile IDs, preventing fresh &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; runs from
blocking on missing invocation profiles.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; now skips empty post-merge bookkeeping commits after a
successful lane merge instead of failing the command after the target branch
has already been updated.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added---changed-2&quot;&gt;✨ Added / 🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Execution-context unification (mission 01KTPKST, slice of #1619/#1666):&lt;/strong&gt; structurally drained the
coord-vs-primary split-brain class. One &lt;code dir=&quot;auto&quot;&gt;MissionExecutionContext&lt;/code&gt; (doc-09 fragment/op-composite +
&lt;code dir=&quot;auto&quot;&gt;CommitTarget&lt;/code&gt;) resolved once and threaded through all command surfaces; status owned by the
Mission-Management OHS facade. Collapsed the duplicate read-path resolver, the two worktree-pointer
parsers, and the three sync-daemon orphan-reapers; &lt;code dir=&quot;auto&quot;&gt;materialize_if_stale&lt;/code&gt; now skips during git ops
(no status clobber on rebase); dashboard reads are write-free (&lt;code dir=&quot;auto&quot;&gt;materialize_snapshot&lt;/code&gt;); sync-daemon
singleton enforced one-per-host/auth-scope; occurrence-map gained multi-path &lt;code dir=&quot;auto&quot;&gt;moves:&lt;/code&gt; (backward-compatible);
retrospect record relocated to a tracked home (committable). Adds a dual-CWD + flattened-topology parity
ratchet (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_execution_context_parity.py&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Drains #1814, #1816, #1789, #1071, #1062, #1572, #1737, #1357, #1735, #1771, #1736, #1770, #1764, #1815,
#1622 (partial); follow-ups #1819/#1820/#1821 filed.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc41---2026-06-08&quot;&gt;[3.2.0rc41] - 2026-06-08&lt;/h2&gt;
&lt;h3 id=&quot;-added-7&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Introduced canonical &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; umbrella package (&lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/&lt;/code&gt;) as the sole
sanctioned execution-state resolver; &lt;code dir=&quot;auto&quot;&gt;resolve_action_context&lt;/code&gt; is now the single entry point
for all mission/WP context resolution (epic #1666 slice 2, ADR &lt;code dir=&quot;auto&quot;&gt;2026-06-07-1-execution-state-canonical-surface.md&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;_branch_trees_equal&lt;/code&gt; predicate in merge command for content-based squash-resume
idempotency (FR-037); replaces ancestry-based &lt;code dir=&quot;auto&quot;&gt;rev-list&lt;/code&gt; check that failed after squash merges.&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;path_is_under_worktrees&lt;/code&gt; guard to &lt;code dir=&quot;auto&quot;&gt;_stage_finalize_artifacts_in_coord_worktree&lt;/code&gt;
(FR-035); finalize/implement can no longer stage sources already under &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;, preventing
nested-worktree path pollution on coord-topology missions (#1772 Bug 0).&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;rebuild_mission_event_log&lt;/code&gt; canonical rebuild entry point for migration paths (#1754).&lt;/li&gt;
&lt;li&gt;New ADR &lt;code dir=&quot;auto&quot;&gt;2026-06-07-1-execution-state-canonical-surface.md&lt;/code&gt; documenting the sole-resolver
boundary and migration contract.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-2&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;status/&lt;/code&gt; facade now enforced repo-wide: ~219 deep &lt;code dir=&quot;auto&quot;&gt;specify_cli.status.&amp;#x3C;sub&gt;&lt;/code&gt; imports
collapsed to 21 across &lt;code dir=&quot;auto&quot;&gt;src/specify_cli&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;src/runtime&lt;/code&gt; (724 files covered by boundary test).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_read_path.py&lt;/code&gt; converted to a thin compatibility shim over the canonical
&lt;code dir=&quot;auto&quot;&gt;specify_cli.missions._read_path_resolver&lt;/code&gt;; duplicate resolver implementation eliminated.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_runtime.__all__&lt;/code&gt; trimmed to the 4-symbol public contract; historical first-party
names (&lt;code dir=&quot;auto&quot;&gt;ActionContext&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ActionName&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ACTION_NAMES&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_resolve_mission_slug&lt;/code&gt;) served via
&lt;code dir=&quot;auto&quot;&gt;__getattr__&lt;/code&gt; without appearing in the public surface.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;resolve_action_context&lt;/code&gt; top-level imports moved to deferred (inside function bodies),
breaking the &lt;code dir=&quot;auto&quot;&gt;mission_runtime → dependency_graph → status → uninitialized_hint → dependency_graph&lt;/code&gt;
circular import; cold &lt;code dir=&quot;auto&quot;&gt;import mission_runtime&lt;/code&gt; now works without prior status initialization.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;FrontmatterSource&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;resolve_wp_manifests&lt;/code&gt; routed through single ownership ports (#1757).&lt;/li&gt;
&lt;li&gt;Mission-identity snapshot carry-through added to &lt;code dir=&quot;auto&quot;&gt;runtime_bridge.py&lt;/code&gt; (#1663).&lt;/li&gt;
&lt;li&gt;Full-sequence parity ratchet (&lt;code dir=&quot;auto&quot;&gt;test_execution_context_parity.py&lt;/code&gt;) extended to cover
&lt;code dir=&quot;auto&quot;&gt;next → implement → move-task → review → status&lt;/code&gt; across three execution modes plus a
negative control (#1672).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-11&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Coord-topology merge hardening (#1772): &lt;code dir=&quot;auto&quot;&gt;path_is_under_worktrees&lt;/code&gt; predicate applied at
staging; &lt;code dir=&quot;auto&quot;&gt;_lane_already_integrated&lt;/code&gt; tree-diff gate (fail-loud on zero-diff squash); in-branch
status validation; &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; check for tracked &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; content.&lt;/li&gt;
&lt;li&gt;Cold import of &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; no longer raises &lt;code dir=&quot;auto&quot;&gt;ImportError: cannot import name &apos;detect_cycles&apos; from partially initialized module&lt;/code&gt; (circular import via status facade).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;mission_runtime_api.md&lt;/code&gt; contract corrected to match actual &lt;code dir=&quot;auto&quot;&gt;resolve_action_context&lt;/code&gt; signature
(&lt;code dir=&quot;auto&quot;&gt;action&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;feature&lt;/code&gt; keyword args, not positional &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;status_boundary.md&lt;/code&gt; updated to document &lt;code dir=&quot;auto&quot;&gt;workspace/context.py&lt;/code&gt; as a permanent third
exemption (import-time cycle breaker); contract and test allow-list now in sync.&lt;/li&gt;
&lt;li&gt;Raw &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; path construction eliminated from call sites; all paths go through the
single resolver (FR-009).&lt;/li&gt;
&lt;li&gt;Closed: #1673, #1664, #1672, #1663, #1757, #1754, #1772.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc40---2026-06-07&quot;&gt;[3.2.0rc40] - 2026-06-07&lt;/h2&gt;
&lt;h3 id=&quot;-added-8&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Introduced &lt;code dir=&quot;auto&quot;&gt;Lane.GENESIS&lt;/code&gt; pseudo-state and a canonical &lt;code dir=&quot;auto&quot;&gt;WPState&lt;/code&gt; State-pattern FSM in
&lt;code dir=&quot;auto&quot;&gt;specify_cli.status.wp_state&lt;/code&gt;, making the FSM the single source of truth for WP lanes,
edges, and transitions (mission &lt;code dir=&quot;auto&quot;&gt;wp-lane-state-machine-fsm-01KTGZAZ&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Added ADR &lt;code dir=&quot;auto&quot;&gt;2026-06-07-1-wp-lane-fsm-genesis-and-finalize-clobber.md&lt;/code&gt; documenting the
genesis-lane bootstrap and the finalize event-log clobber fix.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-3&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Routed all WP lane validation and mutation through the single FSM transition primitive;
callers no longer reconstruct transition authority from derived constants (#1666).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-12&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;finalize&lt;/code&gt; no longer overwrite the coordination branch’s canonical
status event log (&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;) with the primary checkout’s
stale copies, preserving seeded lane state on coordination-topology missions (#1589).&lt;/li&gt;
&lt;li&gt;Reconciled the genesis gate and &lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt; 6.0.0 expectations for CI.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc39---2026-06-07&quot;&gt;[3.2.0rc39] - 2026-06-07&lt;/h2&gt;
&lt;h3 id=&quot;-added-9&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;session_presence&lt;/code&gt; package with &lt;code dir=&quot;auto&quot;&gt;SessionPresenceManager&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;InstallResult&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;ClaudeCodeWriter&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MarkdownRulesWriter&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ClaudeCodeHookRegistrar&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;UpgradeChecker&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;SessionPresenceContent&lt;/code&gt;, and supporting writer/hook infrastructure.&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;spec-kitty session-start&lt;/code&gt; CLI command (invoked by the Claude Code &lt;code dir=&quot;auto&quot;&gt;SessionStart&lt;/code&gt;
hook) that emits an orientation block to stdout when run inside a spec-kitty project.
The command always exits 0 and never blocks a Claude Code session start.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now calls &lt;code dir=&quot;auto&quot;&gt;SessionPresenceManager.install()&lt;/code&gt; after saving agent
configuration, writing the orientation block and registering the &lt;code dir=&quot;auto&quot;&gt;SessionStart&lt;/code&gt; hook for
Claude Code projects automatically.&lt;/li&gt;
&lt;li&gt;Added Phase 1 upgrade migration (&lt;code dir=&quot;auto&quot;&gt;3_3_0_session_presence_claude_code&lt;/code&gt;) that detects
existing Claude Code projects missing the orientation section or &lt;code dir=&quot;auto&quot;&gt;SessionStart&lt;/code&gt; hook and
backfills both artefacts on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-13&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Work packages can now declare &lt;code dir=&quot;auto&quot;&gt;scope: codebase-wide&lt;/code&gt; so cross-cutting/refactor
WPs are exempt from &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt; overlap validation, end-to-end through
&lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; (#1753). Two coupled defects were fixed: (1) the strict
(&lt;code dir=&quot;auto&quot;&gt;extra=&quot;forbid&quot;&lt;/code&gt;) &lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; parser rejected the &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt; key at parse time,
and (2) &lt;code dir=&quot;auto&quot;&gt;OwnershipManifest.from_frontmatter&lt;/code&gt; hard-coded &lt;code dir=&quot;auto&quot;&gt;scope = None&lt;/code&gt; on its
&lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; branch - the exact path &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; uses - silently dropping
the exemption even when the key parsed. The adapter now propagates &lt;code dir=&quot;auto&quot;&gt;scope&lt;/code&gt;, and
acceptance tests assert that narrow WPs claiming the same files still fail
regardless of lane/dependency structure, while a codebase-wide WP is exempt.
Also removed redundant &lt;code dir=&quot;auto&quot;&gt;@overload&lt;/code&gt; stubs on &lt;code dir=&quot;auto&quot;&gt;from_frontmatter&lt;/code&gt; that tripped
strict mypy (&lt;code dir=&quot;auto&quot;&gt;overload-cannot-match&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-docs&quot;&gt;📝 Docs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;AGENTS.md: added “Use Canonical Sources, Never Improvise” guidance and a
ruff/mypy-clean (no disabled checks) code-style rule.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tasks-finalize&lt;/code&gt; doctrine prompt: documented ownership-overlap handling for
domain/refactor missions (linearize shared surfaces; declare codebase-wide).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc38---2026-06-06&quot;&gt;[3.2.0rc38] - 2026-06-06&lt;/h2&gt;
&lt;h3 id=&quot;-added-10&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added implementation concern Map terminology and work-package traceability
across planning artifacts, generated task prompts, validation checks, docs,
ADRs, glossary context, and agent snapshots.&lt;/li&gt;
&lt;li&gt;Added tracked Op record storage under &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt;, including
&lt;code dir=&quot;auto&quot;&gt;ops-index.jsonl&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lifecycle.jsonl&lt;/code&gt;, propagation-error records, best-effort
&lt;code dir=&quot;auto&quot;&gt;op(...)&lt;/code&gt; auto-commit support, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops&lt;/code&gt; orphan reporting.&lt;/li&gt;
&lt;li&gt;Added DocFX publishing polish, all-contributors normalization, and updated
CLI/reference documentation for the 3.2 release candidate line.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-improved&quot;&gt;🔧 Improved&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Moved Op record storage from its previous gitignored event directory to
git-tracked &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt;, including &lt;code dir=&quot;auto&quot;&gt;ops-index.jsonl&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;lifecycle.jsonl&lt;/code&gt;, and
propagation errors. Pre-existing records in the retired location are
abandoned and not migrated.&lt;/li&gt;
&lt;li&gt;Consolidated software-dev template source resolution and rejected stale
template-root environment overrides so runtime fixtures and package defaults
cannot silently diverge.&lt;/li&gt;
&lt;li&gt;Tightened release workflow ownership around downstream consumer validation,
release metadata, path filters, and GitHub Pages publishing support.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-14&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Merge done-marking surface divergence&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;merge.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;coordination/surface_resolver.py&lt;/code&gt;):
After &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt;, WPs that were &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; would show as &lt;code dir=&quot;auto&quot;&gt;Completed: 0 (80.0%)&lt;/code&gt;
instead of &lt;code dir=&quot;auto&quot;&gt;Completed: 1 (100%)&lt;/code&gt; when the mission carried a &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;. Root cause: &lt;code dir=&quot;auto&quot;&gt;_mark_wp_merged_done&lt;/code&gt; wrote done events to the coordination
branch surface via &lt;code dir=&quot;auto&quot;&gt;BookkeepingTransaction&lt;/code&gt; (coord-branch-aware), while
&lt;code dir=&quot;auto&quot;&gt;_assert_merged_wps_reached_done&lt;/code&gt; read back from the primary checkout via
&lt;code dir=&quot;auto&quot;&gt;resolve_feature_dir_for_mission&lt;/code&gt; (topology-unaware). The two functions resolved to
different filesystem paths - write never landed where read looked. Fix: introduced
&lt;code dir=&quot;auto&quot;&gt;coordination.surface_resolver.resolve_status_surface(repo_root, mission_slug)&lt;/code&gt; as the
single canonical surface resolver; &lt;code dir=&quot;auto&quot;&gt;_assert_merged_wps_reached_done&lt;/code&gt; now calls it instead
of the topology-unaware resolver, eliminating the divergence. A full merge-path audit
(inline comment in &lt;code dir=&quot;auto&quot;&gt;merge.py&lt;/code&gt;) confirms no other DIVERGENT sites. Parity ratchet added
(four regression tests). Class recurrence of issue
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/1589&quot;&gt;#1589&lt;/a&gt; facet 3.
Closes &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/1726&quot;&gt;#1726&lt;/a&gt;.
(&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/1672&quot;&gt;#1672&lt;/a&gt; parity ratchet)&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Completed Op records are now best-effort auto-committed with &lt;code dir=&quot;auto&quot;&gt;op(...)&lt;/code&gt;
commit messages, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor ops&lt;/code&gt; reports started-only orphan
records.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; (without &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt;) no longer checks or requires origin
sync before performing local lane integration. A local target branch that
is ahead of, behind, or diverged from its remote tracking branch does not
block a local-only merge. This resolves issue #1706 where users with
accumulated orchestration commits on local &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; could not run
&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; until they pushed to origin first.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Push-safety checks now fire only when &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt; is requested. The
&lt;code dir=&quot;auto&quot;&gt;&quot;behind&quot;&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;&quot;diverged&quot;&lt;/code&gt; states block before local merge mutation with
remediation guidance, while &lt;code dir=&quot;auto&quot;&gt;&quot;ahead&quot;&lt;/code&gt; remains push-safe.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;MergeState&lt;/code&gt; now persists &lt;code dir=&quot;auto&quot;&gt;push_requested&lt;/code&gt; for correct resume semantics:
a resumed merge respects the original invocation’s push intent without
requiring re-specification of &lt;code dir=&quot;auto&quot;&gt;--push&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; now preserves query startup latency behavior while runtime
template-source cleanup is in effect.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc37---2026-06-04&quot;&gt;[3.2.0rc37] - 2026-06-04&lt;/h2&gt;
&lt;h3 id=&quot;added-8&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added execution-state domain remediation artifacts, ADRs, and glossary
context covering ExecutionContext ownership, command targets, effector
actors, mission/MissionRun boundaries, and status aggregate behavior.&lt;/li&gt;
&lt;li&gt;Added architectural ratchets for execution-context parity, status module
boundaries, and raw &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;&lt;/code&gt; path construction.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-7&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Routed command and runtime path handling through shared execution-context and
feature-directory resolution so raw mission spec paths consistently resolve
through the active action context.&lt;/li&gt;
&lt;li&gt;Refreshed Contextive execution glossary and doctrine skill metadata while
removing the retired &lt;code dir=&quot;auto&quot;&gt;spk-integrate-ci&lt;/code&gt; skill from the bundled doctrine pack.&lt;/li&gt;
&lt;li&gt;Hardened release-candidate CI ownership and release workflow checks around
path filters, candidate metadata, and downstream compatibility validation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-8&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Fixed 3.1.10 acceptance and move-task regressions across transactional
coordination, protected branch bypass handling, and clean-tree acceptance
fixtures.&lt;/li&gt;
&lt;li&gt;Suppressed SaaS ingress warnings when SaaS sync is disabled.&lt;/li&gt;
&lt;li&gt;Addressed low-risk Sonar cleanup findings and mission-review follow-up
issues from execution-state domain remediation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc36---2026-06-03&quot;&gt;[3.2.0rc36] - 2026-06-03&lt;/h2&gt;
&lt;h3 id=&quot;changed-8&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Polished 3.2 CLI UX around init next steps, scaffold state, widen guidance,
and charter preflight output.&lt;/li&gt;
&lt;li&gt;Updated agent harness installation guidance and snapshots for Codex, Kiro,
Antigravity, and public harness docs.&lt;/li&gt;
&lt;li&gt;Added execution-state/runtime architecture notes covering mission vs.
MissionRun boundaries and context decomposition.&lt;/li&gt;
&lt;li&gt;Hardened release-candidate CI around charter checks, workflow status
coordination, and Next runtime task parsing.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc35---2026-06-02&quot;&gt;[3.2.0rc35] - 2026-06-02&lt;/h2&gt;
&lt;h3 id=&quot;added-9&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added agent upgrade prompts and slash-command repair diagnostics so project
upgrades can detect and repair stale agent command surfaces.&lt;/li&gt;
&lt;li&gt;Added doctrine/profile activation closure work, including canonical kind
resolution, DRG-backed profile lineage, layered charter listing, template
discovery, and single-source doctrine health reporting.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-9&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Reworked parent-mission acceptance docs and charter boundary documentation
around status-commit terminology and profile integrity closeout.&lt;/li&gt;
&lt;li&gt;Tightened coordination topology handling across runtime prompts, decision
logs, dependency gates, move-task transitions, and orchestrator API paths.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-9&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Fixed slash-command install and audit gaps that left generated command files
stale after upgrades.&lt;/li&gt;
&lt;li&gt;Fixed coordination-topology edge cases that could read stale checkout state,
miss decision logs, or proceed across topology gaps without failing closed.&lt;/li&gt;
&lt;li&gt;Fixed charter activation and closeout CI instability, including layer-aware
activation and clean-install latency recalibration.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc34---2026-06-02&quot;&gt;[3.2.0rc34] - 2026-06-02&lt;/h2&gt;
&lt;h3 id=&quot;changed-10&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Clarified that live canary and cross-repo end-to-end runs remain required
release-candidate hygiene under the charter, but are run locally before
tagging instead of as tag-time PyPI publish workflow blockers.&lt;/li&gt;
&lt;li&gt;Transactional mission status reads now resolve the coordination worktree
without creating or mutating checkout state, keeping lane views aligned with
the coordination branch.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-10&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Planning-artifact commits now preserve append-only coordination event logs
instead of clobbering lane history with stale primary-checkout copies.&lt;/li&gt;
&lt;li&gt;Planning-artifact claim commits now parse git porcelain status structurally,
fail closed on unrelated structural changes, and skip idempotent
already-on-coordination content.&lt;/li&gt;
&lt;li&gt;Move-task transitions now derive source and target lanes from transactional
coordination status so review handoffs do not fail after coordination/feature
branch desync.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/sync-state.json&lt;/code&gt; is treated as local relay state, while charter
synthesis provenance can be tracked with the required commit reminder.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc33---2026-06-01&quot;&gt;[3.2.0rc33] - 2026-06-01&lt;/h2&gt;
&lt;h3 id=&quot;changed-11&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Tag-time PyPI publishing now stays focused on release-local checks. Live
canary evidence and the cross-repo end-to-end consumer scenario are no longer
blocking jobs in &lt;code dir=&quot;auto&quot;&gt;.github/workflows/release.yml&lt;/code&gt;; they remain required local
release-candidate hygiene before tagging.&lt;/li&gt;
&lt;li&gt;Release metadata now aligns &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;
for &lt;code dir=&quot;auto&quot;&gt;3.2.0rc33&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc32---2026-06-01&quot;&gt;[3.2.0rc32] - 2026-06-01&lt;/h2&gt;
&lt;h3 id=&quot;added-10&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Charter governance references: &lt;code dir=&quot;auto&quot;&gt;governance_references&lt;/code&gt; declarations in &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;
now surface supporting public governance docs in &lt;code dir=&quot;auto&quot;&gt;charter context&lt;/code&gt; text/JSON and
&lt;code dir=&quot;auto&quot;&gt;charter status&lt;/code&gt; diagnostics, with repo-root-scoped path safety.&lt;/li&gt;
&lt;li&gt;Release authority now has a machine-readable shared-package compatibility
manifest, plus gates that validate CLI ranges, &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt;, SaaS consumer
contracts, and exact PyPI installability for published artifacts.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-12&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Release metadata now aligns &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;
for &lt;code dir=&quot;auto&quot;&gt;3.2.0rc32&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Glossary runtime modules are packaged under canonical top-level &lt;code dir=&quot;auto&quot;&gt;glossary&lt;/code&gt;
while &lt;code dir=&quot;auto&quot;&gt;specify_cli.glossary&lt;/code&gt; remains a registered compatibility shim.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-11&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent decision open --json&lt;/code&gt; now emits exactly one parseable JSON
object on stdout. The response includes a retry-safe idempotency key so callers
can rerun the same logical open by mission slug and recover the same
&lt;code dir=&quot;auto&quot;&gt;decision_id&lt;/code&gt; after wrapper parse/process failures. Idempotent retries repair
a missing opened event when local decision files were persisted before event
emission failed, and dry-run output no longer advertises persisted recovery.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate --force&lt;/code&gt; now refuses to overwrite symlinked &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; paths,
preventing silent writes through symlink targets.&lt;/li&gt;
&lt;li&gt;Sync WebSocket connections now send ephemeral &lt;code dir=&quot;auto&quot;&gt;ws_token&lt;/code&gt; credentials in the
&lt;code dir=&quot;auto&quot;&gt;Authorization: Bearer&lt;/code&gt; upgrade header instead of an ignored &lt;code dir=&quot;auto&quot;&gt;?token=&lt;/code&gt; query
parameter, restoring authenticated live event delivery.&lt;/li&gt;
&lt;li&gt;Prerelease PyPI publishing no longer waives downstream consumer evidence; the
release workflow now requires the private consumer suite before any PyPI
promotion.&lt;/li&gt;
&lt;li&gt;A circular work-package dependency in &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; no longer leaves the canonical
status uninitialized with a misleading, looping error (#1589). &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;
aborts on the cycle before bootstrapping status; &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;
and lane reads now name the dependency cycle as the root cause instead of an
infinite “run finalize-tasks to bootstrap the event log” hint.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent status doctor&lt;/code&gt; no longer reports a mission as “Healthy” when
it has work-package definitions but no canonical status (e.g. after a
cycle-aborted &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;); it now emits an &lt;code dir=&quot;auto&quot;&gt;uninitialized_status&lt;/code&gt; warning
naming the cycle when present (#1589).&lt;/li&gt;
&lt;li&gt;CI: the shared-package drift check now skips gracefully when
&lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_READ_TOKEN&lt;/code&gt; is unavailable (fork PRs) instead of hard-failing;
the cross-repo drift is still enforced by the push-to-main CI that holds the
secret.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;documentation&quot;&gt;Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Clarified that &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/charter.md&lt;/code&gt; is the Spec Kitty runtime governance
center, while public docs such as &lt;code dir=&quot;auto&quot;&gt;spec/constitution.md&lt;/code&gt; are supporting context
rather than alternate authoritative charter paths.&lt;/li&gt;
&lt;li&gt;Added migration guidance for constitution-era &lt;code dir=&quot;auto&quot;&gt;.kittify/memory/constitution.md&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;.kittify/constitution/*&lt;/code&gt; layouts.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc31-rolled-into-rc32&quot;&gt;[3.2.0rc31] (rolled into rc32)&lt;/h2&gt;
&lt;h3 id=&quot;fixed-12&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Legacy &lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_lint.checks.*&lt;/code&gt; shim imports now preserve canonical
&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_runtime.lint.checks.*&lt;/code&gt; module identity and fail loudly if a
nested alias is missing, preventing duplicate checker module instances.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc30---2026-05-29&quot;&gt;[3.2.0rc30] - 2026-05-29&lt;/h2&gt;
&lt;h3 id=&quot;added-11&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;ADR 2026-05-28-1&lt;/strong&gt;: Documents CI dependency resolution and test surface consistency —
five structural gaps identified from CI run 26558837157, chosen remediations, and
confirmation criteria.
(&lt;code dir=&quot;auto&quot;&gt;architecture/adrs/2026-05-28-1-ci-dependency-resolution-and-test-surface-consistency.md&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Typer-surface smoke test (&lt;code dir=&quot;auto&quot;&gt;tests/agent/test_json_group_typer_surface.py&lt;/code&gt;) that exercises
the &lt;code dir=&quot;auto&quot;&gt;_JSONErrorGroup&lt;/code&gt; / JSON-envelope contract end-to-end using &lt;code dir=&quot;auto&quot;&gt;typer.Exit&lt;/code&gt; (not
&lt;code dir=&quot;auto&quot;&gt;click.exceptions.Exit&lt;/code&gt;). Acts as a canary for the typer 0.26+ vendored-click regression.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;agent&lt;/code&gt; pytest marker for orchestrator-api / agent-facing contract surface tests.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-13&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CI: all test and lint jobs now use &lt;code dir=&quot;auto&quot;&gt;uv sync --frozen --all-extras&lt;/code&gt;&lt;/strong&gt; instead of
&lt;code dir=&quot;auto&quot;&gt;pip install -e .[test]&lt;/code&gt;. The lockfile is the single environment contract for both
local and CI, eliminating resolver drift between &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; bounds.
Three infrastructure jobs (&lt;code dir=&quot;auto&quot;&gt;uv-lock-check&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;build-wheel&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;clean-install-verification&lt;/code&gt;)
are unaffected.&lt;/li&gt;
&lt;li&gt;Python version pinned to &lt;code dir=&quot;auto&quot;&gt;3.11.15&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;.python-version&lt;/code&gt; for reproducibility.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-13&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;_JSONErrorGroup&lt;/code&gt; exception handlers now use &lt;code dir=&quot;auto&quot;&gt;_CLICK_USAGE_ERRORS&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_CLICK_ABORTS&lt;/code&gt;
tuples that include both &lt;code dir=&quot;auto&quot;&gt;click.exceptions.*&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;typer._click.exceptions.*&lt;/code&gt; variants,
fixing silent miss of all exceptions raised by typer 0.26+ which vendors click
internally as &lt;code dir=&quot;auto&quot;&gt;typer._click&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Charter-preflight test fixtures (&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/charter_preflight/_fixtures.py&lt;/code&gt;)
now use &lt;code dir=&quot;auto&quot;&gt;charter.hasher.hash_content()&lt;/code&gt; instead of raw &lt;code dir=&quot;auto&quot;&gt;hashlib.sha256(bytes)&lt;/code&gt;,
aligning with the production algorithm and eliminating hash-format divergence.&lt;/li&gt;
&lt;li&gt;E2e conftest synthesises &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/metadata.yaml&lt;/code&gt; after &lt;code dir=&quot;auto&quot;&gt;copytree&lt;/code&gt; using
the production &lt;code dir=&quot;auto&quot;&gt;charter.hasher.hash_content()&lt;/code&gt; helper, making fixtures self-contained
and reproducible on clean clones without gitignored runtime state.&lt;/li&gt;
&lt;li&gt;Missing &lt;code dir=&quot;auto&quot;&gt;import click&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;orchestrator_api/commands.py&lt;/code&gt; that caused &lt;code dir=&quot;auto&quot;&gt;NameError&lt;/code&gt; in the
&lt;code dir=&quot;auto&quot;&gt;except ImportError&lt;/code&gt; fallback when importing the module on typer &amp;#x3C; 0.26.&lt;/li&gt;
&lt;li&gt;Restored &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; CLI group registration (incorrectly removed when a stale regression
test was treated as a contract); narrowed the curation-excision guard to &lt;code dir=&quot;auto&quot;&gt;curate&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;promote&lt;/code&gt;
only; restored &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine&lt;/code&gt; sections in &lt;code dir=&quot;auto&quot;&gt;docs/reference/cli-commands.md&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;security--lint&quot;&gt;Security / Lint&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;TID251&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;flake8-tidy-imports&lt;/code&gt; banned-api) added to ruff: &lt;code dir=&quot;auto&quot;&gt;hashlib.sha256&lt;/code&gt; usage in
&lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt; must go through &lt;code dir=&quot;auto&quot;&gt;charter.hasher.hash_content()&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;click.exceptions.Exit&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;UsageError&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;Abort&lt;/code&gt; in tests must use &lt;code dir=&quot;auto&quot;&gt;typer.*&lt;/code&gt; equivalents instead.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;TID251&lt;/code&gt; is now &lt;strong&gt;enforced&lt;/strong&gt;, not advisory: a dedicated &lt;code dir=&quot;auto&quot;&gt;[ENFORCED] banned-API lint gate (TID251)&lt;/code&gt; step in &lt;code dir=&quot;auto&quot;&gt;ci-quality.yml&lt;/code&gt; runs &lt;code dir=&quot;auto&quot;&gt;ruff check src tests --select TID251&lt;/code&gt;
without &lt;code dir=&quot;auto&quot;&gt;continue-on-error&lt;/code&gt;, so an unannotated banned call fails the build. The
previous whole-directory &lt;code dir=&quot;auto&quot;&gt;per-file-ignores&lt;/code&gt; (which silently exempted 10 test trees and
defeated the “new sha256 still needs a &lt;code dir=&quot;auto&quot;&gt;# noqa&lt;/code&gt;” policy) were removed; every legitimate
raw &lt;code dir=&quot;auto&quot;&gt;hashlib.sha256&lt;/code&gt; now carries an inline &lt;code dir=&quot;auto&quot;&gt;# noqa: TID251 - &amp;#x3C;justification&gt;&lt;/code&gt;. A guard
test (&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_tid251_enforcement.py&lt;/code&gt;) pins the enforcement so it
cannot silently regress to advisory. (Closes the adversarial review block on #1395.)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc29---2026-05-29&quot;&gt;[3.2.0rc29] - 2026-05-29&lt;/h2&gt;
&lt;p&gt;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.&lt;/p&gt;
&lt;h3 id=&quot;added-12&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added mission coordination branches, sparse coordination worktrees,
&lt;code dir=&quot;auto&quot;&gt;BookkeepingTransaction&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;WorkflowMutationPolicy&lt;/code&gt; so mission status
mutations are staged, audited, and committed away from protected target
branches.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;mission close --discard&lt;/code&gt; and doctor diagnostics for coordination
workspace health, restart-daemon timing, command/skill manifest drift, and
upgrade remediation provenance.&lt;/li&gt;
&lt;li&gt;Added external-orchestrator install and compatibility documentation, including
PyPI installation paths, orchestrator API JSON-error guidance, host-surface
governance docs, and environment-variable references.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-14&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;BREAKING (CLI)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty safe-commit&lt;/code&gt; now requires
&lt;code dir=&quot;auto&quot;&gt;--to-branch &amp;#x3C;ref&gt;&lt;/code&gt;. The temporary &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_INFER_DESTINATION_REF=1&lt;/code&gt;
compatibility path lets the CLI resolve and pass the destination explicitly
during rollout; the helper itself never infers it.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;BREAKING (internal)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;safe_commit()&lt;/code&gt; now requires keyword-only
&lt;code dir=&quot;auto&quot;&gt;worktree_root&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;destination_ref&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;paths&lt;/code&gt;, and structurally verifies
that the worktree HEAD matches the declared destination before staging.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;Hardened release CI ownership by deduplicating release-readiness checks,
adding installed-entrypoint smoke coverage, and preserving clean-install
latency evidence.&lt;/li&gt;
&lt;li&gt;Documented the host-surface parity matrix and Mode of Work governance layer
so standalone dispatch behavior has a visible README entry point.&lt;/li&gt;
&lt;li&gt;Clarified correlation link and projection policy / read-model policy coverage
for the 3.2.0 trail-model tranche, including deferred Tier 2 items.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-14&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Migrated remaining production &lt;code dir=&quot;auto&quot;&gt;safe_commit()&lt;/code&gt; 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.&lt;/li&gt;
&lt;li&gt;Fixed protected-branch leakage from &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; by routing
planning artifacts and workflow status writes through coordination-owned
commit paths instead of target-branch bypasses.&lt;/li&gt;
&lt;li&gt;Serialized first-time coordination worktree creation under the feature
status lock to prevent concurrent emitters from racing on &lt;code dir=&quot;auto&quot;&gt;git worktree add&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;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.&lt;/li&gt;
&lt;li&gt;Restored upgrade-readiness preference preservation and compatibility hints,
including uv-tool pytest remediation provenance fallbacks.&lt;/li&gt;
&lt;li&gt;Restored compatibility for older unit-test fakes that do not expose the new
coordination branch or commit-result fields.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;deferred&quot;&gt;Deferred&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Continued tracking deferred follow-up work such as
&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/534&quot;&gt;#534&lt;/a&gt; outside the
3.2.0 readiness tranche.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc28---2026-05-27&quot;&gt;[3.2.0rc28] - 2026-05-27&lt;/h2&gt;
&lt;p&gt;3.2.0rc28 fixes acceptance lane ownership and a clean-install dependency gap.&lt;/p&gt;
&lt;h3 id=&quot;changed-15&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt; and orchestrator-api &lt;code dir=&quot;auto&quot;&gt;accept-mission&lt;/code&gt; now keep &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; distinct: acceptance reports accepted-ready, approved,
merge-pending, and already-merged WPs without closing approved WPs. Merge
remains the owner of the &lt;code dir=&quot;auto&quot;&gt;approved -&gt; done&lt;/code&gt; integration transition.&lt;/li&gt;
&lt;li&gt;Software-dev mission guards now treat &lt;code dir=&quot;auto&quot;&gt;approved&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; as
accepted-ready for mission advancement.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-15&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Declared &lt;code dir=&quot;auto&quot;&gt;click&lt;/code&gt; as a direct runtime dependency because CLI modules import it
directly. This fixes pipx/Windows clean-install import failures.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc27---2026-05-26&quot;&gt;[3.2.0rc27] - 2026-05-26&lt;/h2&gt;
&lt;p&gt;3.2.0rc27 fixes a charter freshness/preflight false positive found in the
post-rc26 mainline checks.&lt;/p&gt;
&lt;h3 id=&quot;fixed-16&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Charter freshness now uses the same canonical hash semantics as
&lt;code dir=&quot;auto&quot;&gt;charter sync&lt;/code&gt;, so whitespace-normalized stored hashes do not falsely mark a
project stale.&lt;/li&gt;
&lt;li&gt;Fresh built-in doctrine seeds now produce the charter synthesis manifest
expected by preflight, preventing new projects from failing with
&lt;code dir=&quot;auto&quot;&gt;charter_source stale&lt;/code&gt; before any local charter exists.&lt;/li&gt;
&lt;li&gt;Synced charter bundles no longer become stale from source mtime drift when
metadata hashes and required bundle files already prove the source is fresh.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc26---2026-05-26&quot;&gt;[3.2.0rc26] - 2026-05-26&lt;/h2&gt;
&lt;p&gt;Rolls up the charter preflight, built-in vocabulary, and CI stabilization
guardrails merged after rc25.&lt;/p&gt;
&lt;h3 id=&quot;breaking-changes&quot;&gt;Breaking changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;shipped&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;built-in&lt;/code&gt; vocabulary rename.&lt;/strong&gt; Public CLI JSON surfaces that
previously emitted &lt;code dir=&quot;auto&quot;&gt;&quot;shipped&quot;&lt;/code&gt; as a doctrine layer label now emit &lt;code dir=&quot;auto&quot;&gt;&quot;built-in&quot;&lt;/code&gt;.
This aligns user-facing terminology with the on-disk &lt;code dir=&quot;auto&quot;&gt;built-in/&lt;/code&gt; directory
layout that already existed. Affected commands:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter status --json&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter lint --json&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter preflight --json&lt;/code&gt; (new in this release)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent profile list --json&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctrine pack validate --json&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;External tooling that pattern-matched the string &lt;code dir=&quot;auto&quot;&gt;&quot;shipped&quot;&lt;/code&gt; MUST be updated.
No deprecation period: the rename is mechanical and the architectural test
&lt;code dir=&quot;auto&quot;&gt;tests/architectural/test_no_shipped_layer_label.py&lt;/code&gt; prevents regression.&lt;/p&gt;
&lt;p&gt;Related: ADR &lt;code dir=&quot;auto&quot;&gt;architecture/3.x/adr/2026-05-24-3-shipped-to-built-in-cutover.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-16&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Deprecated paths:&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_lint&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_freshness&lt;/code&gt;,
and &lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_preflight&lt;/code&gt; now re-export from
&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter_runtime.{lint,freshness,preflight}&lt;/code&gt; under a shared
charter-runtime umbrella (LD-5 / FR-014). The old paths emit no
&lt;code dir=&quot;auto&quot;&gt;DeprecationWarning&lt;/code&gt; yet; they will in the next minor release. External
importers should update to the new paths during this deprecation window
(spec C-008). The &lt;code dir=&quot;auto&quot;&gt;charter_runtime.facade&lt;/code&gt; slot is reserved for a future
charter-facade consolidation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-13&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter preflight&lt;/code&gt; command.&lt;/strong&gt; Caller-facing preflight contract
for governance freshness (FR-006, FR-007, FR-008). Returns a structured JSON
report that &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, and the dashboard consume to decide whether
to proceed, prompt for &lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt;, or block. See
&lt;code dir=&quot;auto&quot;&gt;docs/reference/charter-commands.md&lt;/code&gt; and ADR
&lt;code dir=&quot;auto&quot;&gt;architecture/3.x/adr/2026-05-24-1-charter-freshness-ux-contract.md&lt;/code&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Pre-launch and launch-readiness operator docs for hosted SaaS
sync (#1095). Public docs remain local-first; hosted readiness
stays opt-in via &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC=1&lt;/code&gt;. The new
&lt;code dir=&quot;auto&quot;&gt;docs/how-to/internal-hosted-readiness.md&lt;/code&gt; covers the dogfooding
workflow for internal / pre-launch operators, and the new
&lt;code dir=&quot;auto&quot;&gt;docs/explanation/launch-readiness-future.md&lt;/code&gt; stages the launch-day
behavior shift behind an explicit “Status: pre-launch” banner.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc25---2026-05-23&quot;&gt;[3.2.0rc25] - 2026-05-23&lt;/h2&gt;
&lt;p&gt;Rolls up the post-rc24 static-analysis and upgrade UX type-boundary fixes.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Tightens acceptance package imports, compatibility cache typing, and
readiness upgrade UX helper boundaries after the overnight Sonar sweep.&lt;/li&gt;
&lt;li&gt;Keeps the 3.2.0 stable release candidate line current with &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;
after &lt;code dir=&quot;auto&quot;&gt;#1293&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc24---2026-05-22&quot;&gt;[3.2.0rc24] - 2026-05-22&lt;/h2&gt;
&lt;p&gt;Ships the canonical SaaS-bound producer refactor for CLI lifecycle,
sync, decision, glossary, and migration emitters.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Routes known SaaS-bound CLI payloads through the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;
5.2 canonical models where those contracts exist, while preserving
transitional legacy wire payloads required by current SaaS consumers.&lt;/li&gt;
&lt;li&gt;Preserves local &lt;code dir=&quot;auto&quot;&gt;artifact_path&lt;/code&gt; metadata on artifact-phase Started
events and projects those payloads to the strict canonical SaaS wire
shape before queueing.&lt;/li&gt;
&lt;li&gt;Adds producer conformance coverage, strict lifecycle validation,
handler-reset isolation, and a documented canonical-producer lint
baseline for remaining local-only/test producers.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc23---2026-05-21&quot;&gt;[3.2.0rc23] - 2026-05-21&lt;/h2&gt;
&lt;p&gt;Rolls up the autonomous-runtime safety sweep needed before the 3.2.0
stable cut, plus the documentation and CI guardrails merged after rc22.
The candidate focuses on removing operator-required workarounds from
fully autonomous local missions.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1255&lt;/code&gt;: retrospective files written by &lt;code dir=&quot;auto&quot;&gt;retrospect create&lt;/code&gt;
are now accepted by &lt;code dir=&quot;auto&quot;&gt;retrospect synthesize&lt;/code&gt;, with regression coverage
for both dry-run and apply flows.&lt;/li&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1256&lt;/code&gt;: decisions deferred during planning can be resolved
cleanly at terminus, and &lt;code dir=&quot;auto&quot;&gt;decision verify&lt;/code&gt; no longer reports resolved
clarification markers as drift.&lt;/li&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1235&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;#1257&lt;/code&gt;: task finalization rejects
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; paths in WP &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt; with a clear WP/path error,
while bulk-edit preflight treats WPs that author planning artifacts
such as &lt;code dir=&quot;auto&quot;&gt;occurrence_map.yaml&lt;/code&gt; as informational.&lt;/li&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1236&lt;/code&gt;: lane computation now preserves parallel lanes for
upstream WPs with disjoint &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;; fan-in WPs remain the
synchronization point.&lt;/li&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1258&lt;/code&gt;: autonomous local mission docs now include the
focused-PR fallback for &lt;code dir=&quot;auto&quot;&gt;TARGET_BRANCH_NOT_SYNCHRONIZED&lt;/code&gt; when local
&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; contains orchestration commits.&lt;/li&gt;
&lt;li&gt;Adds the 3.2 documentation refresh, harness/install lifecycle pages,
docs freshness checks, drift-detector CI, canonical-producer linting,
acceptance-matrix extension preservation, and charter-context envelope
repair merged after rc22.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc22---2026-05-21&quot;&gt;[3.2.0rc22] - 2026-05-21&lt;/h2&gt;
&lt;p&gt;Ships the &lt;code dir=&quot;auto&quot;&gt;sync diagnose&lt;/code&gt; canonical-allowlist fix so canary diagnostic
output stops flagging known event types (&lt;code dir=&quot;auto&quot;&gt;TasksCompleted&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;PlanCompleted&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;GatePassed&lt;/code&gt;, etc.) as unknown. The &lt;code dir=&quot;auto&quot;&gt;sync diagnose&lt;/code&gt;
allowlist is replaced with delegation to
&lt;code dir=&quot;auto&quot;&gt;spec_kitty_events.conformance.validators._EVENT_TYPE_TO_MODEL&lt;/code&gt; - the
canonical registry shared with the SaaS strict validator. A
drift-detector regression test asserts the union remains in sync, so
future events releases self-validate. The CLI’s outbound emission
gate (&lt;code dir=&quot;auto&quot;&gt;emitter.VALID_EVENT_TYPES&lt;/code&gt;) is intentionally untouched.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixes &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync diagnose&lt;/code&gt; false-positive “unknown event”
warnings by sourcing recognised types from the canonical events
registry (&lt;code dir=&quot;auto&quot;&gt;Priivacy-ai/spec-kitty#1222&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Adds a drift-detector regression test that fails when the events
package adds or removes an event type without the registry being
re-imported.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc21---2026-05-20&quot;&gt;[3.2.0rc21] - 2026-05-20&lt;/h2&gt;
&lt;p&gt;Rolls up the minor issue-queue cleanup selected before the 3.2.0
stable release, plus the post-merge test hardening needed to keep
&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; green after those fixes landed.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixes tasking help assertions to validate Typer option metadata
instead of Rich-rendered, platform-truncated help text, restoring
the full main test sweep after the task command cleanup.&lt;/li&gt;
&lt;li&gt;Refreshes the rc20 lockfile metadata so branch and release
validation agree on the packaged dependency graph.&lt;/li&gt;
&lt;li&gt;Improves task finalization and review-state behavior: rejected
review overrides are described with the canonical tasking language,
finalize-tasks dependency prose no longer produces false positives,
and the main test sweep covers those edge cases.&lt;/li&gt;
&lt;li&gt;Tightens CI and repository hygiene by requiring PR suffixes in the
protect-main check and tracking research evidence logs.&lt;/li&gt;
&lt;li&gt;Hardens sync, acceptance, retrospective, and dashboard edges found
during the pre-3.2.0 issue sweep: doctor daemon health checks are
isolated, acceptance clarification markers match the canonical
contract, retrospective event emission is materialized, and the
dashboard exposes the glossary shell.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc20---2026-05-20&quot;&gt;[3.2.0rc20] - 2026-05-20&lt;/h2&gt;
&lt;p&gt;Closes the next dormant mask from epic &lt;code dir=&quot;auto&quot;&gt;#1198&lt;/code&gt;, surfaced by the
rc19 canary now that the &lt;code dir=&quot;auto&quot;&gt;#1202&lt;/code&gt; observability fix is in place.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1203&lt;/code&gt; mask 1: &lt;code dir=&quot;auto&quot;&gt;EventEmitter.emit_wp_created&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/sync/emitter.py&lt;/code&gt; now constructs the payload
matching the canonical events 5.1.0 &lt;code dir=&quot;auto&quot;&gt;wp_created_payload&lt;/code&gt; schema.
Four simultaneous violations are closed in a single change:
&lt;code dir=&quot;auto&quot;&gt;title&lt;/code&gt; renamed to &lt;code dir=&quot;auto&quot;&gt;wp_title&lt;/code&gt; at the payload boundary,
&lt;code dir=&quot;auto&quot;&gt;dependencies&lt;/code&gt; renamed to &lt;code dir=&quot;auto&quot;&gt;depends_on&lt;/code&gt;, required &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt;
parameter added (default &lt;code dir=&quot;auto&quot;&gt;&quot;cli&quot;&lt;/code&gt;) and placed in the payload,
and &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; removed from the payload (the parameter is
still accepted for backward compatibility but is no longer
written to the wire - it isn’t in the schema’s allowed set).
The local emitter’s per-event-type validator table is updated
to match the canonical required-fields contract; the
singleton-level &lt;code dir=&quot;auto&quot;&gt;emit_wp_created&lt;/code&gt; mirror in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/sync/events.py&lt;/code&gt; gains an &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt; parameter and
passes it through; and the production caller in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/agent/mission.py:2448&lt;/code&gt; passes
&lt;code dir=&quot;auto&quot;&gt;actor=&quot;spec-kitty agent mission finalize-tasks&quot;&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This was the four-violation drift P4 predicted in the differential
matrix and that the rc19 canary surfaced in full detail thanks to
the per-event-violation observability restored in &lt;code dir=&quot;auto&quot;&gt;#1202&lt;/code&gt;. The
structural follow-up &lt;code dir=&quot;auto&quot;&gt;#1200&lt;/code&gt; (construct payloads via pydantic
models across every &lt;code dir=&quot;auto&quot;&gt;emit_*&lt;/code&gt; site) still pending; this surgical
close prevents the immediate canary blocker while that work
proceeds.&lt;/p&gt;
&lt;h2 id=&quot;320rc19---2026-05-20&quot;&gt;[3.2.0rc19] - 2026-05-20&lt;/h2&gt;
&lt;p&gt;Ships the combined &lt;code dir=&quot;auto&quot;&gt;#1199&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;#1202&lt;/code&gt; surgical fix from epic &lt;code dir=&quot;auto&quot;&gt;#1198&lt;/code&gt;:
the immediate Phase 4 canary blocker plus the observability fix that
restores the SaaS’s per-event violation diversity to operators.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1199&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;emit_mission_created_local&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/lifecycle_events.py&lt;/code&gt; now accepts
&lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; (required) and &lt;code dir=&quot;auto&quot;&gt;wp_count&lt;/code&gt; (default 0) and places
both in the payload. The canonical events 5.1.0 schema for
&lt;code dir=&quot;auto&quot;&gt;mission_created_payload&lt;/code&gt; lists both as required; the deployed
SaaS jsonschema gate rejects payloads without them with
&lt;code dir=&quot;auto&quot;&gt;&apos;mission_type&apos; is a required property&lt;/code&gt;. The sibling call site in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/mission_creation.py:412&lt;/code&gt; now passes both
fields, matching the sync-events path at &lt;code dir=&quot;auto&quot;&gt;:468-470&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;_validate_lifecycle_payload&lt;/code&gt; widened from &lt;code dir=&quot;auto&quot;&gt;extra_forbidden&lt;/code&gt;-only
to fail on ALL model violations (extras + missing-required +
every other &lt;code dir=&quot;auto&quot;&gt;violation_type&lt;/code&gt;). The historical comment block that
rationalised the narrow scope as matching SaaS tolerance was
based on the SaaS-side &lt;code dir=&quot;auto&quot;&gt;_should_validate_strict_envelope&lt;/code&gt; hole
(&lt;code dir=&quot;auto&quot;&gt;Priivacy-ai/spec-kitty-saas#217&lt;/code&gt;) and is no longer true. The
widened validator catches MissionCreated, WPStatusChanged,
MissionDossierArtifactIndexed, and every other event type the
events package recognises, preventing the next analogous drift
from reaching the offline queue.&lt;/li&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1202&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;_parse_error_response&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/sync/batch.py&lt;/code&gt; now reads &lt;code dir=&quot;auto&quot;&gt;details[*].detail&lt;/code&gt;
(the key the SaaS actually ships) before falling back to
&lt;code dir=&quot;auto&quot;&gt;.error&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;.reason&lt;/code&gt;. Without this fix, every per-event line
in a SaaS rejection collapsed to the outer &lt;code dir=&quot;auto&quot;&gt;error_msg&lt;/code&gt; —
hiding the SaaS’s full per-event violation diversity for the
entire &lt;code dir=&quot;auto&quot;&gt;rc12 → rc18&lt;/code&gt; drift-chain investigation. With the fix,
the next failed batch surfaces every distinct violation per
event, dramatically compressing any remaining mask-peeling.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Sequenced first per epic &lt;code dir=&quot;auto&quot;&gt;#1198&lt;/code&gt;. The structural follow-up
&lt;code dir=&quot;auto&quot;&gt;#1200&lt;/code&gt; (pydantic-construct payloads across all &lt;code dir=&quot;auto&quot;&gt;emit_*&lt;/code&gt; sites +
CI conformance gate) and &lt;code dir=&quot;auto&quot;&gt;#1203&lt;/code&gt; (dormant masks sweep) are next,
with &lt;code dir=&quot;auto&quot;&gt;spec-kitty-saas#217&lt;/code&gt; (close the strict-envelope hole)
sequenced after.&lt;/p&gt;
&lt;h2 id=&quot;320rc18---2026-05-20&quot;&gt;[3.2.0rc18] - 2026-05-20&lt;/h2&gt;
&lt;p&gt;Ships the final observed Phase 4 launch-gate payload drift fix after the
rc17 &lt;code dir=&quot;auto&quot;&gt;WPStatusChanged&lt;/code&gt; envelope cleanup.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1190&lt;/code&gt; via &lt;code dir=&quot;auto&quot;&gt;#1191&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;emit_mission_created_local&lt;/code&gt; no longer writes
&lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt; into the &lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; payload. The canonical
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; 5.1.0 schema declares &lt;code dir=&quot;auto&quot;&gt;additionalProperties: false&lt;/code&gt; for
&lt;code dir=&quot;auto&quot;&gt;mission_created_payload&lt;/code&gt; and does not allow &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt;, so deployed SaaS batch
ingest rejected every batch containing one of these events.&lt;/li&gt;
&lt;li&gt;Refactors &lt;code dir=&quot;auto&quot;&gt;_validate_lifecycle_payload&lt;/code&gt; to delegate to
&lt;code dir=&quot;auto&quot;&gt;spec_kitty_events.conformance.validate_event&lt;/code&gt;, replacing the previous
hand-maintained lifecycle payload map that missed &lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; and other
known event types. The local guard now catches extra-property drift before
queue fan-out while still tolerating currently accepted missing-field
violations.&lt;/li&gt;
&lt;li&gt;Adds regression coverage for the cleaned &lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; payload, the
conformance guard’s extra-field rejection, valid-payload pass-through, and
graceful fallback for event types not recognised by the installed events
package.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc17---2026-05-20&quot;&gt;[3.2.0rc17] - 2026-05-20&lt;/h2&gt;
&lt;p&gt;Ships the third Phase 4 launch-gate fix: the actual SaaS-side schema
violation that was hiding behind the parser and canary issues fixed in
rc16.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1188&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;emit_wp_status_changed&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/sync/emitter.py&lt;/code&gt; no longer passes
&lt;code dir=&quot;auto&quot;&gt;envelope_fields=&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;_emit&lt;/code&gt;. The payload-only keys (&lt;code dir=&quot;auto&quot;&gt;from_lane&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;to_lane&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;actor&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;force&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review_ref&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;execution_mode&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;evidence&lt;/code&gt;) were being duplicated at the envelope
level alongside the canonical envelope keys, and the SaaS schema at
&lt;code dir=&quot;auto&quot;&gt;/api/v1/events/batch/&lt;/code&gt; rejected every batch containing a
&lt;code dir=&quot;auto&quot;&gt;WPStatusChanged&lt;/code&gt; event with
&lt;code dir=&quot;auto&quot;&gt;Additional properties are not allowed (&apos;actor&apos; was unexpected)&lt;/code&gt;
(HTTP 400). On rc16 this surfaced as scenarios 1, 2, and 4 of the
deployed-dev identity-boundary canary failing with
&lt;code dir=&quot;auto&quot;&gt;Synced: 0 Duplicates: 0 Errors: N (unknown: N)&lt;/code&gt;; scenario 3 passed
because it never emits events through the batch endpoint.&lt;/li&gt;
&lt;li&gt;Extends &lt;code dir=&quot;auto&quot;&gt;envelope.forbidden_fields&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/upstream_contract.json&lt;/code&gt; to include the
payload-only keys, so the existing
&lt;code dir=&quot;auto&quot;&gt;test_no_forbidden_fields_in_envelope&lt;/code&gt; contract test now guards
against regressions.&lt;/li&gt;
&lt;li&gt;Updates the unit tests in &lt;code dir=&quot;auto&quot;&gt;tests/sync/test_events.py&lt;/code&gt; that
previously asserted the top-level duplicates; the new assertions
pin the contract that those keys live in &lt;code dir=&quot;auto&quot;&gt;payload&lt;/code&gt; only.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;The bug has been on &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; since commit &lt;code dir=&quot;auto&quot;&gt;533e47d2&lt;/code&gt; (2026-04-14,
“Harden SaaS auth and restore build sync emission”). It was masked on
earlier RCs by the audit-predicate gap fixed in rc15
(&lt;code dir=&quot;auto&quot;&gt;#1142&lt;/code&gt;), the parser misclassification fixed in rc16 (&lt;code dir=&quot;auto&quot;&gt;#1182&lt;/code&gt;), and
the canary-command shape fixed in
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-end-to-end-testing#45&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;#1141&lt;/code&gt;). With those three out of
the way, the underlying envelope drift was finally visible end-to-end
and could be fixed.&lt;/p&gt;
&lt;h2 id=&quot;320rc16---2026-05-20&quot;&gt;[3.2.0rc16] - 2026-05-20&lt;/h2&gt;
&lt;p&gt;Ships the Phase 4 canary launch-gate unblock: the actual root-cause fix for
&lt;code dir=&quot;auto&quot;&gt;#1141&lt;/code&gt; and the parser/classification fix for &lt;code dir=&quot;auto&quot;&gt;#1182&lt;/code&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1182&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;_parse_event_results&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/sync/batch.py&lt;/code&gt;
now routes per-event &lt;code dir=&quot;auto&quot;&gt;status=&quot;queued&quot;&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;status=&quot;pending&quot;&lt;/code&gt; responses to a
new &lt;code dir=&quot;auto&quot;&gt;pending_count&lt;/code&gt; bucket on &lt;code dir=&quot;auto&quot;&gt;BatchSyncResult&lt;/code&gt; instead of folding them
into the rejected catch-all with &lt;code dir=&quot;auto&quot;&gt;category=unknown&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; previously
reported durably-queued events as &lt;code dir=&quot;auto&quot;&gt;Errors: N (unknown: N)&lt;/code&gt; and exited
non-zero when the in-process final-sync hit its 5s timeout; pending-only
drains now exit 0 and surface as &lt;code dir=&quot;auto&quot;&gt;Pending: N&lt;/code&gt; in the summary. Queue
mutation policy unchanged (pending rows are left for the next daemon tick,
same disposition as &lt;code dir=&quot;auto&quot;&gt;failed_transient&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1141&lt;/code&gt; (companion fix in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-end-to-end-testing#45&lt;/code&gt;): the
canary scenario 4 &lt;code dir=&quot;auto&quot;&gt;move-task --to planned&lt;/code&gt; invocation was omitting
&lt;code dir=&quot;auto&quot;&gt;--review-feedback-file&lt;/code&gt;, so the CLI hard-rejected the command at the
argument-validation layer before reaching &lt;code dir=&quot;auto&quot;&gt;emit_status_transition&lt;/code&gt;. The
rc15 diagnostic breadcrumb in &lt;code dir=&quot;auto&quot;&gt;fire_saas_fanout&lt;/code&gt; could never fire because
the codepath never reached fan-out. The e2e fix passes a structured
feedback markdown so the backward emit actually lands. No CLI change is
required; the events #32 force-required contract and the CLI’s
review-feedback hardening are both intentional and remain in force.&lt;/li&gt;
&lt;li&gt;New unit coverage in &lt;code dir=&quot;auto&quot;&gt;tests/sync/test_batch_error_surfacing.py&lt;/code&gt; pins the
contract: per-event &lt;code dir=&quot;auto&quot;&gt;queued&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt; are not errors, never count
toward &lt;code dir=&quot;auto&quot;&gt;success_count&lt;/code&gt; (they are durable in-flight, not terminal), but
do count toward sync activity so the “no progress” guard does not fire
on a pending-only drain.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc15---2026-05-19&quot;&gt;[3.2.0rc15] - 2026-05-19&lt;/h2&gt;
&lt;p&gt;Ships the Phase 4 canary unblock work landed via PR &lt;code dir=&quot;auto&quot;&gt;#1180&lt;/code&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1142&lt;/code&gt;: broadens &lt;code dir=&quot;auto&quot;&gt;is_mission_lifecycle_row&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/audit/shape_registry.py&lt;/code&gt; to accept all four canonical
aggregate types (&lt;code dir=&quot;auto&quot;&gt;Project&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;WorkPackage&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MissionDossier&lt;/code&gt;)
rather than &lt;code dir=&quot;auto&quot;&gt;Mission&lt;/code&gt; alone. Fresh missions no longer trip the
&lt;code dir=&quot;auto&quot;&gt;FORBIDDEN_KEY&lt;/code&gt; TeamSpace gate when &lt;code dir=&quot;auto&quot;&gt;sync now&lt;/code&gt; runs.&lt;/li&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1141&lt;/code&gt;: adds a diagnostic breadcrumb at &lt;code dir=&quot;auto&quot;&gt;fire_saas_fanout&lt;/code&gt; entry in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/adapters.py&lt;/code&gt; plus regression coverage that the
backward &lt;code dir=&quot;auto&quot;&gt;in_review → planned&lt;/code&gt; rollback reaches fanout with the expected
shape. &lt;strong&gt;Note&lt;/strong&gt;: this is a diagnostic landing, not the full root-cause fix
&lt;ul&gt;
&lt;li&gt;the silent replacement that the canary scenario 4 peek catches likely
lives downstream in &lt;code dir=&quot;auto&quot;&gt;OfflineQueue.queue_event&lt;/code&gt; and is expected to be
chased on a follow-up RC if it reproduces.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Bundles the +30 targeted audit / status-emit-sequence tests from &lt;code dir=&quot;auto&quot;&gt;#1180&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc14---2026-05-19&quot;&gt;[3.2.0rc14] - 2026-05-19&lt;/h2&gt;
&lt;p&gt;Ships the next 3.2 release candidate after the doctrine/charter and
sync-boundary follow-up window:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Adds the three-layer doctrine and charter DRG work: org-pack loading across
every configured pack, project/org/built-in precedence diagnostics,
org-charter interview pre-fill, collision warnings, and the related
workflow/governance payload hardening.&lt;/li&gt;
&lt;li&gt;Closes the org-pack and charter-scope safety follow-ups by blocking archive
traversal, unsafe server-provided filenames, symlink/hardlink extraction, and
scope roots that escape the repository.&lt;/li&gt;
&lt;li&gt;Documents recovery from partially installed command namespace packages for
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;, including the concrete import error signature and
reinstall path.&lt;/li&gt;
&lt;li&gt;Keeps local workflow test suites honest under the hosted sync preflight:
e2e workflow tests now opt out of &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC&lt;/code&gt; the same way
integration and tasks suites do, while sync/auth suites retain hosted-sync
coverage.&lt;/li&gt;
&lt;li&gt;Restores strict mission-step-contract type checking by making ambiguous DRG
URN matches explicitly typed.&lt;/li&gt;
&lt;li&gt;Carries review and release hygiene fixes for unsafe target-branch merge
guidance, retrospective workflow wording, doctrine language-bias lint, fresh
sync Sonar findings, and Windows/main CI health.&lt;/li&gt;
&lt;li&gt;Aligns the release checklist with the main-branch protection workflow:
release PRs should be squash-merged so the resulting commit retains the PR
marker that &lt;code dir=&quot;auto&quot;&gt;Protect Main Branch&lt;/code&gt; recognizes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc13---2026-05-19&quot;&gt;[3.2.0rc13] - 2026-05-19&lt;/h2&gt;
&lt;p&gt;Ships a focused sync-boundary hotfix for pipx-style CLI installs:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixes &lt;code dir=&quot;auto&quot;&gt;#1120&lt;/code&gt;: daemon owner records now canonicalize
&lt;code dir=&quot;auto&quot;&gt;executable_path&lt;/code&gt; at the &lt;code dir=&quot;auto&quot;&gt;DaemonOwnerRecord&lt;/code&gt; boundary, and foreground
sync identity uses the same canonicalization helper. Pipx-installed CLIs
whose &lt;code dir=&quot;auto&quot;&gt;sys.executable&lt;/code&gt; flows through a symlink no longer report a spurious
&lt;code dir=&quot;auto&quot;&gt;daemon_executable_path&lt;/code&gt; mismatch during &lt;code dir=&quot;auto&quot;&gt;sync status --check&lt;/code&gt; or
sync-producing command preflight.&lt;/li&gt;
&lt;li&gt;Adds adversarial coverage for owner-record dataclass canonicalization,
resolve-failure fallback behavior, and the asymmetric one-sided resolve
failure class that could reintroduce false split-brain detection.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc12---2026-05-18&quot;&gt;[3.2.0rc12] - 2026-05-18&lt;/h2&gt;
&lt;p&gt;Ships the MVP CLI sync-boundary preflight surface required by the Teamspace
auth-boundary hardening launch gate:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Includes &lt;code dir=&quot;auto&quot;&gt;#1115&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;specify_cli.sync.owner&lt;/code&gt; daemon owner record with
mismatch / orphan detection, &lt;code dir=&quot;auto&quot;&gt;specify_cli.sync.preflight&lt;/code&gt; read-only
auth/daemon/queue boundary preflight, and the new identity-boundary rows
exposed by &lt;code dir=&quot;auto&quot;&gt;sync status --check&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Closes &lt;code dir=&quot;auto&quot;&gt;#1087&lt;/code&gt; (sync status/doctor expose auth/queue/daemon split brain),
&lt;code dir=&quot;auto&quot;&gt;#1088&lt;/code&gt; (sync daemon coherent machine-global owner), &lt;code dir=&quot;auto&quot;&gt;#1089&lt;/code&gt; (setup-plan
evidence enqueued in one sync scope), and &lt;code dir=&quot;auto&quot;&gt;#1090&lt;/code&gt; (scoped queue migration
does not strand authenticated work).&lt;/li&gt;
&lt;li&gt;Unblocks the deployed-dev sync identity-boundary canary
(&lt;code dir=&quot;auto&quot;&gt;spec-kitty-end-to-end-testing#42&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#41&lt;/code&gt;) by providing a packaged CLI
whose &lt;code dir=&quot;auto&quot;&gt;sync status --check&lt;/code&gt; output is parseable by the canary harness.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc11---2026-05-17&quot;&gt;[3.2.0rc11] - 2026-05-17&lt;/h2&gt;
&lt;p&gt;Closes the planning#16 backward-transition follow-up across the CLI release
surface:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty backwards --note ...&lt;/code&gt; now preserves the canonical
&lt;code dir=&quot;auto&quot;&gt;backward rewind:&lt;/code&gt; transition-reason prefix when callers supply a note,
keeping emitted &lt;code dir=&quot;auto&quot;&gt;WPStatusChanged&lt;/code&gt; events accepted by the shared contract and
SaaS ingestion.&lt;/li&gt;
&lt;li&gt;The resolved lockfile moves to &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events==5.1.0&lt;/code&gt;, which ships the
review-rejection replay conformance fixture used to verify forced backward
transition handling.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc10---2026-05-17&quot;&gt;[3.2.0rc10] - 2026-05-17&lt;/h2&gt;
&lt;p&gt;Rolls forward &lt;code dir=&quot;auto&quot;&gt;3.2.0rc9&lt;/code&gt; (never tagged) and adds the Teamspace MVP
canonical-lifecycle / sync-daemon launch-gate followups:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;#1067 follow-up.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;core/mission_creation.py:create_mission_core&lt;/code&gt;
now emits the canonical &lt;code dir=&quot;auto&quot;&gt;SpecifyStarted&lt;/code&gt; event immediately after
&lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt;, referencing the freshly scaffolded &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt;
artifact path. Previously the constant was defined but never emitted,
so the canonical lifecycle stream skipped straight from
&lt;code dir=&quot;auto&quot;&gt;MissionCreated&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;SpecifyCompleted&lt;/code&gt; at setup-plan time - leaving
TeamSpace replay and the local dashboard blind to in-progress
specifying. Regression coverage in
&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/core/test_mission_creation_specify_started.py&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;#1071 follow-up.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;sync status --check&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;sync doctor&lt;/code&gt; now
surface the daemon PID/port and any orphan &lt;code dir=&quot;auto&quot;&gt;run_sync_daemon&lt;/code&gt;
processes (via the existing &lt;code dir=&quot;auto&quot;&gt;scan_sync_daemons&lt;/code&gt; helper), so operators
see cross-checkout daemon divergence without grepping &lt;code dir=&quot;auto&quot;&gt;ps&lt;/code&gt;.
&lt;code dir=&quot;auto&quot;&gt;_kill_and_cleanup&lt;/code&gt; now waits for the killed PID to actually exit
before clearing &lt;code dir=&quot;auto&quot;&gt;DAEMON_STATE_FILE&lt;/code&gt; - closing the AC bullet that
required version-mismatch replacement not leave older daemons live.
Module docstring updated to be honest about state-file-scoped
singleton semantics. Regression coverage in
&lt;code dir=&quot;auto&quot;&gt;tests/cli/commands/test_sync_status_singleton_diagnostics.py&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;tests/sync/test_daemon_replace_on_version_mismatch.py&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Everything previously slated for rc9 (below) is included in rc10.&lt;/p&gt;
&lt;h2 id=&quot;320rc9-rolled-into-rc10&quot;&gt;[3.2.0rc9] (rolled into rc10)&lt;/h2&gt;
&lt;p&gt;The &lt;code dir=&quot;auto&quot;&gt;quality-devex-hardening-3-2-01KRJGKH&lt;/code&gt; mission closes six epic-#822
tickets and lands the doctrine tactics, canonical-terminology glossary,
and code-patterns catalog that underpin the 3.2.0 stable release. Push-time
Sonar restoration (#825) is the only remaining operator-action gate.&lt;/p&gt;
&lt;h3 id=&quot;added-14&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Stale-lane auto-rebase with conflict classification&lt;/strong&gt; (#771). New
&lt;code dir=&quot;auto&quot;&gt;specify_cli.merge.conflict_classifier&lt;/code&gt; rule pipeline (Validator-flavor;
5 conflict shapes - pyproject deps union, &lt;code dir=&quot;auto&quot;&gt;__init__.py&lt;/code&gt; import-block
union, urls.py URL list union, &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; regenerate, default manual)
and &lt;code dir=&quot;auto&quot;&gt;specify_cli.lanes.auto_rebase&lt;/code&gt; orchestrator. &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt;
now attempts &lt;code dir=&quot;auto&quot;&gt;git merge &amp;#x3C;mission-branch&gt;&lt;/code&gt; inside a stale lane worktree
before halting, auto-resolves additive-only conflicts via a union-merge
driver, regenerates &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; under a global file lock, runs
&lt;code dir=&quot;auto&quot;&gt;ruff --fix --select I001&lt;/code&gt; on touched &lt;code dir=&quot;auto&quot;&gt;__init__.py&lt;/code&gt; files, and reports
auto-resolved vs manual lanes. Semantic conflicts still halt with the
current actionable error. ADR
&lt;code dir=&quot;auto&quot;&gt;architecture/2.x/adr/2026-05-14-1-stale-lane-auto-rebase-classifier-policy.md&lt;/code&gt;
documents the fail-safe-default policy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No-upgrade UX notification&lt;/strong&gt; (#740). New &lt;code dir=&quot;auto&quot;&gt;core/upgrade_probe.py&lt;/code&gt;
(PyPI probe + 2 s timeout-bounded channel classification:
ALREADY_CURRENT / AHEAD_OF_PYPI / NO_UPGRADE_PATH / UNKNOWN) and
&lt;code dir=&quot;auto&quot;&gt;core/upgrade_notifier.py&lt;/code&gt; (cache-aware emitter). Distinguishes
“already on the latest supported version” from “build/channel with no
upgrade path”; never blocks the CLI on network failure; rate-limited
to once per 24 h with &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_NO_UPGRADE_CHECK=1&lt;/code&gt; opt-out; reuses
&lt;code dir=&quot;auto&quot;&gt;should_check_version()&lt;/code&gt; rather than introducing a parallel gate.
Cache-warm budget &amp;#x3C; 100 ms.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;secure-regex-catastrophic-backtracking&lt;/code&gt; doctrine tactic&lt;/strong&gt; codifying
the four dangerous regex shapes, the rewrite ladder, and the escape
hatches. Every regex change now requires a wall-clock regression test
asserting linear runtime on adversarial input (default budget: &amp;#x3C; 100 ms
for 100 000 chars) per FR-008.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;chain-of-responsibility-rule-pipeline&lt;/code&gt; doctrine tactic&lt;/strong&gt; with three
flavors (Validator / Transformer / Scorer) and the typed
&lt;code dir=&quot;auto&quot;&gt;CanonicalRule&lt;/code&gt; Protocol at
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/migration/canonicalization.py&lt;/code&gt; as the canonical
Transformer-flavor implementation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Core code-patterns catalog&lt;/strong&gt; at
&lt;code dir=&quot;auto&quot;&gt;architecture/2.x/04_implementation_mapping/code-patterns.md&lt;/code&gt; listing
the recurring shapes used across the codebase (Rule-Based Pipeline,
Append-Only Event Log + Reducer, etc.) with doctrine cross-references.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Canonical-terminology glossary entries&lt;/strong&gt; for &lt;code dir=&quot;auto&quot;&gt;characterization test&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;pipeline-shape&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;rule pipeline&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;catastrophic backtracking&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;structural debt&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;deliberate linearity&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;sonar quality gate&lt;/code&gt;
in &lt;code dir=&quot;auto&quot;&gt;.kittify/glossaries/spec_kitty_core.yaml&lt;/code&gt;, each cross-referencing
the doctrine tactic or architectural document that codifies it
(FR-013).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Targeted symlink-fallback test&lt;/strong&gt; for the
&lt;code dir=&quot;auto&quot;&gt;m_0_8_0_worktree_agents_symlink&lt;/code&gt; migration’s &lt;code dir=&quot;auto&quot;&gt;OSError -&gt; shutil.copy2&lt;/code&gt;
fallback (#629). Runs on every CI pass via &lt;code dir=&quot;auto&quot;&gt;monkeypatch&lt;/code&gt;, not gated
by &lt;code dir=&quot;auto&quot;&gt;windows_ci&lt;/code&gt;. Covers both happy-fallback and dual-failure arms.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Behavior-driven coverage tests&lt;/strong&gt; for &lt;code dir=&quot;auto&quot;&gt;cli/commands/charter.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;cli/commands/charter_bundle.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;cli/commands/agent/config.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;next/_internal_runtime/engine.py&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;core/file_lock.py&lt;/code&gt;
(Bucket A/B/C split; &lt;code dir=&quot;auto&quot;&gt;CliRunner&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;tmp_path&lt;/code&gt; real I/O; no
&lt;code dir=&quot;auto&quot;&gt;mock.patch&lt;/code&gt; on Path methods) per the &lt;code dir=&quot;auto&quot;&gt;function-over-form-testing&lt;/code&gt;
tactic (#595 workstream A).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Wall-clock regression guard&lt;/strong&gt; at
&lt;code dir=&quot;auto&quot;&gt;tests/regressions/test_changelog_regex_redos.py&lt;/code&gt; (20 tests; &amp;#x3C; 100 ms
on 100 000-line adversarial input) against future re-introduction of
the three Sonar-flagged patterns in &lt;code dir=&quot;auto&quot;&gt;release/changelog.py&lt;/code&gt; (pre-fixed
in PR #592) (#595 workstream B / FR-008).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;dev&lt;/code&gt; dependency-group type stubs&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;types-jsonschema&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;types-psutil&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;types-PyYAML&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;types-requests&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;types-toml&lt;/code&gt;) in
&lt;code dir=&quot;auto&quot;&gt;[dependency-groups] dev&lt;/code&gt; so &lt;code dir=&quot;auto&quot;&gt;uv run --with mypy mypy --strict&lt;/code&gt;
resolves stubs from the default env.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-17&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;mypy strict baseline&lt;/strong&gt; is now green for &lt;code dir=&quot;auto&quot;&gt;src/specify_cli&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;src/charter&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/doctrine&lt;/code&gt; per decision moment
&lt;code dir=&quot;auto&quot;&gt;DM-01KRJHT7QD7XQMY33Y5TDTQ80V&lt;/code&gt; (option A - fix the existing target;
#971). Includes &lt;code dir=&quot;auto&quot;&gt;doctor.py::_print_overdue_details&lt;/code&gt; annotation fix
(typed &lt;code dir=&quot;auto&quot;&gt;ShimRegistryReport&lt;/code&gt; under &lt;code dir=&quot;auto&quot;&gt;TYPE_CHECKING&lt;/code&gt;) and
&lt;code dir=&quot;auto&quot;&gt;_resolve_fail_on&lt;/code&gt; return-type tightening to
&lt;code dir=&quot;auto&quot;&gt;tuple[Severity | None, bool]&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;_canonicalize_status_row&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;rebuild_state.py&lt;/code&gt;&lt;/strong&gt; refactored onto
the typed &lt;code dir=&quot;auto&quot;&gt;CanonicalRule&lt;/code&gt; Protocol with characterization-test coverage
preceding the refactor commits (NFR-003 / &lt;code dir=&quot;auto&quot;&gt;tdd-red-green-refactor&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor.py::mission_state&lt;/code&gt;&lt;/strong&gt; refactored from cognitive complexity 57
to a CC 3 thin orchestrator plus per-mode runners
(&lt;code dir=&quot;auto&quot;&gt;_validate_modes&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_resolve_fail_on&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_resolve_audit_root&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;_emit_mission_state&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_run_audit_mode&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_run_mission_repair&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;_run_teamspace_dry_run_mode&lt;/code&gt;), with 17 characterization tests
guarding behavior across all three dispatch arms (&lt;code dir=&quot;auto&quot;&gt;--audit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;--teamspace-dry-run&lt;/code&gt;) (#595 workstream C).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;review.py&lt;/code&gt; split into &lt;code dir=&quot;auto&quot;&gt;cli/commands/review/&lt;/code&gt; package&lt;/strong&gt; with sibling
files for cleaner ownership boundaries.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-17&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;doctor.py:1092&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;MissionRepairResult.findings&lt;/code&gt; real-branch bug&lt;/strong&gt;:
&lt;code dir=&quot;auto&quot;&gt;report&lt;/code&gt; variable was dual-typed as &lt;code dir=&quot;auto&quot;&gt;RepairReport&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;RepoAuditReport&lt;/code&gt; across mutually exclusive branches; runtime correct
but typing broken. Now closes mypy strict on &lt;code dir=&quot;auto&quot;&gt;doctor.py&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pre-existing YAML scanner error&lt;/strong&gt; in
&lt;code dir=&quot;auto&quot;&gt;.kittify/glossaries/spec_kitty_core.yaml&lt;/code&gt; line 484: the &lt;code dir=&quot;auto&quot;&gt;unsafe bypass&lt;/code&gt;
definition contained an unquoted backtick-wrapped &lt;code dir=&quot;auto&quot;&gt;bypass_used: true&lt;/code&gt;
literal that &lt;code dir=&quot;auto&quot;&gt;yaml.safe_load&lt;/code&gt; interpreted as a nested mapping. The
definition value is now double-quoted; semantic content unchanged.
File now parses cleanly under &lt;code dir=&quot;auto&quot;&gt;yaml.safe_load&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ruamel.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;documentation-1&quot;&gt;Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission-review report&lt;/strong&gt; at
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/quality-devex-hardening-3-2-01KRJGKH/mission-review.md&lt;/code&gt;
citing every doctrine tactic applied per WP and linking the
code-patterns catalog (NFR-006 / FR-012).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Post-merge audit report&lt;/strong&gt; at
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/quality-devex-hardening-3-2-01KRJGKH/post-merge-review.md&lt;/code&gt; —
independent adversarial review confirming PASS WITH NOTES (no code
defects; release-readiness gated on three operator-action items:
Sonar hotspot rationale application, NFR-001 smoke execution, and the
push-time Sonar workflow flip). Documents FR coverage matrix, drift
findings, silent-failure scan, and security notes. All four
post-merge stale-assertion findings classified as false alarms.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;NFR-001 release-stability smoke recipe&lt;/strong&gt; at
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/quality-devex-hardening-3-2-01KRJGKH/nfr-001-smoke-recipe.md&lt;/code&gt;
for operator execution post-merge.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SonarCloud hotspot rationales&lt;/strong&gt; at
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/quality-devex-hardening-3-2-01KRJGKH/sonar-hotspot-rationales.md&lt;/code&gt;
documenting the 4 encrypt-data hotspots for operator application in the
Sonar UI before push-time CI restoration (#825).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ADR &lt;code dir=&quot;auto&quot;&gt;2026-05-14-1-stale-lane-auto-rebase-classifier-policy&lt;/code&gt;&lt;/strong&gt; for #771.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;deferred-1&quot;&gt;Deferred&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Push-time SonarCloud restoration&lt;/strong&gt; (#825 / FR-004): gated on the
operator applying the four hotspot rationales in the Sonar UI and the
sonar quality gate flipping to &lt;code dir=&quot;auto&quot;&gt;OK&lt;/code&gt; (at audit time: ERROR —
&lt;code dir=&quot;auto&quot;&gt;new_coverage&lt;/code&gt; 58.9% vs threshold 80%; &lt;code dir=&quot;auto&quot;&gt;new_security_hotspots_reviewed&lt;/code&gt;
0% vs threshold 100%). The
&lt;code dir=&quot;auto&quot;&gt;.github/workflows/ci-quality.yml::sonarcloud&lt;/code&gt; conditional remains on
&lt;code dir=&quot;auto&quot;&gt;schedule || workflow_dispatch&lt;/code&gt; until gate is OK. See
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/quality-devex-hardening-3-2-01KRJGKH/sonar-pre-flip-verification.txt&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-1&quot;&gt;Removed&lt;/h3&gt;
&lt;h2 id=&quot;320rc8---2026-05-14&quot;&gt;[3.2.0rc8] - 2026-05-14&lt;/h2&gt;
&lt;p&gt;3.2.0rc8 rolls up the post-rc7 TeamSpace launch fixes and compatibility
cleanup needed before the final 3.2.0 cut. It includes defensive sync batching
for real edge-proxy limits, the Mission Dossier event-envelope migration for
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&gt;=5.0.0&lt;/code&gt;, and the small compatibility/quality fixes that
landed after rc7.&lt;/p&gt;
&lt;h3 id=&quot;changed-18&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Reduced the CLI’s default sync batch decompressed byte budget to 256 KiB and
added a 512 KiB hard ceiling for over-generous server-advertised limits, so
large TeamSpace queue drains split into safe requests instead of relying on
HTTP 413 retry shrinkage.&lt;/li&gt;
&lt;li&gt;Migrated all four Mission Dossier event emitters to the namespaced envelope
required by &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&gt;=5.0.0&lt;/code&gt;, including &lt;code dir=&quot;auto&quot;&gt;namespace&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;artifact_id&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;expected_identity&lt;/code&gt;, content refs, and schema-compatible
diagnostics.&lt;/li&gt;
&lt;li&gt;Preserved legacy queued Mission Dossier events by migrating flat queued
payloads on drain when namespace data is available, and kept queue coalescing
scoped correctly across both legacy and namespaced payload shapes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-18&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Restored agent profile list compatibility after the rc7 candidate.&lt;/li&gt;
&lt;li&gt;Reduced SonarCloud noise in path helper and charter synthesizer code without
changing runtime behavior.&lt;/li&gt;
&lt;li&gt;Fixed the deployed-dev TeamSpace sync canary failure where a 1200-event
backlog could cascade into 1000 HTTP 413 failures.&lt;/li&gt;
&lt;li&gt;Fixed SaaS ingestion rejection of CLI-emitted Mission Dossier artifact events
caused by the old flat payload shape being rejected with
&lt;code dir=&quot;auto&quot;&gt;Additional properties are not allowed&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc7---2026-05-12&quot;&gt;[3.2.0rc7] - 2026-05-12&lt;/h2&gt;
&lt;p&gt;3.2.0rc7 lands the &lt;code dir=&quot;auto&quot;&gt;review-merge-gate-hardening-3-2-x-01KRC57C&lt;/code&gt; mission
covering the remaining 3.2.x P1 release blockers plus a narrowed slice of the
charter encoding chokepoint, with post-merge remediation, SonarCloud
new-code gate cleanup, and CI portability fixes folded in.&lt;/p&gt;
&lt;h3 id=&quot;added-15&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;New canonical &lt;code dir=&quot;auto&quot;&gt;KittyInternalConsistencyError&lt;/code&gt; base under
&lt;code dir=&quot;auto&quot;&gt;src/kernel/errors.py&lt;/code&gt;, with &lt;code dir=&quot;auto&quot;&gt;CharterEncodingError&lt;/code&gt; now inheriting from it
so any UI/CLI/TUI surface can render structured remediation uniformly.&lt;/li&gt;
&lt;li&gt;Reusable SonarCloud branch-review snippet at
&lt;code dir=&quot;auto&quot;&gt;work/snippets/sonarcloud_branch_review.sh&lt;/code&gt; (qualitygates/project_status +
measures/component_tree + issues/search via REST API).&lt;/li&gt;
&lt;li&gt;Architectural decision record
&lt;code dir=&quot;auto&quot;&gt;architecture/adrs/2026-05-11-1-defer-391-structural-extraction-from-3-2-x.md&lt;/code&gt;
deferring still-open &lt;code dir=&quot;auto&quot;&gt;#391&lt;/code&gt; sub-tickets (&lt;code dir=&quot;auto&quot;&gt;#612&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#613&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;#614&lt;/code&gt;) from
3.2.x scope, on top of the shared-package-boundary cutover precedent.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-19&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Refactored &lt;code dir=&quot;auto&quot;&gt;_bake_mission_number_into_mission_branch&lt;/code&gt; in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/merge.py&lt;/code&gt; from cognitive complexity 22 down
to a flat coordinator backed by six named predicate / effect helpers, with
no behavior change.&lt;/li&gt;
&lt;li&gt;Narrowed broad &lt;code dir=&quot;auto&quot;&gt;except&lt;/code&gt; clauses in &lt;code dir=&quot;auto&quot;&gt;src/charter/_io.py&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;src/charter/compiler.py&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;src/charter/interview.py&lt;/code&gt; so charter
encoding errors propagate to the canonical handler instead of being
swallowed.&lt;/li&gt;
&lt;li&gt;Wired &lt;code dir=&quot;auto&quot;&gt;assert_pytest_available()&lt;/code&gt; into the production review preflight in
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/review/__init__.py&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-19&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Pre-merge mission-review remediation of findings &lt;code dir=&quot;auto&quot;&gt;D1&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;D2&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;D3&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;S1&lt;/code&gt;,
and &lt;code dir=&quot;auto&quot;&gt;S2&lt;/code&gt; against the canonical issue matrix at
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/review-merge-gate-hardening-3-2-x-01KRC57C/issue-matrix.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Repaired 18 pre-existing test failures by extracting a shared
&lt;code dir=&quot;auto&quot;&gt;setup_mocked_env()&lt;/code&gt; context manager to &lt;code dir=&quot;auto&quot;&gt;tests/mocked_env.py&lt;/code&gt; and rewiring
the affected sites onto it.&lt;/li&gt;
&lt;li&gt;CI portability: &lt;code dir=&quot;auto&quot;&gt;tests/integration/test_pytest_venv_concurrency.py&lt;/code&gt; now
invokes pytest through &lt;code dir=&quot;auto&quot;&gt;sys.executable&lt;/code&gt; instead of relying on a bare &lt;code dir=&quot;auto&quot;&gt;uv&lt;/code&gt;
on &lt;code dir=&quot;auto&quot;&gt;$PATH&lt;/code&gt;, which is not guaranteed inside slow-test CI shards.&lt;/li&gt;
&lt;li&gt;Cleared the SonarCloud new-code coverage gate for the branch by adding 26
focused coverage tests under &lt;code dir=&quot;auto&quot;&gt;tests/kernel/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tests/charter/&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;tests/core/test_paths_coverage_supplements.py&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Repaired dead links to the deleted &lt;code dir=&quot;auto&quot;&gt;kitty-specs/_drafts/&lt;/code&gt; directory in the
3.2.x deferral ADR and the mission spec after the pre-PR cleanup pass.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc6---2026-05-11&quot;&gt;[3.2.0rc6] - 2026-05-11&lt;/h2&gt;
&lt;p&gt;3.2.0rc6 includes the post-rc5 TeamSpace migration enforcement and dry-run
compatibility fixes needed before publishing the next TeamSpace-ready CLI
candidate.&lt;/p&gt;
&lt;h3 id=&quot;changed-20&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Surface pending TeamSpace mission-state migration during &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;
and require a clean migration before hosted TeamSpace connection flows.&lt;/li&gt;
&lt;li&gt;Allow the release compatibility gate to prove SaaS-supported dependency
versions when the candidate CLI declares a compatible range instead of an
exact pin.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-20&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Render user-friendly TeamSpace migration gate failures when mission-state
repair raises unexpected payload or filesystem errors.&lt;/li&gt;
&lt;li&gt;Preserve SaaS-disabled sync opt-in behavior while still enforcing
mission-state readiness for hosted sync paths.&lt;/li&gt;
&lt;li&gt;Synthesize historical approval evidence during TeamSpace dry-run conversion
so approved/done mission-state rows can validate against the canonical event
contract.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc5---2026-05-11&quot;&gt;[3.2.0rc5] - 2026-05-11&lt;/h2&gt;
&lt;p&gt;3.2.0rc5 closes the remaining CLI-side TeamSpace migration readiness gaps found
while rechecking the historical mission-state migration parent issue.&lt;/p&gt;
&lt;h3 id=&quot;changed-21&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Documented the deterministic historical mission-state repair contract and
safe release sequencing used before any repository-wide repair is required.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-21&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Block TeamSpace dry-run/import envelope synthesis when audit findings still
contain TeamSpace blockers, so legacy mission-state rows cannot bypass the
readiness audit.&lt;/li&gt;
&lt;li&gt;Reject historical mission-state sync batches with legacy status fields before
network submission, preserving the local queue and returning remediation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc4---2026-05-11&quot;&gt;[3.2.0rc4] - 2026-05-11&lt;/h2&gt;
&lt;p&gt;3.2.0rc4 tightens the TeamSpace release candidate against the published
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; 5.0.0 contract and includes the latest migration rehearsal
diagnostics.&lt;/p&gt;
&lt;h3 id=&quot;changed-22&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Tightened the CLI &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; dependency to &lt;code dir=&quot;auto&quot;&gt;&gt;=5.0.0,&amp;#x3C;6.0.0&lt;/code&gt; now
that the 5.0.0 TeamSpace canonical event contract is published to PyPI
(#978).&lt;/li&gt;
&lt;li&gt;Included the TeamSpace dry-run row mapping diagnostics merged after rc3 so
migration rehearsals can trace source rows to synthesized TeamSpace envelopes
(#1014).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc3---2026-05-06&quot;&gt;[3.2.0rc3] - 2026-05-06&lt;/h2&gt;
&lt;p&gt;3.2.0rc3 fixes a TeamSpace dry-run compatibility gap found during the
historical mission-state migration rehearsal.&lt;/p&gt;
&lt;h3 id=&quot;fixed-22&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Synthesized minimal repo evidence for historical done rows that only
preserved review evidence, allowing &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --teamspace-dry-run&lt;/code&gt;
to validate those rows against the &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; 5.0.0 payload contract
(#997).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc2---2026-05-05&quot;&gt;[3.2.0rc2] - 2026-05-05&lt;/h2&gt;
&lt;p&gt;3.2.0rc2 adds the TeamSpace mission-state repair and validation surface needed
before public TeamSpace import. The repair command is available now; the
TeamSpace dry-run path requires &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&gt;=5.0.0&lt;/code&gt; once that contract
package is published.&lt;/p&gt;
&lt;h3 id=&quot;added-16&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added deterministic &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --fix&lt;/code&gt; repair for historical
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; state, including Git safety checks, migration manifests, legacy
key cleanup, typed-row quarantine, lane normalization, and production
&lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; rematerialization (#980).&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --teamspace-dry-run&lt;/code&gt; to synthesize canonical
TeamSpace envelopes in memory and validate them with the 5.0.0 event contract
when available (#980).&lt;/li&gt;
&lt;li&gt;Documented the distributed Git repair workflow for coordinated repository
migration before TeamSpace launch (#980).&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --include-fixtures&lt;/code&gt; and the packaged
mission-state survey fixture pack used by the TeamSpace readiness audit
contract (#920, #922, #929).&lt;/li&gt;
&lt;li&gt;Added an opt-in &lt;code dir=&quot;auto&quot;&gt;TeamSpace Mission-State Readiness&lt;/code&gt; GitHub Actions workflow
that runs &lt;code dir=&quot;auto&quot;&gt;doctor mission-state --audit --fail-on teamspace-blocker&lt;/code&gt; and
uploads the JSON audit artifact (#920, #934).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-23&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Aligned CLI sync emission for &lt;code dir=&quot;auto&quot;&gt;WPStatusChanged&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;MissionClosed&lt;/code&gt; with the
canonical TeamSpace event payload shape while keeping launch dry-run gated on
the published events contract (#980).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;doctor mission-state --audit&lt;/code&gt; JSON reports now expose TeamSpace blocker
counts, and &lt;code dir=&quot;auto&quot;&gt;--fail-on teamspace-blocker&lt;/code&gt; gates import/sync readiness
without requiring network access (#920, #934).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320rc1---2026-05-05&quot;&gt;[3.2.0rc1] - 2026-05-05&lt;/h2&gt;
&lt;p&gt;3.2.0rc1 is the first release candidate for the 3.2.0 line. It rolls up the
workflow stabilization work from the alpha series and the final release
confidence missions.&lt;/p&gt;
&lt;h3 id=&quot;fixed-23&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Hardened the mission status, review, and merge surfaces that block reliable
implement-review-retrospect loops, including stale review verdict handling,
finalized-board routing, canonical review feedback pointers, and first-class
retrospective synthesis paths.&lt;/li&gt;
&lt;li&gt;Fixed task-board progress semantics so done-only counts are no longer paired
with unlabeled weighted readiness percentages; JSON status output now exposes
explicit progress semantics and weighted readiness fields (#966).&lt;/li&gt;
&lt;li&gt;Added an installed dependency drift guard for shared packages so release and
review evidence fail when the active environment disagrees with &lt;code dir=&quot;auto&quot;&gt;uv.lock&lt;/code&gt; for
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;spec-kitty-tracker&lt;/code&gt; (#848).&lt;/li&gt;
&lt;li&gt;Addressed final mission-review regressions around machine-facing contract
output, sync-control side effects, and the charter golden-path E2E assertion.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;release-validation&quot;&gt;Release Validation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Closed the stale ruff blocker after &lt;code dir=&quot;auto&quot;&gt;uv run ruff check src tests&lt;/code&gt; passed on
current &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; (#869).&lt;/li&gt;
&lt;li&gt;Re-ran final local release gates from fresh &lt;code dir=&quot;auto&quot;&gt;origin/main&lt;/code&gt;: dependency sync,
lock validation, installed shared-package drift guard, ruff, and the
contract/architectural/release pytest batch all passed.&lt;/li&gt;
&lt;li&gt;GitHub Actions on the release candidate base commit passed &lt;code dir=&quot;auto&quot;&gt;CI Quality&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;ci-windows&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;Protect Main Branch&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;known-limitations-1&quot;&gt;Known Limitations&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;The broad strict mypy gate remains tracked for follow-up in #971 and is not a
blocking gate for this release candidate.&lt;/li&gt;
&lt;li&gt;Hosted sync drain reliability has a known SaaS-sync limitation tracked in
#889; do not treat this release candidate as proof of full hosted drain
reliability until that issue is fixed.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a10---2026-05-04&quot;&gt;[3.2.0a10] - 2026-05-04&lt;/h2&gt;
&lt;p&gt;3.2.0a10 is a prerelease that stabilizes the implement-review-retrospect
control loop after the 3.2.0 release-blocker triage.&lt;/p&gt;
&lt;h3 id=&quot;fixed-24&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Rejection transitions from &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; now derive or require structured
rejected review results before mutating task state, closing the gap where
reviewer feedback could fail without a durable review result (#960).&lt;/li&gt;
&lt;li&gt;Review feedback pointers are canonicalized to &lt;code dir=&quot;auto&quot;&gt;review-cycle://...&lt;/code&gt; URIs and
legacy &lt;code dir=&quot;auto&quot;&gt;feedback://&lt;/code&gt; references are normalized or resolved with a warning,
preserving focused fix-mode context across rejection cycles (#962).&lt;/li&gt;
&lt;li&gt;Written &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt; artifacts now include required YAML frontmatter
before they can be referenced, and invalid review artifacts fail closed
instead of leaving dangling status pointers (#963).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; now treats finalized task boards and work-package lane
state as authoritative in query mode without bypassing mutating runtime
composition or retrospective terminus handling (#961).&lt;/li&gt;
&lt;li&gt;Completed missions now have a usable &lt;code dir=&quot;auto&quot;&gt;agent retrospect synthesize&lt;/code&gt; path when
&lt;code dir=&quot;auto&quot;&gt;retrospective.yaml&lt;/code&gt; is missing, with JSON output that distinguishes created,
synthesized, insufficient-artifacts, and mission-not-found outcomes (#965).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-4&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added targeted regression coverage for the shared review-cycle domain,
rejection transitions, canonical feedback resolution, finalized routing,
retrospective synthesis, and the focused implement-review-retrospect smoke
path.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a9---2026-05-03&quot;&gt;[3.2.0a9] - 2026-05-03&lt;/h2&gt;
&lt;p&gt;3.2.0a9 is a prerelease that adds mission-state audit diagnostics and hardens
the 3.2.0 workflow reliability path for implementation, review, merge, and
release-blocker triage.&lt;/p&gt;
&lt;h3 id=&quot;added-17&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added a read-only mission-state audit engine for inspecting mission status,
work package state, review artifacts, and lifecycle consistency without
mutating project state.&lt;/li&gt;
&lt;li&gt;Added reliability fixture coverage for branch, mission, review prompt, and
sync workflows used by the 3.2.0 release-blocker tranche.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-25&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Implementation start is now idempotent across planned, claimed, and
in-progress task states, preventing duplicate or inconsistent lifecycle
transitions (#946).&lt;/li&gt;
&lt;li&gt;Merge preflight now refreshes the target branch tracking ref before enforcing
target-branch synchronization, so stale local &lt;code dir=&quot;auto&quot;&gt;origin/main&lt;/code&gt; state cannot
allow an unsafe merge (#959).&lt;/li&gt;
&lt;li&gt;Merge, review prompt, worktree ownership, sync finalization, and review
artifact consistency checks now have tighter diagnostics and regression
coverage for the 3.2.0 workflow reliability tranche (#959).&lt;/li&gt;
&lt;li&gt;Command JSON output now avoids leaking non-serializable status event mocks in
covered move-task paths, preserving strict JSON command contracts.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-5&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Recorded the atomic work-package start lifecycle ADR and expanded regression
coverage around status persistence, bootstrap seeding, merge preflight, and
test sync isolation.&lt;/li&gt;
&lt;li&gt;Restored CI release confidence by covering the previously failing
&lt;code dir=&quot;auto&quot;&gt;fast-tests-core-misc&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;integration-tests-merge&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;integration-tests-cli&lt;/code&gt;,
and &lt;code dir=&quot;auto&quot;&gt;diff-coverage&lt;/code&gt; gates.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a8---2026-05-01&quot;&gt;[3.2.0a8] - 2026-05-01&lt;/h2&gt;
&lt;p&gt;3.2.0a8 is a prerelease that hardens direct SaaS sync ingress around the
Private Teamspace boundary. CLI sync side effects now resolve a canonical
Private Teamspace target, rehydrate session membership once when needed, and
skip direct ingress with a diagnostic instead of falling back to a shared team.&lt;/p&gt;
&lt;h3 id=&quot;fixed-26&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Direct sync ingress for &lt;code dir=&quot;auto&quot;&gt;/api/v1/events/batch/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;/api/v1/ws-token&lt;/code&gt; now
uses a strict Private Teamspace resolver and refuses shared-team fallbacks
from stale &lt;code dir=&quot;auto&quot;&gt;default_team_id&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;teams[0]&lt;/code&gt;, or websocket state (#943).&lt;/li&gt;
&lt;li&gt;Auth refresh and session rehydration now update team membership from
&lt;code dir=&quot;auto&quot;&gt;/api/v1/me&lt;/code&gt;, recomputing &lt;code dir=&quot;auto&quot;&gt;default_team_id&lt;/code&gt; from the refreshed private team
list instead of preserving stale shared defaults (#943).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; command stdout remains parseable when SaaS sync cannot connect or
cannot resolve a Private Teamspace; sync diagnostics route to stderr or
structured logs rather than contaminating stdout (#943).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-6&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added strict resolver, sync call-site, websocket, offline queue, and
strict-JSON regression coverage for the Private Teamspace ingress boundary.&lt;/li&gt;
&lt;li&gt;Added mission review evidence for
&lt;code dir=&quot;auto&quot;&gt;private-teamspace-ingress-safeguards-01KQH03Y&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a7---2026-05-01&quot;&gt;[3.2.0a7] - 2026-05-01&lt;/h2&gt;
&lt;p&gt;3.2.0a7 is a focused prerelease that bounds WebSocket sync startup and
shutdown behavior. Short-lived agent commands now fail over to batch sync
instead of hanging indefinitely when a local sync socket accepts the
connection but never emits the initial snapshot.&lt;/p&gt;
&lt;h3 id=&quot;fixed-27&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;WebSocket sync startup now has bounded open, initial snapshot, and close
deadlines so &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission setup-plan&lt;/code&gt; and other short-lived
commands degrade to batch sync instead of blocking forever on a stalled
sync socket (#936).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-7&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added regression coverage for a WebSocket connection that never sends the
initial snapshot and for shutdown paths where the close handshake stalls.&lt;/li&gt;
&lt;li&gt;Aligned existing Bandit suppressions in touched sync/readiness callsites so
local and CI security scans recognize the intended safe dynamic SQL and
localhost URL patterns.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a6---2026-04-30&quot;&gt;[3.2.0a6] - 2026-04-30&lt;/h2&gt;
&lt;p&gt;3.2.0a6 is a prerelease hardening sweep that restores the documented
fresh-project golden path (&lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt; → charter &lt;code dir=&quot;auto&quot;&gt;setup&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt;/
&lt;code dir=&quot;auto&quot;&gt;synthesize&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;), locks in strict JSON for covered &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; commands
under any SaaS state, fixes agent identity parsing and review-cycle
accounting, adds paired profile-invocation lifecycle observability for
&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt;, and tightens merge/review/status recovery paths. The
release introduces the new top-level &lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt; mission-review
command and no new top-level runtime dependencies.&lt;/p&gt;
&lt;h3 id=&quot;fixed-28&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter bundle validate --json&lt;/code&gt; now fail-closes on incomplete Charter
synthesis state while preserving strict JSON stdout. Sidecar-only bundles,
manifest-only bundles, incompatible bundle versions, missing provenance
sidecars, dangling sidecar references, and synthesis manifest integrity
failures all produce parseable failure envelopes with actionable
&lt;code dir=&quot;auto&quot;&gt;synthesis_state&lt;/code&gt; details (#914, closes the final Phase 7 release gap for
#469/#515).&lt;/li&gt;
&lt;li&gt;Stamp &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; and a &lt;code dir=&quot;auto&quot;&gt;schema_capabilities&lt;/code&gt; block in
&lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; so a fresh project no
longer requires hand-edits before subsequent CLI commands; existing
schema fields are preserved (additive, idempotent) (#840, WP01).&lt;/li&gt;
&lt;li&gt;Strict JSON envelope contract for covered &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; commands: stdout is
parseable by &lt;code dir=&quot;auto&quot;&gt;json.loads&lt;/code&gt; regardless of SaaS sync state (disabled,
unauthorized, network-failed, success); sync/auth diagnostics route to
stderr or nest inside the envelope (#842, WP02).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;WPMetadata.resolved_agent()&lt;/code&gt; parses 4-segment colon-delimited agent
strings (&lt;code dir=&quot;auto&quot;&gt;tool:model:profile:role&lt;/code&gt;) and preserves every supplied field
through implement and review prompt rendering, with deterministic
fallback for partial strings (#833, WP03).&lt;/li&gt;
&lt;li&gt;Review-cycle counter advances exactly once per genuine reviewer
rejection; reclaim/regenerate of an &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; prompt no longer
inflates the counter or writes a spurious &lt;code dir=&quot;auto&quot;&gt;review-cycle-N.md&lt;/code&gt;
artifact (#676, WP04).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; writes paired &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; profile-invocation
lifecycle records keyed to the canonical mission step + action it
issued, observable via &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor invocation-pairing&lt;/code&gt; (#843,
WP05).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; auto-tracks the produced &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt; and ensures
the required &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; entries exist; &lt;code dir=&quot;auto&quot;&gt;charter bundle validate&lt;/code&gt;
succeeds immediately afterwards with no operator &lt;code dir=&quot;auto&quot;&gt;git add&lt;/code&gt; between
the two commands. Outside a git working tree, &lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt; fails fast
with an actionable error that names &lt;code dir=&quot;auto&quot;&gt;git init&lt;/code&gt; as the remediation
(#841, WP06).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;charter synthesize&lt;/code&gt; succeeds on a fresh project via the public CLI
with no hand-seeded &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt;; the bounded fresh-project
path materialises a minimal doctrine tree (&lt;code dir=&quot;auto&quot;&gt;PROVENANCE.md&lt;/code&gt;) so the
shipped doctrine layer can supply content (#839, WP06).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty merge --abort&lt;/code&gt; now clears the global merge lock, removes
legacy merge-state files, aborts an in-progress Git merge when present,
and remains idempotent when no merge is active (#903).&lt;/li&gt;
&lt;li&gt;Approved/done work packages with stale &lt;code dir=&quot;auto&quot;&gt;verdict: rejected&lt;/code&gt; review
artifacts are now surfaced across status views, including
&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;show_kanban_status()&lt;/code&gt;. Review
artifact lookup follows the real &lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;WP-slug&gt;/review-cycle-N.md&lt;/code&gt;
layout, and &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; work packages now warn when reviewer movement
stalls beyond the configured threshold (#904, #909).&lt;/li&gt;
&lt;li&gt;Review lane-guard failures now name the planning branch and include a
concrete &lt;code dir=&quot;auto&quot;&gt;git show &amp;#x3C;planning-branch&gt;:&amp;#x3C;path&gt;&lt;/code&gt; command for the first
contaminated path, instead of a placeholder path (#905).&lt;/li&gt;
&lt;li&gt;Work-package review definition-of-done coverage now includes real error
path and artifact-deletion regressions, not only happy-path review
behavior (#906).&lt;/li&gt;
&lt;li&gt;Broad &lt;code dir=&quot;auto&quot;&gt;except Exception&lt;/code&gt; / BLE001 suppressions in touched runtime paths
were audited and now carry inline justification where fail-open behavior
is intentional (#907).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty review &amp;#x3C;mission&gt;&lt;/code&gt; is now a first-class mission-review CLI
command with structured status/exit behavior for post-merge mission
fidelity checks (#908).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-8&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Consolidated golden-path E2E (&lt;code dir=&quot;auto&quot;&gt;tests/e2e/test_charter_epic_golden_path.py&lt;/code&gt;)
rewritten to drive the fresh-project chain through the public CLI
only - no hand seeding of &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt;, no edits to
&lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;, no manual &lt;code dir=&quot;auto&quot;&gt;git add&lt;/code&gt; of charter artifacts
between &lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;bundle validate&lt;/code&gt;. Runs in well under the
120-second NFR-007 budget. Also exercises strict JSON parsability of
&lt;code dir=&quot;auto&quot;&gt;mission branch-context --json&lt;/code&gt; (WP02 spot-check) and the &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt;
lifecycle record (WP05 spot-check) (WP07).&lt;/li&gt;
&lt;li&gt;Governance setup docs (&lt;code dir=&quot;auto&quot;&gt;docs/how-to/setup-governance.md&lt;/code&gt;) note that
&lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; now auto-tracks &lt;code dir=&quot;auto&quot;&gt;charter.md&lt;/code&gt;, removing any
expectation that operators run &lt;code dir=&quot;auto&quot;&gt;git add&lt;/code&gt; between &lt;code dir=&quot;auto&quot;&gt;generate&lt;/code&gt; and
&lt;code dir=&quot;auto&quot;&gt;bundle validate&lt;/code&gt; (WP07).&lt;/li&gt;
&lt;li&gt;Added regression coverage for merge abort cleanup, stale rejected review
artifacts, stalled in-review work packages, lane-guard remediation text,
mission-review command behavior, review DoD deletion/error cases, and
agent-shard coverage for status warning paths (#903-#909).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;tranche-2-acceptance-pass-sc-001sc-008&quot;&gt;Tranche-2 acceptance pass (SC-001..SC-008)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;SC-001 (Fresh-path completion)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;tests/e2e/test_charter_epic_golden_path.py::test_charter_epic_golden_path&lt;/code&gt; walks &lt;code dir=&quot;auto&quot;&gt;init → charter interview → generate → bundle validate → synthesize → mission create → setup-plan → finalize-tasks → next&lt;/code&gt; against a fresh project with no &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; hand-edits and no &lt;code dir=&quot;auto&quot;&gt;git add&lt;/code&gt; of charter artifacts. Passes locally in &amp;#x3C;20s.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SC-002 (JSON parsability)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;tests/integration/test_json_envelope_strict.py&lt;/code&gt; (WP02) covers the SaaS state matrix; the consolidated E2E spot-checks &lt;code dir=&quot;auto&quot;&gt;mission branch-context --json&lt;/code&gt; via &lt;code dir=&quot;auto&quot;&gt;json.loads(stdout)&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SC-003 (Identity preservation rate)&lt;/strong&gt; - WP03 unit + integration tests cover colon arities 1–4 and assert &lt;code dir=&quot;auto&quot;&gt;model&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;profile_id&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;role&lt;/code&gt; in rendered prompts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SC-004 (Review-cycle precision)&lt;/strong&gt; - WP04 tests assert the counter is unchanged across ≥3 reclaim/regenerate runs and advances by exactly 1 on a real rejection.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SC-005 (Lifecycle observability)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;tests/integration/test_next_lifecycle_records.py&lt;/code&gt; (WP05) covers ≥5 issuances with mid-cycle orphan; the consolidated E2E asserts at least one &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record after &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; issues an action and that the &lt;code dir=&quot;auto&quot;&gt;canonical_action_id&lt;/code&gt; matches the issued step id.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SC-006 (Charter parity rate)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/cli/commands/test_charter_generate_autotrack.py&lt;/code&gt; (WP06) covers the auto-track + non-git fail-fast contract; the consolidated E2E exercises &lt;code dir=&quot;auto&quot;&gt;generate → bundle validate&lt;/code&gt; with no intervening git ops.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SC-007 (Documentation/CLI agreement)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;docs/how-to/setup-governance.md&lt;/code&gt; updated; no documented governance-setup flow contains a &lt;code dir=&quot;auto&quot;&gt;git add charter.md&lt;/code&gt; step between &lt;code dir=&quot;auto&quot;&gt;charter generate&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;charter bundle validate&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SC-008 (Release-surface discipline)&lt;/strong&gt; - Diff inventory: one new top-level public CLI command, &lt;code dir=&quot;auto&quot;&gt;spec-kitty review&lt;/code&gt;, added for mission-review fidelity checks (#908); one new &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor invocation-pairing&lt;/code&gt; subcommand under the existing &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; group for lifecycle observability; zero new top-level runtime dependencies in &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;[project.dependencies]&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a5---2026-04-27&quot;&gt;[3.2.0a5] - 2026-04-27&lt;/h2&gt;
&lt;h3 id=&quot;fixed-29&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;CLI auth now consumes the server Tranche 2 contract end to end: logout posts refresh tokens to &lt;code dir=&quot;auto&quot;&gt;/oauth/revoke&lt;/code&gt;, local credential cleanup failures are reported truthfully, refresh handles benign 409 replay without resubmitting a spent token, and &lt;code dir=&quot;auto&quot;&gt;auth doctor --server&lt;/code&gt; checks &lt;code dir=&quot;auto&quot;&gt;/api/v1/session-status&lt;/code&gt; with safe re-authentication guidance (#902).&lt;/li&gt;
&lt;li&gt;Fix &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; silently leaving projects in PROJECT_MIGRATION_NEEDED state by stamping &lt;code dir=&quot;auto&quot;&gt;schema_version&lt;/code&gt; after metadata save (#705, WP01).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; in a non-git directory now prints an actionable “run &lt;code dir=&quot;auto&quot;&gt;git init&lt;/code&gt;” message (#636, WP05).&lt;/li&gt;
&lt;li&gt;Suppress misleading “shutdown / final-sync” red error lines after a successful &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent mission create --json&lt;/code&gt; payload (#735, WP06).&lt;/li&gt;
&lt;li&gt;Deduplicate “Not authenticated, skipping sync” / “token refresh failed” diagnostics to at most once per CLI invocation (#717, WP06).&lt;/li&gt;
&lt;li&gt;Fix &lt;code dir=&quot;auto&quot;&gt;read_events()&lt;/code&gt; raising &lt;code dir=&quot;auto&quot;&gt;KeyError(&apos;wp_id&apos;)&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;DecisionPointOpened&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;DecisionPointResolved&lt;/code&gt; events that share &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; with lane-transition events. Restores &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;materialize&lt;/code&gt; / dashboard for any mission that uses the decision moment Protocol (#830, WP08).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-24&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Loosen &lt;code dir=&quot;auto&quot;&gt;.python-version&lt;/code&gt; from a hard &lt;code dir=&quot;auto&quot;&gt;3.13&lt;/code&gt; pin to &lt;code dir=&quot;auto&quot;&gt;3.11&lt;/code&gt; (the floor declared by &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;) and restore &lt;code dir=&quot;auto&quot;&gt;mypy --strict&lt;/code&gt; cleanliness on &lt;code dir=&quot;auto&quot;&gt;mission_step_contracts/executor.py&lt;/code&gt; (#805, WP03).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-2&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Retire the deprecated &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.checklist&lt;/code&gt; command surface from every supported agent’s rendered output. The canonical requirements checklist at &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/checklists/requirements.md&lt;/code&gt; is unaffected (#815, supersedes #635, WP04).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;internal-9&quot;&gt;Internal&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Add regression tests confirming &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; aliases stay hidden from &lt;code dir=&quot;auto&quot;&gt;--help&lt;/code&gt; while remaining accepted (#790, WP07).&lt;/li&gt;
&lt;li&gt;Add regression test confirming &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent decision&lt;/code&gt; command shape stays consistent across docs / help / skill snapshots (#774, WP07).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-18&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Frontend Freddy agent profile&lt;/strong&gt; - browser-side implementer specialising in HTML/CSS/JavaScript/TypeScript, component frameworks (React, Vue, Svelte), WCAG 2.1 accessibility, Core Web Vitals performance, and frontend testing (vitest, Playwright). Specialises from &lt;code dir=&quot;auto&quot;&gt;implementer-ivan&lt;/code&gt;. Self-review protocol enforces lint, type-check, unit/component tests, e2e smoke, axe accessibility gate, and bundle budget. Avoidance boundary explicitly names Node Norris’s server-side domain.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Node Norris agent profile&lt;/strong&gt; - server-side Node.js implementer specialising in HTTP APIs (Express/Fastify/NestJS), async/Promise discipline, streaming, npm security (&lt;code dir=&quot;auto&quot;&gt;npm audit&lt;/code&gt;), and integration testing (supertest). Specialises from &lt;code dir=&quot;auto&quot;&gt;implementer-ivan&lt;/code&gt;. Avoidance boundary explicitly names Frontend Freddy’s browser-rendering domain. The two profiles are mutually exclusive by design.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;BDD paradigm&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;behaviour-driven-development&lt;/code&gt;) - encodes BDD as a three-phase collaboration practice: Discovery (Three Amigos conversations), Formulation (Given/When/Then specifications), and Automation (executable living documentation). References &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_034&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_037&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;BDD Scenario Lifecycle procedure&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;bdd-scenario-lifecycle&lt;/code&gt;) - covers the Formulation → Automation → Maintenance phases that follow an Example Mapping Workshop. Toolchain-agnostic (Cucumber-JVM, Cucumber-JS, Behave, SpecFlow). Encodes four anti-patterns: imperative Gherkin, rubber-stamp scenarios, shared mutable state, and orphaned step definitions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New tactics:&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;reference-architectural-patterns&lt;/code&gt; - structured selection of named reference patterns (Layered, Hexagonal, Event-Driven, CQRS, Microservices, Modular Monolith) scored against coupling, scalability, and operational complexity constraints.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;development-bdd&lt;/code&gt; - architecture-level BDD tactic for expressing observable behavioral contracts at system boundaries before implementation; distinct from the existing &lt;code dir=&quot;auto&quot;&gt;behavior-driven-development&lt;/code&gt; technique tactic.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;bug-fixing-checklist&lt;/code&gt; - language-agnostic test-first defect resolution: write a reproduction test before touching production code.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;test-readability-clarity-check&lt;/code&gt; - dual-perspective reconstruction check: read only tests, reconstruct system understanding, compare against spec to surface documentation gaps.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;code-documentation-analysis&lt;/code&gt; - brownfield boundary discovery by extracting and clustering domain terminology from code and documentation artifacts. Contributes foundational analysis tactics toward the brownfield investigation skill described in &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/666&quot;&gt;#666&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;terminology-extraction-mapping&lt;/code&gt; - systematic extraction and relationship mapping of domain terms across multiple sources to produce a maintainable glossary. Complementary artifact to the bounded-context linguistic discovery approach targeted by &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/666&quot;&gt;#666&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tactic directory normalization&lt;/strong&gt; - shipped tactics reorganised into four category subdirectories: &lt;code dir=&quot;auto&quot;&gt;testing/&lt;/code&gt; (15 tactics), &lt;code dir=&quot;auto&quot;&gt;analysis/&lt;/code&gt; (14), &lt;code dir=&quot;auto&quot;&gt;communication/&lt;/code&gt; (7), &lt;code dir=&quot;auto&quot;&gt;architecture/&lt;/code&gt; (14). Cross-cutting tactics remain in the &lt;code dir=&quot;auto&quot;&gt;shipped/&lt;/code&gt; root. The existing &lt;code dir=&quot;auto&quot;&gt;rglob&lt;/code&gt; loader requires no changes.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;tasks-finalize&lt;/code&gt; command skill&lt;/strong&gt; - added to &lt;code dir=&quot;auto&quot;&gt;CANONICAL_COMMANDS&lt;/code&gt; in the agent skills pipeline and deployed to &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty.tasks-finalize/&lt;/code&gt;. Closes the gap where this command was missing from Codex/Vibe skill packages. &lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-25&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Profile enrichment&lt;/strong&gt; - four existing profiles updated with additive tactic and paradigm references:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;implementer-ivan&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;bug-fixing-checklist&lt;/code&gt; tactic reference (propagates to all specialist profiles via &lt;code dir=&quot;auto&quot;&gt;resolve_profile()&lt;/code&gt; union merge).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;reviewer-renata&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;test-readability-clarity-check&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;bdd-scenario-lifecycle&lt;/code&gt; tactic references; &lt;code dir=&quot;auto&quot;&gt;behaviour-driven-development&lt;/code&gt; paradigm in context sources.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;architect-alphonso&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;development-bdd&lt;/code&gt; tactic reference; BDD paradigm, example-mapping-workshop, and bdd-scenario-lifecycle in additional context sources.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;java-jenny&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;behavior-driven-development&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;bdd-scenario-lifecycle&lt;/code&gt; tactic references; &lt;code dir=&quot;auto&quot;&gt;bdd-scenarios&lt;/code&gt; self-review step (Cucumber-JVM + Serenity BDD gate).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;behavior-driven-development&lt;/code&gt; tactic enriched&lt;/strong&gt; - extended &lt;code dir=&quot;auto&quot;&gt;notes&lt;/code&gt; with a toolchain landscape section (Cucumber family, Playwright, Selenium, Serenity BDD, custom DSLs; source: &lt;code dir=&quot;auto&quot;&gt;patterns.sddevelopment.be/primers/toolchain-and-automation/bdd&lt;/code&gt;); three new &lt;code dir=&quot;auto&quot;&gt;failure_modes&lt;/code&gt; (rubber-stamp scenarios, shared mutable state between scenarios, orphaned step definitions); cross-references to the new BDD paradigm and procedure.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;tactic-references&lt;/code&gt; union-merged in &lt;code dir=&quot;auto&quot;&gt;resolve_profile()&lt;/code&gt;&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;tactic-references&lt;/code&gt; added to &lt;code dir=&quot;auto&quot;&gt;_LIST_FIELDS&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/doctrine/agent_profiles/repository.py&lt;/code&gt;. Specialist profiles now inherit base-profile tactic references via &lt;code dir=&quot;auto&quot;&gt;_union_merge&lt;/code&gt; at resolution time rather than overriding them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tactic compliance test extended&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;test_tactic_compliance.py&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;ARTIFACT_DIRS&lt;/code&gt; now includes &lt;code dir=&quot;auto&quot;&gt;procedure&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;paradigm&lt;/code&gt; types, enabling cross-type reference validation for tactics that reference procedures or paradigms.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shared package boundary cutover&lt;/strong&gt; (mission &lt;code dir=&quot;auto&quot;&gt;shared-package-boundary-cutover-01KQ22DS&lt;/code&gt;) - &lt;code dir=&quot;auto&quot;&gt;spec-kitty-runtime&lt;/code&gt; is no longer a dependency of &lt;code dir=&quot;auto&quot;&gt;spec-kitty-cli&lt;/code&gt;. The CLI now owns its own runtime internally under &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/next/_internal_runtime/&lt;/code&gt;; &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; works from a clean install of &lt;code dir=&quot;auto&quot;&gt;spec-kitty-cli&lt;/code&gt; alone. &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty-tracker&lt;/code&gt; are external PyPI dependencies consumed via their public import surfaces (&lt;code dir=&quot;auto&quot;&gt;spec_kitty_events&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec_kitty_tracker&lt;/code&gt;). The vendored events tree under &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/spec_kitty_events/&lt;/code&gt; has been removed (~23 kLoC). Developers who relied on editable cross-package overrides should consult &lt;a href=&quot;/development/how-to/local-overrides/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/development/local-overrides.md&lt;/code&gt;&lt;/a&gt;; operators upgrading from a pre-cutover release should consult &lt;a href=&quot;/migrations/shared-package-boundary-cutover/&quot;&gt;&lt;code dir=&quot;auto&quot;&gt;docs/migration/shared-package-boundary-cutover.md&lt;/code&gt;&lt;/a&gt;. Decision rationale recorded in &lt;a href=&quot;/adr/3.x/2026-04-25-1-shared-package-boundary/&quot;&gt;ADR 2026-04-25-1&lt;/a&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-3&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;constraints.txt&lt;/code&gt;&lt;/strong&gt; - the file existed solely to paper over a transitive pin conflict with the retired &lt;code dir=&quot;auto&quot;&gt;spec-kitty-runtime&lt;/code&gt; package and is no longer needed.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-30&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config list/status&lt;/code&gt; now checks global command roots for slash-command agents instead of reporting missing project-local command directories after &lt;code dir=&quot;auto&quot;&gt;init&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config add/sync --create-missing&lt;/code&gt; no longer recreates retired project-local command directories for globally managed slash-command agents.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config remove/sync&lt;/code&gt; now removes only the managed command surface for project-local agent directories, preserving unrelated files such as &lt;code dir=&quot;auto&quot;&gt;.github/workflows/&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added---documentation-mission-composition-rewrite-502-461-phase-6-wp64&quot;&gt;Added - Documentation mission composition rewrite (#502, #461, Phase 6 WP6.4)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Documentation mission now runs on the StepContractExecutor composition substrate, mirroring research (#504) and software-dev (#503). The runtime resolves the new composed step contracts ahead of the legacy &lt;code dir=&quot;auto&quot;&gt;mission.yaml&lt;/code&gt; workflow via the existing &lt;code dir=&quot;auto&quot;&gt;_resolve_runtime_template_in_root&lt;/code&gt; precedence - no loader changes were required.&lt;/li&gt;
&lt;li&gt;New runtime sidecar templates: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/documentation/mission-runtime.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/documentation/mission-runtime.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Six shipped step contracts under &lt;code dir=&quot;auto&quot;&gt;src/doctrine/mission_step_contracts/shipped/documentation-{discover,audit,design,generate,validate,publish}.step-contract.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Six action doctrine bundles under &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/documentation/actions/{discover,audit,design,generate,validate,publish}/&lt;/code&gt; (governance guidelines + directive/tactic indices).&lt;/li&gt;
&lt;li&gt;DRG action nodes and edges for &lt;code dir=&quot;auto&quot;&gt;action:documentation/{discover,audit,design,generate,validate,publish}&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;src/doctrine/graph.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Composition wiring in &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/next/runtime_bridge.py&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;_COMPOSED_ACTIONS_BY_MISSION[&quot;documentation&quot;]&lt;/code&gt; and a fail-closed guard branch in &lt;code dir=&quot;auto&quot;&gt;_check_composed_action_guard()&lt;/code&gt; raising a structured error for unknown documentation actions. &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/mission_step_contracts/executor.py&lt;/code&gt; adds six &lt;code dir=&quot;auto&quot;&gt;_ACTION_PROFILE_DEFAULTS&lt;/code&gt; entries (&lt;code dir=&quot;auto&quot;&gt;researcher-robbie&lt;/code&gt; for discover/audit, &lt;code dir=&quot;auto&quot;&gt;architect-alphonso&lt;/code&gt; for design, &lt;code dir=&quot;auto&quot;&gt;implementer-ivan&lt;/code&gt; for generate, &lt;code dir=&quot;auto&quot;&gt;reviewer-renata&lt;/code&gt; for validate/publish).&lt;/li&gt;
&lt;li&gt;Real-runtime integration walk at &lt;code dir=&quot;auto&quot;&gt;tests/integration/test_documentation_runtime_walk.py&lt;/code&gt; proving SC-001 / SC-003 / SC-004 from a freshly initialized temp repo.&lt;/li&gt;
&lt;/ul&gt;
&lt;h4 id=&quot;backward-compatibility&quot;&gt;Backward compatibility&lt;/h4&gt;
&lt;ul&gt;
&lt;li&gt;The legacy &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/documentation/mission.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;src/doctrine/missions/documentation/mission.yaml&lt;/code&gt; files remain on disk for backward reference. Existing documentation-mission projects that authored against the legacy workflow continue to work; runtime template resolution prefers the new &lt;code dir=&quot;auto&quot;&gt;mission-runtime.yaml&lt;/code&gt; ahead of the legacy file via the existing precedence in &lt;code dir=&quot;auto&quot;&gt;_resolve_runtime_template_in_root&lt;/code&gt; (no loader changes in this PR).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-19&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Upgrade compatibility planner&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now separates CLI
update guidance from current-project schema compatibility. New flags
&lt;code dir=&quot;auto&quot;&gt;--cli&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--project&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;--no-nag&lt;/code&gt; support CLI-only guidance,
project-only migrations, non-interactive confirmation, and explicit nag
suppression. &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --dry-run --json&lt;/code&gt; emits the stable
compatibility-plan contract for automation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Host-surface parity matrix&lt;/strong&gt; at &lt;code dir=&quot;auto&quot;&gt;docs/host-surface-parity.md&lt;/code&gt; - authoritative record of how each of the 15 supported host surfaces teaches the standalone dispatch governance-injection contract. Closes the remaining &lt;code dir=&quot;auto&quot;&gt;#496&lt;/code&gt; host-surface breadth rollout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mode of work runtime derivation&lt;/strong&gt; - every standalone dispatch invocation records its &lt;code dir=&quot;auto&quot;&gt;mode_of_work&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;mission_step&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;query&lt;/code&gt;) on the &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; event. Derivation is from the CLI entry command.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Correlation links&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete&lt;/code&gt; accepts &lt;code dir=&quot;auto&quot;&gt;--artifact &amp;#x3C;path&gt;&lt;/code&gt; (repeatable) and &lt;code dir=&quot;auto&quot;&gt;--commit &amp;#x3C;sha&gt;&lt;/code&gt; (singular); each appends an additive event to the invocation JSONL for single-file request→artifact/commit correlation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SaaS read-model policy&lt;/strong&gt; at &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/projection_policy.py&lt;/code&gt; - typed module mapping &lt;code dir=&quot;auto&quot;&gt;(mode, event)&lt;/code&gt; to projection rules. Documented in &lt;code dir=&quot;auto&quot;&gt;docs/trail-model.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tier 2 SaaS projection decision&lt;/strong&gt; - decisively documented as deferred in &lt;code dir=&quot;auto&quot;&gt;docs/trail-model.md&lt;/code&gt;. Tier 2 evidence stays local-only in 3.2.x.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;README Governance layer subsection&lt;/strong&gt; - entry point for operators discovering standalone dispatch.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;decision moment Ledger (V1)&lt;/strong&gt; - new &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent decision&lt;/code&gt; subgroup with five
subcommands: &lt;code dir=&quot;auto&quot;&gt;open&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;resolve&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;defer&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;cancel&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;verify&lt;/code&gt;. Mints ULID &lt;code dir=&quot;auto&quot;&gt;decision_id&lt;/code&gt;s
at interview ask-time, writes paper trail under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/decisions/&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;index.json&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;DM-&amp;#x3C;id&gt;.md&lt;/code&gt;), and appends &lt;code dir=&quot;auto&quot;&gt;DecisionPointOpened(interview)&lt;/code&gt; /
&lt;code dir=&quot;auto&quot;&gt;DecisionPointResolved(interview)&lt;/code&gt; events to &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;. Local-only;
no SaaS sync required.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Charter integration&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter interview&lt;/code&gt; now calls &lt;code dir=&quot;auto&quot;&gt;decision open&lt;/code&gt;
before each question and the appropriate terminal command after each answer.
&lt;code dir=&quot;auto&quot;&gt;answers.yaml&lt;/code&gt; behavior is unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Specify + Plan template updates&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;specify.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt; source templates
gain a decision moment Protocol section instructing the LLM to call decision
subcommands at ask/resolution time and write &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;!-- decision_id: &amp;#x3C;id&gt; --&gt;&lt;/code&gt; anchors
for deferred decisions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;decision verify&lt;/code&gt; gate&lt;/strong&gt; - scans &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;plan.md&lt;/code&gt; for
&lt;code dir=&quot;auto&quot;&gt;[NEEDS CLARIFICATION: ...] &amp;#x3C;!-- decision_id: &amp;#x3C;id&gt; --&gt;&lt;/code&gt; sentinels and
cross-checks against the decisions index. Exits non-zero on drift
(&lt;code dir=&quot;auto&quot;&gt;DEFERRED_WITHOUT_MARKER&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;MARKER_WITHOUT_DECISION&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;STALE_MARKER&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;widen mode (#758)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent decision widen&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;resolve --from-widen&lt;/code&gt;
lifecycle. Writes &lt;code dir=&quot;auto&quot;&gt;widen-pending.jsonl&lt;/code&gt;, emits &lt;code dir=&quot;auto&quot;&gt;DecisionPointWidened&lt;/code&gt; events,
integrates with charter/specify/plan widen affordances. Surfaces decision
write-back errors explicitly instead of silently suppressing them.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-26&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Project schema compatibility is now enforced by the centralized compat
planner. Out-of-date CLI notices are passive and throttled; incompatible
project schemas block unsafe commands with exit codes 4, 5, or 6 and exact
remediation guidance.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty profile-invocation complete --evidence&lt;/code&gt; is now mode-gated: rejected on non-evidence-eligible invocations with &lt;code dir=&quot;auto&quot;&gt;InvalidModeForEvidenceError&lt;/code&gt;. Rejection occurs before any write; the invocation stays open.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;_propagate_one&lt;/code&gt; consults the new projection policy after the sync-gate and authentication lookup. Existing &lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;mission_step&lt;/code&gt; projection behaviour is preserved exactly.&lt;/li&gt;
&lt;li&gt;Dashboard user-visible wording: the mission selector, current-mission header, overview heading, analysis heading, and empty-state prompt now read “Mission Run” / “mission” instead of “Feature”. Backend identifiers (CSS classes, HTML IDs, cookie keys, API route segments, JSON field names) are unchanged.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; bumped to &lt;code dir=&quot;auto&quot;&gt;==4.0.0&lt;/code&gt;&lt;/strong&gt; - vendored copy at
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/spec_kitty_events/&lt;/code&gt; refreshed. Introduces
&lt;code dir=&quot;auto&quot;&gt;DecisionPointOpenedInterviewPayload&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;DecisionPointResolvedInterviewPayload&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;OriginSurface.PLANNING_INTERVIEW&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;origin_surface: planning_interview&lt;/code&gt;),
&lt;code dir=&quot;auto&quot;&gt;OriginFlow&lt;/code&gt; enum (values &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;DecisionPointWidened&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;TerminalOutcome&lt;/code&gt; enum.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;[tool.uv.sources]&lt;/code&gt;&lt;/strong&gt; redirects &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;../spec-kitty-events/&lt;/code&gt;
in editable mode for monorepo development. Dev-only; ignored by pip / PyPI.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;deferred-2&quot;&gt;Deferred&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty explain&lt;/code&gt; (issue #534) remains deferred to Phase 5 pending DRG glossary addressability (#499, #759).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;out-of-scope-tracked-separately&quot;&gt;Out of scope (tracked separately)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;SaaS sync projection for widened decisions - tracked in spec-kitty-saas#110, #111.&lt;/li&gt;
&lt;li&gt;Tasks-phase interview support - future mission.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;migration-notes&quot;&gt;Migration notes&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;No operator action required for routine upgrade.&lt;/strong&gt; The trail model is additive:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Pre-mission invocation records (no &lt;code dir=&quot;auto&quot;&gt;mode_of_work&lt;/code&gt;) continue to accept &lt;code dir=&quot;auto&quot;&gt;--evidence&lt;/code&gt; and project under legacy &lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt; rules.&lt;/li&gt;
&lt;li&gt;Existing SaaS dashboards see no change for &lt;code dir=&quot;auto&quot;&gt;task_execution&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;mission_step&lt;/code&gt; traffic.&lt;/li&gt;
&lt;li&gt;New standalone dispatch events now appear in the SaaS timeline as minimal entries without body - this is a deliberate behaviour change documented in the SaaS Read-Model Policy table.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-phase-4-trail-follow-on&quot;&gt;Added (Phase 4 trail follow-on)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;docs/trail-model.md&lt;/code&gt;: Formal operator documentation for the Phase 4 trail contract,
mode-of-work taxonomy, tier promotion rules, SaaS projection policy, intake positioning,
and explain deferral (WP04).&lt;/li&gt;
&lt;li&gt;“Governance context injection” section in &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty/SKILL.md&lt;/code&gt; 
for Codex/Vibe hosts, enabling Tier 1 trail recording without host-side SaaS auth (WP03).&lt;/li&gt;
&lt;li&gt;“Standalone invocations (outside missions)” section in
&lt;code dir=&quot;auto&quot;&gt;src/doctrine/skills/spec-kitty-runtime-next/SKILL.md&lt;/code&gt; for Claude Code and gstack hosts,
covering when to open an invocation record outside the mission workflow (WP04).&lt;/li&gt;
&lt;li&gt;End-to-end invocation integration tests in
&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/invocation/test_invocation_e2e.py&lt;/code&gt; covering Tier 1 JSONL write,
complete-event append, local-only list read, and sync-gate suppression (WP05).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-31&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;propagator.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;_propagate_one&lt;/code&gt;): Invocation events are now suppressed when
&lt;code dir=&quot;auto&quot;&gt;effective_sync_enabled = False&lt;/code&gt;, even when the user is authenticated. Previously,
sync-disabled checkouts could still emit SaaS events if a WebSocket client was
connected (WP01).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;executor.complete_invocation&lt;/code&gt; now calls &lt;code dir=&quot;auto&quot;&gt;promote_to_evidence()&lt;/code&gt; when the
&lt;code dir=&quot;auto&quot;&gt;--evidence&lt;/code&gt; flag is supplied, enabling correct Tier 2 artifact promotion (WP03).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-27&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Issue #496: Priority-surface slice complete in 3.2.x (Claude Code via
&lt;code dir=&quot;auto&quot;&gt;spec-kitty-runtime-next&lt;/code&gt; doctrine skill, Codex CLI via SKILL.md governance context
injection). Remaining 9 surfaces tracked in #496 for a follow-on patch or Phase 5.&lt;/li&gt;
&lt;li&gt;Issue #534: &lt;code dir=&quot;auto&quot;&gt;spec-kitty explain&lt;/code&gt; explicitly deferred to Phase 5 (requires DRG
glossary addressability, issue #499). A partial implementation without glossary
citations would be misleading.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a4---2026-04-21&quot;&gt;[3.2.0a4] - 2026-04-21&lt;/h2&gt;
&lt;h3 id=&quot;added-20&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mutation-aware test suites&lt;/strong&gt; - kill-the-survivor passes for &lt;code dir=&quot;auto&quot;&gt;doctrine.resolver&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine.agent_profiles&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine.missions&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctrine.shared&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;specify_cli.compat.registry&lt;/code&gt;. Achieves 75–85 % kill rates per module; residuals documented as trampoline-equivalent, unloadable, or functionally equivalent in &lt;code dir=&quot;auto&quot;&gt;docs/development/mutation-testing-findings.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;_OPTIONAL_KEYS&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_ALL_KNOWN_KEYS&lt;/code&gt; constants in &lt;code dir=&quot;auto&quot;&gt;specify_cli.compat.registry._validate_entry&lt;/code&gt; - unknown YAML keys now raise &lt;code dir=&quot;auto&quot;&gt;RegistrySchemaError&lt;/code&gt; before &lt;code dir=&quot;auto&quot;&gt;ShimEntry(**entry)&lt;/code&gt; can raise &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;model_dump(mode=&quot;json&quot;)&lt;/code&gt; on WP frontmatter serialization in &lt;code dir=&quot;auto&quot;&gt;finalize_tasks&lt;/code&gt; - prevents &lt;code dir=&quot;auto&quot;&gt;Path&lt;/code&gt; objects from reaching YAML serialization.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-21&quot;&gt;Added&lt;/h3&gt;
&lt;h2 id=&quot;320a3---2026-04-21&quot;&gt;[3.2.0a3] - 2026-04-21&lt;/h2&gt;
&lt;h3 id=&quot;fixed-32&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Release publish no longer hard-fails when the private &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_SAAS_READ_TOKEN&lt;/code&gt; secret is absent. The pipeline still enforces runtime drift and exact wheel installability, and it runs the SaaS consumer-contract check whenever the private compatibility reference can actually be fetched.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a2---2026-04-21&quot;&gt;[3.2.0a2] - 2026-04-21&lt;/h2&gt;
&lt;h3 id=&quot;changed-28&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-runtime&lt;/code&gt; is now pinned to &lt;code dir=&quot;auto&quot;&gt;0.4.4&lt;/code&gt;, matching the corrected published runtime line rather than the broken &lt;code dir=&quot;auto&quot;&gt;0.4.3&lt;/code&gt; metadata.&lt;/li&gt;
&lt;li&gt;Release readiness and tag-time publish pipelines now verify shared-package drift, candidate-wheel installability with plain &lt;code dir=&quot;auto&quot;&gt;pip&lt;/code&gt;, and candidate compatibility against the SaaS consumer contract before publish.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-4&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Temporary &lt;code dir=&quot;auto&quot;&gt;tool.uv.override-dependencies&lt;/code&gt; masking for &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;. Release validation now requires the published runtime metadata to resolve cleanly without local overrides.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;320a1---2026-04-20&quot;&gt;[3.2.0a1] - 2026-04-20&lt;/h2&gt;
&lt;h3 id=&quot;added-22&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mutation testing&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;mutmut&lt;/code&gt; 3.5.0 added to &lt;code dir=&quot;auto&quot;&gt;[project.optional-dependencies.test]&lt;/code&gt; and configured in &lt;code dir=&quot;auto&quot;&gt;[tool.mutmut]&lt;/code&gt; as a &lt;strong&gt;local-only&lt;/strong&gt; quality gate. Includes a curated doctrine set: &lt;code dir=&quot;auto&quot;&gt;tactic:mutation-testing-workflow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;styleguide:mutation-aware-test-design&lt;/code&gt;, and language-specific toolguides for Python (&lt;code dir=&quot;auto&quot;&gt;mutmut&lt;/code&gt;) and TypeScript (&lt;code dir=&quot;auto&quot;&gt;stryker&lt;/code&gt;), all anchored to &lt;code dir=&quot;auto&quot;&gt;DIRECTIVE_034&lt;/code&gt; in the DRG graph. ADR &lt;code dir=&quot;auto&quot;&gt;2026-04-20-1-mutation-testing-as-local-only-quality-gate.md&lt;/code&gt; records the decision, the sandbox constraints, and the two-marker exclusion taxonomy.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;non_sandbox&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;flaky&lt;/code&gt; pytest markers&lt;/strong&gt; - registered in &lt;code dir=&quot;auto&quot;&gt;pytest.ini&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;pyproject.toml[tool.pytest.ini_options].markers&lt;/code&gt;. Per-file &lt;code dir=&quot;auto&quot;&gt;--ignore=&lt;/code&gt; entries for sandbox-incompatible tests have been migrated to module-level &lt;code dir=&quot;auto&quot;&gt;pytestmark&lt;/code&gt; declarations; &lt;code dir=&quot;auto&quot;&gt;[tool.mutmut].pytest_add_cli_args&lt;/code&gt; now deselects via &lt;code dir=&quot;auto&quot;&gt;-m &quot;not non_sandbox and not flaky ...&quot;&lt;/code&gt;. Directory-level ignores remain only where tests fail during pytest &lt;em&gt;collection&lt;/em&gt; (import errors that markers cannot intercept). 1 test is currently marked &lt;code dir=&quot;auto&quot;&gt;flaky&lt;/code&gt; as debt to be root-caused.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;docs/how-to/run-mutation-tests.md&lt;/code&gt;&lt;/strong&gt; - Contributor how-to covering local &lt;code dir=&quot;auto&quot;&gt;mutmut run&lt;/code&gt; invocation, the kill-the-survivor workflow, equivalent-mutant suppression, and the &lt;code dir=&quot;auto&quot;&gt;non_sandbox&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;flaky&lt;/code&gt; marker taxonomy.&lt;/li&gt;
&lt;li&gt;Charter synthesizer now has a real harness-owned operator path: the new generated-artifact adapter reads agent-authored YAML from &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/generated/&lt;/code&gt; and promotes validated doctrine into the live &lt;code dir=&quot;auto&quot;&gt;.kittify/doctrine/&lt;/code&gt; tree.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter resynthesize --list-topics&lt;/code&gt; now lists valid project-artifact selectors, DRG URNs, and interview-section selectors, including hyphenated aliases for section names.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter status --provenance&lt;/code&gt; now reports synthesis generation state, evidence summary, manifest health, and per-artifact provenance visibility alongside the older charter sync surface.&lt;/li&gt;
&lt;li&gt;ADR &lt;code dir=&quot;auto&quot;&gt;2026-04-19-6-harness-owned-generated-artifact-charter-handoff.md&lt;/code&gt; now records the host-side charter handoff contract: exact file layout, identity rules, and CLI sequence.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;architecture/2.x/06_migration_and_shim_rules.md&lt;/code&gt;&lt;/strong&gt; - Authoritative compatibility shim lifecycle
rulebook covering 4 rule families: schema/version gating, bundle/runtime migration authoring contract,
shim lifecycle (with copy-paste template), and removal plans/registry contract. Required reading for
all future extraction missions (#615).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;architecture/2.x/shim-registry.yaml&lt;/code&gt;&lt;/strong&gt; - Machine-readable registry of all known compatibility
shims. Starts empty (zero-shim baseline confirmed at mission-615 start). Future shims must be
registered here before merging. Validated by &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor shim-registry&lt;/code&gt; (#615).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor shim-registry&lt;/code&gt;&lt;/strong&gt; - New CI enforcement subcommand that classifies each
registered shim as &lt;code dir=&quot;auto&quot;&gt;pending&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;overdue&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;grandfathered&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;removed&lt;/code&gt;. Exits 1 when any shim
is overdue; exits 2 on configuration error. Supports &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; for machine-readable CI output (#615).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-29&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter synthesize&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty charter resynthesize&lt;/code&gt; now default to the generated-artifact adapter. &lt;code dir=&quot;auto&quot;&gt;--adapter fixture&lt;/code&gt; remains available only for deterministic offline regression runs.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter synthesize --dry-run&lt;/code&gt; is now a real stage-and-validate pass: it writes the staged artifact set, runs project DRG validation and neutrality gating, and only skips the final promote step.&lt;/li&gt;
&lt;li&gt;Shared contract-library pins now align with the current released pair consumed across the CLI and SaaS surfaces: &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events==3.2.0&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty-tracker==0.4.2&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Release pipeline now generates and attaches a CycloneDX SBOM (&lt;code dir=&quot;auto&quot;&gt;sbom.cdx.json&lt;/code&gt;) to every GitHub Release. The SBOM is an environment-snapshot of the fully resolved dependency tree at build time, making it straightforward for enterprise users to ingest the inventory into tools like Dependency-Track for continuous CVE monitoring without rescanning the package themselves.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-33&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Directive provenance now records canonical URNs (&lt;code dir=&quot;auto&quot;&gt;directive:PROJECT_&amp;#x3C;NNN&gt;&lt;/code&gt;) instead of slug-based placeholders, which restores correct directive filenames, provenance reload, and &lt;code dir=&quot;auto&quot;&gt;directive:PROJECT_&amp;#x3C;NNN&gt;&lt;/code&gt; resynthesis.&lt;/li&gt;
&lt;li&gt;Bounded resynthesis now preserves evidence inputs end-to-end, so regenerated provenance entries keep the correct &lt;code dir=&quot;auto&quot;&gt;evidence_bundle_hash&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;corpus_snapshot_id&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Generated-artifact synthesis errors now point to the exact expected file path and exact expected artifact id, which makes harness handoff mistakes easier to diagnose.&lt;/li&gt;
&lt;li&gt;Charter neutrality lint now scans mission &lt;code dir=&quot;auto&quot;&gt;templates/&lt;/code&gt; directories in addition to &lt;code dir=&quot;auto&quot;&gt;command-templates/&lt;/code&gt;, so banned terms in generic mission prompt files are caught by the default repo scan (#653 tripwire).&lt;/li&gt;
&lt;li&gt;Bump &lt;code dir=&quot;auto&quot;&gt;requests&lt;/code&gt; floor to &lt;code dir=&quot;auto&quot;&gt;&gt;=2.33.0&lt;/code&gt; (CVE-2026-25645).&lt;/li&gt;
&lt;li&gt;Bump &lt;code dir=&quot;auto&quot;&gt;pytest&lt;/code&gt; floor to &lt;code dir=&quot;auto&quot;&gt;&gt;=9.0.3&lt;/code&gt; (CVE-2025-71176).&lt;/li&gt;
&lt;li&gt;Pin &lt;code dir=&quot;auto&quot;&gt;pygments&gt;=2.20.0&lt;/code&gt; explicitly to resolve CVE-2026-4539 in the transitive dependency pulled in via &lt;code dir=&quot;auto&quot;&gt;rich&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;auth refresh&lt;/code&gt; now treats &lt;code dir=&quot;auto&quot;&gt;HTTP 401&lt;/code&gt; responses with &lt;code dir=&quot;auto&quot;&gt;invalid_grant&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;session_invalid&lt;/code&gt; error codes identically to &lt;code dir=&quot;auto&quot;&gt;HTTP 400&lt;/code&gt;, and clears the locally stored session on server-side refresh rejection so &lt;code dir=&quot;auto&quot;&gt;auth status&lt;/code&gt; no longer reports stale credentials as authenticated.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-5&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;specify_cli.charter&lt;/code&gt; compatibility shim&lt;/strong&gt; - The re-export shim at &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/charter/&lt;/code&gt; has been
removed. External code importing &lt;code dir=&quot;auto&quot;&gt;specify_cli.charter.*&lt;/code&gt; must migrate to the canonical package:
&lt;code dir=&quot;auto&quot;&gt;from charter import &amp;#x3C;name&gt;&lt;/code&gt;. See
&lt;a href=&quot;/architecture/05_ownership_map/&quot;&gt;docs/architecture/05_ownership_map.md&lt;/a&gt; for the full
charter slice entry and the reference exemplar pattern. Closes #611.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;318---2026-04-29&quot;&gt;[3.1.8] - 2026-04-29&lt;/h2&gt;
&lt;h3 id=&quot;fixed-34&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Dashboard feature polling now tolerates &lt;code dir=&quot;auto&quot;&gt;/api/features&lt;/code&gt; error responses and
malformed payloads without crashing on an undefined &lt;code dir=&quot;auto&quot;&gt;features&lt;/code&gt; array, so the
UI no longer gets stuck loading when feature scanning fails.&lt;/li&gt;
&lt;li&gt;OpenCode global command installation now targets OpenCode’s config command
directory, honoring &lt;code dir=&quot;auto&quot;&gt;OPENCODE_CONFIG_DIR&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;XDG_CONFIG_HOME&lt;/code&gt; before
falling back to &lt;code dir=&quot;auto&quot;&gt;~/.config/opencode/commands&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;317---2026-04-28&quot;&gt;[3.1.7] - 2026-04-28&lt;/h2&gt;
&lt;h3 id=&quot;fixed-35&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Compact charter context now preserves charter section anchors, directive IDs,
and tactic IDs so follow-on agent prompts keep project charter rules in LLM
context after bootstrap load.&lt;/li&gt;
&lt;li&gt;Review claims now enter the canonical &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; lane while still
recognizing legacy review-claim events, avoiding review-loop false blocks.&lt;/li&gt;
&lt;li&gt;Merge completion now keeps post-merge status transitions stable and avoids
duplicate done/approved emissions.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty intake&lt;/code&gt; now caps oversized plan files, ignores out-of-repo and
symlinked auto-detected plans, and writes mission brief/provenance files
atomically.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;auth refresh&lt;/code&gt; now treats &lt;code dir=&quot;auto&quot;&gt;HTTP 401&lt;/code&gt; responses with &lt;code dir=&quot;auto&quot;&gt;invalid_grant&lt;/code&gt; or
&lt;code dir=&quot;auto&quot;&gt;session_invalid&lt;/code&gt; error codes like &lt;code dir=&quot;auto&quot;&gt;HTTP 400&lt;/code&gt;, and clears locally stored
sessions after server-side refresh rejection.&lt;/li&gt;
&lt;li&gt;Local dashboard mission selectors now sort by mission recency instead of
lexical slug order.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;agent config list/status/add/sync/remove&lt;/code&gt; now respects global command roots
for slash-command agents and avoids recreating retired project-local command
directories.&lt;/li&gt;
&lt;li&gt;Status event readers now ignore non-lane mission events in
&lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; while still failing loudly for malformed lane events.&lt;/li&gt;
&lt;li&gt;Sync shutdown diagnostics are deduplicated within a process and suppressed
after successful JSON mission creation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-30&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty-tracker&lt;/code&gt; is pinned to &lt;code dir=&quot;auto&quot;&gt;0.4.3&lt;/code&gt; for the latest tracker-side
stability fixes.&lt;/li&gt;
&lt;li&gt;The local &lt;code dir=&quot;auto&quot;&gt;.python-version&lt;/code&gt; pin now uses &lt;code dir=&quot;auto&quot;&gt;3.13&lt;/code&gt; instead of a patch-specific
interpreter version.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;316---2026-04-20&quot;&gt;[3.1.6] - 2026-04-20&lt;/h2&gt;
&lt;h3 id=&quot;fixed-36&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement&lt;/code&gt; now exposes and forwards
&lt;code dir=&quot;auto&quot;&gt;--acknowledge-not-bulk-edit&lt;/code&gt; to the underlying workspace-allocation command,
allowing non-bulk-edit missions to suppress false-positive bulk-edit inference
warnings during workspace creation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;docs&quot;&gt;Docs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Spec Kitty’s internal maintainer charter now records the ownership boundary
for user-authored custom commands, custom skills, and project overrides, with
an explicit proof trail showing that package-owned mutation flows must preserve
files whose ownership is not proven by managed-path or manifest data.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;315---2026-04-16&quot;&gt;[3.1.5] - 2026-04-16&lt;/h2&gt;
&lt;h3 id=&quot;changed-31&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Keep &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; on the stable &lt;code dir=&quot;auto&quot;&gt;3.x&lt;/code&gt; release line. Release docs, install guidance,
and README messaging now point new users at &lt;code dir=&quot;auto&quot;&gt;3.1.x&lt;/code&gt; on GitHub Releases and PyPI,
while keeping &lt;code dir=&quot;auto&quot;&gt;1.x-maintenance&lt;/code&gt; explicitly maintenance-only.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-37&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Make &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; auto-commit safely through the charter rename migration.
The &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; backstop now disables rename collapsing during its staged-path
probe, and upgrade auto-commit expands changed directories into concrete paths
before validating the staging area. This closes the false-positive abort reported
in &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/643&quot;&gt;#643&lt;/a&gt;.&lt;/li&gt;
&lt;li&gt;Remove pytest/junit prompt bias from charter defaults, plan templates, and doctrine
guidance. Packaged defaults now start from neutral selections, language inference
flows through explicit repo signals, and language-scoped doctrine artifacts remain
available when no active language filter is provided.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;docs-1&quot;&gt;Docs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Align README and user-facing release docs around swim-lane terminology and the
&lt;code dir=&quot;auto&quot;&gt;3.1.x&lt;/code&gt; stable release line.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;314---2026-04-15&quot;&gt;[3.1.4] - 2026-04-15&lt;/h2&gt;
&lt;h3 id=&quot;fixed-38&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Make &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt; stop instructing agents to update imaginary
agent-specific context files or hunt for non-existent &lt;code dir=&quot;auto&quot;&gt;agent context update&lt;/code&gt;
commands. Planning now stays focused on the actual mission artifacts it owns.&lt;/li&gt;
&lt;li&gt;Clarify &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; mission-handle timing and non-blocking charter
behavior so creation-time flows do not assume a mission already exists or stop
on missing charter state.&lt;/li&gt;
&lt;li&gt;Tighten generated &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.review&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.merge&lt;/code&gt; wrappers so they use the canonical &lt;code dir=&quot;auto&quot;&gt;--mission &amp;#x3C;handle&gt;&lt;/code&gt;
language and explicitly avoid redundant context rediscovery, including
separate charter loads.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;313---2026-04-15&quot;&gt;[3.1.3] - 2026-04-15&lt;/h2&gt;
&lt;h3 id=&quot;fixed-39&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Make &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.charter&lt;/code&gt; use an LLM-led interview by default, with better
repo-scan guidance for greenfield/bootstrap repos, explicit doctrine-gap
handling, natural-language questioning, depth scaling, and commit-after-generate
behavior.&lt;/li&gt;
&lt;li&gt;Preserve explicit empty &lt;code dir=&quot;auto&quot;&gt;selected_paradigms&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;selected_directives&lt;/code&gt;, and
&lt;code dir=&quot;auto&quot;&gt;available_tools&lt;/code&gt; during charter compilation instead of broadening them to
packaged defaults.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;docs-2&quot;&gt;Docs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Add ADR recording that explicit empty charter selections must remain empty and
must not silently expand to shipped defaults.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;312---2026-04-15&quot;&gt;[3.1.2] - 2026-04-15&lt;/h2&gt;
&lt;h3 id=&quot;fixed---ci-recovery--release-readiness&quot;&gt;Fixed - CI recovery &amp;#x26; release readiness&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;release-readiness&lt;/code&gt; workflow now filters &lt;code dir=&quot;auto&quot;&gt;windows_ci&lt;/code&gt; tests&lt;/strong&gt; on the Linux runner. The job was running the full suite with no marker filter, failing 10 Windows-only tests (auth file-fallback, kernel paths, sync daemon paths, tracker credentials, migrate messaging, keyring packaging, lock contention, Windows home path). Those tests continue to run on the native &lt;code dir=&quot;auto&quot;&gt;ci-windows.yml&lt;/code&gt; job.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Kiro agent registration completed&lt;/strong&gt;: added &lt;code dir=&quot;auto&quot;&gt;.kiro/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;gitignore_manager.AGENT_DIRECTORIES&lt;/code&gt;, regenerated 11 canonical command baselines under &lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/regression/_twelve_agent_baseline/kiro/&lt;/code&gt;, and updated the four count constants that had drifted after PR #626 (13 slash-command agents, 15 &lt;code dir=&quot;auto&quot;&gt;AGENT_DIRECTORIES&lt;/code&gt; entries).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Auth test fixtures aligned with the hardened HTTP transport&lt;/strong&gt; introduced in &lt;code dir=&quot;auto&quot;&gt;Harden SaaS auth and restore build sync emission&lt;/code&gt;. Tests for &lt;code dir=&quot;auto&quot;&gt;AuthorizationCodeFlow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;TokenRefreshFlow&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;WebSocketTokenProvisioner&lt;/code&gt;, and the browser-login/refresh-transport integration paths now patch &lt;code dir=&quot;auto&quot;&gt;PublicHttpClient&lt;/code&gt; in each flow module’s own namespace (matching the production call graph) instead of raw &lt;code dir=&quot;auto&quot;&gt;httpx.AsyncClient&lt;/code&gt;. Network-error paths raise &lt;code dir=&quot;auto&quot;&gt;NetworkError&lt;/code&gt; from the client mock rather than &lt;code dir=&quot;auto&quot;&gt;httpx.ConnectError&lt;/code&gt; to match the new &lt;code dir=&quot;auto&quot;&gt;except NetworkError&lt;/code&gt; contract.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ResolutionTier&lt;/code&gt; unified across &lt;code dir=&quot;auto&quot;&gt;doctrine.resolver&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;specify_cli.runtime.resolver&lt;/code&gt;&lt;/strong&gt;. &lt;code dir=&quot;auto&quot;&gt;specify_cli.runtime.resolver&lt;/code&gt; is now a thin re-export shim, as its own docstring had claimed. Tests assert tier equivalence via &lt;code dir=&quot;auto&quot;&gt;.name&lt;/code&gt; to stay robust against &lt;code dir=&quot;auto&quot;&gt;pytestarch&lt;/code&gt;’s filesystem-walk loader, which can load the same source file under alternate module names during &lt;code dir=&quot;auto&quot;&gt;pytest --import-mode=importlib&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Post-&lt;code dir=&quot;auto&quot;&gt;unified-charter-bundle-chokepoint&lt;/code&gt; test fixture hardening&lt;/strong&gt;: three pre-existing tests (&lt;code dir=&quot;auto&quot;&gt;test_local_support_declarations_end_to_end&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_template_prompt_bootstrap_context_first_load&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_all_pass_with_healthy_setup&lt;/code&gt;) now &lt;code dir=&quot;auto&quot;&gt;git init&lt;/code&gt; their tmp directories to satisfy the new &lt;code dir=&quot;auto&quot;&gt;resolve_canonical_repo_root&lt;/code&gt; precondition that calls &lt;code dir=&quot;auto&quot;&gt;git rev-parse --git-common-dir&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Codex / Vibe agent skills migration test alignment&lt;/strong&gt;: five tests that pre-dated mission 083 were updated to assert the new &lt;code dir=&quot;auto&quot;&gt;.agents/skills/spec-kitty.&amp;#x3C;cmd&gt;/SKILL.md&lt;/code&gt; layout rather than the retired &lt;code dir=&quot;auto&quot;&gt;.codex/prompts/&lt;/code&gt; layout. Invariants preserved (direct &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action&lt;/code&gt; CLI calls, per-agent argument handling, agent assets generation); only the probe path changed to match the post-083 architecture.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Contract handoff fixture&lt;/strong&gt; updated to include &lt;code dir=&quot;auto&quot;&gt;BuildRegistered&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;BuildHeartbeat&lt;/code&gt; event types added on the emitter side by the SaaS-auth hardening.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Miscellaneous tails&lt;/strong&gt;: redacted a dev-machine path literal in an architecture review doc (caught by &lt;code dir=&quot;auto&quot;&gt;test_command_template_cleanliness&lt;/code&gt;); fixed &lt;code dir=&quot;auto&quot;&gt;test_rewrite_shims.py::test_result_counts&lt;/code&gt; to use two slash-command agents since codex is no longer one; marked &lt;code dir=&quot;auto&quot;&gt;test_home_unit.py::TestGetKittifyHomeWindows::test_windows_default_path&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;windows_ci&lt;/code&gt; since DRIFT-3 of the Windows Compatibility Hardening mission made &lt;code dir=&quot;auto&quot;&gt;get_kittify_home()&lt;/code&gt; delegate to &lt;code dir=&quot;auto&quot;&gt;specify_cli.paths.get_runtime_root().base&lt;/code&gt;, which the monkeypatch-based simulation no longer drives reliably on non-Windows runners.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Kiro regenerated baselines&lt;/strong&gt; for all 12 canonical commands, closing the &lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/regression/test_twelve_agent_parity.py&lt;/code&gt; baseline-missing cluster introduced by PR #626.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-23&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Unified charter bundle manifest v1.0.0&lt;/strong&gt; at &lt;code dir=&quot;auto&quot;&gt;src/charter/bundle.py&lt;/code&gt; declaring the three &lt;code dir=&quot;auto&quot;&gt;sync()&lt;/code&gt;-produced derivatives (&lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directives.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt;) as the authoritative bundle contract. &lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;context-state.json&lt;/code&gt; are explicitly out of v1.0.0 scope; they are produced by other pipelines.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Canonical-root resolver&lt;/strong&gt; at &lt;code dir=&quot;auto&quot;&gt;src/charter/resolution.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;resolve_canonical_repo_root()&lt;/code&gt;). Readers running inside a git worktree now transparently observe the main-checkout charter bundle without per-worktree materialisation. Closes Priivacy-ai/spec-kitty#339.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty charter bundle validate [--json]&lt;/code&gt;&lt;/strong&gt; CLI surface for operator and CI bundle-health checks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration &lt;code dir=&quot;auto&quot;&gt;m_3_2_3_unified_bundle&lt;/code&gt;&lt;/strong&gt; advances 3.x projects to the unified bundle layout. On a populated project it validates the bundle against the v1.0.0 manifest, invokes &lt;code dir=&quot;auto&quot;&gt;ensure_charter_bundle_fresh()&lt;/code&gt; to regenerate any missing derivatives, and emits a structured JSON report (see &lt;code dir=&quot;auto&quot;&gt;kitty-specs/unified-charter-bundle-chokepoint-01KP5Q2G/contracts/migration-report.schema.json&lt;/code&gt;). Idempotent - the second apply against an already-upgraded project is a clean no-op. Refs Priivacy-ai/spec-kitty#464, #479.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-32&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;SyncResult&lt;/code&gt; extended with &lt;code dir=&quot;auto&quot;&gt;canonical_root: Path&lt;/code&gt;&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;files_written&lt;/code&gt; remains a list of file names relative to &lt;code dir=&quot;auto&quot;&gt;canonical_root / .kittify/charter/&lt;/code&gt;. Existing readers were rewired in lockstep; no compatibility shim.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;ensure_charter_bundle_fresh()&lt;/code&gt; is now the sole chokepoint&lt;/strong&gt; for readers of &lt;code dir=&quot;auto&quot;&gt;governance.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;directives.yaml&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;metadata.yaml&lt;/code&gt;. Direct reads of those files are forbidden and are enforced by an AST-walk coverage test (&lt;code dir=&quot;auto&quot;&gt;tests/charter/test_chokepoint_coverage.py&lt;/code&gt;). Refs Priivacy-ai/spec-kitty#461, #464.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;unchanged-explicitly&quot;&gt;Unchanged (explicitly)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/memory/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/AGENTS.md&lt;/code&gt; symlinks in worktrees&lt;/strong&gt; remain as-is - they provide project-memory and agent-instructions sharing, documented-intentional per &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/templates/AGENTS.md:168-179&lt;/code&gt;. They are NOT part of the charter bundle; the canonical-root resolver fixes the worktree charter-visibility story without touching &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/worktree.py&lt;/code&gt; (C-011).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Files under &lt;code dir=&quot;auto&quot;&gt;.kittify/charter/&lt;/code&gt; that are not v1.0.0 manifest files&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;references.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;context-state.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;interview/answers.yaml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;library/*.md&lt;/code&gt;) are unchanged. The migration lists them under &lt;code dir=&quot;auto&quot;&gt;bundle_validation.unexpected&lt;/code&gt; for operator visibility but does not delete, move, or rewrite them (C-012).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Project &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; is not reconciled&lt;/strong&gt; by the migration. The v1.0.0 manifest’s required entries already match the repository &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; verbatim; the migration performs no read or write against &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; (D-12).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;refs&quot;&gt;Refs&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;EPIC: Priivacy-ai/spec-kitty#461 (Charter as Synthesis &amp;#x26; doctrine reference graph).&lt;/li&gt;
&lt;li&gt;Phase 2 tracking: Priivacy-ai/spec-kitty#464.&lt;/li&gt;
&lt;li&gt;Closes on merge: Priivacy-ai/spec-kitty#339, #451.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-40&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission merge&lt;/code&gt; no longer silently loses content when the repository carries legacy sparse-checkout state&lt;/strong&gt; - the stash/merge/stash-pop cascade used by the merge driver previously recorded phantom deletions for paths filtered out by a sparse-checkout pattern, and the subsequent housekeeping commit silently reverted content the preceding merge had introduced. Merge and &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt; now run a sparse-checkout preflight and fail closed unless the operator passes &lt;code dir=&quot;auto&quot;&gt;--allow-sparse-checkout&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; now aborts commits whose staging area contains paths outside the intended scope, and &lt;code dir=&quot;auto&quot;&gt;mission merge&lt;/code&gt; performs a post-merge refresh and invariant check before leaving the integration branch. Closes Priivacy-ai/spec-kitty#588.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;move-task --to approved&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--to planned&lt;/code&gt; on a lane-worktree review no longer require &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; when the only untracked content is &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/&lt;/code&gt;&lt;/strong&gt; - the review-lock uncommitted-changes guard now treats the execution lane’s own &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/&lt;/code&gt; scratch directory as expected content rather than an unexplained untracked path, so operators stop being trained to pass &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; reflexively. Closes Priivacy-ai/spec-kitty#589.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Retry guidance emitted by the uncommitted-changes guard now names the actual target lane&lt;/strong&gt; rather than hardcoded &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;, so operators see the transition they were attempting instead of a misleading default.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-24&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor sparse-checkout --fix&lt;/code&gt;&lt;/strong&gt; - detection and one-command migration for repositories upgraded from pre-3.0 spec-kitty that still carry &lt;code dir=&quot;auto&quot;&gt;core.sparseCheckout=true&lt;/code&gt; and a &lt;code dir=&quot;auto&quot;&gt;.git/info/sparse-checkout&lt;/code&gt; pattern file. The fix removes the git-config entry, clears the pattern file, and verifies post-fix state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--allow-sparse-checkout&lt;/code&gt; flag on &lt;code dir=&quot;auto&quot;&gt;mission merge&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent action implement&lt;/code&gt;&lt;/strong&gt; - explicit escape hatch for users with intentional sparse configurations. Use of the flag emits a &lt;code dir=&quot;auto&quot;&gt;WARNING&lt;/code&gt;-level structured log record (&lt;code dir=&quot;auto&quot;&gt;spec_kitty.override.sparse_checkout&lt;/code&gt;) at the CLI layer. Durable cross-repo audit event support is tracked as Priivacy-ai/spec-kitty#617.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commit-time backstop inside &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt;&lt;/strong&gt; - fail-closed check that aborts commits whose staging area contains paths outside the intended scope, independent of the preflight. This is the universal defence that catches sparse-stash-pop phantom-deletion cascades regardless of which command initiated them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Per-worktree &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/&lt;/code&gt; exclude entry&lt;/strong&gt; - every lane worktree now receives a local git exclude entry for &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/&lt;/code&gt; at worktree creation, so lane scratch content stays invisible to the working-tree guard even in worktrees initialised before the fix.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Session-scoped sparse-checkout warning&lt;/strong&gt; at review-lock and task-command entry points - surfaces detected legacy sparse-checkout state once per process before an operator wastes a commit cycle, without blocking.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ADR &lt;code dir=&quot;auto&quot;&gt;2026-04-14-1-sparse-checkout-defense-in-depth&lt;/code&gt;&lt;/strong&gt; - documents the four-layer hybrid defence (merge/implement preflight, &lt;code dir=&quot;auto&quot;&gt;safe_commit&lt;/code&gt; backstop, session warning, &lt;code dir=&quot;auto&quot;&gt;doctor --fix&lt;/code&gt;) and the alternatives considered.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;recovery-for-users-already-affected&quot;&gt;Recovery for users already affected&lt;/h3&gt;
&lt;p&gt;If a prior &lt;code dir=&quot;auto&quot;&gt;mission merge&lt;/code&gt; landed on your target branch with a silent content
reversion (symptoms: a follow-up &lt;code dir=&quot;auto&quot;&gt;chore: record done transitions&lt;/code&gt; commit that
deleted content merged in the preceding commit), restore the content from the
merge commit that introduced it:&lt;/p&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;# Identify the merge commit&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;git&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;log&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--merges&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--oneline&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--&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;&amp;#x3C;affected-file&gt;&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;# Restore content from that merge&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;git&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;checkout&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;&amp;#x3C;merge-sha&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--&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;&amp;#x3C;affected-file&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; [...]&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;# Commit the restoration&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;git&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;add&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;&amp;#x3C;affected-file&gt;&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; [...]&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;git&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;commit&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;-m&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;fix: restore content reverted by phantom-deletion bug&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Then run the migration to prevent recurrence:&lt;/p&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:#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;doctor&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;sparse-checkout&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;--fix&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;Root-cause diagnostic trail: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/588#issuecomment-4242179946&quot;&gt;Priivacy-ai/spec-kitty#588 (comment)&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;312a4---2026-04-14&quot;&gt;[3.1.2a4] - 2026-04-14&lt;/h2&gt;
&lt;h3 id=&quot;added-25&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Kiro CLI as first-class agent&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty init --ai kiro&lt;/code&gt; registers the Kiro CLI (Amazon Q Developer CLI’s rebrand) with its own &lt;code dir=&quot;auto&quot;&gt;.kiro/prompts/&lt;/code&gt; directory and &lt;code dir=&quot;auto&quot;&gt;kiro-cli&lt;/code&gt; binary check. Legacy &lt;code dir=&quot;auto&quot;&gt;--ai q&lt;/code&gt; (→ &lt;code dir=&quot;auto&quot;&gt;.amazonq/prompts/&lt;/code&gt;) remains supported for backwards compatibility. README and &lt;code dir=&quot;auto&quot;&gt;docs/reference/supported-agents.md&lt;/code&gt; now document the shell-quoting requirement for &lt;code dir=&quot;auto&quot;&gt;$ARGUMENTS&lt;/code&gt; pass-through (see kirodotdev/Kiro#4141). Closes #246.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-41&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;diff-coverage&lt;/code&gt; CI job no longer fails with “no merge base”&lt;/strong&gt; - the base-branch fetch was passing &lt;code dir=&quot;auto&quot;&gt;--depth=1&lt;/code&gt; after &lt;code dir=&quot;auto&quot;&gt;actions/checkout@v6&lt;/code&gt; had already fetched full history, which truncated &lt;code dir=&quot;auto&quot;&gt;origin/&amp;#x3C;base&gt;&lt;/code&gt; back to a single commit and broke &lt;code dir=&quot;auto&quot;&gt;diff-cover&lt;/code&gt;’s merge-base computation. Dropped &lt;code dir=&quot;auto&quot;&gt;--depth=1&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;test_mission_v1_guards_unit.py::test_registry_keys&lt;/code&gt; now matches the guard registry&lt;/strong&gt; - synchronised the &lt;code dir=&quot;auto&quot;&gt;EXPECTED_GUARDS&lt;/code&gt; set with the &lt;code dir=&quot;auto&quot;&gt;occurrence_map_complete&lt;/code&gt; guard added in #616.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;312a3---2026-04-12&quot;&gt;[3.1.2a3] - 2026-04-12&lt;/h2&gt;
&lt;h3 id=&quot;fixed-42&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Merge-time numbering lock and retry safety&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;mission_number&lt;/code&gt; assignment now acquires a file lock before scanning existing prefixes, MergeState uses &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; as its canonical key, and interrupted merges no longer risk duplicate or skipped numbers on retry. Closes #601.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CLI no longer hangs 15–20 min when offline queue is full and session expired&lt;/strong&gt; - the offline queue drain path now respects a bounded timeout instead of blocking indefinitely on expired-session retries. Closes #598, #602.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sonar readiness and parser findings addressed&lt;/strong&gt; - actionable maintenance issues flagged by SonarCloud (code smells, complexity, minor bugs) are resolved. Closes #599, #600.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;312a2---2026-04-11&quot;&gt;[3.1.2a2] - 2026-04-11&lt;/h2&gt;
&lt;h3 id=&quot;added-26&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Hosted readiness control surfaces&lt;/strong&gt; - the CLI now exposes the canonical SaaS rollout/readiness module, a six-state hosted readiness evaluator, and a background-daemon policy/intent model that keeps stealth rollout behavior explicit while making enabled-mode failures actionable.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-33&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Tracker command classification is corrected for first-run flows&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;tracker discover&lt;/code&gt; no longer requires an existing mission binding, &lt;code dir=&quot;auto&quot;&gt;tracker providers&lt;/code&gt; remains available as static output without hosted prerequisites, and hosted/manual-daemon checks are applied according to command intent rather than indiscriminately.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tracker dependency advances to the hardened hosted-discovery release line&lt;/strong&gt; - the CLI now targets &lt;code dir=&quot;auto&quot;&gt;spec-kitty-tracker==0.4.1&lt;/code&gt;, aligning the prerelease with the published runtime validation and canonical discovery contract shipped in the tracker SDK.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-43&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Background-daemon policy no longer blocks local-provider sync flows&lt;/strong&gt; - local tracker providers continue to execute direct sync operations even when hosted SaaS daemon startup is set to manual.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;312a1---2026-04-10&quot;&gt;[3.1.2a1] - 2026-04-10&lt;/h2&gt;
&lt;h3 id=&quot;added-27&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Browser-mediated CLI auth preview&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty auth login&lt;/code&gt; now supports browser-based OAuth with Device Authorization Flow fallback, centralized token management, secure storage, and WebSocket token provisioning against the SaaS contract.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-34&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Human CLI auth now flows through the new auth subsystem&lt;/strong&gt; - HTTP transport, sync runtime, and tracker SaaS callers now refresh through the shared token manager instead of the legacy password/JWT credential path.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-44&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Browser auth CI coverage gaps&lt;/strong&gt; - test dependencies and stale tracker refresh patch targets were corrected so the new auth stack passes the core and integration suites reliably in CI.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;311---2026-04-09&quot;&gt;[3.1.1] - 2026-04-09&lt;/h2&gt;
&lt;h3 id=&quot;added-28&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Semantic status-event merge driver&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**/status.events.jsonl&lt;/code&gt; now uses a Spec Kitty merge driver that unions append-only event logs by &lt;code dir=&quot;auto&quot;&gt;event_id&lt;/code&gt;, rejects conflicting payloads, and fails closed when merged WPs do not reach &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; in the canonical event log.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Forward-safe mission identity&lt;/strong&gt; - newly created missions now mint a ULID &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt; at creation time, persist it to &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, and emit it through mission-created event payloads.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release hygiene guardrail&lt;/strong&gt; - release validation now enforces &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; version sync before a cut can proceed.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-35&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now produces a minimal file scaffold&lt;/strong&gt; - init no longer initializes git, creates bootstrap commits, or seeds &lt;code dir=&quot;auto&quot;&gt;.agents/skills/&lt;/code&gt;. The generated next steps now point users at &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; plus &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action implement/review&lt;/code&gt; as the canonical workflow.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Planning-artifact WPs are first-class lane-owned items&lt;/strong&gt; - the canonical planning lane is now &lt;code dir=&quot;auto&quot;&gt;lane-planning&lt;/code&gt;, and it resolves to the main repository checkout instead of an ad hoc special-case path.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Top-level &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; is de-emphasized&lt;/strong&gt; - onboarding and command docs now treat &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; as internal infrastructure rather than the primary user-facing flow.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-45&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Merge conflict recovery for &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;&lt;/strong&gt; - append-only status events are no longer silently dropped during merge conflict resolution, and fresh repositories now self-heal the local git merge-driver config when running merge flows. Closes #574.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Planning/query consistency after PR #555&lt;/strong&gt; - mixed planning/code review-context resolution no longer crashes when a dependency resolves to the repo-root workspace, and fresh-run query mode now returns &lt;code dir=&quot;auto&quot;&gt;run_id: null&lt;/code&gt; instead of leaking a deleted temporary run id.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dependency parser trailing-prose bleed&lt;/strong&gt; - the final WP section is now bounded at non-WP &lt;code dir=&quot;auto&quot;&gt;##&lt;/code&gt; headings so trailing prose does not get misread as dependency declarations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Concurrent auth refresh race&lt;/strong&gt; - stale 401 responses during token rotation no longer wipe valid shared credentials from active CLI sessions.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;311a3---2026-04-07&quot;&gt;[3.1.1a3] - 2026-04-07&lt;/h2&gt;
&lt;h3 id=&quot;added-29&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Global slash command installation&lt;/strong&gt; - all 16 spec-kitty slash commands are now installed globally to &lt;code dir=&quot;auto&quot;&gt;~/.&amp;#x3C;agent-dir&gt;/&lt;/code&gt; (e.g. &lt;code dir=&quot;auto&quot;&gt;~/.claude/commands/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;~/.gemini/commands/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;~/.codex/prompts/&lt;/code&gt;, etc.) at every CLI startup, for all 13 supported agents. No &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; or per-project &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; is required for commands to be available. Commands update automatically when the CLI is upgraded.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration &lt;code dir=&quot;auto&quot;&gt;3.1.2_globalize_commands&lt;/code&gt;&lt;/strong&gt; - removes existing per-project &lt;code dir=&quot;auto&quot;&gt;spec-kitty.*&lt;/code&gt; command files from &lt;code dir=&quot;auto&quot;&gt;.claude/commands/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.gemini/commands/&lt;/code&gt;, and equivalent directories in all configured agents. Runs automatically on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ADR &lt;code dir=&quot;auto&quot;&gt;2026-04-07-1-global-slash-command-installation&lt;/code&gt;&lt;/strong&gt; - documents the decision to install commands globally, the full 13-agent table with global roots, and the rationale.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-36&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; no longer writes per-project command files. Commands are managed exclusively by the global startup hook.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;311a2---2026-04-07&quot;&gt;[3.1.1a2] - 2026-04-07&lt;/h2&gt;
&lt;h3 id=&quot;fixed-46&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; / any CLI command no longer dirties the git repo&lt;/strong&gt; - every CLI invocation that touched status was unconditionally rewriting &lt;code dir=&quot;auto&quot;&gt;kitty-specs/*/status.json&lt;/code&gt;, even when nothing had changed, leaving ~60 files modified in &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt;. Root cause: &lt;code dir=&quot;auto&quot;&gt;materialize()&lt;/code&gt; stamped a fresh &lt;code dir=&quot;auto&quot;&gt;datetime.now(UTC)&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;materialized_at&lt;/code&gt; on every call. Fixed in &lt;code dir=&quot;auto&quot;&gt;reducer.py&lt;/code&gt; (3.1.1a1): &lt;code dir=&quot;auto&quot;&gt;materialized_at&lt;/code&gt; is now derived deterministically from the last event’s &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; timestamp (or &lt;code dir=&quot;auto&quot;&gt;&quot;&quot;&lt;/code&gt; for features with no events), and a content-equality guard skips the write when the file is already up to date. Closes #524.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-30&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Migration &lt;code dir=&quot;auto&quot;&gt;3.1.1_normalize_status_json&lt;/code&gt;&lt;/strong&gt; - one-shot upgrade migration that normalises all existing &lt;code dir=&quot;auto&quot;&gt;kitty-specs/*/status.json&lt;/code&gt; files to the new deterministic format. Runs automatically on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; for any project where the committed files still carry old wall-clock timestamps or the legacy &lt;code dir=&quot;auto&quot;&gt;feature_slug&lt;/code&gt; field. After the migration the skip-write guard in &lt;code dir=&quot;auto&quot;&gt;materialize()&lt;/code&gt; keeps all status snapshots stable indefinitely.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-37&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;StatusSnapshot&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ProgressResult&lt;/code&gt; serialisation no longer emits &lt;code dir=&quot;auto&quot;&gt;feature_slug&lt;/code&gt;&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;with_tracked_mission_slug_aliases&lt;/code&gt; previously injected a redundant &lt;code dir=&quot;auto&quot;&gt;feature_slug&lt;/code&gt; alias into every serialised snapshot. Now only &lt;code dir=&quot;auto&quot;&gt;mission_slug&lt;/code&gt; is written. Reading still accepts both keys for backward compat with existing files.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;311a1---2026-04-07&quot;&gt;[3.1.1a1] - 2026-04-07&lt;/h2&gt;
&lt;h3 id=&quot;added-31&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Typed &lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; Pydantic model&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/wp_metadata.py&lt;/code&gt;) - immutable, validated work package metadata with &lt;code dir=&quot;auto&quot;&gt;update()&lt;/code&gt; builder API; replaces all raw &lt;code dir=&quot;auto&quot;&gt;frontmatter.get()&lt;/code&gt; dict access across consumer files. Closes #410.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;Lane&lt;/code&gt; enum state machine&lt;/strong&gt; - valid lane transitions enforced at the type level; all runtime consumers migrated from string comparisons to &lt;code dir=&quot;auto&quot;&gt;Lane&lt;/code&gt; enum values.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Typed dashboard API contracts&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/dashboard/handlers/api.py&lt;/code&gt;) - Pydantic response models replace untyped dicts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;RE2 shim&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/kernel/_safe_re.py&lt;/code&gt;) - &lt;code dir=&quot;auto&quot;&gt;types.ModuleType&lt;/code&gt;-based shim backed by &lt;code dir=&quot;auto&quot;&gt;google-re2&lt;/code&gt;; exposes the full &lt;code dir=&quot;auto&quot;&gt;re&lt;/code&gt; API and mitigates Sonar DOS hotspot findings. &lt;code dir=&quot;auto&quot;&gt;google-re2&gt;=1.1&lt;/code&gt; added as a core runtime dependency.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI status-layer test stages&lt;/strong&gt; - new &lt;code dir=&quot;auto&quot;&gt;fast-tests-status&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;integration-tests-status&lt;/code&gt; jobs run the &lt;code dir=&quot;auto&quot;&gt;tests/status/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/status/&lt;/code&gt; suites in parallel with existing core/doctrine jobs; their coverage outputs feed the &lt;code dir=&quot;auto&quot;&gt;diff-coverage&lt;/code&gt; gate.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;WPMetadata.display_title&lt;/code&gt; property&lt;/strong&gt; - safe fallback for missing or empty WP titles.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-38&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;All &lt;code dir=&quot;auto&quot;&gt;frontmatter.get()&lt;/code&gt; calls outside &lt;code dir=&quot;auto&quot;&gt;frontmatter.py&lt;/code&gt; migrated to typed &lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; access. Migration scripts retain raw dict access annotated &lt;code dir=&quot;auto&quot;&gt;# MIGRATION-ONLY&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;WPMetadata.title&lt;/code&gt; is now optional; WP read errors propagate gracefully via &lt;code dir=&quot;auto&quot;&gt;read_wp_frontmatter()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;OwnershipManifest.from_frontmatter()&lt;/code&gt; accepts &lt;code dir=&quot;auto&quot;&gt;WPMetadata&lt;/code&gt; directly.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;diff-coverage&lt;/code&gt; job wired to consume &lt;code dir=&quot;auto&quot;&gt;coverage-kernel.xml&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;coverage-fast-status.xml&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;coverage-integration-status.xml&lt;/code&gt; in both enforced (critical-path 90%) and advisory (full-diff) steps.&lt;/li&gt;
&lt;li&gt;GitHub Actions upgraded to Node.js 24 compatible versions (&lt;code dir=&quot;auto&quot;&gt;actions/checkout@v6&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;actions/setup-python@v6&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;actions/setup-node@v6&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;actions/upload-artifact@v7&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;actions/download-artifact@v8&lt;/code&gt;) across all workflow files.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-47&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;ValidationError&lt;/code&gt; caught in phase-1 status mirror (&lt;code dir=&quot;auto&quot;&gt;status/emit.py&lt;/code&gt;) - prevents NoneType crashes on malformed WP files.&lt;/li&gt;
&lt;li&gt;Ruff and mypy violations cleaned up in all files touched by the migration.&lt;/li&gt;
&lt;li&gt;Sonar false-positive NOSONAR suppressions added in &lt;code dir=&quot;auto&quot;&gt;arbiter.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;dashboard/handlers/api.py&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;WP03 validation report (mission 068) decision corrected from &lt;code dir=&quot;auto&quot;&gt;close_with_evidence&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;tighten_workflow&lt;/code&gt; to reflect the CI logic additions; &lt;code dir=&quot;auto&quot;&gt;test_tighten_workflow_passes_large_pr_sample&lt;/code&gt; implemented to verify the advisory-only contract.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;310---2026-04-07&quot;&gt;[3.1.0] - 2026-04-07&lt;/h2&gt;
&lt;h3 id=&quot;added-32&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Planning pipeline integrity (mission 069)&lt;/strong&gt; - four structural fixes eliminating fragilities discovered during mission 068:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dirty-git reads fix (WP01)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;materialize()&lt;/code&gt; now derives &lt;code dir=&quot;auto&quot;&gt;materialized_at&lt;/code&gt; from the last event timestamp (deterministic) and skips the write when content is byte-identical. &lt;code dir=&quot;auto&quot;&gt;materialize_if_stale()&lt;/code&gt; returns a read-only &lt;code dir=&quot;auto&quot;&gt;reduce()&lt;/code&gt; call. All read-only commands leave zero modified files in &lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt;. Fixes #524.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Structured WP manifest - &lt;code dir=&quot;auto&quot;&gt;wps.yaml&lt;/code&gt; (WP02, WP03, WP04)&lt;/strong&gt; - new &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/wps_manifest.py&lt;/code&gt; with Pydantic model, YAML loader, and &lt;code dir=&quot;auto&quot;&gt;generate_tasks_md_from_manifest()&lt;/code&gt;. JSON Schema at &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/schemas/wps.schema.json&lt;/code&gt;. When &lt;code dir=&quot;auto&quot;&gt;wps.yaml&lt;/code&gt; is present, &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; derives dependencies exclusively from the manifest; &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; is regenerated as a derived artifact. &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks-outline&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks-packages&lt;/code&gt; templates updated to produce/consume &lt;code dir=&quot;auto&quot;&gt;wps.yaml&lt;/code&gt;. Migration &lt;code dir=&quot;auto&quot;&gt;m_3_2_0_update_planning_templates&lt;/code&gt; propagates changes to existing installations. Fixes #525.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; query mode (WP05)&lt;/strong&gt; - bare &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; (no &lt;code dir=&quot;auto&quot;&gt;--result&lt;/code&gt;) enters query mode: returns current step with &lt;code dir=&quot;auto&quot;&gt;[QUERY - no result provided, state not advanced]&lt;/code&gt; prefix without advancing the state machine. Prevents ghost completions when agents call &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; while disoriented. Fixes #526.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Slug validator digit-prefix support (WP06)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;KEBAB_CASE_PATTERN&lt;/code&gt; updated to accept &lt;code dir=&quot;auto&quot;&gt;NNN-*&lt;/code&gt; slugs following spec-kitty’s own naming convention. Fixes #527.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;310a8---2026-04-07&quot;&gt;[3.1.0a8] - 2026-04-07&lt;/h2&gt;
&lt;h3 id=&quot;added-33&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Post-merge reliability and release hardening (mission 068)&lt;/strong&gt; - 5 work packages closing the workflow-stabilization track:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Stale-assertion analyzer (WP01)&lt;/strong&gt; - new &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/post_merge/&lt;/code&gt; package: stdlib &lt;code dir=&quot;auto&quot;&gt;ast&lt;/code&gt;-based tool that detects test assertions likely invalidated by merged source changes. CLI: &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tests stale-check --base &amp;#x3C;ref&gt; --head &amp;#x3C;ref&gt; [--json]&lt;/code&gt;. Integrated into the merge runner. No new dependencies, no network calls.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Merge strategy + safe-commit + linear-history hint (WP02)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;MergeStrategy&lt;/code&gt; enum (MERGE/SQUASH/REBASE) in new &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/merge/config.py&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;--strategy&lt;/code&gt; CLI flag (resolves: flag → &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; → squash default). &lt;code dir=&quot;auto&quot;&gt;safe_commit()&lt;/code&gt; called after &lt;code dir=&quot;auto&quot;&gt;_mark_wp_merged_done&lt;/code&gt; before worktree removal (FR-019). Linear-history rejection hint guides users past protected-branch push failures. Closes #456.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Diff-coverage policy validation (WP03)&lt;/strong&gt; - validation report confirms the enforce/advisory split already satisfies the policy intent. CI step names tightened to &lt;code dir=&quot;auto&quot;&gt;diff-coverage (critical-path, enforced)&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;diff-coverage (full-diff, advisory)&lt;/code&gt;. Closes #455.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release-prep CLI (WP04)&lt;/strong&gt; - new &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/release/&lt;/code&gt; package: &lt;code dir=&quot;auto&quot;&gt;propose_version()&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;build_changelog_block()&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ReleasePrepPayload&lt;/code&gt;. CLI: &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent release prep --channel {alpha,beta,stable} [--json]&lt;/code&gt;. Zero network calls. Closes #457.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Recovery extension + mission close (WP05)&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;scan_recovery_state()&lt;/code&gt; extended with &lt;code dir=&quot;auto&quot;&gt;consult_status_events=True&lt;/code&gt; to detect merged-and-deleted WPs via event log; new &lt;code dir=&quot;auto&quot;&gt;RecoveryState.ready_to_start_from_target&lt;/code&gt; field. &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; gains &lt;code dir=&quot;auto&quot;&gt;--base &amp;#x3C;ref&gt;&lt;/code&gt; flag for explicit worktree branching. Closes #415.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-48&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;implement --base&lt;/code&gt; Typer pattern&lt;/strong&gt; - changed to Annotated pattern, fixing test isolation failures where direct Python calls received &lt;code dir=&quot;auto&quot;&gt;OptionInfo&lt;/code&gt; objects instead of &lt;code dir=&quot;auto&quot;&gt;None&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt; console capsys isolation&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;_json_safe_output&lt;/code&gt; wrapper now resets &lt;code dir=&quot;auto&quot;&gt;console._file = None&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;finally&lt;/code&gt; to prevent “I/O operation on closed file” when tests run in sequence with pytest capsys&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Replay parity test&lt;/strong&gt; - corrected &lt;code dir=&quot;auto&quot;&gt;reduced.mission_key == &quot;replay-mission&quot;&lt;/code&gt; (was wrong field name and wrong value)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;310a7---2026-04-06&quot;&gt;[3.1.0a7] - 2026-04-06&lt;/h2&gt;
&lt;h3 id=&quot;added-34&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Runtime recovery and audit safety (mission 067)&lt;/strong&gt; — 6 work packages delivering resilience and audit infrastructure:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Merge resume recovery (WP01)&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge --resume&lt;/code&gt; recovers from interrupted merges with persistent state tracking in &lt;code dir=&quot;auto&quot;&gt;.kittify/merge-state.json&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Implementation crash recovery (WP02)&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement --recover&lt;/code&gt; restores execution context after agent crashes, rebuilding worktree state and resuming from last known checkpoint&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stale-claim doctor checks (WP03)&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor&lt;/code&gt; detects orphaned claims, stale locks, and zombie worktrees with structured diagnostic output&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Audit-mode scope relaxation (WP04)&lt;/strong&gt; — ownership validation supports &lt;code dir=&quot;auto&quot;&gt;scope: codebase-wide&lt;/code&gt; for audit/cutover WPs; new &lt;code dir=&quot;auto&quot;&gt;validate_audit_coverage()&lt;/code&gt; warns on uncovered audit targets&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Shim-to-canonical migration (WP05)&lt;/strong&gt; — all &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent shim &amp;#x3C;action&gt;&lt;/code&gt; calls replaced with direct &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action &amp;#x3C;action&gt;&lt;/code&gt; across 48 agent command files&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Finalize-tasks audit wiring (WP06)&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;validate_audit_coverage()&lt;/code&gt; integrated into finalize-tasks ownership validation pipeline as a soft warning check&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-49&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Agent command files&lt;/strong&gt; — regenerated all 48 agent command files to use canonical &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action&lt;/code&gt; instead of deprecated &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent shim&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Post-merge test regressions&lt;/strong&gt; — fixed 4 stale test assertions after mission 067 merge (implement template content, merge resume behavior, —recover flag default)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;310a6---2026-04-06&quot;&gt;[3.1.0a6] - 2026-04-06&lt;/h2&gt;
&lt;h3 id=&quot;added-35&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Review loop stabilization (mission 066)&lt;/strong&gt; - new &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/review/&lt;/code&gt; module with 6 submodules:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;artifacts.py&lt;/code&gt; - persisted review-cycle artifacts at &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;mission&gt;/tasks/&amp;#x3C;WP-slug&gt;/review-cycle-{N}.md&lt;/code&gt; with YAML frontmatter. Replaces ephemeral &lt;code dir=&quot;auto&quot;&gt;.git/spec-kitty/feedback/&lt;/code&gt; storage. Backward-compatible &lt;code dir=&quot;auto&quot;&gt;feedback://&lt;/code&gt; pointer resolution retained (#432, #433).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;fix_prompt.py&lt;/code&gt; - focused fix-mode prompt generation from review-cycle artifacts. Rejected WPs get ~40-line targeted prompts instead of replaying 400-500 line full WP prompts (#430).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;dirty_classifier.py&lt;/code&gt; - dirty-state classification for review handoff. Partitions &lt;code dir=&quot;auto&quot;&gt;git status --porcelain&lt;/code&gt; output into blocking (WP-owned files) vs benign (status artifacts, other WP files, metadata). External reviewers no longer need &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; for unrelated dirtiness (#439).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;baseline.py&lt;/code&gt; - baseline test capture at implement time via &lt;code dir=&quot;auto&quot;&gt;pytest --junitxml&lt;/code&gt; + JUnit XML parsing. Review prompts include “Baseline Context” section distinguishing pre-existing failures from regressions. Configurable &lt;code dir=&quot;auto&quot;&gt;review.test_command&lt;/code&gt; for non-pytest projects (#444).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;lock.py&lt;/code&gt; - concurrent review serialization via &lt;code dir=&quot;auto&quot;&gt;.spec-kitty/review-lock.json&lt;/code&gt;. Stale lock detection via PID check. Opt-in env-var isolation for projects that configure &lt;code dir=&quot;auto&quot;&gt;review.concurrent_isolation&lt;/code&gt; in config.yaml (#440).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;arbiter.py&lt;/code&gt; - structured arbiter checklist with 5 standard rationale categories (pre-existing failure, wrong context, cross-scope, infra/environmental, custom). Override detection on forward &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; from planned after rejection event. Decisions persisted in review-cycle artifact frontmatter (#441).&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;147 new tests&lt;/strong&gt; across the review module (avg 93% coverage, range 91-99%)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Implement-review skill update&lt;/strong&gt; - parallel sprint pattern, merge/conflict resolution guide, dead-code detection warning, post-merge validation steps&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tasks template handoff&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks&lt;/code&gt; now offers to invoke &lt;code dir=&quot;auto&quot;&gt;/spec-kitty-implement-review&lt;/code&gt; skill at completion for automated full-sprint execution&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-50&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;ReviewLock wired into live command path&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;ReviewLock.acquire()&lt;/code&gt; called in &lt;code dir=&quot;auto&quot;&gt;workflow.py review()&lt;/code&gt; after workspace resolution; &lt;code dir=&quot;auto&quot;&gt;ReviewLock.release()&lt;/code&gt; called in &lt;code dir=&quot;auto&quot;&gt;tasks.py move-task&lt;/code&gt; on review completion&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Removed dead &lt;code dir=&quot;auto&quot;&gt;wp_prompt_path&lt;/code&gt; parameter&lt;/strong&gt; from &lt;code dir=&quot;auto&quot;&gt;generate_fix_prompt()&lt;/code&gt; and all callers&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;310a5---2026-04-06&quot;&gt;[3.1.0a5] - 2026-04-06&lt;/h2&gt;
&lt;h3 id=&quot;fixed-51&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dependency parsing in finalize-tasks&lt;/strong&gt; - new shared parser (&lt;code dir=&quot;auto&quot;&gt;core/dependency_parser.py&lt;/code&gt;) recognizes inline, colon-header, and bullet-list dependency formats. Both &lt;code dir=&quot;auto&quot;&gt;agent mission finalize-tasks&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;agent tasks finalize-tasks&lt;/code&gt; use the same parser. Non-empty disagreement between tasks.md and WP frontmatter triggers a diagnostic error instead of silently overwriting (#406).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;validate-only is genuinely non-mutating&lt;/strong&gt; - all file writes gated behind &lt;code dir=&quot;auto&quot;&gt;if not validate_only&lt;/code&gt;. JSON output reports &lt;code dir=&quot;auto&quot;&gt;would_modify&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;unchanged&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;preserved&lt;/code&gt; without touching disk (#417).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lane computation completeness&lt;/strong&gt; - every executable WP must appear in &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; or lane computation fails with a diagnostic error. Missing ownership manifests are a hard failure. Planning-artifact WPs surfaced in diagnostic summary. Zero-match globs and &lt;code dir=&quot;auto&quot;&gt;src/**&lt;/code&gt; fallback emit warnings (#422).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Parallelism collapse reporting&lt;/strong&gt; - new &lt;code dir=&quot;auto&quot;&gt;CollapseReport&lt;/code&gt; records every union-find merge with rule name and evidence. Rule 3 (surface heuristics) now gated on &lt;code dir=&quot;auto&quot;&gt;_are_disjoint()&lt;/code&gt; - WPs with provably disjoint owned files are not collapsed by keyword matches alone (#423).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Pipe-table mark-status support&lt;/strong&gt; - column-aware parser recognizes &lt;code dir=&quot;auto&quot;&gt;[P]&lt;/code&gt; in Parallel column (not corrupted), updates Status column or appends one. Checkbox format remains canonical for new generation (#438).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agent command guidance&lt;/strong&gt; - all error messages, shim templates, and command-template examples now use &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; consistently. Five &lt;code dir=&quot;auto&quot;&gt;require_explicit_feature()&lt;/code&gt; callers fixed from &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;. Error messages include complete copy-pasteable example commands (#434).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Full —feature → —mission sweep&lt;/strong&gt; - 12 typer.Option declarations, 4 argparse declarations, 11 error messages, and 5 docstrings updated. &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; is the primary displayed flag name; &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; retained as hidden backward-compatibility alias (#448).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-36&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/dependency_parser.py&lt;/code&gt; - canonical shared dependency parser&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;CollapseEvent&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;CollapseReport&lt;/code&gt; data models in &lt;code dir=&quot;auto&quot;&gt;lanes/models.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;LaneComputationError&lt;/code&gt; exception for diagnostic lane failures&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;validate_glob_matches()&lt;/code&gt; in ownership validation&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;planning_artifact_wps&lt;/code&gt; field on &lt;code dir=&quot;auto&quot;&gt;LanesManifest&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Charter regression vigilance rules for &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; terminology canon&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;310a4---2026-04-06&quot;&gt;[3.1.0a4] - 2026-04-06&lt;/h2&gt;
&lt;h3 id=&quot;fixed-52&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission-era host surface cleanup&lt;/strong&gt; - removed remaining feature-era host command references from shipped templates, agent-facing prompts, and smoke-test scaffolding so new missions no longer regenerate &lt;code dir=&quot;auto&quot;&gt;create-feature&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;feature_slug&lt;/code&gt;, or &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; guidance on canonical paths.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Runtime mission metadata normalization&lt;/strong&gt; - mission resolution now prefers canonical &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt; metadata and rehydrates mission identity consistently in diagnostics, verification, and rebuild-state migrations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release-readiness regressions after host cutover&lt;/strong&gt; - updated cross-cutting, orchestrator, parity, body-sync, gitignore-isolation, and e2e smoke coverage to validate the mission-era CLI and contract instead of the removed feature-era host surface.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;310a3---2026-04-05&quot;&gt;[3.1.0a3] - 2026-04-05&lt;/h2&gt;
&lt;h3 id=&quot;fixed-53&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Doctrine artifact discovery in subdirectories&lt;/strong&gt; - all 7 doctrine repositories now use &lt;code dir=&quot;auto&quot;&gt;rglob()&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;glob()&lt;/code&gt;, so artifacts in subdirectories of &lt;code dir=&quot;auto&quot;&gt;shipped/&lt;/code&gt; are no longer silently skipped (#396).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard &lt;code dir=&quot;auto&quot;&gt;/api/features&lt;/code&gt; empty response&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;StatusEvent.from_dict()&lt;/code&gt; now accepts both &lt;code dir=&quot;auto&quot;&gt;feature_slug&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;mission_slug&lt;/code&gt; field names and normalizes the legacy &lt;code dir=&quot;auto&quot;&gt;in_review&lt;/code&gt; lane to &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stale &lt;code dir=&quot;auto&quot;&gt;patch()&lt;/code&gt; targets caught at lint time&lt;/strong&gt; - new &lt;code dir=&quot;auto&quot;&gt;scripts/check_patch_targets.py&lt;/code&gt; validates every &lt;code dir=&quot;auto&quot;&gt;@patch()&lt;/code&gt; target string resolves, added as an &lt;code dir=&quot;auto&quot;&gt;[ENFORCED]&lt;/code&gt; CI lint step (#394).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Architectural layer coverage guards&lt;/strong&gt; - meta-tests fail when a &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; package has no layer assignment or a defined layer matches no module (#395).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sonar reliability bugs&lt;/strong&gt; - resolved 7 findings: unreachable code (S1763), identical branches (S3923), premature async task GC (S7502), always-true condition (S2583), tautological assertion (S3981), CSS shorthand override (S4657), parameter shadowing (S1226).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Async task GC in event emitter&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;asyncio.ensure_future()&lt;/code&gt; results held in &lt;code dir=&quot;auto&quot;&gt;_pending_tasks&lt;/code&gt; set with done-callback cleanup, preventing premature garbage collection.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;check-readiness&lt;/code&gt; CI gate unblocked&lt;/strong&gt; - post-release version bump missed after tagging v3.1.0a2 (#408).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-39&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CI test parallelization&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;fast-tests&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;integration-tests&lt;/code&gt; split into &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;core&lt;/code&gt; phases running in parallel (#397).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--mission-run&lt;/code&gt; as canonical CLI flag&lt;/strong&gt; - added as alias for &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; across all CLI commands. &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; remains accepted as legacy alias.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Node.js 20 → 22&lt;/strong&gt; in CI workflows (current LTS).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mutation testing CI job disabled&lt;/strong&gt; - too slow to run reliably.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Ruff max line length&lt;/strong&gt; increased from 120 to 164.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Defunct &lt;code dir=&quot;auto&quot;&gt;tests/legacy&lt;/code&gt; references removed&lt;/strong&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-37&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;RTK search tooling toolguide&lt;/strong&gt; - new shipped doctrine artifact documenting RTK interception patterns and correct search tooling for worktree sessions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;last_updated&lt;/code&gt; field&lt;/strong&gt; on Toolguide model and schema.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Integration tests for nested artifact discovery&lt;/strong&gt; - 281-line test suite covering all 8 doctrine repository types.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;integration&lt;/code&gt; pytest marker&lt;/strong&gt; registered in &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;310a2---2026-04-05&quot;&gt;[3.1.0a2] - 2026-04-05&lt;/h2&gt;
&lt;h3 id=&quot;changed-40&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Prerelease publishing is now first-class&lt;/strong&gt; - tag-mode release validation accepts matching prerelease tags such as &lt;code dir=&quot;auto&quot;&gt;v3.1.0a0&lt;/code&gt;, GitHub Releases are marked as prereleases automatically for those tags, and maintainer docs now document the end-to-end prerelease PyPI/GitHub publish path.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Rebased doctrine-stack work onto &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;’s execution architecture&lt;/strong&gt; - carry forward the doctrine, constitution, and template-repository work from PR #305 into PR #348 while preserving &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;’s context, ownership, event-log, merge-engine, and shim foundations instead of reviving deleted subsystems.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Kernel established as the shared dependency floor&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;src/kernel/&lt;/code&gt; now owns shared path, atomic-write, and glossary-boundary primitives; doctrine no longer reaches back into &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt;, and the package boundary is documented by ADRs and enforced by architectural tests.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Constitution now acts as the local routing layer for governance assets&lt;/strong&gt; - project-local mission path construction flows through &lt;code dir=&quot;auto&quot;&gt;ProjectMissionPaths&lt;/code&gt;, while doctrine-backed mission/template access is routed through &lt;code dir=&quot;auto&quot;&gt;MissionTemplateRepository&lt;/code&gt; and constitution-facing resolvers instead of scattered path assembly.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission terminology split clarified as the architectural answer to issue #241&lt;/strong&gt; - a direct &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; rename would have collided with the existing mission-type concept, so the branch now separates &lt;code dir=&quot;auto&quot;&gt;mission type&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;--mission-type&lt;/code&gt;) from &lt;code dir=&quot;auto&quot;&gt;mission run&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;--mission-run&lt;/code&gt;) and keeps legacy &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; compatibility where required during the deprecation window.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI flows extended for the new package layout&lt;/strong&gt; - quality workflows now cover doctrine and kernel explicitly, including dedicated kernel coverage enforcement and updated readiness/release paths.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fork-safe SonarCloud targeting via repository variables&lt;/strong&gt; - CI now resolves SonarCloud settings from &lt;code dir=&quot;auto&quot;&gt;SONAR_ORGANIZATION&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;SONAR_PROJECT_KEY&lt;/code&gt;, and optional &lt;code dir=&quot;auto&quot;&gt;SONAR_HOST_URL&lt;/code&gt;, with upstream-safe defaults and a fallback project-key convention of &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;organization&gt;_&amp;#x3C;repo-name&gt;&lt;/code&gt; when &lt;code dir=&quot;auto&quot;&gt;SONAR_PROJECT_KEY&lt;/code&gt; is unset.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-54&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard loading regressions on shared mission installs&lt;/strong&gt; - repaired the shared dashboard JavaScript syntax error, made feature scanning tolerate unreadable legacy event logs, hardened &lt;code dir=&quot;auto&quot;&gt;/api/features&lt;/code&gt; error handling, and marked the scanner regressions as part of the &lt;code dir=&quot;auto&quot;&gt;fast&lt;/code&gt; suite so CI/Sonar coverage reflects the new branches.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Narrow exception handlers in doctrine repositories&lt;/strong&gt; - Replace 21 bare &lt;code dir=&quot;auto&quot;&gt;except Exception&lt;/code&gt; handlers across &lt;code dir=&quot;auto&quot;&gt;src/doctrine/&lt;/code&gt; with specific exception tuples (&lt;code dir=&quot;auto&quot;&gt;YAMLError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ValidationError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;OSError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ModuleNotFoundError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;UnicodeDecodeError&lt;/code&gt;) matching actual failure modes. Addresses PR #305 review finding M1.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fix &lt;code dir=&quot;auto&quot;&gt;spec-kitty --help&lt;/code&gt; crash&lt;/strong&gt; - Add missing &lt;code dir=&quot;auto&quot;&gt;Optional&lt;/code&gt; import to &lt;code dir=&quot;auto&quot;&gt;workflow.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tasks.py&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;from __future__ import annotations&lt;/code&gt; defers annotation evaluation; Typer’s &lt;code dir=&quot;auto&quot;&gt;eval()&lt;/code&gt; of &lt;code dir=&quot;auto&quot;&gt;Optional[str]&lt;/code&gt; annotations raised &lt;code dir=&quot;auto&quot;&gt;NameError&lt;/code&gt; at app construction time.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Address PR #305 architectural review gaps in the rebased branch&lt;/strong&gt; - resolve the core review findings by removing doctrine→&lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; dependency leakage, bringing doctrine into CI coverage, lifting shared glossary/path primitives into kernel, and documenting the resulting boundary in the architecture corpus.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;documentation-2&quot;&gt;Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Doctrine inclusion assessment&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;docs/development/doctrine-inclusion-assessment.md&lt;/code&gt; evaluates the current state of the three Doctrine+Kitty merger pillars (agent profiles ~80%, mission type customization ~45%, ad-hoc experimentation ~25%) with gap analysis, dependency violation status, and phased recommendations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Doctrine skills README&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;src/doctrine/skills/README.md&lt;/code&gt; documents the skills-vs-mission-composition boundary, the iterative context loading pattern, and the skill inventory. Captures the architectural distinction from the PR #305 review.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Updated skill: spec-kitty-runtime-next&lt;/strong&gt; - new “Doctrine-Aware Step Execution” section teaches agents to load agent profiles at init, apply action-scoped constitution context at step boundaries, and pull specific tactics/directives on demand instead of dumping all doctrine upfront.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Updated skill: spec-kitty-constitution-doctrine&lt;/strong&gt; - new “Programmatic Doctrine Access”, “Doctrine Artifact Kinds”, and “Iterative Context Loading Pattern” sections document &lt;code dir=&quot;auto&quot;&gt;DoctrineService&lt;/code&gt; entry points, explain all 8 artifact kinds (directives, tactics, paradigms, styleguides, toolguides, procedures, agent profiles, step contracts) with access patterns, and teach the anti-pattern of upfront context dumps.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Updated skill: spec-kitty-mission-system&lt;/strong&gt; - new “Doctrine Composition Layer” section documents &lt;code dir=&quot;auto&quot;&gt;MissionStepContract&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;Procedure&lt;/code&gt;, and action index artifacts as the structured primitives backing mission behavior.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New skill: ad-hoc-profile-load&lt;/strong&gt; - teaches agents how to load a profile on demand for interactive sessions outside the mission loop: resolve by ID or task context, adopt identity/boundaries/governance scope, maintain role throughout the session, and persist to tool context.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Recorded the remaining follow-on work after the PR #305 -&gt; PR #348 transition&lt;/strong&gt; - the compiler-backed mission-bundle follow-up remains relevant, the skills-vs-mission-composition boundary still needs to stay explicit, constitution-local routing should expand beyond mission-path centralization, issue #241 still has compatibility/documentation cleanup left on older &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt;-based surfaces, and residual runtime/test debt remains outside this rebase-focused integration.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;303---2026-04-01&quot;&gt;[3.0.3] - 2026-04-01&lt;/h2&gt;
&lt;h3 id=&quot;added-38&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Ticket-first mission origin binding&lt;/strong&gt; (feature 061): Service-layer workflow for starting a mission from an existing Jira or Linear ticket. Adds &lt;code dir=&quot;auto&quot;&gt;search_origin_candidates()&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;bind_mission_origin()&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;start_mission_from_ticket()&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;tracker/origin.py&lt;/code&gt;. Persists durable &lt;code dir=&quot;auto&quot;&gt;origin_ticket&lt;/code&gt; provenance in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; with 7-field validation. Emits &lt;code dir=&quot;auto&quot;&gt;MissionOriginBound&lt;/code&gt; observational telemetry event. SaaS-first write ordering ensures local metadata never runs ahead of the authoritative control plane.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reusable feature-creation API&lt;/strong&gt;: Extracted &lt;code dir=&quot;auto&quot;&gt;create_feature_core()&lt;/code&gt; from the CLI command into &lt;code dir=&quot;auto&quot;&gt;core/feature_creation.py&lt;/code&gt; - a stable, programmatic API returning &lt;code dir=&quot;auto&quot;&gt;FeatureCreationResult&lt;/code&gt; with domain exceptions instead of &lt;code dir=&quot;auto&quot;&gt;typer.Exit()&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SaaS tracker client extensions&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;search_issues()&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;bind_mission_origin()&lt;/code&gt; transport methods on &lt;code dir=&quot;auto&quot;&gt;SaaSTrackerClient&lt;/code&gt; with full retry, auth refresh, and error handling.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;302---2026-04-01&quot;&gt;[3.0.2] - 2026-04-01&lt;/h2&gt;
&lt;h3 id=&quot;fixed-55&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Missing prompt-driven slash commands&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;rewrite_agent_shims()&lt;/code&gt; (3.0.0 migration step 6) deleted 9 prompt-driven template files (specify, plan, tasks, etc.) leaving only 7 CLI shims. Now regenerates all 16 command files per the hybrid architecture (feature 058). Added &lt;code dir=&quot;auto&quot;&gt;m_3_0_2&lt;/code&gt; migration to restore prompt files for already-affected projects.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Event log not created at feature birth&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; was only bootstrapped during &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt;, causing &lt;code dir=&quot;auto&quot;&gt;CanonicalStatusNotFoundError&lt;/code&gt; when the dashboard scanned features in the specify/plan phase. Now initialized when &lt;code dir=&quot;auto&quot;&gt;create-feature&lt;/code&gt; runs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard scanner crash on pre-finalization features&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;_count_wps_by_lane()&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;_process_wp_file()&lt;/code&gt; propagate &lt;code dir=&quot;auto&quot;&gt;CanonicalStatusNotFoundError&lt;/code&gt; (hard-fail contract); callers &lt;code dir=&quot;auto&quot;&gt;scan_all_features()&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;scan_feature_kanban()&lt;/code&gt; catch at feature level with actionable error messages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Stale &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.clarify&lt;/code&gt; references&lt;/strong&gt;: Removed 14 remaining references to the deleted clarify command across kitty-specs checklists, coverage tables, and &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Missing &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; entries&lt;/strong&gt;: Added &lt;code dir=&quot;auto&quot;&gt;.kittify/workspaces/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.kittify/merge-state.json&lt;/code&gt; to match &lt;code dir=&quot;auto&quot;&gt;state_contract.py&lt;/code&gt; expectations.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;301---2026-03-31&quot;&gt;[3.0.1] - 2026-03-31&lt;/h2&gt;
&lt;h3 id=&quot;fixed-56&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Canonical status hard cutover completed.&lt;/strong&gt; Work-package lane state is now consistently sourced from &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; across active CLI commands, packaged task tooling, templates, docs, and standalone helpers. Frontmatter lane fallbacks and &lt;code dir=&quot;auto&quot;&gt;lane=&lt;/code&gt; body-log writes are removed from active 3.0 flows.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Canonical bootstrap and hard-fail behavior hardened.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&lt;/code&gt; now seeds canonical &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; state for generated WPs, while runtime commands fail explicitly when canonical status is missing instead of silently reconstructing it from abandoned frontmatter state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release automation updated for 3.x.&lt;/strong&gt; GitHub release validation, maintainer docs, and workflow tag handling now use semantic &lt;code dir=&quot;auto&quot;&gt;vX.Y.Z&lt;/code&gt; tags generically, so &lt;code dir=&quot;auto&quot;&gt;v3.0.1&lt;/code&gt; publishes correctly to GitHub Releases and PyPI.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;300---2026-03-30&quot;&gt;[3.0.0] - 2026-03-30&lt;/h2&gt;
&lt;h3 id=&quot;breaking-changes-1&quot;&gt;Breaking Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Event log is sole authority for mutable WP state.&lt;/strong&gt; Frontmatter &lt;code dir=&quot;auto&quot;&gt;lane&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review_status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;reviewed_by&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;progress&lt;/code&gt; fields are no longer written or read at runtime. Status is read from &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt; via the reducer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;feature_detection.py&lt;/code&gt; deleted.&lt;/strong&gt; All commands require explicit &lt;code dir=&quot;auto&quot;&gt;--feature &amp;#x3C;slug&gt;&lt;/code&gt; in multi-feature repos. No branch scanning, no env var detection, no cwd walking.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Legacy worktree file filtering removed.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;planning_artifact&lt;/code&gt; WPs work in-repo; &lt;code dir=&quot;auto&quot;&gt;code_change&lt;/code&gt; WPs use standard full worktrees.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Command templates restored as hybrid.&lt;/strong&gt; Planning commands (specify, plan, tasks, etc.) install as full prompts; execution commands (implement, review, merge, etc.) install as thin CLI-dispatch shims.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-39&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;MissionContext&lt;/strong&gt; - opaque token-based bound identity for all workflow commands (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/context/&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WP Ownership Manifest&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;execution_mode&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;owned_files&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;authoritative_surface&lt;/code&gt; per WP (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/ownership/&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Lane-weighted progress&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;planned=0.0&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;in_progress=0.3&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;for_review=0.6&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;done=1.0&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/status/progress.py&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty materialize&lt;/code&gt;&lt;/strong&gt; command for CI/debugging regeneration of derived views&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dedicated merge workspace&lt;/strong&gt; at &lt;code dir=&quot;auto&quot;&gt;.kittify/runtime/merge/&lt;/code&gt; with per-mission state and atomic lock&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Merge conflict auto-resolution&lt;/strong&gt; for event logs (append-merge) and metadata (take-theirs)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Thin agent shims&lt;/strong&gt; for CLI-driven commands with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent shim &amp;#x3C;command&gt;&lt;/code&gt; entrypoints&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Schema version gate&lt;/strong&gt; (disabled until 3.0.0 migration ships to consumers)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One-shot migration framework&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;backfill_identity&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;backfill_ownership&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;rebuild_state&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;strip_frontmatter&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;--validate-only&lt;/code&gt;&lt;/strong&gt; flag on &lt;code dir=&quot;auto&quot;&gt;finalize-tasks&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;&lt;/strong&gt; hint in &lt;code dir=&quot;auto&quot;&gt;tasks status&lt;/code&gt; output&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Integration Verification&lt;/strong&gt; section in WP prompt template&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Doctor &lt;code dir=&quot;auto&quot;&gt;command-files&lt;/code&gt;&lt;/strong&gt; check - detects stale/missing/wrong-type agent command files&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Version markers&lt;/strong&gt; in generated command files (&lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;!-- spec-kitty-command-version: X.Y.Z --&gt;&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration &lt;code dir=&quot;auto&quot;&gt;m_2_1_4&lt;/code&gt;&lt;/strong&gt; - unconditionally enforces correct hybrid command file state&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-6&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;feature_detection.py&lt;/code&gt; (668 lines) - replaced by MissionContext tokens&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;status/legacy_bridge.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status/phase.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status/reconcile.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status/migrate.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;merge/executor.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge/forecast.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge/status_resolver.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;core/agent_context.py&lt;/code&gt; - tech-stack parsing no longer needed&lt;/li&gt;
&lt;li&gt;~56 command template files (replaced by 9 canonical prompts + 7 thin shims)&lt;/li&gt;
&lt;li&gt;Sparse checkout policy enforcement&lt;/li&gt;
&lt;li&gt;Frontmatter lane/review_status read/write throughout codebase&lt;/li&gt;
&lt;li&gt;Dual-write (event log + frontmatter) behavior&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-57&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;“planning repository” → “project root checkout” terminology (migration included)&lt;/li&gt;
&lt;li&gt;Template path references removed from agent prompts (agents no longer search for &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&lt;/code&gt; files)&lt;/li&gt;
&lt;li&gt;Workflow &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt; now emit status events (was silently failing)&lt;/li&gt;
&lt;li&gt;Merge reconciliation marks ALL ancestor WPs as done (not just effective tips)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;require_explicit_feature()&lt;/code&gt; lists available features in error message&lt;/li&gt;
&lt;li&gt;YAML parse errors in frontmatter now logged as warnings (not silently swallowed)&lt;/li&gt;
&lt;li&gt;Merge engine uses &lt;code dir=&quot;auto&quot;&gt;git reset --hard&lt;/code&gt; on detached HEAD (not &lt;code dir=&quot;auto&quot;&gt;git checkout&lt;/code&gt; which fails when branch is checked out elsewhere)&lt;/li&gt;
&lt;li&gt;Migration backup covers &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; (not just &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;rebuild_state.py&lt;/code&gt; uses max timestamp (not last file line) for terminal state&lt;/li&gt;
&lt;li&gt;Merge lock uses atomic &lt;code dir=&quot;auto&quot;&gt;open(&apos;x&apos;)&lt;/code&gt; (not TOCTOU &lt;code dir=&quot;auto&quot;&gt;exists()&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;write_text()&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;merge --resume&lt;/code&gt; errors when multiple paused merges exist (not silently picks first)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;214---2026-03-27&quot;&gt;[2.1.4] - 2026-03-27&lt;/h2&gt;
&lt;h3 id=&quot;added-40&quot;&gt;Added&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Enforce correct command file state&lt;/strong&gt;: Version markers and migration to guarantee all agent command files are always in the correct state.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;!-- spec-kitty-command-version: X.Y.Z --&gt;&lt;/code&gt; marker added as the first line of every generated command file (both full prompts and thin shims)&lt;/li&gt;
&lt;li&gt;Migration &lt;code dir=&quot;auto&quot;&gt;m_2_1_4_enforce_command_file_state&lt;/code&gt; unconditionally writes all 16 command files per configured agent; idempotent on subsequent runs when version markers match&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty doctor command-files&lt;/code&gt; subcommand checks all agent command files for missing files, stale version markers, and wrong file type (full prompt vs thin shim)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;213---2026-03-27&quot;&gt;[2.1.3] - 2026-03-27&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-15&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Preserve explicit WP args in workflow prompts&lt;/strong&gt;: Slash-command arguments passed to &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.implement&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.review&lt;/code&gt; are now forwarded into the resolver-first flow instead of being silently dropped. Agents receiving explicit WP selectors (e.g., &lt;code dir=&quot;auto&quot;&gt;WP03&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--base WP01&lt;/code&gt;) will correctly pass them to &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent context resolve&lt;/code&gt; via &lt;code dir=&quot;auto&quot;&gt;--wp-id&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; flags.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;implement.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;review.md&lt;/code&gt; mission templates now include an &lt;code dir=&quot;auto&quot;&gt;{ARGS}&lt;/code&gt; placeholder with conditional forwarding instructions&lt;/li&gt;
&lt;li&gt;Public slash-command docs updated: &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.implement&lt;/code&gt; documents &lt;code dir=&quot;auto&quot;&gt;[--base WP_ID]&lt;/code&gt; support; &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.review&lt;/code&gt; is now WP-only (removed stale “or prompt path” syntax)&lt;/li&gt;
&lt;li&gt;Regression tests added across Markdown and TOML agent formats to ensure argument placeholders survive rendering&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;212---2026-03-23&quot;&gt;[2.1.2] - 2026-03-23&lt;/h2&gt;
&lt;h3 id=&quot;-improved-1&quot;&gt;🔧 Improved&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Skills audit and expansion&lt;/strong&gt;: All 6 distributed skills audited, command-verified, and expanded with full architecture documentation. Skills now document internal systems (glossary pipeline, constitution extraction, runtime DAG, git workflow boundary) so agents can operate effectively.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;setup-doctor: Fixed wrong CLI commands (&lt;code dir=&quot;auto&quot;&gt;verify&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;verify-setup&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;agent tasks status&lt;/code&gt;), added &lt;code dir=&quot;auto&quot;&gt;--remove-orphaned&lt;/code&gt; safety warning&lt;/li&gt;
&lt;li&gt;runtime-review: Added discovery step, &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; flags, empty-lane guidance&lt;/li&gt;
&lt;li&gt;glossary-context: Added 5-layer middleware pipeline, extraction methods, checkpoint/resume, step config&lt;/li&gt;
&lt;li&gt;constitution-doctrine: Added extraction rules, governance.yaml schema, interview profiles, answers.yaml schema&lt;/li&gt;
&lt;li&gt;runtime-next: Added decision algorithm, WP iteration logic, 6 guard primitives, agent loop pattern&lt;/li&gt;
&lt;li&gt;orchestrator-api: Added JSON output examples, error code catalog, idempotency behavior, preflight details&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added-11&quot;&gt;✨ Added&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;2 new skills&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty-mission-system&lt;/code&gt; (explains missions, 4 types, template resolution, guards) and &lt;code dir=&quot;auto&quot;&gt;spec-kitty-git-workflow&lt;/code&gt; (documents Python vs agent git operation boundary).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Reusable skill update utility&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/upgrade/skill_update.py&lt;/code&gt; for finding and patching skill files across all 13 agent skill roots.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;10 upgrade migrations&lt;/strong&gt; for consumer projects: 6 skill fixes, 1 release skill removal, 2 new skill installations, 1 glossary skill expansion.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Documentation parity sprint (Feature 056)&lt;/strong&gt;: DocFX build now includes all 4 Divio categories (was only building 1x/ and 2x/). 5 new user guides distilled from skills, 4 existing docs expanded, 22 fact-check corrections across 20 files.&lt;/p&gt;
&lt;h3 id=&quot;-fixed-16&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;DocFX build gap&lt;/strong&gt;: 56 docs files (tutorials, how-to, reference, explanation) were in the repo but excluded from the docs.spec-kitty.ai build. Now included via updated &lt;code dir=&quot;auto&quot;&gt;docfx.json&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;8-lane state machine documentation&lt;/strong&gt;: All docs updated from outdated 4-lane model (planned/doing/for_review/done) to correct 8-lane model (planned/claimed/in_progress/for_review/approved/done/blocked/canceled) with 24 allowed transitions.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;CLI reference completeness&lt;/strong&gt;: Added 12 missing commands to cli-commands.md, 7 missing subcommands to agent-subcommands.md. Fixed &lt;code dir=&quot;auto&quot;&gt;spec-kitty sync&lt;/code&gt; (documented as flat command, actually a group with 6 subcommands).&lt;/p&gt;
&lt;h3 id=&quot;-maintenance-1&quot;&gt;🧹 Maintenance&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Removed &lt;code dir=&quot;auto&quot;&gt;release&lt;/code&gt; skill from distribution (spec-kitty development only, not for consumers)&lt;/li&gt;
&lt;li&gt;Removed obsolete &lt;code dir=&quot;auto&quot;&gt;docs/how-to/upgrade-to-0-11-0.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Fixed all cross-reference links in new docs (0 new DocFX build warnings)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;211---2026-03-21&quot;&gt;[2.1.1] - 2026-03-21&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-17&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bundled doctrine payload in wheels&lt;/strong&gt;: the PyPI wheel now includes the full &lt;code dir=&quot;auto&quot;&gt;doctrine/&lt;/code&gt; package tree, including the canonical skill pack under &lt;code dir=&quot;auto&quot;&gt;doctrine/skills/&lt;/code&gt;, so &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; can install managed skills for shipped builds.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;2.1.0 repair migration&lt;/strong&gt;: added &lt;code dir=&quot;auto&quot;&gt;2.1.1_repair_skill_pack&lt;/code&gt; so projects that already upgraded on broken &lt;code dir=&quot;auto&quot;&gt;2.1.0&lt;/code&gt; wheels reinstall the canonical managed skill pack on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release verification guard&lt;/strong&gt;: the release workflow now fails if the built wheel omits doctrine files or bundled skills, and distribution tests now assert that a wheel-installed &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; produces the managed skill manifest and installed skill files.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;210---2026-03-21&quot;&gt;[2.1.0] - 2026-03-21&lt;/h2&gt;
&lt;h3 id=&quot;-added-12&quot;&gt;✅ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;agent skills Pack (&lt;code dir=&quot;auto&quot;&gt;#330&lt;/code&gt;)&lt;/strong&gt;: added canonical bundled skills, registry/installer/verification flow, manifest support, and upgrade migration &lt;code dir=&quot;auto&quot;&gt;m_2_0_11_install_skills&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Structured requirement mapping (&lt;code dir=&quot;auto&quot;&gt;#329&lt;/code&gt;)&lt;/strong&gt;: added requirement-to-work-package mapping support with CLI integration for tracing delivery intent into execution planning.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-4&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Deterministic planning branch intent (&lt;code dir=&quot;auto&quot;&gt;#328&lt;/code&gt;)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;plan&lt;/code&gt; commands now inject explicit target-branch metadata into templates to reduce ambiguity in downstream execution.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Primary release line promotion&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt; becomes the stable &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; line, with GitHub Releases and PyPI publication starting at &lt;code dir=&quot;auto&quot;&gt;2.1.0&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-deprecated&quot;&gt;⚠️ Deprecated&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt; overall&lt;/strong&gt;: the former &lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt; line is now deprecated and moves to &lt;code dir=&quot;auto&quot;&gt;1.x-maintenance&lt;/code&gt; for critical fixes only. No new &lt;code dir=&quot;auto&quot;&gt;1.x&lt;/code&gt; PyPI releases are planned.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-removed&quot;&gt;🗑️ Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Public &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.clarify&lt;/code&gt; slash command (&lt;code dir=&quot;auto&quot;&gt;#322&lt;/code&gt;)&lt;/strong&gt;: removed the legacy clarify command, template, and migration path in favor of the current planning/discovery flow.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;2011---2026-03-20&quot;&gt;[2.0.11] - 2026-03-20&lt;/h2&gt;
&lt;h3 id=&quot;-documentation&quot;&gt;📄 Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;2.x release metadata refresh&lt;/strong&gt;: updated the README’s current-release banner so the branch advertises the active GitHub-only 2.x release line instead of the initial &lt;code dir=&quot;auto&quot;&gt;v2.0.0&lt;/code&gt; placeholder.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;2010---2026-03-20&quot;&gt;[2.0.10] - 2026-03-20&lt;/h2&gt;
&lt;h3 id=&quot;-added-13&quot;&gt;✅ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Project-level &lt;code dir=&quot;auto&quot;&gt;auto_commit&lt;/code&gt; setting (&lt;code dir=&quot;auto&quot;&gt;#321&lt;/code&gt;)&lt;/strong&gt;: repos can now configure automatic commit behavior directly in project config.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sync queue resilience and diagnostics (&lt;code dir=&quot;auto&quot;&gt;#320&lt;/code&gt;)&lt;/strong&gt;: offline queue now supports FIFO eviction, coalescing, configurable caps, and sync doctor coverage for failure recovery.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-18&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Merge target resolution (&lt;code dir=&quot;auto&quot;&gt;#272&lt;/code&gt;)&lt;/strong&gt;: merge target branch is now resolved from feature &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, preventing merges from targeting the wrong branch.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Acceptance and state persistence hardening (&lt;code dir=&quot;auto&quot;&gt;#319&lt;/code&gt;)&lt;/strong&gt;: state writes are now centralized around canonical metadata/state handling to reduce drift across acceptance, mission, and status flows.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Feature context fallback restored&lt;/strong&gt;: ambiguous agent/task resolution now falls back to the latest incomplete feature instead of stopping on a stale explicit-selection error.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Upgrade downgrade protection&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now refuses older targets instead of silently rewriting project metadata backwards.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration discovery fail-fast&lt;/strong&gt;: broken &lt;code dir=&quot;auto&quot;&gt;m_*.py&lt;/code&gt; modules now fail discovery immediately instead of being skipped with a stderr warning.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Upgrade metadata durability&lt;/strong&gt;: successful and failed migration records are now persisted immediately so retries can resume from an accurate state after mid-run failures.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Safe auto-commit stash isolation&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;safe_commit()&lt;/code&gt; now restores only the stash entry it created, preventing unrelated user stashes from being popped during upgrade/status auto-commits.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Embedded task script compatibility&lt;/strong&gt;: copied &lt;code dir=&quot;auto&quot;&gt;.kittify/scripts/tasks&lt;/code&gt; helpers now fall back cleanly when the host &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; install is older than the copied templates.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-5&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;State architecture cleanup phase 2 (&lt;code dir=&quot;auto&quot;&gt;#319&lt;/code&gt;)&lt;/strong&gt;: consolidated atomic-write and state-contract handling across runtime, acceptance, and feature metadata paths.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test and quality isolation follow-ups&lt;/strong&gt;: retained the refactors that separated policy/test churn from release-critical behavior on the 2.x line.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;209---2026-03-15&quot;&gt;[2.0.9] - 2026-03-15&lt;/h2&gt;
&lt;h3 id=&quot;-added-14&quot;&gt;✅ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mutation testing CI integration (feat #047)&lt;/strong&gt;: mutmut toolchain setup, CI integration, and targeted kill sessions for &lt;code dir=&quot;auto&quot;&gt;status/&lt;/code&gt; reducer and transitions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agentic mutation testing remediation workflow&lt;/strong&gt;: GitHub Agentic Workflow (gh-aw) replaces the legacy Claude workflow for mutation testing remediation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SonarCloud integration&lt;/strong&gt;: added SonarCloud config; &lt;code dir=&quot;auto&quot;&gt;develop&lt;/code&gt; branch recognized as 2.x-equivalent in CI quality gates.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Architecture corpus restructure&lt;/strong&gt;: versioned architecture docs under &lt;code dir=&quot;auto&quot;&gt;architecture/1.x/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;architecture/2.x/&lt;/code&gt;, 45 ADRs, glossary contexts across 10 bounded domains, Contextive integration, and stakeholder persona definitions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; schema example in specify template&lt;/strong&gt;: documents &lt;code dir=&quot;auto&quot;&gt;&quot;target_branch&quot;&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;&quot;vcs&quot;&lt;/code&gt; as required explicit fields.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-19&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Post-rebase quality fixes&lt;/strong&gt;: resolved unmatched &lt;code dir=&quot;auto&quot;&gt;)&lt;/code&gt; syntax error, &lt;code dir=&quot;auto&quot;&gt;gap_analysis_path&lt;/code&gt; undefined name (F821), &lt;code dir=&quot;auto&quot;&gt;timezone&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;UTC&lt;/code&gt; reference, unused &lt;code dir=&quot;auto&quot;&gt;type: ignore&lt;/code&gt; comments, and &lt;code dir=&quot;auto&quot;&gt;toml&lt;/code&gt; import-untyped mypy errors.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test isolation&lt;/strong&gt;: moved misplaced test package; fixed 3 test failures and Pydantic V1 deprecation warnings.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sync offline queue&lt;/strong&gt;: redirect offline queue warning to stderr instead of stdout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI branch detection&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;develop&lt;/code&gt; now recognized as a 2.x branch for branch-contract guards.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-6&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Ruff lint compliance&lt;/strong&gt;: full ruff clean pass across &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;; added ruff lint config to &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Documentation site updates&lt;/strong&gt;: 2.x docs site refresh with Contextive IDE integration guide.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test suite restructuring&lt;/strong&gt;: migrated to vertical-slice layout; redesigned CI quality workflow; annotated suite with fast/slow/git_repo markers; deleted tests/legacy/ after extracting unique behaviours.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;208---2026-03-11&quot;&gt;[2.0.8] - 2026-03-11&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-20&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard approved lane&lt;/strong&gt;: WPs with &lt;code dir=&quot;auto&quot;&gt;lane: &quot;approved&quot;&lt;/code&gt; no longer silently fall back to the “planned” column. Added “Approved” as a 5th kanban column between For Review and Done, with &lt;code dir=&quot;auto&quot;&gt;claimed&lt;/code&gt;→planned and &lt;code dir=&quot;auto&quot;&gt;in_progress&lt;/code&gt;→doing lane normalization in the scanner.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Slim FEATURE_CONTEXT_UNRESOLVED payload&lt;/strong&gt;: reduced error payload size for LLM consumption to stay within agent context budgets.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;207---2026-03-11&quot;&gt;[2.0.7] - 2026-03-11&lt;/h2&gt;
&lt;h3 id=&quot;-added-15&quot;&gt;✅ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mutation testing CI integration (feat #047)&lt;/strong&gt;: mutmut toolchain setup, CI integration, and targeted kill sessions for &lt;code dir=&quot;auto&quot;&gt;status/&lt;/code&gt; reducer and transitions (#275).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agentic mutation testing remediation workflow&lt;/strong&gt;: GitHub Agentic Workflow (gh-aw) replaces the legacy Claude workflow for mutation testing remediation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;SonarCloud integration&lt;/strong&gt;: added SonarCloud config; &lt;code dir=&quot;auto&quot;&gt;develop&lt;/code&gt; branch recognized as 2.x-equivalent in CI quality gates.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Architecture corpus restructure&lt;/strong&gt;: versioned architecture docs under &lt;code dir=&quot;auto&quot;&gt;architecture/1.x/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;architecture/2.x/&lt;/code&gt;, 45 ADRs, glossary contexts across 10 bounded domains, Contextive integration, and stakeholder persona definitions.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Google Antigravity as first-class agent (#266)&lt;/strong&gt;: added Google Antigravity to the supported agent roster with directory, templates, and migration coverage.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Commands own workflow context (#261)&lt;/strong&gt;: commands now carry their own workflow context rather than relying on ambient state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tracker snapshot publish payload (feat #048)&lt;/strong&gt;: resource routing in publish path (WP01) and batch API contract for tracker snapshot publish (WP02).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-21&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Stale overrides from upgrade version-skew (#285)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;classify_asset()&lt;/code&gt; now compares project &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; files against immutable package-bundled defaults (&lt;code dir=&quot;auto&quot;&gt;get_package_asset_root()&lt;/code&gt;) instead of the mutable &lt;code dir=&quot;auto&quot;&gt;~/.kittify/&lt;/code&gt; directory. This prevents old managed templates from being misclassified as user customizations and permanently shadowing newer templates in &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/&lt;/code&gt; during upgrades.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New &lt;code dir=&quot;auto&quot;&gt;SUPERSEDED&lt;/code&gt; disposition&lt;/strong&gt;: managed files that differ from the current package default are now correctly classified as &lt;code dir=&quot;auto&quot;&gt;SUPERSEDED&lt;/code&gt; (removed) rather than &lt;code dir=&quot;auto&quot;&gt;CUSTOMIZED&lt;/code&gt; (moved to overrides). Only files with no package counterpart are treated as genuine user customizations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Repair migration for already-affected users&lt;/strong&gt;: new &lt;code dir=&quot;auto&quot;&gt;2.0.7_fix_stale_overrides&lt;/code&gt; migration scans &lt;code dir=&quot;auto&quot;&gt;.kittify/overrides/&lt;/code&gt; for files byte-identical to current package defaults and removes them. Genuine user customizations are preserved.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Constitution: resolve_doctrine_root fallback for pip-installed users (#278)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;resolve_doctrine_root()&lt;/code&gt; no longer crashes when the &lt;code dir=&quot;auto&quot;&gt;doctrine&lt;/code&gt; package directory is missing from pip wheels; falls back to &lt;code dir=&quot;auto&quot;&gt;specify_cli&lt;/code&gt; package root.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Merge: worktree/branch cleanup when feature is already integrated (#271)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty merge&lt;/code&gt; now runs worktree removal and branch deletion when all WP branches are already merged, instead of exiting with “Nothing to merge” and leaving cleanup to the user.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Post-rebase quality fixes (#273)&lt;/strong&gt;: resolved unmatched &lt;code dir=&quot;auto&quot;&gt;)&lt;/code&gt; syntax error, &lt;code dir=&quot;auto&quot;&gt;gap_analysis_path&lt;/code&gt; undefined name (F821), &lt;code dir=&quot;auto&quot;&gt;timezone&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;UTC&lt;/code&gt; reference, unused &lt;code dir=&quot;auto&quot;&gt;type: ignore&lt;/code&gt; comments, and &lt;code dir=&quot;auto&quot;&gt;toml&lt;/code&gt; import-untyped mypy errors.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test isolation&lt;/strong&gt;: moved misplaced test package; fixed 3 test failures and Pydantic V1 deprecation warnings.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sync offline queue&lt;/strong&gt;: redirect offline queue warning to stderr instead of stdout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CI branch detection&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;develop&lt;/code&gt; now recognized as a 2.x branch for branch-contract guards.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tracker publish path normalization (feat #048)&lt;/strong&gt;: normalize provider in publish path and document auth token resolution.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-7&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Ruff lint compliance&lt;/strong&gt;: full ruff clean pass across &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tests/&lt;/code&gt;; added ruff lint config to &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Documentation site updates&lt;/strong&gt;: 2.x docs site refresh with Contextive IDE integration guide.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;206---2026-03-10&quot;&gt;[2.0.6] - 2026-03-10&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-22&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Upgrade consistency sweep&lt;/strong&gt;: added a new &lt;code dir=&quot;auto&quot;&gt;2.0.6_consistency_sweep&lt;/code&gt; migration that backfills missing or blank feature &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;, infers &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; from feature docs or the repo primary branch, reconstructs missing &lt;code dir=&quot;auto&quot;&gt;status.events.jsonl&lt;/code&gt;, regenerates &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; and generated &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; status blocks, normalizes legacy WP frontmatter lane aliases/quoting, rewrites stale prompt paths, and archives orphan empty &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt; snapshots before rebuilding canonical state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Worktree upgrade coverage&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now upgrades worktrees that have &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; or legacy &lt;code dir=&quot;auto&quot;&gt;.specify/&lt;/code&gt; state even when &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; has not been created yet.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Detector false positives&lt;/strong&gt;: runtime-managed 2.x installs no longer trip legacy project-local mission migrations, and the constitution migration only flags the legacy &lt;code dir=&quot;auto&quot;&gt;.kittify/memory/constitution.md&lt;/code&gt; path.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Target-branch backfill correctness&lt;/strong&gt;: the &lt;code dir=&quot;auto&quot;&gt;0.13.8_target_branch&lt;/code&gt; migration now uses repo-aware branch inference instead of the obsolete hardcoded Feature 025 exception.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;205---2026-03-10&quot;&gt;[2.0.5] - 2026-03-10&lt;/h2&gt;
&lt;h3 id=&quot;-added-16&quot;&gt;✅ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Namespace-aware artifact body sync (Feature 047)&lt;/strong&gt;: Full offline-first pipeline for pushing spec artifact bodies (markdown content) to the SaaS backend, including &lt;code dir=&quot;auto&quot;&gt;NamespaceRef&lt;/code&gt; typed identifiers, &lt;code dir=&quot;auto&quot;&gt;OfflineBodyUploadQueue&lt;/code&gt; SQLite persistence, body upload preparation and filtering, HTTP transport with response classification, dossier pipeline orchestration with partial failure handling, background sync queue drain, and end-to-end diagnostics/logging.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-23&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Init default directory (&lt;code dir=&quot;auto&quot;&gt;#258&lt;/code&gt;)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now defaults to the current directory when project name is omitted on the 2.x line.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Sync integration&lt;/strong&gt;: Completed namespace artifact body sync wiring for end-to-end operation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-documentation-1&quot;&gt;📄 Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Connector auth binding ADR&lt;/strong&gt;: Added architectural decision record for connector authentication binding and installation model gap analysis.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Command-owned action context ADR&lt;/strong&gt;: Defined command-owned action context pattern.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;204---2026-03-06&quot;&gt;[2.0.4] - 2026-03-06&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-24&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Upgrade JSON machine-parseability hardening (&lt;code dir=&quot;auto&quot;&gt;#254&lt;/code&gt;)&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade --json&lt;/code&gt; now emits raw JSON output without Rich console wrapping.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Upgrade migration status consistency (&lt;code dir=&quot;auto&quot;&gt;#256&lt;/code&gt;)&lt;/strong&gt;: non-applicable migrations are reported as &lt;code dir=&quot;auto&quot;&gt;skipped&lt;/code&gt; instead of incorrectly marked as applied.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-8&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Contract hardening closeout (&lt;code dir=&quot;auto&quot;&gt;#213&lt;/code&gt;-&lt;code dir=&quot;auto&quot;&gt;#218&lt;/code&gt;)&lt;/strong&gt;: merged deterministic branch/runtime contracts, typed artifact-path payloads, merge/preflight JSON enrichment, and banner suppression in agent contexts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Codex/Copilot slash-flow reliability (&lt;code dir=&quot;auto&quot;&gt;#128&lt;/code&gt;)&lt;/strong&gt;: integrated slash-command output stability improvements via deterministic JSON/banners/template alignment.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Worktree/preflight stability (&lt;code dir=&quot;auto&quot;&gt;#226&lt;/code&gt;)&lt;/strong&gt;: released preflight and command-contract hardening on the 2.x line for end-to-end spec→implement→review runs.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;202---2026-02-27&quot;&gt;[2.0.2] - 2026-02-27&lt;/h2&gt;
&lt;h3 id=&quot;-added-17&quot;&gt;✅ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Flag-gated tracker command group&lt;/strong&gt;: added &lt;code dir=&quot;auto&quot;&gt;spec-kitty tracker ...&lt;/code&gt; commands behind &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_ENABLE_SAAS_SYNC&lt;/code&gt;, including provider listing, bind/unbind, mapping, local sync pull/push/run, and snapshot publish.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tracker host-local persistence + credentials support&lt;/strong&gt;: added CLI-owned tracker SQLite cache/checkpoints and provider credential handling consistent with existing Spec Kitty host persistence patterns.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-9&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dependency floor hardening for 2.x installs&lt;/strong&gt;: added explicit lower bounds for previously unbounded core CLI direct dependencies to reduce resolver drift in fresh environments.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Workflow review lane guard&lt;/strong&gt;: review start now requires a valid &lt;code dir=&quot;auto&quot;&gt;for_review&lt;/code&gt; lane state before progressing.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;201---2026-02-26&quot;&gt;[2.0.1] - 2026-02-26&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-25&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Main bias fix&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;resolve_primary_branch()&lt;/code&gt; now checks the current branch before the hardcoded &lt;code dir=&quot;auto&quot;&gt;[main, master, develop]&lt;/code&gt; list. Repos on non-standard primary branches (e.g., &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;) no longer get blocked by &lt;code dir=&quot;auto&quot;&gt;spec-kitty specify&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;create_feature()&lt;/code&gt; records the current branch as &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; instead of guessing via heuristics. Added &lt;code dir=&quot;auto&quot;&gt;--target-branch&lt;/code&gt; CLI option for explicit override.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;guards.py&lt;/code&gt; uses &lt;code dir=&quot;auto&quot;&gt;resolve_primary_branch()&lt;/code&gt; instead of hardcoded &lt;code dir=&quot;auto&quot;&gt;{&quot;main&quot;, &quot;master&quot;}&lt;/code&gt; set.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;merge-feature --target&lt;/code&gt; auto-detects from &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; when not specified.&lt;/li&gt;
&lt;li&gt;Template references to “main” replaced with “target branch” throughout command templates.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-10&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard &lt;code dir=&quot;auto&quot;&gt;--open&lt;/code&gt; flag&lt;/strong&gt;: Browser auto-open is now disabled by default. Pass &lt;code dir=&quot;auto&quot;&gt;--open&lt;/code&gt; to open the dashboard URL in your browser. Prevents browser windows from spawning during tests or CI.&lt;/li&gt;
&lt;li&gt;Consolidated 3 ad-hoc branch-check functions into &lt;code dir=&quot;auto&quot;&gt;_show_branch_context()&lt;/code&gt; for consistent branch banners across all planning commands.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;200---2026-02-22&quot;&gt;[2.0.0] - 2026-02-22&lt;/h2&gt;
&lt;h3 id=&quot;-changed-11&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Start semantic versioning for &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt; GitHub-only releases using &lt;code dir=&quot;auto&quot;&gt;v2.&amp;#x3C;minor&gt;.&amp;#x3C;patch&gt;&lt;/code&gt; tags.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt; release automation now publishes GitHub Releases only (no PyPI publish step).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-26&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; no longer short-circuits &lt;code dir=&quot;auto&quot;&gt;--result failed|blocked&lt;/code&gt; in the CLI bridge; both now flow through &lt;code dir=&quot;auto&quot;&gt;spec-kitty-runtime&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;next_step(...)&lt;/code&gt;, preserving canonical runtime lifecycle behavior and run metadata.&lt;/li&gt;
&lt;li&gt;Runtime mission template selection for &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; now follows deterministic precedence tiers (&lt;code dir=&quot;auto&quot;&gt;explicit&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;env&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project override&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project legacy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;user global&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project config&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;builtin&lt;/code&gt;) when resolving &lt;code dir=&quot;auto&quot;&gt;mission-runtime.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--answer --json&lt;/code&gt; integration coverage now exercises a real pending-decision success path (runtime &lt;code dir=&quot;auto&quot;&gt;requires_inputs&lt;/code&gt;) instead of fake decision IDs.&lt;/li&gt;
&lt;li&gt;Added replay-parity integration coverage in &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; against &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt; canonical fixture stream (&lt;code dir=&quot;auto&quot;&gt;mission-next-replay-full-lifecycle&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WP prompt tracking reliability&lt;/strong&gt;: removed stale &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**/tasks/*.md&lt;/code&gt; from tracked &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;, migrated existing projects away from that rule, and hardened workflow status commits to fail loudly if claim commits cannot be written.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;200a5---2026-02-14&quot;&gt;[2.0.0a5] - 2026-02-14&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-27&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Backported orchestrator deadlock fixes from v0.15.3&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Orchestrator deadlock&lt;/strong&gt;: Fixed false “No progress possible” detection when WP tasks raise exceptions or complete but leave WPs in intermediate states (IMPLEMENTATION/REVIEW). The orchestrator now properly marks failed WPs as FAILED and restarts orphaned WPs, preventing deadlock cascades. (Backport of #137 by @tannn)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Exception handling&lt;/strong&gt;: Task exceptions now properly mark WPs as FAILED with error details, allowing dependent WPs to recognize failure instead of blocking indefinitely&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;WP restart logic&lt;/strong&gt;: Added restart counter to prevent infinite restart loops if WP repeatedly fails to advance state. Restarts are now capped at &lt;code dir=&quot;auto&quot;&gt;max_retries&lt;/code&gt; (default: 3)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;State recovery&lt;/strong&gt;: Improved detection of interrupted implementations (IMPLEMENTATION status without &lt;code dir=&quot;auto&quot;&gt;implementation_completed&lt;/code&gt; timestamp) to automatically reset and retry&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-maintenance-2&quot;&gt;🧹 Maintenance&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Test coverage&lt;/strong&gt;: Added 8 new orchestrator tests covering exception handling, restart scenarios, deadlock detection, and state persistence&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test quality&lt;/strong&gt;: Reorganized test suite with proper markers (&lt;code dir=&quot;auto&quot;&gt;@pytest.mark.orchestrator_exception_handling&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.orchestrator_deadlock_detection&lt;/code&gt;) and class grouping following project conventions&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;200a4---2026-02-13&quot;&gt;[2.0.0a4] - 2026-02-13&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-28&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Backported v0.15.2 hotfix from main branch&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Branch detection&lt;/strong&gt;: Replaced single &lt;code dir=&quot;auto&quot;&gt;rev-parse --abbrev-ref HEAD&lt;/code&gt; with dual-strategy
approach (&lt;code dir=&quot;auto&quot;&gt;git branch --show-current&lt;/code&gt; primary, &lt;code dir=&quot;auto&quot;&gt;rev-parse&lt;/code&gt; fallback). Fixes unborn branch
detection and detached HEAD handling. Updated all inline callers in tasks.py, workflow.py,
and vcs/git.py.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Subprocess encoding safety&lt;/strong&gt;: Added &lt;code dir=&quot;auto&quot;&gt;encoding=&quot;utf-8&quot;, errors=&quot;replace&quot;&lt;/code&gt; to all ~135
&lt;code dir=&quot;auto&quot;&gt;subprocess.run(text=True)&lt;/code&gt; calls across 36 files. Prevents crashes on non-UTF-8 git output (Windows, locale mismatches).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Pre-commit hook safety&lt;/strong&gt;: Removed &lt;code dir=&quot;auto&quot;&gt;set -e&lt;/code&gt; from encoding check hook, expanded Python
interpreter detection (loops through python3/python/py with smoke test), fixed exit code
handling to distinguish encoding errors (exit 2) from execution failures.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Init fail-fast&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now raises RuntimeError immediately after git init
failure instead of falling through to “project ready” success message.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;PowerShell templates&lt;/strong&gt;: Added PowerShell equivalent blocks to implement.md templates
for software-dev, research, and documentation missions.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;200a3---2026-02-11&quot;&gt;[2.0.0a3] - 2026-02-11&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-29&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Complete Bug #119 cherry-pick&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed missing update to &lt;code dir=&quot;auto&quot;&gt;scripts/tasks/acceptance_support.py&lt;/code&gt; (root-level test helper)&lt;/li&gt;
&lt;li&gt;This file was missed in the original Bug #119 cherry-pick, causing test failures&lt;/li&gt;
&lt;li&gt;Now all acceptance_support.py copies correctly exclude ‘done’ lane from assignee requirement&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;200a2---2026-02-11&quot;&gt;[2.0.0a2] - 2026-02-11&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-30&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Cherry-picked 7 critical bug fixes from v0.15.0 (main branch)&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bug #95&lt;/strong&gt;: Enforce kebab-case validation for feature slugs&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Rejects slugs with spaces, underscores, uppercase, or leading numbers&lt;/li&gt;
&lt;li&gt;Prevents invalid directory structures and broken workflow commands&lt;/li&gt;
&lt;li&gt;Added 8 comprehensive validation tests&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bug #120&lt;/strong&gt;: Use local git exclude for worktree ignores&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Worktree-specific ignores now written to &lt;code dir=&quot;auto&quot;&gt;.git/info/exclude&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Prevents &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; pollution when merging worktrees&lt;/li&gt;
&lt;li&gt;VCS abstraction layer handles legacy worktree filtering consistently&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bug #117&lt;/strong&gt;: Improve dashboard lifecycle and error diagnostics&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Dashboard process detection no longer reports false failures&lt;/li&gt;
&lt;li&gt;Distinguishes between health check timeout (process running) vs actual failure&lt;/li&gt;
&lt;li&gt;Provides specific error messages for missing metadata, port conflicts, permission errors&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bug #124&lt;/strong&gt;: Unify branch resolution, stop implicit master fallback&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Respects user’s current branch instead of auto-checkout&lt;/li&gt;
&lt;li&gt;Shows notification when current branch differs from feature target&lt;/li&gt;
&lt;li&gt;No more surprise checkouts during &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;move-task&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Consistent branch resolution across all commands&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bug #119&lt;/strong&gt;: Relax strict assignee gate in acceptance validation&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Assignee now optional for completed work packages in ‘done’ lane&lt;/li&gt;
&lt;li&gt;Strict validation still enforces assignee for ‘doing’ and ‘for_review’&lt;/li&gt;
&lt;li&gt;Required fields (lane, agent, shell_pid) still mandatory&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bug #122&lt;/strong&gt;: Prevent staged files from leaking into status commits&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New &lt;code dir=&quot;auto&quot;&gt;safe_commit()&lt;/code&gt; helper explicitly stages only intended files&lt;/li&gt;
&lt;li&gt;Status commits no longer capture unrelated staged changes&lt;/li&gt;
&lt;li&gt;Preserves user’s staging area across workflow operations&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Bug #123&lt;/strong&gt;: Call lane transition before status update (atomic state)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Lane transitions now happen BEFORE internal state updates&lt;/li&gt;
&lt;li&gt;Prevents inconsistent state when operations fail mid-transition&lt;/li&gt;
&lt;li&gt;Applies to orchestrator implementation and review phases&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;All fixes include comprehensive test coverage (54+ new tests) and maintain backward compatibility.&lt;/p&gt;
&lt;h2 id=&quot;01326---2026-02-04&quot;&gt;[0.13.26] - 2026-02-04&lt;/h2&gt;
&lt;h3 id=&quot;️-refactored&quot;&gt;🛠️ Refactored&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Consolidated workflow implement workspace creation&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow implement&lt;/code&gt; now delegates workspace creation to &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; when needed&lt;/li&gt;
&lt;li&gt;Removes duplicated worktree setup in the agent command&lt;/li&gt;
&lt;li&gt;Prevents agents from creating worktrees from inside another worktree&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-31&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Clearer recovery guidance for multi-parent merge failures&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;When auto-merge fails, instructions now show concrete recovery steps&lt;/li&gt;
&lt;li&gt;Explicitly warns there is no &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow merge&lt;/code&gt; command&lt;/li&gt;
&lt;li&gt;Points agents to the correct &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent feature merge&lt;/code&gt; command&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;01325---2026-02-04&quot;&gt;[0.13.25] - 2026-02-04&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-32&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; not bumping version when no migrations needed&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;When &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; found no applicable migrations, it returned early without updating the version in &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;This left the project stuck at its old version (e.g., 0.13.21) even though the CLI was newer (0.13.24)&lt;/li&gt;
&lt;li&gt;The dashboard then blocked with a version mismatch error&lt;/li&gt;
&lt;li&gt;Fixed both &lt;code dir=&quot;auto&quot;&gt;upgrade.py&lt;/code&gt; (CLI command path) and &lt;code dir=&quot;auto&quot;&gt;runner.py&lt;/code&gt; (programmatic path) to stamp the version even when no migrations are needed&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;01324---2026-02-04&quot;&gt;[0.13.24] - 2026-02-04&lt;/h2&gt;
&lt;h3 id=&quot;-improved-2&quot;&gt;🔧 Improved&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Review workflow shows git context for reviewers&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow review&lt;/code&gt; now displays the WP’s branch name, base branch, and commit count&lt;/li&gt;
&lt;li&gt;Reviewers see exactly which commits belong to the WP vs inherited history&lt;/li&gt;
&lt;li&gt;Provides ready-to-use &lt;code dir=&quot;auto&quot;&gt;git log &amp;#x3C;base&gt;..HEAD&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;git diff &amp;#x3C;base&gt;..HEAD&lt;/code&gt; commands&lt;/li&gt;
&lt;li&gt;base branch auto-detected from WP dependencies (tries dependency branches first, then main/2.x)&lt;/li&gt;
&lt;li&gt;Prevents reviewers from accidentally diffing against the wrong base (e.g., &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;2.x&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;01320---2026-01-30&quot;&gt;[0.13.20] - 2026-01-30&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-33&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Merged Single-Parent Dependency Workflow Gap&lt;/strong&gt; (ADR-18):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; failing when single-parent dependency has been merged to target branch&lt;/li&gt;
&lt;li&gt;Issue: WP01 merged to 2.x → WP02 can’t implement (looks for non-existent WP01 workspace branch)&lt;/li&gt;
&lt;li&gt;Root cause: Implement command didn’t distinguish between in-progress vs merged dependencies&lt;/li&gt;
&lt;li&gt;Solution: Auto-detect when dependency lane is “done” and branch from target branch instead&lt;/li&gt;
&lt;li&gt;Behavior:
&lt;ul&gt;
&lt;li&gt;If &lt;code dir=&quot;auto&quot;&gt;base_wp.lane == &quot;done&quot;&lt;/code&gt;: Branch from target branch (e.g., 2.x) - merged work already there&lt;/li&gt;
&lt;li&gt;If &lt;code dir=&quot;auto&quot;&gt;base_wp.lane != &quot;done&quot;&lt;/code&gt;: Branch from workspace branch (e.g., 025-feature-WP01) - work in progress&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Eliminates need for manual frontmatter editing (remove dependencies, update base_branch)&lt;/li&gt;
&lt;li&gt;Complements ADR-15 (multi-parent all-done suggestion) for single-parent case&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Critical fix for normal workspace-per-WP workflow where dependencies complete before dependents start&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Technical Story&lt;/strong&gt;: Feature 025-cli-event-log-integration WP02/WP08 blocked on merged WP01&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0137---2026-01-27&quot;&gt;[0.13.7] - 2026-01-27&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-34&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Activity Log Parser Failing on Hyphenated Agent Names&lt;/strong&gt; (&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/pull/111&quot;&gt;#111&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;activity_entries()&lt;/code&gt; regex in &lt;code dir=&quot;auto&quot;&gt;tasks_support.py&lt;/code&gt; to handle hyphenated agent names&lt;/li&gt;
&lt;li&gt;Parser was using &lt;code dir=&quot;auto&quot;&gt;[^–-]+?&lt;/code&gt; pattern which treated hyphens as field separators&lt;/li&gt;
&lt;li&gt;Agent names like &lt;code dir=&quot;auto&quot;&gt;cursor-agent&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;claude-reviewer&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;cursor-reviewer&lt;/code&gt; now parse correctly&lt;/li&gt;
&lt;li&gt;Acceptance validation no longer fails with “Activity Log missing entry for lane=done” for hyphenated agents&lt;/li&gt;
&lt;li&gt;Changed pattern to &lt;code dir=&quot;auto&quot;&gt;\S+(?:\s+\S+)*?&lt;/code&gt; (matches non-whitespace), aligning with &lt;code dir=&quot;auto&quot;&gt;task_helpers.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Added comprehensive test suite with 11 test cases covering hyphenated names, backward compatibility, and edge cases&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Contributors&lt;/strong&gt;: Rodrigo D. L. (bruj0)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Workflow Completion Instructions Missing Git Commit Step&lt;/strong&gt; (&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/pull/104&quot;&gt;#104&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed agents not committing implementation files before marking tasks done&lt;/li&gt;
&lt;li&gt;Issue caused cascading failures where dependent work packages started from empty branches
&lt;ul&gt;
&lt;li&gt;WP02 worktree had HTML + CSS ✅&lt;/li&gt;
&lt;li&gt;WP03 worktree had HTML only (missing WP02’s CSS) ❌&lt;/li&gt;
&lt;li&gt;WP04 worktree had HTML only (missing CSS and JS from WP02 and WP03) ❌&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Root cause: “WHEN YOU’RE DONE” instructions in &lt;code dir=&quot;auto&quot;&gt;workflow implement&lt;/code&gt; command didn’t include git commit step&lt;/li&gt;
&lt;li&gt;Fix: Added explicit git commit instruction as step 1 in completion checklist&lt;/li&gt;
&lt;li&gt;Updated both in-prompt instructions (shown twice) and terminal output summary&lt;/li&gt;
&lt;li&gt;Added warning: “The move-task command will FAIL if you have uncommitted changes! Commit all implementation files BEFORE moving to for_review. Dependent work packages need your committed changes.”&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Critical fix for multi-agent parallel development workflows using workspace-per-WP model (v0.11.0+)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Contributors&lt;/strong&gt;: Jerome Lacube&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Dashboard Command Template Generating Python Code Instead of Running CLI&lt;/strong&gt; (&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/94&quot;&gt;#94&lt;/a&gt;, &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/pull/99&quot;&gt;#99&lt;/a&gt;):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.dashboard&lt;/code&gt; command template to use &lt;code dir=&quot;auto&quot;&gt;spec-kitty dashboard&lt;/code&gt; CLI command&lt;/li&gt;
&lt;li&gt;Removed outdated Python code that manually checked dashboard status and opened browsers&lt;/li&gt;
&lt;li&gt;Dashboard now properly:
&lt;ul&gt;
&lt;li&gt;Starts automatically if not running&lt;/li&gt;
&lt;li&gt;Opens in default browser&lt;/li&gt;
&lt;li&gt;Handles worktree detection automatically&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Updated all three dashboard template files:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/missions/software-dev/command-templates/dashboard.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/software-dev/command-templates/dashboard.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/templates/command-templates/dashboard.md&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Reduced template code from ~264 lines to ~47 lines&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Contributors&lt;/strong&gt;: Jerome Lacube&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0136---2026-01-27&quot;&gt;[0.13.6] - 2026-01-27&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-35&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Critical JSON Mode Corruption Fix&lt;/strong&gt; (Release Blocker):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed JSON output corruption in &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement --json&lt;/code&gt; mode (GitHub Issue #72 follow-up)
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bug&lt;/strong&gt;: Warning messages from empty branch detection were written to stdout, corrupting JSON output&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Automated workflows using &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt; flag would fail with JSON parse errors&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fix&lt;/strong&gt;: Changed warning messages to use &lt;code dir=&quot;auto&quot;&gt;file=sys.stderr&lt;/code&gt; to separate warnings from JSON output&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/multi_parent_merge.py:142-144&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Tests&lt;/strong&gt;: Updated 5 tests in &lt;code dir=&quot;auto&quot;&gt;test_multi_parent_merge_empty_branches.py&lt;/code&gt; to check stderr instead of stdout&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Missing Migration Fix&lt;/strong&gt; (Existing Users Affected):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed missing migration for commit workflow section (GitHub Issue #72 follow-up)
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bug&lt;/strong&gt;: New projects got commit workflow section in implement.md, but existing projects didn’t after upgrade&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Existing users remained vulnerable to agents forgetting to commit work&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fix&lt;/strong&gt;: Created migration &lt;code dir=&quot;auto&quot;&gt;m_0_13_5_add_commit_workflow_to_templates.py&lt;/code&gt; to update all agent templates&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Coverage&lt;/strong&gt;: Updates both software-dev and documentation mission templates for all 12 agents&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration&lt;/strong&gt;: Automatically runs on &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; for projects missing commit workflow&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Subprocess Error Handling&lt;/strong&gt; (Defensive Programming):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added timeout and error handling to multi-parent merge git commands
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bug&lt;/strong&gt;: Git commands in empty branch detection lacked timeout parameters and try/except blocks&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Function could hang forever or crash on git errors (corrupted repo, permission issues)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fix&lt;/strong&gt;: Added 10-second timeouts and exception handling to all git subprocess calls&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/multi_parent_merge.py:117-144&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Errors handled&lt;/strong&gt;: TimeoutExpired (&gt;10s git commands), general exceptions with warning&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-41&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Git commit validation for “done” status transitions - prevents completing WPs with uncommitted changes&lt;/li&gt;
&lt;li&gt;Empty branch detection in merge-base creation - warns when dependencies have no commits&lt;/li&gt;
&lt;li&gt;Git commit workflow section in documentation mission template (consistency with software-dev/research)&lt;/li&gt;
&lt;li&gt;Comprehensive troubleshooting guide for empty branch recovery in the legacy workspace-model documentation&lt;/li&gt;
&lt;li&gt;Migration to add commit workflow section to existing projects (&lt;code dir=&quot;auto&quot;&gt;m_0_13_5_add_commit_workflow_to_templates.py&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-41&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;move-task --to done&lt;/code&gt; now validates git status (same checks as “for_review”)&lt;/li&gt;
&lt;li&gt;Use &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; flag to bypass validation (not recommended)&lt;/li&gt;
&lt;li&gt;Warning messages in multi-parent merge now output to stderr instead of stdout (preserves JSON output integrity)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-non-critical&quot;&gt;Fixed (Non-Critical)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;WP agents can no longer mark tasks as “done” without committing implementation files&lt;/li&gt;
&lt;li&gt;Multi-parent merge-bases no longer silently accept empty dependency branches&lt;/li&gt;
&lt;li&gt;Documentation mission now instructs agents to commit work before review&lt;/li&gt;
&lt;li&gt;Stale WP detection now correctly detects default branch name (main/master/develop) instead of hardcoding “main”
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bug&lt;/strong&gt;: Fresh worktrees incorrectly flagged as stale when repository used non-standard default branch&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Root Cause&lt;/strong&gt;: Code hardcoded “main” as default branch; when &lt;code dir=&quot;auto&quot;&gt;git merge-base HEAD main&lt;/code&gt; failed, it fell through to using parent branch’s old commit timestamp&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fix&lt;/strong&gt;: Added &lt;code dir=&quot;auto&quot;&gt;get_default_branch()&lt;/code&gt; helper to dynamically detect default branch via origin HEAD or local branch existence&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Prevents false staleness warnings for fresh worktrees in repos using “master”, “develop”, or other default branches&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0135---2026-01-26&quot;&gt;[0.13.5] - 2026-01-26&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-36&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Fixed /spec-kitty.clarify Command Template&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed broken placeholder in clarify template that prevented agents from running clarification workflow
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bug&lt;/strong&gt;: Template contained &lt;code dir=&quot;auto&quot;&gt;(Missing script command for sh)&lt;/code&gt; placeholder instead of actual command&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Agents couldn’t get feature context, invented non-existent commands like &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent feature get-active --json&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fix&lt;/strong&gt;: Replaced manual detection logic with &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent feature check-prerequisites --json --paths-only&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Consistency&lt;/strong&gt;: Now matches pattern used in specify.md, plan.md, and tasks.md templates&lt;/li&gt;
&lt;li&gt;Migration &lt;code dir=&quot;auto&quot;&gt;m_0_13_5_fix_clarify_template.py&lt;/code&gt; automatically updates all 12 agent directories on upgrade&lt;/li&gt;
&lt;li&gt;Source template: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/software-dev/command-templates/clarify.md&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Testing&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added comprehensive test suite with 34 tests covering all scenarios
&lt;ul&gt;
&lt;li&gt;Parametrized tests for all 12 agents (claude, copilot, gemini, cursor, qwen, opencode, windsurf, codex, kilocode, auggie, roo, q)&lt;/li&gt;
&lt;li&gt;Tests for detection, application, agent config respect, idempotency, dry-run&lt;/li&gt;
&lt;li&gt;Template content validation (ensures no broken placeholders, matches tasks.md pattern)&lt;/li&gt;
&lt;li&gt;End-to-end integration test verifying migration actually runs and fixes templates&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0134---2026-01-26&quot;&gt;[0.13.4] - 2026-01-26&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-37&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Critical Dependency Validation Fix&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow implement&lt;/code&gt; not validating WP dependencies before creating workspaces
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Bug&lt;/strong&gt;: WP with single dependency could create workspace without &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; flag&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Workspace branched from main instead of dependency branch (silent correctness bug)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Fix&lt;/strong&gt;: Added shared validation utility that errors when single dependency but no &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; provided&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Example&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;WP06&lt;/code&gt; depends on &lt;code dir=&quot;auto&quot;&gt;WP04&lt;/code&gt; → command now errors and suggests &lt;code dir=&quot;auto&quot;&gt;--base WP04&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Created &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/implement_validation.py&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;validate_and_resolve_base()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Agent commands now delegate to top-level commands (no more legacy script calls)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Fixed Broken Agent Commands&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent feature accept&lt;/code&gt; calling non-existent &lt;code dir=&quot;auto&quot;&gt;scripts/tasks/tasks_cli.py&lt;/code&gt;
&lt;ul&gt;
&lt;li&gt;Now delegates to top-level &lt;code dir=&quot;auto&quot;&gt;accept()&lt;/code&gt; command&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent feature merge&lt;/code&gt; calling non-existent &lt;code dir=&quot;auto&quot;&gt;scripts/tasks/tasks_cli.py&lt;/code&gt;
&lt;ul&gt;
&lt;li&gt;Now delegates to top-level &lt;code dir=&quot;auto&quot;&gt;merge()&lt;/code&gt; command&lt;/li&gt;
&lt;li&gt;Parameter mapping: &lt;code dir=&quot;auto&quot;&gt;keep_branch&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;delete_branch&lt;/code&gt; (inverted logic)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Critical Merge Workflow Fix&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed merge failing when main branch lacks upstream tracking (Issue reported post-0.13.2 release)
&lt;ul&gt;
&lt;li&gt;0.13.2 only checked if remote EXISTS, but not if branch TRACKS it&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;has_tracking_branch()&lt;/code&gt; function to check upstream tracking&lt;/li&gt;
&lt;li&gt;Merge now skips pull if: (1) no remote OR (2) no upstream tracking&lt;/li&gt;
&lt;li&gt;Affects users with local-only repos or repos where main doesn’t track origin/main&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Testing &amp;#x26; Prevention&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added 22 new tests for dependency validation and agent command wrappers
&lt;ul&gt;
&lt;li&gt;Unit tests: &lt;code dir=&quot;auto&quot;&gt;test_implement_validation.py&lt;/code&gt; (11 tests)&lt;/li&gt;
&lt;li&gt;Integration tests: &lt;code dir=&quot;auto&quot;&gt;test_agent_command_wrappers.py&lt;/code&gt; (11 tests)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;TestMigrationRegistryCompleteness&lt;/code&gt; test (prevents 0.13.2-style release blocker)
&lt;ul&gt;
&lt;li&gt;Verifies all &lt;code dir=&quot;auto&quot;&gt;m_*.py&lt;/code&gt; migration files are imported in &lt;code dir=&quot;auto&quot;&gt;__init__.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Prevents silent bugs where migrations exist but never run&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added integration tests for merge with untracked branches&lt;/li&gt;
&lt;li&gt;Added unit tests for &lt;code dir=&quot;auto&quot;&gt;has_tracking_branch()&lt;/code&gt; function&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Documentation&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/agent/README.md&lt;/code&gt; (wrapper pattern documentation)
&lt;ul&gt;
&lt;li&gt;Dependency validation best practices&lt;/li&gt;
&lt;li&gt;Parameter mapping guidelines&lt;/li&gt;
&lt;li&gt;Common pitfalls and examples&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Updated RELEASE_CHECKLIST.md with mandatory migration registry verification&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0132---2026-01-26&quot;&gt;[0.13.2] - 2026-01-26&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-38&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Critical Windows Compatibility Issues&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed UTF-8 encoding errors causing Windows crashes (Issue #101)
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;encoding=&apos;utf-8&apos;&lt;/code&gt; to all &lt;code dir=&quot;auto&quot;&gt;write_text()&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;read_text()&lt;/code&gt; calls&lt;/li&gt;
&lt;li&gt;Affected files: feature.py, worktree.py, agent_context.py, doc_generators.py, gap_analysis.py&lt;/li&gt;
&lt;li&gt;Completes PR #100 which missed several locations&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Fixed hardcoded &lt;code dir=&quot;auto&quot;&gt;python3&lt;/code&gt; breaking Windows installations (Issue #105)
&lt;ul&gt;
&lt;li&gt;Replaced with &lt;code dir=&quot;auto&quot;&gt;sys.executable&lt;/code&gt; in Python code (feature.py)&lt;/li&gt;
&lt;li&gt;Added dynamic Python detection in git hooks (tries python3, falls back to python)&lt;/li&gt;
&lt;li&gt;Windows users no longer need to create python3 hardlinks/aliases&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Workflow Improvements&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; parameter to &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow implement&lt;/code&gt; (Issue #96)
&lt;ul&gt;
&lt;li&gt;Enables agents to create dependent WP worktrees via workflow command&lt;/li&gt;
&lt;li&gt;Provides feature parity with top-level &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement&lt;/code&gt; command&lt;/li&gt;
&lt;li&gt;Example: &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow implement WP02 --base WP01 --agent claude&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Template and Documentation Fixes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed broken &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.clarify&lt;/code&gt; skill (Issue #106)
&lt;ul&gt;
&lt;li&gt;Removed unresolved &lt;code dir=&quot;auto&quot;&gt;{SCRIPT}&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;{ARGS}&lt;/code&gt; placeholders&lt;/li&gt;
&lt;li&gt;Replaced with auto-detection instructions for feature paths&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Fixed outdated template path references (Issue #102)
&lt;ul&gt;
&lt;li&gt;Updated 6 references from &lt;code dir=&quot;auto&quot;&gt;.kittify/templates/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Templates now reference correct bundled locations&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Fixed upgrade version detection for modern projects (Issue #108)
&lt;ul&gt;
&lt;li&gt;Added detection for versions 0.7.0-0.13.0&lt;/li&gt;
&lt;li&gt;Prevents unnecessary migrations on modern projects&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Regenerated all 12 agent constitution templates (Issue #97)
&lt;ul&gt;
&lt;li&gt;All agents now correctly suggest &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; as next step (not &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-documentation-2&quot;&gt;📚 Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added GitHub CLI authentication troubleshooting to CLAUDE.md
&lt;ul&gt;
&lt;li&gt;Documents &lt;code dir=&quot;auto&quot;&gt;unset GITHUB_TOKEN&lt;/code&gt; technique for organization repos&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Issues Closed&lt;/strong&gt;: #96, #97, #101, #102, #105, #106, #108, #103 (not a bug), #107 (not a bug)&lt;/p&gt;
&lt;h2 id=&quot;0131---2026-01-25&quot;&gt;[0.13.1] - 2026-01-25&lt;/h2&gt;
&lt;h3 id=&quot;-added-18&quot;&gt;✨ Added&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Adversarial Test Suite for 0.13.0 Release&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Distribution tests&lt;/strong&gt;: Validate PyPI user experience without SPEC_KITTY_TEMPLATE_ROOT bypass (prevents 0.10.8-style packaging failures)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Path validation security tests&lt;/strong&gt;: Test directory traversal, symlink attacks, case-sensitivity bypasses, and path injection prevention&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CSV schema attack tests&lt;/strong&gt;: Validate handling of formula injection, encoding errors, duplicate columns, and empty files&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Git state detection tests&lt;/strong&gt;: Verify accuracy of uncommitted work, merge state, and branch divergence detection&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration robustness tests&lt;/strong&gt;: Test UTF-8 encoding, idempotency, and partial/corrupted file handling&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Multi-parent merge tests&lt;/strong&gt;: Validate dependency-order merging and conflict resolution&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Context &amp;#x26; config tests&lt;/strong&gt;: Test non-interactive modes, agent configuration, and workspace validation&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Test Infrastructure&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New &lt;code dir=&quot;auto&quot;&gt;tests/adversarial/&lt;/code&gt; directory with shared fixtures and attack vectors&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;@pytest.mark.distribution&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;@pytest.mark.slow&lt;/code&gt; markers for CI optimization&lt;/li&gt;
&lt;li&gt;Session-scoped &lt;code dir=&quot;auto&quot;&gt;wheel_install&lt;/code&gt; fixture for efficient testing&lt;/li&gt;
&lt;li&gt;Platform-specific skip conditions for cross-platform compatibility&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-documentation-3&quot;&gt;📚 Documentation&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Testing&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Comprehensive adversarial test documentation in feature 024 spec&lt;/li&gt;
&lt;li&gt;Attack vector catalog with prevention strategies&lt;/li&gt;
&lt;li&gt;CI integration guidance for slow/distribution tests&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0130---2026-01-25&quot;&gt;[0.13.0] - 2026-01-25&lt;/h2&gt;
&lt;h3 id=&quot;-added-19&quot;&gt;✨ Added&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Deterministic CSV Schema Enforcement for Research Missions&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Canonical schema documentation&lt;/strong&gt;: Research CSV schemas now documented in all 12 agent implement.md templates&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Two schemas enforced&lt;/strong&gt;:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;evidence-log.csv&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;timestamp,source_type,citation,key_finding,confidence,notes&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;source-register.csv&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;source_id,citation,url,accessed_date,relevance,status&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Schema visibility&lt;/strong&gt;: Agents see schemas before editing (in “Research CSV Schemas” section with examples)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Detection migration&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;m_0_13_0_research_csv_schema_check.py&lt;/code&gt; scans existing features for schema mismatches (informational only, no auto-fix)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Template propagation&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;m_0_13_0_update_research_implement_templates.py&lt;/code&gt; updates all agent templates with schema documentation&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reusable validator&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/validators/csv_schema.py&lt;/code&gt; provides &lt;code dir=&quot;auto&quot;&gt;CSVSchemaValidation&lt;/code&gt; dataclass for exact schema matching&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Exported constants&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;EVIDENCE_REQUIRED_COLUMNS&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;SOURCE_REGISTER_REQUIRED_COLUMNS&lt;/code&gt; now importable from &lt;code dir=&quot;auto&quot;&gt;research.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ADR #8&lt;/strong&gt;: Documents architecture decision for documentation-based enforcement vs runtime enforcement/auto-migration&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Problem Solved&lt;/strong&gt;: Agents were modifying CSV schemas during implementation, creating different schemas in parallel WPs, causing merge conflicts and validation failures at review time.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Solution Approach&lt;/strong&gt;: Document schemas where agents can see them (prevention) rather than runtime enforcement or auto-migration (data loss risk).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Fully Non-Interactive Init Support&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;--non-interactive&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;--yes&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_NON_INTERACTIVE&lt;/code&gt; to disable prompts&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;--agent-strategy&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--preferred-implementer&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;--preferred-reviewer&lt;/code&gt; to expose all selection options via CLI&lt;/li&gt;
&lt;li&gt;Non-interactive mode now avoids arrow-key menus and requires &lt;code dir=&quot;auto&quot;&gt;--force&lt;/code&gt; for non-empty &lt;code dir=&quot;auto&quot;&gt;--here&lt;/code&gt; directories&lt;/li&gt;
&lt;li&gt;Updated documentation for automation and CI usage&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-39&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Windows UTF-8 Encoding Crashes&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed all &lt;code dir=&quot;auto&quot;&gt;write_text()&lt;/code&gt; calls to include &lt;code dir=&quot;auto&quot;&gt;encoding=&apos;utf-8&apos;&lt;/code&gt; parameter&lt;/li&gt;
&lt;li&gt;Affects feature creation, worktree setup, gap analysis, doc generators, agent context, and test fixtures&lt;/li&gt;
&lt;li&gt;Windows users can now create features without charmap encoding errors&lt;/li&gt;
&lt;li&gt;Fixes #101, incorporates PR #100&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Constitution Template Workflow&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed incorrect next-step suggestion after creating constitution&lt;/li&gt;
&lt;li&gt;Now correctly suggests &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Propagated fix to all 12 agent directories via migration&lt;/li&gt;
&lt;li&gt;Fixes #97 (inspired by PR #98)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Research Mission Detection&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission current&lt;/code&gt; to show feature-level missions&lt;/li&gt;
&lt;li&gt;Now auto-detects feature from current directory (kitty-specs or worktree)&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;--feature&lt;/code&gt; flag for explicit feature specification&lt;/li&gt;
&lt;li&gt;No longer always defaults to software-dev for research features&lt;/li&gt;
&lt;li&gt;Fixes #93&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-closed&quot;&gt;🎉 Closed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Agent Configuration Feature&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Closed #51 as completed (already implemented in v0.12.0)&lt;/li&gt;
&lt;li&gt;Feature: &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config add/remove/list&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-documentation-4&quot;&gt;📚 Documentation&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Release Management&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;RELEASE_CHECKLIST.md&lt;/code&gt; - Comprehensive release preparation checklist with version-specific sections for research missions, agent management, and workspace-per-WP changes&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;migration-notes-1&quot;&gt;Migration Notes&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;For users with existing research features&lt;/strong&gt;:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to trigger detection migration&lt;/li&gt;
&lt;li&gt;See informational report with schema diffs and migration tips&lt;/li&gt;
&lt;li&gt;Use LLM agent to help migrate data:
&lt;ul&gt;
&lt;li&gt;Read canonical schema in &lt;code dir=&quot;auto&quot;&gt;.claude/commands/spec-kitty.implement.md&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Create new CSV with correct headers&lt;/li&gt;
&lt;li&gt;Map old columns → new columns&lt;/li&gt;
&lt;li&gt;Replace old file and commit to main&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;For new research features (0.13.0+)&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Templates already have correct schemas&lt;/li&gt;
&lt;li&gt;Agents see schema documentation before editing&lt;/li&gt;
&lt;li&gt;Follow append-only pattern to avoid overwrites&lt;/li&gt;
&lt;li&gt;Validation passes at review&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0121---2026-01-24&quot;&gt;[0.12.1] - 2026-01-24&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-40&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;kitty-specs/ in .gitignore Blocking Feature Creation&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed issue where users with &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; in their &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; couldn’t create features&lt;/li&gt;
&lt;li&gt;Error manifested as: “Issue Detected: The spec-kitty agent feature create-feature command failed to commit because .gitignore contains kitty-specs/”&lt;/li&gt;
&lt;li&gt;New migration &lt;code dir=&quot;auto&quot;&gt;m_0_12_1_remove_kitty_specs_from_gitignore&lt;/code&gt; automatically removes blocking entries&lt;/li&gt;
&lt;li&gt;Only removes patterns that block the entire &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; directory&lt;/li&gt;
&lt;li&gt;Preserves worktree-specific patterns like &lt;code dir=&quot;auto&quot;&gt;kitty-specs/**/tasks/*.md&lt;/code&gt; (used to prevent merge conflicts)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;migration-notes-2&quot;&gt;Migration Notes&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;For users experiencing this bug:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to apply the fix automatically&lt;/li&gt;
&lt;li&gt;Or manually remove &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; from your &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The migration will detect and remove entries like:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;/kitty-specs&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;/kitty-specs/&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;It will NOT remove specific subpath patterns that are intentionally used in worktrees.&lt;/p&gt;
&lt;h2 id=&quot;0120---2026-01-23&quot;&gt;[0.12.0] - 2026-01-23&lt;/h2&gt;
&lt;h3 id=&quot;-added-20&quot;&gt;✨ Added&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Config-Driven Agent Management&lt;/strong&gt; (Feature 022):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Single source of truth&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt; now controls which agents are configured&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New CLI commands&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent config list|add|remove|status|sync&lt;/code&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;list&lt;/code&gt;: Show configured agents&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;add &amp;#x3C;agents...&gt;&lt;/code&gt;: Add agents to configuration&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;remove &amp;#x3C;agents...&gt;&lt;/code&gt;: Remove agents from configuration&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;: Show configured vs orphaned agents&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;sync&lt;/code&gt;: Synchronize filesystem with configuration&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migrations respect config&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;get_agent_dirs_for_project()&lt;/code&gt; helper only processes configured agents&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Orphan detection&lt;/strong&gt;: Identifies agent directories not in config (from manual deletions)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;ADR #6&lt;/strong&gt;: Documents architectural decision for config-driven approach&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Smarter Feature Merge with Pre-flight&lt;/strong&gt; (Feature 017):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Pre-flight validation&lt;/strong&gt;: Checks all WP worktrees for uncommitted changes, missing worktrees, and target branch divergence before any merge starts&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conflict forecasting&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt; predicts which files will conflict and classifies them as auto-resolvable (status files) or manual&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Smart merge order&lt;/strong&gt;: WPs merged in dependency order based on frontmatter &lt;code dir=&quot;auto&quot;&gt;dependencies&lt;/code&gt; field&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Status file auto-resolution&lt;/strong&gt;: Conflicts in WP prompt files (&lt;code dir=&quot;auto&quot;&gt;kitty-specs/*/tasks/*.md&lt;/code&gt;) automatically resolved by taking advanced lane status&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;merge state persistence&lt;/strong&gt;: Progress saved to &lt;code dir=&quot;auto&quot;&gt;.kittify/merge-state.json&lt;/code&gt; for recovery&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resume/abort flags&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt; continues interrupted merges, &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; clears state and starts fresh&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Auto-cleanup&lt;/strong&gt;: Worktrees and branches removed after successful merge (configurable with &lt;code dir=&quot;auto&quot;&gt;--keep-worktree&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--keep-branch&lt;/code&gt;)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-documentation-5&quot;&gt;📚 Documentation&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Merge Preflight Documentation&lt;/strong&gt; (Feature 018):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;docs/how-to/merge-feature.md&lt;/code&gt; - Complete merge workflow guide with pre-flight, dry-run, strategies, and cleanup options&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;docs/how-to/troubleshoot-merge.md&lt;/code&gt; - Comprehensive troubleshooting guide with error reference table&lt;/li&gt;
&lt;li&gt;Updated CLAUDE.md with Merge &amp;#x26; Preflight Patterns section documenting MergeState dataclass and public API&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Agent Management Documentation Sprint&lt;/strong&gt; (Feature 023):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;docs/how-to/manage-agents.md&lt;/code&gt; - Complete guide to adding, removing, and managing AI agent integrations&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;docs/how-to/upgrade-to-0-12-0.md&lt;/code&gt; - Migration guide for config-driven agent management&lt;/li&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;docs/reference/cli-commands.md&lt;/code&gt; with comprehensive &lt;code dir=&quot;auto&quot;&gt;agent config&lt;/code&gt; subcommand documentation&lt;/li&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;docs/reference/agent-subcommands.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs/reference/configuration.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;docs/reference/supported-agents.md&lt;/code&gt; with accurate cross-references&lt;/li&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;docs/how-to/install-spec-kitty.md&lt;/code&gt; with agent configuration guidance&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-41&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Merge Resume Bug&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;merge_workspace_per_wp()&lt;/code&gt; missing &lt;code dir=&quot;auto&quot;&gt;resume_state&lt;/code&gt; parameter causing &lt;code dir=&quot;auto&quot;&gt;TypeError&lt;/code&gt; when using &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Agent Workflow Output Truncation&lt;/strong&gt; (GitHub Codex compatibility):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed workflow commands (&lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review&lt;/code&gt;) outputting 300+ lines which got truncated by agents like GitHub Codex&lt;/li&gt;
&lt;li&gt;Prompts now written to temp file with concise 15-line summary to stdout&lt;/li&gt;
&lt;li&gt;Added directive language (&lt;code dir=&quot;auto&quot;&gt;▶▶▶ NEXT STEP: Read the full prompt file now:&lt;/code&gt;) so agents automatically read the file&lt;/li&gt;
&lt;li&gt;Agents no longer miss work package requirements due to output truncation&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;False Staleness for Newly-Created Worktrees&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed stale detection flagging new worktrees as stale immediately&lt;/li&gt;
&lt;li&gt;Previously, &lt;code dir=&quot;auto&quot;&gt;git log -1&lt;/code&gt; returned parent branch’s commit time (could be hours old)&lt;/li&gt;
&lt;li&gt;Now checks if branch has commits since diverging from main&lt;/li&gt;
&lt;li&gt;Worktrees with no new commits are NOT flagged as stale (agent just started)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0111---2026-01-16&quot;&gt;[0.11.1] - 2026-01-16&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-42&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Merge Template Improvements&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added explicit preflight validation code using &lt;code dir=&quot;auto&quot;&gt;python3 -c&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;validate_worktree_location()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Added clear visual ”⛔ Location Pre-flight Check (CRITICAL)” section to prevent agents running merge from wrong location&lt;/li&gt;
&lt;li&gt;Fixed contradictory instructions in software-dev mission merge template (was incorrectly saying “run from main”)&lt;/li&gt;
&lt;li&gt;Fixed empty Python code block in research mission merge template that confused agents&lt;/li&gt;
&lt;li&gt;Added workspace-per-WP model (0.11.0+) documentation vs legacy pattern in worktree strategy section&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Documentation Accuracy&lt;/strong&gt; (Feature 014):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Rewrote &lt;code dir=&quot;auto&quot;&gt;multi-agent-orchestration.md&lt;/code&gt; for the 0.11.0+ isolated-WP worktree model:
&lt;ul&gt;
&lt;li&gt;Planning happens in main repo (not worktrees)&lt;/li&gt;
&lt;li&gt;Each WP gets its own worktree (not shared)&lt;/li&gt;
&lt;li&gt;Removed references to non-existent scripts&lt;/li&gt;
&lt;li&gt;Updated lane tracking to frontmatter (not directories)&lt;/li&gt;
&lt;li&gt;Added parallelization patterns and status monitoring&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Fixed the legacy isolated-worktree guide merge command syntax (runs from worktree without feature argument)&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;documentation-mission.md&lt;/code&gt; broken source links&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;reference/README.md&lt;/code&gt; - replaced outdated “Planned Content” with actual content links&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;kanban-workflow.md&lt;/code&gt; - clarified &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.accept&lt;/code&gt; works on features, not individual WPs&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added-21&quot;&gt;📚 Added&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Comprehensive End-User Documentation&lt;/strong&gt; (Feature 014):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Complete Divio 4-type documentation suite:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Tutorials&lt;/strong&gt;: Getting Started, Your First Feature, Claude Code Integration, Claude Code Workflow, Multi-Agent Workflow, Missions Overview&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;How-To Guides&lt;/strong&gt;: 14 task-oriented guides covering installation, specifications, planning, implementation, review, dependencies, parallel development, dashboard usage, and migration&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reference&lt;/strong&gt;: CLI Commands, Slash Commands, Agent Subcommands, Configuration, Environment Variables, File Structure, Missions, Supported Agents&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Explanations&lt;/strong&gt;: Spec-Driven Development, Divio Documentation, legacy isolated worktree model, Git Worktrees, Mission System, Kanban Workflow, AI Agent Architecture, Documentation Mission, Multi-Agent Orchestration&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Cross-references between all documentation types&lt;/li&gt;
&lt;li&gt;DocFX-compatible structure with &lt;code dir=&quot;auto&quot;&gt;toc.yml&lt;/code&gt; navigation&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0110---2026-01-12&quot;&gt;[0.11.0] - 2026-01-12&lt;/h2&gt;
&lt;h3 id=&quot;-breaking-changes---workspace-model-changed-feature-010&quot;&gt;🚨 BREAKING CHANGES - Workspace Model Changed (Feature 010)&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Old (0.10.x)&lt;/strong&gt;: One worktree per feature&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; created &lt;code dir=&quot;auto&quot;&gt;.worktrees/###-feature/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;All WPs worked in same worktree&lt;/li&gt;
&lt;li&gt;Sequential development (one agent at a time)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;New (0.11.0)&lt;/strong&gt;: One worktree per work package&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Planning commands (specify, plan, tasks) work in main repository (NO worktree created)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty implement WP##&lt;/code&gt; creates &lt;code dir=&quot;auto&quot;&gt;.worktrees/###-feature-WP##/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Each WP has isolated worktree with dedicated branch&lt;/li&gt;
&lt;li&gt;Enables parallel multi-agent development&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-migration-required&quot;&gt;⚠️ Migration Required&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;You MUST complete or delete all in-progress features before upgrading to 0.11.0.&lt;/strong&gt;&lt;/p&gt;
&lt;p&gt;See docs/upgrading-to-0-11-0.md for complete migration guide.&lt;/p&gt;
&lt;h3 id=&quot;-security-important---feature-011&quot;&gt;🔒 Security (IMPORTANT) - Feature 011&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Comprehensive adversarial review framework&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Expanded review template from 3 bullets (109 lines) to 12 scrutiny categories (505 lines)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Security scrutiny now mandatory&lt;/strong&gt;: 10 detailed security subsections&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mandatory verification&lt;/strong&gt;: 7 security grep commands must be run on EVERY review&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automatic rejection&lt;/strong&gt; if any security check fails&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: All future features will have security-first reviews&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added-22&quot;&gt;✨ Added&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Legacy isolated-WP worktree features (010)&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;New command&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty implement WP## [--base WPXX]&lt;/code&gt; - Create workspace for work package
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--base&lt;/code&gt; flag branches from another WP’s branch (for dependencies)&lt;/li&gt;
&lt;li&gt;Automatically moves WP from &lt;code dir=&quot;auto&quot;&gt;planned&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;doing&lt;/code&gt; lane&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New command&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent feature finalize-tasks&lt;/code&gt; - Finalize WP generation
&lt;ul&gt;
&lt;li&gt;Parses dependencies from tasks.md&lt;/li&gt;
&lt;li&gt;Generates &lt;code dir=&quot;auto&quot;&gt;dependencies: []&lt;/code&gt; field in WP frontmatter&lt;/li&gt;
&lt;li&gt;Validates dependency graph (cycle detection, invalid references)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dependency tracking&lt;/strong&gt;: WP frontmatter includes &lt;code dir=&quot;auto&quot;&gt;dependencies: []&lt;/code&gt; field&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dependency graph utilities&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/core/dependency_graph.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review warnings&lt;/strong&gt;: Alert when dependent WPs need rebase&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Constitution Features (011)&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Interactive constitution command&lt;/strong&gt; (Phase-based discovery)
&lt;ul&gt;
&lt;li&gt;4-phase discovery workflow (Technical, Quality, Tribal Knowledge, Governance)&lt;/li&gt;
&lt;li&gt;Two paths: Minimal (Phase 1 only) or Comprehensive (all phases)&lt;/li&gt;
&lt;li&gt;Skip options for each phase&lt;/li&gt;
&lt;li&gt;Truly optional - all commands work without constitution&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-refactored---feature-011&quot;&gt;♻️ Refactored - Feature 011&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Template source relocation&lt;/strong&gt; (Safe dogfooding - Critical)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moved ALL template sources from &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Updated template manager to load from package resources&lt;/li&gt;
&lt;li&gt;Removed &lt;code dir=&quot;auto&quot;&gt;.kittify/*&lt;/code&gt; force-includes from &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Developers can now safely dogfood without packaging risk&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission-specific constitutions removed&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Single project-level constitution model (&lt;code dir=&quot;auto&quot;&gt;.kittify/memory/constitution.md&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Migration removes mission constitutions from user projects&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed---feature-011&quot;&gt;🐛 Fixed - Feature 011&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Windows dashboard ERR_EMPTY_RESPONSE&lt;/strong&gt; (#71)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Replaced POSIX-only signal handling with cross-platform psutil&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;psutil&gt;=5.9.0&lt;/code&gt; dependency&lt;/li&gt;
&lt;li&gt;Dashboard now works on Windows 10/11&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upgrade migration failures&lt;/strong&gt; (#70)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed multiple migrations to handle missing files gracefully&lt;/li&gt;
&lt;li&gt;All migrations now idempotent&lt;/li&gt;
&lt;li&gt;Upgrade path from 0.6.4 → 0.10.12 completes without intervention&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed---feature-012&quot;&gt;🐛 Fixed - Feature 012&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.status&lt;/code&gt; template instructed agents to run Python code&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;AI agents cannot execute arbitrary Python - they use CLI tools&lt;/li&gt;
&lt;li&gt;Updated template to use CLI command as primary method&lt;/li&gt;
&lt;li&gt;Python API now documented as alternative for Jupyter/scripts&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-documentation---feature-010&quot;&gt;📖 Documentation - Feature 010&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;New docs&lt;/strong&gt;: legacy isolated-worktree workflow guide with examples&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;New docs&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;docs/upgrading-to-0-11-0.md&lt;/code&gt; - Migration instructions&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-why-these-changes&quot;&gt;🎯 Why These Changes?&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;Feature 010 (Workspace-per-WP)&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Enables parallel multi-agent development&lt;/li&gt;
&lt;li&gt;Better isolation per work package&lt;/li&gt;
&lt;li&gt;Explicit dependencies with validation&lt;/li&gt;
&lt;li&gt;Scalability for large features (10+ WPs)&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Feature 011 (Constitution &amp;#x26; Packaging Safety)&lt;/strong&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Safe dogfooding (no packaging contamination)&lt;/li&gt;
&lt;li&gt;Cross-platform dashboard support&lt;/li&gt;
&lt;li&gt;Optional, interactive constitution setup&lt;/li&gt;
&lt;li&gt;Smooth upgrade migrations&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;01013---2026-01-12&quot;&gt;[0.10.13] - 2026-01-12&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-43&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CRITICAL: Missing migration in PyPI v0.10.12 package&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Migration &lt;code dir=&quot;auto&quot;&gt;m_0_10_12_constitution_cleanup.py&lt;/code&gt; was missing from PyPI package uploaded on 2026-01-07&lt;/li&gt;
&lt;li&gt;File existed in source repository but was not included in distributed wheel&lt;/li&gt;
&lt;li&gt;Caused constitution cleanup to not run during upgrades from v0.10.11&lt;/li&gt;
&lt;li&gt;v0.10.13 includes the missing migration file&lt;/li&gt;
&lt;li&gt;Users who installed v0.10.12 should run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; again after upgrading to v0.10.13&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Root cause&lt;/strong&gt;: PyPI package was built before migration file was committed to repository&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prevention&lt;/strong&gt;: Added migration file count verification to release workflow&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-improved&quot;&gt;♻️ Improved&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Release workflow hardening&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Added verification step to count migration files in built wheel&lt;/li&gt;
&lt;li&gt;Release now fails if migration count doesn’t match source repository&lt;/li&gt;
&lt;li&gt;Prevents future packaging bugs where files are missing from distribution&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-migration-for-v01012-users&quot;&gt;📋 Migration for v0.10.12 Users&lt;/h3&gt;
&lt;p&gt;If you installed v0.10.12 from PyPI and upgraded from v0.10.11:&lt;/p&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:#82AAFF;--1:#3B61B0&quot;&gt;pip&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:#82AAFF;--1:#3B61B0&quot;&gt;--upgrade&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;/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;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt;  &lt;/span&gt;&lt;span style=&quot;--0:#919F9F;--1:#5F636F&quot;&gt;# Run again to apply missing migration 0.10.12&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;The migration will remove mission-specific constitution directories:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/missions/software-dev/constitution/&lt;/code&gt; → removed&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/missions/research/constitution/&lt;/code&gt; → removed&lt;/li&gt;
&lt;li&gt;Single project-level constitution: &lt;code dir=&quot;auto&quot;&gt;.kittify/memory/constitution.md&lt;/code&gt; (kept)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;01012---2026-01-12&quot;&gt;[0.10.12] - 2026-01-12&lt;/h2&gt;
&lt;h3 id=&quot;-security-important&quot;&gt;🔒 Security (IMPORTANT)&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Comprehensive adversarial review framework&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Expanded review template from 3 bullets (109 lines) to 12 scrutiny categories (505 lines)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Security scrutiny now mandatory&lt;/strong&gt;: 10 detailed security subsections&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mandatory verification&lt;/strong&gt;: 7 security grep commands must be run on EVERY review&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Automatic rejection&lt;/strong&gt; if any security check fails&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: All future features will have security-first reviews&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Rationale&lt;/strong&gt;: Prevents systematic quality issues (TODOs in prod, mocked implementations, security vulnerabilities)&lt;/li&gt;
&lt;li&gt;See spec footnote and commit &lt;code dir=&quot;auto&quot;&gt;61d7d01&lt;/code&gt; for complete rationale&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-44&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Windows dashboard ERR_EMPTY_RESPONSE&lt;/strong&gt; (#71)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Replaced POSIX-only signal handling with cross-platform psutil library&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;signal.SIGKILL&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;signal.SIGTERM&lt;/code&gt; don’t exist on Windows&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;psutil&gt;=5.9.0&lt;/code&gt; dependency for cross-platform process management&lt;/li&gt;
&lt;li&gt;Refactored &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/dashboard/lifecycle.py&lt;/code&gt;:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;os.kill(pid, 0)&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;psutil.Process(pid).is_running()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;signal.SIGKILL&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;psutil.Process(pid).kill()&lt;/code&gt; (6 locations)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;signal.SIGTERM&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;psutil.Process(pid).terminate()&lt;/code&gt; with timeout&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;Added proper exception handling (NoSuchProcess, AccessDenied, TimeoutExpired)&lt;/li&gt;
&lt;li&gt;Dashboard now starts, serves HTML, and stops cleanly on Windows 10/11&lt;/li&gt;
&lt;li&gt;All 41 dashboard tests passing&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upgrade migration failures&lt;/strong&gt; (#70)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;m_0_7_3_update_scripts.py&lt;/code&gt; to handle missing bash scripts gracefully&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;m_0_10_6_workflow_simplification.py&lt;/code&gt; to copy templates before validation&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;m_0_10_2_update_slash_commands.py&lt;/code&gt; to explicitly remove legacy .toml files&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;m_0_10_0_python_only.py&lt;/code&gt; to explicitly remove &lt;code dir=&quot;auto&quot;&gt;.kittify/scripts/tasks/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Created &lt;code dir=&quot;auto&quot;&gt;m_0_10_12_constitution_cleanup.py&lt;/code&gt; to remove mission constitutions&lt;/li&gt;
&lt;li&gt;All migrations now idempotent (safe to run multiple times)&lt;/li&gt;
&lt;li&gt;Upgrade path from 0.6.4 → 0.10.12 now completes without manual intervention&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upgrade migration parameter mismatch&lt;/strong&gt; (#68 follow-up)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;m_0_10_9_repair_templates.py&lt;/code&gt; migration calling &lt;code dir=&quot;auto&quot;&gt;generate_agent_assets()&lt;/code&gt; with wrong parameter name&lt;/li&gt;
&lt;li&gt;Changed &lt;code dir=&quot;auto&quot;&gt;ai=ai_config&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;agent_key=ai_config&lt;/code&gt; to match function signature&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;️-refactored-1&quot;&gt;♻️ Refactored&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Template source relocation&lt;/strong&gt; (Safe dogfooding - Critical)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moved ALL template sources from &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Templates: &lt;code dir=&quot;auto&quot;&gt;.kittify/templates/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/templates/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Missions: &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Scripts: &lt;code dir=&quot;auto&quot;&gt;.kittify/scripts/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/scripts/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/template/manager.py&lt;/code&gt; to load from &lt;code dir=&quot;auto&quot;&gt;src/&lt;/code&gt; not &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Removed ALL &lt;code dir=&quot;auto&quot;&gt;.kittify/*&lt;/code&gt; force-includes from &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Spec-kitty developers can now safely dogfood spec-kitty without risk of packaging their filled-in constitutions&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Verification&lt;/strong&gt;: Building wheel produces ZERO &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;memory/constitution.md&lt;/code&gt; entries&lt;/li&gt;
&lt;li&gt;Package now only contains &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/&lt;/code&gt; (proper Python packaging)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission-specific constitutions removed&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Removed &lt;code dir=&quot;auto&quot;&gt;mission.constitution_dir&lt;/code&gt; property from &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/mission.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Removed constitution scanning from &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/manifest.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Deleted all &lt;code dir=&quot;auto&quot;&gt;missions/*/constitution/&lt;/code&gt; directories&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Single project-level constitution model (&lt;code dir=&quot;auto&quot;&gt;.kittify/memory/constitution.md&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Migration&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;m_0_10_12_constitution_cleanup.py&lt;/code&gt; removes mission constitutions from user projects&lt;/li&gt;
&lt;li&gt;Eliminates confusion about which constitution applies&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;01011---2026-01-07&quot;&gt;[0.10.11] - 2026-01-07&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-45&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Upgrade migration parameter mismatch&lt;/strong&gt; (#68 follow-up)
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;m_0_10_9_repair_templates.py&lt;/code&gt; migration calling &lt;code dir=&quot;auto&quot;&gt;generate_agent_assets()&lt;/code&gt; with wrong parameter name&lt;/li&gt;
&lt;li&gt;Changed &lt;code dir=&quot;auto&quot;&gt;ai=ai_config&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;agent_key=ai_config&lt;/code&gt; to match function signature&lt;/li&gt;
&lt;li&gt;Corrected parameter order to match function definition&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Root cause&lt;/strong&gt;: Migration was using deprecated parameter name, blocking users from upgrading to 0.10.11&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Users unable to run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to get template fixes from 0.10.11&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;01011---2026-01-07-1&quot;&gt;[0.10.11] - 2026-01-07&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-46&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Deprecated script references in mission templates&lt;/strong&gt; (#68)
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/software-dev/templates/task-prompt-template.md&lt;/code&gt; to use workflow commands instead of deprecated &lt;code dir=&quot;auto&quot;&gt;python3 .kittify/scripts/tasks/tasks_cli.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;.kittify/templates/task-prompt-template.md&lt;/code&gt; with same update&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/software-dev/command-templates/tasks.md&lt;/code&gt; to reference workflow commands&lt;/li&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;.kittify/templates/POWERSHELL_SYNTAX.md&lt;/code&gt; to document spec-kitty CLI instead of obsolete PowerShell scripts&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Root cause&lt;/strong&gt;: Migration 0.10.9 fixed agent command templates but missed mission-specific templates&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Impact&lt;/strong&gt;: Agents were executing users’ local &lt;code dir=&quot;auto&quot;&gt;cli.py&lt;/code&gt; files instead of spec-kitty CLI on Windows&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added-23&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Template compliance tests&lt;/strong&gt; - Prevent deprecated script references
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;test_no_deprecated_script_references()&lt;/code&gt; - Detects old &lt;code dir=&quot;auto&quot;&gt;.kittify/scripts/&lt;/code&gt; paths in templates&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;test_templates_use_spec_kitty_cli()&lt;/code&gt; - Ensures templates reference spec-kitty CLI commands&lt;/li&gt;
&lt;li&gt;Tests run on all mission templates and global templates&lt;/li&gt;
&lt;li&gt;Prevents regression of issue #68&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;01010---2026-01-06&quot;&gt;[0.10.10] - 2026-01-06&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-47&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Windows UTF-8 encoding error in agent commands&lt;/strong&gt; (#66)
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;&apos;charmap&apos; codec can&apos;t encode characters&lt;/code&gt; error on Windows&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent feature create-feature&lt;/code&gt; now works correctly on Windows&lt;/li&gt;
&lt;li&gt;Added UTF-8 stdout/stderr reconfiguration in main() entry point&lt;/li&gt;
&lt;li&gt;Handles Unicode characters in git output and error messages&lt;/li&gt;
&lt;li&gt;Gracefully falls back for Python &amp;#x3C; 3.7&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0109---2026-01-06&quot;&gt;[0.10.9] - 2026-01-06&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-48&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CRITICAL: Wrong templates bundled in PyPI packages&lt;/strong&gt; (#62, #63, #64)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed pyproject.toml to bundle .kittify/templates/ instead of outdated /templates/&lt;/li&gt;
&lt;li&gt;Removed outdated /templates/ directory entirely to prevent confusion&lt;/li&gt;
&lt;li&gt;All PyPI installations now receive correct Python CLI templates&lt;/li&gt;
&lt;li&gt;No more bash script references in command templates&lt;/li&gt;
&lt;li&gt;Migration 0.10.0 now handles missing templates gracefully&lt;/li&gt;
&lt;li&gt;Added package bundling validation tests to prevent regression&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Template divergence eliminated&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;10 of 13 command templates were outdated in /templates/&lt;/li&gt;
&lt;li&gt;implement.md was 199 lines longer in old location (277 vs 78 lines)&lt;/li&gt;
&lt;li&gt;Git hooks were missing (1 vs 3)&lt;/li&gt;
&lt;li&gt;claudeignore-template was missing&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;All 12 AI agent integrations fixed&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Claude Code, GitHub Copilot, Cursor, Gemini, Qwen Code, OpenCode, Windsurf,
GitHub Codex, Kilocode, Augment Code, Roo Cline, Amazon Q&lt;/li&gt;
&lt;li&gt;All agents now receive correct Python CLI slash commands&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added-24&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Repair migration (0.10.9_repair_templates)&lt;/strong&gt; - Automatically fixes broken installations&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Detects projects with broken template references&lt;/li&gt;
&lt;li&gt;Regenerates all agent slash commands from correct templates&lt;/li&gt;
&lt;li&gt;Runs automatically during &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Verifies repair was successful&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Package bundling validation tests&lt;/strong&gt; - Prevents future regressions&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Validates correct templates are bundled in sdist and wheel&lt;/li&gt;
&lt;li&gt;Checks for bash script references before release&lt;/li&gt;
&lt;li&gt;Tests importlib.resources accessibility&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-migration--upgrade-path&quot;&gt;📚 Migration &amp;#x26; Upgrade Path&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;For users with broken installations (issues #62, #63, #64):&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Upgrade spec-kitty package:&lt;/strong&gt;&lt;/p&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:#82AAFF;--1:#3B61B0&quot;&gt;pip&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:#82AAFF;--1:#3B61B0&quot;&gt;--upgrade&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;/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:#82AAFF;--1:#3B61B0&quot;&gt;--version&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;# Should show 0.10.9&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Run upgrade to apply repair migration:&lt;/strong&gt;&lt;/p&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:#C5E478;--1:#3B61B0&quot;&gt;cd&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;/path/to/your/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;This will automatically detect and fix broken templates.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Verify repair:&lt;/strong&gt;&lt;/p&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;# Check for bash script references (should return nothing)&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;grep&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#82AAFF;--1:#3B61B0&quot;&gt;-r&lt;/span&gt;&lt;span style=&quot;--0:#D6DEEB;--1:#403F53&quot;&gt; &lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&lt;/span&gt;&lt;span style=&quot;--0:#ECC48D;--1:#984E4D&quot;&gt;scripts/bash&lt;/span&gt;&lt;span style=&quot;--0:#D9F5DD;--1:#111111&quot;&gt;&quot;&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;.claude/commands/&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;For new projects:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Automatically get correct templates from package&lt;/li&gt;
&lt;li&gt;No action needed&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;For existing healthy projects:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to stay current&lt;/li&gt;
&lt;li&gt;No breaking changes&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-breaking-changes-5&quot;&gt;🔒 Breaking Changes&lt;/h3&gt;
&lt;p&gt;None - Fully backwards compatible. Existing projects will upgrade smoothly.&lt;/p&gt;
&lt;h2 id=&quot;0108---2025-12-30&quot;&gt;[0.10.8] - 2025-12-30&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-49&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Critical: Constitution not copied to worktrees&lt;/strong&gt; (#46)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Moved &lt;code dir=&quot;auto&quot;&gt;memory/&lt;/code&gt; directory from root to &lt;code dir=&quot;auto&quot;&gt;.kittify/memory/&lt;/code&gt; where code expects it&lt;/li&gt;
&lt;li&gt;Removed broken circular symlinks (&lt;code dir=&quot;auto&quot;&gt;.kittify/memory&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;../../../.kittify/memory&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;.kittify/AGENTS.md&lt;/code&gt; to be real file instead of broken symlink&lt;/li&gt;
&lt;li&gt;Fixed worktree.py symlink handling (check for symlink before trying rmtree)&lt;/li&gt;
&lt;li&gt;Added migration to automatically fix existing projects&lt;/li&gt;
&lt;li&gt;Worktrees now correctly access constitution from main repo&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Migration system&lt;/strong&gt; (v0.10.8_fix_memory_structure)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Automatically moves &lt;code dir=&quot;auto&quot;&gt;memory/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;.kittify/memory/&lt;/code&gt; in existing projects&lt;/li&gt;
&lt;li&gt;Removes broken symlinks and creates proper structure&lt;/li&gt;
&lt;li&gt;Updates worktrees to use correct paths&lt;/li&gt;
&lt;li&gt;Handles both Unix symlinks and Windows file copies&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-12&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Directory structure standardization&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;memory/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;.kittify/memory/&lt;/code&gt; (matches &lt;code dir=&quot;auto&quot;&gt;.kittify/scripts/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kittify/templates/&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/AGENTS.md&lt;/code&gt; is now a real file (not symlink)&lt;/li&gt;
&lt;li&gt;All &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; resources now follow consistent pattern&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0107---2025-12-30&quot;&gt;[0.10.7] - 2025-12-30&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-50&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Critical: Copilot initialization bug&lt;/strong&gt; (#53, fixes #61, #50)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed NameError when running &lt;code dir=&quot;auto&quot;&gt;spec-kitty init --ai copilot&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Changed &lt;code dir=&quot;auto&quot;&gt;commands_dir&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;command_templates_dir&lt;/code&gt; in asset_generator.py&lt;/li&gt;
&lt;li&gt;Unblocks all users trying to initialize projects with Copilot&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Critical: Dashboard contracts and checklists missing&lt;/strong&gt; (#59, fixes #52)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Restored contracts and checklists handlers that were lost in Nov 11 dashboard refactoring&lt;/li&gt;
&lt;li&gt;Added generic &lt;code dir=&quot;auto&quot;&gt;_handle_artifact_directory()&lt;/code&gt; helper method&lt;/li&gt;
&lt;li&gt;Both contracts and checklists now display correctly in dashboard&lt;/li&gt;
&lt;li&gt;Fixed frontend to use full filepath instead of filename only&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Critical: Windows UTF-8 encoding errors&lt;/strong&gt; (#56)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added explicit &lt;code dir=&quot;auto&quot;&gt;encoding=&apos;utf-8&apos;&lt;/code&gt; to read_text() calls&lt;/li&gt;
&lt;li&gt;Fixes dashboard diagnostics showing “undefined” on Windows&lt;/li&gt;
&lt;li&gt;Affects manifest.py and migration files&lt;/li&gt;
&lt;li&gt;Windows defaults to cp1252, causing UnicodeDecodeError with UTF-8 content&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Plan.md location validation&lt;/strong&gt; (#60)&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Improved validation messaging in plan.md template&lt;/li&gt;
&lt;li&gt;Added prominent ⚠️ STOP header for AI agents&lt;/li&gt;
&lt;li&gt;Clearer examples of correct vs wrong worktree locations&lt;/li&gt;
&lt;li&gt;Template-only change (no code modifications)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-closed-1&quot;&gt;🔄 Closed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;PR #58 - Obsolete (PowerShell scripts deleted in v0.10.0)&lt;/li&gt;
&lt;li&gt;PR #57 - Obsolete (PowerShell scripts deleted in v0.10.0)&lt;/li&gt;
&lt;li&gt;PR #49 - Superseded by #59 (better architecture)&lt;/li&gt;
&lt;li&gt;PR #43 - Obsolete (PowerShell scripts deleted in v0.10.0)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0106---2025-12-18&quot;&gt;[0.10.6] - 2025-12-18&lt;/h2&gt;
&lt;h3 id=&quot;-added-25&quot;&gt;✨ Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Workflow commands for simplified agent experience&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;New &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow implement [WP_ID]&lt;/code&gt; command&lt;/li&gt;
&lt;li&gt;New &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent workflow review [WP_ID]&lt;/code&gt; command&lt;/li&gt;
&lt;li&gt;Commands display full WP prompt directly to agents (no file navigation)&lt;/li&gt;
&lt;li&gt;Auto-detect first planned/for_review WP when no ID provided&lt;/li&gt;
&lt;li&gt;Auto-move WP to “doing” lane before displaying prompt&lt;/li&gt;
&lt;li&gt;Show “WHEN YOU’RE DONE” instructions at top of output&lt;/li&gt;
&lt;li&gt;Display source file path for easy re-reading&lt;/li&gt;
&lt;li&gt;Prevents race conditions (two agents picking same WP)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-13&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Slash command template simplification&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;implement.md: 78 lines → 11 lines (calls workflow command)&lt;/li&gt;
&lt;li&gt;review.md: 72 lines → 11 lines (calls workflow command)&lt;/li&gt;
&lt;li&gt;Templates now just run workflow commands instead of complex instructions&lt;/li&gt;
&lt;li&gt;Agents see prompts immediately without navigation confusion&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Consistent lane management&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Both implement and review workflows move WP to “doing” at start&lt;/li&gt;
&lt;li&gt;Prevents ambiguity about which lane means “actively working”&lt;/li&gt;
&lt;li&gt;Review workflow now supports auto-detect (no argument needed)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-51&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Worktree path resolution&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;_find_first_planned_wp()&lt;/code&gt; to work correctly in worktrees&lt;/li&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;_find_first_for_review_wp()&lt;/code&gt; to work correctly in worktrees&lt;/li&gt;
&lt;li&gt;Auto-detect now finds WPs in worktree’s kitty-specs/, not main repo&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Legacy subdirectory cleanup&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Migrated features 007 and 010 from old subdirectory structure to flat structure&lt;/li&gt;
&lt;li&gt;Moved 15 WP files from &lt;code dir=&quot;auto&quot;&gt;tasks/done/phase-*/&lt;/code&gt; to flat &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;All features now use proper flat structure with frontmatter-only lanes&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;094---2025-12-17&quot;&gt;[0.9.4] - 2025-12-17&lt;/h2&gt;
&lt;h3 id=&quot;-documentation--validation&quot;&gt;📚 Documentation &amp;#x26; Validation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Prevent agent-created subdirectories in tasks/&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Added explicit warnings to tasks/README.md&lt;/li&gt;
&lt;li&gt;Updated AGENTS.md with flat structure requirements&lt;/li&gt;
&lt;li&gt;Updated /spec-kitty.tasks template to forbid subdirectories&lt;/li&gt;
&lt;li&gt;Added runtime validation in check-prerequisites.sh&lt;/li&gt;
&lt;li&gt;Blocks execution if phase-&lt;em&gt;, component-&lt;/em&gt;, or any subdirectories found&lt;/li&gt;
&lt;li&gt;Clear error messages with examples of correct vs wrong paths&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This prevents Claude agents from creating organizational subdirectories like &lt;code dir=&quot;auto&quot;&gt;tasks/phase-1/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks/backend/&lt;/code&gt;, etc.&lt;/p&gt;
&lt;h2 id=&quot;093---2025-12-17&quot;&gt;[0.9.3] - 2025-12-17&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-52&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Critical symlink detection fix&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Now checks &lt;code dir=&quot;auto&quot;&gt;is_symlink()&lt;/code&gt; BEFORE &lt;code dir=&quot;auto&quot;&gt;exists()&lt;/code&gt; (exists() returns False for broken symlinks!)&lt;/li&gt;
&lt;li&gt;Properly removes both working and broken symlinks from worktrees&lt;/li&gt;
&lt;li&gt;Fixes remaining test failures in worktree cleanup migration&lt;/li&gt;
&lt;li&gt;Handles all symlink scenarios correctly&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This completes the fix for symlink removal in worktree cleanup.&lt;/p&gt;
&lt;h2 id=&quot;092---2025-12-17&quot;&gt;[0.9.2] - 2025-12-17&lt;/h2&gt;
&lt;h3 id=&quot;-fixed-53&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Symlink handling in worktree cleanup&lt;/strong&gt;
&lt;ul&gt;
&lt;li&gt;Migration now properly detects and removes symlinks to command directories&lt;/li&gt;
&lt;li&gt;Uses &lt;code dir=&quot;auto&quot;&gt;unlink()&lt;/code&gt; for symlinks instead of &lt;code dir=&quot;auto&quot;&gt;shutil.rmtree()&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Fixes “Cannot call rmtree on a symbolic link” error during upgrade&lt;/li&gt;
&lt;li&gt;Handles both symlinks and regular directories correctly&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;This fixes the upgrade failure when worktrees have symlinked agent command directories.&lt;/p&gt;
&lt;h2 id=&quot;091---2025-12-17&quot;&gt;[0.9.1] - 2025-12-17&lt;/h2&gt;
&lt;h3 id=&quot;-bug-fixes--improvements&quot;&gt;🔧 Bug Fixes &amp;#x26; Improvements&lt;/h3&gt;
&lt;p&gt;This release fixes critical issues found in v0.9.0 and adds version checking to prevent compatibility problems.&lt;/p&gt;
&lt;h3 id=&quot;-added-26&quot;&gt;🆕 Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Version compatibility checking&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;CLI now checks for version mismatches between installed spec-kitty-cli and project version&lt;/li&gt;
&lt;li&gt;Hard error with explicit instructions when versions don’t match&lt;/li&gt;
&lt;li&gt;Special critical warning for v0.9.0+ upgrade explaining breaking changes&lt;/li&gt;
&lt;li&gt;Shows detailed before/after directory structure comparison&lt;/li&gt;
&lt;li&gt;Version checks in all CLI commands and bash scripts&lt;/li&gt;
&lt;li&gt;Graceful handling of legacy projects without metadata&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Programmatic frontmatter management&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New &lt;code dir=&quot;auto&quot;&gt;specify_cli.frontmatter&lt;/code&gt; module for consistent YAML operations&lt;/li&gt;
&lt;li&gt;Uses ruamel.yaml for absolute formatting consistency&lt;/li&gt;
&lt;li&gt;No more manual YAML editing by LLMs or scripts&lt;/li&gt;
&lt;li&gt;Prevents quoted vs unquoted value inconsistencies&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-fixed-54&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Migration improvements&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;v0.9.0 migration now finds ALL markdown files (not just WP*.md)&lt;/li&gt;
&lt;li&gt;Detects and removes empty lane subdirectories&lt;/li&gt;
&lt;li&gt;Uses shutil.rmtree() for robust directory removal&lt;/li&gt;
&lt;li&gt;Better detection of legacy format&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Complete lane migration (v0.9.1)&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Migrates files missed by v0.9.0 (phase-&lt;em&gt;.md, task-&lt;/em&gt;.md, etc.)&lt;/li&gt;
&lt;li&gt;Removes ALL agent command directories from worktrees (.codex/prompts/, .gemini/commands/, etc.)&lt;/li&gt;
&lt;li&gt;Removes .kittify/scripts/ from worktrees (inherit from main repo)&lt;/li&gt;
&lt;li&gt;Normalizes all frontmatter to consistent YAML format&lt;/li&gt;
&lt;li&gt;Fixes issue where worktrees had old command templates referencing deprecated scripts&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Flat structure in new features&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Fixed create-new-feature.sh to create flat tasks/ directory (not subdirectories)&lt;/li&gt;
&lt;li&gt;Updated README.md documentation to reflect v0.9.0+ structure&lt;/li&gt;
&lt;li&gt;New features now work correctly with frontmatter-only lanes from day one&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lane validation&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;tasks_cli.py update command now validates lane values&lt;/li&gt;
&lt;li&gt;Rejects invalid lanes before processing&lt;/li&gt;
&lt;li&gt;Clear error messages for invalid input&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-14&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;ruamel.yaml&gt;=0.18.0&lt;/code&gt; dependency for consistent YAML handling&lt;/li&gt;
&lt;li&gt;Updated success messages to reflect flat structure&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-migration&quot;&gt;🚀 Migration&lt;/h3&gt;
&lt;p&gt;If you upgraded to v0.9.0 and still have issues, run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; again to apply v0.9.1 fixes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Completes any remaining lane migrations&lt;/li&gt;
&lt;li&gt;Cleans up worktree command directories&lt;/li&gt;
&lt;li&gt;Normalizes all frontmatter for consistency&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;090---2025-12-17&quot;&gt;[0.9.0] - 2025-12-17&lt;/h2&gt;
&lt;h3 id=&quot;-major-release-frontmatter-only-lane-management&quot;&gt;🎯 Major Release: Frontmatter-Only Lane Management&lt;/h3&gt;
&lt;p&gt;This release fundamentally changes how Spec Kitty manages work package lanes, eliminating directory-based lane tracking in favor of a simpler, conflict-free frontmatter-only system.&lt;/p&gt;
&lt;h3 id=&quot;️-breaking-changes&quot;&gt;⚠️ Breaking Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lane system completely redesigned&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Work packages now live in a flat &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;feature&gt;/tasks/&lt;/code&gt; directory&lt;/li&gt;
&lt;li&gt;Lane status determined &lt;strong&gt;solely by &lt;code dir=&quot;auto&quot;&gt;lane:&lt;/code&gt; frontmatter field&lt;/strong&gt; (no more subdirectories)&lt;/li&gt;
&lt;li&gt;Old system: &lt;code dir=&quot;auto&quot;&gt;tasks/planned/WP01.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;tasks/doing/WP02.md&lt;/code&gt; ❌&lt;/li&gt;
&lt;li&gt;New system: &lt;code dir=&quot;auto&quot;&gt;tasks/WP01.md&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;lane: &quot;planned&quot;&lt;/code&gt; ✅&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Command renamed: &lt;code dir=&quot;auto&quot;&gt;move&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;update&lt;/code&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Legacy &lt;code dir=&quot;auto&quot;&gt;tasks_cli.py move&lt;/code&gt; command removed&lt;/li&gt;
&lt;li&gt;Use &lt;code dir=&quot;auto&quot;&gt;tasks_cli.py update &amp;#x3C;feature&gt; &amp;#x3C;WP&gt; &amp;#x3C;lane&gt;&lt;/code&gt; instead&lt;/li&gt;
&lt;li&gt;Semantic clarity: command updates metadata, doesn’t move files&lt;/li&gt;
&lt;li&gt;Legacy format detection: &lt;code dir=&quot;auto&quot;&gt;update&lt;/code&gt; command refuses to work on old directory-based structure&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Direct frontmatter editing now supported&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;You can now directly edit the &lt;code dir=&quot;auto&quot;&gt;lane:&lt;/code&gt; field in WP frontmatter&lt;/li&gt;
&lt;li&gt;Previous “DO NOT EDIT” warnings removed from all templates&lt;/li&gt;
&lt;li&gt;System recognizes manual lane changes immediately&lt;/li&gt;
&lt;li&gt;No file movement required for lane transitions&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-added-27&quot;&gt;🆕 Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Migration command: &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Automatically migrates features from directory-based to frontmatter-only format&lt;/li&gt;
&lt;li&gt;Preserves all lane assignments during migration&lt;/li&gt;
&lt;li&gt;Idempotent: safe to run multiple times&lt;/li&gt;
&lt;li&gt;Cleans up empty lane subdirectories after migration&lt;/li&gt;
&lt;li&gt;Migrates both main repo and worktree features&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Legacy format detection&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;is_legacy_format()&lt;/code&gt; function detects old directory-based structure&lt;/li&gt;
&lt;li&gt;CLI commands display helpful warnings when legacy format detected&lt;/li&gt;
&lt;li&gt;Dashboard shows migration prompt for legacy features&lt;/li&gt;
&lt;li&gt;Non-blocking: legacy features remain functional until migrated&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Enhanced status command&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Better formatted output with lane grouping&lt;/li&gt;
&lt;li&gt;Auto-detects feature from branch/worktree when not specified&lt;/li&gt;
&lt;li&gt;Shows work packages organized by current lane&lt;/li&gt;
&lt;li&gt;Works with both legacy and new formats&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-changed-15&quot;&gt;🔧 Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;work package location logic&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;locate_work_package()&lt;/code&gt; now searches flat &lt;code dir=&quot;auto&quot;&gt;tasks/&lt;/code&gt; directory first&lt;/li&gt;
&lt;li&gt;Falls back to legacy subdirectory search for backwards compatibility&lt;/li&gt;
&lt;li&gt;Exact WP ID matching (WP04 won’t match WP04b)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Lane extraction utilities&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;New &lt;code dir=&quot;auto&quot;&gt;get_lane_from_frontmatter()&lt;/code&gt; function extracts lane from YAML&lt;/li&gt;
&lt;li&gt;Defaults to “planned” when &lt;code dir=&quot;auto&quot;&gt;lane:&lt;/code&gt; field missing&lt;/li&gt;
&lt;li&gt;Validates lane values against allowed set&lt;/li&gt;
&lt;li&gt;Available in both &lt;code dir=&quot;auto&quot;&gt;task_helpers.py&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;tasks_support.py&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dashboard scanner updates&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Reads lane from frontmatter instead of directory location&lt;/li&gt;
&lt;li&gt;Displays legacy format warnings&lt;/li&gt;
&lt;li&gt;Works seamlessly with both formats during transition&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Activity log behavior&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Lane transitions still append activity log entries&lt;/li&gt;
&lt;li&gt;Captures agent, shell PID, and timestamp&lt;/li&gt;
&lt;li&gt;No file movement logged (because no movement occurs)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-documentation-6&quot;&gt;📚 Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Updated all templates&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/templates/task-prompt-template.md&lt;/code&gt; - Removed “DO NOT EDIT” warnings&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/templates/tasks-template.md&lt;/code&gt; - Updated for flat structure&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/templates/AGENTS.md&lt;/code&gt; - New lane management instructions&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;tasks/README.md&lt;/code&gt; - Rewritten for flat directory layout&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Updated mission templates&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;All mission-specific templates updated (software-dev, research)&lt;/li&gt;
&lt;li&gt;Command templates updated (&lt;code dir=&quot;auto&quot;&gt;implement.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;review.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;merge.md&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Examples updated to show new workflow&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Updated main documentation&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;README.md&lt;/code&gt; - Updated quick start examples&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;docs/quickstart.md&lt;/code&gt; - New lane management workflow&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;docs/multi-agent-orchestration.md&lt;/code&gt; - Updated collaboration examples&lt;/li&gt;
&lt;li&gt;All &lt;code dir=&quot;auto&quot;&gt;examples/&lt;/code&gt; updated with new commands&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-testing&quot;&gt;🧪 Testing&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;286 tests passing (0 failures)&lt;/li&gt;
&lt;li&gt;New tests for frontmatter-only lane system&lt;/li&gt;
&lt;li&gt;Legacy format detection tests&lt;/li&gt;
&lt;li&gt;Migration command tests&lt;/li&gt;
&lt;li&gt;Dual-format compatibility tests&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-migration-guide&quot;&gt;🚀 Migration Guide&lt;/h3&gt;
&lt;p&gt;&lt;strong&gt;For existing projects:&lt;/strong&gt;&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Back up your work&lt;/strong&gt; (commit changes, push to remote)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Run migration&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Verify&lt;/strong&gt;: &lt;code dir=&quot;auto&quot;&gt;spec-kitty status --feature &amp;#x3C;your-feature&gt;&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Update workflows&lt;/strong&gt;: Replace &lt;code dir=&quot;auto&quot;&gt;move&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;update&lt;/code&gt; in scripts/docs&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Key benefits of upgrading:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;✅ No file conflicts during lane changes (especially in worktrees)&lt;/li&gt;
&lt;li&gt;✅ Direct editing of &lt;code dir=&quot;auto&quot;&gt;lane:&lt;/code&gt; field supported&lt;/li&gt;
&lt;li&gt;✅ Better multi-agent compatibility&lt;/li&gt;
&lt;li&gt;✅ Simpler mental model (one directory, not four)&lt;/li&gt;
&lt;li&gt;✅ Fewer git operations per lane change&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Legacy format still works&lt;/strong&gt; - You can continue using old directory structure until ready to migrate. All commands detect format automatically.&lt;/p&gt;
&lt;h3 id=&quot;-fixed-55&quot;&gt;🐛 Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;File conflicts during simultaneous lane changes by multiple agents&lt;/li&gt;
&lt;li&gt;Git staging issues with lane transitions&lt;/li&gt;
&lt;li&gt;Race conditions in worktree-based parallel development&lt;/li&gt;
&lt;li&gt;Lane mismatch validation errors (no longer possible with frontmatter-only)&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;-related&quot;&gt;🔗 Related&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Feature implementation: &lt;code dir=&quot;auto&quot;&gt;007-frontmatter-only-lane&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;All 6 work packages completed and reviewed&lt;/li&gt;
&lt;li&gt;Comprehensive test coverage added&lt;/li&gt;
&lt;/ul&gt;
&lt;hr&gt;
&lt;h2 id=&quot;082---2025-12-17&quot;&gt;[0.8.2] - 2025-12-17&lt;/h2&gt;
&lt;h3 id=&quot;added-42&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Task lane management documentation&lt;/strong&gt; - Added clear instructions to AGENTS.md and task templates warning agents never to manually edit the &lt;code dir=&quot;auto&quot;&gt;lane:&lt;/code&gt; YAML field
&lt;ul&gt;
&lt;li&gt;Lane is determined by directory location, not YAML field&lt;/li&gt;
&lt;li&gt;Editing &lt;code dir=&quot;auto&quot;&gt;lane:&lt;/code&gt; without moving the file creates a mismatch that breaks the system&lt;/li&gt;
&lt;li&gt;All templates now include YAML comment: &lt;code dir=&quot;auto&quot;&gt;# DO NOT EDIT - use: workflow commands&lt;/code&gt; (legacy note)&lt;/li&gt;
&lt;li&gt;Added “Task Lane Management Rule” section to project AGENTS.md&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;081---2025-12-17&quot;&gt;[0.8.1] - 2025-12-17&lt;/h2&gt;
&lt;h3 id=&quot;fixed-58&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;work package move race conditions&lt;/strong&gt; - Multiple agents can now work on different WPs simultaneously without blocking each other&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Conflict detection now only blocks on changes to the same WP, not unrelated WP files&lt;/li&gt;
&lt;li&gt;Agents working on WP05 no longer block moves of WP04&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Exact WP ID matching&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;WP04&lt;/code&gt; no longer incorrectly matches &lt;code dir=&quot;auto&quot;&gt;WP04b&lt;/code&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Changed from prefix matching to exact boundary matching&lt;/li&gt;
&lt;li&gt;Pattern now requires WP ID to be followed by &lt;code dir=&quot;auto&quot;&gt;-&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;_&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.&lt;/code&gt;, or end of filename&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Cleanup no longer leaves staged deletions&lt;/strong&gt; - Stale copy cleanup uses filesystem delete instead of &lt;code dir=&quot;auto&quot;&gt;git rm&lt;/code&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Prevents orphaned staged deletions from blocking subsequent operations&lt;/li&gt;
&lt;li&gt;Automatically unstages any previously staged changes to cleaned files&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;080---2025-12-15&quot;&gt;[0.8.0] - 2025-12-15&lt;/h2&gt;
&lt;h3 id=&quot;breaking-changes-2&quot;&gt;Breaking Changes&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission system refactored to per-feature model&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Missions are now selected during &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Each feature stores its mission in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; (field: &lt;code dir=&quot;auto&quot;&gt;&quot;mission&quot;: &quot;software-dev&quot;&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;.kittify/active-mission&lt;/code&gt; symlink/file is no longer used&lt;/li&gt;
&lt;li&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to clean up existing projects&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Removed commands&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty mission switch&lt;/code&gt; - Missions are now per-feature, not per-project&lt;/li&gt;
&lt;li&gt;Running this command now shows a helpful error message explaining the new workflow&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Removed flags&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; flag from &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; - Use &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; instead&lt;/li&gt;
&lt;li&gt;Flag is hidden but shows deprecation warning if used&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-43&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission inference during &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt;&lt;/strong&gt; - LLM analyzes feature description and suggests appropriate mission:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;“Build a REST API” → suggests &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;“Research best practices” → suggests &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;User confirms or overrides the suggestion&lt;/li&gt;
&lt;li&gt;Explicit &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt; flag bypasses inference&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Per-feature mission storage&lt;/strong&gt; - Selected mission stored in feature’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;All downstream commands read mission from feature context&lt;/li&gt;
&lt;li&gt;Legacy features without mission field default to &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Mission discovery&lt;/strong&gt; - New &lt;code dir=&quot;auto&quot;&gt;discover_missions()&lt;/code&gt; function returns all available missions with source indicators&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Updated &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission list&lt;/code&gt;&lt;/strong&gt; - Shows source column (project/built-in) for each mission&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Migration for v0.8.0&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; removes obsolete &lt;code dir=&quot;auto&quot;&gt;.kittify/active-mission&lt;/code&gt; file&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;AGENTS.md worktree fix&lt;/strong&gt; - New worktrees get AGENTS.md symlink, and &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; fixes existing worktrees&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-42&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;All downstream commands (&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.implement&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.review&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.accept&lt;/code&gt;) now read mission from feature’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;create-new-feature.sh&lt;/code&gt; accepts &lt;code dir=&quot;auto&quot;&gt;--mission &amp;#x3C;key&gt;&lt;/code&gt; parameter to set mission in meta.json&lt;/li&gt;
&lt;li&gt;Common bash/PowerShell scripts updated to resolve mission from feature directory&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty mission current&lt;/code&gt; shows current default mission (for informational purposes)&lt;/li&gt;
&lt;li&gt;Dashboard template now includes dynamic AGENTS.md path discovery instructions&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;deprecated&quot;&gt;Deprecated&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;set_active_mission()&lt;/code&gt; function - Shows deprecation warning, will be removed in future version&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;migration-guide&quot;&gt;Migration Guide&lt;/h3&gt;
&lt;ol&gt;
&lt;li&gt;Run &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; to remove &lt;code dir=&quot;auto&quot;&gt;.kittify/active-mission&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Existing features without &lt;code dir=&quot;auto&quot;&gt;mission&lt;/code&gt; field will use &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; by default&lt;/li&gt;
&lt;li&gt;New features will have mission set during &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt;&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;074---2025-12-14&quot;&gt;[0.7.4] - 2025-12-14&lt;/h2&gt;
&lt;h3 id=&quot;added-44&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Script Update Migration&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; now updates project scripts:
&lt;ul&gt;
&lt;li&gt;Copies latest &lt;code dir=&quot;auto&quot;&gt;create-new-feature.sh&lt;/code&gt; from package to project&lt;/li&gt;
&lt;li&gt;Fixes worktree feature numbering bug in existing projects&lt;/li&gt;
&lt;li&gt;Previously, projects kept old scripts from when they were initialized&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;073---2025-12-14&quot;&gt;[0.7.3] - 2025-12-14&lt;/h2&gt;
&lt;h3 id=&quot;fixed-59&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Duplicate Feature Numbers with Worktrees&lt;/strong&gt; – Script now scans both &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; AND &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt; for existing feature numbers:
&lt;ul&gt;
&lt;li&gt;Previously only scanned &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; which was empty when using worktrees&lt;/li&gt;
&lt;li&gt;This caused new features to get &lt;code dir=&quot;auto&quot;&gt;001&lt;/code&gt; even when &lt;code dir=&quot;auto&quot;&gt;001-*&lt;/code&gt; worktree already existed&lt;/li&gt;
&lt;li&gt;Now correctly finds highest number across both locations&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;072---2025-12-14&quot;&gt;[0.7.2] - 2025-12-14&lt;/h2&gt;
&lt;h3 id=&quot;fixed-60&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Duplicate Slash Commands in Worktrees (Corrected)&lt;/strong&gt; – Fixed the fix from v0.7.1:
&lt;ul&gt;
&lt;li&gt;v0.7.1 incorrectly removed commands from main repo (broke &lt;code dir=&quot;auto&quot;&gt;/&lt;/code&gt; commands there)&lt;/li&gt;
&lt;li&gt;v0.7.2 removes commands from &lt;strong&gt;worktrees&lt;/strong&gt; instead (they inherit from main repo)&lt;/li&gt;
&lt;li&gt;Claude Code traverses UP, so worktrees find main repo’s &lt;code dir=&quot;auto&quot;&gt;.claude/commands/&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;main repo keeps commands, worktrees don’t need their own copy&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;071---2025-12-14-yanked&quot;&gt;[0.7.1] - 2025-12-14 [YANKED]&lt;/h2&gt;
&lt;h3 id=&quot;fixed-61&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;del&gt;Duplicate Slash Commands in Worktrees&lt;/del&gt; – &lt;strong&gt;Incorrect fix, replaced by v0.7.2&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;070---2025-12-14&quot;&gt;[0.7.0] - 2025-12-14&lt;/h2&gt;
&lt;h3 id=&quot;added-45&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; Command&lt;/strong&gt; – Automatically migrate existing projects to current version:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Detects project version via metadata or directory structure heuristics&lt;/li&gt;
&lt;li&gt;Applies all necessary migrations in order (0.2.0 → 0.6.7)&lt;/li&gt;
&lt;li&gt;Auto-upgrades worktrees alongside main project&lt;/li&gt;
&lt;li&gt;Supports &lt;code dir=&quot;auto&quot;&gt;--dry-run&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--verbose&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--target&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;--no-worktrees&lt;/code&gt; options&lt;/li&gt;
&lt;li&gt;Tracks applied migrations in &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Idempotent - safe to run multiple times&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Migration System&lt;/strong&gt; – Five automatic migrations for project structure updates:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;0.2.0&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;.specify/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; directory rename&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;0.4.8&lt;/code&gt;: Add all 12 agent directories to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;0.5.0&lt;/code&gt;: Install encoding validation git hooks&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;0.6.5&lt;/code&gt;: &lt;code dir=&quot;auto&quot;&gt;commands/&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;command-templates/&lt;/code&gt; rename&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;0.6.7&lt;/code&gt;: Ensure software-dev and research missions are present&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Broken Mission Detection&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;VersionDetector.detect_broken_mission_system()&lt;/code&gt; identifies corrupted mission.yaml files&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Migration Registry Validation&lt;/strong&gt; – Duplicate migration IDs and missing required fields now raise &lt;code dir=&quot;auto&quot;&gt;ValueError&lt;/code&gt;&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-62&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Test Timeout in Dashboard CLI Tests&lt;/strong&gt; – Reduced port cleanup from 763 ports to 8 specific test ports&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Playwright Window Handling&lt;/strong&gt; – Tests now open new windows (not tabs) and close properly on exit&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;067---2025-12-13&quot;&gt;[0.6.7] - 2025-12-13&lt;/h2&gt;
&lt;h3 id=&quot;fixed-63&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Missing software-dev Mission in PyPI Package&lt;/strong&gt; – Fixed build configuration to include all missions:
&lt;ul&gt;
&lt;li&gt;Added explicit sdist include patterns to pyproject.toml&lt;/li&gt;
&lt;li&gt;The &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; mission was missing from v0.6.5 and v0.6.6 wheel builds&lt;/li&gt;
&lt;li&gt;Root cause: &lt;code dir=&quot;auto&quot;&gt;force-include&lt;/code&gt; only applied to wheel target, not sdist (wheel was built from sdist)&lt;/li&gt;
&lt;li&gt;Now both &lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt; missions are correctly packaged&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;066---2025-12-13&quot;&gt;[0.6.6] - 2025-12-13&lt;/h2&gt;
&lt;h3 id=&quot;fixed-64&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Test Suite Updated for 12 Agent Directories&lt;/strong&gt; – All tests now expect 12 agents (added &lt;code dir=&quot;auto&quot;&gt;.github/copilot/&lt;/code&gt;):
&lt;ul&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;test_init_flow.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_gitignore_management.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_gitignore_manager_simple.py&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;tests/unit/test_gitignore_manager.py&lt;/code&gt; to expect 12 agents&lt;/li&gt;
&lt;li&gt;Fixed template manager tests to use new &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; source paths&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-43&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Template Source Paths&lt;/strong&gt; – Tests now use correct &lt;code dir=&quot;auto&quot;&gt;.kittify/templates/command-templates/&lt;/code&gt; paths&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;065---2025-12-13&quot;&gt;[0.6.5] - 2025-12-13&lt;/h2&gt;
&lt;h3 id=&quot;added-46&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Pre-commit Git Hooks&lt;/strong&gt; – Automatic protection against committing agent directories:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Blocks commits containing &lt;code dir=&quot;auto&quot;&gt;.claude/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.codex/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.gemini/&lt;/code&gt;, etc.&lt;/li&gt;
&lt;li&gt;Warns about &lt;code dir=&quot;auto&quot;&gt;.github/copilot/&lt;/code&gt; (nested in &lt;code dir=&quot;auto&quot;&gt;.github/&lt;/code&gt; which is usually committed)&lt;/li&gt;
&lt;li&gt;Installed automatically during &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;GitHub Copilot Directory Protection&lt;/strong&gt; – Added &lt;code dir=&quot;auto&quot;&gt;.github/copilot/&lt;/code&gt; as 12th protected agent directory&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;.claudeignore Generation&lt;/strong&gt; – Optimizes Claude Code token usage by excluding templates&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-65&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Worktree Constitution Symlinks&lt;/strong&gt; – Feature worktrees now share constitution via symlink&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Git Hooks Installation Timing&lt;/strong&gt; – Hooks now install after &lt;code dir=&quot;auto&quot;&gt;.git/&lt;/code&gt; is created&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;064---2025-11-26&quot;&gt;[0.6.4] - 2025-11-26&lt;/h2&gt;
&lt;h3 id=&quot;fixed-66&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Agent Commands Missing in Worktrees&lt;/strong&gt; – Slash commands now work in all feature worktrees for all AI agents:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;create-new-feature.sh&lt;/code&gt; now symlinks agent command directories from main repo to worktrees&lt;/li&gt;
&lt;li&gt;Supports all 12 agent types: Claude, Gemini, Copilot, Cursor, Qwen, OpenCode, Windsurf, Codex, KiloCode, Auggie, Roo, Amazon Q&lt;/li&gt;
&lt;li&gt;Fixes &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt;, and all other slash commands in worktrees&lt;/li&gt;
&lt;li&gt;Existing worktrees get symlinks added when reused (backward compatible)&lt;/li&gt;
&lt;li&gt;Root cause: worktrees are separate working directories that don’t share &lt;code dir=&quot;auto&quot;&gt;.claude/commands/&lt;/code&gt; etc.&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;063---2025-11-25&quot;&gt;[0.6.3] - 2025-11-25&lt;/h2&gt;
&lt;h3 id=&quot;fixed-67&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission Directory Not Copied During Init&lt;/strong&gt; – Projects initialized with &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now correctly receive mission templates:
&lt;ul&gt;
&lt;li&gt;Fixed &lt;code dir=&quot;auto&quot;&gt;copy_specify_base_from_package()&lt;/code&gt; to look at correct path &lt;code dir=&quot;auto&quot;&gt;specify_cli/missions&lt;/code&gt; (matching pyproject.toml)&lt;/li&gt;
&lt;li&gt;Previously looked at wrong paths: &lt;code dir=&quot;auto&quot;&gt;.kittify/missions&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;template_data/missions&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;software-dev&lt;/code&gt; mission was missing from initialized projects, breaking &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt; and other commands&lt;/li&gt;
&lt;li&gt;Root cause: pyproject.toml packages missions to &lt;code dir=&quot;auto&quot;&gt;specify_cli/missions&lt;/code&gt; but code looked elsewhere&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;062---2025-11-18&quot;&gt;[0.6.2] - 2025-11-18&lt;/h2&gt;
&lt;h3 id=&quot;fixed-68&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;PowerShell Wrapper Parameter Handling&lt;/strong&gt; – Windows lane transitions now work correctly:
&lt;ul&gt;
&lt;li&gt;Fixed legacy &lt;code dir=&quot;auto&quot;&gt;tasks-move-to-lane.ps1&lt;/code&gt; to properly parse named PowerShell parameters&lt;/li&gt;
&lt;li&gt;Translates Spec Kitty’s named params (&lt;code dir=&quot;auto&quot;&gt;-FeatureName&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;-TaskId&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;-TargetLane&lt;/code&gt;) to &lt;code dir=&quot;auto&quot;&gt;tasks_cli.py&lt;/code&gt; positional args&lt;/li&gt;
&lt;li&gt;Resolves &lt;code dir=&quot;auto&quot;&gt;unrecognized arguments&lt;/code&gt; error that broke &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.review&lt;/code&gt; on Windows&lt;/li&gt;
&lt;li&gt;Maintains backward compatibility with positional argument usage&lt;/li&gt;
&lt;li&gt;Fixes #34&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;061---2025-11-18&quot;&gt;[0.6.1] - 2025-11-18&lt;/h2&gt;
&lt;h3 id=&quot;fixed-69&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Untracked Task File Moves&lt;/strong&gt; – Task move workflow now handles untracked files:
&lt;ul&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;is_file_tracked()&lt;/code&gt; helper to detect if file is in git index&lt;/li&gt;
&lt;li&gt;Move command automatically stages untracked source files before moving&lt;/li&gt;
&lt;li&gt;Fixes &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.implement&lt;/code&gt; failures when &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks&lt;/code&gt; doesn’t commit&lt;/li&gt;
&lt;li&gt;Provides clear feedback: &lt;code dir=&quot;auto&quot;&gt;[spec-kitty] Added untracked file: ...&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Defensive fix works with both existing untracked files and future workflows&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;060---2025-11-16&quot;&gt;[0.6.0] - 2025-11-16&lt;/h2&gt;
&lt;h3 id=&quot;fixed-70&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dashboard Constitution Tracking&lt;/strong&gt; – Feature-level constitution.md files now tracked and displayed:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added constitution to scanner artifact list&lt;/li&gt;
&lt;li&gt;Constitution appears in overview with ⚖️ icon&lt;/li&gt;
&lt;li&gt;Frontend properly detects constitution.exists property&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dashboard Modification Detection&lt;/strong&gt; – Dashboard now detects file modifications, not just existence:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Scanner returns {exists, mtime, size} for each artifact instead of boolean&lt;/li&gt;
&lt;li&gt;Frontend updated to use .exists property with optional chaining&lt;/li&gt;
&lt;li&gt;Overview auto-reloads when artifacts change during polling&lt;/li&gt;
&lt;li&gt;No manual refresh required to see new/modified files&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dashboard Project Constitution Endpoint&lt;/strong&gt; – Project constitution now loads in dashboard:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added /api/constitution endpoint to serve .kittify/memory/constitution.md&lt;/li&gt;
&lt;li&gt;Sidebar Constitution link now displays file content instead of “not found”&lt;/li&gt;
&lt;li&gt;Separate from feature-level constitution tracking&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;work package Conflict Detection Too Strict&lt;/strong&gt; – Moving WP no longer blocked by unrelated WP changes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Conflict detection now scoped to same work package ID only&lt;/li&gt;
&lt;li&gt;Moving WP04 no longer fails if WP06/WP08 have uncommitted changes&lt;/li&gt;
&lt;li&gt;Reduces false positives from ~90% to ~5%&lt;/li&gt;
&lt;li&gt;Agents don’t need —force for unrelated work packages&lt;/li&gt;
&lt;li&gt;Still catches real conflicts (same WP in multiple lanes)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Accept Command Over-Questioning&lt;/strong&gt; – Acceptance workflow now auto-detects instead of asking:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;feature slug auto-detected from git branch&lt;/li&gt;
&lt;li&gt;Mode defaults to ‘local’ (most common)&lt;/li&gt;
&lt;li&gt;Validation commands searched in git log&lt;/li&gt;
&lt;li&gt;Only asks user if auto-detection fails&lt;/li&gt;
&lt;li&gt;Reduces user questions from 3-4 to 0 in typical case&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Init Command Blocking on Optional Tools&lt;/strong&gt; – Project init no longer fails on missing agent tools:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Changed from red error + exit(1) to yellow warning + continue&lt;/li&gt;
&lt;li&gt;Gemini CLI and other tools are optional&lt;/li&gt;
&lt;li&gt;Users can install tools later without re-init&lt;/li&gt;
&lt;li&gt;—ignore-agent-tools flag still available but rarely needed&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Encoding Normalization Incomplete&lt;/strong&gt; – Unicode smart quotes now properly normalized to ASCII:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Added character mapping for 12 common Unicode characters&lt;/li&gt;
&lt;li&gt;Smart quotes (U+2018/U+2019) → ASCII apostrophe&lt;/li&gt;
&lt;li&gt;Em/en dashes → hyphens&lt;/li&gt;
&lt;li&gt;Ellipsis, bullets, nbsp → ASCII equivalents&lt;/li&gt;
&lt;li&gt;—normalize-encoding now produces true ASCII output&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-44&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission Display Simplified&lt;/strong&gt; – Reduced verbose mission card to single line:
&lt;ul&gt;
&lt;li&gt;Removed domain label, version number, path display&lt;/li&gt;
&lt;li&gt;Removed redundant refresh button (auto-updates every second)&lt;/li&gt;
&lt;li&gt;Changed from card layout to inline text: “Mission: {name}”&lt;/li&gt;
&lt;li&gt;Cleaner, less cluttered header&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-47&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission System Architecture&lt;/strong&gt; – Complete mission-based workflow system (feature 005):
&lt;ul&gt;
&lt;li&gt;Guards module for pre-flight validation&lt;/li&gt;
&lt;li&gt;Pydantic mission schema validation&lt;/li&gt;
&lt;li&gt;Mission CLI commands (list, current, switch, info)&lt;/li&gt;
&lt;li&gt;Research mission templates and citation validators&lt;/li&gt;
&lt;li&gt;Path convention validation&lt;/li&gt;
&lt;li&gt;Dashboard mission display&lt;/li&gt;
&lt;li&gt;Comprehensive integration tests&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;053---2025-11-15&quot;&gt;[0.5.3] - 2025-11-15&lt;/h2&gt;
&lt;h3 id=&quot;fixed-71&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dashboard Orphaned Process Cleanup&lt;/strong&gt; – Fixed dashboard startup failures caused by orphaned test processes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Dashboard now detects and cleans up orphaned processes when health check fails due to project path mismatch&lt;/li&gt;
&lt;li&gt;Added retry logic after successful orphan cleanup&lt;/li&gt;
&lt;li&gt;Orphan cleanup triggers on health check failure (not just port exhaustion)&lt;/li&gt;
&lt;li&gt;Eliminates false “Unable to start dashboard” errors when orphaned test dashboards occupy ports&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Dashboard Subprocess Import Failure&lt;/strong&gt; – Fixed ModuleNotFoundError in complex Python environments:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;Dashboard subprocess now always inserts spec-kitty path at sys.path[0]&lt;/li&gt;
&lt;li&gt;Fixes import failures when user’s PYTHONPATH or .pth files contain spec-kitty path at lower priority&lt;/li&gt;
&lt;li&gt;Ensures correct spec-kitty installation takes precedence over environment paths&lt;/li&gt;
&lt;li&gt;Resolves “ModuleNotFoundError: No module named ‘specify_cli.dashboard’” in subprocesses&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-45&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Test Suite Cleanup Improvements&lt;/strong&gt; – Enhanced dashboard test cleanup to prevent orphaned processes:
&lt;ul&gt;
&lt;li&gt;Module-level cleanup fixture kills all orphaned dashboards before and after test runs&lt;/li&gt;
&lt;li&gt;Expanded cleanup port range from 9992-9999 to 9237-10000 (covers default and test ranges)&lt;/li&gt;
&lt;li&gt;Added &lt;code dir=&quot;auto&quot;&gt;kill_all_spec_kitty_dashboards()&lt;/code&gt; helper using pgrep/pkill&lt;/li&gt;
&lt;li&gt;Two-tier cleanup strategy: module-level (all processes) + function-level (specific ports)&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-48&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Testing Guidelines for Agents&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;docs/testing-guidelines.md&lt;/code&gt;) – Comprehensive testing best practices:
&lt;ul&gt;
&lt;li&gt;Required cleanup patterns for dashboard tests (pytest fixtures, autouse fixtures)&lt;/li&gt;
&lt;li&gt;Anti-patterns to avoid (cleanup in test body, shared directories, no exception handling)&lt;/li&gt;
&lt;li&gt;Impact analysis of orphaned processes on local development and CI/CD&lt;/li&gt;
&lt;li&gt;Examples of proper test isolation and resource management&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-46&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Command Consolidation&lt;/strong&gt; – Merged &lt;code dir=&quot;auto&quot;&gt;spec-kitty check&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty diagnostics&lt;/code&gt; into &lt;code dir=&quot;auto&quot;&gt;spec-kitty verify-setup&lt;/code&gt;:
&lt;ul&gt;
&lt;li&gt;Removed redundant &lt;code dir=&quot;auto&quot;&gt;spec-kitty check&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;spec-kitty diagnostics&lt;/code&gt; commands&lt;/li&gt;
&lt;li&gt;Tool checking now integrated into &lt;code dir=&quot;auto&quot;&gt;verify-setup&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;--check-tools&lt;/code&gt; flag (default: enabled)&lt;/li&gt;
&lt;li&gt;Diagnostics mode with dashboard health available via &lt;code dir=&quot;auto&quot;&gt;--diagnostics&lt;/code&gt; flag&lt;/li&gt;
&lt;li&gt;Removed ASCII banner from verify-setup for cleaner output&lt;/li&gt;
&lt;li&gt;Simplifies CLI interface - single command for all environment verification&lt;/li&gt;
&lt;li&gt;JSON output includes tool availability when &lt;code dir=&quot;auto&quot;&gt;--check-tools&lt;/code&gt; is enabled&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-7&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty check&lt;/code&gt; command&lt;/strong&gt; – Functionality moved to &lt;code dir=&quot;auto&quot;&gt;verify-setup --check-tools&lt;/code&gt;
&lt;ul&gt;
&lt;li&gt;Migration: Use &lt;code dir=&quot;auto&quot;&gt;spec-kitty verify-setup&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;spec-kitty check&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Tool checking enabled by default, disable with &lt;code dir=&quot;auto&quot;&gt;--check-tools=false&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty diagnostics&lt;/code&gt; command&lt;/strong&gt; – Functionality moved to &lt;code dir=&quot;auto&quot;&gt;verify-setup --diagnostics&lt;/code&gt;
&lt;ul&gt;
&lt;li&gt;Migration: Use &lt;code dir=&quot;auto&quot;&gt;spec-kitty verify-setup --diagnostics&lt;/code&gt; instead of &lt;code dir=&quot;auto&quot;&gt;spec-kitty diagnostics&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Shows Rich panel-based output with dashboard health, observations, and issues&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;052---2025-11-14&quot;&gt;[0.5.2] - 2025-11-14&lt;/h2&gt;
&lt;h3 id=&quot;fixed-72&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Startup Race Condition&lt;/strong&gt; – Fixed root cause of dashboard health check timing out prematurely:
&lt;ul&gt;
&lt;li&gt;Increased health check timeout from 10 to 20 seconds with exponential backoff&lt;/li&gt;
&lt;li&gt;Retry pattern: 10×100ms, 40×250ms, 20×500ms for adaptive performance&lt;/li&gt;
&lt;li&gt;Removed workaround fallback check that was masking the real issue&lt;/li&gt;
&lt;li&gt;Eliminated false “Unable to start dashboard” errors on slower systems&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-47&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Health Check Strategy&lt;/strong&gt; – Improved reliability with exponential backoff:
&lt;ul&gt;
&lt;li&gt;Quick initial checks (100ms) for fast systems&lt;/li&gt;
&lt;li&gt;Gradual slowdown (250ms then 500ms) for slower systems&lt;/li&gt;
&lt;li&gt;Total timeout increased to ~20 seconds for adequate startup time&lt;/li&gt;
&lt;li&gt;Cleaner error handling without port-scanning fallback&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-49&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Symlinked kitty-specs Test Coverage&lt;/strong&gt; – New test validates dashboard works with worktree structure:
&lt;ul&gt;
&lt;li&gt;Tests scenario from bug report (symlinked &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;.worktrees/&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Ensures dashboard starts correctly with symlinked directories&lt;/li&gt;
&lt;li&gt;Prevents regression of false error reporting&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;051---2025-11-14&quot;&gt;[0.5.1] - 2025-11-14&lt;/h2&gt;
&lt;h3 id=&quot;added-50&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Task Metadata Validation Guardrail&lt;/strong&gt; – Prevents workflow failures when file locations don’t match frontmatter:
&lt;ul&gt;
&lt;li&gt;Auto-detects lane mismatches (file in &lt;code dir=&quot;auto&quot;&gt;for_review/&lt;/code&gt; but &lt;code dir=&quot;auto&quot;&gt;lane: &quot;planned&quot;&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;CLI command: &lt;code dir=&quot;auto&quot;&gt;spec-kitty validate-tasks --fix&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Integrated into &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.review&lt;/code&gt; workflow (auto-runs before review)&lt;/li&gt;
&lt;li&gt;Adds activity log entries documenting all repairs&lt;/li&gt;
&lt;li&gt;Validates required fields (work_package_id, lane) and formats&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Task Metadata Validation Module&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/task_metadata_validation.py&lt;/code&gt;) – Core validation:
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;detect_lane_mismatch()&lt;/code&gt; - Finds directory/frontmatter inconsistencies&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;repair_lane_mismatch()&lt;/code&gt; - Auto-fixes with audit trail&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;validate_task_metadata()&lt;/code&gt; - Comprehensive field validation&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;scan_all_tasks_for_mismatches()&lt;/code&gt; - Feature-wide scanning&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-48&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Version Reading&lt;/strong&gt; – Now reads dynamically from package metadata instead of hardcoded value:
&lt;ul&gt;
&lt;li&gt;Uses &lt;code dir=&quot;auto&quot;&gt;importlib.metadata.version()&lt;/code&gt; to get actual installed version&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty --version&lt;/code&gt; always shows correct version&lt;/li&gt;
&lt;li&gt;No manual updates needed in &lt;code dir=&quot;auto&quot;&gt;__init__.py&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review Workflow&lt;/strong&gt; – Added automatic task metadata validation before review:
&lt;ul&gt;
&lt;li&gt;Runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty validate-tasks --fix&lt;/code&gt; automatically&lt;/li&gt;
&lt;li&gt;Prevents agents getting stuck on lane mismatches&lt;/li&gt;
&lt;li&gt;Documented in &lt;code dir=&quot;auto&quot;&gt;.claude/commands/spec-kitty.review.md&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-73&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard CLI False Error&lt;/strong&gt; – CLI no longer reports “Unable to start dashboard” when dashboard actually started successfully. Added fallback verification to check if dashboard is accessible before reporting failure. Handles race condition where health check times out but server is functional.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review Workflow Blocking&lt;/strong&gt; – Review command no longer fails when file locations don’t match frontmatter metadata. Auto-validation repairs inconsistencies before review.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hardcoded Version&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;spec-kitty --version&lt;/code&gt; now reads from package metadata, always shows correct installed version.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;documentation-3&quot;&gt;Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;task-metadata-validation.md&lt;/strong&gt; (350 lines) – Auto-repair workflow:
&lt;ul&gt;
&lt;li&gt;Lane mismatch detection and repair&lt;/li&gt;
&lt;li&gt;CLI usage examples&lt;/li&gt;
&lt;li&gt;Python API reference&lt;/li&gt;
&lt;li&gt;Integration with review workflow&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;testing&quot;&gt;Testing&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added version detection tests to prevent future hardcoded version bugs&lt;/li&gt;
&lt;li&gt;Task metadata validation tested with real frontmatter/directory mismatches&lt;/li&gt;
&lt;li&gt;All tests passing (13/13)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;050---2025-11-13&quot;&gt;[0.5.0] - 2025-11-13&lt;/h2&gt;
&lt;h3 id=&quot;added-51&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Encoding Validation Guardrail&lt;/strong&gt; – Comprehensive 5-layer defense system to prevent Windows-1252 characters from crashing the dashboard:
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Layer 1&lt;/strong&gt;: Dashboard auto-fixes encoding errors on read (server-side resilience)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Layer 2&lt;/strong&gt;: Character sanitization module with 15+ problematic character mappings&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Layer 3&lt;/strong&gt;: CLI command &lt;code dir=&quot;auto&quot;&gt;spec-kitty validate-encoding&lt;/code&gt; with &lt;code dir=&quot;auto&quot;&gt;--fix&lt;/code&gt; flag&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Layer 4&lt;/strong&gt;: Pre-commit hook that blocks commits with encoding errors&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Layer 5&lt;/strong&gt;: Enhanced AGENTS.md with real crash examples and character blacklist&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Plan Validation Guardrail&lt;/strong&gt; – Prevents agents from skipping the planning phase:
&lt;ul&gt;
&lt;li&gt;Detects 11 template markers in plan.md (threshold: 5+ markers = unfilled)&lt;/li&gt;
&lt;li&gt;Blocks &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.research&lt;/code&gt; command when plan is unfilled&lt;/li&gt;
&lt;li&gt;Blocks &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks&lt;/code&gt; via check-prerequisites.sh&lt;/li&gt;
&lt;li&gt;Clear error messages with remediation steps&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Character Sanitization Module&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/text_sanitization.py&lt;/code&gt;) – Core module for encoding fixes:
&lt;ul&gt;
&lt;li&gt;Maps smart quotes (&lt;code dir=&quot;auto&quot;&gt;&apos; &apos; &quot; &quot;&lt;/code&gt;) → ASCII (&lt;code dir=&quot;auto&quot;&gt;&apos; &quot;&lt;/code&gt;)&lt;/li&gt;
&lt;li&gt;Maps plus-minus (&lt;code dir=&quot;auto&quot;&gt;±&lt;/code&gt;) → &lt;code dir=&quot;auto&quot;&gt;+/-&lt;/code&gt;, multiplication (&lt;code dir=&quot;auto&quot;&gt;×&lt;/code&gt;) → &lt;code dir=&quot;auto&quot;&gt;x&lt;/code&gt;, degree (&lt;code dir=&quot;auto&quot;&gt;°&lt;/code&gt;) → &lt;code dir=&quot;auto&quot;&gt;degrees&lt;/code&gt;&lt;/li&gt;
&lt;li&gt;Supports dry-run mode and automatic backup creation&lt;/li&gt;
&lt;li&gt;Directory-wide sanitization with glob patterns&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Plan Validation Module&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/plan_validation.py&lt;/code&gt;) – Template detection:
&lt;ul&gt;
&lt;li&gt;Configurable threshold (default: 5 markers)&lt;/li&gt;
&lt;li&gt;Line-precise error reporting&lt;/li&gt;
&lt;li&gt;Strict and lenient validation modes&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-49&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Version Reading&lt;/strong&gt; – Now reads dynamically from package metadata instead of hardcoded value:
&lt;ul&gt;
&lt;li&gt;Uses &lt;code dir=&quot;auto&quot;&gt;importlib.metadata.version()&lt;/code&gt; to get actual installed version&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty --version&lt;/code&gt; always shows correct version&lt;/li&gt;
&lt;li&gt;No manual updates needed in &lt;code dir=&quot;auto&quot;&gt;__init__.py&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review Workflow&lt;/strong&gt; – Added automatic task metadata validation before review:
&lt;ul&gt;
&lt;li&gt;Runs &lt;code dir=&quot;auto&quot;&gt;spec-kitty validate-tasks --fix&lt;/code&gt; automatically&lt;/li&gt;
&lt;li&gt;Prevents agents getting stuck on lane mismatches&lt;/li&gt;
&lt;li&gt;Documented in &lt;code dir=&quot;auto&quot;&gt;.claude/commands/spec-kitty.review.md&lt;/code&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Scanner&lt;/strong&gt; – Now resilient to encoding errors:
&lt;ul&gt;
&lt;li&gt;Auto-fixes files on read with backup creation&lt;/li&gt;
&lt;li&gt;Creates error cards instead of crashing on bad files&lt;/li&gt;
&lt;li&gt;Logs encoding issues with clear error messages&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Research Command&lt;/strong&gt; – Added plan validation gate before allowing research artifact creation&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Prerequisites Check Script&lt;/strong&gt; – Added bash-based plan validation (35 lines)&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;AGENTS.md Template&lt;/strong&gt; – Enhanced with encoding warnings:
&lt;ul&gt;
&lt;li&gt;Real crash examples from production&lt;/li&gt;
&lt;li&gt;Explicit character blacklist with Unicode codepoints&lt;/li&gt;
&lt;li&gt;Auto-fix workflow documentation&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-74&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Blank Page Issue&lt;/strong&gt; – Dashboard no longer crashes when markdown files contain Windows-1252 smart quotes, ±, ×, ° symbols. Auto-fix sanitizes files on first read.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agents Skipping Planning&lt;/strong&gt; – Research and tasks commands now blocked until plan.md is properly filled out (not just template).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Review Workflow Blocking&lt;/strong&gt; – Review command no longer fails when file locations don’t match frontmatter metadata. Auto-validation repairs inconsistencies before review.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hardcoded Version&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;spec-kitty --version&lt;/code&gt; now reads from package metadata, always shows correct installed version.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;documentation-4&quot;&gt;Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;encoding-validation.md&lt;/strong&gt; (554 lines) – Complete guide covering:
&lt;ul&gt;
&lt;li&gt;Problem description with real examples&lt;/li&gt;
&lt;li&gt;5-layer architecture explanation&lt;/li&gt;
&lt;li&gt;Testing procedures and troubleshooting&lt;/li&gt;
&lt;li&gt;Migration guide for existing projects&lt;/li&gt;
&lt;li&gt;API reference and performance considerations&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;plan-validation-guardrail.md&lt;/strong&gt; (202 lines) – Implementation details:
&lt;ul&gt;
&lt;li&gt;Problem and solution overview&lt;/li&gt;
&lt;li&gt;Configuration instructions&lt;/li&gt;
&lt;li&gt;Testing procedures&lt;/li&gt;
&lt;li&gt;Benefits and future enhancements&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;task-metadata-validation.md&lt;/strong&gt; (350 lines) – Auto-repair workflow:
&lt;ul&gt;
&lt;li&gt;Lane mismatch detection and repair&lt;/li&gt;
&lt;li&gt;CLI usage examples&lt;/li&gt;
&lt;li&gt;Python API reference&lt;/li&gt;
&lt;li&gt;Integration with review workflow&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;TESTING_REQUIREMENTS_ENCODING_AND_PLAN_VALIDATION.md&lt;/strong&gt; (1056 lines) – Functional test specifications:
&lt;ul&gt;
&lt;li&gt;35+ test cases across 6 test suites&lt;/li&gt;
&lt;li&gt;Coverage targets (85-95%)&lt;/li&gt;
&lt;li&gt;Performance requirements&lt;/li&gt;
&lt;li&gt;Edge case testing requirements&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;testing-1&quot;&gt;Testing&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Added 7 unit tests for plan validation (all passing)&lt;/li&gt;
&lt;li&gt;Verified on real project (battleship): fixed 9 files with encoding issues&lt;/li&gt;
&lt;li&gt;Dashboard now loads successfully after encoding fixes&lt;/li&gt;
&lt;li&gt;Character mapping tests: smart quotes, ±, ×, ° all converted correctly&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0413---2025-11-13&quot;&gt;[0.4.13] - 2025-11-13&lt;/h2&gt;
&lt;h3 id=&quot;fixed-75&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CRITICAL: verify-setup ImportError (Issue #28)&lt;/strong&gt; – Fixed ImportError in &lt;code dir=&quot;auto&quot;&gt;verify-setup&lt;/code&gt; command caused by incorrect import statement in &lt;code dir=&quot;auto&quot;&gt;verify_enhanced.py&lt;/code&gt;. Changed &lt;code dir=&quot;auto&quot;&gt;from . import detect_feature_slug, AcceptanceError&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;from .acceptance import detect_feature_slug, AcceptanceError&lt;/code&gt;. This was a blocking bug that prevented users from running the diagnostic command.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0412---2025-11-13&quot;&gt;[0.4.12] - 2025-11-13&lt;/h2&gt;
&lt;h3 id=&quot;added-52&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Version Flag&lt;/strong&gt; – Added &lt;code dir=&quot;auto&quot;&gt;--version&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;-v&lt;/code&gt; flags to display installed spec-kitty-cli version.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Health Diagnostics&lt;/strong&gt; – Enhanced &lt;code dir=&quot;auto&quot;&gt;spec-kitty diagnostics&lt;/code&gt; to detect dashboard startup failures, test if dashboard can start, and report specific errors. Now catches issues like corrupted files, health check timeouts, and background process failures.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-50&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Diagnostics Output&lt;/strong&gt; – Added Dashboard Health panel showing startup test results, PID tracking status, and specific failure reasons.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0411---2025-11-13&quot;&gt;[0.4.11] - 2025-11-13&lt;/h2&gt;
&lt;h3 id=&quot;fixed-76&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;PowerShell Python Quoting Bug (Issue #26)&lt;/strong&gt; – Fixed SyntaxError in PowerShell scripts caused by double-quote conflicts in embedded Python code. Changed all Python strings in &lt;code dir=&quot;auto&quot;&gt;common.ps1&lt;/code&gt; to use single quotes to avoid PowerShell string parsing conflicts.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-53&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;PowerShell Syntax Guide&lt;/strong&gt; – Created comprehensive &lt;code dir=&quot;auto&quot;&gt;templates/POWERSHELL_SYNTAX.md&lt;/code&gt; with bash vs PowerShell syntax comparison table, common mistakes, and debugging tips for AI agents.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Conditional PowerShell Reference&lt;/strong&gt; – Enhanced &lt;code dir=&quot;auto&quot;&gt;agent-file-template.md&lt;/code&gt; to conditionally include PowerShell syntax reminders only for PowerShell projects, keeping bash contexts clean.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-51&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;AI Agent Context&lt;/strong&gt; – PowerShell-specific guidance now provided via separate reference document instead of cluttering bash-focused templates.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Fixes #26
Addresses #27&lt;/p&gt;
&lt;h2 id=&quot;0410---2025-11-13&quot;&gt;[0.4.10] - 2025-11-13&lt;/h2&gt;
&lt;h3 id=&quot;fixed-77&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CRITICAL: Missing missions directory in PyPI package&lt;/strong&gt; – Added &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; force-include list. Previous release (0.4.9) was missing this directory, causing “Active mission directory not found” errors for all fresh installations.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;049---2025-11-13&quot;&gt;[0.4.9] - 2025-11-13&lt;/h2&gt;
&lt;h3 id=&quot;added-54&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Diagnostics CLI Command&lt;/strong&gt; – New &lt;code dir=&quot;auto&quot;&gt;spec-kitty diagnostics&lt;/code&gt; command with human-readable and JSON output for comprehensive project health checks.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Process Tracking&lt;/strong&gt; – Dashboard now stores process PID in &lt;code dir=&quot;auto&quot;&gt;.dashboard&lt;/code&gt; metadata file for reliable cleanup and monitoring.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Feature Collision Detection&lt;/strong&gt; – Added explicit warnings when creating features with duplicate names that would overwrite existing work.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;LLM Context Documentation&lt;/strong&gt; – Enhanced all 13 command templates with location pre-flight checks, file discovery sections, and workflow context to prevent agents from getting lost.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-52&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Lifecycle&lt;/strong&gt; – Enhanced &lt;code dir=&quot;auto&quot;&gt;ensure_dashboard_running()&lt;/code&gt; to automatically clean up orphaned dashboard processes on initialization, preventing port exhaustion.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Feature Creation Warnings&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;create-new-feature.sh&lt;/code&gt; now warns when git is disabled or features already exist, with clear JSON indicators for LLM agents.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Import Safety&lt;/strong&gt; – Fixed &lt;code dir=&quot;auto&quot;&gt;detect_feature_slug&lt;/code&gt; import path in diagnostics module to use correct module location.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Worktree Documentation&lt;/strong&gt; – Updated WORKTREE_MODEL.md to accurately describe &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; as a complete copy (not symlink) with disk space implications documented.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-78&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;CRITICAL: Dashboard Process Orphan Leak&lt;/strong&gt; – Fixed critical bug where background dashboard processes were orphaned and accumulated until all ports were exhausted. Complete fix includes:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;PIDs are captured and stored in &lt;code dir=&quot;auto&quot;&gt;.dashboard&lt;/code&gt; file (commit b8c7394)&lt;/li&gt;
&lt;li&gt;Orphaned processes with .dashboard files are automatically cleaned up on next init&lt;/li&gt;
&lt;li&gt;HTTP shutdown failures fall back to SIGTERM/SIGKILL with PID tracking&lt;/li&gt;
&lt;li&gt;Port range cleanup scans for orphaned dashboards without .dashboard files (commit 11340a4)&lt;/li&gt;
&lt;li&gt;Safe fingerprinting via health check API prevents killing unrelated services&lt;/li&gt;
&lt;li&gt;Automatic retry with cleanup when port exhaustion detected&lt;/li&gt;
&lt;li&gt;Failed startup processes are cleaned up (no orphans from Ctrl+C during health check)&lt;/li&gt;
&lt;li&gt;Multi-project scenarios remain fully isolated (per-project PIDs, safe port sweeps)&lt;/li&gt;
&lt;li&gt;Handles all orphan types: with metadata, without metadata, deleted temp projects&lt;/li&gt;
&lt;li&gt;Prevents “Could not find free port” errors after repeated uses&lt;/li&gt;
&lt;/ul&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Import Path Bug&lt;/strong&gt; – Fixed &lt;code dir=&quot;auto&quot;&gt;detect_feature_slug&lt;/code&gt; import in &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/dashboard/diagnostics.py&lt;/code&gt; to import from &lt;code dir=&quot;auto&quot;&gt;specify_cli.acceptance&lt;/code&gt; instead of package root.&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;&lt;strong&gt;Worktree Documentation Accuracy&lt;/strong&gt; – Corrected WORKTREE_MODEL.md which incorrectly stated &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; was symlinked; it’s actually a complete copy due to git worktree behavior.&lt;/p&gt;
&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;llm-context-improvements&quot;&gt;LLM Context Improvements&lt;/h3&gt;
&lt;p&gt;All command templates enhanced with consistent context patterns:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Location Pre-flight Checks&lt;/strong&gt;: pwd/git branch verification with expected outputs and correction steps&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File Discovery&lt;/strong&gt;: Lists what files {SCRIPT} provides, output locations, and available context&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Workflow Context&lt;/strong&gt;: Documents before/after commands and feature lifecycle integration&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Templates updated:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;merge.md: CRITICAL safety check preventing merges from wrong location&lt;/li&gt;
&lt;li&gt;clarify.md, research.md, analyze.md: HIGH priority core workflow commands&lt;/li&gt;
&lt;li&gt;specify.md, checklist.md: Entry point and utility commands&lt;/li&gt;
&lt;li&gt;constitution.md, dashboard.md: Project-level and monitoring commands&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;testing-2&quot;&gt;Testing&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;✅ Dashboard comprehensive test suite (34 tests, 100% coverage)&lt;/li&gt;
&lt;li&gt;✅ All CLI commands validated&lt;/li&gt;
&lt;li&gt;✅ Import paths verified&lt;/li&gt;
&lt;li&gt;✅ Worktree behavior confirmed across test scenarios&lt;/li&gt;
&lt;li&gt;✅ LLM context patterns applied consistently&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;security-1&quot;&gt;Security&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Dashboard process cleanup prevents resource exhaustion attacks&lt;/li&gt;
&lt;li&gt;Explicit warnings when creating duplicate features prevent silent data overwrite&lt;/li&gt;
&lt;li&gt;Git disabled warnings ensure users know when version control is unavailable&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;backward-compatibility-1&quot;&gt;Backward Compatibility&lt;/h3&gt;
&lt;p&gt;All changes are fully backward compatible:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;PID storage is optional (old &lt;code dir=&quot;auto&quot;&gt;.dashboard&lt;/code&gt; files still work)&lt;/li&gt;
&lt;li&gt;Feature collision detection is advisory (doesn’t block creation)&lt;/li&gt;
&lt;li&gt;LLM context additions don’t change command behavior&lt;/li&gt;
&lt;li&gt;Dashboard cleanup is automatic (users don’t need to do anything)&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0412---2025-11-11&quot;&gt;[0.4.12] - 2025-11-11&lt;/h2&gt;
&lt;h3 id=&quot;added-55&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Core Service Modules&lt;/strong&gt; – Introduced &lt;code dir=&quot;auto&quot;&gt;specify_cli.core.git_ops&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;project_resolver&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;tool_checker&lt;/code&gt; packages to host git utilities, project discovery, and tool validation logic with clean public APIs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test Coverage&lt;/strong&gt; – Added dedicated suites (&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/test_core/test_git_ops.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_project_resolver.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_tool_checker.py&lt;/code&gt;) covering subprocess helpers, path resolution, and tool validation flows.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-53&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CLI Import Surface&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/__init__.py&lt;/code&gt; now imports git, resolver, and tool helpers from the new core modules, slimming the monolith and sharing the implementations across commands.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Versioning Compliance&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;pyproject.toml&lt;/code&gt; bumped to v0.4.12 to capture the core-service extraction and accompanying behavior changes.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0411---2025-11-11&quot;&gt;[0.4.11] - 2025-11-11&lt;/h2&gt;
&lt;h3 id=&quot;added-56&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Template Test Suite&lt;/strong&gt; – New &lt;code dir=&quot;auto&quot;&gt;tests/test_template/&lt;/code&gt; coverage exercises template manager, renderer, and agent asset generator flows to guard the init experience.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-54&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Template System Extraction&lt;/strong&gt; – Moved template discovery, rendering, and asset generation logic out of &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/__init__.py&lt;/code&gt; into dedicated &lt;code dir=&quot;auto&quot;&gt;specify_cli.template&lt;/code&gt; modules with shared frontmatter parsing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Reuse&lt;/strong&gt; – Updated the dashboard scanner to consume the shared frontmatter parser so Kanban metadata stays in sync with CLI-generated commands.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0410---2025-11-11&quot;&gt;[0.4.10] - 2025-11-11&lt;/h2&gt;
&lt;h3 id=&quot;added-57&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Core Modules&lt;/strong&gt; – Introduced &lt;code dir=&quot;auto&quot;&gt;specify_cli.core.config&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;specify_cli.core.utils&lt;/code&gt; to centralize constants, shared helpers, and exports for downstream packages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CLI UI Package&lt;/strong&gt; – Moved &lt;code dir=&quot;auto&quot;&gt;StepTracker&lt;/code&gt;, arrow-key selection, and related utilities into &lt;code dir=&quot;auto&quot;&gt;specify_cli.cli.ui&lt;/code&gt;, enabling reuse across commands.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test Coverage&lt;/strong&gt; – Added dedicated unit suites for the new core modules and CLI UI interactions (12 new tests).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-55&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Package Structure&lt;/strong&gt; – Created foundational package directories for &lt;code dir=&quot;auto&quot;&gt;core/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;cli/&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;template/&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;dashboard/&lt;/code&gt;, including structured &lt;code dir=&quot;auto&quot;&gt;__init__.py&lt;/code&gt; exports.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Init Command Dependencies&lt;/strong&gt; – Updated &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/__init__.py&lt;/code&gt; to consume the extracted modules, reducing monolith size and improving readability.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;File Utilities&lt;/strong&gt; – Replaced ad-hoc directory creation/removal with safe helper functions to prevent duplication across commands.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;048---2025-11-10&quot;&gt;[0.4.8] - 2025-11-10&lt;/h2&gt;
&lt;h3 id=&quot;added-58&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;GitignoreManager Module&lt;/strong&gt; – New centralized system for managing .gitignore entries for AI agent directories, replacing fragmented approach.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Comprehensive Agent Protection&lt;/strong&gt; – Auto-protect ALL 12 AI agent directories (.claude/, .codex/, .opencode/, etc.) in .gitignore during init, not just selected ones.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Duplicate Detection&lt;/strong&gt; – Smart duplicate detection prevents .gitignore pollution when running init multiple times.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cross-Platform Support&lt;/strong&gt; – Line ending preservation ensures .gitignore works correctly on Windows, macOS, and Linux.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-56&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;init Command Behavior&lt;/strong&gt; – Now automatically protects all AI agent directories instead of just selected ones, ensuring no sensitive data is accidentally committed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Error Messages&lt;/strong&gt; – Improved error messages for permission issues with clear remediation steps (e.g., “Run: chmod u+w .gitignore”).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-79&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Markdown Rendering&lt;/strong&gt; – Fixed issue where .md files in Research and Contracts tabs were not rendered, now properly displays formatted markdown content.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard CSV Display&lt;/strong&gt; – Fixed CSV files not rendering in dashboard, now displays as formatted tables with proper styling and hover effects.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;security-2&quot;&gt;Security&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Agent Directory Protection&lt;/strong&gt; – All 12 known AI agent directories are now automatically added to .gitignore during init, preventing accidental commit of API keys, auth tokens, and other sensitive data.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Special .github/ Handling&lt;/strong&gt; – Added warning for .github/ directory which is used both by GitHub Copilot and GitHub Actions, reminding users to review before committing.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-8&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Legacy Functions&lt;/strong&gt; – Removed &lt;code dir=&quot;auto&quot;&gt;handle_codex_security()&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;ensure_gitignore_entries()&lt;/code&gt; functions, replaced by comprehensive GitignoreManager class.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;047---2025-11-07&quot;&gt;[0.4.7] - 2025-11-07&lt;/h2&gt;
&lt;h3 id=&quot;added-59&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Diagnostics Page&lt;/strong&gt; – New diagnostics page showing real-time environment analysis, artifact location mismatches, and actionable recommendations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;CLI verify-setup Command&lt;/strong&gt; – New &lt;code dir=&quot;auto&quot;&gt;spec-kitty verify-setup&lt;/code&gt; command for comprehensive environment diagnostics in the terminal.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Worktree-Aware Resolution&lt;/strong&gt; – Added &lt;code dir=&quot;auto&quot;&gt;resolve_worktree_aware_feature_dir()&lt;/code&gt; function that intelligently detects and prefers worktree locations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Agent Location Checks&lt;/strong&gt; – Standardized “CRITICAL: Location Requirement” sections in command templates with bash verification scripts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test Coverage&lt;/strong&gt; – Added comprehensive test suite for gitignore management and Codex security features with 9 test cases covering all edge cases.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-57&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Command Templates&lt;/strong&gt; – Enhanced plan.md and tasks.md with explicit worktree location requirements and verification scripts.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Error Messages&lt;/strong&gt; – Improved bash script errors with visual indicators (❌ ERROR, 🔧 TO FIX, 💡 TIP) and exact fix commands.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Research Command&lt;/strong&gt; – Updated to use worktree-aware feature directory resolution.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Refactored Codex Security&lt;/strong&gt; – Extracted Codex credential protection logic into a dedicated &lt;code dir=&quot;auto&quot;&gt;handle_codex_security()&lt;/code&gt; function for better maintainability and testability.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-80&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Artifact Location Mismatch&lt;/strong&gt; – Fixed issue where agents create artifacts in wrong location, preventing them from appearing in dashboard.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;045---2025-11-06&quot;&gt;[0.4.5] - 2025-11-06&lt;/h2&gt;
&lt;h3 id=&quot;added-60&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Agent Guidance&lt;/strong&gt; – Bundled a shared &lt;code dir=&quot;auto&quot;&gt;AGENTS.md&lt;/code&gt; ruleset that is copied into &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; so every generated command has a canonical place to point agents for path/encoding/git expectations.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Encoding Toolkit&lt;/strong&gt; – Introduced &lt;code dir=&quot;auto&quot;&gt;scripts/validate_encoding.py&lt;/code&gt; and new documentation to scan/fix Windows-1252 artifacts, plus a non-interactive init guide in &lt;code dir=&quot;auto&quot;&gt;docs/non-interactive-init.md&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Assets&lt;/strong&gt; – Split the inline dashboard UI into static CSS/JS files and committed them with the release.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-58&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;CLI Help &amp;#x26; Docs&lt;/strong&gt; – Expanded &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;research&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;check&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;merge&lt;/code&gt; help text and refreshed README/index links to render correctly on PyPI.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard Runtime&lt;/strong&gt; – Hardened the dashboard server/CLI handshake with health checks, token-gated shutdown, and more resilient worktree detection.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission Handling&lt;/strong&gt; – Improved mission activation to fall back gracefully when symlinks are unavailable (e.g., Windows w/out dev mode) and aligned shell helpers with the new logic.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;security-3&quot;&gt;Security&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Codex Guardrails&lt;/strong&gt; – Automatically append &lt;code dir=&quot;auto&quot;&gt;.codex/&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;, warn if &lt;code dir=&quot;auto&quot;&gt;auth.json&lt;/code&gt; is tracked, and reiterate the &lt;code dir=&quot;auto&quot;&gt;CODEX_HOME&lt;/code&gt; workflow to keep API credentials out of source control.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;046---2025-11-06&quot;&gt;[0.4.6] - 2025-11-06&lt;/h2&gt;
&lt;h3 id=&quot;fixed-81&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;PyYAML Dependency&lt;/strong&gt; – Added &lt;code dir=&quot;auto&quot;&gt;pyyaml&lt;/code&gt; to the core dependency list so mission loading works in clean environments (CI no longer fails installing the package).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;PyPI README Links&lt;/strong&gt; – Restored absolute documentation links to keep images and references working on PyPI.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;044---2025-11-06&quot;&gt;[0.4.4] - 2025-11-06&lt;/h2&gt;
&lt;h3 id=&quot;security-4&quot;&gt;Security&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Credential Cleanup&lt;/strong&gt; – Removed the committed &lt;code dir=&quot;auto&quot;&gt;.codex&lt;/code&gt; directory (OpenAI credentials) from the entire Git history and regenerated sanitized release assets.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Token Rotation&lt;/strong&gt; – Documented that all compromised keys were revoked and environments refreshed before reissuing packages.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-59&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Release Artifacts&lt;/strong&gt; – Rebuilt GitHub release bundles and PyPI distributions from the cleaned history to ensure no secrets are present in published archives.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;032---2025-11-03&quot;&gt;[0.3.2] - 2025-11-03&lt;/h2&gt;
&lt;h3 id=&quot;added-61&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Automated PyPI Release Pipeline&lt;/strong&gt; – Tag-triggered GitHub Actions workflow automatically builds, validates, and publishes releases to PyPI using &lt;code dir=&quot;auto&quot;&gt;PYPI_API_TOKEN&lt;/code&gt; secret, eliminating manual publish steps.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release Validation Tooling&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;scripts/release/validate_release.py&lt;/code&gt; CLI enforces semantic version progression, changelog completeness, and version/tag alignment in both branch and tag modes with actionable error messages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release Readiness Guardrails&lt;/strong&gt; – Pull request workflow validates version bumps, changelog entries, and test passage before merge; nightly scheduled checks monitor drift.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Comprehensive Release Documentation&lt;/strong&gt; – Complete maintainer guides covering secret management, branch protection, troubleshooting, and step-by-step release workflows.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Changelog Extraction&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;scripts/release/extract_changelog.py&lt;/code&gt; automatically extracts version-specific release notes for GitHub Releases.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release Test Suite&lt;/strong&gt; – 4 pytest tests validate branch mode, tag mode, changelog parsing, and version regression detection.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-60&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;GitHub Actions Workflows&lt;/strong&gt; – Updated &lt;code dir=&quot;auto&quot;&gt;release.yml&lt;/code&gt; with pinned dependency versions, proper workflow ordering (PyPI publish before GitHub Release), and checksums stored in &lt;code dir=&quot;auto&quot;&gt;dist/SHA256SUMS.txt&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Workflow Reliability&lt;/strong&gt; – Fixed heredoc syntax error in &lt;code dir=&quot;auto&quot;&gt;protect-main.yml&lt;/code&gt; that was causing exit code 127 failures.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;security-5&quot;&gt;Security&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Secret Hygiene&lt;/strong&gt; – PyPI credentials exclusively stored in GitHub Actions secrets with rotation guidance; no tokens in repository or logs; workflows sanitize outputs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Workflow Permissions&lt;/strong&gt; – Explicit least-privilege permissions in all workflows (contents:write, id-token:write for releases; contents:read for guards).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;031---2025-11-03&quot;&gt;[0.3.1] - 2025-11-03&lt;/h2&gt;
&lt;h3 id=&quot;changed-61&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Worktree-Aware Merge Flow&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;/spec-kitty merge&lt;/code&gt; now detects when it is invoked from a Git worktree, runs the actual merge steps from the primary repository checkout, and surfaces clearer guidance when the target checkout is dirty.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;documentation-5&quot;&gt;Documentation&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Merge Workflow Guidance&lt;/strong&gt; – Updated templates and Claude workflow docs to describe the primary-repo hand-off during merges and reinforce the feature-worktree best practice.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;030---2025-11-02&quot;&gt;[0.3.0] - 2025-11-02&lt;/h2&gt;
&lt;h3 id=&quot;added-62&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;pip Installation Instructions&lt;/strong&gt; – All documentation now includes pip installation commands alongside uv, making Spec Kitty accessible to users who prefer traditional Python package management.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Multiple Installation Methods&lt;/strong&gt; – Documented three installation paths: PyPI (stable), GitHub (development), and one-time usage (pipx/uvx).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-62&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Documentation Consistency&lt;/strong&gt; – Updated README.md, docs/index.md, docs/installation.md, and docs/quickstart.md to provide both pip and uv commands throughout.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Installation Recommendations&lt;/strong&gt; – PyPI installation now marked as recommended for stable releases, with GitHub source for development versions.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-82&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Packaging Issues&lt;/strong&gt; – Removed duplicate &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt; force-include that caused “Duplicate filename in local headers” errors on PyPI.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Test Dependencies&lt;/strong&gt; – Added &lt;code dir=&quot;auto&quot;&gt;pip install -e .[test]&lt;/code&gt; to workflows to ensure all project dependencies available for tests.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0220---2025-11-02&quot;&gt;[0.2.20] - 2025-11-02&lt;/h2&gt;
&lt;h3 id=&quot;added-63&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Automated PyPI Release Pipeline&lt;/strong&gt; – Tag-triggered GitHub Actions workflow automatically builds, validates, and publishes releases to PyPI using &lt;code dir=&quot;auto&quot;&gt;PYPI_API_TOKEN&lt;/code&gt; secret, eliminating manual publish steps.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release Validation Tooling&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;scripts/release/validate_release.py&lt;/code&gt; CLI enforces semantic version progression, changelog completeness, and version/tag alignment in both branch and tag modes with actionable error messages.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release Readiness Guardrails&lt;/strong&gt; – Pull request workflow validates version bumps, changelog entries, and test passage before merge; protect-main workflow blocks direct pushes to main branch.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Comprehensive Release Documentation&lt;/strong&gt; – Complete maintainer guides covering secret management, branch protection, troubleshooting, and step-by-step release workflows in README, docs, and inline help.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Enhanced PyPI Metadata&lt;/strong&gt; – Added project URLs (repository, issues, docs, changelog), keywords, classifiers, and license information to improve PyPI discoverability and presentation.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Changelog Extraction&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;scripts/release/extract_changelog.py&lt;/code&gt; automatically extracts version-specific release notes for GitHub Releases.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Release Test Suite&lt;/strong&gt; – 4 pytest tests validate branch mode, tag mode, changelog parsing, and version regression detection.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-63&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;GitHub Actions Workflows&lt;/strong&gt; – Replaced legacy release workflow with modern PyPI automation supporting validation, building, checksums, GitHub Releases, and secure publishing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Documentation Structure&lt;/strong&gt; – Added dedicated releases section to docs with readiness checklist, workflow references, and troubleshooting guides; updated table of contents.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;security-6&quot;&gt;Security&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Secret Hygiene&lt;/strong&gt; – PyPI credentials exclusively stored in GitHub Actions secrets with rotation guidance; no tokens in repository or logs; workflows sanitize outputs.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Workflow Permissions&lt;/strong&gt; – Explicit least-privilege permissions in all workflows (contents:write, id-token:write for releases; contents:read for guards).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;023---2025-10-29&quot;&gt;[0.2.3] - 2025-10-29&lt;/h2&gt;
&lt;h3 id=&quot;added-64&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission system assets&lt;/strong&gt; – Bundled Software Dev Kitty and Deep Research Kitty mission definitions (commands, templates, constitutions) directly in the CLI package so &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; can hydrate missions without a network call.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-64&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Synced mission templates between the repository and packaged wheel to keep &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.*&lt;/code&gt; commands consistent across &lt;code dir=&quot;auto&quot;&gt;--ai&lt;/code&gt; choices.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;022---2025-10-29&quot;&gt;[0.2.2] - 2025-10-29&lt;/h2&gt;
&lt;h3 id=&quot;added-65&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Phase 0 Research command&lt;/strong&gt; – &lt;code dir=&quot;auto&quot;&gt;spec-kitty research&lt;/code&gt; (and &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.research&lt;/code&gt;) scaffolds &lt;code dir=&quot;auto&quot;&gt;research.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;data-model.md&lt;/code&gt;, and CSV evidence logs using mission-aware templates so Deep Research Kitty teams can execute discovery workflows without leaving the guided process.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission templates for research&lt;/strong&gt; – Deep Research Kitty now ships reusable templates for research decisions, data models, and evidence capture packaged inside the Python wheel.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-65&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; guidance, plan command instructions, and README workflow to include the new research phase between planning and task generation.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;021---2025-10-29&quot;&gt;[0.2.1] - 2025-10-29&lt;/h2&gt;
&lt;h3 id=&quot;added-66&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Mission picker in init&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now prompts for a mission (or accepts &lt;code dir=&quot;auto&quot;&gt;--mission&lt;/code&gt;) so projects start with Software Dev Kitty, Deep Research Kitty, or another bundled mission and record the choice in &lt;code dir=&quot;auto&quot;&gt;.kittify/active-mission&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-66&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Highlight the active mission in the post-init guidance while keeping the Codex export step as the final instruction.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;020---2025-10-28&quot;&gt;[0.2.0] - 2025-10-28&lt;/h2&gt;
&lt;h3 id=&quot;added-67&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;New &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.merge&lt;/code&gt; command&lt;/strong&gt; - Completes the workflow by merging features into main branch and cleaning up worktrees automatically. Supports multiple merge strategies (merge, squash, rebase), optional push to origin, and configurable cleanup of worktrees and branches.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Worktree Strategy documentation&lt;/strong&gt; - Added comprehensive guide to the opinionated worktree approach for parallel feature development.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Dashboard screenshots&lt;/strong&gt; - Added dashboard-kanban.png and dashboard-overview.png showcasing the real-time kanban board.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Real-Time Dashboard section&lt;/strong&gt; - Added prominent dashboard documentation “above the fold” in README with screenshots and feature highlights.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission management CLI&lt;/strong&gt; - &lt;code dir=&quot;auto&quot;&gt;spec-kitty mission list|current|switch|info&lt;/code&gt; for inspecting and activating domain-specific missions inside a project.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Deep Research Kitty mission&lt;/strong&gt; - Research-focused templates (spec, plan, tasks, findings, prompts) and command guardrails for evidence-driven work.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Mission packaging&lt;/strong&gt; - Missions are now bundled in release archives and Python wheels so project initialization copies &lt;code dir=&quot;auto&quot;&gt;.kittify/missions&lt;/code&gt; automatically.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-67&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Updated command list in init output to show workflow order and include merge command.&lt;/li&gt;
&lt;li&gt;Updated &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.accept&lt;/code&gt; description to clarify it verifies (not merges) features.&lt;/li&gt;
&lt;li&gt;Reordered slash commands documentation to reflect actual execution workflow.&lt;/li&gt;
&lt;li&gt;Updated maintainers to reflect fork ownership.&lt;/li&gt;
&lt;li&gt;Updated all repository references from &lt;code dir=&quot;auto&quot;&gt;spec-kitty/spec-kitty&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;Priivacy-ai/spec-kitty&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Updated installation instructions to use GitHub repository URL instead of local directory.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;fixed-83&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Removed invalid &lt;code dir=&quot;auto&quot;&gt;multiple=True&lt;/code&gt; parameter from &lt;code dir=&quot;auto&quot;&gt;typer.Option()&lt;/code&gt; in accept command that caused TypeError on CLI startup.&lt;/li&gt;
&lt;li&gt;Fixed “nine articles” claim in spec-driven.md to “core articles” (only 6 are documented).&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;removed-9&quot;&gt;Removed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Removed SECURITY.md (GitHub-specific security policies).&lt;/li&gt;
&lt;li&gt;Removed CODE_OF_CONDUCT.md (GitHub-specific contact information).&lt;/li&gt;
&lt;li&gt;Removed video overview section from README (outdated content).&lt;/li&gt;
&lt;li&gt;Removed plant emoji (🌱) branding from all documentation and code.&lt;/li&gt;
&lt;li&gt;Replaced logo_small.webp and logo_large.webp with actual spec-kitty cat logo.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;013---2025-10-28&quot;&gt;[0.1.3] - 2025-10-28&lt;/h2&gt;
&lt;h3 id=&quot;fixed-84&quot;&gt;Fixed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Removed invalid &lt;code dir=&quot;auto&quot;&gt;multiple=True&lt;/code&gt; parameter from &lt;code dir=&quot;auto&quot;&gt;typer.Option()&lt;/code&gt; in accept command that caused TypeError on CLI startup.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;012---2025-10-28&quot;&gt;[0.1.2] - 2025-10-28&lt;/h2&gt;
&lt;h3 id=&quot;changed-68&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Rebranded the CLI command prefix from &lt;code dir=&quot;auto&quot;&gt;speckitty&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt;, including package metadata and documentation references.&lt;/li&gt;
&lt;li&gt;Migrated template directories from &lt;code dir=&quot;auto&quot;&gt;.specify&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt; and feature storage from &lt;code dir=&quot;auto&quot;&gt;/specs&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;/kitty-specs&lt;/code&gt; to avoid namespace conflicts with Spec Kit.&lt;/li&gt;
&lt;li&gt;Updated environment variables, helper scripts, and dashboards to align with the new &lt;code dir=&quot;auto&quot;&gt;.kittify&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;kitty-specs&lt;/code&gt; conventions.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;011---2025-10-07&quot;&gt;[0.1.1] - 2025-10-07&lt;/h2&gt;
&lt;h3 id=&quot;added-68&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;New &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.accept&lt;/code&gt; command (and &lt;code dir=&quot;auto&quot;&gt;spec-kitty accept&lt;/code&gt;) for feature-level acceptance: validates kanban state, frontmatter metadata, and artifacts; records acceptance metadata in &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;; prints merge/cleanup instructions; and supports PR or local workflows across every agent.&lt;/li&gt;
&lt;li&gt;Acceptance helper scripts (&lt;code dir=&quot;auto&quot;&gt;accept-feature.sh&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;.ps1&lt;/code&gt;) and expanded &lt;code dir=&quot;auto&quot;&gt;tasks_cli&lt;/code&gt; utilities (&lt;code dir=&quot;auto&quot;&gt;status&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;verify&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;) for automation and integration with AI agents.&lt;/li&gt;
&lt;li&gt;Worktree-aware bootstrap workflow now defaults to creating per-feature worktrees, enabling parallel feature development with isolated sandboxes.&lt;/li&gt;
&lt;li&gt;Implementation prompts now require operating inside the feature’s worktree and rely on the lane helper scripts for moves/metadata, eliminating &lt;code dir=&quot;auto&quot;&gt;git mv&lt;/code&gt; conflicts; the dashboard also surfaces active/expected worktree paths.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-69&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.clarify&lt;/code&gt; now run fully conversational interviews—asking one question at a time, tracking internal coverage without rendering markdown tables, and only proceeding once summaries are confirmed—while continuing to resolve helper scripts via the &lt;code dir=&quot;auto&quot;&gt;.kittify/scripts/...&lt;/code&gt; paths.&lt;/li&gt;
&lt;li&gt;Added proportionality guidance so discovery, planning, and clarification depth scales with feature complexity (e.g., lightweight tic-tac-toe flows vs. an operating system build).&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.tasks&lt;/code&gt; now produces both &lt;code dir=&quot;auto&quot;&gt;tasks.md&lt;/code&gt; and the kanban prompt files in one pass; the separate &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.task-prompts&lt;/code&gt; command has been removed.&lt;/li&gt;
&lt;li&gt;Tasks are grouped into at most ten work packages with bundled prompts, reducing file churn and making prompt generation LLM-friendly.&lt;/li&gt;
&lt;li&gt;Both shell and PowerShell feature bootstrap scripts now stop with guidance to return &lt;code dir=&quot;auto&quot;&gt;WAITING_FOR_DISCOVERY_INPUT&lt;/code&gt; when invoked without a confirmed feature description, aligning with the new discovery workflow.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;010---2025-10-07&quot;&gt;[0.1.0] - 2025-10-07&lt;/h2&gt;
&lt;h3 id=&quot;changed-70&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.specify&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.plan&lt;/code&gt; now enforce mandatory discovery interviews, pausing until you answer their question sets before any files are written.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;/spec-kitty.implement&lt;/code&gt; now enforces the kanban workflow (planned → doing → for_review) with blocking validation, new helper scripts, and a task workflow quick reference.&lt;/li&gt;
&lt;li&gt;Removed the legacy &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; entrypoint; the CLI is now invoked exclusively via &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Updated installation instructions and scripts to use the new &lt;code dir=&quot;auto&quot;&gt;spec-kitty-cli&lt;/code&gt; package name and command.&lt;/li&gt;
&lt;li&gt;Simplified local template overrides to use the &lt;code dir=&quot;auto&quot;&gt;SPEC_KITTY_TEMPLATE_ROOT&lt;/code&gt; environment variable only.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0020---2025-10-07&quot;&gt;[0.0.20] - 2025-10-07&lt;/h2&gt;
&lt;h3 id=&quot;changed-71&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Renamed the primary CLI entrypoint to &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; and temporarily exposed a legacy &lt;code dir=&quot;auto&quot;&gt;specify&lt;/code&gt; alias for backwards compatibility.&lt;/li&gt;
&lt;li&gt;Refreshed documentation, scripts, and examples to use the &lt;code dir=&quot;auto&quot;&gt;spec-kitty&lt;/code&gt; command by default.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0019---2025-10-07&quot;&gt;[0.0.19] - 2025-10-07&lt;/h2&gt;
&lt;h3 id=&quot;changed-72&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Rebranded the project as Spec Kitty, updating CLI defaults, docs, and scripts while acknowledging the original GitHub Spec Kit lineage.&lt;/li&gt;
&lt;li&gt;Renamed all slash-command prefixes and generated artifact names from &lt;code dir=&quot;auto&quot;&gt;/speckit.*&lt;/code&gt; to &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.*&lt;/code&gt; to match the new branding.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;added-69&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Refreshed CLI banner text and tagline to reflect spec-kitty branding.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;0018---2025-10-06&quot;&gt;[0.0.18] - 2025-10-06&lt;/h2&gt;
&lt;h3 id=&quot;added-70&quot;&gt;Added&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;Support for using &lt;code dir=&quot;auto&quot;&gt;.&lt;/code&gt; as a shorthand for current directory in &lt;code dir=&quot;auto&quot;&gt;spec-kitty init .&lt;/code&gt; command, equivalent to &lt;code dir=&quot;auto&quot;&gt;--here&lt;/code&gt; flag but more intuitive for users.&lt;/li&gt;
&lt;li&gt;Use the &lt;code dir=&quot;auto&quot;&gt;/spec-kitty.&lt;/code&gt; command prefix to easily discover Spec Kitty-related commands.&lt;/li&gt;
&lt;li&gt;Refactor the prompts and templates to simplify their capabilities and how they are tracked. No more polluting things with tests when they are not needed.&lt;/li&gt;
&lt;li&gt;Ensure that tasks are created per user story (simplifies testing and validation).&lt;/li&gt;
&lt;li&gt;Add support for Visual Studio Code prompt shortcuts and automatic script execution.&lt;/li&gt;
&lt;li&gt;Allow &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; to bootstrap multiple AI assistants in one run (interactive multi-select or comma-separated &lt;code dir=&quot;auto&quot;&gt;--ai&lt;/code&gt; value).&lt;/li&gt;
&lt;li&gt;When running from a local checkout, &lt;code dir=&quot;auto&quot;&gt;spec-kitty init&lt;/code&gt; now copies templates directly instead of downloading release archives, so new commands are immediately available.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;changed-73&quot;&gt;Changed&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;All command files now prefixed with &lt;code dir=&quot;auto&quot;&gt;spec-kitty.&lt;/code&gt; (e.g., &lt;code dir=&quot;auto&quot;&gt;spec-kitty.specify.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;spec-kitty.plan.md&lt;/code&gt;) for better discoverability and differentiation in IDE/CLI command palettes and file explorers&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
