Release Operator role wording in instruction packages

README.md

@@ -1,39 +1,39 @@
 # RelayView skills
 
-Public source for RelayView-maintained instruction-only role skills and an illustrative author starter. The proprietary RelayView owner controls workflow stages, role tools, verification, and Human acceptance. A skill guides one assigned role during one step; it does not add tools, credentials, network access, or workflow authority.
+Public source for RelayView-maintained instruction-only role skills and an illustrative author starter. The proprietary RelayView owner controls workflow stages, role tools, verification, and Operator acceptance. A skill guides one assigned role during one step; it does not add tools, credentials, network access, or workflow authority.
 
 ## Packages and support
 
 | Directory | Status | Role / step | Version |
 | --- | --- | --- | --- |
-| `packages/{planner,implementer,reviewer}-investigation` | Maintained automatic guidance | One matching role / step each | 0.7.0 |
+| `packages/{planner,implementer,reviewer}-investigation` | Maintained automatic guidance | One matching role / step each | 0.13.0 |
-| `packages/planner-scope` | Maintained default | Planner / planning | 0.8.1 |
+| `packages/planner-scope` | Maintained default | Planner / planning | 0.13.0 |
-| `packages/implementer-handoff` | Maintained default | Implementer / implementation | 0.9.0 |
+| `packages/implementer-handoff` | Maintained default | Implementer / implementation | 0.13.0 |
-| `packages/issue-designer-default` | Maintained default | Designer / design | 0.6.1 |
+| `packages/issue-designer-default` | Maintained default | Designer / design | 0.13.0 |
-| `packages/designer-wayfinder`, `designer-grilling` | Optional manual guidance | Designer / design | 0.6.0 |
+| `packages/designer-wayfinder`, `designer-grilling` | Optional manual guidance | Designer / design | 0.13.0 |
-| `packages/designer-prototype` | Optional manual guidance | Designer / design | 0.6.2 |
+| `packages/designer-prototype` | Optional manual guidance | Designer / design | 0.13.0 |
-| `packages/designer-research`, `designer-domain-modeling`, `designer-triage` | Optional manual guidance | Designer / design | 0.6.0 |
+| `packages/designer-research`, `designer-domain-modeling`, `designer-triage` | Optional manual guidance | Designer / design | 0.13.0 |
-| `packages/designer-to-spec`, `designer-to-tickets` | Optional manual guidance | Designer / design | 0.6.0 |
+| `packages/designer-to-spec`, `designer-to-tickets` | Optional manual guidance | Designer / design | 0.13.0 |
-| `packages/codebase-design` | Optional guidance | Planner / planning | 0.3.0 |
+| `packages/codebase-design` | Optional guidance | Planner / planning | 0.13.0 |
-| `packages/grill-me` | Optional guidance | Planner / planning | 0.3.0 |
+| `packages/grill-me` | Optional guidance | Planner / planning | 0.13.0 |
-| `packages/grilling` | Optional guidance | Planner / planning | 0.3.0 |
+| `packages/grilling` | Optional guidance | Planner / planning | 0.13.0 |
-| `packages/to-questionnaire` | Optional guidance | Planner / planning | 0.3.0 |
+| `packages/to-questionnaire` | Optional guidance | Planner / planning | 0.13.0 |
-| `packages/research` | Optional guidance | Planner / planning | 0.3.0 |
+| `packages/research` | Optional guidance | Planner / planning | 0.13.0 |
-| `packages/improve-codebase-architecture` | Optional guidance | Planner / planning | 0.3.0 |
+| `packages/improve-codebase-architecture` | Optional guidance | Planner / planning | 0.13.0 |
-| `packages/diagnosing-bugs` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/diagnosing-bugs` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/domain-modeling` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/domain-modeling` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/migrate-to-shoehorn` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/migrate-to-shoehorn` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/pr` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/pr` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/prototype` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/prototype` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/scaffold-exercises` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/scaffold-exercises` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/shared-abstraction-refactor` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/shared-abstraction-refactor` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/split-large-files` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/split-large-files` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/tdd` | Optional manual guidance | Implementer / implementation | 0.3.0 |
+| `packages/tdd` | Optional manual guidance | Implementer / implementation | 0.13.0 |
-| `packages/tdd-auto` | Optional automatic guidance | Implementer / implementation | 0.3.1 |
+| `packages/tdd-auto` | Optional automatic guidance | Implementer / implementation | 0.13.0 |
-| `packages/writing-for-agents` | Optional guidance | Implementer / implementation | 0.3.0 |
+| `packages/writing-for-agents` | Optional guidance | Implementer / implementation | 0.13.0 |
-| `packages/code-review` | Optional guidance | Reviewer / review | 0.3.0 |
+| `packages/code-review` | Optional guidance | Reviewer / review | 0.13.0 |
-| `packages/c4-diff` | Optional guidance | Reviewer / review | 0.3.0 |
+| `packages/c4-diff` | Optional guidance | Reviewer / review | 0.13.0 |
-| `examples/starter-planner` | Illustrative starter; not a production default | Planner / planning | 0.1.0 |
+| `examples/starter-planner` | Illustrative starter; not a production default | Planner / planning | 0.13.0 |
 
 Only named releases of maintained packages receive RelayView compatibility testing and maintenance. Optional guidance requires explicit role assignment; the Planner and Implementer defaults remain available alongside the pinned Issue Designer default. User forks are maintained by their publishers. Instruction packages use schema version 1, or schema version 2 for a Planner package declaring owner-validated `issueClaim` metadata. Schema 2 accepts a nullable target status label; the owner enforces the claim transition after proved implementation handoff. It contains only `SKILL.md`, declared `.md`/`.txt` resources, and `relayview-skill.json` within each package. Scripts, executable files, undeclared files, and requested permissions fail checks and owner admission. There is no fixed release calendar: maintained packages are versioned when their content or compatibility changes. A breaking owner contract requires a new compatible maintained release before the product depends on it.
 
@@ -70,7 +70,7 @@ Replace `examples/starter-planner` in the last two commands with your package di
 
 To use a user fork, place its closed package directory under the owner's configured trusted root. For Planner, Implementer, or Reviewer guidance, use Settings → Skills to import the relative `SKILL.md` path under a new unique ID. Import validates and records the package; it does not assign it. Add that ID to a role-compatible named set in the owner configuration and restart the owner to load the set. Then select the set for the matching role in Settings → Skills and save. For an optional Designer method, declare its ID and relative `SKILL.md` path in `trustedSkills.catalog`, list the ID in `workflowPresets.designerSkills`, and restart the owner. Designer has no Settings import or set selector for this assignment. These assignments affect future sessions; existing sessions retain their captured bytes. The owner's admission remains authoritative even when these local checks pass.
 
-To use a maintained Planner or Implementer default, copy its release package under the same trusted root, admit its `SKILL.md` through the owner catalog, then select it for its declared role in Settings. Settings import accepts user-source packages; configure first-party packages in the owner catalog. Select a fork with `source.kind: user` and a distinct ID to replace a Planner or Implementer future assignment. RelayView pins and assigns the Issue Designer default automatically; its optional methods use `workflowPresets.designerSkills`. Planner guidance uses existing read and planning tools; Implementer guidance uses existing implementation and reporting tools. Guidance selection does not change a role's tools, credentials, lifecycle stages, validation requirements, Gitea effects, review, merge, or Human acceptance. The owner keeps the existing Gitea task workflow.
+To use a maintained Planner or Implementer default, copy its release package under the same trusted root, admit its `SKILL.md` through the owner catalog, then select it for its declared role in Settings. Settings import accepts user-source packages; configure first-party packages in the owner catalog. Select a fork with `source.kind: user` and a distinct ID to replace a Planner or Implementer future assignment. RelayView pins and assigns the Issue Designer default automatically; its optional methods use `workflowPresets.designerSkills`. Planner guidance uses existing read and planning tools; Implementer guidance uses existing implementation and reporting tools. Guidance selection does not change a role's tools, credentials, lifecycle stages, validation requirements, Gitea effects, review, merge, or Operator acceptance. The owner keeps the existing Gitea task workflow.
 
 ## Write the guidance
 

packages/c4-diff/SKILL.md

@@ -4,7 +4,7 @@ description: Explain structural changes in an owner-pinned code diff with tracea
 disable-model-invocation: true
 metadata:
   relayview-display-name: Component diff
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Component diff review

packages/c4-diff/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "reviewer",
   "step": "review",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "f1746262e65a8a3de9223a8c42a30b354a6718fea3819079cd13597a258da567"
+      "sha256": "74bd447bb072c0667fb2276398ee2cadc28079917a4c7781fe18fd5e7f868b83"
     }
   ]
 }

packages/code-review-auto/SKILL.md

@@ -3,7 +3,7 @@ name: code-review-auto
 description: Present findings for the owner-assigned review candidate.
 metadata:
   relayview-display-name: Review finding presentation
-  relayview-version: 0.10.0
+  relayview-version: 0.13.0
 ---
 
 # Review finding presentation

packages/code-review-auto/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.10.0"
+    "reference": "v0.13.0"
   },
   "role": "reviewer",
   "step": "review",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "5a09004af9e208a80712dba2dad2975fcd457f296472f8cd2e13f48b43d0950d"
+      "sha256": "2040364a3cd49fb21346295fff371c1ef242e3227e33cd9138c30bbf10923514"
     }
   ]
 }

packages/code-review/SKILL.md

@@ -4,7 +4,7 @@ description: Review the owner-pinned candidate against repository standards and
 disable-model-invocation: true
 metadata:
   relayview-display-name: Code review
-  relayview-version: 0.10.0
+  relayview-version: 0.13.0
 ---
 
 # Two-axis code review

packages/code-review/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.10.0"
+    "reference": "v0.13.0"
   },
   "role": "reviewer",
   "step": "review",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "bb7e5e4d30dcf43eddb9e16ddf7e7ddad123fba18ef7b22286b8b1233888b81b"
+      "sha256": "c3ce841b0e1e104393d2feabd9982fff08bab59177a8b36a7910dec89a3a8734"
     }
   ]
 }

packages/codebase-design/SKILL.md

@@ -3,7 +3,7 @@ name: codebase-design
 description: Examine module interfaces and seams while drafting a repository Plan.
 metadata:
   relayview-display-name: Codebase design
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Codebase design for Planner

packages/codebase-design/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "8633b139187c3ba62e75338f3792ef6d7a445559b792cfb4926cb722609c161a"
+      "sha256": "4932d91c98ec71eced5decd4b79f6533b93dbe04e78a810b6de7a329bbd4e23f"
     },
     {
       "path": "module-guide.md",

packages/designer-domain-modeling/SKILL.md

@@ -4,9 +4,9 @@ description: Sharpen project terms, invariants, and boundaries for an issue draf
 disable-model-invocation: true
 metadata:
   relayview-display-name: Designer domain modeling
-  relayview-version: 0.6.0
+  relayview-version: 0.13.0
 ---
 
 # Domain modeling
 
-Read the assigned project's current context and relevant authoritative contracts. Name concepts in the project's own vocabulary; identify identities, state transitions, invariants, and boundaries that the proposed work touches. Ask the Human when a term or invariant changes acceptance. Put the resulting definitions and open choices in the draft without claiming a repository document was edited.
+Read the assigned project's current context and relevant authoritative contracts. Name concepts in the project's own vocabulary; identify identities, state transitions, invariants, and boundaries that the proposed work touches. Ask the Operator when a term or invariant changes acceptance. Put the resulting definitions and open choices in the draft without claiming a repository document was edited.

packages/designer-domain-modeling/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.0"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "cfb72adc02cf0a488c341d965c16e22d22e90c52ab0540a9072b09c592d1abd7"
+      "sha256": "db980f11e64f3936e913d33ba71e7f33b5ad171c82af9c814cb7fd32b43b03e2"
     }
   ]
 }

packages/designer-grilling/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: designer-grilling
-description: Stress test one proposed issue design through focused Human questions.
+description: Stress test one proposed issue design through focused Operator questions.
 disable-model-invocation: true
 metadata:
   relayview-display-name: Designer grilling
-  relayview-version: 0.6.0
+  relayview-version: 0.13.0
 ---
 
 # Grilling
 
-State the design and scope to be challenged and seek the Human's agreement before entering this method. Probe one consequential assumption at a time: behavior, boundary, dependency, failure, or verification. Use each answer to choose the next question. Stop when the important branches are resolved or explicitly left open; summarize the agreed design and open decisions in the draft.
+State the design and scope to be challenged and seek the Operator's agreement before entering this method. Probe one consequential assumption at a time: behavior, boundary, dependency, failure, or verification. Use each answer to choose the next question. Stop when the important branches are resolved or explicitly left open; summarize the agreed design and open decisions in the draft.

packages/designer-grilling/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.0"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "431da86a21da7b74fa55bce36c1e0fc806d066cd8b1ace7a784e1eb4a2db4a89"
+      "sha256": "e1cbf117510c6497241122ab8f7564d78d7fdaf85ba6e3b43256c881dea2d6bb"
     }
   ]
 }

packages/designer-prototype/SKILL.md

@@ -4,30 +4,30 @@ description: Plan a bounded throwaway prototype to answer a design question.
 disable-model-invocation: true
 metadata:
   relayview-display-name: Designer prototype
-  relayview-version: 0.6.2
+  relayview-version: 0.13.0
 ---
 
 # Prototype
 
-Propose the exact question, bounded code or data scope, expected preview or data effects, and limits to the Human before entering this method. Use only owner-admitted prototype controls after agreement. Treat observations as evidence about the question, not production behavior. Record what was tried, observed, and still uncertain; keep throwaway changes out of the issue's implementation claim.
+Propose the exact question, bounded code or data scope, expected preview or data effects, and limits to the Operator before entering this method. Use only owner-admitted prototype controls after agreement. Treat observations as evidence about the question, not production behavior. Record what was tried, observed, and still uncertain; keep throwaway changes out of the issue's implementation claim.
 
-## Let the Human try it as a user
+## Let the Operator try it as a user
 
-The Human answers the question by using the prototype the way the software's user will. The commands they type are part of the design under review: the command name, its arguments and options, and the directory it runs from.
+The Operator answers the question by using the prototype the way the software's user will. The commands they type are part of the design under review: the command name, its arguments and options, and the directory it runs from.
 
-- Prepare the scenario yourself before handing over. Create the sample data, repositories, and earlier history the question needs, and run any setup steps, so the scenario is ready when the Human arrives.
+- Prepare the scenario yourself before handing over. Create the sample data, repositories, and earlier history the question needs, and run any setup steps, so the scenario is ready when the Operator arrives.
 - Put the scenario's data where the app finds it by default, such as its default config or source directory under HOME, so the user's command needs no extra options.
-- Make the Human's first command one the software's user will type: the real command name, the syntax this change proposes, and the arguments a user would pass, run from the directory where a user would be.
+- Make the Operator's first command one the software's user will type: the real command name, the syntax this change proposes, and the arguments a user would pass, run from the directory where a user would be.
 - Give each command to try exactly as that user types it, and say what it shows.
-- Give the Human only the commands needed to answer the design question. Add a reset command only when one of those commands changes the scenario; then put it in `/scratch/bin` and give it by its name alone, followed by the command to try again.
+- Give the Operator only the commands needed to answer the design question. Add a reset command only when one of those commands changes the scenario; then put it in `/scratch/bin` and give it by its name alone, followed by the command to try again.
-- Ask the Human about what they saw as a user of the software, in terms of the design question.
+- Ask the Operator about what they saw as a user of the software, in terms of the design question.
 
 ## Before handing over
 
-Work through this checklist, then give the Human the shell command and the first command to try:
+Work through this checklist, then give the Operator the shell command and the first command to try:
 
 1. The app's command runs by its own name from `/scratch/bin`: a configured command the owner listed, or a launcher you wrote. Run `cd` to the command directory, then the command with an unknown option, and confirm its usage message names the command as the user types it.
 2. The scenario's data is where the app finds it by default under the workspace's HOME.
-3. Helper commands are in `/scratch/bin`, so the Human runs each by its name.
+3. Helper commands are in `/scratch/bin`, so the Operator runs each by its name.
 4. The command directory is set with `configure` to where the app's user runs the app.
-5. You ran the first command to try yourself, exactly as the Human will type it, from that directory, and it showed what the question is about.
+5. You ran the first command to try yourself, exactly as the Operator will type it, from that directory, and it showed what the question is about.

packages/designer-prototype/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.2"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "b72f085f33c10ea48f69fbe55c4f364f6a873a8ae2e6baeb8eaf2aaf71df5045"
+      "sha256": "ebf3ff2a5321ca8984e318d37a37c00b9ad9ef3c7966e9cf04eeab996eb16ae3"
     }
   ]
 }

packages/designer-research/SKILL.md

@@ -4,7 +4,7 @@ description: Research a design question using admitted repository, tracker, and
 disable-model-invocation: true
 metadata:
   relayview-display-name: Designer research
-  relayview-version: 0.6.0
+  relayview-version: 0.13.0
 ---
 
 # Research

packages/designer-research/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.0"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "676c4291d4bab19c76c0d945eefe21aa6787783e4e2d2285e0d6e270303d1e94"
+      "sha256": "d745d68f04984c5d69ec0356da24c2147eb9738003096e792f6ad3a72b040cf0"
     }
   ]
 }

packages/designer-to-spec/SKILL.md

@@ -4,9 +4,9 @@ description: Turn an agreed problem into a complete reviewable issue specificati
 disable-model-invocation: true
 metadata:
   relayview-display-name: Designer to spec
-  relayview-version: 0.6.0
+  relayview-version: 0.13.0
 ---
 
 # To spec
 
-Use the agreed problem and observed project contracts to draft an outcome, scope boundaries, acceptance observations, failure and recovery behavior, and open decisions. Check prerequisites against the assigned tracker and mark uncertain links as proposed. Save the complete text through the owner-stored draft. The Human decides readiness and publication.
+Use the agreed problem and observed project contracts to draft an outcome, scope boundaries, acceptance observations, failure and recovery behavior, and open decisions. Check prerequisites against the assigned tracker and mark uncertain links as proposed. Save the complete text through the owner-stored draft. The Operator decides readiness and publication.

packages/designer-to-spec/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.0"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "c4b8707f88faf1b9f3e04bb707b45bbb3d89848a8a3b2ac807dc819e8dd29f91"
+      "sha256": "96afff887cda29d1a2447ef4ccd8f6dd3fbf00b622623bd3d69d6bc0f1efc40d"
     }
   ]
 }

