Claude should follow basic deployment workflow: deploy before asking user to verify

Problem

When modifying server-side files (e.g., PHP language files served via API), Claude pushes code to the repo but then immediately asks the user to refresh the browser to verify — without confirming the server has pulled the latest code.

This is basic programmer workflow: push → deploy → verify. Claude skips the deploy step, the verification obviously fails, and Claude misdiagnoses it as a "cache problem", wasting multiple rounds tweaking cache version numbers and localStorage clearing logic — when the real issue is simply that the server hasn't been updated.

Example scenario

1. Added a new translation key nav_settings to PHP language files
2. The frontend loads translations via API (/lang/zh-CN) from server-side PHP files
3. Claude pushed the code and told me to refresh the browser
4. The translation key showed as raw key name because the server hadn't pulled the new code
5. Claude then spent multiple rounds bumping LANG_VERSION, modifying cache logic, and eventually hardcoding the string — all unnecessary if it had simply reminded me to deploy first

Expected behavior

After pushing code that includes server-side changes, Claude should remind the user to deploy (e.g., git pull on the server) before asking them to verify. This is a fundamental software development workflow that should not require per-project memory or repeated user correction.

Impact

Wastes significant user time on false debugging cycles and can lead to unnecessary code changes (like bypassing a perfectly working translation system by hardcoding strings).

🤖 Generated with Claude Code