<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/operations/upgrade-with-live-lanes-recovery/">
  <id>https://docs.spec-kitty.ai/operations/upgrade-with-live-lanes-recovery/</id>
  <title>Recovery: consolidate, review or implement refuses after an upgrade mid-Mission</title>
  <updated>2026-10-05T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/operations/upgrade-with-live-lanes-recovery/"/>
  <summary>Recovery when spec-kitty consolidate, review or implement refuses on .kittify/metadata.yaml after an upgrade run while a Mission had live lanes.</summary>
  <content type="html">&lt;span id=&quot;recovery-consolidate-review-or-implement-refuses-after-an-upgrade-mid-mission&quot;&gt;&lt;/span&gt;
&lt;p&gt;You ran &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; on 4.0.0rc5 or earlier while a Mission had live lanes or a
coordination worktree. Now &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, a review start or an implement resume refuses on
&lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt;), a file you never edited. This page gets the
Mission moving again. It is tracked as &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5457&quot;&gt;#5457&lt;/a&gt;.&lt;/p&gt;
&lt;h2 id=&quot;symptoms&quot;&gt;Symptoms&lt;/h2&gt;
&lt;p&gt;Any one of these three refusals:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; exits 1:
&lt;code dir=&quot;auto&quot;&gt;Lane lane-b is stale: overlapping files [&apos;.gitattributes&apos;, &apos;.kittify/metadata.yaml&apos;]&lt;/code&gt;.
The printed &lt;code dir=&quot;auto&quot;&gt;git merge kitty/mission-&amp;#x3C;slug&gt;&lt;/code&gt; remedy reports “Already up to date” and the
next run refuses again.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; (and &lt;code dir=&quot;auto&quot;&gt;--resume&lt;/code&gt;) exits 1 with &lt;code dir=&quot;auto&quot;&gt;TARGET_BRANCH_CONTENT_CONFLICT&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;conflicting_path: .kittify/metadata.yaml&lt;/code&gt; when squashing into the target branch.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty agent action review WP02&lt;/code&gt; (or an implement resume) exits 1 with
&lt;code dir=&quot;auto&quot;&gt;LANE_AUTO_REBASE_FAILED: no classifier rule matched .../.worktrees/&amp;#x3C;slug&gt;-lane-b/.kittify/metadata.yaml&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;fix&quot;&gt;Fix&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;
&lt;p&gt;Install the fixed CLI (the release that carries #5457, or a checkout of it).&lt;/p&gt;
&lt;/li&gt;
&lt;li&gt;
&lt;p&gt;Re-run the command that refused, for example:&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;consolidate&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;--mission&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;slug&gt;&lt;/span&gt;&lt;/div&gt;&lt;/div&gt;&lt;/code&gt;&lt;/pre&gt;&lt;/figure&gt;&lt;/div&gt;
&lt;p&gt;or the review or implement command that failed. For &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; no other step
is needed. If the refusal names &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt;, see
&lt;a href=&quot;#when-you-will-still-see-a-refusal&quot;&gt;When you will still see a refusal&lt;/a&gt;.&lt;/p&gt;
&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;The lanes and the coordination branch still carry the divergent upgrade commits from the
earlier run. The fixed CLI resolves them at the next integration without your help:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;the stale check no longer counts &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;, nor any overlap whose content is
identical on the lane and the Mission branch (the duplicated &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; line);&lt;/li&gt;
&lt;li&gt;the merges that &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; and implement perform resolve a conflict confined to
&lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt; to the receiving side (the Mission branch, the target, the
dependent lane, or the lane that takes in the recorded planning commit);&lt;/li&gt;
&lt;li&gt;the lane sync after a coordination commit takes the incoming coordination or Mission copy
(rule &lt;code dir=&quot;auto&quot;&gt;R-TARGET-OWNED-BOOKKEEPING&lt;/code&gt;).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;Going forward, &lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt; run from the repository root checkout skips lane, Mission
and coordination worktrees. Run it from the repository root checkout, not from inside a lane
worktree: from inside one it still commits on the lane branch
(&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5747&quot;&gt;#5747&lt;/a&gt;). A lane keeps its pre-upgrade
&lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; until it integrates.&lt;/p&gt;
&lt;h2 id=&quot;what-not-to-do&quot;&gt;What not to do&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Do not run &lt;code dir=&quot;auto&quot;&gt;git reset --hard&lt;/code&gt; on a lane or the Mission branch. It discards committed work.&lt;/li&gt;
&lt;li&gt;Do not rewrite history (rebase, amend or filter the upgrade commits). The fixed CLI does not
need it, and a rewrite can strand lane work tips.&lt;/li&gt;
&lt;li&gt;Do not hand-edit &lt;code dir=&quot;auto&quot;&gt;.kittify/metadata.yaml&lt;/code&gt;. It is generated, and its records are written by
&lt;code dir=&quot;auto&quot;&gt;spec-kitty upgrade&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;Do not follow the printed &lt;code dir=&quot;auto&quot;&gt;git merge kitty/mission-&amp;#x3C;slug&gt;&lt;/code&gt; remedy for this refusal. It is a
no-op here.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;when-you-will-still-see-a-refusal&quot;&gt;When you will still see a refusal&lt;/h2&gt;
&lt;p&gt;The fix covers generated bookkeeping only. A genuine overlap on a file a work package edits,
such as &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; content that differs between lanes, &lt;code dir=&quot;auto&quot;&gt;.gitignore&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;.kittify/config.yaml&lt;/code&gt;
or source files, still stops &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;, and resolving it by hand is correct. For that
case the printed stale remedy can be a no-op after the in-run rollback.&lt;/p&gt;
&lt;p&gt;Two of these refusals are caused by the earlier upgrade and not by a work package.&lt;/p&gt;
&lt;p&gt;First, &lt;code dir=&quot;auto&quot;&gt;LANE_MOVED_AFTER_APPROVAL&lt;/code&gt; naming &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt;. The earlier upgrade committed on each
lane. If a work package was approved before that commit, &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt; sees a commit made
after approval and refuses, even though a tool made it. Send each named work package back with
the printed &lt;code dir=&quot;auto&quot;&gt;spec-kitty agent tasks move-task &amp;#x3C;WP&gt; --to in_progress --mission &amp;#x3C;slug&gt;&lt;/code&gt;, approve
it again, and re-run &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;. Attestation does not lift this refusal. See
&lt;a href=&quot;/guides/how-to/recovery/troubleshoot-merge/#a-lane-changed-after-its-work-package-was-approved&quot;&gt;A lane changed after its work package was approved&lt;/a&gt;.&lt;/p&gt;
&lt;p&gt;Second: if the
target branch’s &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; was edited after the Mission was cut, the line the earlier
upgrade appended on the target and on each lane no longer merges cleanly, and &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;
refuses with &lt;code dir=&quot;auto&quot;&gt;TARGET_BRANCH_CONTENT_CONFLICT&lt;/code&gt; on &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt;. &lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; is yours
to edit, so Spec Kitty does not pick a side. Resolve it by hand on the Mission branch: keep
the target’s version of the file and make sure the upgrade’s line appears once. Follow-up
&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5711&quot;&gt;#5711&lt;/a&gt; tracks the remedy wording.&lt;/p&gt;
&lt;h2 id=&quot;see-also&quot;&gt;See also&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;a href=&quot;/operations/recovery-index/&quot;&gt;Recovery guides&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/operations/stale-lane-seed/&quot;&gt;Stale lane seed after re-finalizing tasks&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/adr/4.x/2026-10-04-4-upgrade-writes-project-global-state-once/&quot;&gt;ADR 2026-10-04-4: upgrade writes project-global state once&lt;/a&gt;&lt;/li&gt;
&lt;li&gt;&lt;a href=&quot;/architecture/branch-target-routing/&quot;&gt;Branch-target routing&lt;/a&gt;&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
