template-broadcast

Multi-project downstream template synchronization is automated by applying upstream template changes to all active projects listed in references/projects.md, coordinating pre-flight checks, per-project updates, and consolidated reporting.

Diff-aware template broadcasting preserves project-specific files by applying differential updates that avoid deleting upstream-only files, ensuring project-only configurations remain intact while propagating upstream template changes safely.

The best way to bulk propagate template configuration changes is using a broadcast workflow that applies updates to all registered downstream projects consistently, providing robust error handling and clear progress feedback during synchronization.

Yes, broadcasting template updates to multiple downstream projects preserves project-only files through diff-aware updates that prevent the deletion of upstream-only files, ensuring project-specific modifications remain safe during bulk synchronization.

When a pre-flight check fails during downstream template synchronization, robust error handling captures the failure, halts the per-project update, and includes the error status in the consolidated reporting for review.

Active downstream projects are registered in the references/projects.md file, which the broadcast workflow reads to determine the target projects for receiving upstream template synchronization updates.