Sync: four open product decisions blocking anything beyond the Linear-only path

Four decisions the sync engine needs before it can be turned on beyond its current Linear-only path. Each is a product call, not an implementation question.

1. Which Linear team receives Outpost issues. The adapter needs a destination team; there is no default that is obviously right.
2. All tickets, or escalated-only. Pushing every community ticket into Linear will bury the engineering backlog. Escalated-only is the conservative default but needs agreement.
3. Conflict-queue UI. When both sides change the same field, something has to arbitrate. Today the loser is silently discarded (#139 covers the mechanical bug; this is the product surface for the conflicts that remain after it is fixed).
4. Reconcile generic TRACKER_SYNC against per-plugin LINEAR_SYNC. Two job types overlap. One should win, and the other should be removed rather than left as a second path that drifts.

Fix

Decide 1 and 2 first — they gate turning sync on at all. 3 and 4 can follow.

Start with the four product decisions in issue #210, prioritizing the Linear destination team and ticket filtering. Read issue #139 for the related conflict-handling context. This is done when the four decisions are explicitly resolved and the intended sync path is recorded; no implementation file or test is named.