Operations Integration (260628): inspect-diff-converse cockpit, task_reopen, provider caps — MCP 3.0.0rc1

.agents/skills/c-04-retrieval-strategy-router/codegraphcontext-high-level-methods.md

@@ -34,7 +34,7 @@ and complexity signals.
 | Where is this symbol? | `cgc_symbol_search` | `find name <name>` |
 | What does this function/method call? | `cgc_callees` | `analyze calls <function>` |
 | Who calls this function/method? | `cgc_callers` | `analyze callers <function>` |
-| Which files import this module string? | `cgc_dependencies` | `analyze dependencies <module>` |
+| Which files import this module string? | `cgc_dependencies` | `analyze deps <module>` |
 | Which functions are most complex? | `cgc_complexity` | `analyze complexity [function]` |
 | Do I need the interactive graph view? | `cgc_visualize` | `visualize` |
 

.agents/skills/c-09-git-worktree-manager/SKILL.md

@@ -30,6 +30,7 @@ worktree_closeout_preview(contract_path="<enclosure series-contract.md>", code_c
 worktree_closeout_apply(contract_path="<enclosure series-contract.md>", intent_note="<developer intent>", code_commit_message="<message>", memory_commit_message="<message>", ledger_commit_message="<message>")
 worktree_integrate(contract_path="<enclosure series-contract.md>", strategy="ff-only")
 worktree_cleanup(contract_path="<enclosure series-contract.md>")
+task_reopen(contract_path="<enclosure series-contract.md>", dry_run=true)
 lifecycle_finalize_task(contract_path="<enclosure series-contract.md>", task_doc_path="<task.json>", master_doc_path="<parent task.json>", subtask_number="<N>", dry_run=true)
 ```
 
@@ -254,6 +255,20 @@ edge is finalized separately.
 
 Cleanup is idempotent. If the worktrees or merged branches are already gone, it reports the already-clean state instead of failing. If Git refuses to delete an unmerged branch, cleanup leaves that branch in place and reports it for developer review.
 
+## Reopening A Completed Leaf
+
+Reopening reuses the EXACT same leaf id — never mint a suffixed leaf (`…-r1`).
+`task_reopen(contract_path=…)` is a state reset, not a worktree creator: it refuses
+anything but a fully landed leaf (closeout, integration, and cleanup completed, worktrees
+gone), then resets the contract's review/closeout/integration state, clears the stale
+lifecycle binding, marks `cleanup: reopened`, and puts the leaf's task document back to
+`planning` (master index entry flipped, audit decision appended). Preview with
+`dry_run=true` first. Afterwards: edit the doc's steps via `task_doc` (add, change, or
+untick work), then run a NORMAL `worktree_start` with the same leaf id — it recreates the
+worktrees off the current source tips, promotes/mints a fresh lifecycle, and restamps the
+doc's `lifecycleId`, so doc, chat, and dashboard bindings hold by construction. Implementation
+then proceeds as usual, including closeout → integrate → finalize.
+
 ## Boundaries
 
 1. The `c-09-git-worktree-manager` skill may create or reuse worktrees, root series contracts, and leaf enclosure contracts.

.claude/skills/c-04-retrieval-strategy-router/codegraphcontext-high-level-methods.md

@@ -34,7 +34,7 @@ and complexity signals.
 | Where is this symbol? | `cgc_symbol_search` | `find name <name>` |
 | What does this function/method call? | `cgc_callees` | `analyze calls <function>` |
 | Who calls this function/method? | `cgc_callers` | `analyze callers <function>` |
-| Which files import this module string? | `cgc_dependencies` | `analyze dependencies <module>` |
+| Which files import this module string? | `cgc_dependencies` | `analyze deps <module>` |
 | Which functions are most complex? | `cgc_complexity` | `analyze complexity [function]` |
 | Do I need the interactive graph view? | `cgc_visualize` | `visualize` |
 

.claude/skills/c-09-git-worktree-manager/SKILL.md

@@ -30,6 +30,7 @@ worktree_closeout_preview(contract_path="<enclosure series-contract.md>", code_c
 worktree_closeout_apply(contract_path="<enclosure series-contract.md>", intent_note="<developer intent>", code_commit_message="<message>", memory_commit_message="<message>", ledger_commit_message="<message>")
 worktree_integrate(contract_path="<enclosure series-contract.md>", strategy="ff-only")
 worktree_cleanup(contract_path="<enclosure series-contract.md>")
+task_reopen(contract_path="<enclosure series-contract.md>", dry_run=true)
 lifecycle_finalize_task(contract_path="<enclosure series-contract.md>", task_doc_path="<task.json>", master_doc_path="<parent task.json>", subtask_number="<N>", dry_run=true)
 ```
 
@@ -254,6 +255,20 @@ edge is finalized separately.
 
 Cleanup is idempotent. If the worktrees or merged branches are already gone, it reports the already-clean state instead of failing. If Git refuses to delete an unmerged branch, cleanup leaves that branch in place and reports it for developer review.
 
+## Reopening A Completed Leaf
+
+Reopening reuses the EXACT same leaf id — never mint a suffixed leaf (`…-r1`).
+`task_reopen(contract_path=…)` is a state reset, not a worktree creator: it refuses
+anything but a fully landed leaf (closeout, integration, and cleanup completed, worktrees
+gone), then resets the contract's review/closeout/integration state, clears the stale
+lifecycle binding, marks `cleanup: reopened`, and puts the leaf's task document back to
+`planning` (master index entry flipped, audit decision appended). Preview with
+`dry_run=true` first. Afterwards: edit the doc's steps via `task_doc` (add, change, or
+untick work), then run a NORMAL `worktree_start` with the same leaf id — it recreates the
+worktrees off the current source tips, promotes/mints a fresh lifecycle, and restamps the
+doc's `lifecycleId`, so doc, chat, and dashboard bindings hold by construction. Implementation
+then proceeds as usual, including closeout → integrate → finalize.
+
 ## Boundaries
 
 1. The `c-09-git-worktree-manager` skill may create or reuse worktrees, root series contracts, and leaf enclosure contracts.

