planner-scope v0.4.0 explains that a linked Gitea issue is claimed by the owner after the exact Plan reaches the Implementer. Schema-version-2 package metadata declares its default target, status/in-progress. A user can select an automatic Planner fork with a different issueClaim.statusLabel or null to disable the claim. The owner validates and freezes that declaration; skill prose has no provider authority. The package is pinned by public tag v0.5.0 at 24e3deb34ef531fcdeabf549c358949b923eb723.
Evidence
Before:planner-scope did not describe the issue claim milestone or declare a replaceable policy.
After: the package check prints identity b6f7249d8ac66cc0cec587c4a79063d4ff05d4a1bc4dcff6afb6609c26fcb025; all 12 source tests pass. Product PR #892 tests owner admission and fork selection.
Blast Radius: future Planner sessions assigned this package receive revised guidance and a bounded owner claim policy. Existing sessions and tasks retain their captured identities. The skill has no provider credentials or stage authority.
Reviewer prerequisites
None.
Manual Test Plan
Action: Inspect packages/planner-scope/SKILL.md and packages/planner-scope/relayview-skill.json on this branch.
Expected: the instruction names the owner-managed handoff milestone and replacement path; the manifest declares issueClaim.statusLabel and pins its exact instruction bytes.
Post-Merge Cleanup
No worktree cleanup until the dependent product change has been reviewed.
## Summary
`planner-scope` v0.4.0 explains that a linked Gitea issue is claimed by the owner after the exact Plan reaches the Implementer. Schema-version-2 package metadata declares its default target, `status/in-progress`. A user can select an automatic Planner fork with a different `issueClaim.statusLabel` or `null` to disable the claim. The owner validates and freezes that declaration; skill prose has no provider authority. The package is pinned by public tag `v0.5.0` at `24e3deb34ef531fcdeabf549c358949b923eb723`.
## Evidence
- **Before:** `planner-scope` did not describe the issue claim milestone or declare a replaceable policy.
- **After:** the package check prints identity `b6f7249d8ac66cc0cec587c4a79063d4ff05d4a1bc4dcff6afb6609c26fcb025`; all 12 source tests pass. Product PR #892 tests owner admission and fork selection.
### Checks run
- `python -m tools.packages check packages/planner-scope` — passed.
- `python -m unittest discover -s tests -v` — 12 passed.
- `git diff --check` — passed.
## Merge Danger
**Door:** two-way
**Blast Radius:** future Planner sessions assigned this package receive revised guidance and a bounded owner claim policy. Existing sessions and tasks retain their captured identities. The skill has no provider credentials or stage authority.
## Reviewer prerequisites
None.
## Manual Test Plan
1. [ ] **Action:** Inspect `packages/planner-scope/SKILL.md` and `packages/planner-scope/relayview-skill.json` on this branch.
**Expected:** the instruction names the owner-managed handoff milestone and replacement path; the manifest declares `issueClaim.statusLabel` and pins its exact instruction bytes.
## Post-Merge Cleanup
No worktree cleanup until the dependent product change has been reviewed.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
planner-scopev0.4.0 explains that a linked Gitea issue is claimed by the owner after the exact Plan reaches the Implementer. Schema-version-2 package metadata declares its default target,status/in-progress. A user can select an automatic Planner fork with a differentissueClaim.statusLabelornullto disable the claim. The owner validates and freezes that declaration; skill prose has no provider authority. The package is pinned by public tagv0.5.0at24e3deb34ef531fcdeabf549c358949b923eb723.Evidence
planner-scopedid not describe the issue claim milestone or declare a replaceable policy.b6f7249d8ac66cc0cec587c4a79063d4ff05d4a1bc4dcff6afb6609c26fcb025; all 12 source tests pass. Product PR #892 tests owner admission and fork selection.Checks run
python -m tools.packages check packages/planner-scope— passed.python -m unittest discover -s tests -v— 12 passed.git diff --check— passed.Merge Danger
Door: two-way
Blast Radius: future Planner sessions assigned this package receive revised guidance and a bounded owner claim policy. Existing sessions and tasks retain their captured identities. The skill has no provider credentials or stage authority.
Reviewer prerequisites
None.
Manual Test Plan
Action: Inspect
packages/planner-scope/SKILL.mdandpackages/planner-scope/relayview-skill.jsonon this branch.Expected: the instruction names the owner-managed handoff milestone and replacement path; the manifest declares
issueClaim.statusLabeland pins its exact instruction bytes.Post-Merge Cleanup
No worktree cleanup until the dependent product change has been reviewed.
View command line instructions
Checkout
From your project repository, check out a new branch and test the changes.