[Tracking] Assistant work after the move

Abierto
  • ¿Algo no está bien?
#420 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
4/5
Tiempo estimado
3-5 días
Aptitud para principiantes
35/100
Tipo de issue
Nueva funcionalidad
Claridad
Bastante claro
Estado de actividad
Activo
Stack tecnológico
csharp
Área
backend-api-design

Línea de trabajo

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.

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

Descripción

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.

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.