Repository navigation
docs(structure): scope canonical Fast injection to the bridged Chat path - #2049
Conversation
structure/04's native Chat passthrough paragraph claimed canonical Fast follows the resolved Fast policy without chatServiceTier. The code does not do that: chat-native.ts has no tier wiring at all — tier resolution lives only in the Responses pipeline feeding adapter buildRequest, which the passthrough bypasses. On the native path every caller service_tier is forwarded raw and only under chatServiceTier: true, and fastMode injects nothing (openai-chat.ts:121, chat-native.ts:54-72). Campaign wp9 docs-drift fix; provenance and code-verification record in devlog/_plan/260818_bug_pr_resolution/040.
|
✅ Deterministic PR hygiene checks passed. |
|
No actionable comments were generated in the recent review. 🎉 ℹ️ Recent review info⚙️ Run configurationConfiguration used: Path: .coderabbit.yaml Review profile: ASSERTIVE Plan: Pro Plus Run ID: 📒 Files selected for processing (1)
Included review availability: Your plan includes up to 10 reviews per rolling hour; 9 remain after this review. 📝 WalkthroughWalkthroughThe transport documentation updates native Chat passthrough behavior. Caller-supplied ChangesChat service tier policy
Estimated code review effort: 1 (Trivial) | ~3 minutes Merge Risk: ⚪ Minimal · up to This documentation-only change corrects the description of Fast injection behavior without changing runtime code; no actionable merge-blocking risk remains. Suggested reviewers: 🚥 Pre-merge checks | ✅ 5✅ Passed checks (5 passed)
✨ Finishing Touches🧪 Generate unit tests (beta)
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. Comment |
…4-drift docs(structure): scope canonical Fast injection to the bridged Chat path
Summary
Campaign wp9 docs-drift fix (the release-readiness follow-up item). structure/04's native Chat passthrough paragraph claimed canonical Fast follows the resolved Fast policy without chatServiceTier. The code does not do that on the native path: chat-native.ts has no tier wiring — tier resolution lives only in the Responses pipeline feeding adapter buildRequest, which the passthrough bypasses. On the native path every caller service_tier is forwarded raw and only under chatServiceTier: true, and fastMode injects nothing (openai-chat.ts:121, chat-native.ts:54-72; adversarial verification recorded in devlog/_plan/260818_bug_pr_resolution/040).
Docs-only: one paragraph in structure/04_transports-and-sidecars.md.
Verification
Checklist
Summary by CodeRabbit