[Task][RFC]: Deliver human-confirmed operations across frontend and Lark
维护者通常 1 天内回复
还没有人认领这个 Issue。
评估
- 难度
- 5/5
- 预计耗时
- 一周以上
- 新手友好度
- 25/100
- Issue 类型
- 功能
- 描述清晰度
- 基本清楚
- 活跃度
- 活跃
- 技术栈
- python, typescript
调研方向
Read the linked RFC and coordinate with the existing typed-action and simulated-provider owners before choosing an unowned acceptance gap. Start with loopx/chat_action_store.py, loopx/chat_actions.py, loopx/extensions/lark/event_collector.py, and apps/presentation/dashboard/src/data/chat.ts. Done means the accepted scope is integrated across the required entrypoints, with commands and passed, failed, and untested evidence recorded; a merged PR alone is not completion.
由索引模型根据 Issue 内容生成。
描述
Outcome / 目标
交付前端与 Lark 一致的人类确认操作。One task tracks this RFC's delivery; keep implementation PRs and milestone evidence here instead of creating a parallel task tree.
Canonical design: RFC. Roadmap: S8/S9, under #4574. Design acceptance is distinct from implementation, live qualification and promotion.
Current boundary
Source audit: main at ce3862e33 (2026-09-28). This is source/PR inspection, not a new test or live-qualification claim.
The RFC separates generic interaction authority, optional domain execution and venue adapters. Existing typed action and operation-card work must be inventoried before adding anything; M1 requires a simulated consumer plus both entrypoints.
Work remaining
- Complete the generic preview/confirm/execute/reconcile/return lifecycle through the existing typed-action owner and authenticated callback path.
- Use one optional simulated domain consumer for M1; keep domain reservation/precision/state with that provider. M2/M3 remain separately gated.
Ownership and ongoing work
Coordinate with current generic operation-card and simulated-provider work. Do not open a competing approval/financial ledger. This public task authorizes no trading, payment, account mutation, credential setup or live order; M3 requires the RFC’s exact user authorization.
Contribution route: implementation/integration overlaps active work. Start from the linked current owners/PRs and identify an unowned acceptance gap in a claim comment; do not begin a competing rewrite.
Acceptance
- The same exact request confirmed from two entrypoints executes once; stale/rejected/expired confirmations cannot execute.
- Ambiguous submission, restart and duplicate callback recover one outcome and return it to the originating conversation.
- Packaged frontend, Lark and receipt readback agree; default-off and protected-operation boundaries hold.
- Reconcile the RFC's current delivery checkpoint and this issue with the integrated revision, commands, passed/failed/untested evidence and remaining gates. Close the accepted scope only; no claim that a merged PR alone completes the RFC.
Starting points and delivery boundary
- loopx/chat_action_store.py
- loopx/chat_actions.py
- loopx/extensions/lark/event_collector.py
- apps/presentation/dashboard/src/data/chat.ts
Base: latest main. Reuse the existing typed owner and provider boundaries. Include affected CLI/frontend/Lark companions; verify real entrypoints and backend where changed. Preserve existing first-screen review and maintainer merge gates. Public artifacts contain only synthetic/public-safe evidence, no private operational state. This task does not authorize provider promotion, benchmark launches, release/deployment or unrelated protected effects.
- 主要语言
- Python
- 星标
- 6.2k
- 派生
- 596
- 平均合并
- 6 小时 44 分钟
- 30 天内合并 PR
- 915
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
loopx-project/loopx 的其他 Issue
-
难度 2/5 1-3 小时 新手友好度 84/100
loopx-project/loopx#6842 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 72/100
loopx-project/loopx#6108 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
loopx-project/loopx#5688 · 2 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 60/100
loopx-project/loopx#5632 · 1 条评论 ·
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 65/100
loopx-project/loopx#5443 · 1 条评论 ·
维护者通常 1 天内回复
查看 loopx-project/loopx 的全部 Issue
相似的 Issue
-
bug
难度 2/5 1-3 小时 新手友好度 68/100
anchore/grype-db#1149 · 1 条评论 ·
维护者通常 1 天内回复
-
[Bug]: `hermes plugins update` clones an entire monorepo twice - `subdir` is resolved but dropped at both catalog-update call sites可能已有人在做 @HootRock 今天认领。 未关闭comp/cli P2 type/perf
难度 2/5 1-3 小时 新手友好度 72/100
NousResearch/hermes-agent#142417 · 2 条评论 ·
维护者通常 1 天内回复
-
SMC SPEC
难度 2/5 1-3 小时 新手友好度 70/100
tenstorrent/tt-oca-harness#3287 ·
维护者通常 1 天内回复
-
bug enhancement python
难度 2/5 1-3 小时 新手友好度 85/100
DewaldOosthuizen/tech-cheat-sheets-and-notes#392 ·
维护者通常 1 天内回复
-
security
难度 2/5 1-3 小时 新手友好度 72/100
fabriziosalmi/wildbox#801 ·
维护者通常 1 天内回复