[Tracking] Assistant work after the move

Aperta
  • Qualcosa non va?
#420 0 commenti 0 reazioni 0 assegnatari Vedi su GitHub

I maintainer di solito rispondono entro 1 giorno

Nessuno ha ancora preso questa issue.

Valutazione

Difficoltà
4/5
Tempo stimato
3-5 giorni
Idoneità per principianti
35/100
Tipo di issue
Funzionalità
Chiarezza
Abbastanza chiara
Stato di attività
Attiva
Stack tecnologico
csharp
Ambito
backend-api-design

Direzione di ricerca

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.

Scritto dal modello di indicizzazione a partire dal testo della issue.

Descrizione

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.

Lingua principale
C#
Stelle
1
Fork
0
Merge medio
2h 2m
PR unite (30g)
98

Preparare l'ambiente

Come iniziare

  1. Leggi tutta la issue e poi la guida ai contributi del progetto.
  2. Commenta sulla issue per dire che te ne occupi tu — evita che due persone facciano lo stesso lavoro.
  3. Fai un fork del repository e lavora su un branch.
  4. Apri una pull request che faccia riferimento al numero della issue.

Altre issue di nevridge/TaskFlow

Tutte le issue di nevridge/TaskFlow

Issue simili

Altre issue su C#

Ricevi le nuove issue nella tua casella

Un breve riepilogo di issue GitHub adatte ai principianti.