docs: Clarify Workflow Specification is still required in SDS (v0.7.3)

Important clarification for v0.7.3:
- Specification Operations ≠ Workflow Specification
- Even if Operations empty, Workflow Specification REQUIRED
- Workflow describes user journey (v0.7.0)
- Operations describe API interfaces (optional)

This prevents confusion that v0.7.3 removed ALL operations from SDS.

Author: NeilJo-GY

CHANGELOG.md

@@ -81,6 +81,29 @@ Operations:
 
 **Key principle**: Most domains don't need Specification Operations. This is specifically for API/Protocol specifications.
 
+### ⚠️ Important Clarification
+
+**This fix is ONLY about "Specification Operations"**. Domain Specs still MUST include:
+
+✅ **Workflow Specification** (v0.7.0 requirement):
+```yaml
+user_workflows:
+  - name: Marketing Workflow
+    phases:
+      - Discover: Research market needs
+      - Strategy: Plan campaigns
+      - Design: Create content
+      - Execute: Launch campaigns
+      - Analyze: Measure results
+```
+
+This describes **how users use the specification**, not API interfaces or toolkit commands.
+
+**Summary**:
+- ✅ **Keep**: Workflow Specification (describes user workflow)
+- ⚠️ **Conditional**: Specification Operations (only for API specs)
+- ❌ **Remove**: Toolkit Commands (belongs in SDD)
+
 ### Impact
 
 **Before this fix**:

src/metaspec/templates/meta/sds/commands/specify.md.j2

@@ -193,12 +193,19 @@ ls specs/domain/ | grep -E '^[0-9]{3}-' | sort -n
    **Key distinction**:
    - **Specification Operations** (SDS) = Interfaces the specification defines (e.g., API endpoints)
    - **Toolkit Commands** (SDD) = Commands your toolkit provides (e.g., `/domainspec.discover`)
+   - **Workflow Specification** (SDS) = How users use the specification (REQUIRED, see v0.7.0)
    - These are completely different! Most domains don't need Specification Operations.
+   
+   **⚠️ Don't confuse**:
+   - Specification Operations ≠ Workflow Specification
+   - Even if you leave Operations empty, you MUST still define Workflow Specification
+   - Workflow describes user journey, Operations describe API interfaces
 
 **Important Notes**:
 - This is SDS (Spec-Driven Specification) - focus on specification definition only
 - Do NOT include implementation details (Parser, Validator, CLI)
 - Do NOT define toolkit commands here - use `/metaspec.sdd.specify` for that
+- You MUST define Workflow Specification (see v0.7.0 Workflow Completeness principle)
 - For toolkit development, use `/metaspec.sdd.specify` instead
 
 **If user input is vague**, make informed guesses based on domain standards and document assumptions.