v0.49.0
Make resolve reliable: config.resolveFields binds a field (by selector substring) to a resolver, and the executor fills it from the resolver no matter what the plan put there — so OTP/token flows are deterministic regardless of what the LLM planned. Plus: value_ref/url_ref names are normalized (OTP_CODE/otp-code -> otp_code) and tolerated by the schema, and a goto with url_ref now validates. Validated live.