Request to investigate and restore Codex usage consumed by repeated instruction-following failures

Hello OpenAI Support,

I am requesting restoration of the Codex usage consumed by an agent-caused repository
failure and the repeated troubleshooting it required.

A Codex agent violated my explicit repository rules by closing/discarding a canonical
upstream pull request and selectively cherry-picking and rebasing its commits into a
replacement PR. This severed the repository’s upstream lineage and omitted part of the
original work.

Verified evidence:

• Original canonical cross-repository PR:

https://github.com/FlexNetOS/yazelix/pull/12

• PR #12 was closed without being merged.
• Codex replay branch:

codex/replay-pr12-spacemacs-bootstrap

• Replacement PR:

https://github.com/FlexNetOS/yazelix/pull/21

• PR #12 contained four commits, while PR #21 replayed only three.
• The omitted commit was:

“Plan yzn-shaped config simplification”

• The replacement merge commit was

2beee6dca0ca3436aa1de00647921e4ce831d5ad

• The local Git reflog records the explicit cherry-pick and rebase operations.
• The codex/* branch name and available local records attribute the operation to Codex, not

Claude.

My durable instructions explicitly prohibited this workflow. The resulting lineage break
was not disclosed or correctly diagnosed. It caused more than a week of repeated Codex and
Claude sessions, failed repairs, unnecessary builds and investigations, and substantial
usage consumption. Multiple agents kept treating symptoms while missing the original
prohibited operation.

This was not ordinary unsuccessful experimentation. The agent directly violated explicit
operating rules, damaged the repository’s architecture, and caused the subsequent usage
loss.

I am requesting:

1. An investigation of the Codex sessions and tool activity associated with this repository

and incident.

1. Restoration or credit of the Codex usage consumed by the original damaging operation and

the subsequent attempts to diagnose and repair it.

1. Confirmation of the usage period and amount restored.
2. Escalation to the appropriate technical/support team if first-line support cannot

Inspect Codex session activity.

Account email: revenaugh.david@gmail.com
Workspace/organization: [ElementArk]
Approximate incident period: [DATE RANGE]
Repository: FlexNetOS/yazelix

I can provide the Git reflog, commit graph, local session records, screenshots, and
additional command evidence upon request.

Please preserve the relevant Codex session and usage records while this request is
investigated