Add epics 10–12 (plans UI, completion artifacts, ops copilot), worker draft-PR and live E2E verify tasks, and phase A–E execution order after A1 gap review. Co-authored-by: Cursor <cursoragent@cursor.com>
48 lines
1.3 KiB
Markdown
48 lines
1.3 KiB
Markdown
---
|
||
kind: task
|
||
slug: completion-summary-generator
|
||
title: Generate plain-language completion summary for a convoy
|
||
plan_slug: automation-foundation
|
||
epic_slug: owner-completion-artifacts
|
||
status: ready
|
||
priority: P1
|
||
tenant_id: global
|
||
owner: unassigned
|
||
cursor_todo_id: null
|
||
updated_at: "2026-08-12"
|
||
---
|
||
|
||
# Task summary
|
||
|
||
On convoy transition to `merged` or `released` (or manual “Generate summary”), produce a short owner-facing summary stored on the convoy and shown in Mission Control — no code diff.
|
||
|
||
## Description
|
||
|
||
Use `resolveModel` with a dedicated role alias (e.g. `role-doc-writer` or `completion-summarizer`) and context: success metric, briefs, recent `convoy_events`, PR title if present.
|
||
|
||
### Output
|
||
|
||
- 3–8 sentences: what changed for the user/operator, what’s left, risks
|
||
- Persist on convoy content `completionSummary` + `completionSummaryAt`
|
||
- tRPC `convoys.getCompletion` / include in `convoys.get`
|
||
|
||
## Subtasks
|
||
|
||
- [ ] Zod fields on convoy content
|
||
- [ ] Generator service + role route seed
|
||
- [ ] Trigger on transition and manual regenerate
|
||
- [ ] Mission control detail section
|
||
|
||
## Estimation
|
||
|
||
M
|
||
|
||
## Acceptance criteria
|
||
|
||
- [ ] After merge/released, summary appears without git access
|
||
- [ ] Regenerating updates text and timestamp
|
||
- [ ] No file diffs in the owner-facing panel
|
||
|
||
## Links
|
||
|
||
- Epic: `./Epic-owner-completion-artifacts.md`
|