[Tracking] Assistant work after the move

未关闭
#420 0 条评论 0 个 reaction 已指派 0 人 在 GitHub 查看

维护者通常 1 天内回复

还没有人认领这个 Issue。

评估

难度
4/5
预计耗时
3-5 天
新手友好度
35/100
Issue 类型
功能
描述清晰度
基本清楚
活跃度
活跃
技术栈
csharp

调研方向

Read the linked issues #414, #415, #409, #412, and #410 to understand their scope and dependencies, then check blockers #400 and #398. The tracking issue is done when all five are closed or closed as not wanted, each with a one-line reason.

由索引模型根据 Issue 内容生成。

描述

tech-debt

Groups the assistant (assistant/) work that follows the monorepo move (#397, done: #398 closed 2026-11-06). All of it except #410 waits for #400, because assistant feature work uses the merged pipeline.

Suggested order

  1. #410 — One-command install and update: the plugin and MCP server run from a runtime folder outside the repo, not from the clone (redesigned 2026-11-06; needs grooming; not blocked by #400, and first because it changes how the assistant is run every day)
  2. #414 — Report created tasks when create_tasks hits a transport error (bug; also set_journal_todos). Independent of the others.
  3. #415 — Stop get_journal from silently creating entries and carrying tasks forward (bug; needs a design decision first). Decide with #409 part 3 and #412 item 1, since all three change how moved tasks are reported.
    3a. [ ] #422 — Show planned subtasks in the planned list and count them in the Planned tasks (N) header of get_journal (needs grooming; changes the same tool output as #415, so build them together)
  4. #409 — Planning reliability in task tools (parts 2 to 4; part 3 is decided with #415).
  5. #412 — Review the smaller API gaps (item 1 is decided with #415; items 7 to 9 came from asst#37).

Notes

  • #411 (run the MCP client against the real API in CI) is not here: it is part of the move and is listed in #397.
  • #414, #415, #409, #412 and #422 are blocked by #400 on GitHub. #410 is not (the blocker was removed on 2026-11-06), so it can be done before the pipeline merge.
  • #409, #410 and #412 were transferred from nevridge/taskflow-assistant on 2026-11-04; their old references redirect.

Done when

All six are closed or closed as not wanted, each with a one-line reason.

主要语言
C#
星标
1
派生
0
平均合并
2 小时 2 分钟
30 天内合并 PR
98

环境准备

  • 提供 Dockerfile 或 Docker Compose 文件
  • 没有 Pull Request 模板
  • 阅读贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

nevridge/TaskFlow 的其他 Issue

查看 nevridge/TaskFlow 的全部 Issue

相似的 Issue

更多 C# Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。