bridge-synclisted

# Bridge Sync — Batch end-of-sprint upstream sync `/bridge-sync` is the **wide-net** complement to `/promote` and `/contribute`. | Skill | Granularity | Use case | |---|---|---| | `/promote` | per-commit | "promote this batch of recent commits" | | `/contribute` | per-file | "scan for upstream-worthy files, adapt, PR" | | `/bridge-sync` | per-sprint | "push EVERYTHING pending to both upstreams now" | Read the referenced file ONLY when triggered. ## When to use - End of a work-sprint, ready to publish all upstream-worthy changes at once - After a refactor that touched many CORE+org files — manual cherry-pick is tedious - When `/promote` has been deferred for days and there's a backlog - When you want both `bks-lab/open-bridge` and your org overlay updated in one operation **NOT** for: - A single commit (`/promote` is leaner) - File-level adaptation work (`/contribute --adapt` does that) - USER-only changes (those stay local) ## Arguments | Argument | Effect | Default | |---|---|---| | `(none)` | Full sync to both upstreams | — | | `--dry-run` | Show routing matrix, don't push | false | | `--repo open-bridge` | Sync only to open-bridge | both | | `--repo <your-bridge>` | Sync only to your org overlay | both | | `--since <ref>` | Sync commits since this ref (default: last sync tag) | last sync | | `--no-scrub` | Disable open-bridge scrubbing (DANGER — only for emergency) | false | ## Prerequisites - Current branch must be `user/*`. Refuses on `development` / `main`. -