fix: remove coding-specific vocabulary from Hard Signal Framework descriptions

Replace "exit codes, test results, grep matches" and similar coding-centric
examples with domain-neutral language per Design Principle 3 (Domain
Agnosticism). create-expert serves all domains, not just software development.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>

Author: FL4TLiN3

definitions/create-expert/perstack.toml

@@ -14,8 +14,8 @@
 #
 # 1. Hard Signal Verification
 #    - Verification loop must be driven by hard signals — checks whose
-#      results do not depend on LLM judgment. Exit codes, test results,
-#      grep matches, deterministic command output.
+#      results do not depend on LLM judgment. Any command that produces
+#      deterministic, binary output qualifies.
 #    - Hard signal = Ground truth × Context separation × Determinism.
 #      All three required; missing any one degrades to soft signal (noise).
 #    - Ground truth: verify the final artifact itself, not a proxy.
@@ -164,7 +164,7 @@ One comprehensive, realistic query that exercises the expert's full capability.
 ### Verification Signals
 Hard signals for the test query — verification checks whose results do not depend on LLM judgment:
 - The exact command to run (deterministic, repeatable)
-- The expected result (exit code, output pattern, file existence)
+- The expected result (specific output, presence/absence of content, numeric threshold)
 - Why this checks ground truth, not a proxy
 
 Include both positive signals (artifact works correctly) and reject signals (domain-specific anti-patterns are absent). Reject signals are not the inverse of positive signals — they detect fundamental failures derived from deeply understanding the domain.
@@ -394,7 +394,7 @@ All three steps below are MANDATORY. Skipping any step is grounds for an invalid
 
 Run every hard signal check defined in plan.md's Verification Signals:
 - Execute the exact command specified
-- Compare the result against the expected output (exit code, pattern match, file existence)
+- Compare the result against the expected output (specific output, presence/absence of content, numeric threshold)
 - Record per check: command run, expected result, actual result, PASS/FAIL
 
 If a check has no deterministic expected output, flag it as an invalid signal and CONTINUE — the plan must define a proper hard signal.