docs: project docs, scripts, deployment configs, and evidence

docs/evidence/ops/2026-03-24/rollback/20260324-084928/ROLLBACK_DRILL.md

@@ -0,0 +1,32 @@
+# Rollback Drill
+
+- Generated at: 2026-03-24 08:49:39 +08:00
+- Source DB: D:\project\data\user_management.db
+- Stable DB copy: D:\project\docs\evidence\ops\2026-03-24\rollback\20260324-084928\user_management.stable.db
+- Probe port: 18087
+
+## Drill Result
+
+- Stable release started successfully before rollback gate evaluation.
+- Candidate release was rejected by release-mode runtime validation before becoming healthy.
+- Rollback to the previous stable config/artifact path completed successfully on the same probe port.
+- Candidate rejection evidence: stderr matched release validation failure
+- Stable capabilities before rollback: {"password":true,"email_code":false,"sms_code":false,"password_reset":false,"oauth_providers":[]}
+- Stable capabilities after rollback: {"password":true,"email_code":false,"sms_code":false,"password_reset":false,"oauth_providers":[]}
+
+## Scope Note
+
+- This local drill validates rollback operational steps and health gates for the current artifact/config path.
+- It does not prove cross-version schema downgrade compatibility between distinct historical releases.
+
+## Evidence Files
+
+- config.stable.yaml
+- config.candidate.yaml
+- stable-initial.stdout.log
+- stable-initial.stderr.log
+- candidate.stdout.log
+- candidate.stderr.log
+- stable-rollback.stdout.log
+- stable-rollback.stderr.log
+