sync-github-task

Purpose

One-way sync of a local technical task markdown file to GitHub Issues. Auto-detects create vs update from github_issue in frontmatter.

`github_issue` present?	Action
Absent / null	Pre-flight dedup search by title, then Create (no parent linkage; milestone resolved from frontmatter / epic lookup (see `ensure-task-github-issue` Step T3) / standalone default) if no match. Writes `github_issue` back to file.
Present	Update existing GitHub issue (title, body, labels, milestone), reconcile open/closed state with frontmatter `status`. A Change Log row is written only if the status transitioned.

Difference from sync-github-story: tasks are standalone — no parent epic issue lookup, no sub-issue linking. Milestone is the only relationship to a higher-level work item, mirroring sync-jira-task's "no jira_epic" stance.

When to Use

"Create this task in GitHub"
"Sync / push / update this task to GitHub"
"I've edited the task, push changes to GitHub"
"Publish this task file to GitHub"