| name | run-dev-graph-sync |
| description | tracker_binding に従い dev-graph と Beads を同期したいとき、GitHub Issues/Projects/PR lifecycle を冪等収束したいときに使う。 |
| version | 0.1.0 |
| owner | harness maintainers |
| source | plugin-plans/dev-graph/component-inventory.json#C03 |
| kind | run |
| prefix | run |
| hierarchy | L1 |
| user-invocable | true |
| argument-hint | [--repo-root PATH] [--dry-run] [--resolve-conflicts PATH] |
| allowed-tools | ["Read","Write","Edit","Bash","AskUserQuestion","Skill","Agent"] |
| script_refs | ["../../scripts/resolve-repo-context.py","../../scripts/validate-graph-schema.py","../../scripts/gh-bridge.py","../../scripts/bd-bridge.py","../../scripts/reconcile-github-lifecycle.py","../../scripts/manage-worktree-lease.py"] |
| schema_refs | ["../../schemas/graph-node.schema.json","../../schemas/repo-config.schema.json"] |
| reference_refs | ["../../references/execution-tracker-contract.md","../../references/github-lifecycle-contract.md"] |
| responsibility_refs | ["prompts/R1-elicit.md","prompts/R2-plan.md","prompts/R3-sync.md","prompts/R4-tombstone.md","prompts/R5-dryrun.md","prompts/R6-confirm.md","prompts/R7-lifecycle.md","prompts/R8-scheduled.md"] |
| responsibilities | [{"id":"R1-elicit","name":"elicit","prompt_required":true,"summary":"repo-local configのissue repository、複数Projects target alias/owner/project number、default/auto-add policy、field name/type/option mappingを読み、GitHub node IDは実行時解決する"},{"id":"R2-plan","name":"plan","prompt_required":true,"summary":"Issueはid+updated_at、Projects custom fieldsはfield value updatedAtを競合hint、last-synced snapshotを削除/renameを含むcanonical baseとする3-way diffで同期計画を作る。Statusはlocal_to_project固定でremote変更を完了authorityにしない"},{"id":"R3-sync","name":"sync","prompt_required":true,"summary":"tracker_binding=githubだけをC12経由でIssue/Projects更新し、tracker_binding=beadsはC28でstatus・depends_on edge exact-setを突合する。Beads GitHub mirrorはbd github sync --push-onlyだけを使いC12 mutationを禁止する"},{"id":"R4-tombstone","name":"tombstone","prompt_required":true,"summary":"GitHub Issue の close/delete を検知し、C02 経由でローカルグラフノードを物理削除せず tombstone/status 遷移 (open→closed 等) として双方向伝播する"},{"id":"R5-dryrun","name":"dryrun","prompt_required":true,"summary":"--dry-run時はIssue作成/更新/close、Project item-add/item-editを一切実行せず、project alias・field別の反映予定差分だけを提示する"},{"id":"R6-confirm","name":"confirm","prompt_required":true,"summary":"id+updated_at 同時競合で立てた手動確認フラグを次回同期の入力として読み取り、利用者の確認結果を反映した上で当該ノードのフラグを解消する"},{"id":"R7-lifecycle","name":"lifecycle","prompt_required":true,"summary":"C26でlinked PRのmerged/default-branch/closing-reference evidenceとC27 pending worktree eventをreconcileし、cleanなdefault branch worktreeだけでtask status/completion_evidence/execution_contextsをatomic更新する"},{"id":"R8-scheduled","name":"scheduled","prompt_required":true,"summary":"configのinterval/owner/entry_pointとlast-reconciled時刻を読み、owner=claude_session_startならC25 SessionStart、owner=host_schedulerなら明示host invocationから同じC26 entry pointを冪等起動する"}] |
| combinators | ["with-goal-seek","with-feedback-contract"] |
| goal_seek | {"engine":"inline","fork":"subagent","max_loops":5} |
| completeness_exempt | ["manifest: goal_seek.engine=inline が未達 checklist から実行局面を都度選ぶため、固定 phase の workflow-manifest.json は適用外。停止条件と配線は本文 ## ゴールシーク実行を正本とする。"] |
| feedback_contract | {"max_iterations":3,"criteria":[{"id":"IN1","loop_scope":"inner","text":"validate-graph-schema.py と gh-bridge.py で同期ペイロードを送信前検証し取込/反映の必須キー欠落が 0 件","verify_by":"script"},{"id":"OUT1","loop_scope":"outer","text":"同一状態を二回同期し 2 回目のGitHubからの取込/ローカルからの反映が 0 件になることを受入テストが確認する","verify_by":"live-trial"},{"id":"OUT2","loop_scope":"outer","text":"id+updated_at が同時競合するケースを注入した際、規定のタイブレーク規則 (更新が新しい方を採用・同時刻はGitHub優先+ローカル手動確認フラグ) どおりに競合解決されることを受入テストが確認する","verify_by":"test"},{"id":"OUT3","loop_scope":"outer","text":"GitHub Issue が close/delete された場合、次回同期でローカルノードが物理削除されず tombstone/status 遷移 (open→closed 等) として双方向伝播されることを受入テストが確認する","verify_by":"test"},{"id":"OUT4","loop_scope":"outer","text":"--dry-run 指定時に GitHub 側への書込みが 0 件のまま反映予定差分のみがプレビューされることを受入テストが確認する (暴発防止)","verify_by":"test"},{"id":"OUT5","loop_scope":"outer","text":"手動確認フラグが立ったノードについて、確認結果を反映した後の再同期でフラグが解消されることを受入テストが確認する","verify_by":"test"},{"id":"OUT6","loop_scope":"outer","text":"同一Issue contentを同一Projectへ二回同期してもProject itemが重複せずitem_idが安定し、複数Project targetにはaliasごとに1 itemだけがlinkされる","verify_by":"test"},{"id":"OUT7","loop_scope":"outer","text":"Projects fieldのlocal/remote双方変更を3-way fixtureで検出して自動上書き0件・manual conflict 1件となり、片側変更だけはmappingどおり同期されsnapshotが更新される","verify_by":"test"},{"id":"OUT8","loop_scope":"outer","text":"permission/rate-limit/field削除/option rename/pagination/途中失敗fixtureでローカルtask promotionを維持し、未完了Project writeだけpending_retryとして再実行できる","verify_by":"test"},{"id":"OUT9","loop_scope":"outer","text":"PR closed未mergeではdone 0件、default branchへmergedかつpolicy充足時だけdoneとなり、feature worktreeではpending event、clean default worktreeでのみdurable task spec/graphが更新される","verify_by":"test"}]} |
