Shared IDMP CLI rules

🛑 Destructive op confirmation (mandatory)

Before executing any DELETE, non-readonly POST / PUT / PATCH, --ack-risk command, or local destructive helper (config remove / profile remove / auth logout --clear), the agent MUST print the 4 items below and then wait for an explicit user yes before running the command:

1. Target — resource type + id + name + owning element / template / profile.
2. Action — HTTP method + path + schemaPath + param summary (mask secrets).
3. Reason — why this operation is needed (trace it back to the user's request; if it is a rollback of a failed previous step, say so).
4. Blast radius — dependent analyses / panels / dashboards / alerts / notifications; whether the action is reversible; whether sub-objects are deleted transitively; cross-profile impact.

Read-only commands (get, list, search, path, tree, new-name, *-search, *-query, forecast) do not require this confirmation. For detailed wording and the ready-to-use template, see references/idmp-safety-rules.md.

Two working modes

| Mode | CLI families | Use when |