lark-kiro-bridge 0.3.1 → 0.5.0

package/README.en.md

@@ -59,18 +59,20 @@
 - 🔘 **Clickable buttons** — `/model` `/help` `/status` `/ws list` `/config` are all interactive cards, zero command memorization
 - 📝 **`/config` in-Feishu form** — Edit access control & preferences inside Feishu, takes effect instantly, anti-lockout validation
 - 🚄 **Rapid-fire message merging** — Multiple short messages within 200ms merge into a single Kiro call, no more abort-and-retry
+- 🧠 **`/steering` to manage Kiro instruction files in Feishu** — list/view/edit/new/rm, global or project scope, edit via in-Feishu form, persists permanently
 - 🎤 **Voice input** — Send a voice message in Feishu → auto-transcribed (Feishu ASR) → fed to Kiro. Requires `ffmpeg` and ASR scope.
 - 🛡️ **Process group kill** — `detached: true` + `process.kill(-pid)` reaches kiro-cli's grandchildren
 - ⏱ **Idle watchdog** — Stuck process auto-killed; tunable globally and per-chat
 - 🔐 **Three-tier access control** — User / chat / admin allowlists. **DMs always bypass the chat allowlist** so you can never lock yourself out.
-- 🍎 **macOS native daemon** — launchd auto-restart on crash, login auto-start
+- 🐧 **Cross-platform daemon** — macOS launchd / Linux systemd --user / Windows Task Scheduler. Auto-restart on crash, login auto-start.
+- 🖥️ **`/ps` `/exit` process management** — List host bridge processes from Feishu, stop with one button
 - 📊 **`/doctor` self-diagnosis** — Feed logs back to Kiro to analyze its own failures
 
 ## 🚀 Quick Start
 
 ### Prerequisites
 
-- macOS (Linux / Windows daemon on roadmap)
+- macOS / Linux / Windows
 - Node.js ≥ 20
 - `kiro-cli` installed and logged in
 - A Feishu / Lark account (personal edition is fine — the QR wizard auto-creates the app)
@@ -110,11 +112,22 @@ lark-kiro-bridge init --app-id cli_xxx --app-secret xxx
 ### Background daemon (recommended for production)
 
 ```bash
-lark-kiro-bridge start          # Install launchd plist and start
+lark-kiro-bridge start          # Install platform service and start
 lark-kiro-bridge status         # Check status
 lark-kiro-bridge restart        # Restart
 ```
 
+Platform mapping:
+
+| Platform | Implementation | Service path |
+|---|---|---|
+| **macOS** | launchd user agent | `~/Library/LaunchAgents/ai.lark-kiro-bridge.bot.plist` |
+| **Linux** | systemd user unit | `~/.config/systemd/user/lark-kiro-bridge.service` |
+| **Windows** | Task Scheduler ONLOGON | Task `LarkKiroBridge.Bot`, launcher `~/.lark-kiro-bridge/daemon-launcher.cmd` |
+
+> Linux: to keep the daemon running after logout (servers), run once:
+> `loginctl enable-linger $USER`
+
 ## 📖 Slash Commands
 
 ### Daily commands (everyone)
@@ -129,6 +142,8 @@ lark-kiro-bridge restart        # Restart
 | `/pwd` | `/cwd` | Current working directory |
 | `/ws list` | — | List named workspaces with switch buttons |
 | `/timeout [N\|off]` | `/to` | Idle watchdog threshold (minutes) |
+| `/ps` | — | List all bridge processes on this host |
+| `/steering` | `/memory` `/mem` | List Kiro steering files for current project (card + buttons) |
 | `/doctor [desc]` | — | Let Kiro inspect logs and diagnose |
 
 ### Admin commands
@@ -140,6 +155,8 @@ lark-kiro-bridge restart        # Restart
 | `/ws save <name>` | Save current cwd as a named workspace |
 | `/ws use <name>` | Switch to a named workspace |
 | `/ws remove <name>` | Delete a named workspace |
+| `/steering edit/new/rm <name>` | Edit / create / delete a steering file |
+| `/exit <id\|#>` | Stop a bridge process (self / others) |
 | `/reconnect` | Force reconnect Feishu WebSocket |
 
 > By default everyone is admin (`access.admins` empty). Tighten before sharing with a team.
@@ -283,9 +300,9 @@ Conventions: TypeScript strict / Biome lint / vitest tests / conventional commit
 
 - **v0.2** ✅ Current (structured cards + button callbacks + Slack-style tool panels + QR app binding + voice input via ASR)
 - **v0.3** ✅ In-Feishu `/config` form + three-tier access control (DM bypass) + rapid-fire message merging
-- **v0.4** Linux systemd / Windows Task Scheduler daemon
-- **v0.4** `/ps` `/exit` to manage host processes from Feishu
-- **v0.5** Group-name → workspace heuristic (joining "agenzo" group defaults cwd to agenzo dir)
+- **v0.4** ✅ Linux systemd / Windows Task Scheduler daemon + `/ps` `/exit` in-Feishu process management
+- **v0.5** ✅ `/steering` to manage Kiro instruction files in Feishu (list/view/edit/new/rm, global/project scope)
+- **v0.6** `/cron` scheduled tasks — natural-language or cron-expression schedules, e.g. "every day 6am summarize trending"
 - **v1.0** Centralized server deployment / multi-user isolation / web admin panel
 
 ## 📄 License

package/README.md

