Settle commercial identity nuances with consolidated enums and linking rules

Add commercial-identity-nuance-settlement.md resolving control_basis,
binding_trigger, cross-registry Synonymity strengths, OPI branch modeling,
escrow commitment type, reputation portability, payment edge cases, CRM renewal
rules, Person Account adapters, and eIDAS wallet scope. Update canon, OpenQuestions,
and all commercial-identity source notes.

research/commercial-identity/crm-pipeline-commitment-threshold.md

@@ -141,10 +141,13 @@ tier — internal sales telemetry). They support **Trust Relationship** only for
 
 ## Open Questions
 
-- Standard `binding_trigger` enum for cross-CRM adapters.
-- Whether **renewal Opportunity** on existing contract is Pipeline Pursuit or
-  commitment amendment (lean: amendment on existing Commercial Commitment).
-- Partner Opportunity vs. customer Opportunity — same Pipeline Pursuit type with role metadata.
+*(none — settled in `commercial-identity-nuance-settlement.md`)*
+
+## Settled
+
+- `binding_trigger` enum — seven values including `org_policy_closed_won`.
+- Renewal on same contract → commitment amendment; rebid → new Pipeline Pursuit.
+- `pursuit_role`: customer | partner | vendor on Pipeline Pursuit.
 
 ## References