Stop setting the deploying stage of a run

[anurag]

Summary

prompt-to-app set the stage deploying after publish-app. Then awaitDeployment() looked up the Blueprint and set waiting_for_services. stageOrder in public/app.js does not list deploying. While a run was at that stage, the heading read Deploying, and the UI marked no stage as complete or active. Thus the stage list was the same as for a run that did not start.

No code, test, or script reads deploying. The tests use only done or a mock of setRunStage(), and scripts/demo.ts prints each stage that it gets. The docs do not list it. This change removes it from the workflow, and does not change the UI.

Changes

app/workflow.ts: the workflow does not set deploying before awaitDeployment(). The stage stays publishing during the Blueprint lookup, which is normally complete in a few seconds. publish-app writes no progress, so in that time the UI shows Publishing as active, with no progress text.

app/store.ts: RunStage has no deploying, so tsc gives an error for a new write of it. Now RunStage and stageOrder list the same ten stages in the same order. A comment on RunStage says to keep the two lists the same.

Limits

• A run that ended at deploying before this change keeps that stage in its row, and the UI shows it as before. Only a run that failed during the Blueprint lookup ended there.
• The change is in the workflows service. A run that starts before the new version registers its tasks still sets deploying.

Test plan

• npm run check: Biome, tsc, and 376 tests pass.
• A script compared RunStage with stageOrder: the same ten stages in the same order.
• tsc gives TS2345 for setRunStage(id, "deploying").
• After the workflows service deploys, start a run in the UI, and make sure that Publishing goes directly to Waiting For Services.

🤖 Generated with Claude Code