RULESET_HINT hard-codes main as the local branch and as --base, so under --tracking-branch trunk the hint's git push -u origin main:seed/scaffold names a branch the work clone does not have and its gh pr create --base main opens against the wrong base #324

Lane: openreposhape-3 (openRepoShape-3)

What happens. The hint printed when a leg or root push is refused says:

git -C <work> push -u origin main:seed/scaffold
gh pr create --repo org/Atlas-spec --base main --head seed/scaffold --title 'Seed the spec leg' ...

scaffold-project.py --tracking-branch trunk creates the work clones with git init -b trunk and pushes trunk. Measured on be2790e, in a clone made with git init -b trunk that already pushed trunk: the hint's push exits 1 with error: src refspec main does not match any. The --base main names a branch the repository does not have. Measured for the scaffold's path; not run for the other callers (below), which pass the same constant.

Where. scripts/shape_materialize.py:RULESET_HINT (:578-592). Printed from scaffold-project.py:_seed_legs (:1027) and _build_assembly_root (:1142), scripts/family.py:_create_holder_worktree (:732), adopt-project.py:_extract_leg (:2517) and _seed_leg (:2565).

Why it matters. It is the advice a person follows when a ruleset has just refused a direct push, the case the hint exists for, and for a non-main tracking branch it fails on the first command. #209 (closed) fixed the same wrong main in update-shape.py's gh pr create. #177 (open) is about the same constant's origin advice and its "listed above"; parameterising the hint for #177 can take the branch too.

Source. PR #218, ## Left out, first bullet.