sh.git ~/.local/bin on lezama: same parent shape, evidenced version-string collision 2026-08-30

PATH sh.git checkout ~/.local/bin, same shape as parent case, on lezama specifically. WHO WRITES: nw-lezama-cc + bin-lezama-cc both commit into this single working tree on lezama (also bin-venus-cc/bin-whey-cc push into the same origin, pulled here). ISOLATION: none - one shared checkout, convention only (gitpush.sh --only, never add -A; a manual git commit without gitpush.sh skips the Agent: trailer and trips push-scope-guard). COLLISION EVIDENCED, not hypothetical: 2026-08-30, I bumped rutap-watch.sh to VERSION=2.3 for the /resource-lezama->/data-lezama path rename; bin-whey-cc independently authored an uncommitted mkdir-p fix under the SAME version string 2.3. git pull on whey refused rather than silently picking one - caught by version-string collision, not by any lock. bin-whey-cc merged both edits as VERSION=2.4 (commit cffc2ee); I verified nothing was lost. INSTRUMENT USED: git log --format Agent: trailer count on ~/.local/bin (12 bin-venus-cc, 9 bin-whey-cc, 6 bin-lezama-cc, 1 nw-venus-cc, 1 monitor-context-cc across last 30 commits) - not file permissions, not git author (git user is uniformly 'Elazar Pimentel' on all hosts, author name does not distinguish agent). FIX: already being decided fleet-wide under OPS-157 (tree per agent) / OPS-158 (deploy versioned artifact); no independent lezama action needed, this is corroborating local evidence for that decision.