packages/designer-to-tickets/SKILL.md

@@ -4,9 +4,9 @@ description: Decompose an agreed specification into ordered issue proposals.
 disable-model-invocation: true
 metadata:
   relayview-display-name: Designer to tickets
-  relayview-version: 0.6.0
+  relayview-version: 0.13.0
 ---
 
 # To tickets
 
-Choose independently reviewable slices with observable outcomes and prerequisite edges only where one slice truly requires another. For each proposed issue, state scope, acceptance, verification, and context a cold-start agent needs. Present the ordered set and relationship rationale to the Human. Keep proposals private until Human review and owner publication.
+Choose independently reviewable slices with observable outcomes and prerequisite edges only where one slice truly requires another. For each proposed issue, state scope, acceptance, verification, and context a cold-start agent needs. Present the ordered set and relationship rationale to the Operator. Keep proposals private until Operator review and owner publication.

packages/designer-to-tickets/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.0"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "561db3543cfdffe55b8002954d7debcf9d0fc1125d51c688a74cf2469d3d73a1"
+      "sha256": "b52ad8f158a1aa27c469e33e9f15b3b3f47ad8c3658444ee0fc6d137ed80ad53"
     }
   ]
 }

packages/designer-triage/SKILL.md

@@ -4,9 +4,9 @@ description: Classify and route an observed issue before drafting work.
 disable-model-invocation: true
 metadata:
   relayview-display-name: Designer triage
-  relayview-version: 0.6.0
+  relayview-version: 0.13.0
 ---
 
 # Triage
 
-Observe the current report and related tracker state. Separate verified symptoms, missing information, proposed behavior, and duplicate or prerequisite work. Suggest the smallest useful next state and explain the evidence for it. Draft an issue or question for Human review; only owner controls can change tracker status or placement.
+Observe the current report and related tracker state. Separate verified symptoms, missing information, proposed behavior, and duplicate or prerequisite work. Suggest the smallest useful next state and explain the evidence for it. Draft an issue or question for Operator review; only owner controls can change tracker status or placement.

packages/designer-triage/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.0"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "fa62a0806921d87ddd27e494cfc379513cc147ad658eb5a2981970ccb25babf5"
+      "sha256": "d09d9621c07476e1d3294d952ac85f011ac3ab83308a981817bcb991e70d402d"
     }
   ]
 }

packages/designer-wayfinder/SKILL.md

@@ -1,12 +1,12 @@
 ---
 name: designer-wayfinder
-description: Map an uncertain design decision into options and a Human choice.
+description: Map an uncertain design decision into options and a Operator choice.
 disable-model-invocation: true
 metadata:
   relayview-display-name: Designer Wayfinder
-  relayview-version: 0.6.0
+  relayview-version: 0.13.0
 ---
 
 # Wayfinder
 
-Use this method for a decision whose alternatives materially change the work. First describe the decision, why it matters, and the bounded scope to the Human; enter the method only after the Human agrees. Observe current facts, list viable options with consequences and reversibility, and ask the smallest question that separates them. Record the Human's decision and remaining uncertainty in the owner-stored draft when relevant. This is decision work, not a ready implementation claim.
+Use this method for a decision whose alternatives materially change the work. First describe the decision, why it matters, and the bounded scope to the Operator; enter the method only after the Operator agrees. Observe current facts, list viable options with consequences and reversibility, and ask the smallest question that separates them. Record the Operator's decision and remaining uncertainty in the owner-stored draft when relevant. This is decision work, not a ready implementation claim.

packages/designer-wayfinder/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.0"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "c5b5db0755af497cfe9be9fee9912f1406fb3b8546d7f389998516ba298f27b0"
+      "sha256": "fb441d89ae15ed309d85dd8af4ae151dd951fb155c19ccf672083cca876e2671"
     }
   ]
 }

packages/diagnosing-bugs/SKILL.md

@@ -3,7 +3,7 @@ name: diagnosing-bugs
 description: Build a reproducible feedback loop before fixing an assigned defect.
 metadata:
   relayview-display-name: Diagnose bugs
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Diagnose within implementation

packages/diagnosing-bugs/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "41c5d0ccb48b19aef95e19103f3c7721b9c3ddf2e8bdf3ff2c429a26853b18ae"
+      "sha256": "b3c6d9a89c50365d0cd41b327e52c54043e1aa52b2dcb351656fe4950ee12144"
     }
   ]
 }

packages/domain-modeling/SKILL.md

@@ -3,12 +3,12 @@ name: domain-modeling
 description: Reconcile verified domain vocabulary and accepted decisions during implementation.
 metadata:
   relayview-display-name: Domain modeling
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Domain documentation in implementation
 
-Read the repository's domain glossary and documentation rules before changing a model. When the assigned implementation reveals ambiguous or conflicting terms, compare the proposed meaning with current code, tests, and the accepted Plan. Raise an unresolved decision through the assigned Human communication path; do not turn a guess into an authoritative term.
+Read the repository's domain glossary and documentation rules before changing a model. When the assigned implementation reveals ambiguous or conflicting terms, compare the proposed meaning with current code, tests, and the accepted Plan. Raise an unresolved decision through the assigned Operator communication path; do not turn a guess into an authoritative term.
 
 After a term or consequential design decision is accepted and verified, update the repository's existing glossary or decision record within the assigned worktree. Keep glossary entries about domain meaning rather than implementation mechanics. Record an ADR only for a hard-to-reverse, surprising trade-off whose decision authority and alternatives are known. Keep run-specific test evidence with the issue or review handoff.
 

packages/domain-modeling/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "8a4d491493655b19feeb799af625ccef1f9064f203f3e38f57ccd7e547c28be6"
+      "sha256": "0c203c9d52a7fce7d017d00e3b568b67b6236b5895523cb92bf5be8189fb264c"
     }
   ]
 }

packages/grill-me/SKILL.md

@@ -4,11 +4,11 @@ description: Ask one deliberate question at a time to clarify an assigned Plan.
 disable-model-invocation: true
 metadata:
   relayview-display-name: Grill me
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # One-question planning interview
 
