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/reputation-assurance-gradient.md

@@ -222,13 +222,14 @@ Evidence Source before modeling.
 
 ## Open Questions
 
-- Standard `assurance_tier` enum vs. numeric score with tier mapping.
-- Whether platform escrow counts as `committed` or `observed` when no separate
-  contract artifact exists (lean: committed when funds legally segregated).
-- Cross-platform reputation portability — Synonymity between Reputation Signals
-  across scopes?
-- Smart-contract automated adjudication (on-chain oracle outcome) — observed or
-  adjudicated?
+*(none — settled in `commercial-identity-nuance-settlement.md`)*
+
+## Settled
+
+- `assurance_tier` primary; optional `numeric_score` + `score_scale` downstream.
+- Segregated escrow → Commercial Commitment `commitment_type: escrow`.
+- Reputation portability → Synonymity `linked_to`, weak default.
+- Oracle release → observed; ADR/court → adjudicated.
 
 ## References