Motivation
After a delivery is launched through manage-artificer, the local user has no ongoing foreground explanation of what Artificer is doing. In the observed issue #217 run, current activity became visible only through a separate status request, making the active local process difficult to understand.
Acceptance criteria
- A delivery launched through
manage-artificer provides periodic foreground status while work remains active.
- Each update explains the current delivery state and any action needed from the user.
- Foreground reporting ends with a clear terminal or waiting state rather than leaving an unexplained poll running.
Open questions
- Should the skill poll every 30 seconds, or should an event-driven or different interval provide the foreground updates?
Motivation
After a delivery is launched through
manage-artificer, the local user has no ongoing foreground explanation of what Artificer is doing. In the observed issue #217 run, current activity became visible only through a separate status request, making the active local process difficult to understand.Acceptance criteria
manage-artificerprovides periodic foreground status while work remains active.Open questions