- Ya
- 21 Agosti 2026, 02:47 UTC
- Mwandishi
- Kamo
- Ahadi ya
- a08b1f9
FFA bypassed the credit system outright, which left a manager with no lever over it: Max Daily Spend sat behind if (!ffa) and could not cap an FFA product, and "accepted today" had no rows to count because nothing was ever spent. An FFA acceptance now mints a credit and spends it on the lead in the same block as the claim, so the spend record always exists and can never drift from the assignment. Max Daily Spend moves out of the credit-only branch and applies to both paths — free-for-all means the member was not granted a balance to pay from, not that a manager cannot bound how many they take in a day. Deliberately still credit-only: the org-wide credit switch and the balance check. FFA has no balance to be short of. The cap is checked AFTER those, so a credit member who is both broke and capped keeps reporting INSUFFICIENT_CREDITS. Note AcceptResult.creditSpent is now true on the FFA path (it was documented as always false). It is accurate — a credit really is consumed — and it reaches the accept response and the publishAssigned NATS payload. LeadAssignmentType still records AUTO_ASSIGN for FFA, so history keeps the two apart.