Git Merge Base Candidates Visual

Inputs: [branch refs], [commit graph], [git merge-base --all output], [repository rules]. Review common ancestors of two branches using read-only Git evidence. Preserve every merge-base candidate when criss-cross history produces several; do not choose one arbitrarily or perform a merge. Distinguish graph ancestry from commit date order. Produce a commit graph highlighting all supplied best common ancestors without invented edges. Include one concrete verification step that checks the defining task detail against the supplied inputs. Use [audience] and [tone] to calibrate presentation.

Use the attached references only for the specified visual attributes. If a required reference is missing, request it before generation. Produce one finished image with a deliberate focal point, consistent geometry and clean margins. Keep any exact wording on a separate editable label layer or leave its area blank. Do not invent evidence or present an illustration as documentary proof.