The prod deploy (deploy-mokogitea.yml, on push to main) failed the #733 release and
silently corrupted the shared compose. Three fixes:
- Removed the 'Verify dev environment is healthy' gate: it curled git.dev and exit 1
on failure, so a dev blip false-negatives the PROD deploy (wrong-tier gate; the
dev->rc->main pipeline + RC env is the real gate).
- Replaced 'sed s|mokogitea:...|:$TAG|' (matched ALL mokogitea service lines and
clobbered the dev+rc ${MOKOGITEA_*_TAG} env-vars with the prod tag) with the
env-var pattern: env $TAG_ENV=$TAG docker compose up -- drives only the target
service, no sed.
- Added 'docker rm -f $CONTAINER' + '-p gitea-dev' + '--force-recreate' before the
compose up, fixing the 'Container name /mokogitea already in use' conflict.
Aligns deploy-mokogitea.yml with the fixed deploy-dev/deploy-rc pattern. Host compose
was separately restored to env-var form (the bad run had clobbered dev+rc tags).
Long-term: cut over Template-Go#5 deploy-prod.yml. Refs #733, #752.
Claude-Session: https://claude.ai/code/session_01Wsno14cxE49MstXFs9G5KT