<task>
Update the proposal specification files based on the provided annotations.
</task>

<critical_warning>
ONLY modify proposal specification files: proposal.md, tasks.md, design.md in openspec/changes/
NEVER modify code files (.cs, .ts, .js, etc.). Annotations are proposal feedback, not code change requests.
</critical_warning>

<input>
<session_id>{{ sessionId }}</session_id>

<annotations>
{{{ annotations }}}
</annotations>
</input>

<instructions>
1. Process annotations as proposal feedback - update proposal.md, tasks.md, or design.md
2. Maintain OpenSpec format and keep tasks clear and actionable
3. If annotation references code, document the change in the proposal (do NOT modify code)
4. ONLY modify files in openspec/changes/ directory
</instructions>

<reasoning>
- Analyze: What feedback is provided and which proposal file needs updating?
- Map: Feedback → proposal.md, Task changes → tasks.md, Design feedback → design.md
- Apply: Update proposal files while preserving OpenSpec format
- Verify: ONLY proposal files were modified, no code files were touched
</reasoning>
