[Desktop 26.721.4979.0] Viewing a deleted automation renders an untitled scheduled-task card instead of not found

Environment

• Codex Desktop: 26.721.4979.0
• Windows 11 25H2, build 26200.8037

Summary

Calling the automation view operation for an id that has already been deleted renders a new-looking untitled scheduled-task card in the conversation instead of returning a structured not-found result.

Reproduction

1. Create an automation and record its id.
2. Delete it and verify that it is absent from the automation store.
3. Call the automation operation with:

{"mode":"view","id":"<deleted-automation-id>"}

1. The tool reports:

Rendered automation card in the app.

1. The UI inserts a card labelled:

Запланированная задача без названия

1. Re-read the automation store.

Expected behavior

The view call should return a structured not_found / deleted result and should not render an automation card.

Actual behavior

A generic untitled scheduled-task card is rendered even though no automation with that id exists.

Fresh post-call readback confirmed:

• the deleted id remained absent;
• the automation store contained no unnamed automation;
• no new automation was created or persisted by the view call.

Impact

The card makes the user reasonably believe that Codex created an unknown scheduled task. It also makes UI state disagree with the automation store and complicates cleanup/audit decisions.

Suggested fix

• Validate id existence before rendering.
• Return a structured not_found result for deleted or unknown ids.
• Distinguish deleted/missing automation references from real automation cards.
• Add a regression test proving that view cannot create or render a phantom card.

No automation prompt, task contents, usernames, local paths, credentials, or private logs are included.