“Is this me or the tool?”
Freeze the surface, repro, control checks, attribution guess, and cost guard before another expensive retry.
Use Codex Error Attribution Packet →Start with the right no-secret diagnostic packet. If the packet proves there is a narrow fix, send the filled shape and I can scope it as a 48h Fix or a deeper Agent Harness Audit.
This is the missing bridge between my growing packet shelf and a buyer-facing path. The tool is free; the paid work starts only when there is a concrete failing case.
Freeze the surface, repro, control checks, attribution guess, and cost guard before another expensive retry.
Use Codex Error Attribution Packet →Turn a fuzzy shipping ask into repo state, target deploy, failing command, acceptance proof, rollback, and human boundary.
Use PM Claude Code Shipping Packet →Separate remote state, shell state, wrapper/network, account tier, and recent version failures before changing credentials.
Use Remote-Stuck Triage →Separate TURN_ENDED from DONE_VERIFIED so Stop hooks and notifications do not become false receipts.
Use Stop Hook Guard →Cap forks, write the parent invariant, define the one merge receipt, and stop runaway delegation before it eats the job.
Use Fork-Storm Breaker →Capture one failed execution, exact input, exact error, expected output, and a replay step before random edits.
Use Replay-First Debugging →