This flow covers settings and validation for all three windows, when edited values take effect, and the warning / limit stages. ✓ = testable in this flow; · = server or backoffice boundary without a separate client screen.
✓ All three inputs are optional and default to 0 §3.1.1
✓ 0 means no limit and does not apply a minimum §3.1.1
✓ Outside cooling-off, saved changes apply immediately; success shows only “set success” §5 · AC18 AC40
✓ During cooling-off, any allowed change applies when saved and preserves the original Pause Until §5 · AC36 AC37
✓ During cooling-off, a lower value applies immediately §5 · AC38
✓ The second level displays numeric 0 for no limit, never the text “No limit” §3.3.1
✓ Placeholders are generated from configuration §3.1.1
✓ Validate Daily ≤ Weekly ≤ Monthly only among configured values §3.2.1 · AC12
✓ A validation error affects only that row §3.2.1 · AC13
✓ Cooling-off switch 1 allows entry to the adjustment page §5 · AC15
✓ Cooling-off switch 0 removes underline and arrow and blocks entry §5 · AC16
✓ Outside cooling-off, adjustment works normally §5 · AC17
✓ Warning reached: value turns red and notification names the window §3.3.1 · §4.3.1 · AC21
✓ Limit reached: the triggering bet settles first, then the limit is evaluated §2.3.1 · AC1 · AC2
✓ Turnover above the limit is shown as-is, without capping §2.3.1
✓ One bet crossing multiple windows sends only the notification with the largest limit §4.3.1 · AC23
· Current turnover resets at the natural-period boundary; limit-evaluation count resets when cooling-off ends §3.3 · §4.2 · AC9 AC31
· Report rows show current values; change history is kept in the audit log §7.3.1 · AC25 · AC27
· Backoffice does not cross-validate the six min/max settings §6 · AC14
You have reached {N}% of your {daily/weekly/monthly} betting limit.You have reached your {daily/weekly/monthly} betting limit. Betting is paused until {time}.Please ensure Daily ≤ Weekly ≤ Monthly limitsMust follow Daily ≤ Weekly ≤ Monthlyset successRemember to play responsibly and stay within your comfort level. Your full access will be resumed at {MM/DD/YYYY HH:mm:ss}