[wenzowski]

Closes CLOUD-1268.

The class, re-derived from the tree

SubjectFacts::died is .all(): every subject a dying .bats suite declared must be absent before the deletion is admitted. Re-derived here rather than inherited —

for b in tests/*.bats; do awk 'NR==2' "$b"; done | grep -v 'mise-tasks/'

— 16 suites declare a # subject: that CLOUD-843 never retires: mise.toml, hk.pkl, batten.toml, clippy.toml, install.sh, a .claude/hooks/ program, tests/helpers.bash, Rust source. .all() can never hold for them, so those suites are undeletable by construction — 217.9s of a 1097.1s corpus, in a lane that runs --no-parallelize-within-files and whose makespan therefore cannot fall below its longest suite.

CLOUD-1156 landed the detector (policy/suite-subject-retirable.rego) and closed; its own header at :47-51 defers the recovery to "its own row", and no such row was filed. This is that row.

Why this route

The module header establishes the other two and they stay refused: re-subjecting a suite edits a governed tests/**/*.bats (V-SHELL-RULE-EDITED, one route, no bypass_env), and an in-file marker is an added line that is neither a truncation nor a repointing.

The arm

// ported: is the exact mirror of // withdrawn:. That one is admissible only where the dying file's declared subject died; this one only where it lives. Between them, both answers to "what happened to the subject" have a spelling.

It obliges more than carried, never less:

• a target the head tree carries, exactly as the first three do;
• plus a subject: field naming a path the dying file itself declared at base and the head tree still carries.

That field is what clears the aggregate subject-alive term — by naming the survivor, rather than by a carried row falsely claiming the case moved into helpers.bash. The subject is read from the base # subject: header rather than taken from the author, which is the anti-fabrication term.

Additive, not a loosening. named_and_alive reads carried and subsumed only and is untouched, so CLOUD-1130's refusal over the four existing markers stands byte-for-byte.

The discriminating pair is the whole commit

In ratchet.rs, over the compiled binary:

• a_complete_port_over_a_surviving_subject_is_admitted — passes;
• the_same_port_with_one_case_unported_still_refuses — byte-identical fixture minus one arm, and it refuses twice: the unmapped case at the suite, and the aggregate subject-alive blocker because the path is then not fully mapped.

Without the second this would be a hole and CLOUD-908's finding — "conserves files, not logic: six cases have no successor anything in the tree can name" — recurs by design.

Four more: a port whose subject died refuses (use carried); one naming no survivor refuses; one naming a survivor the suite never declared refuses; and a_carried_arm_over_a_live_subject_still_refuses is the anti-vacuity mirror that would go red if this had relaxed CLOUD-1130 rather than added to it.

Still to come on this branch

Commits 2–4 spend the spelling on pre-commit-staging (23.3s), helpers (36.1s) and session-start (135.9s) — 195.3s, 90% of the class — each deleting the suite, removing its row from suite-subject-retirable.rego's exempt map, and asserting the surviving subject's coverage in its new home. The rego and batten.toml halves of the spelling land in this PR too; both are protected paths, and their refusal's own remedy is to change them under review, which is here.

Notes for the reviewer

• policy/shell-retirement.rego is a protected path because CLOUD-833 derives every policy row's module into the protected set — worth knowing before touching it.
• mise-tasks/replay.sh:349 iterates carried subsumed changed, so a ported arm is skipped rather than broken; it needs no edit (and is governed, so it could not take one). The cost — ported cases get no differential replay — is real and gets its own row.
• shell-retirement.rego's header claims rules-drift holds arm_markers to the TOML. It does not; mise-tasks/rules-drift.sh contains no reference to the arms. Nothing would have caught adding the marker in only one of the two places.

---

Generated by Claude Code

[linear-code]

CLOUD-1268 Port-without-retirement: the ledger has no spelling for a suite whose subject survives — ~82s, 15 suites, and `session-start` is NOT one of them (its 135.9s is `mise install`, not the harness)

⚠️ CORRECTION 2026-08-31, AFTER THIS ROW WENT IN PROGRESS — session-start IS NOT A MEMBER, AND THE HEADLINE WAS WRONG BY 136 SECONDS

If you are working this row, read this before touching tests/session-start.bats. The
row was filed claiming "session-start, helpers and pre-commit-staging — 195.3s, 90% of the*
**class"*. The session-start third of that is false, and it was asserted from the class
it sat in rather than from the file — CLOUD-1166 arm 4, in the row that
quotes CLOUD-1166.

