refactor: remove resource binding contract - #7
Conversation
![chatgpt-codex-connector[bot]](https://avatars.githubusercontent.com/in/1144995?s=60&v=4){kind=small}
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 9ab58edbc0
ℹ️ 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".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
| policy: Policy | ||
| context: ContextConfig | ||
| resources: Optional[ResourceConfig] = None | ||
| llm: LLMConfig |
There was a problem hiding this comment.
When an older control-plane replica or a rollback still returns a version-2 bootstrap containing the formerly valid resources field—even resources: null—ExecutionSnapshot.model_validate() now rejects it because the model still declares contract_version: Literal[2] but has extra="forbid"; OrchestratorClient.bootstrap() then propagates the validation error and the worker terminates the run as BOOTSTRAP_FAILED. Preserve a deprecated ignored field until every producer is upgraded, or introduce a new contract version with explicit rollout ordering rather than making the existing version incompatible.
AGENTS.md reference: AGENTS.md:L42-L42
Useful? React with 👍 / 👎.
1 participant
Removes the retired resource-binding contract in favor of agent target access settings.\n\nValidation:\n- task validate (227 tests and 29 keyless evaluations)\n\nPart of the coordinated release-readiness update.