h2: spec test that a GOAWAY names the last processed peer stream
RFC 9113 6.8: the GOAWAY last-stream-id is "the highest-numbered stream identifier for which the sender of the GOAWAY frame might have taken some action on or might yet take action on". After the server processes a peer request on stream 3, both a connection-error GOAWAY (triggered here by an oversized frame, unrelated to any stream id) and a graceful Server.goaway must advertise last-stream-id 3, not 0. Advertising 0 tells the client none of its requests were acted upon, so it may safely retry a non-idempotent request the server already handled.
Both tests fail today: the emitted GOAWAY carries 0.