adopt-project.py: after the hand edit of legs.spec_path or legs.code_path it asks for, the read-across follow-up and the contracts/ rule's reason still name the plan-time paths

The read-across follow-up and the contracts/ rule's reason should name legs.spec_path and legs.code_path by key, so the hand edit the tool itself asks for leaves no plan-time path behind in check's output, the split commit's message or the pull request body.

From the checklist triage of 2026-10-15; Brett Heap approved its recommendations at 2026-10-15T16:49:38Z. One pull request covers the lines below.

Lands after: #572 and #566.

Lines

L2-18: after the hand edit of legs.spec_path or legs.code_path that the tool asks for, the read-across follow-up keeps plan-time paths. Where: adopt-project.py cross_leg_references (:1726-1728), follow_ups_for. Effort S; all. On main 26c1600: At 26c1600 plan renders the list once (:3401), with {code_path}/… and ../{spec_path}/… values (:1726-1728), and check (:5837) and execute (:8294) read it back from the plan; open adopt-project.py: the Makefile block execute appends and the cross-leg follow-up name each leg where the plan mounts it, so --spec-path legs/spec exports a CONTRACTS_DIR that exists and a nested --code-path gets the right ../ path (#522) #572 at 22ce69b rewrites only the Makefile line to name legs.spec_path and still renders this line from the plan-time values. (source)

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

L2-19: the contracts/ rule's reason: says ../spec/contracts from code/, which is false for a nested plan. Where: contracts/path-classification.yaml:299-300. Effort S; all. On main 26c1600: Unchanged at 26c1600 (:299-300); contracts/path-classification.yaml: a source's own single-repository.yaml is asked drop or root, drop by default, under its own rule, so adopt-project.py plan no longer asks a record no leg reads the spec, code or root question (#528) #566 edits this file only at its header and in a new rule (hunks at :33 and :419), and adopt-project.py: the Makefile block execute appends and the cross-leg follow-up name each leg where the plan mounts it, so --spec-path legs/spec exports a CONTRACTS_DIR that exists and a nested --code-path gets the right ../ path (#522) #572 does not touch it, so the fix waits for contracts/path-classification.yaml: a source's own single-repository.yaml is asked drop or root, drop by default, under its own rule, so adopt-project.py plan no longer asks a record no leg reads the spec, code or root question (#528) #566. (source)

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

L2-18 (P3; adopt-project.py, #572 review): after the hand edit of legs.spec_path or legs.code_path that the tool itself asks for, the read-across follow-up that plan wrote still names the plan-time paths.

follow_ups_for (adopt-project.py:1733) calls cross_leg_references (:1618-1693) once, at plan (:1751), at 9ddb7ef. MOUNT_REMEDIATION (:7311-7324) tells the person to change legs.spec_path or legs.code_path, and plan-leg-path-collides says the answers "are edited after plan writes them" (:1979-1984). execute then mounts the legs at the edited paths.

So check's output, the split commit's message and the pull request body keep saying code/... and ../spec/contracts/ for a layout that no longer has them. Probe: review572-9ddb7ef/tools/l2rv522-handedit.py. The same on main bfed143. adopt-project.py: the Makefile block execute appends and the cross-leg follow-up name each leg where the plan mounts it, so --spec-path legs/spec exports a CONTRACTS_DIR that exists and a nested --code-path gets the right ../ path (#522) #572's review F1 covers the Makefile line of the same follow-up list (it names the key); this is the other line, and adopt-project.py: the tracking branch defaults to the source's default branch, topics are set before the pull request, and NEXT names scripts/bootstrap.py when the shape's Makefile went aside (#479, #480, #481) #493-F3's staleness for the leg paths.

Direction: name the keys and not their values, as adopt-project.py: the tracking branch defaults to the source's default branch, topics are set before the pull request, and NEXT names scripts/bootstrap.py when the shape's Makefile went aside (#479, #480, #481) #493-F3 did for tracking_branch (:1745-1750), or have execute render the list from the plan it reads.

— #457, comment

L2-19 (nit; contracts/path-classification.yaml, #572 review): the contracts/ rule's reason: says ../spec/contracts from code/, and every matching plan entry copies it.

contracts/path-classification.yaml:299-300 at 9ddb7ef: "spec/contracts from the root, ../spec/contracts from code/".

For a nested plan, such as --spec-path legs/spec --code-path impl/code, the entry's reason contradicts the corrected follow-up a few lines below it. It was there before adopt-project.py: the Makefile block execute appends and the cross-leg follow-up name each leg where the plan mounts it, so --spec-path legs/spec exports a CONTRACTS_DIR that exists and a nested --code-path gets the right ../ path (#522) #572.

Direction: path-free wording in the reason ("read across the assembly-root mount"). contracts/path-classification.yaml: a source's own single-repository.yaml is asked drop or root, drop by default, under its own rule, so adopt-project.py plan no longer asks a record no leg reads the spec, code or root question (#528) #566 also edits this file (the policy header at :30-35), so sequence it after contracts/path-classification.yaml: a source's own single-repository.yaml is asked drop or root, drop by default, under its own rule, so adopt-project.py plan no longer asks a record no leg reads the spec, code or root question (#528) #566.

— #457, comment

CLAIMED — lane openRepoShape-2, session 81650e29-c906-4fe8-96c9-55580bfe0c44@Eagle, 2026-10-15T18:21:18Z, for #600

Logged in lanes/log/openRepoShape-2.md at de584552a0ed32dde63d09ee75e98322e1efc6bf.

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

1. existing `CLAIMED —` comments on opensoft/openRepoShape#600:
   none
2. `gh pr list --repo opensoft/openRepoShape --state all --search "#600"`, kept where the row or its body names `#600`:
551	tests/test_repo_hygiene.py and docs/handbook.html: each handbook section records the hash of every README section it reads, and README.md's line cap is 1422 plus one file per raise in tests/readme-cap.d/, so two README pull requests no longer conflict on the footer's one blob or the cap's one line, and a stale page names exactly which sections to re-read (#519)	l3-519-handbook-section-hashes	MERGED
3. `git ls-remote --heads git@github.com:opensoft/openRepoShape` branches naming `600` as a whole token:
   none

Merge origin/main 8f453d0 into fix/600-adopt-leg-keys

adopt-project.py: `check`'s "mount the legs at" line and the split me…

adopt-project.py: the read-across follow-up names `legs.code_path` an…

Merge origin/main (de92614) into l3-563-docs

README.md, the handbook and the v1.1.0 notes: the adopted repository …

Navigation Menu

Repository navigation

adopt-project.py: after the hand edit of `legs.spec_path` or `legs.code_path` it asks for, the read-across follow-up and the `contracts/` rule's reason still name the plan-time paths #600

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

adopt-project.py: after the hand edit of legs.spec_path or legs.code_path it asks for, the read-across follow-up and the contracts/ rule's reason still name the plan-time paths #600

Description

Activity

brettheap commented on Oct 15, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions

adopt-project.py: after the hand edit of `legs.spec_path` or `legs.code_path` it asks for, the read-across follow-up and the `contracts/` rule's reason still name the plan-time paths #600