From 0819fd9c92c73b810829477d82833f9b916db091 Mon Sep 17 00:00:00 2001 From: JUN Date: Sat, 12 Sep 2026 20:45:24 +0900 Subject: [PATCH] docs(structure): record what clear-cooldown does to a lapsed window #4397 made a live avoidance window its own reason for the clear-cooldown operation to act, which changes the operator-facing contract. structure/INDEX.md maps src/codex/ to this document, so the SSOT has to say that a lapsed cooldown with a live window still reports a clear, and that an account with neither still reports no change. --- structure/providers/openai-tiers.md | 6 ++++++ 1 file changed, 6 insertions(+) diff --git a/structure/providers/openai-tiers.md b/structure/providers/openai-tiers.md index 92737b5301..6fdc920b02 100644 --- a/structure/providers/openai-tiers.md +++ b/structure/providers/openai-tiers.md @@ -104,6 +104,12 @@ cooldown it belonged to, and both operator escapes remove it: clearing a cooldow account each clear the window from the account-wide entry and from every scoped entry, because a reset-derived refusal records only the scoped one. +Clearing a cooldown is also the management operation for a window whose cooldown has already +lapsed. Because the cooldown is the shorter of the two durations, the state an operator usually +finds is an expired cooldown and a live window, so a live window alone makes the operation +succeed and report a clear. An account with neither reports no change, which is what keeps the +route from disclosing whether an account exists. + A confirmed manual reset-credit consumption may immediately reconcile that account's eligible pre-existing ordinary reset-derived cooldown after a complete, non-exhausted usage observation started after the reset. Paused or reauthentication-required accounts and