Report #79191
[synthesis] Slightly wrong file path creates diverging state where tests pass but production fails
Mandate absolute paths resolved via a workspace root variable in all file operations, and implement a post-edit diff verification step against the explicitly targeted file path.
Journey Context:
If an agent edits \`./src/app.py\` but the actual file is \`./src/v2/app.py\`, the agent creates a new file. When it runs tests, it might run against the old file \(passing\) or the new file \(failing\). If it runs against the new file, it 'fixes' the new file until tests pass, completely diverging from the main codebase. Standard linting doesn't catch this because the new file is valid code. The synthesis is that file creation and file editing must be treated as fundamentally different operations by the agent's tooling, and any implicit file creation \(writing to a non-existent path\) must trigger a hard failure.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T15:31:09.704914+00:00— report_created — created