Add Wave general-purpose pipelines

ADR, changelog, code-review, debug, doc-sync, explain, feature,
hotfix, improve, onboard, plan, prototype, refactor, security-scan,
smoke-test, speckit-flow, supervise, test-gen, and more.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>

.wave/pipelines/hotfix.yaml

@@ -0,0 +1,88 @@
+kind: WavePipeline
+metadata:
+  name: hotfix
+  description: "Quick investigation and fix for production issues"
+
+input:
+  source: cli
+  example: "fix panic in pipeline executor when step has nil context"
+
+steps:
+  - id: investigate
+    persona: navigator
+    workspace:
+      mount:
+        - source: ./
+          target: /project
+          mode: readonly
+    exec:
+      type: prompt
+      source: |
+        Investigate this production issue: {{ input }}
+
+        1. Search for related code paths
+        2. Check recent commits that may have introduced the bug
+        3. Identify the root cause
+        4. Assess blast radius (what else could be affected)
+    output_artifacts:
+      - name: findings
+        path: .wave/output/findings.json
+        type: json
+    handover:
+      contract:
+        type: json_schema
+        source: .wave/output/findings.json
+        schema_path: .wave/contracts/findings.schema.json
+        on_failure: retry
+        max_retries: 2
+
+  - id: fix
+    persona: craftsman
+    dependencies: [investigate]
+    memory:
+      inject_artifacts:
+        - step: investigate
+          artifact: findings
+          as: investigation
+    workspace:
+      mount:
+        - source: ./
+          target: /project
+          mode: readwrite
+    exec:
+      type: prompt
+      source: |
+        Fix the production issue based on the investigation findings.
+
+        Requirements:
+        1. Apply the minimal fix - don't refactor surrounding code
+        2. Add a regression test that would have caught this bug
+        3. Ensure all existing tests still pass
+        4. Document the fix in a commit-ready message
+    handover:
+      contract:
+        type: test_suite
+        command: "{{ project.test_command }}"
+
+        must_pass: true
+        on_failure: retry
+        max_retries: 3
+
+  - id: verify
+    persona: auditor
+    dependencies: [fix]
+    exec:
+      type: prompt
+      source: |
+        Verify the hotfix:
+
+        1. Is the fix minimal and focused? (no unrelated changes)
+        2. Does the regression test actually test the reported issue?
+        3. Are there other code paths with the same vulnerability?
+        4. Is the fix safe for production deployment?
+
+        Output a go/no-go recommendation with reasoning.
+    output_artifacts:
+      - name: verdict
+        path: .wave/output/verdict.md
+        type: markdown