UX: Restore sub-phase progress detail in deploy progress table
- Dominant language
- Go
- Stars
- 569
- Forks
- 364
- Avg merge
- 2d 19h
- Merged PRs (30d)
- 136
Description
## Description
The deploy progress table's \\detail\\ column is always empty during execution — it only gets populated on error. The old deploy path used `async.RunWithProgress` to pipe real-time detail like \\Packaging service api (Compiling...)\\ into the spinner.
The tracker's `Update(svc, phase, detail)` API already supports this; it just needs a real progress callback wired in from the Package/Publish/Deploy calls instead of `async.NewNoopProgress()`.
## Impact
This is a noticeable UX regression for long deploys where the user wants to know *what's happening* within a phase, not just *which phase* is active.
## Context
- Requested by @vhvb1989 in [PR #7776 comment](https://github.com/Azure/azure-dev/pull/7776#issuecomment-4280643268)
- The API surface exists (`Update(svc, phase, detail)`), just needs wiring
- Related: #7977 (table indentation/spacing)
Contributor guide
Assessment
This issue has not been assessed yet.