TODO: Force-deploy pal-e-app after E2E chicken-and-egg test failure

todo-pal-e-app-e2e-deploy-gate Doc

todo done

Project

What: pal-e-app CI pipeline built and pushed the image to Harbor, but the update-deployment-tag step was skipped because 16/61 E2E tests failed. The failures are expected — the tests validate new behavior (public-readiness checks, QuickJot FAB visibility) but the deployed site still has the old code.

Problem: Chicken-and-egg — E2E tests run against the live deployment, but the deployment won't update until tests pass. This pattern always blocks the first deploy of behavior-changing PRs.

Failures (16):

public-readiness tests (10): Check for "Contact Lucas" messaging and no private content, but deployed site still shows private content
quick-jot tests (6): FAB "Create new note" button now correctly hidden for anonymous visitors, but old tests expected it visible

Fix options:

(a) Force deploy: Manually update the kustomize deployment tag to the built image SHA, let ArgoCD sync, then re-run E2E tests. Cleaner.
(b) Skip gate: Mark public-readiness tests as skip-in-CI until first deploy, then enable. More fragile.

Where: pal-e-app repo. Image already built in Harbor. Need to update pal-e-deployments/overlays/pal-e-app/prod/kustomization.yaml with the new tag.