Local Agent Guides CI: run the resume job weekly, not dispatch-only

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.

.github/workflows/local-agent-guides-ci.yml

@@ -479,11 +479,12 @@ jobs:
   #   a temp dir wiped on exit, so codex/pi cannot resume; --persist routes the
   #   session to the stable Unsloth agents dir so it persists. opencode/claude
   #   keep their session data in a fixed user dir, so they persist either way.
-  #   Dispatch-only: it is an end-to-end experiment, not a PR gate.
+  #   Weekly + dispatch only (like file-edit) -- it drives the launch path end
+  #   to end on a 4B model, too slow and model-heavy to gate PRs.
   # ═════════════════════════════════════════════════════════════════════
   resume:
     name: resume (${{ matrix.agent }})
-    if: github.event_name == 'workflow_dispatch'
+    if: github.event_name != 'pull_request'
     runs-on: ubuntu-latest
     timeout-minutes: 60
     strategy: