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

Abierto
  • ¿Algo no está bien?
#412 0 comentarios 0 reacciones 0 asignados Ver en GitHub

Los mantenedores suelen responder en 1 día

Nadie ha tomado este issue todavía.

Evaluación

Dificultad
5/5
Tiempo estimado
Más de una semana
Aptitud para principiantes
15/100
Tipo de issue
Nueva funcionalidad
Claridad
Necesita aclaración
Estado de actividad
Estancado
Stack tecnológico
csharp, openapi
Área
api

Línea de trabajo

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.

Escrito por el modelo de indexación a partir del texto del issue.

Descripción

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

Lenguaje dominante
C#
Estrellas
1
Forks
0
Merge medio
2 h 2 min
PR fusionados (30 d)
98

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de nevridge/TaskFlow

Todos los issues de nevridge/TaskFlow

Issues similares

Más issues de C#

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.