name	writefluency-deploy
description	WriteFluency production deployment workflow for committing staged changes, pushing master, creating service version tags, and pushing those tags to trigger GitHub Actions deploys. Use when the user asks to deploy, push to production/prd, trigger production deploys, release staged changes, or create/push deploy tags for WriteFluency services.

WriteFluency Deploy

Use this workflow for production deploys from /Users/mateusmedeiros/Desktop/repos/WriteFluency.

git status --short --branch
git diff --cached --stat
git diff --cached --name-only

Commit only staged changes unless the user explicitly asks to stage more. If there are no staged changes, stop and tell the user.

src/propositions-service/** or tests/propositions-service/** -> propositions-v*
src/webapp/** -> webapp-v*
src/users-service/** or tests/users-service/** -> users-v*
src/users-progress-service/**, tests/users-progress-service/**, or infra/users-progress/** -> check workflows before tagging; current workflows use users-v* for deploy-users-progress.yml, despite historical users-progress-v* tags.
.github/workflows/deploy-*.yml, src/host/WriteFluency.AppHost/deploy-k8s.sh, or src/host/WriteFluency.AppHost/aspirate-overlays-* -> inspect workflows and ask if service tags are not obvious.

rg -n "tags:|propositions-v|webapp-v|users-v|users-progress-v" .github/workflows
git tag --sort=-creatordate | head -n 30

Choose the next patch version for each affected service. Examples:

git commit -m "<message>"

git push origin master

git tag <service-vX.Y.Z> HEAD
git push origin <service-vX.Y.Z> [<another-service-vX.Y.Z>...]

git status --short --branch
git log --oneline -n 3 --decorate
git ls-remote --tags origin <tag-1> <tag-2>

Do not rewrite, delete, or move existing tags.
Do not run git reset, git checkout --, or otherwise discard work.
Do not commit unstaged changes unless the user explicitly asks.
If staged changes span multiple services, create one tag per affected service after pushing the commit.
If the branch is not master, ask before proceeding unless the user explicitly requested the current branch.
If origin/master has new commits, pull/rebase only after telling the user what will happen.
If tests were not already run in the session, run focused tests when the staged changes include code, unless the user asked for a fast deploy.

As of the current repo workflow, production deploys are triggered by:

name	writefluency-deploy
description	WriteFluency production deployment workflow for committing staged changes, pushing master, creating service version tags, and pushing those tags to trigger GitHub Actions deploys. Use when the user asks to deploy, push to production/prd, trigger production deploys, release staged changes, or create/push deploy tags for WriteFluency services.

Use this workflow for production deploys from /Users/mateusmedeiros/Desktop/repos/WriteFluency.

git status --short --branch
git diff --cached --stat
git diff --cached --name-only

Commit only staged changes unless the user explicitly asks to stage more. If there are no staged changes, stop and tell the user.

src/propositions-service/** or tests/propositions-service/** -> propositions-v*
src/webapp/** -> webapp-v*
src/users-service/** or tests/users-service/** -> users-v*
src/users-progress-service/**, tests/users-progress-service/**, or infra/users-progress/** -> check workflows before tagging; current workflows use users-v* for deploy-users-progress.yml, despite historical users-progress-v* tags.
.github/workflows/deploy-*.yml, src/host/WriteFluency.AppHost/deploy-k8s.sh, or src/host/WriteFluency.AppHost/aspirate-overlays-* -> inspect workflows and ask if service tags are not obvious.

rg -n "tags:|propositions-v|webapp-v|users-v|users-progress-v" .github/workflows
git tag --sort=-creatordate | head -n 30

Choose the next patch version for each affected service. Examples:

git commit -m "<message>"

git push origin master

git tag <service-vX.Y.Z> HEAD
git push origin <service-vX.Y.Z> [<another-service-vX.Y.Z>...]

git status --short --branch
git log --oneline -n 3 --decorate
git ls-remote --tags origin <tag-1> <tag-2>

Do not rewrite, delete, or move existing tags.
Do not run git reset, git checkout --, or otherwise discard work.
Do not commit unstaged changes unless the user explicitly asks.
If staged changes span multiple services, create one tag per affected service after pushing the commit.
If the branch is not master, ask before proceeding unless the user explicitly requested the current branch.
If origin/master has new commits, pull/rebase only after telling the user what will happen.
If tests were not already run in the session, run focused tests when the staged changes include code, unless the user asked for a fast deploy.

As of the current repo workflow, production deploys are triggered by:

writefluency-deploy