**Read, not divided. **tests/session-start.bats is 10 cases. Its setup() at :55-60
installs a mise stub that intercepts container-preflight, doctor and install:

if [ "$1" = install ] && [ -z "${SESSION_START_REAL_INSTALL:-}" ]; then exit 0; fi

Only two cases opt back in, through real_install_or_skip at :150 and :175. Eight run
against the stub and are cheap. So 135.9s is not 10 × 13.6s of provisioning — that figure was
arithmetic on the corpus total, and the per-case cost is nothing like uniform.

Three consequences, and the first kills its membership

1. A port to crates/batten/tests/*.rs recovers almost nothing. The seconds are in
   mise install, not in the bats harness. A Rust case that runs the same install pays the
   same wall clock. Porting session-start moves 136 seconds from one lane to another.

2. Its real remedy is one line, and it is not a retirement. The suite states it itself at
   :73: "Idempotent and warm, so the second install costs milliseconds." Warm
   mise install once in [tasks."test:bats"]. mise.toml is ungoverned —
   governed_at_head selects mise-tasks/ paths and .bats suites and nothing else — so
   there is no V-SHELL-RULE-EDITED, no ledger arm, and no retirement. That is
   CLOUD-1198's shape exactly: build once, feed the seam the programs already
   declare.

3. The check that settles it before any code, and it costs two minutes:

   mise install                                     # warm the toolchain
   mise run test:bats -- tests/session-start.bats    # time it warm vs 135.9s
   

   If it collapses, this is a one-line mise.toml change against the corpus's second-largest
   suite and it belongs to no bundle at all.

What that does to this row's numbers

	filed	corrected
members	16	15
class total	217.9s	~82.0s
"90% in three suites"	195.3s	59.4s in two — helpers 36.1 + pre-commit-staging 23.3

The remaining 13 members total ~22.6s, so this row is now a mechanism row with a modest**
**yield, not a 218-second recovery. That does not make it not worth doing — the ledger
spelling is the deliverable CLOUD-1156 deferred and nothing else can land
the class — but it must be scheduled against ~82s, and the makespan-floor argument below is
withdrawn: session-start leaves this row still standing at 135.9s, so this row does not
move the floor after Bundle A. Only its own remedy does.

And .claude/hooks/session-start.sh was never governed either

The premise that put it in this class — "the subject cannot die" — is true but irrelevant
for it. governed_at_head selects mise-tasks/ paths carrying a shebang or #MISE description, plus any .bats under tests/. A .claude/hooks/ program is in neither set,
so it is ungoverned for edits and for deletion. Filing it under "immortal subject" sent
every pass at it toward a retirement it never needed.

Action: drop session-start from §1's scope and from Acceptance, and file its
[tasks."test:bats"] warm-install remedy as its own row.

---

Why

SubjectFacts::died is .all() — every declared subject must be absent before a suite's
deletion is admitted. 16 suites declare a # subject: that is not a mise-tasks/ program:
mise.toml, hk.pkl, batten.toml, clippy.toml, install.sh, a .claude/hooks/ program,
or Rust source. Those subjects are not what the campaign retires, so .all() can never hold,
so the suites are undeletable by construction.

Measured at origin/main against bench/suites/RESULTS.md (138 suites, 1097.1s):

suite	s	# subject:
session-start	135.9	.claude/hooks/session-start.sh
helpers	36.1	tests/helpers.bash
pre-commit-staging	23.3	hk.pkl
lint-deno	5.6	mise.toml
hk-selection	5.0	hk.pkl
spawn-census	2.9	clippy.toml
lint-rego	2.6	mise.toml
install	2.2	install.sh
verify	1.5	mise.toml
fact-record-keying	1.0	crates/batten/src/facts.rs
commit-attribution	0.6	hk.pkl mise.toml
commit-convention	0.4	batten.toml mise.toml
task-fail-closed	0.4	mise.toml
git-hook	0.3	.claude/hooks/git-hook.sh
cross-check	0.1	mise.toml
zizmor-split	0.0	mise.toml
	217.9	19.9%

Three suites are 195.3s — 90% of the class.

The row that owns this is Done, and it deferred the recovery to a row nobody filed

CLOUD-1156 closed 2026-08-31 04:36:52, inside the same ~4-second bulk cluster CLOUD-1253
documents. PR #777 landed policy/suite-subject-retirable.rego — the detector, which
refuses a new instance arriving unnoticed. That is a real deliverable and it is not this row's
complaint.

What it deferred is stated in the module's own header, policy/suite-subject-retirable.rego:47-51:

THE THIRD ROUTE IS STILL OPEN AND IS NOT THIS MODULE'S. A suite over batten.toml has
cases worth porting into crates/batten/tests/*.rs even though nothing dies — a port
WITHOUT a retirement, which the ledger has no spelling for. Each such port is its own row.
This module only refuses a NINETEENTH instance arriving unnoticed, which is the acceptance
CLOUD-1156 owes.

No such row exists. CLOUD-1156's own Acceptance says "All 19 suites are classified:
exempted, re-subjected, or ported-without-retirement" — they are exempted, which is one of
the three, and the 217.9s is untouched. This is CLOUD-1253's class stated precisely: the row**
**closed when its analysis was finished, not when its condition was gone.

Why the two obvious routes are refused, and why the third is landable

The module's header already establishes the first two, and they are not re-litigated here:

• RE-SUBJECT — rewriting a # subject: line is an edit to a governed tests/**/*.bats.
  governed_at_head selects every bats suite, so it is V-SHELL-RULE-EDITED: one route, no
  bypass_env. The one admitted edit needs every removed line to name a path the same delta
  deletes, and a re-subjected header names paths that are staying. Refused.
