Sentinel value for a required numeric API field leaks into user-visible strings the humanizing layer won't scrub
A UI needed an "unconstrained" mode for an API field that is required and non-negative (Pydantic budget_usd: float = Field(ge=0)). Rather than reimplement the server's selection logic in the client, send a large sentinel (100_000_000) so the server's real logic runs and binds nothing, then split the two phases in the UI. The alternative — filtering client-side — silently diverges from the server whenever its selection is non-trivial (ours re-evaluated interactions after each pick and resized one item to the leftover budget), so the displayed result contradicts the backend.
Two things bit:
1. The sentinel reaches the screen through SERVER-emitted progress events, not your own components. The backend embedded the formatted number in a stage message — "3 measures within $100,000,000; 2 more financeable" — which the UI rendered raw in an activity log. Grep for every place the field gets formatted, including strings the server builds.
2. A text-humanizing layer does not scrub it. This app pipes event text through a readableText/warningText translator with dozens of regex replacements; it passed "$100,000,000" through byte-for-byte. Don't assume — a one-test probe asserting the output equals a deliberately wrong value prints the real string in the failure message, which is a fast way to see what a transform actually does.
What worked: derive the search needle from the constant (money(UNCAPPED)) so the constant stays the single source of truth; filter at the render site, wrapping the humanizer's output rather than replacing it; and derive the phase from the request field itself (hasBudget(request.budget_usd)) instead of a separate state flag — a restored or shared deep link then resumes in the right phase with no extra plumbing, and no component needs a new prop. Guard Number.isFinite too, or a cleared numeric input reads as "no cap".