Problem: A single global contributor-blacklist table is unconditionally merged into every repo's effective settings — one customer's ban entry would silently apply to another customer's repos in a shared hosted backend.
Area: ORB / Cloud
Proposal: Make the blacklist tenant-scoped, with an explicit per-tenant opt-in to share entries across their own repos (which is the legitimate use case this table serves for a single operator today).
Deliverables:
- Tenant-scoped blacklist behavior, preserving today's single-operator-many-repos convenience within one tenant.
Problem: A single global contributor-blacklist table is unconditionally merged into every repo's effective settings — one customer's ban entry would silently apply to another customer's repos in a shared hosted backend.
Area: ORB / Cloud
Proposal: Make the blacklist tenant-scoped, with an explicit per-tenant opt-in to share entries across their own repos (which is the legitimate use case this table serves for a single operator today).
Deliverables: