fix(db,deploy): migration safety + release tagging #16

2026-08-07T13:36:19+09:00

kjh2064 commented

2026-08-07 13:36:19 +09:00

Summary

DB Safety (AEG-X-004): Prevent accidental drop of kartsell_migration_test by guarding credential source. Distinct test DB (kartselldb_test) vs rehearsal DB avoids config collision.
Deploy Bug (Release Tagging): Pipeline was computing version sequence by counting git tags but never created them. Now auto-tags releases as vYYYY.MM.DD.N.SHA10.

AGENTS.md Compliance

Necessity-driven (real safety fix + root-cause bug fix)
Right-way (no shortcuts, actual tagging logic added)

## Summary - **DB Safety (AEG-X-004):** Prevent accidental drop of kartsell_migration_test by guarding credential source. Distinct test DB (kartselldb_test) vs rehearsal DB avoids config collision. - **Deploy Bug (Release Tagging):** Pipeline was computing version sequence by counting git tags but never created them. Now auto-tags releases as vYYYY.MM.DD.N.SHA10. ## AGENTS.md Compliance - Necessity-driven (real safety fix + root-cause bug fix) - Right-way (no shortcuts, actual tagging logic added)

kjh2064 added 2 commits 2026-08-07 17:14:09 +09:00

fix(db): prevent migration-test database drop + correct AEG-X-004 evidence f0a945ab96

Tests now guard against accidental drop of kartsell_migration_test by throwing
when the credential source DB is the destructive rehearsal target. Distinct
credential DB (kartselldb_test) prevents config collision.

AEG-X-004 evidence consolidated: rehearsal .trx files + preflight markdown
documented. Schema 0032 (shadow_run_queued_status_contract) verified
fresh/upgrade/recovery on isolated DB.

AGENTS.md: Necessity-driven (guard against destructive accident); no new feature.

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

fix(deploy): implement release version tagging for VITE_APP_VERSION 63a95c9242

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>

kjh2064 force-pushed fix/deploy-build-frontend-artifact from 562163f48c to 63a95c9242

2026-08-07 17:14:09 +09:00

Compare

kjh2064 merged commit 907ab937f4 into main

2026-08-07 17:14:44 +09:00

Sign in to join this conversation.

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: kjh2064/KArtSell.Aegis#16