Add E2E test for session.providerEndpoint.get

[SteveSandersonMS]

Adds a Node E2E test for the new session.providerEndpoint.get shared API (not yet shipped).

The new RPC returns the provider endpoint + credentials for a session — the BYOK config if one is set, otherwise the resolved CAPI endpoint — so SDK consumers can call the LLM backend directly with their own OpenAI/Anthropic client.

Changes

• Regenerated nodejs/src/generated/rpc.ts and session-events.ts against the runtime schema that adds providerEndpoint.
• New nodejs/test/e2e/provider_endpoint.e2e.test.ts covering:
  • BYOK: returns protocol, baseUrl, apiKey, headers from the configured provider.
  • CAPI: returns the resolved CAPI base URL (using the harness CapiProxy so no real network calls).

Validating

Built the runtime branch locally and pointed the harness at it:

COPILOT_CLI_PATH=<runtime>\dist-cli\index.js npm run test:e2e -- provider_endpoint

Both tests pass.

Draft because this depends on the runtime PR landing + a release that includes the new schema before it can run in CI.

[github-actions]

Cross-SDK Consistency Review

Summary: This draft PR regenerates Node.js types from an updated runtime schema and adds E2E tests for the new session.provider.getEndpoint RPC. Since it's draft and depends on a not-yet-shipped runtime release, the incomplete multi-SDK coverage is expected — but flagging the gaps here so nothing is missed before merge.

---

🔴 New provider RPC namespace — missing from all other SDKs

The regenerated nodejs/src/generated/rpc.ts adds a new provider namespace to the session RPC object (around line 14022):

session.rpc.provider.getEndpoint(params?)  // → "session.provider.getEndpoint"

The equivalent needs to be added (via generated-type regeneration) to all five other SDK implementations before this can be considered fully consistent:

SDK	Location	What needs to be added
Python	python/copilot/generated/rpc.py	session.rpc.provider.get_endpoint()
Go	go/rpc/zrpc.go	session.RPC.Provider.GetEndpoint() (new ProviderAPI field in SessionRPC)
.NET	dotnet/src/Generated/Rpc.cs	session.Rpc.Provider.GetEndpointAsync() (new ProviderApi property in SessionRpc)
Java	java/src/generated/java/	session.rpc().provider().getEndpoint()
Rust	rust/src/generated/rpc.rs	session.rpc.provider.get_endpoint()

🟡 New/renamed generated types — not yet in other SDKs

The schema regeneration brings several other type additions/renames that are currently Node.js-only:

New types:

• ProviderEndpoint, ProviderEndpointType, ProviderEndpointWireApi, ProviderSessionToken, ProviderGetEndpointRequest
• AgentsDiscoverRequest, InstructionsDiscoverRequest
• MemoryConfiguration
• ServerAgentList, ServerInstructionSourceList
• AssistantMessageServerTools

Renames (breaking for any consumers relying on the old names):

• InstructionsSources → InstructionSource
• InstructionsSourcesType → InstructionSourceType
• InstructionsSourcesLocation → InstructionSourceLocation

Modified shapes:

• ScheduleEntry.intervalMs is now optional; cron, tz, and at fields added (one-shot and calendar schedules)
• SlashCommandInfo gains schedulable?: boolean
• InstructionSource gains projectPath?: string
• ResumeData / ShutdownData gain eventsFileSizeBytes?: number
• HookProgressData gains temporary?: boolean

All of these will need to be propagated to Python, Go, .NET, Java, and Rust generated files (via the normal codegen regeneration step for each SDK) before the schema is fully in sync.

---

Minor nit: PR title vs RPC method name

The PR title and description reference session.providerEndpoint.get, but the actual wire name and TypeScript accessor path are session.provider.getEndpoint. Worth aligning the PR description to avoid confusion.

---

As a draft PR this is all expected — just flagging as a pre-merge checklist so nothing slips through when the runtime ships and this gets un-drafted.

Generated by SDK Consistency Review Agent for issue #1621 · sonnet46 3.1M · ◷