You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
adopt-project.py: five printed sentences say what the run does not do: the Makefile follow-up beside a root Makefile, the contracts/-only read-across path, execute would stop there, a path names no attribute, and WHAT WILL HAPPEN under --local-remote-dir #906
Goal: each follow-up, finding and plan line that adopt-project.py prints says what the run does.
Filed by lane openRepoShape-3, from its triage of #457 at the v1.1.1 release commit 5017830. It groups #457's lines L2-72, L2-73, L1-91, L1-93 and L1-75, one pull request's worth.
State at 5017830. Read, not run.
L2-72.follow_ups_for (adopt-project.py:3303) adds "the root Makefile wires CONTRACTS_DIR to the contracts/ of the spec leg ..." whenever the spec leg holds contracts/ (:3346-3351). It adds it even where the source keeps its own root Makefile. Then the shape's Makefile, with the block, is written beside it as shape/Makefile, and the root Makefile wires nothing until the two are merged. Lane 2 measured this on 4cf5fb07: make contracts-dir says No rule to make target.
L2-73.contracts_from_code_leg (:3258) returns nothing unless a path of the spec leg is contracts/ or lies under it (:3283). So a code file that names specs/ gets the key-form read-across line and no ready path, where v1.1.0 printed ../spec/specs/.
L1-91._refused_finding (:10444-10448) says "execute would stop there, after the leg repositories exist". For * working-tree-encoding=UTF-16LE with .gitattributes exempted, execute stops earlier, mounting the legs, on .gitmodules.
L1-93. The docstring at :9675 says "A target that is a path names no attribute". That holds only for a link target with no space.
L1-75. Under --local-remote-dir, WHAT WILL HAPPEN still prints create <Project>-spec and <Project>-code (private) (:8575-8580), though a bare repository has no visibility.
CLAIMED — lane openRepoShape-1, session 300f8f46-004a-4e72-8587-4f192be2e108@Eagle, 2026-10-18T15:00:57Z, for #906
Logged in lanes/log/openRepoShape-1.md at 62248f5960d2ea2258e25122e75b8ff680a65366.
The three reads (lane-collision-protocol Rule 1):
1. existing `CLAIMED —` comments on opensoft/openRepoShape#906:
none
2. `gh pr list --repo opensoft/openRepoShape --state all --search "#906"`, kept where the row or its body names `#906`:
none
3. `git ls-remote --heads git@github.com:opensoft/openRepoShape` branches naming `906` as a whole token:
none
Activity
brettheap commentedon Oct 18, 2026
CLAIMED — lane openRepoShape-1, session 300f8f46-004a-4e72-8587-4f192be2e108@Eagle, 2026-10-18T15:00:57Z, for #906
Logged in
lanes/log/openRepoShape-1.mdat62248f5960d2ea2258e25122e75b8ff680a65366.The three reads (lane-collision-protocol Rule 1):
adopt-project.py, shape_materialize.py: `execute` is said to stop at …
adopt-project.py and README.md: the Makefile follow-up names a kept `…