coordinator-task-status-renderer

To keep OpenSpec tasks.md in sync with coordinator issue state, you can run a rendering script that reads labeled issues and rewrites the managed GENERATED block in openspec/changes/<change-id>/tasks.md automatically.

Yes, you can seed coordinator tasks from manually authored markdown by parsing human-authored task lines and dependencies, then creating idempotent coordinator issues labeled with change and task keys.

When the coordinator is unreachable during OpenSpec task rendering, the script handles timeouts via a persisted stale marker in sidecar state to maintain fail-safe behavior without crashing the documentation workflow.

Yes, you need a valid change-id format to render OpenSpec task status blocks. The script validates the change-id format and includes safety guards to prevent path traversal during file access.

The coordinator task status renderer prevents duplicate issue creation through fail-safe idempotency, refusing to seed new issues when the coordinator response is truncated and ensuring issues are only created once per task key.

Your OpenSpec tasks.md generated block shows stale task status when the coordination_bridge reports timeouts or unreachability, triggering a persisted stale marker that preserves existing data until the connection is restored.