fix(lab): record that the Chat conformance destination accepts the developer role

[lidge-jun]

Summary

• The Lab conformance vector chat-core.protocol.request-mapping asserts that a developer message reaches the Chat wire as developer. fix(openai-chat): fold the developer role unless a destination records that it accepts it #5334 made the wire role fold to system unless a destination records that it accepts it, and this fixture records nothing, so the assertion started failing with roles:value_mismatch on dev and on every branch cut from it.
• The fixture provider already states that it exercises native OpenAI Chat semantics "including role:developer", and api.openai.com does accept the role. The destination it stands for now records that, so the vector keeps testing what it was written to test.
• No fixture bytes or digests change; only the provider the harness builds. The declaration is scoped to the Chat adapter, which is the only one that reaches the role decision.

Verification

• The failure is reproduced by the exact assertion text in the hosted log: chat-core.protocol.request-mapping: protocol_failure deterministic_assertion roles:value_mismatch on shard 2/4 of run 35510777682.
• A repository-wide search for wire-role expectations found this as the only remaining one outside tests/; the other role: "developer" occurrences construct the internal representation that the adapter maps, and are unaffected.
• Local suites, typecheck and builds were not run in this lane; exact-head hosted CI on this pull request is the execution evidence.

Checklist

• Scope stays focused and avoids unrelated cleanup.
• Docs or release notes were updated when needed.
• Security-sensitive changes were reviewed for secrets, auth, and unsafe defaults.

[coderabbitai]

Warning

Review limit reached

Next included review available in 6 minutes.

Check out review usage here.

View limit details

Limit details: You’ve used all 10 included reviews currently available.

You've used all free OSS reviews for now. Wait for the free limit to reset to keep reviewing this public repository.

Learn how review limits work.

Review configuration:

⚙️ Run configuration

Configuration used: Repository: lidge-jun/opencodex/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: d2e2fcc3-125b-4213-8e6c-8a7ec220ac31

📥 Commits

Reviewing files that changed from the base of the PR and between d9cb0eb and 1552fee.

📒 Files selected for processing (1)

• src/lab/conformance/fixture-provider.ts

---

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

• X
• Mastodon
• Reddit
• LinkedIn

_{Comment @coderabbitai help to get the list of available commands.}

[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-09-20T12:51:12.192392Z	1552fee	PR opened

ℹ️ 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.

[github-actions]

⚠️ Deterministic hygiene checks failed.

• missing_regression_test — Behavior changed under src/ or gui/src/ without a test change. Add focused coverage or obtain test-exception-approved.

[github-actions]

⏳ DRAFT

• hygiene: missing_regression_test.

What to do

• Fix missing_regression_test — Behavior changed under src/ or gui/src/ without a test change. Add focused coverage or obtain test-exception-approved.

Automatic draft conversion failed (token cannot change draft status). Please convert this pull request to a draft manually. The required enforce-target check will keep failing until every issue above is resolved.