AppIntents Parameter requestValue not working in iOS 18 when parameter is not in parameterSummary

In iOS 18, the requestValue method no longer works when the parameter it is called on is not included in the parameterSummary of an AppIntent. This issue causes the app to fail to present a prompt for the user to select a value, resulting in an error with the message:

Domain=NSCocoaErrorDomain Code=4099 "The connection from pid 40685 on anonymousListener or serviceListener was interrupted, but the message was sent over an additional proxy and therefore this proxy has become invalid."

Steps to Reproduce:

1. Create a simple AppIntent with the following code:

import AppIntents

struct Intent: AppIntent {
    static let title: LocalizedStringResource = "Intent"
    
    static var parameterSummary: some ParameterSummary {
        Summary("Test \(\.$category)") {}
    }

    @Parameter(title: "Category")
    private var category: CategoryEntity?
    
    @Parameter(title: "Hidden Category")
    private var hidden: CategoryEntity?
    
    @MainActor
    func perform() async throws -> some ReturnsValue<CategoryEntity?> {
        var result: CategoryEntity?
        do {
            result = try await $hidden.requestValue("Select category") // Doesn't work since iOS 18 as $hidden is not set in parameterSummary
        } catch {
            print("\(error)")
        }
        
        return .result(value: result)
    }
}

1. Run the code on a device with iOS 18.
2. Observe that the requestValue method fails to present the selection prompt and instead throws an error.

Expected Results:

The app should successfully present a prompt for the user to select a value for the hidden parameter using requestValue, even if the parameter is not included in the parameterSummary.

Actual Results:

The app fails to present the selection prompt and throws an error, making it impossible to use requestValue for parameters not included in parameterSummary.

Version/Build:

iOS 18.0

Configuration:

Tested on various devices running iOS 18.

Is there a change in the API that I might have missed?