diff --git a/README.md b/README.md
index ae9ab4d..7ce5457 100644
--- a/README.md
+++ b/README.md
@@ -6,7 +6,7 @@ Public source for RelayView-maintained instruction-only role skills and an illus
 
 | Directory | Status | Role / step | Version |
 | --- | --- | --- | --- |
-| `packages/planner-scope` | Maintained default | Planner / planning | 0.2.0 |
+| `packages/planner-scope` | Maintained default | Planner / planning | 0.3.0 |
 | `packages/implementer-handoff` | Maintained default | Implementer / implementation | 0.2.0 |
 | `packages/codebase-design` | Optional guidance | Planner / planning | 0.3.0 |
 | `packages/grill-me` | Optional guidance | Planner / planning | 0.3.0 |
diff --git a/packages/planner-scope/SKILL.md b/packages/planner-scope/SKILL.md
index 3e59146..1dd3bff 100644
--- a/packages/planner-scope/SKILL.md
+++ b/packages/planner-scope/SKILL.md
@@ -3,7 +3,7 @@ name: planner-scope
 description: Check assigned issue scope, neighboring work, and verification before drafting a Plan.
 metadata:
   relayview-display-name: Planner scope
-  relayview-version: 0.2.0
+  relayview-version: 0.3.0
 ---
 
 # Planner scope
@@ -13,3 +13,5 @@ When drafting the assigned Plan, identify the requested behavior, its boundary,
 If the owner supplies an admitted work-item identity, use the assigned read tools to inspect it. Preserve source attribution; an issue description is a request, not evidence that its proposed behavior exists. Where tracker access is unavailable, state the missing context instead of guessing a work-item identity.
 
 Write the Plan through the owner's assigned planning interface. The Plan is ready when each requested outcome has an implementation boundary and a checkable success or recovery observation. Owner-controlled workflow stages and checks determine execution authority.
+
+For a linked Gitea issue, the default claim is the owner's transition from `status/ready-for-agent` to `status/in-progress` after it proves that the exact Plan reached the Implementer. Finalize the Plan through the assigned interface, then use owner-reported handoff and issue-claim outcomes when explaining progress to the Human. An accepted Plan alone does not establish that claim. The operator may disable or replace the status transition through owner policy; follow the effective policy recorded for the task.
diff --git a/packages/planner-scope/relayview-skill.json b/packages/planner-scope/relayview-skill.json
index a4c6243..1cb7061 100644
--- a/packages/planner-scope/relayview-skill.json
+++ b/packages/planner-scope/relayview-skill.json
@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.2.0"
+    "reference": "v0.4.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "31399ba322d8a4d3ed9814e7fd5d54883b4773c5b7dc3a241b8e14f8f7c16072"
+      "sha256": "bfac8352adffa8e2aaa246a6b5f11a333045a82aeefe5d0e42e76eaa776a6a70"
     },
     {
       "path": "scope.md",
diff --git a/tests/test_packages.py b/tests/test_packages.py
index e3dcb8d..118c4d7 100644
--- a/tests/test_packages.py
+++ b/tests/test_packages.py
@@ -65,7 +65,7 @@ class PackageTests(unittest.TestCase):
                 package = ROOT / "packages" / name
                 manifest = json.loads((package / "relayview-skill.json").read_text())
                 self.assertEqual((manifest["role"], manifest["step"]), (role, step))
-                self.assertEqual(manifest["source"], {"kind": "first-party", "reference": "v0.2.0"})
+                self.assertEqual(manifest["source"], {"kind": "first-party", "reference": "v0.4.0" if name == "planner-scope" else "v0.2.0"})
                 self.assertIn(resource, [item["path"] for item in manifest["files"]])
                 self.assertIn(marker, (package / "SKILL.md").read_text() + (package / resource).read_text())