<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/4.x/2026-10-05-1-bare-slug-coordination-directory-alias/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-10-05-1-bare-slug-coordination-directory-alias/</id>
  <title>ADR: a bare-slug coordination Mission has one exact directory alias set, and one directory on the target</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/adr/4.x/2026-10-05-1-bare-slug-coordination-directory-alias/"/>
  <summary>A coordination Mission with a bare primary directory owns two directory names; one resolver pairs them from recorded identity, and consolidate folds them into one directory.</summary>
  <content type="html">&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-10-05&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (owner). Operator rulings of 2026-10-05 on the alias authority and on the end state (one directory on the target).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt; &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5651&quot;&gt;#5651&lt;/a&gt; (regression), &lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5611&quot;&gt;#5611&lt;/a&gt; (nightly red), Mission &lt;code dir=&quot;auto&quot;&gt;nightly-suites-green-01M44FEP&lt;/code&gt; (Track A, WP01 to WP04; FR-001 to FR-006, FR-017).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Readers:&lt;/strong&gt; maintainers of the consolidation and coordination code, and whoever lands this Mission’s pull request.&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;A coordination Mission whose directory under &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&lt;/code&gt; is the bare slug (no &lt;code dir=&quot;auto&quot;&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; suffix) is a genuine shape, documented in &lt;code dir=&quot;auto&quot;&gt;coordination/transaction.py::_canonical_coord_mission_slug&lt;/code&gt;. Its coordination branch still carries a canonical &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; name. Such a Mission has &lt;strong&gt;two directory names&lt;/strong&gt;: the primary directory &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt; and the composed coordination directory &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;/&lt;/code&gt;.&lt;/p&gt;
