Success outro claims all changes even when some steps didn't complete
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 197
- Forks
- 51
- Avg merge
- 1d 23h
- Merged PRs (30d)
- 94
Description
The success outro always shows the framework's full static "What the agent did" list. There is no partial state — a run where a step didn't complete still renders every claimed change under "Successfully installed PostHog!".
Seen in a Flutter run (#942): the agent couldn't install the SDK, said so in its setup report, and left its "Install SDK" task pending — the outro still claimed the SDK was added.
The outro is the wizard's last word, so overstating it undermines the "please review the changes" note right below. The run's task statuses already exist in the store; the outro could reflect them instead of static copy.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the success outro and trace how it reads task statuses from the store, using the Flutter run described in issue #942 as the partial-completion case. Update the outro's claimed changes to match completed tasks, then verify that pending or failed steps are not presented as successfully installed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript
- Domain
- developer-experience
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 68/100