May We Ring Them

Whether this number is inside its own callable window, and what to say.

⛔THE BROWSER COULD NOT ASK THIS BEFORE, WHICH IS WHY THE DIALPAD WARNED NOBODY. No endpoint exposed a ringability verdict, so a warning would have meant a second copy of "is this a decent hour" in TypeScript -- a literal that drifts out of agreement with callable_hours, which owns the rule.

So the rule stays where it is and this route carries its answer, sentence included. Same principle as Ringable.reason: this module already owns the words an agent is shown about an hour.

⛔A READ, AND ONLY A READ. It places no call and changes nothing; the refusal that actually stops a CALLBACK is at the dial in /outbound/from-browser, because a screen's copy of the hour is as old as its last fetch and a hidden button is a convention rather than an invariant. This exists so a manual dial can be an informed override, which is what was asked for -- not so the browser can police itself.