docs(skills): clarify issue boundary routing

Co-Authored-By: Paperclip <noreply@paperclip.ing>

skills/paperclip/SKILL.md

@@ -405,17 +405,16 @@ currently-checked-out issue. If you try to `PATCH /api/issues/{id}` or
 is dropped. This is a per-run scope, not a per-agent scope: you can own an
 issue conceptually and still hit 403 from a different task-bridge run.
 
-**Before you mutate another agent's issue, do one of:**
+**Before you mutate another agent's issue:**
 
-1. Check the target issue's `assigneeAgentId` and `authorizationBoundary` fields:
+1. Always check the target issue's `assigneeAgentId` and `authorizationBoundary` fields:
    ```sh
    curl -sS "$PAPERCLIP_API_URL/api/issues/<targetId>" \
      -H "Authorization: Bearer $PAPERCLIP_API_KEY" \
      | jq '{assignee: .assigneeAgentId, boundary: .authorizationBoundary}'
    ```
-   If the assignee is not you and the boundary does not include you, do not
-   attempt the write. Route the ask instead.
-2. Route the ask via one of:
+2. If the target issue is not inside your current run's write boundary, do not
+   attempt the write. Route the ask via one of:
    - A comment on your own issue naming the target owner and the desired change.
    - A child issue assigned to the owner with the mutation encoded as its body.
    - An `interactions` request on your issue when a human/board approval is