feat: evaluate recycle-bin and dangerous delete operations

[pandaria75]

背景

当前插件明确不做 delete / archive，避免 Dify Agent 误删内容。

但后续可能需要 recycle-bin 查询、恢复或受保护删除能力。

目标

评估是否需要新增：

• list_recycle_bin
• restore_recycle_item
• destroy_recycle_item
• dangerous_delete_page
• dangerous_delete_book
• dangerous_delete_chapter
• dangerous_delete_shelf

设计要求

如果未来实现危险删除工具，必须要求强确认参数，例如：

{
  "resource_type": "page",
  "resource_id": "123",
  "confirm": "DELETE page:123"
}

非目标

当前不实现删除能力。

验收标准

• 明确删除风险。
• 明确不应由 LLM 自动调用。
• 给出是否需要实现 recycle-bin 查询和恢复能力的建议。

[pandaria75]

Completed evaluation for #47 in task planning artifacts.

Summary:

• Recycle-bin, restore, delete, and destroy operations are highly safety-sensitive because they can directly affect content lifecycle and may become irreversible.
• These operations must not be automatically invoked by an LLM.
• Even recycle-bin query/restore should only be reconsidered later as tightly controlled admin workflows with explicit human confirmation.

Recommendation:

• Priority P3 / deferred.
• Do not expose delete/destroy behavior as normal plugin tools.
• Revisit only with separate approval, strong operator gating, and a non-casual workflow design.

No production implementation for #47 is included in this task.