[Spector] Add 200 body / 204 no-content success response scenario

[Copilot]

Adds HTTP Spector coverage for an operation with multiple success responses where one variant carries a body and the other does not. This lets emitters verify they distinguish a 204 empty-success variant from a nullable body on a single response.

Scenario

New namespace Response.BodyOrNoContent under response/body-or-no-content. Both operations return the same union so the generated shape matches the issue exactly; a mock endpoint is deterministic, so each declared outcome gets its own route:

alias LayoutResponse = {
  @statusCode statusCode: 200;
  @body layout: BlobLayout;
} | {
  @statusCode statusCode: 204;
};

@route("/body") @get op getBody(): LayoutResponse;         // mock → 200 { "content": "hello" }
@route("/no-content") @get op getNoContent(): LayoutResponse; // mock → 204, no body

Changes

• specs/response/body-or-no-content/main.tsp — scenario definitions with docs calling out the validation goals (both classified successful, 200 deserialized normally, 204 skips body deserialization, raw status/headers available).
• specs/response/body-or-no-content/mockapi.ts — passOnSuccess mocks for the 200-with-body and 204-no-content routes.
• spec-summary.md — regenerated.
• .chronus/changes/ — feature entry for @typespec/http-specs.

• Fixes [Spector] Add 200 body / 204 no-content success response scenario #11650

[azure-pipelines]

Azure Pipelines:
Successfully started running 1 pipeline(s).
1 pipeline(s) were filtered out due to trigger conditions.
There may be pipelines that require an authorized user to comment /azp run to run.

[azure-sdk-automation]

You can try these changes here

🛝 Playground	🌐 Website	🛝 VSCode Extension

[pkg-pr-new]

Open in StackBlitz

npm i https://pkg.pr.new/@typespec/http-specs@11677

commit: a305245