fix: compose script paths, add {SCRIPT} placeholder, trim tags and description

- Fix compose command script paths: ../../scripts/ -> ../scripts/
- Add {SCRIPT} invocation to compose command Execution section
- Trim tags from 9 to 5: evaluator, evidence, provenance, quality, governance
- Shorten description from 177 to 113 chars per publishing guide

Assisted-by: GitHub Copilot (model: deepseek-v4-pro, autonomous)

Author: tbitcs

commands/speckit.evaluator.compose.md

@@ -1,9 +1,9 @@
 ---
 description: "Compose multiple evaluator results at a lifecycle point with deterministic precedence"
 scripts:
-  sh: ../../scripts/bash/compose-results.sh
-  ps: ../../scripts/powershell/compose-results.ps1
-  py: ../../scripts/python/compose_results.py
+  sh: ../scripts/bash/compose-results.sh
+  ps: ../scripts/powershell/compose-results.ps1
+  py: ../scripts/python/compose_results.py
 ---
 
 # Evaluator Compose
@@ -32,6 +32,14 @@ The user input specifies **which results to compose**. Accept:
 
 ## Execution
 
+Run `{SCRIPT}` with the appropriate arguments to compose the results:
+
+```bash
+{SCRIPT} --results-dir .specify/extensions/evaluator/results/ --phase <phase> [--strategy strict|majority|optimistic] [--output <path>]
+```
+
+The script performs the steps below. Use these rules as reference for interpreting the output.
+
 ### 1. Collect Results
 
 Read all result files for the specified phase from `.specify/extensions/evaluator/results/`. Filter to files matching the pattern `<evaluator-id>-<phase>-<timestamp>.json`.