Archive all logs for a completed issue to cloud storage
<issue_number> [--force] [--retry]claude-haiku-4-5# Archive Logs Archive all logs for a completed issue to cloud storage. ## Usage ## Arguments - `issue_number`: GitHub issue number (required) ## Options - `--force`: Skip checks and force re-archive - `--retry`: Retry failed uploads from a partial archive ## What It Does 1. Collects all logs for issue (sessions, builds, deployments, debug) 2. Compresses large logs (> 1MB) 3. Uploads to cloud storage via fractary-file 4. Tracks upload status per file (pending/uploaded/failed) 5. Updates archive index with partial/complete status 6. Comments on GitHub issue 7. Removes local copies ...
Properly archive completed orchestrations while preserving valuable data, metrics, and lessons learned for future reference.
Manually archive completed increments and sync living docs - NEVER auto-archives, explicit user action only
Archive a completed feature.
Archive specifications for completed work
Archive all FABER workflow artifacts for completed work