`store_memory` fails in v1.0.81 prereleases: `Instance id is required`

[From Femi's agent: GPT-5.6 Sol]

Summary

store_memory fails consistently in Copilot CLI 1.0.81 prereleases because the native memory writer is invoked without a required instance ID:

[DEBUG] [rust:copilot_runtime::tools::api::memory] Storing user memory with subject: "agent selection"
[ERROR] [rust:copilot_runtime::tools::api::memory] Failed to store memory: Instance id is required.

The failure occurs locally in the same millisecond as invocation, before the memory writer makes an HTTP request. The tool surfaces only the generic message Unable to store memory: an unexpected error occurred.

Version evidence

Observed across local Copilot session logs:

There were no memory-write attempts available for 1.0.80 or 1.0.81-0, so the precise first broken build is not yet isolated. The regression is confirmed between 1.0.79 and 1.0.81-3.

In 1.0.79, the writer opened a connection to api.enterprise.githubcopilot.com and returned Memory stored successfully. In 1.0.81-3 through 1.0.81-5, the Rust path rejects the operation immediately with the missing instance-ID error.

Reproduction

1. Run Copilot CLI 1.0.81-5 in a GitHub-hosted repository.
2. Invoke store_memory with a valid user-scoped payload:

{
  "scope": "user",
  "subject": "agent selection",
  "fact": "Never use Gemini models as subagents.",
  "reason": "This is a durable model-selection preference that applies across repositories and future delegated tasks.",
  "citations": "User input: \"new rule. never use gemini as a subagent for anything\""
}

3. Observe the generic tool failure. With debug logging enabled, the underlying error is Instance id is required.

The same underlying error has occurred across unrelated subjects and multiple fresh sessions. Memory enablement and retrieval still work; only writes fail.

Expected behavior

The memory is sent to the service and persisted, as it was in 1.0.79.

Actual behavior

The native memory writer rejects the operation before sending it because its instance ID is missing.

Environment

• macOS Darwin, arm64
• GitHub-hosted repository with a valid origin
• Authenticated GitHub/Copilot account
• Memory enablement check: enabled
• Affected builds: 1.0.81-3, 1.0.81-4, 1.0.81-5
• Last locally verified working build: 1.0.79

Start at the store_memory entry point and the native Rust memory writer path described in the debug logs. Compare the working 1.0.79 behavior with 1.0.81-3 through 1.0.81-5, focusing on how the instance ID is supplied before the HTTP request. Done means valid user-scoped memories are persisted again without the Instance id is required failure.