be post advances the current branch — worktree→repo commit and/or fast-forward push, recursing into mounted submodules. Tickets below tighten its commit-message handling, push transports, and no-op reporting. Each entry is one active ticket with its live state; an entry drops off once the whole ticket lands (landed commits stay on the board's POST line). The fix-and-land method is Issues.
POSTCFLCT false-fires on conflict-marker strings in tracked source comments/literals (e.g. sniff/PATCH.c:339), forcing a blunt --force. Recognize only the real WEAVE output shape, not any inline <<<<…||||…>>>> occurrence.put: banner (staged 1 put row(s)) leaks into the MIDDLE of be post when a submodule advanced; the bump already shows as mod <sub> in the parent post rows. Suppress the standalone put banner for the internal path. Surfaced by POST-018/BE-005.
POST-021 (git-scheme push BNOROOM — BASS exhaustion: per-commit walk scratch never rewound + unused walk buffer; skip it, route the walk through try(), size pack buffers) landed 387a6f99; test/post/46. POST-022 (sub-push wrecked output: bare per-row label + full-history dump) subsumed + fixed by BE-007 1a006d08; test/post/48. POST-020 (git-push post path raw-printf'd sniff: N change(s) + the keeper synthetic-coordinate notice → both now ride post: ROWS) landed 8c7f5f3a; repro test/post/25-dot-branch-no-git-wire, post/13 grep repointed. POST-018 (be post/be put confirmations bypassed the shared ROWS banner) landed 95252ffd + 0ac49e6a (put:/post: banner on stdout). POST-017 (refused be post was non-atomic — POSTCFLCT scan ran mid-pack-feed, so KEEPPackClose persisted orphan objects + a rewritten idx before refusing; hoisted all validation to a pre-flight before any store write) landed f5b41282; test/post/42. Follow-up still open: be-level scan-before-sub-recursion ordering (DISPATCH.c:446).