export v0.1.8: session-scope-guard human-only three-channel ruling (#6617) + browser-debug nested OOPIF skill update

core/rules/session-scope-guard.md

@@ -84,6 +84,19 @@ and the provision wrapper (adds the worktree + Tier-1 runs scaffold). The
 manual 3-step is the fallback where the scripts are unavailable, same
 re-verification.
 
+**Human-only tickets ([org-internal #6617]-P1).** A ticket marked
+human-only in ANY of three machine-readable forms — title `[人工执行]`
+(ASCII/【】 fullwidth variants), label `executor/human-only`, or a body
+line `executor: human` / `executor: human-only` (line-anchored,
+blockquote-tolerant) — is NOT claimable by an agent: the claim script
+refuses (exit 4, stage=precheck; takeover mode too — taking over a dead
+claim is not taking over execution rights). The title channel keeps the
+`--allow-human-only` override (explicit human instruction only, visible in
+the invoking transcript); the label/body channels have NO override — an
+explicit marker is a hard refusal for agents ([org-internal #6617] merged
+ruling). Never claim, execute, self-accept or close such a ticket on agent
+initiative.
+
 **Merge-time equivalence check.** Before merging, scan the remote main
 branch's recent commits for `#<ticket>` — surfacing an equivalent
 implementation already on main *before* the merge rejection.