Reconcile issue, merge, rollout, and behavior separately

Model tracker lifecycle, merge state, deployment or rollout, and behavior verification as separate evidence dimensions. Query the authoritative system for each and report mismatches. Merge ancestry proves repository integration only; it does not prove enablement or observed behavior. An open issue after merge may be intentional when rollout validation remains pending, so do not label it stale without comments or owner confirmation.