workflows: add missing translation directions - #10
Merged
Conversation
idy
marked this pull request as ready for review
July 24, 2026 09:18
Member
Author
There was a problem hiding this comment.
🤖 OpenAI PR review
Reviewed commit: 09dfb8c813
Reviewed range: be5b2eca68..09dfb8c813
Review mode: full
Session key: repo-1308402561-pr-10-v2
Generation key: 2f0dc369e655c2d55d825c34308d31766559c5c208c83c7eab602058215ef37d
Diff chunks: 1
Model: gpt-5.6-terra
Reasoning effort: medium
Review time: 8s
Input tokens: 43,400
Cached input tokens: 31,645
Cache write tokens: 11,743
Cache hit ratio: 72.9%
Output tokens: 560
Reasoning tokens: 180
Total tokens: 43,960
Estimated Codex credits: 1.142
Credit rate per 1M tokens: 62.5 input / 6.25 cached / 375 output
Per-chunk and aggregation usage
| Turn key | Time | Input | Cached | Cache hit | Cache write | Output | Reasoning | Total | Est. credits |
|---|---|---|---|---|---|---|---|---|---|
chunk:1/1:633e34853aac0dbbd4c8874fe914e7debf86237ed15e431abb75a7a4fdccb6d9 |
5s | 20,374 | 9,423 | 46.3% | 10,945 | 375 | 170 | 20,749 | 0.884 |
aggregate:2f0dc369e655c2d55d825c34308d31766559c5c208c83c7eab602058215ef37d |
3s | 23,026 | 22,222 | 96.5% | 798 | 185 | 10 | 23,211 | 0.259 |
No actionable findings.
No actionable findings.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
What changed
Why
H106 needs seven translation directions. Four already existed in Raids and had been exercised by existing deployments; keeping the remaining generic directions in Raids avoids duplicating AST workflow definitions in each product deployment. Product RuntimeProfiles remain responsible for resolving translator to the product-specific voice.
Validation