.codex/skills/c-04-retrieval-strategy-router/codegraphcontext-high-level-methods.md

@@ -34,7 +34,7 @@ and complexity signals.
 | Where is this symbol? | `cgc_symbol_search` | `find name <name>` |
 | What does this function/method call? | `cgc_callees` | `analyze calls <function>` |
 | Who calls this function/method? | `cgc_callers` | `analyze callers <function>` |
-| Which files import this module string? | `cgc_dependencies` | `analyze dependencies <module>` |
+| Which files import this module string? | `cgc_dependencies` | `analyze deps <module>` |
 | Which functions are most complex? | `cgc_complexity` | `analyze complexity [function]` |
 | Do I need the interactive graph view? | `cgc_visualize` | `visualize` |
 

.codex/skills/c-09-git-worktree-manager/SKILL.md

@@ -30,6 +30,7 @@ worktree_closeout_preview(contract_path="<enclosure series-contract.md>", code_c
 worktree_closeout_apply(contract_path="<enclosure series-contract.md>", intent_note="<developer intent>", code_commit_message="<message>", memory_commit_message="<message>", ledger_commit_message="<message>")
 worktree_integrate(contract_path="<enclosure series-contract.md>", strategy="ff-only")
 worktree_cleanup(contract_path="<enclosure series-contract.md>")
+task_reopen(contract_path="<enclosure series-contract.md>", dry_run=true)
 lifecycle_finalize_task(contract_path="<enclosure series-contract.md>", task_doc_path="<task.json>", master_doc_path="<parent task.json>", subtask_number="<N>", dry_run=true)
 ```
 
@@ -254,6 +255,20 @@ edge is finalized separately.
 
 Cleanup is idempotent. If the worktrees or merged branches are already gone, it reports the already-clean state instead of failing. If Git refuses to delete an unmerged branch, cleanup leaves that branch in place and reports it for developer review.
 
+## Reopening A Completed Leaf
+
+Reopening reuses the EXACT same leaf id — never mint a suffixed leaf (`…-r1`).
+`task_reopen(contract_path=…)` is a state reset, not a worktree creator: it refuses
+anything but a fully landed leaf (closeout, integration, and cleanup completed, worktrees
+gone), then resets the contract's review/closeout/integration state, clears the stale
+lifecycle binding, marks `cleanup: reopened`, and puts the leaf's task document back to
+`planning` (master index entry flipped, audit decision appended). Preview with
+`dry_run=true` first. Afterwards: edit the doc's steps via `task_doc` (add, change, or
+untick work), then run a NORMAL `worktree_start` with the same leaf id — it recreates the
+worktrees off the current source tips, promotes/mints a fresh lifecycle, and restamps the
+doc's `lifecycleId`, so doc, chat, and dashboard bindings hold by construction. Implementation
+then proceeds as usual, including closeout → integrate → finalize.
+
 ## Boundaries
 
 1. The `c-09-git-worktree-manager` skill may create or reuse worktrees, root series contracts, and leaf enclosure contracts.

.cursor/skills/c-04-retrieval-strategy-router/codegraphcontext-high-level-methods.md

@@ -34,7 +34,7 @@ and complexity signals.
 | Where is this symbol? | `cgc_symbol_search` | `find name <name>` |
 | What does this function/method call? | `cgc_callees` | `analyze calls <function>` |
 | Who calls this function/method? | `cgc_callers` | `analyze callers <function>` |
-| Which files import this module string? | `cgc_dependencies` | `analyze dependencies <module>` |
+| Which files import this module string? | `cgc_dependencies` | `analyze deps <module>` |
 | Which functions are most complex? | `cgc_complexity` | `analyze complexity [function]` |
 | Do I need the interactive graph view? | `cgc_visualize` | `visualize` |
 

.cursor/skills/c-09-git-worktree-manager/SKILL.md

@@ -30,6 +30,7 @@ worktree_closeout_preview(contract_path="<enclosure series-contract.md>", code_c
 worktree_closeout_apply(contract_path="<enclosure series-contract.md>", intent_note="<developer intent>", code_commit_message="<message>", memory_commit_message="<message>", ledger_commit_message="<message>")
 worktree_integrate(contract_path="<enclosure series-contract.md>", strategy="ff-only")
 worktree_cleanup(contract_path="<enclosure series-contract.md>")
+task_reopen(contract_path="<enclosure series-contract.md>", dry_run=true)
 lifecycle_finalize_task(contract_path="<enclosure series-contract.md>", task_doc_path="<task.json>", master_doc_path="<parent task.json>", subtask_number="<N>", dry_run=true)
 ```
 
@@ -254,6 +255,20 @@ edge is finalized separately.
 
 Cleanup is idempotent. If the worktrees or merged branches are already gone, it reports the already-clean state instead of failing. If Git refuses to delete an unmerged branch, cleanup leaves that branch in place and reports it for developer review.
 
+## Reopening A Completed Leaf
+
+Reopening reuses the EXACT same leaf id — never mint a suffixed leaf (`…-r1`).
+`task_reopen(contract_path=…)` is a state reset, not a worktree creator: it refuses
+anything but a fully landed leaf (closeout, integration, and cleanup completed, worktrees
+gone), then resets the contract's review/closeout/integration state, clears the stale
+lifecycle binding, marks `cleanup: reopened`, and puts the leaf's task document back to
+`planning` (master index entry flipped, audit decision appended). Preview with
+`dry_run=true` first. Afterwards: edit the doc's steps via `task_doc` (add, change, or
+untick work), then run a NORMAL `worktree_start` with the same leaf id — it recreates the
+worktrees off the current source tips, promotes/mints a fresh lifecycle, and restamps the
+doc's `lifecycleId`, so doc, chat, and dashboard bindings hold by construction. Implementation
+then proceeds as usual, including closeout → integrate → finalize.
+
 ## Boundaries
 
 1. The `c-09-git-worktree-manager` skill may create or reuse worktrees, root series contracts, and leaf enclosure contracts.