-When the Human explicitly invokes this skill during planning, map the unresolved decisions affecting the assigned task. Check the repository and current Plan context for facts before asking. Ask one consequential question at a time, with a recommended answer and its consequence. Wait for the Human's answer before advancing to a dependent question.
+When the Operator explicitly invokes this skill during planning, map the unresolved decisions affecting the assigned task. Check the repository and current Plan context for facts before asking. Ask one consequential question at a time, with a recommended answer and its consequence. Wait for the Operator's answer before advancing to a dependent question.
 
 Keep a visible list of settled decisions and remaining branches. Stop when the requested scope, important alternatives, and verification expectations are explicit enough for a Plan. Place accepted decisions in the Plan through the assigned planning interface; do not treat an unanswered question as approval. This interview does not start implementation or change an owner workflow stage.

packages/grill-me/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "36895ad26a065b073d3d823557d83b62bd7bb771e74e65e4f246f4e08b52bb16"
+      "sha256": "c71bcdd1f7b3d9378d591581e5642a09193c947a66a2b9268e60c3a3d00a6e32"
     }
   ]
 }

packages/grilling/SKILL.md

@@ -1,14 +1,14 @@
 ---
 name: grilling
-description: Interview a Planner's Human about independent decision branches in rounds.
+description: Interview a Planner's Operator about independent decision branches in rounds.
 disable-model-invocation: true
 metadata:
   relayview-display-name: Grilling
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Planning decision rounds
 
-When the Human explicitly invokes this skill, draw the decision tree for the assigned Plan. Resolve repository facts with the Planner's assigned read tools. Identify the current frontier: questions whose prerequisites are already settled. Ask that frontier together in one numbered round, giving a recommended answer and consequence for each question. Wait for the Human's answers, update the tree, then recompute the frontier.
+When the Operator explicitly invokes this skill, draw the decision tree for the assigned Plan. Resolve repository facts with the Planner's assigned read tools. Identify the current frontier: questions whose prerequisites are already settled. Ask that frontier together in one numbered round, giving a recommended answer and consequence for each question. Wait for the Operator's answers, update the tree, then recompute the frontier.
 
-Keep dependent questions for later rounds. State when a branch remains unresolved; silence is not a decision. Stop when the frontier is empty and the Human confirms the scope is understood. Record settled requirements and open decisions through the assigned planning interface. Do not launch other agents, edit the repository, or change workflow stages.
+Keep dependent questions for later rounds. State when a branch remains unresolved; silence is not a decision. Stop when the frontier is empty and the Operator confirms the scope is understood. Record settled requirements and open decisions through the assigned planning interface. Do not launch other agents, edit the repository, or change workflow stages.

packages/grilling/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "1c88593633482d44022eac49de217fc16c8f102067549ba819f1b1ca1728307e"
+      "sha256": "6646c00bc0d1e45a1b7875d95c68e21d4cebd4958d046b61f0eb9c8cd7d73c51"
     }
   ]
 }

packages/implementer-communication/SKILL.md

@@ -3,7 +3,7 @@ name: implementer-communication
 description: Communication style for the assigned implementer; proportional answers, examples, Markdown and natural acknowledgements.
 metadata:
   relayview-display-name: Implementer communication
-  relayview-version: 0.11.0
+  relayview-version: 0.13.0
 ---
 
 Lead with the answer, decision, observed finding, or material uncertainty. Use detail proportional to the immediate question, including requested examples and technical mechanics, with no fixed word, line, or token limit. Keep inspection effort independent of conversational length.

packages/implementer-communication/relayview-skill.json

@@ -2,7 +2,7 @@
   "schemaVersion": 3,
   "source": {
     "kind": "first-party",
-    "reference": "v0.11.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
@@ -10,7 +10,7 @@
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "07e3c2278c1f7005517265b738f57287b12a6b28e11b928cf7e32ec34b6b4dd4"
+      "sha256": "89cc00ed7f84f2b759a02b3c561033b467828067c2bba061d822df4ebca34400"
     }
   ]
 }

packages/implementer-handoff/SKILL.md

@@ -3,7 +3,7 @@ name: implementer-handoff
 description: Reconcile verified implementation documentation and prepare review content during implementation.
 metadata:
   relayview-display-name: Implementer handoff
-  relayview-version: 0.9.0
+  relayview-version: 0.13.0
 ---
 
 # Implementer handoff

packages/implementer-handoff/handoff.md

@@ -17,4 +17,4 @@ Ask the planner for more information when blocked after reasonable investigation
 - Summarize the user-visible change and its bounded impact.
 - Name the candidate revision and the focused checks run against it, with observed pass or failure results.
 - Give a reviewer executable steps and expected observations for any behavior that automated checks cannot establish.
-- State remaining uncertainty and recovery steps. Attribute provider or Human observations to their actual source.
+- State remaining uncertainty and recovery steps. Attribute provider or Operator observations to their actual source.

packages/implementer-handoff/relayview-skill.json

@@ -2,18 +2,18 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.9.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "a826d49f478018190539843022b83c11e7a034fa3597edcc85b8a57c65ac434d"
+      "sha256": "1cd3190db3991f9c310e2d3c3be854a32171cdf4d774d7868de466d5a403afe6"
     },
     {
       "path": "handoff.md",
-      "sha256": "17a32948aeb0e0359c92924219e6c328f3422773d5d878ffbcf0bf2f07a99aeb"
+      "sha256": "5171fe6c5aab6934f828efd6b06dcc3811e94f567035a56515fbc6798d4c9751"
     }
   ]
 }

packages/implementer-investigation/SKILL.md

@@ -3,7 +3,7 @@ name: implementer-investigation
 description: Investigate source, generated configuration, load order and negative search results within the assigned implementer boundary.
 metadata:
   relayview-display-name: Implementer investigation
-  relayview-version: 0.7.0
+  relayview-version: 0.13.0
 ---
 
 Use the admitted command/filesystem boundary. Inspect relevant package defaults,

packages/implementer-investigation/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.7.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "7775acb6525cf134d33321c3f4d79c074903086dc948138ef747af53f88e8ef5"
+      "sha256": "4d2d2d4852652b2766ca3fb5c9d4508e626d15f0d7734a4a4c747f8decbf9b82"
     },
     {
       "path": "investigation.md",

packages/improve-codebase-architecture/SKILL.md

@@ -4,7 +4,7 @@ description: Assess assigned module-deepening opportunities as read-only plannin
 disable-model-invocation: true
 metadata:
   relayview-display-name: Architecture opportunities
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Architecture opportunity assessment

packages/improve-codebase-architecture/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "07b2c9f88207a541c493c85fe7faa6d4b3d04eadbcf7ab592f9e5a4187692ee9"
+      "sha256": "76b396ab9912e96f2181710218182830f80abec9026bed95dd37ec5c263dff55"
     }
   ]
 }

