<?xml version="1.0" encoding="utf-8"?>
<entry xmlns="http://www.w3.org/2005/Atom" xml:base="https://docs.spec-kitty.ai/adr/3.x/2026-06-25-1-terminal-artifact-durable-home-teardown/">
  <id>https://docs.spec-kitty.ai/adr/3.x/2026-06-25-1-terminal-artifact-durable-home-teardown/</id>
  <title>ADR: Terminal-Artifact Durable Home + Topology-Aware Teardown Contract</title>
  <updated>2026-06-25T00:00:00.000Z</updated>
  <author><name>Spec Kitty</name></author>
  <link rel="alternate" type="text/html" href="https://docs.spec-kitty.ai/adr/3.x/2026-06-25-1-terminal-artifact-durable-home-teardown/"/>
  <summary>Terminal artifacts such as `retrospective.yaml` become PRIMARY-partition kinds with a tracked durable home, and worktree teardown is ordered after they persist.</summary>
  <content type="html">&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/retrospective/*&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;src/specify_cli/cli/commands/{merge,mission_type}.py&lt;/code&gt;
&lt;strong&gt;Tracker&lt;/strong&gt;: &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2119&quot;&gt;#2119&lt;/a&gt; · &lt;strong&gt;&lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/2136&quot;&gt;#2136&lt;/a&gt;&lt;/strong&gt; (handle-canonicalization, folded as FR-011) · parent &lt;a href=&quot;https://github.com/Priivacy-ai/spec-kitty/issues/1878&quot;&gt;#1878&lt;/a&gt;
&lt;strong&gt;Precedents&lt;/strong&gt;: &lt;a href=&quot;/adr/3.x/2026-06-24-1-kind-and-topology-aware-artifact-placement/&quot;&gt;kind-and-topology-aware artifact placement&lt;/a&gt; (#2101/#2090);
&lt;a href=&quot;/adr/3.x/2026-06-19-1-coord-empty-surface-fallback/&quot;&gt;coord-empty surface fallback&lt;/a&gt; (#1716, the read twin)&lt;/p&gt;
&lt;hr&gt;
&lt;h2 id=&quot;context&quot;&gt;Context&lt;/h2&gt;
&lt;p&gt;A coordination-topology mission writes its &lt;strong&gt;terminal artifact&lt;/strong&gt; — &lt;code dir=&quot;auto&quot;&gt;retrospective.yaml&lt;/code&gt; — into the
ephemeral coordination worktree, resolved through a coordination-topology-aware resolver
(&lt;code dir=&quot;auto&quot;&gt;resolve_feature_dir_for_slug&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;resolve_feature_dir_for_mission&lt;/code&gt;). On close or merge, that worktree is
torn down and the retrospective is &lt;strong&gt;silently lost&lt;/strong&gt;. The CLOSED #1771 moved the home to
&lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt; but kept the coord-aware resolver, so the divergence survived — #2119 is its residual.&lt;/p&gt;
&lt;p&gt;This is the &lt;strong&gt;write-surface twin&lt;/strong&gt; of a problem the read side already solved: planning-artifact &lt;em&gt;reads&lt;/em&gt; were
re-pointed to the primary surface via the kind-aware &lt;code dir=&quot;auto&quot;&gt;MissionArtifactKind&lt;/code&gt; partition (#2106/#2101), and the
coord-empty read fallback was made loud (the read-twin ADR above). The terminal-artifact &lt;em&gt;write&lt;/em&gt; home had no
equivalent authority, and teardown had no ordering guarantee with respect to artifact persistence.&lt;/p&gt;
&lt;p&gt;Three structural faults compound it:
0. &lt;strong&gt;Handle-blind PRIMARY entry points (#2136).&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;:1212&lt;/code&gt;) is a
topology-blind primitive (handle-blind by contract — docstring &lt;code dir=&quot;auto&quot;&gt;:1213&lt;/code&gt;): it does a raw literal compose
(&lt;code dir=&quot;auto&quot;&gt;:1240&lt;/code&gt;). Its callers on the PRIMARY path — the kind-aware read seam &lt;code dir=&quot;auto&quot;&gt;resolve_planning_read_dir&lt;/code&gt;’s PRIMARY
leg (&lt;code dir=&quot;auto&quot;&gt;:1306&lt;/code&gt;) and the retrospective write — pass it a &lt;em&gt;raw&lt;/em&gt; handle, so 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 resolves
to a &lt;em&gt;different&lt;/em&gt; dir than the canonical &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt;. #2136 names this “the same root behind #2119”:
placement is only as correct as the handle is canonical, and today these entry points do not canonicalize
before composing. (The primitive cannot self-canonicalize: &lt;code dir=&quot;auto&quot;&gt;_canonicalize_bare_modern_handle:418&lt;/code&gt; calls it
at &lt;code dir=&quot;auto&quot;&gt;:454&lt;/code&gt; → recursion. The cure is caller-side, mirroring the live exemplars &lt;code dir=&quot;auto&quot;&gt;:1204&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;:1208&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;:820&lt;/code&gt;.)&lt;/p&gt;
&lt;ol&gt;
&lt;li&gt;&lt;strong&gt;Six divergent home-resolution sites&lt;/strong&gt; (5 coord-aware resolvers + 1 event-payload path string that
hardcodes &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;id&gt;/&lt;/code&gt;) — no single authority.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Three duplicated coordination-teardown blocks&lt;/strong&gt;, one of which (merge) destroys the worktree &lt;em&gt;before&lt;/em&gt; the
retrospective postcondition runs; &lt;code dir=&quot;auto&quot;&gt;close --discard&lt;/code&gt; has no persist step at all.&lt;/li&gt;
&lt;/ol&gt;
&lt;p&gt;&lt;strong&gt;Landed-base note (2026-06-25).&lt;/strong&gt; PR &lt;strong&gt;#2121 (#2120)&lt;/strong&gt; landed the close-path teardown helper
&lt;code dir=&quot;auto&quot;&gt;mission_type.py:_teardown_coordination_worktree&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;:904&lt;/code&gt;, the canonical seam-anchor — a destruction-completeness
verifier &lt;code dir=&quot;auto&quot;&gt;_verify_discard_complete&lt;/code&gt; + a &lt;code dir=&quot;auto&quot;&gt;_flatten_discarded_mission&lt;/code&gt; step, but &lt;strong&gt;NO persistence ordering&lt;/strong&gt;), and
PR &lt;strong&gt;#2129 (#2127)&lt;/strong&gt; landed the lane exact-set (&lt;code dir=&quot;auto&quot;&gt;_remove_lane_worktrees&lt;/code&gt; exact-name +
&lt;code dir=&quot;auto&quot;&gt;_verify_discard_complete&lt;/code&gt; sibling-safe). The persist-before-destroy gap (binding B) is precisely what #2121
left un-addressed — #2121/#2129 &lt;em&gt;reinforced&lt;/em&gt; the destruction completeness without adding persistence ordering.
&lt;strong&gt;PR #2133 (#2057) has now MERGED&lt;/strong&gt; (along with #2114/#2134/#2135) — its &lt;code dir=&quot;auto&quot;&gt;cli/commands/merge.py&lt;/code&gt; god-module
decomposition RELOCATED the merge-path teardown anchor into &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;merge/executor.py:795&lt;/code&gt;&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;_phase_cleanup_worktrees_and_branches&lt;/code&gt; cleanup phase) but &lt;strong&gt;left the &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; teardown in
&lt;code dir=&quot;auto&quot;&gt;cli/commands/merge.py:270&lt;/code&gt;&lt;/strong&gt; (it did NOT migrate into &lt;code dir=&quot;auto&quot;&gt;merge/&lt;/code&gt;), and it shipped
&lt;code dir=&quot;auto&quot;&gt;test_phase_cleanup_coord_teardown_failure_is_non_fatal&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;tests/merge/test_executor_coverage.py:616&lt;/code&gt;). With no
open-PR gate remaining, this decision is delivered as &lt;strong&gt;one slice&lt;/strong&gt; of one mission — both bindings plan against
the settled base (&lt;code dir=&quot;auto&quot;&gt;upstream/main e36547461&lt;/code&gt;).&lt;/p&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;Adopt a &lt;strong&gt;Terminal-Artifact Durable Home + Topology-Aware Teardown Contract&lt;/strong&gt; with two bindings:&lt;/p&gt;
&lt;h3 id=&quot;binding-a--terminal-artifacts-resolve-to-a-durable-handle-safe-primary-home-via-the-kind-partition&quot;&gt;Binding A — Terminal artifacts resolve to a durable, HANDLE-SAFE PRIMARY home via the kind partition&lt;/h3&gt;
&lt;p&gt;Terminal artifacts (today: &lt;code dir=&quot;auto&quot;&gt;retrospective.yaml&lt;/code&gt;) are PRIMARY-partition artifacts. A &lt;code dir=&quot;auto&quot;&gt;RETROSPECTIVE&lt;/code&gt; member is
added to &lt;code dir=&quot;auto&quot;&gt;_PRIMARY_ARTIFACT_KINDS&lt;/code&gt;, and &lt;strong&gt;all&lt;/strong&gt; home-resolution sites route through the single primary-anchored
placement authority — modeled on the &lt;strong&gt;topology-blind &lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt;&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/missions/_read_path_resolver.py:1212&lt;/code&gt;) gated by &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;is_primary_artifact_kind&lt;/code&gt;&lt;/strong&gt;
(&lt;code dir=&quot;auto&quot;&gt;src/mission_runtime/artifacts.py:220&lt;/code&gt;). The topology-aware &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;resolve_status_surface&lt;/code&gt; is explicitly REJECTED
as the write exemplar&lt;/strong&gt; (it would reproduce the coord-routing bug — it is read-side only). The home is the
tracked &lt;code dir=&quot;auto&quot;&gt;kitty-specs/&amp;#x3C;slug&gt;/&lt;/code&gt; — &lt;strong&gt;not&lt;/strong&gt; a gitignored &lt;code dir=&quot;auto&quot;&gt;.kittify/&lt;/code&gt; location — preserving #1771’s
tracked/reviewable intent. No bespoke resolver is introduced (unification-not-parity).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Handle-safety at the PRIMARY entry points (#2136, the foundation of this binding) — caller-canonicalization,
NOT seam-internal.&lt;/strong&gt; 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 MUST be canonicalized to the canonical &lt;code dir=&quot;auto&quot;&gt;&amp;#x3C;slug&gt;-&amp;#x3C;mid8&gt;&lt;/code&gt; dir
&lt;strong&gt;before&lt;/strong&gt; it reaches the topology-blind compose. The placement primitive &lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt;
(&lt;code dir=&quot;auto&quot;&gt;:1212&lt;/code&gt;) is &lt;strong&gt;deliberately handle-blind by contract&lt;/strong&gt; (docstring &lt;code dir=&quot;auto&quot;&gt;:1213&lt;/code&gt;) and &lt;strong&gt;stays so&lt;/strong&gt;: it cannot
canonicalize internally, because &lt;code dir=&quot;auto&quot;&gt;_canonicalize_bare_modern_handle&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;:418&lt;/code&gt;) itself calls
&lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt; at &lt;code dir=&quot;auto&quot;&gt;:454&lt;/code&gt; — folding canonicalization into the primitive is &lt;strong&gt;infinite
recursion&lt;/strong&gt;. The cure therefore lives in the &lt;strong&gt;callers&lt;/strong&gt;, mirroring the EXISTING live exemplars &lt;code dir=&quot;auto&quot;&gt;:1204&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;:1208&lt;/code&gt;
and &lt;code dir=&quot;auto&quot;&gt;:820&lt;/code&gt;, which canonicalize via &lt;code dir=&quot;auto&quot;&gt;_canonicalize_bare_modern_handle&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;:418&lt;/code&gt; → &lt;code dir=&quot;auto&quot;&gt;_canonicalize_handle&lt;/code&gt; &lt;code dir=&quot;auto&quot;&gt;:467&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;→&lt;code dir=&quot;auto&quot;&gt;mid8&lt;/code&gt;→numeric→&lt;code dir=&quot;auto&quot;&gt;slug&lt;/code&gt;) and pass the &lt;em&gt;canonical&lt;/em&gt; handle DOWN to the blind compose. Two entry points
are routed through this canonicalization: (1) the kind-aware read seam &lt;code dir=&quot;auto&quot;&gt;resolve_planning_read_dir&lt;/code&gt;’s PRIMARY
leg (&lt;code dir=&quot;auto&quot;&gt;:1306&lt;/code&gt;), and (2) the retrospective WRITE placement (FR-001/FR-003 sites). Both reuse the existing
identity machinery — &lt;strong&gt;no parallel resolver, no silent fallback&lt;/strong&gt; (an ambiguous handle raises
&lt;code dir=&quot;auto&quot;&gt;MissionSelectorAmbiguous&lt;/code&gt;, WP07/C-009), and the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;-present / unresolvable-handle short-circuit legs
stay no-ops. Today the raw read leg (&lt;code dir=&quot;auto&quot;&gt;:1306&lt;/code&gt;) and the raw write composition feed the blind primitive an
un-canonicalized handle, so a bare handle silently diverges from the canonical dir — #2136 identifies this as
“the same root behind #2119.” Canonicalizing at both entry points makes the placement authority correct &lt;strong&gt;by
construction&lt;/strong&gt; for every PRIMARY read/write, without ever mutating the blind primitive’s contract.&lt;/p&gt;
&lt;h3 id=&quot;binding-b--topology-teardown-is-persist-before-destroy-per-path-orderings&quot;&gt;Binding B — Topology teardown is persist-before-destroy (per-path orderings)&lt;/h3&gt;
&lt;p&gt;Coordination teardown is a single shared seam whose load-bearing invariant is &lt;strong&gt;persist-before-destroy&lt;/strong&gt;: the
terminal artifact is persisted to its durable home BEFORE any worktree is destroyed, and &lt;strong&gt;persist runs OUTSIDE
the best-effort &lt;code dir=&quot;auto&quot;&gt;except Exception&lt;/code&gt; swallow&lt;/strong&gt; so a persistence failure is never absorbed by the destroy handler.
The exact step order differs by path, because the discard path carries a pre-existing &lt;strong&gt;verify-before-flatten&lt;/strong&gt;
invariant the seam MUST NOT break (&lt;code dir=&quot;auto&quot;&gt;_verify_discard_complete&lt;/code&gt; reads &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;,
which &lt;code dir=&quot;auto&quot;&gt;_flatten_discarded_mission&lt;/code&gt; then clears):&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Merge path:&lt;/strong&gt; &lt;strong&gt;persist → destroy&lt;/strong&gt; (no verify/flatten step on this path).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Discard / close path:&lt;/strong&gt; &lt;strong&gt;persist → destroy → verify → flatten&lt;/strong&gt; — the persist hook is hoisted ahead of the
destructive &lt;code dir=&quot;auto&quot;&gt;_discard_mission&lt;/code&gt; call (&lt;code dir=&quot;auto&quot;&gt;mission_type.py:623&lt;/code&gt;, which contains the destroy at &lt;code dir=&quot;auto&quot;&gt;:676&lt;/code&gt;); the
existing &lt;code dir=&quot;auto&quot;&gt;destroy → verify(:634) → flatten(:639)&lt;/code&gt; sequence is PRESERVED (flatten stays AFTER verify; the seam
does NOT move flatten ahead of destroy on this path).&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;In both paths the destroy step never runs before persist completes. WP04 reconciles these orderings; the seam’s
docstring records the per-path step order and confirms alignment with this binding.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Seam-anchor (live, post-#2133).&lt;/strong&gt; The “one shared seam” binding unifies the three live
&lt;code dir=&quot;auto&quot;&gt;CoordinationWorkspace.teardown(&lt;/code&gt; sites: &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;merge/executor.py:795&lt;/code&gt;&lt;/strong&gt; (the &lt;code dir=&quot;auto&quot;&gt;_phase_cleanup_worktrees_and_branches&lt;/code&gt;
cleanup phase), &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;cli/commands/merge.py:270&lt;/code&gt;&lt;/strong&gt; (the &lt;code dir=&quot;auto&quot;&gt;--abort&lt;/code&gt; helper — #2133 left this in &lt;code dir=&quot;auto&quot;&gt;cli/&lt;/code&gt;, it did NOT
migrate into &lt;code dir=&quot;auto&quot;&gt;merge/&lt;/code&gt;), and &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;mission_type._teardown_coordination_worktree&lt;/code&gt;&lt;/strong&gt; (&lt;code dir=&quot;auto&quot;&gt;:904&lt;/code&gt;, call &lt;code dir=&quot;auto&quot;&gt;:910&lt;/code&gt;). Because
these span TWO packages plus &lt;code dir=&quot;auto&quot;&gt;mission_type&lt;/code&gt;, the seam lives in &lt;strong&gt;&lt;code dir=&quot;auto&quot;&gt;coordination/&lt;/code&gt;&lt;/strong&gt; (near &lt;code dir=&quot;auto&quot;&gt;CoordinationWorkspace&lt;/code&gt;),
not in &lt;code dir=&quot;auto&quot;&gt;merge/&lt;/code&gt;. The &lt;em&gt;decision&lt;/em&gt; is unchanged; only the &lt;em&gt;cited anchors&lt;/em&gt; moved when #2133 merged.
Lane-worktree destruction already targets &lt;strong&gt;exact mid8-anchored names&lt;/strong&gt; from &lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt; (never a slug-prefix
match) — shipped on the base by #2129; this binding inherits that invariant rather than re-implementing it.&lt;/p&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Positive:&lt;/strong&gt; retrospectives survive teardown for all topologies; one owning authority for terminal-artifact
placement (future terminal artifacts inherit it); the persist-before-destroy invariant is provable
(destroy-step fault injection) and lives in one seam. The #2123 sibling-deletion data-loss is already closed
on the base by #2129 (regression-reference, not re-implemented here).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Positive (handle-safety at the entry points, #2136):&lt;/strong&gt; canonicalizing at the PRIMARY read seam
(&lt;code dir=&quot;auto&quot;&gt;resolve_planning_read_dir:1306&lt;/code&gt;) and the retrospective WRITE placement makes those entry points handle-safe
by construction, curing the handle-blind bug class where the handle enters the path resolution — without
mutating the blind primitive’s contract (which recursion forbids anyway). Reuses the existing identity
machinery (no parallel resolver) and preserves no-silent-fallback. The blind primitive stays the single
topology-invariant compose; only its callers are made handle-aware.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cost (verification surface):&lt;/strong&gt; the read seam feeds planning reads, status, merge, and acceptance, so the
change is verified against the full &lt;code dir=&quot;auto&quot;&gt;tests/missions/&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;tests/integration/&lt;/code&gt; suites; the &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;-present
and unresolvable-handle short-circuit legs of &lt;code dir=&quot;auto&quot;&gt;_canonicalize_bare_modern_handle&lt;/code&gt; stay no-ops, so a canonical
or already-resolvable handle is unaffected.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Cost:&lt;/strong&gt; the teardown work (binding B) consolidates three live teardown sites that now span two packages
(&lt;code dir=&quot;auto&quot;&gt;merge/executor.py&lt;/code&gt; + &lt;code dir=&quot;auto&quot;&gt;cli/commands/merge.py&lt;/code&gt;) plus &lt;code dir=&quot;auto&quot;&gt;mission_type.py&lt;/code&gt; — so the shared seam lives in
&lt;code dir=&quot;auto&quot;&gt;coordination/&lt;/code&gt;. One new enum member + the partition entry (minimal surface).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;No-persist test (must be UPDATED, not deleted).&lt;/strong&gt; #2133 shipped
&lt;code dir=&quot;auto&quot;&gt;test_phase_cleanup_coord_teardown_failure_is_non_fatal&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;tests/merge/test_executor_coverage.py:616&lt;/code&gt;), which
asserts teardown-failure is swallowed — i.e. it hard-codes the &lt;em&gt;absence&lt;/em&gt; of persist-before-destroy. Binding B
requires that test be &lt;strong&gt;UPDATED&lt;/strong&gt; to assert persist-runs-outside-the-swallow (persist before destroy),
&lt;strong&gt;never deleted to go green&lt;/strong&gt; (DIR-041). This pre-empts a future agent deleting it to pass.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Single-slice delivery.&lt;/strong&gt; With #2133/#2114/#2134/#2135 all merged, both bindings are delivered in &lt;strong&gt;one
slice&lt;/strong&gt; against the settled base — no open-PR gate. Both bindings are UNCHANGED in shape.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Verification:&lt;/strong&gt; the binding is only credible against a &lt;strong&gt;live coord-topology mission that genuinely
diverges&lt;/strong&gt; from primary (coord surface lacks &lt;code dir=&quot;auto&quot;&gt;meta.json&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;lanes.json&lt;/code&gt;) — a stubbed/flattened fixture
reproduces the #1771 false-green and is rejected (NFR-002).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;alternatives-considered&quot;&gt;Alternatives considered&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Gitignored &lt;code dir=&quot;auto&quot;&gt;.kittify/missions/&amp;#x3C;id&gt;/&lt;/code&gt; home&lt;/strong&gt; — rejected: loses #1771’s tracked/reviewable intent; the
retrospective is a reviewable artifact, not transient state.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Reorder teardown without consolidating&lt;/strong&gt; — rejected: leaves the 3-way duplication, so the invariant
re-drifts on the next edit (it already drifted once: merge vs discard).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;A new bespoke terminal-artifact resolver&lt;/strong&gt; — rejected: a parallel authority is the split-brain we are removing.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Hard-fail retrospect on a torn-down topology&lt;/strong&gt; — rejected: that is the #2119 dead-end, not a fix.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Canonicalize INSIDE &lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt; (seam-internal) (#2136)&lt;/strong&gt; — rejected as architecturally
impossible: &lt;code dir=&quot;auto&quot;&gt;_canonicalize_bare_modern_handle&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;:418&lt;/code&gt;) calls &lt;code dir=&quot;auto&quot;&gt;primary_feature_dir_for_mission&lt;/code&gt; (&lt;code dir=&quot;auto&quot;&gt;:454&lt;/code&gt;), so
folding canonicalization into the primitive is infinite recursion; the primitive is handle-blind by contract
(&lt;code dir=&quot;auto&quot;&gt;:1213&lt;/code&gt;). The cure is caller-side at the PRIMARY entry points (read seam &lt;code dir=&quot;auto&quot;&gt;:1306&lt;/code&gt; + the retrospective write),
mirroring the live exemplars &lt;code dir=&quot;auto&quot;&gt;:1204&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;:1208&lt;/code&gt;/&lt;code dir=&quot;auto&quot;&gt;:820&lt;/code&gt;. A new bespoke identity resolver is also rejected — the
existing &lt;code dir=&quot;auto&quot;&gt;_canonicalize_bare_modern_handle&lt;/code&gt; / &lt;code dir=&quot;auto&quot;&gt;_canonicalize_handle&lt;/code&gt; machinery is reused (unification-not-parity).&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;out-of-scope-follow-on-read-surface-residual-cluster&quot;&gt;Out-of-scope follow-on (read-surface residual cluster)&lt;/h2&gt;
&lt;p&gt;Issues #2138 (decision-event payload persists slug as &lt;code dir=&quot;auto&quot;&gt;mission_id&lt;/code&gt;), #2139 (dual &lt;code dir=&quot;auto&quot;&gt;target_branch&lt;/code&gt; reader with a silent
&lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; fallback), and #2140 (&lt;code dir=&quot;auto&quot;&gt;is_committed&lt;/code&gt; spec-read coord-unaware post-#2090) are a cohesive SIBLING cluster
of surface-resolution read-surface residuals — &lt;strong&gt;explicitly OUT of this mission’s scope.&lt;/strong&gt; They are recommended
as their own small follow-on mission, or parked under the #1868/#1716 strangler epic; folding them here would
widen the bounded context past placement + teardown + the handle-safe seam.&lt;/p&gt;</content>
</entry>
