dpd-editlisted

# /dpd-edit <node_id|pool_id> Announce: "Using dpd-edit skill." --- ## When to invoke - User wants to close, add, or mutate a node directly without waiting for ambient detection - User wants to reject, drop, or unsuppress a Pool item - Correcting a misclassification that ambient mode introduced - Any explicit manual graph surgery --- ## Argument parsing ``` /dpd-edit <id> [<operation>] [<additional args>] ``` `<id>` is either a `node_id` (e.g., `node_abc123`) or a `pool_id` (e.g., `pool_def456`). Determine target type from the prefix: `pool_` = pool item, anything else = node. If `<operation>` is omitted, present available operations for the target and ask user to choose. --- ## Node operations ### Close a node Use when user wants to mark a node resolved, rejected, or invalidated. ``` close_node( session_id=<session_id>, node_id=<node_id>, closure_reason=<"resolved" | "rejected" | "invalidated"> ) ``` After: one-line summary — `closed <node_id>: <text> [<closure_reason>]` ### Add a child node (manual) Use when user wants to add a node directly, not from conversation inference. ``` add_node( session_id=<session_id>, parent_id=<node_id>, type=<node_type>, text=<text>, provenance='manual' ) ``` `provenance='manual'` marks this as a direct user edit with no conversation trace (spec §9.3). After: one-line summary — `added <new_node_id> under <parent_id>: <text>` ### Edit node text (v0.3.1 gap) **No `update_node_text` tool exists in v0.3.1.** W