Implement opsx-render Command

To sync spec.md and tasks.md with TD task management state, run the opsx-render command to automatically render OpenSpec artifacts from current TD data. This updates documentation to reflect live project status, preserving requirement IDs and task statuses.

OpenSpec artifact rendering generates spec.md and tasks.md files from current TD task management data. This process synchronizes filesystem documentation with live TD state, ensuring accurate requirement traceability and task status updates across project files.

Opsx-render preserves task IDs during synchronization by validating and maintaining requirement identifiers across spec.md, tasks.md, and TD state. This ensures traceability is maintained while updating task statuses and rendering current project documentation.

Yes, opsx-render supports atomic writes to ensure data integrity when rendering spec.md and tasks.md files. This prevents partial file updates during synchronization with TD state, protecting documentation accuracy during automated rendering operations.

You need to render OpenSpec documents when TD task statuses change and spec.md or tasks.md files must reflect current progress. Running opsx-render after TD updates ensures documentation accurately mirrors live project state, requirements, and completion status.

Yes, opsx-render automates GitOps documentation sync by rendering spec.md and tasks.md directly from TD state. This eliminates manual file updates, ensuring filesystem documentation stays synchronized with TD task management data automatically.