Identity Server connect/authorize Does Not Pass Back Same State

[Mike-E-angelo]

I've been exploring eShop for the past day, with Maui-integration especially, and ran into the following issue:
dotMorten/WinUIEx#195

Upon inspection it appears that the state being passed into connect/authorize:

https://localhost:5243/connect/authorize
	?client_id=maui
		&
		request_uri=urn%3aietf%3aparams%3aoauth%3arequest_uri%3a2570D19BBB1F7FED8A9FCF756C6775A8131214F6FF3518E48F995C9DDABBAAC2
		&
		state=%7b%22appInstanceId%22%3a%22%22%2c%22signinId%22%3a%2236b7da9a-b9e4-4828-b315-f8e6fa44cc4b%22%7d

Is different from what is passed back into the target application on callback:

maui://authcallback/?
	ode=B985916E25D787B867DCDC8C96413A7E15F416B79B61D279850ACDE2F748977E-1
	&
	scope=openid profile basket orders offline_access
	&
	state=DyjXbgvFk1k6NdSsZ-2jiA
	&
	session_state=Jg2lFiZZMthU_f6a2YdXZXci1aHApme-3zaltAarG_c.9EAAE4B3A1F1C7175692A84F7EE88845
	&
	iss=https%3A%2F%2Flocalhost%3A5243

I looked into IdentityServer, and it "states" (😏) that the state is supposed to be passed back as-is:

https://identityserver4.readthedocs.io/en/latest/endpoints/authorize.html

identityserver will echo back the state value on the token response, this is for round tripping state between client and provider, correlating request and response and CSRF/replay protection. (recommended)

So, color me confused here and I would appreciate some clarity around this if at all possible. 🙏