[prineycom]

Flow epic-tasks — one task.

MP-86 — /flow в табе задачи: запуск по своей задаче и по её дочерним задачам (эпики), с подхватом цепочки подзадач

• Plan: https://draft.yokeloop.com/artifacts/mp-86-flow-c69kv898
• What changed:
  • Parent task relation in the engine: schema 13 (tasks.parent_id), parent on task create/update/show across CLI (task create --parent, task parent <KEY> <PARENT|none> --reason), local and remote MCP and the HTTP API. Same-project, not-self and cycle guards; journal note on change.
  • Pipeline: mp-task subtasks <KEY> (descendants, subtasks before parent), parent in /board; the session scope of a task chat P-N now covers P-N and its subtasks for /plan, /do, /flow, /ship; /flow expands each typed key into its subtask tree (post-order) and handles their statuses.
  • Task chat role prompt and glossary updated; README/AGENTS schema 13 notes.
• Review: round 1 changes_required (README still said schema 12) → fixed; round 2 approved, no findings.
• Checks on the assembled flow branch: pnpm build 0; pnpm verify 0 — fast 172/172, boundary 62/62, TUI 30/30, test unit runtime 34.3 s (budget ≤55 s).
• Live acceptance: not required by the plan; the executor ran the plan's CLI scenario on a disposable DB (subtask tree, rejected cycle, journal note).
• Engineer's answers taken on the way: relation model «parent_id (рекомендую)»; scope «все команды»; order «Подзадачи раньше (рекомендую)».
• Upgrade: run mypi db init once after updating (schema 12 → 13; back up the database first). CHANGELOG entry left to the release.

🤖 Generated with Claude Code