@@ -59,18 +59,20 @@
 - 🔘 **按钮可点** — `/model` `/help` `/status` `/ws list` `/config` 全部可点击操作，0 命令记忆
 - 📝 **`/config` 飞书内表单** — 在飞书里改访问控制和偏好，即时生效，防自锁校验
 - 🚄 **rapid-fire 消息合并** — 200ms 内连发的多条短消息自动合并为一次 Kiro 调用，不再被前一条 abort
+- 🧠 **`/steering` 飞书内管理 Kiro 指令文件** — list/view/edit/new/rm，全局或项目 scope，飞书表单直接改，永久生效
 - 🎤 **语音输入** — 飞书发语音消息 → 自动转写（飞书 ASR）→ 喂给 Kiro，需 `ffmpeg` 和 ASR 权限
 - 🛡️ **进程组 kill** — `detached: true` + `process.kill(-pid)` 杀掉 kiro-cli 全部子孙
 - ⏱ **Idle Watchdog** — 卡住自动 killTree，可全局 / per-chat 配置
 - 🔐 **三层访问控制** — 用户 / 群 / 管理员白名单，**DM 永远豁免群白名单**，不会把自己锁外面
-- 🍎 **macOS 原生守护** — launchd 崩溃自动拉起，开机自启
+- 🐧 **跨平台守护** — macOS launchd / Linux systemd --user / Windows Task Scheduler，崩溃自动拉起，开机自启
+- 🖥️ **`/ps` `/exit` 进程管理** — 飞书内列出本机所有 bridge 进程，按按钮停止
 - 📊 **`/doctor` 自诊断** — 让 Kiro 看日志自己分析故障
 
 ## 🚀 快速上手
 
 ### 前置条件
 
-- macOS（Linux / Windows daemon 在路线图）
+- macOS / Linux / Windows
 - Node.js ≥ 20
 - `kiro-cli` 已安装并登录
 - 飞书账号（个人版即可，扫码自动创建应用）
@@ -110,11 +112,22 @@ lark-kiro-bridge init --app-id cli_xxx --app-secret xxx
 ### 后台守护（推荐生产）
 
 ```bash
-lark-kiro-bridge start          # 装 launchd plist 并启动
+lark-kiro-bridge start          # 装平台原生服务并启动
 lark-kiro-bridge status         # 看状态
 lark-kiro-bridge restart        # 重启
 ```
 
+平台映射：
+
+| 平台 | 实现 | 服务定义路径 |
+|---|---|---|
+| **macOS** | launchd 用户代理 | `~/Library/LaunchAgents/ai.lark-kiro-bridge.bot.plist` |
+| **Linux** | systemd 用户单元 | `~/.config/systemd/user/lark-kiro-bridge.service` |
+| **Windows** | Task Scheduler ONLOGON | 任务名 `LarkKiroBridge.Bot`，启动器 `~/.lark-kiro-bridge/daemon-launcher.cmd` |
+
+> Linux 想让 daemon 在用户登出后还跑（比如服务器场景），跑一次：
+> `loginctl enable-linger $USER`
+
 ## 📖 飞书内的命令
 
 ### 日常命令（所有人）
@@ -129,6 +142,8 @@ lark-kiro-bridge restart        # 重启
 | `/pwd` | `/cwd` | 当前工作目录 |
 | `/ws list` | — | 列出命名工作区，按钮一键切 |
 | `/timeout [N\|off]` | `/to` | idle watchdog 阈值（分钟） |
+| `/ps` | — | 列出本机所有 bridge 进程 |
+| `/steering` | `/memory` `/mem` | 列出当前项目的 Kiro 指令文件（卡片+按钮） |
 | `/doctor [描述]` | — | 让 Kiro 看日志自诊断 |
 
 ### 管理员命令
@@ -140,6 +155,8 @@ lark-kiro-bridge restart        # 重启
 | `/ws save <name>` | 把当前 cwd 存为命名工作区 |
 | `/ws use <name>` | 切到命名工作区 |
 | `/ws remove <name>` | 删除命名工作区 |
+| `/steering edit/new/rm <name>` | 编辑 / 新建 / 删除 steering 文件 |
+| `/exit <id\|#>` | 停止指定 bridge 进程（自己 / 他人） |
 | `/reconnect` | 强制重连飞书 WebSocket |
 
 > 默认所有人都是管理员（`access.admins` 为空）。团队推广前请收紧。
@@ -281,9 +298,9 @@ node bin/lark-kiro-bridge.mjs run           # 本地跑（先 stop daemon）
 
 - **v0.2** ✅ 当前版（结构化卡片 + 按钮回调 + Slack-style 工具面板 + 扫码绑定 + 语音输入 ASR）
 - **v0.3** ✅ `/config` 飞书内表单 + 三层访问控制（DM 豁免群白名单）+ rapid-fire 消息合并
-- **v0.4** Linux systemd / Windows Task Scheduler 守护
-- **v0.4** `/ps` `/exit` 飞书内调用本机进程
-- **v0.5** 群名 → 工作区的启发式默认（进 agenzo 群默认在 agenzo 目录）
+- **v0.4** ✅ Linux systemd / Windows Task Scheduler 守护 + `/ps` `/exit` 飞书内进程管理
+- **v0.5** ✅ `/steering` 飞书内管理 Kiro 指令文件（list/view/edit/new/rm，global/project scope）
+- **v0.6** `/cron` 定时任务 — 自然语言或 cron 表达式设定，"每天 6 点总结 trending"
 - **v1.0** 服务器集中部署 / 多用户隔离 / Web 管理面板
 
 ## 📄 License