Artifact publication, retry, and confirmation

The service locates or creates the chat file volume, checks volume.write, reads the file, and reauthorizes at the storage boundary. It publishes task artifacts only after saving files and associating the volume. Artifact-step failure retains files. While the original task remains working and identity valid, identical filenames/bytes produce the same identifier and allow missing events to be published. Content, name, or task changes produce different artifacts.

After a task becomes terminal, an existing identical artifact does not establish that publication remains permitted.

Within an active turn, a readable artifact projection is persisted first, while its event may wait for the next turn transaction. Other branches directly append committed events. HTTP success does not mean the whole task ended or the client downloaded the file. file_id reads files; artifact_id reads artifact projections. Confirm both through actual task results.

Locating chat files may create necessary directories/databases/user volumes before reading the upload body. Bad requests after authorization may still leave this initialization state.

Last updated on