be post be://localhost?/<proj> recurses into a sub and fails WIRECLFL though the sub's project exists in the remote
A parent be post be://localhost?/dogs recurses (be: post abc) and the submodule push dies WIRECLFL/BEDOGEXIT, even though the sub's project DOES exist in the remote ~/.be (a direct be post --nosub be://localhost?/abc from inside the sub pushes fine). So the sub-recursion derives the wrong remote target / branch for the sub instead of pushing it to its own project in the same peer. See POST, Submodules, CLAUDE, submodule-parent-source-fetch, submodule-synthetic-branch-post.
The recursive sub push targets the wrong remote coordinate.
be post be://localhost?/dogs → be: post abc → WIRECLFL, while be post --nosub be://localhost?/abc from the sub succeeds — so the peer and project are reachable; the recursion picks the wrong target.?/libabc/.dogs (see submodule-synthetic-branch-post); the recursion likely pushes that synthetic branch / a ?/dogs-derived path instead of the sub's own ?/<subproj> on the peer.Depends on how the parent derives a sub's remote target (mirror of the parent-source FETCH logic, submodule-parent-source-fetch).
Recurse the sub push to the sub's own project on the same peer.
be post be://localhost?/<parent> pushes BOTH parent and sub (sub → its ?/<subproj> on the peer), exit 0.?/<sub>/.<parent> coordinate); resolve its remote branch like POST-013 for git remotes.