diff --git a/src/skills/github-pr-workflow/skill.md b/src/skills/github-pr-workflow/skill.md
index 990f78a..01763be 100644
--- a/src/skills/github-pr-workflow/skill.md
+++ b/src/skills/github-pr-workflow/skill.md
@@ -147,7 +147,11 @@ This section earns trust over time. Hide problems in it once and it becomes usel
 
 Post in Slack with the PR link and a one-line *consequence* summary — what the merge will change for the team, and what (if anything) is shaky enough to watch after it lands. Not "opened a PR titled X"; rather "PR up to fix the export timezone bug — safe for the next migration window, flagging the rollback path as untested." See `src/identity.md` "Lead with the consequence" for the framing.
 
-Watch CI. When CI completes:
+Watch CI. If CI is going to take more than ~60 seconds to complete, **do not sit in sleep loops waiting for it** (as seen in session `e0c352b08e45` which accumulated 11× `sleep` and timed out on 2026-05-25). 
+
+Instead, post the PR link with the current CI status, exit the session cleanly, and let a subsequent session — or, now that SAM-5's webhook loop is live, the inbound `check_run` event — catch up on the result once CI completes.
+
+When CI does complete and you are back in a session:
 
 - **Green:** post in Slack. PR is ready for review.
 - **Red:** read the logs and decide. If the failure is clearly Sam's, fix and push. If it looks like flake or infra, say so in Slack and ask whether to retry. If unsure, post what Sam sees and ask.