Handle Codex cache metadata on 304/fallback

[riatzukiza]

Summary

• refresh Codex instructions cache metadata when using 304 responses or cached/bundled fallbacks to honor TTL
• add guard rails around cache writes and align tests with new metadata refresh behavior
• document review follow-up steps in spec/pr57-review.md

Testing

• npm test -- test/prompts-codex.test.ts

[coderabbitai]

Warning

Rate limit exceeded

@riatzukiza has exceeded the limit for the number of commits or files that can be reviewed per hour. Please wait 17 minutes and 15 seconds before requesting another review.

⌛ How to resolve this issue?

After the wait time has elapsed, a review can be triggered using the @coderabbitai review command as a PR comment. Alternatively, push new commits to this PR.

We recommend that you space out your commits to avoid hitting the rate limit.

🚦 How do rate limits work?

CodeRabbit enforces hourly rate limits for each developer per organization.

Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout.

Please see our FAQ for further information.

📥 Commits

Reviewing files that changed from the base of the PR and between 284ad45 and 67b687f.

⛔ Files ignored due to path filters (1)

• spec/pr57-review.md is excluded by none and included by none

📒 Files selected for processing (2)

• lib/prompts/codex.ts (5 hunks)
• test/prompts-codex.test.ts (5 hunks)

✨ Finishing touches

• 📝 Generate docstrings

🧪 Generate unit tests (beta)

• Create PR with unit tests
• Post copyable unit tests in a comment
• Commit unit tests in branch pr57-comments

---

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