• AN IN-FILE MARKER — an added line that is neither a truncation nor a repointing. Refused
  by the same arm.

The third route is landable, and that is the finding. A ledger spelling for
port-without-retirement lives in policy/shell-retirement.rego and crates/batten/src/rules.rs
— neither is governed by shell-retirement (governed_at_head selects mise-tasks/ paths
and .bats suites and nothing else). So unlike mutant.sh (CLOUD-1267) this class is not
trapped behind an unlandable edit. Nobody has tried.

And the ledger genuinely has no spelling today — checked rather than inherited.
shell-retirement.rego:62 declares
#MUTANT shell-subject-alive-unchecked|…|CLOUD-1130 — a row naming a subject this delta does NOT retire is refused, whichever of the four markers it carries, and named_and_alive
(:683-688) raises on exactly that. So CLOUD-1130 tightened this deliberately, and the new
spelling must be additive rather than a loosening of that arm — a suite deletion whose ledger
carries a complete port arm for every case, with the surviving subject named and its ongoing
coverage asserted elsewhere. .claude/rules/toolchain.md's "the ledger must name it too"
states the obligation; what is missing is a marker under which naming it is admitted.

It moves the makespan floor a second time, which is the reason to do it after Bundle A

test:bats runs --no-parallelize-within-files, so the lane's makespan cannot fall below the
longest single suite.

	longest suite	corpus
