Guard against web deploy rollback from divergent worktrees

t-684·WorkTask·
·
·
Created1 month ago·Updated1 month ago·pipeline runs →

Dependencies

Description

Edit

Observed deployment confusion where live and ava worktrees diverged (ava lacked Omni/Web.hs and new Fund overview modules), making it possible for stale deploys to overwrite newer web behavior. Add safeguards so web deploys cannot silently roll back due cross-worktree drift (e.g., enforce deploy source branch/worktree consistency, or validate expected routes/version marker before manifest update).

Timeline (2)

🔄[human]Open → InProgress1 month ago
🔄[human]InProgress → Open1 month ago