feat(ci/cd): Implement release-based deployment with two-workflow architecture
- Add prepare-release.yml: Manual release creation workflow
* Builds code, generates appsettings.Production.json
* Packages artifact (.tar.gz)
* Creates git tag and Gitea Release with attached artifact
- Refactor deploy-prod.yml: Release-based deployment workflow
* Fetch Release stage: Query Gitea Releases, download artifact
* Pre-Check stage: Verify SSH credentials and release integrity
* Deploy stage: Upload, extract, symlink, restart service
* Health Check stage: 5-point verification (HTTP, CSS, login, service, release)
* Report stage: Final deployment status
* Now triggered via workflow_dispatch with release version input
* Removes on:push trigger (manual release selection required)
- Update CLAUDE.md:
* Document two-workflow architecture
* Add release creation and deployment procedures
* Update SSH key configuration with GITEA_TOKEN requirement
* Clarify CI/CD-Only Deployment Mandate with release traceability
* Add complete deployment flow documentation
**Motivation**:
- Separate build/release phase from deployment phase
- Enable release tagging for version control and rollback
- Reduce build time on re-deployments (use cached releases)
- Improve deployment auditability via git tags and Gitea Releases
- Match taxbaik-pattern release management strategy
Co-Authored-By: Claude Haiku 4.5 <noreply@anthropic.com>
kjh2064
352b440e8d