update-oo-component-documentation

Update the existing documentation file at: ${file} by analyzing the corresponding component code. Extract the component path from the existing documentation's front matter ( component_path field) or infer it from the documentation content. Analyze the current component implementation and update the documentation accordingly. Documentation Standards: Analysis Instructions: Language-Specific Optimizations: Update Strategy: Error Handling: Output Format: Update the existing Markdown file maintaining its structure while refreshing content to match current implementation. Preserve formatting, heading hierarchy, and existing organizational decisions. Required Documentation Structure: Update the existing documentation following the same template structure, ensuring all sections reflect current implementation: - DOC-001: Follow C4 Model documentation levels (Context, Containers, Components, Code) - DOC-002: Align with Arc42 software architecture documentation template - DOC-003: Comply with IEEE 1016 Software Design Description standard - DOC-004: Use Agile Documentation principles (just enough documentation that adds value) - DOC-005: Target developers and maintainers as primary audience - ANA-001: Read existing documentation to understand component context and structure - ANA-002: Identify component path from front matter or content analysis - ANA-003: Examine current source code...