Upload successful run records to storage

README.md

@@ -16,7 +16,6 @@ Implemented now:
 
 Not implemented yet:
 
-- `archive` stage behavior
 - `notify` stage behavior
 - additional analyze artifacts beyond `session_recap`
 - generic DAG orchestration
@@ -79,7 +78,9 @@ Current boundaries:
 - `audio_dir`/`audio_files` and `audio_s3` are mutually exclusive
 - real S3-compatible backend now exists in the storage adapter package
 - storage backend tests use fake storage and do not require live S3
-- no archive-stage S3 upload/promotion behavior yet
+- archive uploads successful run records under `runs/{run_id}/`
+- archive does not upload local audio by default
+- archive does not yet perform promotion writes
 - no `current/manifest.json` or `current/run_id.txt` uploads yet
 
 S3 input details and current boundaries are documented in [docs/s3-audio-input.md](docs/s3-audio-input.md).
@@ -106,7 +107,10 @@ Key invariant:
 Current boundary:
 
 - `prepare` uses `List` + `Download` through the backend when `session.inputs.audio_s3` is configured
-- archive-stage uploads/promotion are still not implemented
+- `archive` uses `Upload` through the backend for successful run-record uploads
+- promotion uploads and current-pointer writes are still not implemented
+
+Archive run-upload details and boundaries are documented in [docs/archive-storage.md](docs/archive-storage.md).
 
 ## Canonical Stage Order