[maxmad64bis]

⚠️ base-red inherited: #15306

Summary

Combo runs that saved the provider choice twice when the combo id matched the combo name now save it once. The dropped write carried the same provider and connection but was never read back. Pinned combos resolve the same provider as before.

Related Issues

• No linked issue — standalone duplicate write cleanup with no upstream report.

Validation

• Change type: routing
• Focused tests and category gates from the golden path
• npm run lint
• Reconciled with the current active release base; focused checks rerun afterward
• Production-code changes include a new or updated automated test in this PR

Tests Added Or Updated

• tests/unit/combo/record-lkgp-pin.test.ts — two new cases for matching id and missing id, each asserting a single combo-level write on the read key plus a read-back of the stored provider; the key assertion guards the direction of the fix because a count-only check passes with either key kept.

Coverage Notes

• open-sse/services/combo/recordLkgpPin.ts — covered by tests/unit/combo/record-lkgp-pin.test.ts (existing distinct-keys case plus the two new matching-key cases).

Reviewer Notes

• Behavior: When the normalized combo key matches the combo name, only the combo-level write is kept and the target-scoped write is skipped. The kept entry is the one every combo-level reader looks up, so the resolved pin is unchanged.
• Follow-up: The shared normalization stays inline; a later change factors the repeated fallback into one helper.