Name: Build Review Ship
Author: stericishere

Create or update the PR and complete the shipping path.

By the time this stage starts, fix has already converged. This stage should not reopen the main review loop unless shipping itself uncovers a new blocker.

Inputs

docs/build/check.md
docs/build/brief.md
docs/build/plan.md
docs/build/execute.md
docs/build/fix.md

Process

Create or update the PR using the stage docs as the source of truth.
Use gstack:/ship as the default shipping path.
Once the PR is merged, use gstack:/land-and-deploy to land and verify production:
- Merge the PR (if not already merged)
- Wait for CI and deploy to complete
- Run canary health checks against the production URL
- If canary checks fail, flag immediately and halt — do not mark the stage complete
If branch cleanup or alternate closeout handling is needed after shipping, invoke .

Create or update the PR and complete the shipping path.

By the time this stage starts, fix has already converged. This stage should not reopen the main review loop unless shipping itself uncovers a new blocker.

Inputs

docs/build/check.md
docs/build/brief.md
docs/build/plan.md
docs/build/execute.md
docs/build/fix.md

Process

Create or update the PR using the stage docs as the source of truth.
Use gstack:/ship as the default shipping path.
Once the PR is merged, use gstack:/land-and-deploy to land and verify production:
- Merge the PR (if not already merged)
- Wait for CI and deploy to complete
- Run canary health checks against the production URL
- If canary checks fail, flag immediately and halt — do not mark the stage complete
If branch cleanup or alternate closeout handling is needed after shipping, invoke .

Build Review Ship

Inputs

Process

Build Review Ship

Inputs

Process

Output

Github

Openclaw Parallels Smoke

Update Screenshots

Azure Pipelines

Deployment Patterns

Deployment Patterns