Skip to content

skills/handoff/SKILL.md:474 still says '(c) below still runs', the exact promise R-A11-27 refuses, uncorrected 60 lines above the fix #99

Closed

Description

@brettheap

Found auditing skills/handoff/SKILL.md against lane-collision-protocol-amendment-11.md while resolving opensoft/openBenches#93 (the test-claude-profile-amendment-11.sh rot-and-CI pass).

The ruling

Amendment 11 Addendum 4 ruling 11, R-A11-27 (ratified 2026-09-13T21:08:26Z, verbatim "a11 addendum 4 yes"): in a container with no LANES_WORKSTATION the swap also refuses write (c), the row's state-cell flip, alongside (a) and (b) — not "(c) below still runs" the way an earlier PR (opensoft/workBenches#71 @fa0230d) promised. The ruling exists specifically to correct that promise: "#71 @fa0230d promises a row flip its own helper refuses."

What's shipped, and the bug

The shipped skill correctly implements the correction in its code — write (c) is gated behind the same $ws_missing flag as (a) and (b) (:527-541), and the comment right there quotes the retired promise as history:

533:# *"still refreshes the handoff naming the gap"* is step 2's commit, which is in
534:# the LANE'S OWN repository and is not a register write; this is. `#71`'s copy
535:# promised *"(c) below still runs"*, and against this repository's own
536:# dispatcher guard that promise is a write the helper refuses — so the promise
537:# is corrected here rather than repeated.

But a second, unqualified occurrence of the exact retired phrase sits 60 lines earlier, asserting it as current fact rather than quoting it as superseded, in the middle of unrelated prose about the payload's workstation sub-field:

472:# this one is the KEY the records are filed under — a record without it is not
473:# incomplete, it is unfindable. So where there is none the two WRITES stop
474:# instead (ruling 11), and (c) below still runs.
475:[[ -z "$ws" ]] || payload="$payload; workstation $ws"

:474 was never updated when the later fix (gating (c) too, :527-541) landed — it still says only "the two WRITES stop" (a and b) "and (c) below still runs", which is exactly the promise R-A11-27 refuses, left standing three sentences before the ruling number that refutes it, and flatly contradicted by the code 53 lines further down in the same file.

Ask

Fix :474 to match :531-541's own corrected account: (c) stops too, under the same ruling, not "below still runs". A one-line comment fix; not a behavior change (the code at :527-541 is already correct).

Confirmed pre-existing (same gap against git show 8a36eb3:skills/lane-swap/SKILL.md's equivalent comment, independent of any pin move).

Filed from opensoft/openBenches#93 (lane openRepoTools-1). Sibling of #79 and #80.

Activity

  1. brettheap commented on Oct 11, 2026

    @brettheap
    ContributorAuthor

    CLAIMED — lane openRepoTools-4, session e545e636-93fd-4b80-81b1-48177346b887@Eagle, 2026-10-11T16:31:42Z, for #99

    Logged in lanes/log/openRepoTools-4.md at 7d2d53c4497027a9f4fdbb01fa4221e5cc4834f2.

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

    1. existing `CLAIMED —` comments on opensoft/openRepoTools#99:
       none
    2. `gh pr list --repo opensoft/openRepoTools --state all --search "#99"`, kept where the row or its body names `#99`:
    16	Pin openRepoShape at 32450eb (its main, 2026-09-11): `--doctor`/`--preflight`, the generated `docs/cli.md`, the doctor's `placement` row and the platform-aware quoter; none of the eight mounted files moved	chore/bump-openreposhape-pin-32450eb	MERGED
    3. `git ls-remote --heads git@github.com:opensoft/openRepoTools` branches naming `99` as a whole token:
       none
    
  2. brettheap commented on Oct 19, 2026

    @brettheap
    ContributorAuthor

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions