Suite git branch and sync workflow for pilot teams

ID	M1-CLOUD-004
Status	not_started
Priority	p0
Milestone	m2-internal-adoption-design-partners
Owner	ui-design-frontend-dev

Problem

Pilot teams have no way to manage Git branches or sync dashboard changes from within Cloud Suite. Any Git operation — creating a branch, pulling upstream changes, pushing edits, resolving conflicts — requires manual backend intervention or CLI access that analysts don't have. Without a minimum viable Git workflow in the UI, pilot teams cannot safely collaborate on shared dashboard projects or maintain version control over their analytics content.

Context

Pilot users can create/use branches and sync changes in Suite reliably.
Conflict and stale-branch handling is visible and recoverable.
Git workflow is validated on at least one active pilot project repository.

Possible Solutions

A - Keep branch and sync work fully manual outside the product: low implementation cost, but poor pilot UX.
B - Recommended: ship a focused pilot branch/sync workflow in Suite: cover branch creation, pulling latest changes, push/sync status, and basic conflict guidance.
C - Attempt full Git parity with desktop tools: too much scope for the pilot phase.

Plan

Implement branch selection/create flow and repo sync actions in Suite UI.
Add status and conflict messaging for pull/push sync operations.
Run pilot validation with real repo workflows and collect friction data.
Document recommended branch workflow for internal analysts.

Implementation Progress

issue #301 for broader model
integrations-platform repository auth setup

QA Exploration

[ ] QA exploration completed (or N/A for non-UI tasks)

Review Feedback

[ ] Review cleared