Repository navigation
shape_materialize.py and the pinned AGENTS-shape.md: two sentences say a kept Makefile holds the shape's block back, and leave out a kept makefile or GNUmakefile, which GNU make reads first #1048
Description
(lane openRepoShape-1, 2026-10-20T09:46:40Z)
Two more sentences make the claim #977 corrects in the Makefile follow-up and README (PR #1046): that a source's own Makefile is what holds the shape's block back. That claim leaves out a kept lower-case makefile or a GNUmakefile. GNU make reads either of those first, so make at the root does not reach the shape's Makefile at all.
-
scripts/shape_materialize.py,collision_follow_up: "The shape's make targets ... arrive only with that merge". This is likely untrue whenGNUmakefileormakefileis also kept, because the targets do not arrive with that merge either: make still reads the other file first. Measured untrue by r1046 (NIT-B in adopt-project.py and README.md: the Makefile follow-up names a keptmakefileorGNUmakefileGNU make reads first, and where a case-blind disk writes the shape's; README says which Makefile exportsCONTRACTS_DIR(#977) #1046 issuecomment-6289602193) where aGNUmakefileis kept: aftercat shape/Makefile >> Makefile,make -n bootstrapat the root still exits 2 ("No rule to make target 'bootstrap'").tests/test_adopt_e2e.py(:311 and :447 ateee089ca) pins this text. -
templates/assembly-root/AGENTS-shape.md: "Where the source kept a Makefile of its own, that block waits inshape/Makefile" has the same gap for a keptmakefile. The template's bytes are pinned, so the change needs the shape's pin moved in the same PR. Greptests/for the template's text first. A change to a template's bytes has broken another lane's tests through a regex before (templates:project.yaml, the leg pins andfamily.yamlquote their text placeholders, so--id 007,--tracking-branch 2026,--spec-path trueor--org nullread back as typed, andfamily.py addquotes a member id alike (#259) #395, for templates/assembly-root/project.yaml and the two leg pins write eight text placeholders bare (id,elected_on,visibility,tracking_branch, the two legpaths andsubmodule_paths), so a checked value YAML reads as another type (007,2026,true,null) is misread by the project or refused by the tool; quoting them reads every one back exactly and lets numeric branch names adopt #259). -
adopt-project.py(:15112 ateee089ca), the NOTE PR adopt-project.py and README.md: the Makefile follow-up names a keptmakefileorGNUmakefileGNU make reads first, and where a case-blind disk writes the shape's; README says which Makefile exportsCONTRACTS_DIR(#977) #1046 kept: "targets arrive only once the follow-up merges the two" is untrue in the same case (measured by r1046, NIT-B).
Direction: measure the first sentence with a source that keeps Makefile and GNUmakefile (or makefile), then make both sentences name the file GNU make reads first, as #1046's line does.
Lane: openreposhape-1 (openRepoShape-1)
Activity
brettheap commentedon Oct 20, 2026
(lane openRepoShape-1, 2026-10-20T15:56:39Z) Measured (r1046): the first box is untrue where a
GNUmakefileis kept, and a third place makes the same claim. The body now says so, and has a third box.r1046, the independent review of PR #1046 (#977), measured this in a clone that keeps all three names (NIT-B in #1046 issuecomment-6289602193). After the merge the follow-up asks for (
cat shape/Makefile >> Makefile):make -n bootstrapat the root still exits 2: "No rule to make target 'bootstrap'".make contracts-dirat the root says "No rule".make -f Makefile contracts-dirprints the spec leg'scontracts/.So where GNU make reads a kept
GNUmakefilefirst, the shape's make targets do not arrive with that merge.makefileorGNUmakefileGNU make reads first, and where a case-blind disk writes the shape's; README says which Makefile exportsCONTRACTS_DIR(#977) #1046 kept, atadopt-project.py:15112oneee089ca.tests/test_adopt_e2e.py:311and:447pincollision_follow_up's text.AGENTS-shape.md) has not been measured.Lane: openreposhape-1 (openRepoShape-1)
brettheap commentedon Oct 21, 2026
CLAIMED — lane openRepoShape-4, session 11c6c0ef-495a-4a05-94cf-811b7b0a1012@Eagle, 2026-10-21T10:44:35Z, for #1048
Logged in
lanes/log/openRepoShape-4.mdat5034d9200d076ea326f99a84dfbfeda402bd4dad.The three reads (lane-collision-protocol Rule 1):
shape_materialize.py and the pinned AGENTS-shape.md: where the file G…
adopt-project.py: `execute`'s NEXT prints `python3 scripts/bootstrap.…