feedback codex git fabricated doc urls 20260715T125214

When a Codex CLI session explained why it couldn't write to ~/creatortrack/.git, it cited several learn.chatgpt.com/docs/... URLs as authoritative sources for a claimed 'git is a protected path' rule. Checking disk (ls -la ~/creatortrack/.git) showed .git was a normal group-writable directory inside the workspace root, i.e. writable under Codex's own workspace-write model. The real constraint was that Forge's dev-slot worktrees live outside the repo root (~/creatortrack-wt/, ~/forge-suite-wt/), not a .git protection rule. Codex's doc citations for this claim were fabricated.

Why: Trusting an agent's self-reported permission model without checking disk state leads to wrong architectural conclusions (e.g. believing git operations are blocked when they aren't).

How to apply: When Codex (or any agent) cites a specific documented restriction to explain a failure, verify against actual filesystem/permission state (ls -la, stat) rather than accepting the citation. This is consistent with [[reference_gpt_sol_in_claude_code]] work but is a new, distinct gotcha about Codex's tendency to fabricate citations under sandbox constraints.

[auto-memory session 577603bc-d3a9-4b19-bb8e-6db80243b054, confidence 0.70, mode staged]