TODO: Rewire ArgoCD to use pal-e-deployments repo

todo-argocd-rewire-deployments-repo Todo

todo done

Project

ArgoCD for pal-e-docs points at pal-e-docs/k8s/ (the app repo) instead of the deployments repo with kustomize overlays. This means:

Image tags are hardcoded in the app repo's k8s/deployment.yaml
The deployments repo with proper kustomize bases/overlays is completely unused
The Image Updater (when fixed) would need to patch the app repo, not the deployments repo
GitOps separation of concerns is broken — app repo owns deployment config

What	Current	Target
ArgoCD source	<code>forgejo_admin/pal-e-docs</code> path <code>k8s/</code>	<code>forgejo_admin/pal-e-deployments</code> path <code>overlays/pal-e-docs/prod/</code>
Image tag management	Hardcoded in app repo	Updated in deployments repo by CI or Image Updater
Repo name	<code>deployments</code>	<code>pal-e-deployments</code> (naming convention)

Rename repo: forgejo_admin/deployments → forgejo_admin/pal-e-deployments
Clean up kustomization: Remove Litestream-era artifacts (litestream-configmap.yaml, pvc.yaml). Update deployment patch to match current Postgres-based deployment.
Update ArgoCD Application: Change spec.source.repoURL and spec.source.path to point at the deployments repo overlay.
Verify sync: Confirm ArgoCD syncs from the new source and deployment matches.
Remove k8s/ from pal-e-docs: Once ArgoCD reads from deployments, the app repo no longer needs k8s/.
Update CI: Woodpecker build-and-push should update the image tag in the deployments repo (or Image Updater does this when fixed).

ArgoCD reads deployment config from pal-e-deployments repo
pal-e-docs repo has no k8s/ directory
Image tag updates happen in the deployments repo, not the app repo
Deployment works end-to-end: merge → CI builds → deployments repo updated → ArgoCD syncs