Luna Reserve can inspect/test a repo but repository writes fail when weekly usage is exhausted

Summary

When regular Codex weekly usage is exhausted, Luna Reserve is available at 100% and can still inspect the repository, diagnose bugs, and run the existing test suite, but repository write operations are blocked by the regular usage gate.

This leaves Luna Reserve in a partially functional/read-only state for an agentic coding workflow.

Observed quota state

• 5-hour remaining: 100%
• Weekly remaining: 0%
• Luna Reserve remaining: 100%
• Luna Reserve UI is available and can be selected/used

Reproduction

1. Reach 0% remaining on the regular weekly Codex allowance while the 5-hour allowance still shows 100% remaining.
2. Continue the existing coding/debugging conversation using Luna Reserve.
3. Ask Luna/Codex to inspect the repository and continue debugging.
4. Repository reads/analysis work normally.
5. Existing tests can be executed; in my case Luna completed a full regression run successfully (239 passed, 0 failed, 0 skipped).
6. Luna identified additional concrete code fixes that needed to be applied.
7. When Codex attempted to write the remaining fixes to the repository, the write path was rejected with:

Automatic approval review failed: usage limit exhausted

Expected behavior

If Luna Reserve is intended to let a conversation continue after regular usage is exhausted, repository write/edit operations required by the same Codex coding task should continue to work using the Luna Reserve allowance.

At minimum, the write/approval execution path should use the same Reserve entitlement as the Luna inference path rather than continuing to enforce the exhausted weekly regular-usage bucket.

Actual behavior

The Luna model remains usable for repository inspection, debugging, analysis, and test execution, but the repository write/approval path is blocked by the exhausted regular weekly allowance.

Operationally this becomes:

regular weekly allowance: 0%
5-hour allowance: 100%
Luna Reserve: 100%
        ↓
Luna can inspect/analyze/test
        ↓
repository write
        ↓
"Automatic approval review failed: usage limit exhausted"

Why this looks like an entitlement/gating mismatch

Luna Reserve is clearly active enough to execute substantial work in the same Codex session. The failure occurs specifically when the remaining debugging task requires repository writes, and the error reports the normal usage limit rather than a depleted Luna Reserve.

This suggests that the inference/read/test path recognizes the Reserve entitlement while the automatic-approval/repository-write execution path still checks the exhausted regular weekly allowance.

Additional quota UI observation

The quota display simultaneously showed:

5-hour remaining: 100%
weekly remaining: 0%
overall remaining: 0%
Luna Reserve remaining: 100%

The 5-hour figure itself may be valid as a separate bucket, but it makes the gating problem particularly visible: two displayed allowances are at 100% (5-hour and Luna Reserve), yet the Codex repository-write workflow is blocked because the weekly regular allowance is at 0%.

Impact

This prevents Luna Reserve from actually taking over a long-running debugging task when regular usage is exhausted. It can diagnose the next fix but cannot complete the standard Codex loop:

inspect -> edit -> test -> inspect -> edit -> benchmark

Instead it is effectively reduced to a read/test/analysis fallback until the regular weekly allowance resets.

Request

Please verify whether repository writes and automatic approval review are expected to honor Luna Reserve after regular usage is exhausted. If so, the write/approval usage gate appears not to be receiving the Luna Reserve entitlement.

Start by tracing the automatic approval review path that reports "usage limit exhausted" and compare its entitlement checks with the Luna Reserve path used for repository inspection and tests. Reproduce the weekly-limit and Reserve-available state, then verify that repository writes complete under Reserve and add coverage for the gating mismatch.