---
type: "Operations"
title: "Recovery: consolidate, review or implement refuses after an upgrade mid-Mission"
description: "Recovery when spec-kitty consolidate, review or implement refuses on .kittify/metadata.yaml after an upgrade run while a Mission had live lanes."
status: "stable"
generated:
  by: "process:dockitty-export"
  at: "2026-10-05T00:00:00Z"
---

# Recovery: consolidate, review or implement refuses after an upgrade mid-Mission

You ran `spec-kitty upgrade` on 4.0.0rc5 or earlier while a Mission had live lanes or a
coordination worktree. Now `consolidate`, a review start or an implement resume refuses on
`.kittify/metadata.yaml` (or `.gitattributes`), a file you never edited. This page gets the
Mission moving again. It is tracked as [#5457](https://github.com/spec-kitty/spec-kitty/issues/5457).

## Symptoms

Any one of these three refusals:

- `spec-kitty consolidate` exits 1:
  `Lane lane-b is stale: overlapping files ['.gitattributes', '.kittify/metadata.yaml']`.
  The printed `git merge kitty/mission-<slug>` remedy reports "Already up to date" and the
  next run refuses again.
- `spec-kitty consolidate` (and `--resume`) exits 1 with `TARGET_BRANCH_CONTENT_CONFLICT`
  and `conflicting_path: .kittify/metadata.yaml` when squashing into the target branch.
- `spec-kitty agent action review WP02` (or an implement resume) exits 1 with
  `LANE_AUTO_REBASE_FAILED: no classifier rule matched .../.worktrees/<slug>-lane-b/.kittify/metadata.yaml`.

## Fix

1. Install the fixed CLI (the release that carries #5457, or a checkout of it).
2. Re-run the command that refused, for example:

   ```bash
   spec-kitty consolidate --mission <slug>
   ```

   or the review or implement command that failed. For `.kittify/metadata.yaml` no other step
   is needed. If the refusal names `.gitattributes`, see
   [When you will still see a refusal](#when-you-will-still-see-a-refusal).

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:

- the stale check no longer counts `.kittify/metadata.yaml`, nor any overlap whose content is
  identical on the lane and the Mission branch (the duplicated `.gitattributes` line);
- the merges that `consolidate` and implement perform resolve a conflict confined to
  `.kittify/metadata.yaml` to the receiving side (the Mission branch, the target, the
  dependent lane, or the lane that takes in the recorded planning commit);
- the lane sync after a coordination commit takes the incoming coordination or Mission copy
  (rule `R-TARGET-OWNED-BOOKKEEPING`).

Going forward, `spec-kitty upgrade` 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
([#5747](https://github.com/spec-kitty/spec-kitty/issues/5747)). A lane keeps its pre-upgrade
`.gitignore` and `.gitattributes` until it integrates.

## What not to do

- Do not run `git reset --hard` on a lane or the Mission branch. It discards committed work.
- 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.
- Do not hand-edit `.kittify/metadata.yaml`. It is generated, and its records are written by
  `spec-kitty upgrade`.
- Do not follow the printed `git merge kitty/mission-<slug>` remedy for this refusal. It is a
  no-op here.

## When you will still see a refusal

The fix covers generated bookkeeping only. A genuine overlap on a file a work package edits,
such as `.gitattributes` content that differs between lanes, `.gitignore`, `.kittify/config.yaml`
or source files, still stops `consolidate`, and resolving it by hand is correct. For that
case the printed stale remedy can be a no-op after the in-run rollback.

Two of these refusals are caused by the earlier upgrade and not by a work package.

First, `LANE_MOVED_AFTER_APPROVAL` naming `.gitattributes`. The earlier upgrade committed on each
lane. If a work package was approved before that commit, `consolidate` sees a commit made
after approval and refuses, even though a tool made it. Send each named work package back with
the printed `spec-kitty agent tasks move-task <WP> --to in_progress --mission <slug>`, approve
it again, and re-run `consolidate`. Attestation does not lift this refusal. See
[A lane changed after its work package was approved](/guides/how-to/recovery/troubleshoot-merge.md#a-lane-changed-after-its-work-package-was-approved).

Second: if the
target branch's `.gitattributes` 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 `consolidate`
refuses with `TARGET_BRANCH_CONTENT_CONFLICT` on `.gitattributes`. `.gitattributes` 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
[#5711](https://github.com/spec-kitty/spec-kitty/issues/5711) tracks the remedy wording.

## See also

- [Recovery guides](/operations/recovery-index.md)
- [Stale lane seed after re-finalizing tasks](/operations/stale-lane-seed.md)
- [ADR 2026-10-04-4: upgrade writes project-global state once](/adr/4.x/2026-10-04-4-upgrade-writes-project-global-state-once.md)
- [Branch-target routing](/architecture/branch-target-routing.md)

## Related

- [ADR: upgrade writes project-global state once, in the repository root checkout](/adr/4.x/2026-10-04-4-upgrade-writes-project-global-state-once.md)
- [Recovery guides](/operations/recovery-index.md)
- [Recovery: Stale Lane Seed After Re-Finalizing Tasks](/operations/stale-lane-seed.md)

## Audience

- [Stakeholder Persona: Maintainer](/context/audience/internal/maintainer.md) - Written for the Maintainer reader.
