Bugfix for commands that list artifacts in the S3 backend

This commit is contained in:
2026-05-21 21:00:51 -05:00
parent 3752f3ed28
commit ca1ded1821
4 changed files with 166 additions and 6 deletions

View File

@@ -253,7 +253,7 @@ Dry-run does not write restore report files.
- `status` with no config/session flags still requires explicit `--manifest`.
- `status --session-id <id>` uses normal config/session loading, including remote session fallback.
- `status --session-id <id>` includes the same source-based remote output availability view as `artifacts list --remote` when storage is configured.
- `status --session-id <id>` includes the same remote output availability view as `artifacts list --remote` when storage is configured: catalog sections use canonical source paths, and promoted outputs use configured archive destinations.
- local and S3 audio input modes are mutually exclusive.
- archive publish requires upstream stages through `analyze` to be `succeeded`.
- required promotion rules can fail when selected analyze artifacts did not generate a required file path.