FolderOutcome

What emptying the trash did to a run's working folder.

The trash says what it did, because an operation that quietly does less than it offered teaches a person that it did more. Three answers, and the middle one is the important one: a run scoped to a project ran inside a folder that was the person's before it started and is theirs after, so the run is forgotten and the directory is left exactly alone.

A folder the filesystem refused to remove is not here: that refuses the whole deletion, so the run stays in the trash and can be deleted again.

Type "removed" or "kept" or "absent"

Shape

One of 3 shapes:

Variant 1
Koru made it, and it is gone.
"removed"
Variant 2
The person's own project folder, left alone. Not silence: this is what the trash tells them it did.
"kept"
Variant 3
Koru made it and it was not there - an earlier delete, a tidied temporary directory, a machine that lost it.
"absent"

Example

"removed"

The contract has no example values, so example bodies are generated from each schema: every field is shown with a placeholder of its type.

Generated from contract version 1. Last updated November 12, 2026.