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

Open
  • Is something wrong?
#412 0 comments 0 reactions 0 assignees View on GitHub

Maintainers usually reply within 1 day

Nobody has claimed this yet.

Assessment

Difficulty
5/5
Estimated time
Over a week
Newbie friendliness
15/100
Issue type
Feature
Clarity
Needs clarification
Activity status
Stale
Tech stack
csharp, openapi
Domain
api

Research direction

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.

Written by the indexing model from the issue text.

Description

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).

Dominant language
C#
Stars
1
Forks
0
Avg merge
2h 2m
Merged PRs (30d)
98

Getting set up

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from nevridge/TaskFlow

All issues in nevridge/TaskFlow

Similar issues

More C# issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.