fix(cli): include cache writes in app-server freshness

[luvs01]

Motivation

• A cache-only write to models_cache.json could leave a running Codex app-server with an in-memory model list that is newer than the on-disk catalog, but the advisory logic previously compared only the catalog mtime and missed those cases.

Description

• Include models_cache.json mtime in the post-write freshness boundary by importing activeCodexModelsCachePath and adding a modelsCacheMtimeMs seam to CodexAppServerProcessIo so tests can inject a cache clock.
• Compute writeMtimeMs as the newest of the catalog mtime and models-cache mtime and use it for the stale-vs-fresh comparison in afterCatalogWriteHandleAppServers.
• Add a production helper defaultModelsCacheMtimeMs() that reads the active cache file mtime when an injected seam is not provided.
• Update the unit test tests/codex-integration/codex-app-server-processes.test.ts to cover the cache-only timing window and update structure/runtime.md to document that advisory guidance compares against the newest catalog or models-cache mtime.

Testing

• Ran bun test tests/codex-integration/codex-app-server-processes.test.ts with Bun v1.4.0 and the focused suite passed (59 passed, 1 skip).
• Ran bun run typecheck and bun run structure:check, both succeeded.
• Ran bun test tests/ci-workflows/file-size-ratchet.test.ts and bun test tests/ci-workflows/repo-hygiene.test.ts, both succeeded.
• Attempted broader bun run test for full suite; unrelated shared-state failures surfaced outside the changed subsystem while the focused tests for this change passed. The test:changed wrapper could not run due to no resolvable comparison ref in the checkout environment.

---

Codex Task

---

[coderabbitai]

Important

• 🔍 Trigger review

This repository does not receive automatic reviews because it has fewer than 10 stars.

⚙️ Run configuration

Configuration used: Repository: luvs01/opencodex/.coderabbit.yaml

Review profile: ASSERTIVE

Plan: Advanced

Run ID: 8ce692dd-3cc1-4467-86e7-1bedda1ebe2a

---

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-22T11:51:42.575415Z	6457ad9	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 PR hygiene checks passed.

[devin-ai-integration]

Devin Review found 2 potential issues.

[devin-ai-integration]

🔍 Public stale-state documentation remains catalog-only

The public sub-agent guide defines freshness only against the catalog. If cache writes belong to the global contract, update that page and its translations.

---

Was this helpful? React with 👍 or 👎 to provide feedback.

[luvs01]

Closing: current dev already scopes the freshness warning to writes — src/codex/app-server-processes.ts attaches the restart hint only after catalogWritten || cacheSynced and tracks CodexAppServerCatalogState, which is the cache-write inclusion this PR made.