🤖 tests: seed workspace models as unsent picks and workspace metadata

[ibetitsmike]

Summary

Tests that seed a workspace model also seed it where the resolver reads it after #5901: an unsent pick (markAiSelectionIntent) or workspace metadata (setWorkspaceAiMetadata). The model:{workspace} key seed stays next to it until the switch, which deletes it, so each setup holds before and after the model moves to the resolver. Production code does not change.

Stack

Milestone M4 of the server-side settings stack, on top of M3 (#5869 to #5879): per-workspace AI picks (model, thinking level, reasoning mode, agent and Auto routing) are stored in workspace metadata in config.json instead of per-browser localStorage keys, so every browser shows the same picks. An unsent picker change stays in memory in its tab until a send saves it, and a reload before sending drops it, as the plan accepts. Layer 7 of 20.

Testing

• The ThinkingContext, TasksSection, ProposePlanToolCall, command source, send option and model change tests add the pick or metadata seed beside the key seed, and reset the pick store between tests.
• "preserves explicit gateway-scoped saved workspace models" (sendOptions.test.ts, renamed from "... stored model preferences"): an explicit gateway model saved in metadata keeps its gateway identity in the send options.
• The rewritten seeds pass on the code before the switch in 🤖 refactor: resolve the workspace model from metadata and an unsent pick #5901 and after it, and the old key forms fail after the switch (verified for ProposePlanToolCall).
• make static-check and the touched test suites pass at the top of the stack; CI checks each layer on its own.

Review record

• Remote UAT through Coder Agents: Round 1: FAIL on efe7e29096, because a fork without a message dropped the source's unsent picks (fixed by 🤖 feat: fork a workspace with the source composer's unsent AI picks #5897, 🤖 refactor: resolve the workspace agent from metadata and an unsent pick #5908 and 🤖 refactor: resolve auto routing from the unsent pick, saved flags and agent defaults #5909); everything else passed. Round 2: PASS on 80f2b5379e: forks from all five entry points keep the unsent picks, startup removes the retired keys, and the round 1 checks still pass; the plan handoff was not exercised because the mock model cannot propose a plan. The Codex round 1 fixes made since then have no remote UAT yet; that is left to the next UAT round on 🤖 refactor: keep preferences and workspace AI picks on the server #5916.
• Codex round 1: thumbs-up on cb4039391d, no findings. Mike asked to land the stack as one PR, so further review runs on 🤖 refactor: keep preferences and workspace AI picks on the server #5916.
• M4 test audit: no gap found in this layer (audit at efe7e29096, probe edits in production code).

[chatgpt-codex-connector]

Codex Review Summary

This comment shows the latest Codex review activity on this pull request.

Review	Status	Commit	Review trigger
📝 Code Review	✅ Completed 2026-10-09T00:26:03.347374Z	e392190	New commits
🔒 Security Review	✅ Completed 2026-10-09T00:26:09.320367Z	e392190	New commits

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review" or "@codex security review".

Codex reacts with 👀 while any review is running, comments if it has suggestions, and reacts with 👍 once all reviews finish with no findings.

[ibetitsmike]

Landed in #5916 (7b9899d), which collapsed this stack into one squash merge.