When new files are being created, GH Copilot CLI often tries to read them first and outputs failed Read operations

### Describe the bug

For many prompts that result in new files being created, the harness first tries to read the still nonexistent files (probably as a safety measure); but instead of that being a hidden/silent operation, the terminal output shows "Read" errors, which makes it seem like the CLI has bugs even though it's expected behavior.

### Affected version

GitHub Copilot CLI 1.0.28

### Steps to reproduce the behavior

1. Run prompts/flows that create new files ('/openspec-propose' is the one I used this time)
2. See the "Read" errors in the terminal output.

### Expected behavior

No "Read" error should appear.

### Additional context

Beginne damit, das Problem mit dem im Bericht beschriebenen /openspec-propose-Flow zu reproduzieren, und beobachte, wann der Harness die fehlgeschlagenen Read-Operationen ausgibt. Verfolge die CLI-Ausgabe für die Erstellung neuer Dateien und überprüfe, dass erwartete Reads nicht vorhandener Dateien stumm bleiben, während echte Read-Fehler weiterhin sichtbar sind.

Vom Indexierungsmodell aus dem Issue-Text verfasst.