.github-vscode/skills/c-04-retrieval-strategy-router/codegraphcontext-high-level-methods.md

@@ -34,7 +34,7 @@ and complexity signals.
 | Where is this symbol? | `cgc_symbol_search` | `find name <name>` |
 | What does this function/method call? | `cgc_callees` | `analyze calls <function>` |
 | Who calls this function/method? | `cgc_callers` | `analyze callers <function>` |
-| Which files import this module string? | `cgc_dependencies` | `analyze dependencies <module>` |
+| Which files import this module string? | `cgc_dependencies` | `analyze deps <module>` |
 | Which functions are most complex? | `cgc_complexity` | `analyze complexity [function]` |
 | Do I need the interactive graph view? | `cgc_visualize` | `visualize` |
 

.github-vscode/skills/c-09-git-worktree-manager/SKILL.md

@@ -30,6 +30,7 @@ worktree_closeout_preview(contract_path="<enclosure series-contract.md>", code_c
 worktree_closeout_apply(contract_path="<enclosure series-contract.md>", intent_note="<developer intent>", code_commit_message="<message>", memory_commit_message="<message>", ledger_commit_message="<message>")
 worktree_integrate(contract_path="<enclosure series-contract.md>", strategy="ff-only")
 worktree_cleanup(contract_path="<enclosure series-contract.md>")
+task_reopen(contract_path="<enclosure series-contract.md>", dry_run=true)
 lifecycle_finalize_task(contract_path="<enclosure series-contract.md>", task_doc_path="<task.json>", master_doc_path="<parent task.json>", subtask_number="<N>", dry_run=true)
 ```
 
@@ -254,6 +255,20 @@ edge is finalized separately.
 
 Cleanup is idempotent. If the worktrees or merged branches are already gone, it reports the already-clean state instead of failing. If Git refuses to delete an unmerged branch, cleanup leaves that branch in place and reports it for developer review.
 
+## Reopening A Completed Leaf
+
+Reopening reuses the EXACT same leaf id — never mint a suffixed leaf (`…-r1`).
+`task_reopen(contract_path=…)` is a state reset, not a worktree creator: it refuses
+anything but a fully landed leaf (closeout, integration, and cleanup completed, worktrees
+gone), then resets the contract's review/closeout/integration state, clears the stale
+lifecycle binding, marks `cleanup: reopened`, and puts the leaf's task document back to
+`planning` (master index entry flipped, audit decision appended). Preview with
+`dry_run=true` first. Afterwards: edit the doc's steps via `task_doc` (add, change, or
+untick work), then run a NORMAL `worktree_start` with the same leaf id — it recreates the
+worktrees off the current source tips, promotes/mints a fresh lifecycle, and restamps the
+doc's `lifecycleId`, so doc, chat, and dashboard bindings hold by construction. Implementation
+then proceeds as usual, including closeout → integrate → finalize.
+
 ## Boundaries
 
 1. The `c-09-git-worktree-manager` skill may create or reuse worktrees, root series contracts, and leaf enclosure contracts.

.hermes/skills/c-04-retrieval-strategy-router/codegraphcontext-high-level-methods.md

@@ -34,7 +34,7 @@ and complexity signals.
 | Where is this symbol? | `cgc_symbol_search` | `find name <name>` |
 | What does this function/method call? | `cgc_callees` | `analyze calls <function>` |
 | Who calls this function/method? | `cgc_callers` | `analyze callers <function>` |
-| Which files import this module string? | `cgc_dependencies` | `analyze dependencies <module>` |
+| Which files import this module string? | `cgc_dependencies` | `analyze deps <module>` |
 | Which functions are most complex? | `cgc_complexity` | `analyze complexity [function]` |
 | Do I need the interactive graph view? | `cgc_visualize` | `visualize` |
 

.hermes/skills/c-09-git-worktree-manager/SKILL.md

@@ -30,6 +30,7 @@ worktree_closeout_preview(contract_path="<enclosure series-contract.md>", code_c
 worktree_closeout_apply(contract_path="<enclosure series-contract.md>", intent_note="<developer intent>", code_commit_message="<message>", memory_commit_message="<message>", ledger_commit_message="<message>")
 worktree_integrate(contract_path="<enclosure series-contract.md>", strategy="ff-only")
 worktree_cleanup(contract_path="<enclosure series-contract.md>")
+task_reopen(contract_path="<enclosure series-contract.md>", dry_run=true)
 lifecycle_finalize_task(contract_path="<enclosure series-contract.md>", task_doc_path="<task.json>", master_doc_path="<parent task.json>", subtask_number="<N>", dry_run=true)
 ```
 
@@ -254,6 +255,20 @@ edge is finalized separately.
 
 Cleanup is idempotent. If the worktrees or merged branches are already gone, it reports the already-clean state instead of failing. If Git refuses to delete an unmerged branch, cleanup leaves that branch in place and reports it for developer review.
 
+## Reopening A Completed Leaf
+
+Reopening reuses the EXACT same leaf id — never mint a suffixed leaf (`…-r1`).
+`task_reopen(contract_path=…)` is a state reset, not a worktree creator: it refuses
+anything but a fully landed leaf (closeout, integration, and cleanup completed, worktrees
+gone), then resets the contract's review/closeout/integration state, clears the stale
+lifecycle binding, marks `cleanup: reopened`, and puts the leaf's task document back to
+`planning` (master index entry flipped, audit decision appended). Preview with
+`dry_run=true` first. Afterwards: edit the doc's steps via `task_doc` (add, change, or
+untick work), then run a NORMAL `worktree_start` with the same leaf id — it recreates the
+worktrees off the current source tips, promotes/mints a fresh lifecycle, and restamps the
+doc's `lifecycleId`, so doc, chat, and dashboard bindings hold by construction. Implementation
+then proceeds as usual, including closeout → integrate → finalize.
+
 ## Boundaries
 
 1. The `c-09-git-worktree-manager` skill may create or reuse worktrees, root series contracts, and leaf enclosure contracts.

