The resume job (added with unsloth start --persist) proves a launch-path session survives exit and reopens: codex/pi need --persist to keep the session out of the wiped temp home, opencode/claude persist either way. It was gated to workflow_dispatch, so a regression in the --persist wiring only surfaced when someone remembered to run it by hand. Promote it to the same cadence as file-edit (if: github.event_name != 'pull_request'): it now runs on the weekly schedule and on manual dispatch, so --persist is exercised automatically. It stays off pull_request for the same reason file-edit does, it drives the real launch path end to end on a 4B model and is too slow to gate PRs. |
||
|---|---|---|
| .. | ||
| ISSUE_TEMPLATE | ||
| scripts | ||
| workflows | ||
| CODEOWNERS | ||
| dependabot.yml | ||
| FUNDING.yml | ||