&lt;p&gt;Commit &lt;code dir=&quot;auto&quot;&gt;5b5699e500&lt;/code&gt; (“give coordination artifacts one durable home”) made &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; seed the composed directory (&lt;code dir=&quot;auto&quot;&gt;coordination/coord_seed.py::_run_merge_and_commit&lt;/code&gt; writes &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; there). Three places in the code still keyed on one name, so consolidation onto a protected target broke (#5651, the red of the nightly integration job, #5611). The failure has three layers; each hid the next:&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Commit routing.&lt;/strong&gt; The seed commit goes through the commit router, whose partition classifier compared the path’s directory name with the bare slug. It did not recognise the composed directory’s status files, grouped them with the PRIMARY partition, and the protected-branch refusal returned &lt;code dir=&quot;auto&quot;&gt;no_op_wrong_surface&lt;/code&gt;. The seed logged a warning and consolidate carried on with uncommitted files, ending in &lt;code dir=&quot;auto&quot;&gt;MERGE_UNSAFE_WORKTREE_DIRTY&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Gate.&lt;/strong&gt; With the seed committed, the reconciliation gate’s &lt;code dir=&quot;auto&quot;&gt;_is_bookkeeping&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;consolidation/reconciliation.py&lt;/code&gt;) did not treat the composed directory’s status files as bookkeeping, so the gate failed and rolled the target back.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Teardown.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;consolidation/phase_teardown.py&lt;/code&gt; read the Mission’s &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; from the coordination status directory, which holds no &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;. The &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; was empty and the coordination worktree was never destroyed.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;A fourth effect was visible only in the measurement: the squash carries the composed directory onto the target, so a Mission could end with two directories there (the primary one with all six files and the composed one with a strict subset of the event log). The composed directory holds more than the status pair: the seed carries every file of the Mission directory whose kind is not a primary-partition kind (&lt;code dir=&quot;auto&quot;&gt;coordination/coord_seed.py&lt;/code&gt;), that is the status pair, &lt;code dir=&quot;auto&quot;&gt;decisions.events.jsonl&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;acceptance-matrix.json&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;issue-matrix.json&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;issue-matrix.md&lt;/code&gt;, everything under &lt;code dir=&quot;auto&quot;&gt;traces/&lt;/code&gt;, and &lt;code dir=&quot;auto&quot;&gt;tasks/&amp;#x3C;wp&gt;/review-cycle-*.md&lt;/code&gt;. The same Mission directory in the #2709 reproduction (&lt;code dir=&quot;auto&quot;&gt;traces/mission-trace.md&lt;/code&gt;) failed the gate for that reason.&lt;/p&gt;
&lt;p&gt;Evidence: the regression bisects to &lt;code dir=&quot;auto&quot;&gt;5b5699e500&lt;/code&gt; (the sibling test passes at its parent). In this repository 0 of 50 coordination Missions have a bare primary directory, and 48 of 50 have the coordination branch equal to the Mission branch, so a composed directory rides to the target by default. The shape exists in hand-built fixtures; whether older Missions carry it is not measured (#2463 discusses them). Before this change the reproduction mocked &lt;code dir=&quot;auto&quot;&gt;commit_merge_bookkeeping&lt;/code&gt; and so never ran the real bookkeeping door; it now runs the real consolidation under both strategies with no mock of in-repository code.&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;h3 id=&quot;1-one-exact-alias-set-from-recorded-identity-resolved-in-one-place&quot;&gt;1. One exact alias set, from recorded identity, resolved in one place&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;missions/_read_path_resolver.py::mission_dir_aliases(repo_root, mission_slug)&lt;/code&gt; returns a &lt;code dir=&quot;auto&quot;&gt;frozenset&lt;/code&gt; of directory names: the slug as passed, plus the composed &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; name when the literal primary directory’s &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; records a &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; or a &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;. The composed name is built by the same composer the seed uses (verbatim, no stripping, no case folding), so the alias is byte for byte what the seed writes.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Exact, never inferred.&lt;/strong&gt; There is no prefix or suffix matching and no guess from the shape of the slug. A slug that already ends in its &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; yields a one-element set, so a canonical Mission’s bare stem is never an alias.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Safe segment only.&lt;/strong&gt; An unsafe slug, or a recorded identity whose composed name is not one safe path segment (a separator, traversal, padding, a newline), yields the one-element set. Absent, malformed or unreadable metadata also yields the one-element set; the function never raises.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Why in this module.&lt;/strong&gt; It already owns the directory composers and the primary metadata read. Resolving identity inside &lt;code dir=&quot;auto&quot;&gt;mission_runtime&lt;/code&gt; would grow that module’s shrink-only outbound ledger in a gate file that is out of scope. A new module would be a sixth composer.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Resolve once, classify purely.&lt;/strong&gt; The commit router resolves the set once per commit (&lt;code dir=&quot;auto&quot;&gt;coordination/commit_router.py::_group_files_by_partition&lt;/code&gt;, one &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; read per commit that has files) and passes the names to the pure classifiers in &lt;code dir=&quot;auto&quot;&gt;coordination/coherence.py&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;kind_across_mission_dir_names&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;is_coord_residue_churn&lt;/code&gt;). &lt;code dir=&quot;auto&quot;&gt;mission_runtime/artifacts.py&lt;/code&gt; is unchanged.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;2-the-target-ends-with-one-directory&quot;&gt;2. The target ends with one directory&lt;/h3&gt;
&lt;p&gt;Every coordination-kind file of the composed directory rides the squash onto the target. The existing bookkeeping commit removes them: &lt;code dir=&quot;auto&quot;&gt;consolidation/phase_bookkeeping.py::_phase_commit_and_assert&lt;/code&gt; calls &lt;code dir=&quot;auto&quot;&gt;_fold_alias_directory&lt;/code&gt;, which uses &lt;code dir=&quot;auto&quot;&gt;coordination_alias_files&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;assert_alias_events_preserved&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;assert_alias_files_preserved&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;remove_alias_files&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;consolidation/bookkeeping_projection.py&lt;/code&gt;.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;One predicate for “coordination-kind”.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;coordination/coherence.py::is_coordination_kind_file&lt;/code&gt; (a file the kind authority classifies to a kind that is not a primary-partition kind) is the predicate the seed uses to decide what to carry, the fold uses to decide what it may remove, and the gate leg uses to decide what is bookkeeping. The list is stated once, in the kind table.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Proof per file, all or nothing, before anything is deleted.&lt;/strong&gt; The status event log: every event id of the composed log is in the unioned primary log. &lt;code dir=&quot;auto&quot;&gt;status.json&lt;/code&gt;: a derived snapshot, rematerialised into the primary directory, no proof. Any other coordination-kind file: its bytes equal the primary directory’s file at the same relative path, in the target checkout now, or at the run’s pre-mutation target tip (&lt;code dir=&quot;auto&quot;&gt;ConsolidationState.pre_mutation_refs&lt;/code&gt;). The second leg is the one the product’s own seed makes true: the seed copies a root-checkout file into the composed directory when the coordination branch lacks it, so an untouched seed copy equals the primary file as the run found it, even if the primary file has since changed. A symbolic link is never proven. A file that is not proven raises &lt;code dir=&quot;auto&quot;&gt;AliasFileNotPreserved&lt;/code&gt; (code &lt;code dir=&quot;auto&quot;&gt;ALIAS_FILE_NOT_PRESERVED&lt;/code&gt;, all unproven files named at once); an unprovable event raises &lt;code dir=&quot;auto&quot;&gt;AliasStatusEventsNotPreserved&lt;/code&gt;. Both are &lt;code dir=&quot;auto&quot;&gt;AliasFoldRefusal&lt;/code&gt;s, rendered by &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt; with exit 1 after the rollback, with nothing deleted.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;What it removes.&lt;/strong&gt; Tracked coordination-kind files under the composed name that exist on disk, then the directories that unlinking emptied (&lt;code dir=&quot;auto&quot;&gt;rmdir&lt;/code&gt;, never recursive), up to and including the composed directory. Untracked files and every file that is not a coordination kind stay.&lt;/li&gt;
&lt;li&gt;It adds no git command and no run-state field: the door stages a tracked-but-missing path as a deletion in the same commit, and the rollback authority already covers that commit. It returns nothing for a Mission whose status directory is its primary directory.&lt;/li&gt;
&lt;li&gt;Measured through the real door: one directory on the target, the complete event set including the &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; event, the coordination branch and worktree gone, a clean root checkout. The &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; event lands in the primary directory’s log.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;3-the-reconciliation-gate-exempts-only-coordination-kind-files&quot;&gt;3. The reconciliation gate exempts only coordination-kind files&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;_is_bookkeeping&lt;/code&gt; gains one leg, &lt;code dir=&quot;auto&quot;&gt;_is_nested_alias_coordination_file&lt;/code&gt;. It applies only when the claim’s &lt;code dir=&quot;auto&quot;&gt;planning_prefix&lt;/code&gt; is a nested coordination-worktree path whose last segment (the composed name, read from the prefix, not rebuilt from the slug) differs from the Mission slug. It then accepts only a root-anchored path &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;that name&gt;/&amp;#x3C;file&gt;&lt;/code&gt;, at any depth below the directory, whose file satisfies &lt;code dir=&quot;auto&quot;&gt;is_coordination_kind_file&lt;/code&gt;. No signature or call site changes.&lt;/p&gt;
&lt;p&gt;This leg matters for &lt;code dir=&quot;auto&quot;&gt;--strategy merge&lt;/code&gt;, where the per-commit axis flags the seed, fold and &lt;code dir=&quot;auto&quot;&gt;done&lt;/code&gt; status commits, and for any squash run that does not go through the fold.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Why the alias cannot let foreign content through (the closed-world argument).&lt;/strong&gt; The gate refuses any path it cannot attribute to an approved lane, so an exemption is a hole unless it is exact. Three rules close it, and each has a negative control:&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;em&gt;The name is exact.&lt;/em&gt; It is the composed directory the claim itself names. A different &lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt; on the same slug (&lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-01KX0001&lt;/code&gt;) and another Mission’s name (&lt;code dir=&quot;auto&quot;&gt;other-mission-01KX0000&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;other-mission&lt;/code&gt;) are content and fail the gate (&lt;code dir=&quot;auto&quot;&gt;tests/consolidation/test_reconciliation.py&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_gate_fails_status_files_of_a_different_mission_directory&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;test_is_bookkeeping_keeps_non_coordination_kinds_and_foreign_names_as_content&lt;/code&gt;). A slug with no recorded identity has no alias (&lt;code dir=&quot;auto&quot;&gt;tests/specify_cli/missions/test_mission_dir_aliases.py&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;em&gt;The record kind is restricted.&lt;/em&gt; Existing code exempts a whole &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt; subtree for the primary name, so a plain alias would exempt &lt;code dir=&quot;auto&quot;&gt;spec.md&lt;/code&gt; and source under the composed name. Only coordination-kind files are exempt. &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/WP01.md&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;notes/plan.md&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;src/x.py&lt;/code&gt; under the composed name fail the gate, and an integration test commits a planning file there and shows the target rolled back and nothing torn down, under both strategies (&lt;code dir=&quot;auto&quot;&gt;tests/integration/test_merge_lane_planning_data_loss.py&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;em&gt;The prefix must be nested and the path root-anchored.&lt;/em&gt; A missing, root-form or malformed prefix leaves every verdict as before.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;4-teardown-reads-identity-from-the-primary-metadata&quot;&gt;4. Teardown reads identity from the primary metadata&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;phase_teardown.py&lt;/code&gt; loads &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt; from &lt;code dir=&quot;auto&quot;&gt;run.target_feature_dir&lt;/code&gt;, as the neighbouring code does, not from the status directory. No alias is needed there.&lt;/p&gt;
&lt;h3 id=&quot;5-a-refused-coordination-seed-commit-stops-consolidate&quot;&gt;5. A refused coordination seed commit stops consolidate&lt;/h3&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;SeedReport&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;mission_runtime/write_location.py&lt;/code&gt;) gains a defaulted field &lt;code dir=&quot;auto&quot;&gt;commit_refused&lt;/code&gt;, set in &lt;code dir=&quot;auto&quot;&gt;coord_seed.py&lt;/code&gt; when the seed commit is not applied. &lt;code dir=&quot;auto&quot;&gt;consolidation/entry_preflight.py::_resolve_run_status_dir&lt;/code&gt; reads it and raises &lt;code dir=&quot;auto&quot;&gt;_refuse_on_unapplied_seed_commit&lt;/code&gt;: exit 1, error code &lt;code dir=&quot;auto&quot;&gt;COORD_SEED_COMMIT_REFUSED&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;consolidation/_constants.py&lt;/code&gt;), before the lock, the snapshots and any teardown. The message names the uncommitted files and says they are kept. A re-run retries the commit. The “no branch moved” wording reuses &lt;code dir=&quot;auto&quot;&gt;_protected_refusal_footer&lt;/code&gt;, so it is scoped to this run when an earlier merge record exists. The files are not deleted, which keeps the seed-retry design (I-SEED-10) intact. The reviewer measured that the old behaviour lost no status events; the change replaces a misleading dirty-worktree remedy with the real cause.&lt;/p&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Alias set plus fold (chosen).&lt;/strong&gt; Keeps the composed coordination directory, fixes the three layers with one rule and restores the pre-regression end state of one directory.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;One directory name keyed on the primary directory.&lt;/strong&gt; No classifier change, but every Mission seeded since 2 October needs a read fallback to find its composed directory. Rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Alias without the fold.&lt;/strong&gt; Leaves a split status log on the target (two directories). Rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Refuse the bare-slug shape.&lt;/strong&gt; Changes a documented contract, and the shape is genuine. Rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A deletion commit before the squash.&lt;/strong&gt; Removes the coordination home mid-run and forces a re-seed. Rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Seed only when the coordination branch differs from the Mission branch.&lt;/strong&gt; 48 of 50 Missions would have no status home. Rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Filter the squash.&lt;/strong&gt; The squash is in &lt;code dir=&quot;auto&quot;&gt;lanes/consolidation.py&lt;/code&gt;, which another running Mission owns. Rejected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Thread the alias set through the claim object.&lt;/strong&gt; Edits outside the one function this Mission may change in &lt;code dir=&quot;auto&quot;&gt;reconciliation.py&lt;/code&gt;. Rejected in favour of deriving the name from &lt;code dir=&quot;auto&quot;&gt;planning_prefix&lt;/code&gt;.&lt;/li&gt;
&lt;/ol&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;A bare-slug coordination Mission consolidates onto a protected target and lands one directory. The reproduction runs the real consolidation under both strategies.&lt;/li&gt;
&lt;li&gt;The gate leg and the fold are two mechanisms for one end state, and both use the seed’s predicate for what a coordination file is. Under &lt;code dir=&quot;auto&quot;&gt;--strategy merge&lt;/code&gt; both are needed; under squash only the fold is.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;reconciliation.py&lt;/code&gt; gains one adjacent private helper next to the code mission #5668 works in. Flag it for the rebase.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;residuals-and-follow-ups&quot;&gt;Residuals and follow-ups&lt;/h3&gt;
&lt;p&gt;Each is a known gap, not a hidden one.&lt;/p&gt;

































&lt;table&gt;&lt;thead&gt;&lt;tr&gt;&lt;th&gt;Residual&lt;/th&gt;&lt;th&gt;Follow-up&lt;/th&gt;&lt;/tr&gt;&lt;/thead&gt;&lt;tbody&gt;&lt;tr&gt;&lt;td&gt;A coordination write made under the composed name AFTER the seed (a trace written, a matrix or review cycle updated during the Mission) is a file the primary directory does not hold, so the fold refuses with &lt;code dir=&quot;auto&quot;&gt;ALIAS_FILE_NOT_PRESERVED&lt;/code&gt; instead of carrying it into the primary directory. This is safe (nothing is deleted) but not complete: the post-checkpoint projection is keyed on the bare slug and never carries composed-name files. Carrying them forward, instead of refusing, is a product decision.&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5751&quot;&gt;#5751&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Resume after an interruption inside the fold still refuses for a bare-slug Mission. The refusal now says what recovers (&lt;code dir=&quot;auto&quot;&gt;consolidate --abort&lt;/code&gt;, then a fresh run), for deletions of any coordination-kind file under the composed name; making the resume itself work remains.&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5748&quot;&gt;#5748&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;With the gate leg in place, the gate no longer backstops a skipped fold under squash.&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5751&quot;&gt;#5751&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Single-name anchors remain: the post-merge porcelain invariant in &lt;code dir=&quot;auto&quot;&gt;phase_bookkeeping.py&lt;/code&gt; (pinned by a test), the second classifier caller in the acceptance package, and the dead &lt;code dir=&quot;auto&quot;&gt;planning_prefix&lt;/code&gt; leg under coordination topology.&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5751&quot;&gt;#5751&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;The fold’s preservation refusals (&lt;code dir=&quot;auto&quot;&gt;ALIAS_STATUS_EVENTS_NOT_PRESERVED&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;ALIAS_FILE_NOT_PRESERVED&lt;/code&gt;) and the refusal for an uncomposed &lt;code dir=&quot;auto&quot;&gt;coordination_branch&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;COORDINATION_WORKTREE_BRANCH_MISMATCH&lt;/code&gt;) are rendered by &lt;code dir=&quot;auto&quot;&gt;spec-kitty consolidate&lt;/code&gt;, with exit 1. The second prints no recovery command: renaming the branch and correcting &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; and &lt;code dir=&quot;auto&quot;&gt;mission_branch&lt;/code&gt; in &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; recovers only once both corrected files are committed on the target, which was not proven safe to print blind. The shape cannot be minted (&lt;code dir=&quot;auto&quot;&gt;coordination_branch_name&lt;/code&gt; always composes, and 0 of 51 coordination Missions in this repository declare it), and a coordination status write already refused it before this Mission. Remaining: the code-lane path of &lt;code dir=&quot;auto&quot;&gt;orchestrator-api consolidate-mission&lt;/code&gt; has no seed backstop (only its planning-only path reaches it, as a &lt;code dir=&quot;auto&quot;&gt;PREFLIGHT_FAILED&lt;/code&gt; envelope without the cause text), and none of these refusals is rendered there.&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5750&quot;&gt;#5750&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;tr&gt;&lt;td&gt;Several tests build Missions with a shared over-mocked helper.&lt;/td&gt;&lt;td&gt;&lt;a href=&quot;https://github.com/spec-kitty/spec-kitty/issues/5749&quot;&gt;#5749&lt;/a&gt;&lt;/td&gt;&lt;/tr&gt;&lt;/tbody&gt;&lt;/table&gt;
&lt;p&gt;Related, different mechanism (cross-reference only): #5638 (the rollback’s byte-restore leaves tracked status files dirty) and #5644 (the guard that detects committed events lost from the worktree).&lt;/p&gt;</content>
</entry>
