fix: preserve region and profile from YAML model config

[MaxwellCalkin]

Summary

• Add region and profile to the Zod baseModelFields in the config-yaml model schema so they survive YAML parsing instead of being stripped as unknown keys

Problem

The SageMaker docs show region at the model level:

models:
  - name: deepseek-6.7b-instruct
    provider: sagemaker
    model: lmi-model-deepseek-coder-xxxxxxx
    region: eu-central-1

But the Zod schema for ModelConfig didn't include region or profile in baseModelFields, so z.object().parse() silently stripped them. The only way to set these fields was through the nested env object, which the SageMaker docs don't mention.

This caused SageMaker to always default to us-west-2 and Bedrock to us-east-1, regardless of the user's configured region.

Fix

Add region: z.string().optional() and profile: z.string().optional() to baseModelFields. These fields are already in LLMOptions and are spread via ...rest in modelConfigToBaseLLM(), so no other code changes are needed.

The env nested object path continues to work and takes precedence when both are set (the env handler runs after the initial spread), maintaining backward compatibility.

Fixes #10879

Disclosure

This PR was authored by Claude Opus 4.6 (an AI), operating transparently. See https://github.com/anthropics/claude-code for details.

---

Summary by cubic

Preserves region and profile from YAML model configs so SageMaker and Bedrock use the user’s region instead of defaulting to us-west-2/us-east-1. Adds these fields to the baseModelFields Zod schema in packages/config-yaml.

• Bug Fixes
  • Added region and profile as optional fields to baseModelFields so they aren’t stripped during parse.
  • Top-level region/profile are now respected; env still works and takes precedence when both are set.

^{Written for commit 9f70054. Summary will update on new commits.}

[chatgpt-codex-connector]

You have reached your Codex usage limits for code reviews. You can see your limits in the Codex usage dashboard.
To continue using code reviews, you can upgrade your account or add credits to your account and enable them for code reviews in your settings.

[github-actions]

All contributors have signed the CLA ✍️ ✅
_{Posted by the CLA Assistant Lite bot.}

[cubic-dev-ai]

No issues found across 1 file

[MaxwellCalkin]

I have read the CLA Document and I hereby sign the CLA

[RomneyDa]

@MaxwellCalkin I think these values are supposed to be under env in YAML config. Could you check?