Count customer-pipeline overlap by workstream, not PR volume

When mapping weekly engineering activity to customer commitments, de-duplicate pull requests into ticket or feature families and separate direct customer-visible delivery, enabling or platform work, and unrelated operations. Alternate implementations, forward-ports, reverts, and hotfix chains can inflate raw PR counts. Keep merged-to-staging, merged-to-production, production-tested, and customer-confirmed as distinct states.