test(responses): declare the inline-document destination accepts the developer role

[lidge-jun]

Summary

• dev is red on shard 3/4: tests/responses/chat-inline-document-bytes.test.ts asserts that a document survives on a developer turn and reads the wire role to prove it. fix(openai-chat): fold the developer role unless a destination records that it accepts it #5334 folds that role to system unless a destination records acceptance, and this suite records nothing, so the case fails at ab90bea6b1.
• The destination now records that it accepts the role. What the case is about — an inline document surviving to the wire — is unchanged, and no assertion is weakened.
• This is the third and last file in the class, after the Lab conformance vector (fix(lab): record that the Chat conformance destination accepts the developer role #5341) and the dangling tool-call suite (test(openai-chat): declare the dangling-toolcalls destination accepts the developer role #5344). It was missed by the earlier sweep because the assertion is written as a whole-message toEqual on a suite whose subject is documents rather than roles.

Verification

• Reported from a lane's exact-head run against dev ab90bea6b1: expected role "developer", received "system" at line 181.
• The suite's other provider is Anthropic, which does not reach the Chat role decision and is untouched.
• 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.

[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-20T13:29:06.568984Z	86be497	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.

[coderabbitai]

Note

Currently processing new changes in this PR. This may take a few minutes, please wait...

⚙️ Run configuration

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

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 75870fbe-4ed7-48df-9477-f83e9094f6c9

📥 Commits

Reviewing files that changed from the base of the PR and between ab90bea and 86be497.

📒 Files selected for processing (1)

• tests/responses/chat-inline-document-bytes.test.ts

 _______________________________________________________________
< Making your code shine like the top of the Chrysler Building. >
 ---------------------------------------------------------------
  \
   \   \
        \ /\
        ( )
      .( o ).

✨ Finishing Touches

📝 Generate docstrings

• Commit to this branch
• Create a new PR

🧪 Generate unit tests (beta)

• Commit to this branch
• Create a new PR

---

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.}

[github-actions]

✅ Deterministic PR hygiene checks passed.