today	land-lock 195.1	1097.1
after Bundle A (CLOUD-1170)	session-start 135.9	866.2
after this row	land 96.2 (CLOUD-1148's)	~648

Bundle A hands the floor to this class. It is the only other bundle that moves the floor
rather than the total, and it becomes the binding constraint the moment Bundle A lands.

Co-dispatchable remainder — 43.7s, and it shares NO mechanism with the above

Named here so it stops being unscheduled, not because it belongs to the same unit. Each is an
independent delta and any of them can be dropped without touching the spine:

what	s	state
CLOUD-1163 units 6, 7, 8, 10 — token-bench(+check), suite-bench-check(+suite-bench), gh-guard(+check), perf-gate(+perf-compare)	19.1	groomed 2026-08-31 as landing today; dispatched nowhere
hook-latency-drift	24.6	a member of CLOUD-1170's own table, "costed separately"; excluded from Bundle A by the dispatching session and in no bundle since

Units 6, 7, 8 each declare two subjects in one suite (tests/token-bench.bats:2,
tests/suite-bench-check.bats:2, tests/gh-guard.bats:2), so both members of each pair must
die in one delta — SubjectFacts::died is .all().

---

Refinement — Ready (give the ledger a port-without-retirement spelling, then spend it)

Refinement gate: Definition of Ready & Done. This body carries only specializations.

• **Authority boundary (§1). **policy/shell-retirement.rego and crates/batten/src/rules.rs
  for the spelling; then the suites themselves are deleted, one conserves arm per path.
  **No **mise-tasks/ **program and no **tests/**/*.bats is edited or added — every change to a
  suite here is a deletion, which is the only shape available.
• Computable predicate (§2). A .bats deletion whose declared subject survives is admitted
  iff the ledger carries a complete port arm naming where every case went, and refused
  otherwise. named_and_alive's existing refusal stands for every other marker; this adds one
  admitted shape rather than weakening an arm.
• The discriminating pair (§2), and it is the whole row. A deletion with a complete port
  arm passes; the same deletion with one case unported still refuses. Without the second,
  the spelling is a hole and CLOUD-908's finding — "retires_with conserves files, not logic…*
  *six cases have no successor anything in the tree can name" — recurs by design.
• Coverage must not fall (§2). The subject is still alive and still needs testing. Each
  ported case names its crates/batten/tests/*.rs home, and the surviving subject's coverage
  is asserted there. A port that deletes 36 seconds of helpers.bats and lands nothing is the
  defect, not the deliverable.
• Deliberately not in scope (§2). Changing SubjectFacts::died to any — that readmits
  the partial-retirement defect its own comment names, and CLOUD-1156 already rejected it.
  Re-subjecting any suite. Retiring release-tracking-check.sh or board-payloads.sh, the two
  CLOUD-1156 records as stranded by a governed co-subject — each needs this spelling first and
  then its own row.
• **Effect (§3). **read for the policy half.
• Output and exit (§5). Pointer-only: the suite path and the unported case's name. Never a
  case body.
• **Commit / bump (§6). **feat(policy) for the spelling, refactor(ci)! per port — patch (0.0.x, so a feat is a patch bump and a ! on a test-lane refactor carries no public surface with it).
• Test obligation (§7). Over the compiled binary in crates/batten/tests/; suite_subjects.rs
  is the existing tier. Shown able to fail per CLOUD-418, plus the anti-vacuity mirror: a
  conforming whole-file retirement still passes and an unexempted immortal subject is still
  refused, so this does not weaken suite-subject-retirable.
• Blockers (§8). None. Sequenced **after **CLOUD-1170's Bundle A, since that is what makes
  session-start the floor and this row the binding constraint. relatedTo CLOUD-1156 (Done,
  detector landed, this is the recovery it deferred), CLOUD-1130 (whose arm this must extend
  rather than loosen), CLOUD-908 (the conserve-logic-not-files bar), CLOUD-1253 (the
  closed-while-the-condition-persists class this is an instance of), CLOUD-1163 and CLOUD-1170
  (the co-dispatchable remainder), CLOUD-1140 (suite cost).

Acceptance

• The ledger admits a port-without-retirement, and refuses the same deletion with one case
  unported.
• ~~session-start~~~~, ~~helpers and pre-commit-staging are ported and deleted — 59.4s,
  with every case's new home named and the surviving subject's coverage asserted.
  session-start is struck: its 135.9s is mise install in two cases, not the harness,
  so a port pays the same seconds. See the correction at the top of this row.
• bench/suites/RESULTS.md regenerates with helpers and pre-commit-staging absent and the
  serial total down by the measured amount. ~~If ~~~~session-start~~ ~~still heads that table after~~~~

  and will still head the table; the makespan floor is its own remedy's to move.
* The remaining 13 members each carry a disposition: ported, or exempted with a reason that is
  not "the subject cannot die" — that one is now answered.
* `suite-subject-retirable` still refuses an unexempted new instance, asserted.

Found by subtracting four dispatched bundles from the corpus and asking what was left: this
class was in none of them, and the session that built those bundles had recorded
`session-start.bats` as *"the largest number in the tree with no owning row"* — which was
wrong twice over, since [CLOUD-1156](https://linear.app/buttoninc/issue/CLOUD-1156/19-bats-suites-3020s-210percent-of-the-corpus-declare-a-subject-that) owns it and had already closed.
</p>
</details>
<!-- linear-review-link -->
<p><a href="https://linear.app/buttoninc/review/featpolicy-a-fifth-conserves-arm-for-a-port-without-a-retirement-12e33d433120">Review in Linear</a></p>

[coderabbitai]

ℹ️ Recent review info

⚙️ Run configuration

Configuration used: Path: .coderabbit.yaml

Review profile: CHILL

Plan: Free

Run ID: 0b58fa9c-c254-40ed-9859-b2474ec1af1a

📥 Commits

Reviewing files that changed from the base of the PR and between 4756ba1 and 68fb14e.

📒 Files selected for processing (10)

• batten.toml
• bench/suites/RESULTS.md
• crates/batten/src/rules.rs
• crates/batten/tests/it/bats_invocation.rs
• crates/batten/tests/it/hk_fix_selection.rs
• crates/batten/tests/it/ratchet.rs
• crates/batten/tests/it/shell_retirement.rs
• policy/suite-subject-retirable.rego
• schema/batten.local.schema.json
• schema/batten.schema.json

🚧 Files skipped from review as they are similar to previous changes (1)

• bench/suites/RESULTS.md

Included review availability: Your plan provides up to 1 included review per hour; 0 remain after this review.

---

📝 Walkthrough

Walkthrough

The change adds a ported conservation arm with surviving-subject validation in Rust and Rego policy checks. It updates schemas, configuration, verdicts, and retirement documentation. It adds MCP source, credential, response-reduction, and landing-loop schema support. It migrates helper and hook-selection coverage into Rust integration tests. It also regenerates benchmark results and updates nested test-path handling.

Merge Risk: 🔵 Low · up to 68fb1

The PR adds a public MCP configuration contract for credential and source wiring; if schema-accepted settings do not match every runtime consumer, users could receive configuration that validates but does not behave as expected. The change is mergeable with explicit owner awareness of this bounded integration risk.

---

Note

🎁 Summarized by CodeRabbit Free

Your organization is on the Free plan. CodeRabbit will generate a high-level summary and a walkthrough for each pull request. For a comprehensive line-by-line review, please upgrade your subscription to CodeRabbit Essentials by visiting https://app.coderabbit.ai/settings/billing.

_{Comment @coderabbitai help to get the list of available commands.}

[wenzowski]

Dispositions for the rest of the class

CLOUD-1268's Acceptance owes one per remaining member, and none may read "the subject cannot
die" — that answer is what this PR removes. Re-derived from the tree at this head, not copied from
the row's table (CLOUD-1166's arm 4 is exactly that failure, and this row already carries one
correction for it):

for b in tests/*.bats; do printf '%s\t%s\n' "$b" "$(awk 'NR==2' "$b")"; done | grep -v 'mise-tasks/'

14 remain — 16 minus the two ported here. Not 13: the row's Acceptance said 13 while counting
session-start as ported, and its own correction later struck that suite, so it stays in the class
without being this PR's.

suite	s	subject	disposition
session-start	97.8	.claude/hooks/session-start.sh	Own row — CLOUD-1273. Struck from this PR by the row's own correction. Its cost is mise install in the two real_install_or_skip cases, not the harness, so a port moves seconds rather than removing them. Remedy is a one-line warm install in [tasks."test:bats"], and mise.toml is ungoverned so it needs no ledger arm at all.
hk-selection	2.8	hk.pkl	Portable, deferred on cost. Same subject and same shape as pre-commit-staging, which this PR ports; nothing blocks it. 2.8s does not pay for a delta today.
verify	2.5	mise.toml	Portable, deferred on cost.
install	1.8	install.sh	Portable, deferred on cost. Its subject cannot be a policy module by construction — install.sh runs before the engine exists — but that bears on retiring install.sh, never on porting its suite.
spawn-census	0.8	clippy.toml	Portable, deferred on cost.
fact-record-keying	0.7	crates/batten/src/facts.rs	Portable, deferred on cost. Subject is engine source; the natural home is a sibling crates/batten/tests/*.rs.
lint-rego	0.7	mise.toml	Portable, deferred on cost.
lint-deno	0.6	mise.toml	Portable, deferred on cost.
commit-attribution	0.5	hk.pkl mise.toml	Portable, deferred on cost. Two subjects, so a port arm names both.
commit-convention	0.3	batten.toml mise.toml	Portable, deferred on cost. This is the exact suite suite-subject-retirable.rego's header names as the motivating example.
task-fail-closed	0.3	mise.toml	Portable, deferred on cost.
git-hook	0.2	.claude/hooks/git-hook.sh	Portable, deferred on cost.
cross-check	0.1	mise.toml	Portable, deferred on cost.
zizmor-split	0.1	mise.toml	Portable, deferred on cost.

Twelve of the fourteen are now portable and were not before, which is the deliverable. They total
10.6s, so each is a real delta against a small return — deferred on economics, which is a reason
that survives, rather than on impossibility, which was the old one.

Two members are deliberately still refused, and by a new arm

release-tracking-check and remedy-payload-source are not in the list above: their # subject:
headers name a workflow yaml and batten.toml, so they never appeared in the awk pass, but
CLOUD-1156 records both as gluing a governed program to an immortal subject —
mise-tasks/release-tracking-check.sh and mise-tasks/board-payloads.sh are stranded while those
suites stand.

V-PORT-SUBJECT-GOVERNED refuses a // ported: arm whose surviving subject is
governed_when_deleted, so this PR does not unstrand them, on purpose. A live governed path is
something the campaign retires; porting a suite's cases away while its governed subject stands is
the same claim named_and_alive refuses under the other four markers, decided by which word the
author typed. Each still owes its own row, exactly as CLOUD-1156 said.

Filed rather than deferred silently

• CLOUD-1272 — replay.sh does not differentially replay a // ported: case. Its arm loop is
  for candidate in carried subsumed changed, so a ported case is skipped; the file is governed, so
  the one-line fix is unlandable and belongs to whichever row retires it.
• CLOUD-1273 — session-start's warm-install remedy, split out by this row's own correction.

---

Generated by Claude Code

[wenzowski]

Correction to the dispositions comment above — the class is 17, not 14, and my stated reason was wrong

Two errors in my previous comment, both from the same cause. Correcting rather than editing, so the
mistake stays legible.

The derivation was wrong. I used:

for b in tests/*.bats; do ... done | grep -v 'mise-tasks/'

grep -v drops a line if it contains a mise-tasks/ path anywhere. Three suites declare
mixed subjects — a governed mise-tasks/ program and an immortal one on the same header line
— so the filter silently dropped them even though they are squarely in the class:

suite	declared # subject:
release-tracking-check	mise-tasks/release-tracking-check.sh + two .github/workflows/*.yml
remedy-payload-source	mise-tasks/board-payloads.sh + batten.toml
replay	mise-tasks/replay.sh + mise-tasks/replay-pointers.py

Mixed subjects are the whole reason SubjectFacts::died is .all() — they are the case the rule
exists for — and my filter was blind to exactly them. This is .claude/rules/scanning.md's own
warning landing on me: a substring pass answering a question about membership.

So the count is 17, not 14, which is also exactly what suite-subject-retirable.rego's exempt
table holds — the agreement I should have used as the check and didn't. Re-derived properly, per
subject rather than per line:

for b in tests/*.bats; do
  subj=$(awk 'NR==2' "$b" | sed 's/^# subject: *//')
  imm=""
  for s in $subj; do case "$s" in
    mise-tasks/*.py|mise-tasks/*.tsv) imm="$imm $s";;
    mise-tasks/*|tests/*.bats) ;;
    *) imm="$imm $s";;
  esac; done
  [ -n "$imm" ] && printf '%s\t%s\n' "$b" "$imm"
done

And my stated reason for their absence was wrong. I wrote that they "never appeared in the
awk pass" because their headers "name a workflow yaml and batten.toml". They do name those —
but that is not why they were missing. They were missing because they also name a mise-tasks/
program, which is what my filter keyed on. Right conclusion, wrong mechanism, and the wrong
mechanism is the part worth correcting: it would have sent the next reader looking in the wrong
place.

What does not change

The three dispositions themselves, and the commit prose in 90238955, are unaffected — that prose
already says 13 cost + 3 structure + session-start = 17, derived from the exempt table rather than
from my filter. Restating it here so the two agree:

• COST — 13 rows, 11.4s. Portable today, unported because the yield does not pay for a ledger
  block and a Rust port.
• STRUCTURE — 3 rows, 9.2s. replay's .py co-subject is excluded from
  governed_when_deleted by extension; release-tracking-check and remedy-payload-source each
  name a governed and alive co-subject, which V-PORT-SUBJECT-GOVERNED refuses on purpose. This
  PR deliberately does not unstrand them — a live governed path is something the campaign retires,
  and each owes its own row, as CLOUD-1156 said.
• session-start — 97.8s, its own row (CLOUD-1273).

13 + 3 + 1 = 17. ✅

---

Generated by Claude Code

[sonarqubecloud]

❌ The last analysis has failed.

See analysis details on SonarQube Cloud

[wenzowski]

/fast-forward