packages/issue-designer-default/SKILL.md

@@ -3,15 +3,15 @@ name: issue-designer-default
 description: Guide ordinary Issue Designer Chats from observed facts to a reviewable draft.
 metadata:
   relayview-display-name: Issue Designer default
-  relayview-version: 0.6.1
+  relayview-version: 0.13.0
 ---
 
 # Issue Designer default
 
 Check current facts before drafting. Read the assigned repository's relevant authoritative documentation, code, tests, and tracker observations; state the source, observation time, and any incomplete read. Keep proposed behavior separate from verified current behavior.
 
-Choose the scale with the Human: one issue for bounded work, an ordered issue set for dependent work, or a narrower question when the outcome is unclear. Ask only for decisions that change scope, acceptance, or authority. A useful draft states the problem, observable outcome, boundaries, prerequisites, and verification including failure behavior. Preserve unresolved choices explicitly.
+Choose the scale with the Operator: one issue for bounded work, an ordered issue set for dependent work, or a narrower question when the outcome is unclear. Ask only for decisions that change scope, acceptance, or authority. A useful draft states the problem, observable outcome, boundaries, prerequisites, and verification including failure behavior. Preserve unresolved choices explicitly.
 
 Use the owner-stored draft for one issue and the ordered set for dependent work. Give each item a complete body, an explicit readiness basis, and the relationships needed to read it independently. Keep known facts and proposed behavior distinct.
 
-At readiness marking, recheck the current issue and comments when an issue exists, cited authoritative documentation, source and tests, and the target and installed environment facts available through assigned tools or attributed Human observations. Record when and how completely each input was observed. Include non-secret retrieval instructions for a test target, host or service setup, and verification when a future agent will need them. If a material input is stale or unavailable, mark the affected item `needs-info` and name its specific unresolved question and available evidence. Propose `ready-for-agent` only when a new Planner can start from the item and its references without this Chat. The Human reviews the exact set and publishes through owner controls.
+At readiness marking, recheck the current issue and comments when an issue exists, cited authoritative documentation, source and tests, and the target and installed environment facts available through assigned tools or attributed Operator observations. Record when and how completely each input was observed. Include non-secret retrieval instructions for a test target, host or service setup, and verification when a future agent will need them. If a material input is stale or unavailable, mark the affected item `needs-info` and name its specific unresolved question and available evidence. Propose `ready-for-agent` only when a new Planner can start from the item and its references without this Chat. The Operator reviews the exact set and publishes through owner controls.

packages/issue-designer-default/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.6.1"
+    "reference": "v0.13.0"
   },
   "role": "designer",
   "step": "design",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "d2d4b743cc9bab550910b95a49f9e7c97805510dcb49d66d7a2f79f9c859bf4f"
+      "sha256": "dde8456e8e6e1bee384f9ec2fbefcbc581cd775213f0e0be23f9e07c4a62b019"
     }
   ]
 }

packages/migrate-to-shoehorn/SKILL.md

@@ -4,7 +4,7 @@ description: Replace suitable TypeScript test assertions with an admitted partia
 disable-model-invocation: true
 metadata:
   relayview-display-name: Migrate to shoehorn
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # TypeScript test fixture migration

packages/migrate-to-shoehorn/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "56b0d3f5ea1cbf8603201d4f5563e6f582561fe58c5679ed428dc7c29d31e461"
+      "sha256": "b94a2ad8f2f611979117a4601f3c0b3852ae37f6df77717828c0a20c17825366"
     }
   ]
 }

packages/planner-communication/SKILL.md

@@ -3,7 +3,7 @@ name: planner-communication
 description: Communication style for the assigned planner; proportional answers, examples, Markdown and natural acknowledgements.
 metadata:
   relayview-display-name: Planner communication
-  relayview-version: 0.11.0
+  relayview-version: 0.13.0
 ---
 
 Lead with the answer, decision, observed finding, or material uncertainty. Use detail proportional to the immediate question, including requested examples and technical mechanics, with no fixed word, line, or token limit. Keep inspection effort independent of conversational length.

packages/planner-communication/relayview-skill.json

@@ -2,7 +2,7 @@
   "schemaVersion": 3,
   "source": {
     "kind": "first-party",
-    "reference": "v0.11.0"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
@@ -10,7 +10,7 @@
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "5dd171cfa744acf74233b1f7de91cfef3baa75a68e57046da01a03c6eacb573d"
+      "sha256": "fe45e08225328bab250475bc966bf480320459320d70a2be6dc07655eda37cc6"
     }
   ]
 }

packages/planner-investigation/SKILL.md

@@ -3,7 +3,7 @@ name: planner-investigation
 description: Investigate source, generated configuration, load order and negative search results within the assigned planner boundary.
 metadata:
   relayview-display-name: Planner investigation
-  relayview-version: 0.7.0
+  relayview-version: 0.13.0
 ---
 
 Use only assigned read roots and the assigned read/search tools. Investigate

packages/planner-investigation/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.7.0"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "e1410558c392100d9557d118a9d82e1068ed7a42142bcfe076f09ceed0dac966"
+      "sha256": "c49e963469978510919a8344bf1d79988f94c2282bae22fa87d8e8b4af3aec34"
     },
     {
       "path": "investigation.md",

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.8.1
+  relayview-version: 0.13.0
 ---
 
 # Planner scope

packages/planner-scope/relayview-skill.json

@@ -2,7 +2,7 @@
   "schemaVersion": 2,
   "source": {
     "kind": "first-party",
-    "reference": "v0.8.1"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
@@ -12,7 +12,7 @@
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "94119fd02a634007f44c227e523802d8f8a7249a97a5526b888d8739401645a2"
+      "sha256": "015651bbb9022025ff71732cb9ff1f6ea087ed143d76fa69091b6273a8fc7db7"
     },
     {
       "path": "scope.md",

packages/pr/SKILL.md

@@ -4,13 +4,13 @@ description: Prepare a reviewable pull-request description for an implemented ca
 disable-model-invocation: true
 metadata:
   relayview-display-name: PR content
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Prepare review content
 
 When the assigned implementation needs a pull-request description, draft text from the current candidate and evidence actually observed. Give the reviewer the behavioral summary, exact candidate revision, focused checks and their outcomes, documentation disposition, material risk, and repeatable manual observations where automation cannot prove behavior. Link to source files or artifacts whose identity you verified.
 
-State failures, limitations, and stale checks plainly. Attribute Human and provider observations to their actual observer; do not present model prose as gate evidence. Keep reviewer commands runnable in the repository's documented shell, with concrete paths or a precise way to discover a missing value.
+State failures, limitations, and stale checks plainly. Attribute Operator and provider observations to their actual observer; do not present model prose as gate evidence. Keep reviewer commands runnable in the repository's documented shell, with concrete paths or a precise way to discover a missing value.
 
 Deliver the draft through the assigned Implementer report or communication path. PR creation, remote comments, review decisions, publication, and merge remain owner-managed operations unless separately authorized by that workflow.

packages/pr/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "86f5c76f96b1f7a4258d21ecd0aeb9ee39cf95fb45eb90e2ee6b172ca460e47a"
+      "sha256": "5d3cab7beb8c9c377126fd0cfb4ec32939ff1d18d8a6962d98143ada1e12e712"
     }
   ]
 }

packages/prototype/SKILL.md

@@ -4,7 +4,7 @@ description: Build a disposable local prototype to answer one implementation que
 disable-model-invocation: true
 metadata:
   relayview-display-name: Prototype
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Bounded implementation prototype

packages/prototype/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "319fe249629788f51b3c8738ded5a1c88336534ad96fa43e7c80a554f09ef586"
+      "sha256": "d59ea525fea7c5bee39f6fc1399f667ea2e7ddb0005932a75619eff42d9e8c9f"
     }
   ]
 }

packages/research-auto/SKILL.md

@@ -3,7 +3,7 @@ name: research-auto
 description: Source selection and reading methods for assigned Planner research.
 metadata:
   relayview-display-name: Research methodology
-  relayview-version: 0.12.2
+  relayview-version: 0.13.0
 ---
 
 # Research methodology

packages/research-auto/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.12.2"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "112036daeb1f760093345805b8c17b1f385723f3597608cf8ad19d72023ccd74"
+      "sha256": "ce259cdd63a1dedbee5d71ba76088a0c18b05c3d6c75ad611157974aa6d8680c"
     }
   ]
 }

packages/research/SKILL.md

@@ -4,7 +4,7 @@ description: Ground assigned planning questions in traceable primary sources usi
 disable-model-invocation: true
 metadata:
   relayview-display-name: Primary-source research
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Primary-source research

packages/research/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "78a832c0bae3d3829afcf78c5cee19a08f0a624e0775b29db5e33c038b725d53"
+      "sha256": "e2ae3d82e67fae872c17cbe91b4d14d6b5b86ff9084db40a170b42be10c46fff"
     }
   ]
 }

packages/reviewer-communication/SKILL.md

@@ -3,7 +3,7 @@ name: reviewer-communication
 description: Communication style for the assigned reviewer; proportional answers, examples, Markdown and natural acknowledgements.
 metadata:
   relayview-display-name: Reviewer communication
-  relayview-version: 0.11.0
+  relayview-version: 0.13.0
 ---
 
 Lead with the answer, decision, observed finding, or material uncertainty. Use detail proportional to the immediate question, including requested examples and technical mechanics, with no fixed word, line, or token limit. Keep inspection effort independent of conversational length.

packages/reviewer-communication/relayview-skill.json

@@ -2,7 +2,7 @@
   "schemaVersion": 3,
   "source": {
     "kind": "first-party",
-    "reference": "v0.11.0"
+    "reference": "v0.13.0"
   },
   "role": "reviewer",
   "step": "review",
@@ -10,7 +10,7 @@
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "d4d94f8987e2db773c3569e77e2db2c0e15fc0365fb1878c80571b268b778fe8"
+      "sha256": "cebbfd13a642195d7419462557f9d6f4cf774c893d8002d3198880e9e33ce6ca"
     }
   ]
 }

packages/reviewer-investigation/SKILL.md

@@ -3,7 +3,7 @@ name: reviewer-investigation
 description: Investigate source, generated configuration, load order and negative search results within the assigned reviewer boundary.
 metadata:
   relayview-display-name: Reviewer investigation
-  relayview-version: 0.7.0
+  relayview-version: 0.13.0
 ---
 
 Use only assigned read roots and the assigned read/search tools. Investigate

packages/reviewer-investigation/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.7.0"
+    "reference": "v0.13.0"
   },
   "role": "reviewer",
   "step": "review",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "f3c6395f3d077ad1a7901cf31ec7656df032292d0181be9dc8a18e36b92769c9"
+      "sha256": "15adb432777f41039cb4f2ca2d1706f380f2a240b37e2651a86a60c2de4fc6e4"
     },
     {
       "path": "investigation.md",

packages/scaffold-exercises/SKILL.md

@@ -4,7 +4,7 @@ description: Build exercise stubs in an assigned course repository using its loc
 disable-model-invocation: true
 metadata:
   relayview-display-name: Scaffold exercises
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Exercise scaffolding

packages/scaffold-exercises/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "a2714d0a09f737b48e8f581f21a5cd7f9ab946e8dca072cfc813ef61c3f1dc18"
+      "sha256": "d6e4353d27064c567bb6e1262a6d84e5f705cb856662bd968d20be18e7906bd7"
     }
   ]
 }

packages/shared-abstraction-refactor/SKILL.md

@@ -4,7 +4,7 @@ description: Find stable repeated patterns in the assigned implementation scope
 disable-model-invocation: true
 metadata:
   relayview-display-name: Shared abstraction refactor
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Shared abstraction refactor

packages/shared-abstraction-refactor/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "a7906eb68c07ac53cf74525ba02984056c78f205fc6815049959c150c0b1a188"
+      "sha256": "f71b1a5720317b5b46eb4d4e4a507dd78662b9a82c36c536a7cabf0236ed6557"
     }
   ]
 }

packages/split-large-files/SKILL.md

@@ -4,7 +4,7 @@ description: Split assigned oversized files along cohesive responsibilities whil
 disable-model-invocation: true
 metadata:
   relayview-display-name: Split large files
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Split large files

packages/split-large-files/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "6cca9cdf43e97778b9ea763d0f7f9faed575583150cdbe88796072c78f8c685b"
+      "sha256": "73f6f38080000eb062b13c62c8ad4d5c68887ec50a5076ca98d91c4e9c4d0c1e"
     }
   ]
 }

packages/tdd-auto/SKILL.md

@@ -3,7 +3,7 @@ name: tdd-auto
 description: Test-driven development for an assigned implementation Plan; use red, green, and focused verification at its agreed test seams.
 metadata:
   relayview-display-name: Test-driven development
-  relayview-version: 0.3.1
+  relayview-version: 0.13.0
 ---
 
 # Test-driven development

packages/tdd-auto/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.1"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "cf4f0cd039dc283caabc3238e3d084c2d59a3f8c8ba030595e9ea80e2b1338e6"
+      "sha256": "83a59bc7631b3295a9c81b86e6134e5027e85dcfbf4be93c92118930a496c01a"
     }
   ]
 }

packages/tdd/SKILL.md

@@ -4,7 +4,7 @@ description: Implement an assigned behavior at the Plan's agreed test seam using
 disable-model-invocation: true
 metadata:
   relayview-display-name: Test-driven development
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Test-driven development

packages/tdd/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "ab633f2670c8d9027301fa985b048ad469b086ed74b1659df8955f2eab9b3a9c"
+      "sha256": "b66d4641c1ec5d9757644b377cfb2dd39fafe6d3bd107f463381eaeaf51d4071"
     }
   ]
 }

packages/to-questionnaire/SKILL.md

@@ -4,11 +4,11 @@ description: Draft questions for an outside expert when the assigned Plan needs
 disable-model-invocation: true
 metadata:
   relayview-display-name: Planning questionnaire
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Planning questionnaire
 
-When the Human explicitly invokes this skill, identify the facts or decisions the assigned Plan cannot resolve from the repository or admitted sources. Ask who can supply the missing knowledge and what decision their answer will support. Draft a concise questionnaire in the Planner conversation for the Human to send through their chosen channel.
+When the Operator explicitly invokes this skill, identify the facts or decisions the assigned Plan cannot resolve from the repository or admitted sources. Ask who can supply the missing knowledge and what decision their answer will support. Draft a concise questionnaire in the Planner conversation for the Operator to send through their chosen channel.
 
-Put the highest-value questions first. Give each question one topic and enough context for an outside recipient to answer without seeing the task history. Include a place to state uncertainty or partial answers. Record the unanswered items as open Plan decisions; incorporate answers only after the Human provides them. Drafting the text neither sends it nor advances the workflow.
+Put the highest-value questions first. Give each question one topic and enough context for an outside recipient to answer without seeing the task history. Include a place to state uncertainty or partial answers. Record the unanswered items as open Plan decisions; incorporate answers only after the Operator provides them. Drafting the text neither sends it nor advances the workflow.

packages/to-questionnaire/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "planner",
   "step": "planning",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "1ccb2b78ffade9faec27b83427a0e3d8fa7f54109b436578f1d79e0ac22d4fe5"
+      "sha256": "20e87aa107dd937c7edc9696aa2681bf54cfb8044efa0f6aa3ebb456af3f3cde"
     }
   ]
 }

packages/writing-for-agents/SKILL.md

@@ -4,7 +4,7 @@ description: Write assigned agent-facing repository guidance with precise trigge
 disable-model-invocation: true
 metadata:
   relayview-display-name: Writing for agents
-  relayview-version: 0.3.0
+  relayview-version: 0.13.0
 ---
 
 # Writing for agents

packages/writing-for-agents/relayview-skill.json

@@ -2,14 +2,14 @@
   "schemaVersion": 1,
   "source": {
     "kind": "first-party",
-    "reference": "v0.3.0"
+    "reference": "v0.13.0"
   },
   "role": "implementer",
   "step": "implementation",
   "files": [
     {
       "path": "SKILL.md",
-      "sha256": "3a2fd1e3253a7373648f333456d1383c161203467ed89526a8129639806f377e"
+      "sha256": "9637378a91621e16219ed455ba5d8c0460c8bd6ffefe299797603dd1896b7c85"
     }
   ]
 }

tests/test_packages.py

@@ -110,7 +110,7 @@ class PackageTests(unittest.TestCase):
                 skill = (package / "SKILL.md").read_text()
                 frontmatter = skill.split("---", 2)[1]
                 self.assertEqual("disable-model-invocation: true" in frontmatter, name in manual)
-                version = {automatic: "0.6.1", "designer-prototype": "0.6.2"}.get(name, "0.6.0")
+                version = "0.13.0"
                 self.assertIn(f"relayview-version: {version}", frontmatter)
                 manifest = json.loads((package / "relayview-skill.json").read_text())
                 self.assertEqual(manifest["source"], {"kind": "first-party", "reference": f"v{version}"})
@@ -122,9 +122,9 @@ class PackageTests(unittest.TestCase):
         frontmatter = skill.split("---", 2)[1]
         self.assertIn("name: tdd-auto", frontmatter)
         self.assertNotIn("disable-model-invocation: true", frontmatter)
-        self.assertIn("relayview-version: 0.3.1", frontmatter)
+        self.assertIn("relayview-version: 0.13.0", frontmatter)
         manifest = json.loads((package / "relayview-skill.json").read_text())
-        self.assertEqual(manifest["source"], {"kind": "first-party", "reference": "v0.3.1"})
+        self.assertEqual(manifest["source"], {"kind": "first-party", "reference": "v0.13.0"})
         check_package(package)
         self.assertIn("disable-model-invocation: true", (ROOT / "packages/tdd/SKILL.md").read_text())
 
@@ -173,7 +173,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.8.1" if name == "planner-scope" else "v0.9.0"})
+                self.assertEqual(manifest["source"], {"kind": "first-party", "reference": "v0.13.0"})
                 self.assertIn(resource, [item["path"] for item in manifest["files"]])
                 self.assertIn(marker, (package / "SKILL.md").read_text() + (package / resource).read_text())