Retire a Temporary Codex Instruction Override
A temporary instruction can outlive the problem it was meant to solve. Later, Codex appears to ignore the team's normal convention for no obvious reason.
When you introduce an instruction override, record why it exists and what event will remove it. In a practice repository, confirm the active guidance before and after removing that override. Codex's documented discovery rules make override files significant, so their lifecycle belongs in your cleanup plan.
Do not delete a file merely because its name looks temporary. Read its contents and history first. The aim is to restore the intended behavior with evidence, not to erase a local workaround someone still needs. A small follow-up check is cheaper than debugging contradictory instructions several weeks later.
