fix(deploy): implement release version tagging for VITE_APP_VERSION

Deployment pipeline was computing version sequence (YYYY.MM.DD.N) by
counting existing vYYYY.MM.DD.* git tags, but the pipeline never created
those tags. Result: VERSION_SEQUENCE always resolved to 1, making the
"daily sequence" half of the contract decorative.

Now: After successful deployment to production, pipeline automatically
creates and pushes release tag vYYYY.MM.DD.N.SHA10 (e.g. v2026.08.07.1.abc1234567).
Uniqueness preserved even on same-day re-deploys. Permissions upgraded:
contents: read → write for tag push.

AGENTS.md: Right-Way (root cause fixed, not bandaged).

Ref: DEPLOY_FRONTEND_ARTIFACT_CONTRACT.md section "Bug Fix: Version Sequence Tagging"

Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>

.gitea/workflows/deploy.yml

@@ -7,7 +7,7 @@ on:
   workflow_dispatch:
 
 permissions:
-  contents: read
+  contents: write
 
 jobs:
   deploy:
@@ -107,6 +107,11 @@ jobs:
           # Cleanup
           rm /tmp/deploy_key.pem
 
+      - name: Tag release version
+        run: |
+          git tag "v${VITE_APP_VERSION}"
+          git push origin "v${VITE_APP_VERSION}"
+
   notify:
     if: always()
     needs: deploy

docs/CURRENT/DEPLOY_FRONTEND_ARTIFACT_CONTRACT.md

@@ -20,3 +20,9 @@ YYYY.MM.DD.<당일 release 순번>.<commit SHA 10자리>
 
 - Source 변경과 운영 artifact를 분리하지 않고, 매 배포 시 동일 commit에서 재생성한다.
 - 실제 운영 반영 증거는 이 Slice의 CI 및 deploy run 완료 후 보존한다.
+
+## Bug Fix: Version Sequence Tagging
+
+**Issue:** Version sequence 계산이 `vYYYY.MM.DD.*` git tag 존재를 전제로 카운트하지만, 그 tag를 생성/푸시하는 코드가 없었다.
+**Fix:** 배포 후 release tag `v${VITE_APP_VERSION}` (e.g. `v2026.08.07.1.abc1234567`)를 자동 생성/푸시. 
+**Workflow:** `.gitea/workflows/deploy.yml` - 새 스텝 "Tag release version" 추가; permissions.contents = write.