<?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-11-01-2-op-lifecycle-records-are-one-file-per-record/">
  <id>https://docs.spec-kitty.ai/adr/4.x/2026-11-01-2-op-lifecycle-records-are-one-file-per-record/</id>
  <title>ADR: Op lifecycle records are one file per record</title>
  <updated>2026-11-11T00: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-11-01-2-op-lifecycle-records-are-one-file-per-record/"/>
  <summary>spec-kitty next writes each lifecycle record to its own kitty-ops/lifecycle/&lt;ulid&gt;.json; the shared lifecycle.jsonl stays readable, never written.</summary>
  <content type="html">&lt;h2 id=&quot;op-lifecycle-records-are-one-file-per-record&quot;&gt;Op lifecycle records are one file per record&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Status:&lt;/strong&gt; Accepted (2026-11-01). Operator pre-rulings of 2026-11-01 on #7003.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Date:&lt;/strong&gt; 2026-11-01&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Deciders:&lt;/strong&gt; Stijn Dejongh (operator).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Technical Story:&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;#7003: every Mission PR appended to the shared &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl&lt;/code&gt;, so two PRs in the merge
queue conflicted at its end and the second was dropped (#6804, #6843 and #6892 had to land one at a
time on 2026-11-01).&lt;/li&gt;
&lt;li&gt;Extends &lt;a href=&quot;/adr/4.x/2026-11-01-1-pull-requests-touch-no-shared-generated-files-and-land-through-a-merge-queue/&quot;&gt;ADR 2026-11-01-1&lt;/a&gt;
(pull requests touch no shared generated file) to the Op lifecycle log.&lt;/li&gt;
&lt;li&gt;Keeps the interim locked append of &lt;a href=&quot;/adr/4.x/2026-10-22-1-the-java-write-service-is-the-canonical-event-writer/&quot;&gt;ADR 2026-10-22-1&lt;/a&gt;
(#6606) for every write.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;context-and-problem-statement&quot;&gt;Context and Problem Statement&lt;/h2&gt;
&lt;p&gt;&lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; records a &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; lifecycle record when it issues an action and a paired
&lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;failed&lt;/code&gt; record when the agent reports back (&lt;code dir=&quot;auto&quot;&gt;ProfileInvocationRecord&lt;/code&gt;,
&lt;code dir=&quot;auto&quot;&gt;src/specify_cli/invocation/lifecycle.py&lt;/code&gt;). The &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; orphan report and the NFR-006 pairing rate
read them. All of them were appended to one tracked file. Any two branches that each ran &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt;
edited the end of that file, and git cannot merge two appends at the same place without a conflict.&lt;/p&gt;
&lt;p&gt;The interim &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl merge=union&lt;/code&gt; attribute fixed local merges and rebases. It is not
known that GitHub’s merge queue honours a merge driver attribute, and a union merge of two logs is
still a shared-file edit that ADR 2026-11-01-1 rules out.&lt;/p&gt;
&lt;h2 id=&quot;considered-options&quot;&gt;Considered Options&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;A. One file per record&lt;/strong&gt;, &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ulid&gt;.json&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;B. Fold lifecycle records into the per-Op files&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;op-ulid&gt;.jsonl&lt;/code&gt;, which already never
conflict.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;C. Stop tracking the lifecycle log.&lt;/strong&gt;&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;D. One file per (Mission, action) group.&lt;/strong&gt;&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;decision&quot;&gt;Decision&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Option A.&lt;/strong&gt; Each record is written to its own &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ulid&gt;.json&lt;/code&gt;, holding the record’s
one sorted-key JSON line and a line feed. No other branch writes that file, so two PRs never conflict
on lifecycle records and no merge driver is needed.&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;Name.&lt;/strong&gt; A ULID, not the record’s &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; (an ISO timestamp holds colons, which Windows refuses in a
file name). The ULID is issued monotonically within one process, so two records with the same &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt;
keep their write order.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Write.&lt;/strong&gt; Through the interim locked door (&lt;code dir=&quot;auto&quot;&gt;kernel.event_log_append.append_event_log_lines&lt;/code&gt;), with
the record directory as the family lock anchor, so lock files do not grow with the number of
records. The write refuses a final-component symlink and refuses a name that already holds content
(&lt;code dir=&quot;auto&quot;&gt;LifecycleRecordExistsError&lt;/code&gt;): a record file is created once and never rewritten.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Legacy log.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl&lt;/code&gt; stays tracked and readable, and is never written again.
It is not split into record files: that would be a migration commit touching every lifecycle record
in every project for no reader’s benefit.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Read order.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;read_lifecycle_records&lt;/code&gt; returns the legacy log’s lines in insertion order first, then
the record files sorted by (&lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; as UTC, ulid). A corrupt or unreadable record file is skipped like a
corrupt line. Pairing, the orphan report and the pairing rate give the same results on the same
records, whichever layout holds them.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Owned checkouts.&lt;/strong&gt; The owned &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; commit lists only the record files the checkout has not
committed yet (&lt;code dir=&quot;auto&quot;&gt;git status&lt;/code&gt; scoped to the record directory), never every record ever written.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Retention.&lt;/strong&gt; &lt;code dir=&quot;auto&quot;&gt;doctor event-logs&lt;/code&gt; never scans &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt;, and its path guard refuses the record
directory and the legacy log. Committed lifecycle records are never removed.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;Merge attribute.&lt;/strong&gt; The interim &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle.jsonl merge=union&lt;/code&gt; line stays in
&lt;code dir=&quot;auto&quot;&gt;.gitattributes&lt;/code&gt; while open branches still append to the legacy log: &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; no longer writes it,
but two such branches would otherwise conflict with each other at the end of the file on a rebase
or local merge. It is removed in a later change once no open branch appends to the legacy log.
Until then the &lt;code dir=&quot;auto&quot;&gt;docs-lint&lt;/code&gt; guard &lt;code dir=&quot;auto&quot;&gt;scripts/ci/check_legacy_lifecycle_log_untouched.py&lt;/code&gt; refuses a pull request whose net diff modifies the legacy log, so &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt;’s copy never changes; the guard and the union attribute are removed together once no open branch appends to it.&lt;/li&gt;
&lt;/ul&gt;
&lt;h3 id=&quot;why-not-the-others&quot;&gt;Why not the others&lt;/h3&gt;
&lt;ul&gt;
&lt;li&gt;&lt;strong&gt;B&lt;/strong&gt; needs every lifecycle record to carry exactly one Op id when it is issued. It does not:
&lt;code dir=&quot;auto&quot;&gt;ProfileInvocationRecord&lt;/code&gt; has no Op id, and &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; opens no Op (&lt;code dir=&quot;auto&quot;&gt;docs/context/ops-vs-missions.md&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;C&lt;/strong&gt; loses the history the &lt;code dir=&quot;auto&quot;&gt;doctor&lt;/code&gt; orphan report and the pairing-rate check read.&lt;/li&gt;
&lt;li&gt;&lt;strong&gt;D&lt;/strong&gt; still collides: a &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record and its completion can land from different branches, and
both would edit the same group file.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;consequences&quot;&gt;Consequences&lt;/h2&gt;
&lt;ul&gt;
&lt;li&gt;Two PRs that each ran &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; no longer conflict on lifecycle records, in the merge queue or locally.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&lt;/code&gt; grows by one small file per record. Readers list the directory once per read.&lt;/li&gt;
&lt;li&gt;A branch cut before this change still appends to the legacy log. Without the union attribute, two
such branches can still conflict there until they are rebased onto a &lt;code dir=&quot;auto&quot;&gt;main&lt;/code&gt; that has this change;
after the rebase, their next records are files.&lt;/li&gt;
&lt;li&gt;Pairing counts, the orphan count and the pairing rate do not depend on the order. Which &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt;
record of a group the orphan report names can: within the record files it follows &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt;, not write
order, which differs only when the clock steps back between two records of one group; and legacy
lines always read first, even when an older CLI appended one after record files exist.&lt;/li&gt;
&lt;li&gt;The archive preservation gate keeps admitting a byte-prefix append to the legacy log (an older CLI
still writes one) and treats every record file like any other &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; file: it may be added,
never changed.&lt;/li&gt;
&lt;li&gt;&lt;code dir=&quot;auto&quot;&gt;docs/architecture/event-ledger-writers-and-readers.md&lt;/code&gt; still names the legacy path. It is in the
frozen set of ADR 2026-10-29-1 D-9, so it is corrected in &lt;code dir=&quot;auto&quot;&gt;spec-kitty-events&lt;/code&gt;, not here.&lt;/li&gt;
&lt;/ul&gt;
&lt;h2 id=&quot;amendment-2026-11-10-an-abandoned-record-closes-a-stale-lifecycle-record-7346&quot;&gt;Amendment 2026-11-10: an abandoned record closes a stale lifecycle record (#7346)&lt;/h2&gt;
&lt;p&gt;&lt;strong&gt;Reader:&lt;/strong&gt; a maintainer who needs to know how a lifecycle record is closed when &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt;
never reports a result for it.&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Problem.&lt;/strong&gt; The only completion writer was &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; reporting a result, which also advances
the Mission. A work package whose agent stopped mid-action left its &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record open, and the
record shipped open in the pull request (#7340’s WP04).&lt;/p&gt;
&lt;p&gt;&lt;strong&gt;Decision&lt;/strong&gt; (operator rulings, Mission &lt;code dir=&quot;auto&quot;&gt;close-stale-lifecycle-records-01M72B89&lt;/code&gt;).&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The record contract gains a fourth phase, &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt;: the record was closed by
&lt;code dir=&quot;auto&quot;&gt;doctor ops --close-stale&lt;/code&gt;, not by the action’s result. It copies the &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record’s canonical
id, agent, Mission and work package, names the sweep and its threshold in &lt;code dir=&quot;auto&quot;&gt;reason&lt;/code&gt;, and carries
&lt;code dir=&quot;auto&quot;&gt;metadata.closed_by = doctor_sweep&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;metadata.closes_started_at&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; of the exact
&lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record it closes, so a later sweep pairs it with that record and never closes another.&lt;/li&gt;
&lt;li&gt;Pairing counts &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt; as a completion (&lt;code dir=&quot;auto&quot;&gt;lifecycle.COMPLETION_PHASES&lt;/code&gt;), so the orphan count,
the pairing rate and &lt;code dir=&quot;auto&quot;&gt;find_latest_unpaired_started&lt;/code&gt; treat the record as closed.&lt;/li&gt;
&lt;li&gt;One record-level pairing authority, &lt;code dir=&quot;auto&quot;&gt;lifecycle.unpaired_started&lt;/code&gt;, decides which &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; records are
open, for &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt;, &lt;code dir=&quot;auto&quot;&gt;doctor invocation-pairing&lt;/code&gt; and the sweep alike. A completion pairs in
three rounds: an &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt; record pairs the exact record it names; any other completion pairs the
latest record of its own agent and work package started before it; a completion left over pairs the
oldest remaining record of its own agent, then the oldest of any agent. The per-group counts are
unchanged. Before this, &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; and the doctor report named the group’s latest &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; records as
open, so they could disagree with the sweep about which record was open (#7505).&lt;/li&gt;
&lt;li&gt;It has one writer, &lt;code dir=&quot;auto&quot;&gt;lifecycle.write_abandoned_completion&lt;/code&gt;, which writes through the same locked
&lt;code dir=&quot;auto&quot;&gt;append_lifecycle_record&lt;/code&gt;: one new file, never a rewrite. &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; keeps writing only
&lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; and &lt;code dir=&quot;auto&quot;&gt;failed&lt;/code&gt;.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Consequences.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;The store stays append-only; the preservation gate admits the new files as it admits any other.&lt;/li&gt;
&lt;li&gt;A CLI older than this amendment cannot parse an &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt; record, skips it, and keeps reporting
the orphan. The operator accepted this with the phase choice.&lt;/li&gt;
&lt;li&gt;The sweep commits in every checkout that holds a stale record, lane worktrees included. A
repository-root &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ULID&gt;.json&lt;/code&gt; file is &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;’s bookkeeping, as a root
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;ULID&gt;.jsonl&lt;/code&gt; Op record is (&lt;code dir=&quot;auto&quot;&gt;reconciliation_kernel._KITTY_OPS_ROOT_RECORD&lt;/code&gt;; operator
ruling, Decision Moment &lt;code dir=&quot;auto&quot;&gt;01M72P4C1S5Z4MG13Q2W1S1KM0&lt;/code&gt;), so a closure committed on an approved lane
branch is not a commit after the approval and does not trip &lt;code dir=&quot;auto&quot;&gt;LANE_MOVED_AFTER_APPROVAL&lt;/code&gt;.&lt;/li&gt;
&lt;li&gt;The general dirty-state classifier (&lt;code dir=&quot;auto&quot;&gt;coordination.coherence.is_self_bookkeeping_churn&lt;/code&gt;) counts the
same exact path, &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ULID&gt;.json&lt;/code&gt;, as bookkeeping, as it counts a
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/&amp;#x3C;ULID&gt;.jsonl&lt;/code&gt; Op record (operator ruling of 2026-11-11 by Stijn Dejongh, follow-up to
#7506; recorded here, because the Mission that holds Decision Moment &lt;code dir=&quot;auto&quot;&gt;01M72P4C1S5Z4MG13Q2W1S1KM0&lt;/code&gt;
has landed and its history is frozen). A closure the sweep could not commit is no longer dirt in its
checkout, so it no longer refuses &lt;code dir=&quot;auto&quot;&gt;accept&lt;/code&gt;, the &lt;code dir=&quot;auto&quot;&gt;record-analysis&lt;/code&gt; preflight or the review
handoff’s dirty check, and a staged one no longer refuses &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;’s dirty-tree probe or its
post-merge working-tree invariant (both skip untracked files already). The destructive guards
read the same rule through &lt;code dir=&quot;auto&quot;&gt;ResidueContext.is_disposable&lt;/code&gt; (see Residuals). The pattern is the
record’s one definition (&lt;code dir=&quot;auto&quot;&gt;op_commit_policy.LIFECYCLE_RECORDS&lt;/code&gt;). The claim check of &lt;code dir=&quot;auto&quot;&gt;implement&lt;/code&gt;
already exempted the whole &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt; directory and is unchanged.&lt;/li&gt;
&lt;/ul&gt;
&lt;p&gt;&lt;strong&gt;Residuals.&lt;/strong&gt;&lt;/p&gt;
&lt;ul&gt;
&lt;li&gt;A &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record whose &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; cannot be parsed is dropped when the store is read, so neither the
sweep nor &lt;code dir=&quot;auto&quot;&gt;doctor invocation-pairing&lt;/code&gt; sees it.&lt;/li&gt;
&lt;li&gt;Matching a completion to its &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record is a heuristic for records &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; wrote
(same agent and work package, the latest started before it); two retries completed in different
checkouts can still be told apart wrongly.&lt;/li&gt;
&lt;li&gt;A &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record whose &lt;code dir=&quot;auto&quot;&gt;at&lt;/code&gt; is in the future (clock skew) counts as stale, so the sweep closes it
rather than reporting it as fresh on every run. The same rule applies to Op records.&lt;/li&gt;
&lt;li&gt;The record has no schema version. An older CLI drops a record with an unknown phase without a
warning, when it reads the store (&lt;code dir=&quot;auto&quot;&gt;lifecycle.read_lifecycle_records&lt;/code&gt;).&lt;/li&gt;
&lt;li&gt;The bookkeeping path rule trusts a lifecycle record by its path, not its content: a commit on an
approved lane that adds only a hand-written &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&amp;#x3C;ULID&gt;.json&lt;/code&gt; record is not
refused by the approval bound. It changes pairing data, never code.&lt;/li&gt;
&lt;li&gt;The dirty-state rule matches a record by its exact path. A gate that lists untracked files
without &lt;code dir=&quot;auto&quot;&gt;--untracked-files=all&lt;/code&gt; sees a wholly untracked &lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&lt;/code&gt; as one
&lt;code dir=&quot;auto&quot;&gt;kitty-ops/lifecycle/&lt;/code&gt; (or &lt;code dir=&quot;auto&quot;&gt;kitty-ops/&lt;/code&gt;) entry, which the rule does not match, so that gate still
counts it as dirt. The operator ruled the exemption to the exact path, not the directory. The
checkout guard of &lt;code dir=&quot;auto&quot;&gt;git/ref_advance.py&lt;/code&gt; lists every untracked file, so it sees each record.&lt;/li&gt;
&lt;li&gt;The destructive guards (&lt;code dir=&quot;auto&quot;&gt;git/destructive_guard.py&lt;/code&gt;, through &lt;code dir=&quot;auto&quot;&gt;ResidueContext.is_disposable&lt;/code&gt;) count
an uncommitted lifecycle record as disposable in every checkout role, as they count an uncommitted
Op record. &lt;code dir=&quot;auto&quot;&gt;consolidate&lt;/code&gt;’s lane cleanup, the worktree allocator’s remove and &lt;code dir=&quot;auto&quot;&gt;reset --hard&lt;/code&gt;, and the
coordination worktree teardown no longer keep a checkout for one, so they can discard it. This
covers every phase, not only an &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt; closure: a lost &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record drops out of pairing,
and a lost &lt;code dir=&quot;auto&quot;&gt;completed&lt;/code&gt; or &lt;code dir=&quot;auto&quot;&gt;failed&lt;/code&gt; record leaves its &lt;code dir=&quot;auto&quot;&gt;started&lt;/code&gt; record open, which the next sweep
then closes as &lt;code dir=&quot;auto&quot;&gt;abandoned&lt;/code&gt;, so that action’s real outcome is lost. Records are left uncommitted
where the primary branch tracks none (the #6410 skip) or a protected branch refuses the commit.
&lt;code dir=&quot;auto&quot;&gt;tests/coordination/test_disposable_residue.py&lt;/code&gt; pins this consequence.&lt;/li&gt;
&lt;li&gt;A closure the sweep could not commit (skipped or refused) leaves the command’s exit code unchanged,
as for an Op record. &lt;code dir=&quot;auto&quot;&gt;spec-kitty next&lt;/code&gt; commits any uncommitted lifecycle record with its own
commit, so such a closure is committed with the next action that &lt;code dir=&quot;auto&quot;&gt;next&lt;/code&gt; reports in that checkout.&lt;/li&gt;
&lt;/ul&gt;</content>
</entry>
