v2.5.1

• context_size_map now takes precedence over the live models.dev fetch. It was previously merged into the built-in table, which is consulted after the models.dev lookup — so with fetch_context_from_modelsdev enabled, an automatic remote match silently overrode your explicit manual entry. It's now resolved in its own tier, right after override/num_ctx and before models.dev and the static table (source user_map in the debug payload), matching how price_map already beats models.dev for cost. Consequences: a map entry now wins outright on any substring match (even against a longer static/models.dev key — the same semantics as price_map); a falsy size (0) is skipped and falls through; parsing is per-entry tolerant (one bad value drops only that entry). It's returned uncached, so edits take effect immediately.