kevinveenbirkenbachandClaude Opus 5 363a4be068 feat(ci): index the rescue tree at every collection site ...

The rescue artifact is a tarball of whatever the collectors managed to grab, so
reading a failed run meant downloading it to find out which files exist at all.
Run rescue_index.sh right after each collection instead, so the job log names
the tree the artifact contains.

All four sites call it without a fallback, which is what the preceding commit's
exit-status contract is for. host_deploy.sh and one.sh hoist the rescue path
into a variable first - it is now needed twice, once for the collector's
INFINITO_RESCUE_DIAGNOSTICS_DIR and once for the index.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-08-01 02:13:29 +02:00

..

compose_deploy.sh

refactor(guide): reuse the rescue-diagnostics collector and extract the compose replay

2026-07-23 20:01:31 +02:00

host_deploy.sh

feat(ci): index the rescue tree at every collection site

2026-08-01 02:13:29 +02:00

one.sh

feat(ci): index the rescue tree at every collection site

2026-08-01 02:13:29 +02:00