When a custom deserialization hook method (e.g., DeserializeFunctionArgumentsValue) declares a ModelReaderWriterOptions options parameter, the generated deserialization code at the call site does not pass the options value through(e.g. DeserializeFunctionArgumentsValue).
Expected behavior
The generated code should forward the options parameter to the custom deserialization hook:
DeserializeFunctionArgumentsValue(prop, ref functionArguments, options);
Impact
This forces custom deserialization hooks to hard-code ModelSerializationExtensions.WireOptions instead of flowing the caller-provided options, which may behave incorrectly in non-wire serialization scenarios.