.openclaw/workspace/skills/c-04-retrieval-strategy-router/codegraphcontext-high-level-methods.md

@@ -34,7 +34,7 @@ and complexity signals.
 | Where is this symbol? | `cgc_symbol_search` | `find name <name>` |
 | What does this function/method call? | `cgc_callees` | `analyze calls <function>` |
 | Who calls this function/method? | `cgc_callers` | `analyze callers <function>` |
-| Which files import this module string? | `cgc_dependencies` | `analyze dependencies <module>` |
+| Which files import this module string? | `cgc_dependencies` | `analyze deps <module>` |
 | Which functions are most complex? | `cgc_complexity` | `analyze complexity [function]` |
 | Do I need the interactive graph view? | `cgc_visualize` | `visualize` |
 

.openclaw/workspace/skills/c-09-git-worktree-manager/SKILL.md

@@ -30,6 +30,7 @@ worktree_closeout_preview(contract_path="<enclosure series-contract.md>", code_c
 worktree_closeout_apply(contract_path="<enclosure series-contract.md>", intent_note="<developer intent>", code_commit_message="<message>", memory_commit_message="<message>", ledger_commit_message="<message>")
 worktree_integrate(contract_path="<enclosure series-contract.md>", strategy="ff-only")
 worktree_cleanup(contract_path="<enclosure series-contract.md>")
+task_reopen(contract_path="<enclosure series-contract.md>", dry_run=true)
 lifecycle_finalize_task(contract_path="<enclosure series-contract.md>", task_doc_path="<task.json>", master_doc_path="<parent task.json>", subtask_number="<N>", dry_run=true)
 ```
 
@@ -254,6 +255,20 @@ edge is finalized separately.
 
 Cleanup is idempotent. If the worktrees or merged branches are already gone, it reports the already-clean state instead of failing. If Git refuses to delete an unmerged branch, cleanup leaves that branch in place and reports it for developer review.
 
+## Reopening A Completed Leaf
+
+Reopening reuses the EXACT same leaf id — never mint a suffixed leaf (`…-r1`).
+`task_reopen(contract_path=…)` is a state reset, not a worktree creator: it refuses
+anything but a fully landed leaf (closeout, integration, and cleanup completed, worktrees
+gone), then resets the contract's review/closeout/integration state, clears the stale
+lifecycle binding, marks `cleanup: reopened`, and puts the leaf's task document back to
+`planning` (master index entry flipped, audit decision appended). Preview with
+`dry_run=true` first. Afterwards: edit the doc's steps via `task_doc` (add, change, or
+untick work), then run a NORMAL `worktree_start` with the same leaf id — it recreates the
+worktrees off the current source tips, promotes/mints a fresh lifecycle, and restamps the
+doc's `lifecycleId`, so doc, chat, and dashboard bindings hold by construction. Implementation
+then proceeds as usual, including closeout → integrate → finalize.
+
 ## Boundaries
 
 1. The `c-09-git-worktree-manager` skill may create or reuse worktrees, root series contracts, and leaf enclosure contracts.

.pi/skills/c-04-retrieval-strategy-router/codegraphcontext-high-level-methods.md

@@ -34,7 +34,7 @@ and complexity signals.
 | Where is this symbol? | `cgc_symbol_search` | `find name <name>` |
 | What does this function/method call? | `cgc_callees` | `analyze calls <function>` |
 | Who calls this function/method? | `cgc_callers` | `analyze callers <function>` |
-| Which files import this module string? | `cgc_dependencies` | `analyze dependencies <module>` |
+| Which files import this module string? | `cgc_dependencies` | `analyze deps <module>` |
 | Which functions are most complex? | `cgc_complexity` | `analyze complexity [function]` |
 | Do I need the interactive graph view? | `cgc_visualize` | `visualize` |