Skip to content

[Docs] Require provider functionality parity - #1186

Merged
mrubens merged 1 commit into
developfrom
feature/provider-parity-guidance-179nb3k6qgzc8
Aug 9, 2026
Merged

[Docs] Require provider functionality parity#1186
mrubens merged 1 commit into
developfrom
feature/provider-parity-guidance-179nb3k6qgzc8

Conversation

@roomote-roomote

Copy link
Copy Markdown
Contributor

Opened on behalf of Matt Rubens. Follow up by mentioning @roomote-roomote, in the web UI, or in Slack.

What changed

Added repository-wide agent guidance to keep equivalent functionality synchronized across supported source-control, communication, and sandbox providers unless a user explicitly requests a provider-specific exception.

Why this change was made

Provider-backed changes should default to consistent behavior instead of accidentally shipping for only one integration or runtime.

Impact

This is a documentation-only change with no direct user-facing runtime impact. Future agent changes will explicitly account for provider parity by default.

@roomote-community

roomote-community Bot commented Aug 9, 2026

Copy link
Copy Markdown
Contributor

No code issues found. See task

Reviewed 69bfb4a

@mrubens
mrubens marked this pull request as ready for review August 9, 2026 16:20
@mrubens
mrubens merged commit d1297ca into develop Aug 9, 2026
7 of 8 checks passed
@mrubens
mrubens deleted the feature/provider-parity-guidance-179nb3k6qgzc8 branch August 9, 2026 16:21
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant