chore: review smaller API gaps (moved tasks, history dates, unexposed endpoints)

オープン
  • 何か問題がありますか？
#412 コメント 0 件 リアクション 0 件 担当者 0 名 GitHub で見る

メンテナーはふだん 1 日以内に返信

まだ誰も着手していません。

評価

難易度
5/5
見積もり時間
1週間以上
初心者へのやさしさ
15/100
issue の種類
機能追加
明瞭さ
説明が足りない
活発さ
停滞
技術スタック
csharp, openapi
領域
api

調査の方向性

The issue says this work transfers to nevridge/TaskFlow with nevridge/taskflow-assistant#38 and relates to nevridge/TaskFlow#397; start by checking those issues and the overlapping #409 and #415. Review each listed API gap and agree which to do, since none is currently a bug and item 1 needs a joint decision. Done means every item is implemented or closed with a one-line reason, with tool tests, docs, and chat references aligned for additions.

索引モデルが issue の本文から書いたものです。

説明

question

Status 2026-11-04: not required before the move. This issue transfers to nevridge/TaskFlow with nevridge/taskflow-assistant#38 (nevridge/TaskFlow#397). Item 1 overlaps nevridge/TaskFlow#409 part 3 and #415 (report moved tasks); decide the three together.

Problem

Smaller differences between the MCP server and the TaskFlow API (origin/main, 2026-10-30). None is a bug today. Decide which are worth doing.

  1. JournalEntryResponseDto now returns movedCount and movedTaskItemIds on create (carry-forward). JournalEntryDto here drops them, so JournalResolver.EnsureAsync cannot tell the user that tasks were moved when it creates an entry with a timezone offset. TaskFlow's rule is that creating or switching to an entry must never move tasks except into the user's own today; confirm the MCP only creates entries for the date it was asked for.
  2. PreviousStatus is mapped but never shown in output.
  3. TaskEventDto omits FromJournalDate / ToJournalDate, so task history for moves shows only the summary.
  4. Not exposed by any tool: delete project, edit or delete task notes, journal notes and log lines, carry-forward (POST JournalEntries/{id}/carry-forward), and subtask listing. Decide if any are wanted.
  5. The 5xx error text points at Seq on http://localhost:5380, which is only right for the local Docker stack.
  6. Bump plugin.json when the fixes above ship.
  7. Review the tool annotations (read-only, destructive, idempotent hints) against what each tool does. Raised by the documentation advisors during asst#37 (nevridge/taskflow-assistant#40).
  8. De-duplicate the guidance lines in batch reports. When several items in an update_tasks, create_tasks or set_journal_todos call fail with the same rule, the same guidance line repeats for each one. Raised during asst#37.
  9. Share one exception-to-guidance helper between the task and journal tools, instead of each tool wiring ToolGuard itself. Raised during asst#37.

Acceptance criteria

  1. Each item is done, or closed here with a one-line reason.
  2. Tool surface test, docs and chat references stay in sync for anything added.

Related

Part of nevridge/taskflow-assistant#31 (align the MCP server with the TaskFlow API).

主要言語
C#
スター
1
フォーク
0
平均マージ
2時間 2分
マージ済み PR（30日）
98

環境構築

はじめの一歩

  1. issue を最後まで読み、次にプロジェクトのコントリビューションガイドを読みます。
  2. 着手することを issue にコメントします — 二人が同じ作業をするのを防げます。
  3. リポジトリをフォークし、ブランチを切って変更します。
  4. issue 番号を参照したプルリクエストを送ります。

nevridge/TaskFlow のほかの issue

nevridge/TaskFlow の issue をすべて見る

似ている issue

C# の issue をもっと見る

新しい issue をメールで受け取る

初心者向けの GitHub issue を短くまとめたダイジェスト。