chore(ci): simplify Trigger release workflow

[TheodoreSpeaks]

Summary

• Use shared Trigger preparation and promotion jobs for every release environment, passing the selected target and uploaded version between them.
• Preserve migration and image gates, traffic-cutover verification, and each environment's credential session and polling budgets.
• Remove the standalone deployment test harness and its CI step.

Type of Change

• Other: CI simplification

Testing

• Actionlint and Bash syntax checks pass; no workflow references the removed test file.
• Repository lint, all 46 audits, block-registry and generated-artifact checks pass.

Checklist

• Code follows project style guidelines
• Self-reviewed my changes
• Tests added/updated and passing (not applicable: the deployment test harness is removed)
• No new warnings introduced
• I confirm that I have read and agree to the terms outlined in the Contributor License Agreement (CLA)

[vercel]

The latest updates on your projects. Learn more about Vercel for GitHub.

Project	Deployment	Actions	Updated
docs	Ready	Preview	Sep 17, 2026 1:11am UTC

[cubic-dev-ai]

No issues found across 2 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}

[TheodoreSpeaks]

@greptile

[TheodoreSpeaks]

@cubic-dev-ai review this PR

[cubic-dev-ai]

@cubic-dev-ai review this PR

@TheodoreSpeaks I have started the AI code review. It will take a few minutes to complete.

[greptile-apps]

Confidence Score: 4/5

The workflow consolidation appears behaviorally sound, but the loss of its dedicated regression suite is a non-blocking maintainability and release-safety concern.

Findings

1.  Deployment Tests Removed ▶

Summary

This PR consolidates environment-specific Trigger.dev release jobs into shared preparation and promotion jobs while retaining branch-specific targets, AWS credentials, deployment pipelines, and timeout budgets.

• Selects prod, staging, or preview/dev-sim once during preparation and propagates that target with the deployment version.
• Keeps image promotion behind the relevant migration, build, and Trigger preparation gates.
• Verifies ECS traffic cutover before promoting the parked Trigger.dev version.
• Removes the only automated regression harness for this deployment and release-ordering behavior.

Diagram

%%{init: {'theme': 'neutral'}}%%
flowchart LR
  Ref[Push to main, staging, or dev] --> Prepare[Prepare Trigger.dev version]
  Ref --> Migrate[Environment migration]
  Ref --> Build[Environment image build]
  Prepare --> PromoteImages[Promote image tags]
  Migrate --> PromoteImages
  Build --> PromoteImages
  PromoteImages --> Cutover[Verify ECS traffic cutover]
  Prepare --> PromoteTrigger[Promote prepared Trigger.dev version]
  Cutover --> PromoteTrigger

Loading

_{Reviews (2) · Last reviewed commit: "chore(ci): remove Trigger deployment tes..."}

[cubic-dev-ai]

No issues found across 3 files

Confidence score: 5/5

• Automated review surfaced no issues in the provided summaries.
• No files require special attention.

_{Re-trigger cubic}