Skip to content

adopt-project.py: what execute and AGENTS.md say around a run (the plan's follow-up, a failed verification's open PR, an answer with no resolution:, the ruleset hint) #523

Closed

Description

@brettheap

Four places where adopt's printed text, or AGENTS.md about it, says something the tool does not do. One wording change over adopt-project.py, AGENTS.md and the tests that pin the text.

From the v1.1.0 triage of the v1.0.0 known limits on #457 and #459. One pull request covers the lines below.

Lines

Rides along (backlog; tick it here if the same change covers it)

  • N2: under --local-remote-dir, NEXT still says "review the pull request" (source)

Note: #457's N5 line was closed as a duplicate of auA-12, which is here.

Each line above is marked → this issue on its tracking issue. Tick it there too when this closes.

The lines as written on the tracking issues

AT-adopt N1: the follow-up "open the split as a pull request against ...; the legs -spec and -code are seeded before it" (adopt-project.py:1368-1372) is printed by plan and listed under "FOLLOW-UPS, which this commit does NOT do" in the split commit and the pull request body (:5442-5444), though in GitHub mode execute opens that pull request itself, and it calls two legs "seeded" that were extracted (the docs use that word only for a leg made from a template).
— #457, body

auA-12: against GitHub, execute opens the pull request and sets the topic BEFORE verification runs (adopt-project.py:5071-5080). So a failed verification leaves an open pull request for the failed split on the source. Neither the exit-1 text (:5409-5417) nor AGENTS.md:147-149 ("the source is untouched") says so. Deleting the split branch, as the way out says, closes it. This is reachable only when verification fails after check passed.
— #457, comment

AT-adopt N3: AGENTS.md:134-136 says an answer with no resolution: beside it "will be read as a finding", but check prints plan ok, exit 0, for one (the record's resolution: is optional, adopt-project.py:4992-4995). Direction: say who reads it, or let check ask for one.
— #457, body

adopt-project.py's ruleset hint still offers "The scaffold's other exit, a seed branch and a pull request…" (adopt-project.py:5248, comment at :5230, on main at f391e58), an exit #506 removed from the scaffold; tests/test_ruleset_hint_tracking_branch.py:115 pins that sentence word for word, so the fix changes both. From the review of #506 (N3).
— #459, body

AT-adopt N2: under --local-remote-dir no pull request is opened, yet execute ends with NEXT: review the pull request on <Project>, then git clone ... make bootstrap (adopt-project.py:5190, _next_steps at :5577; #493 keeps it, its condition is refused is None). Test path only.
— #457, body

Activity

  1. added this to the v1.1.0 milestone on Oct 14, 2026
  2. brettheap commented on Oct 14, 2026

    @brettheap
    ContributorAuthor

    CLAIMED — lane openRepoShape-3, session b30e8b49-f249-4668-adb1-1dbfa93c09e1@Eagle, 2026-10-14T22:30:31Z, for #523

    Logged in lanes/log/openRepoShape-3.md at 18b700084d17cc08c73c52a449be91a88e7fcc72.

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

    1. existing `CLAIMED —` comments on opensoft/openRepoShape#523:
       none
    2. `gh pr list --repo opensoft/openRepoShape --state all --search "#523"`, kept where the row or its body names `#523`:
       none
    3. `git ls-remote --heads git@github.com:opensoft/openRepoShape` branches naming `523` as a whole token:
       none
    
  3. added 2 commits that reference this issue on Oct 15, 2026
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

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions