fix: clarify verifier is one-per-team not one-per-executor

definitions/create-expert/perstack.toml

@@ -15,7 +15,7 @@
 
 [experts."create-expert"]
 defaultModelTier = "high"
-version = "1.0.11"
+version = "1.0.12"
 description = "Creates and modifies Perstack expert definitions in perstack.toml"
 instruction = """
 You are the coordinator for creating and modifying Perstack expert definitions. perstack.toml is the single source of truth — your job is to produce or modify it according to the user's request.
@@ -60,7 +60,7 @@ pick = ["readTextFile", "exec", "attemptCompletion"]
 
 [experts."@create-expert/plan"]
 defaultModelTier = "high"
-version = "1.0.11"
+version = "1.0.12"
 description = """
 Analyzes the user's request and produces plan.md: domain constraints, test queries, verification methods, and role architecture.
 Provide: (1) what the expert should do, (2) path to existing perstack.toml if one exists.
@@ -99,7 +99,7 @@ For each test query:
 Conditions derived from domain constraints that mean the work must be rejected. These are not the inverse of success criteria — they are hard reject rules that come from deeply understanding the domain. For each failure condition: what specifically is wrong, which expert's work caused it, and where to restart. Example: if the user requires "pure game logic with no I/O," then engine code containing console.log is a failure condition that requires redoing the engine expert's work.
 
 ### Architecture
-Delegation tree with role assignments. Every expert that produces artifacts needs a separate verifier expert that builds, runs, and executes the output to confirm it works — the person who did the work is not the person who signs off on it. For each expert: name, one-line purpose, executor or verifier.
+Delegation tree with role assignments. Include one verifier expert that independently tests the final output by building, running, and executing it — the person who did the work is not the person who signs off on it. The verifier is a single expert with exec capability, not one-per-executor. For each expert: name, one-line purpose, executor or verifier.
 
 After writing plan.md, attemptCompletion with the file path.
 """
@@ -124,7 +124,7 @@ pick = [
 
 [experts."@create-expert/build"]
 defaultModelTier = "low"
-version = "1.0.11"
+version = "1.0.12"
 description = """
 Orchestrates the write → test → verify → improve cycle for perstack.toml.
 Provide: path to plan.md (containing requirements, architecture, test queries, and success criteria).
@@ -186,7 +186,7 @@ pick = ["readTextFile", "exec", "todo", "attemptCompletion"]
 
 [experts."@create-expert/write-definition"]
 defaultModelTier = "low"
-version = "1.0.11"
+version = "1.0.12"
 description = """
 Writes or modifies a perstack.toml definition from plan.md requirements and architecture.
 Provide: (1) path to plan.md, (2) optionally path to existing perstack.toml to preserve, (3) optionally feedback from a failed test to address.
@@ -296,7 +296,7 @@ pick = [
 
 [experts."@create-expert/verify-test"]
 defaultModelTier = "low"
-version = "1.0.11"
+version = "1.0.12"
 description = """
 Verifies test-expert results by inspecting produced artifacts, executing them, and reviewing the definition against plan.md.
 Provide: (1) the test-expert's factual report (query, what was produced, errors), (2) the success criteria from plan.md, (3) path to plan.md (for semantic review of instructions), (4) path to perstack.toml.
@@ -357,7 +357,7 @@ pick = ["readTextFile", "exec", "todo", "attemptCompletion"]
 
 [experts."@create-expert/test-expert"]
 defaultModelTier = "low"
-version = "1.0.11"
+version = "1.0.12"
 description = """
 Executes a single test query against a Perstack expert definition and reports what happened.
 Provide: (1) path to perstack.toml, (2) the test query to execute, (3) the coordinator expert name to test.