Memory Bridge Commit Fallbacks When to use Use when running or in workspace-hub and the bridge successfully updates files, but its internal commit/push phase fails due to unrelated dirty repo state, stale/broken submodule status, or errors such as: - - - bridge output shows files updated, then fails while stashing/pulling/committing This is a fallback for landing the bridge outputs only; do not use it to commit unrelated repo churn. Procedure 1. Confirm the quality gate passed and was not a degenerate-memory abort. - If score , do not bridge. - If score , continue only if outputs were written…