feat: add proto rm/remove command to uninstall protocol

[XiangqianHuang]

概述

添加 cueme proto rm/remove 命令,作为 cueme proto apply 的反向操作,允许用户干净地移除已应用的 HAP 协议。

功能特性

• 移除 HAP 协议管理块 (BEGIN_MARKER 到 END_MARKER)
• 保留文件中其他非管理块的内容
• 如果文件移除后为空,自动删除文件
• 智能处理不同的换行符风格 (CRLF/LF)
• 友好的错误处理和提示信息

使用方法

# 使用 rm 移除协议
$ cueme proto rm windsurf
ok: removed managed block from: ~/.codeium/windsurf/memories/global_rules.md

# 使用 remove 别名
$ cueme proto remove kiro
ok: removed managed block and deleted empty file: ~/.kiro/steering/cueme_proto.md

使用场景

• 卸载不再需要的 HAP 协议
• 清理测试环境
• 重新配置前先移除旧配置

实现细节

修改内容

• 添加 protoRemove() 函数用于移除已应用的协议块
• 在 CLI 中注册 rm 和 remove 两个命令别名
• 更新帮助文档显示新命令
• 导出 protoRemove 函数到 module.exports

代码逻辑

1. 读取目标文件内容
2. 查找 BEGIN_MARKER 和 END_MARKER
3. 移除标记之间的内容
4. 保留文件中的其他内容
5. 如果文件为空则删除文件

测试

# 测试 rm 命令
$ cueme proto apply kiro
ok: applied to ~/.kiro/steering/cueme_proto.md

$ cueme proto rm kiro
ok: removed managed block and deleted empty file: ~/.kiro/steering/cueme_proto.md

# 测试 remove 别名
$ cueme proto apply kiro
ok: applied to ~/.kiro/steering/cueme_proto.md

$ cueme proto remove kiro
ok: removed managed block and deleted empty file: ~/.kiro/steering/cueme_proto.md

相关文档

• 基于已合并的 Kiro 支持 PR feat: add Kiro AI programming tool support #1
• 与 cueme proto apply 命令对应的反向操作

[nmhjklnm]

Thanks — this feature makes a lot of sense as the reverse operation of cueme proto apply, and CI is green.

A couple of things I’d suggest before merging:

Must-fix

1. protoRemove() has an unused local (exists).

   • You set it but never read it; please remove it.

2. When deleting the file fails (fs.unlinkSync throws), the command still returns ok: and exits 0.

   • I’d treat this as an error (e.g. return error: and set a non-zero exit), otherwise users may think everything is clean but the file is still there.

Nice-to-have / confirm behavior

3. Marker pairing robustness: current logic removes from the first BEGIN match to the first END match.

   • If someone accidentally duplicates markers, this might delete an unexpected range. Consider pairing BEGIN with the next END after it (more explicit index search), or at least document the “first block only” behavior.

4. trimEnd() changes trailing whitespace/newlines of the remaining content.

   • Probably fine, but please confirm this is intended; otherwise keep the existing tail formatting and only remove the managed block.

Once you address (1)-(2), I think this is good to go.

[nmhjklnm]

Re-review: looks good.

• Removed the unused exists variable.
• Deletion failure now throws an error (non-zero exit), which is safer.
• Preserves existing file formatting (no trimEnd()), while still removing the managed block.

CI is green. Approving.