lane-end's top-level USAGE synopsis says a DUPLICATE holder retire 'ends nothing', but it TERMs the pair

lane-end's top-level USAGE synopsis (lines 26-27) still says:

#   lane-end <lane> --retire <pid|uuid>  # retire a live FORK (pid or uuid) or a
#                                        # DUPLICATE (pid); ends nothing

"ends nothing" is true for a FORK (--retire's original target: it writes
nothing and kills nothing, per Amendment 11 clause (k) rule (e)) but false
for a DUPLICATE HOLDER: issue #39's own implementation TERMs the pair (the
bg-pty-host parent and its child) — the whole point of the act. --help
prints this exact synopsis, so a user reading it is told the opposite of
what a duplicate-holder retire does.

The longer OPTIONS section below (--retire <pid|uuid>'s own paragraph)
is accurate and detailed about this distinction already — this is only the
one-line top synopsis, which predates the duplicate-holder work being folded
into the combined FORK-or-DUPLICATE phrasing and was never revisited when
that changed.

Raised by Copilot's review of PR #61 at commit 21b8e82 (2026-09-15T21:21Z),
lane-end:67. Not fixed there or in PR #61 at all: the inaccurate line
predates every commit that PR touches (round 12 onward) — it is original to
however issue #39's duplicate-holder retirement was first phrased in this
synopsis, well before PR #61 existed — so it is out of that PR's own scope
by this estate's own "only fix what the diff introduced" rule.

Fix: split the synopsis into two lines (FORK vs DUPLICATE) or otherwise make
the one-line summary say what a DUPLICATE retire actually does, matching the
detailed OPTIONS paragraph already below it.

CLAIMED — lane openRepoTools-3, session 4135b2c9-34a6-47e3-a156-5adebb632fae@Eagle, 2026-09-15T22:09:49Z, for #96

Logged in lanes/log/openRepoTools-3.md at 69decc91d5f5bf82b61107a0a95c7bd9306ebd1e.

The three reads (lane-collision-protocol Rule 1):

1. existing `CLAIMED —` comments on opensoft/openRepoTools#96:
   none
2. `gh pr list --repo opensoft/openRepoTools --state all --search "#96"`, kept where the row or its body names `#96`:
   none
3. `git ls-remote --heads git@github.com:opensoft/openRepoTools` branches naming `96` as a whole token:
   none

The dead-lane revival abort is its own exit code, 9, never coerced to…

TAKEOVERopenRepoTools-3 — lane openRepoTools-4, session e545e636-93fd-4b80-81b1-48177346b887@Eagle, 2026-10-11T16:49:14Z, for #96

Logged in lanes/log/openRepoTools-4.md at 6561f5e392467a03fc9bbddea5c885d56a4584a7 (takeover of the stale claim held by lane openRepoTools-3).

The three reads (lane-collision-protocol Rule 1):

1. existing `CLAIMED —` comments on opensoft/openRepoTools#96:
6:CLAIMED — lane openRepoTools-3, session 4135b2c9-34a6-47e3-a156-5adebb632fae@Eagle, 2026-09-15T22:09:49Z, for opensoft/openRepoTools#96
13:1. existing `CLAIMED —` comments on opensoft/openRepoTools#96:
2. `gh pr list --repo opensoft/openRepoTools --state all --search "#96"`, kept where the row or its body names `#96`:
   none
3. `git ls-remote --heads git@github.com:opensoft/openRepoTools` branches naming `96` as a whole token:
   none

Make lane-end's synopsis say what a DUPLICATE retire does, read a sta…

RELEASED — lane openRepoTools-4, session e545e636-93fd-4b80-81b1-48177346b887@Eagle, 2026-10-19T11:56:07Z, for #96 — #96 is closed by PR #202 (d3b2d9a); lane 4's claim ends

Navigation Menu

Repository navigation

lane-end's top-level USAGE synopsis says a DUPLICATE holder retire 'ends nothing', but it TERMs the pair #96

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

lane-end's top-level USAGE synopsis says a DUPLICATE holder retire 'ends nothing', but it TERMs the pair #96

Description

Activity

brettheap commented on Sep 15, 2026

brettheap commented on Oct 11, 2026

brettheap commented on Oct 19, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions