docs(release): complete REL-011 approval evidence

docs/releases/evidence/rel-011_20260717_execution-evidence.md

@@ -5,7 +5,8 @@
 - Service: `trex-core` — `trex-admin-daily-trading`, `genichin-longterm` daemon instances
 - Evidence received: 2026-07-17 KST, `trex-op` reconstructed release-specific execution handoff
 - Evidence sources: immutable git reflog, Supervisor/runtime logs, and secret-free Mattermost terminal capture `20260716_160613_e1fc5e64` (messages `32666`, `32668`, `32670`, `32725`, `32746`–`32758`)
-- Release decision: **Released** — lead `confirm-release` after reviewing this record and the release owner’s closure direction.
+- Approval: Justin Ko — Mattermost message `32675`, `2026-07-16 17:22:50 KST`
+- Release decision: **Released** — lead `confirm-release` after reviewing this record.
 - Secret policy: no credentials, tokens, account identifiers, DSNs, raw broker responses, raw payloads, or full config values are recorded.
 
 ## Immutable release identity
@@ -19,6 +20,8 @@
 ## Approval, preflight, and activation
 
 - The approved-instance preflight record confirms that the existing configuration was retained and that `credential_fetch_enabled` / break-glass semantic state was unchanged.
+- Approval was recorded by Justin Ko in Mattermost message `32675` at `2026-07-16 17:22:50 KST`.
+- The actual pre-deploy rollback revision was captured as `7845fbe856e125e712ac481e36ac582c1a2fe54b`.
 - Reflog correlates checkout from `main` to target `6d90f895…` at `2026-07-16 17:36:42 +0900`.
 - Supervisor records both approved daemon instances stopping cleanly, spawning as PIDs `2014346` and `2014347`, and reaching `RUNNING` at `17:36:47.316 +0900`.
 - Startup runtime interval contains `ERROR=0`, `CRITICAL=0`, and `Traceback=0`; AMQP connection establishment succeeded.
@@ -35,15 +38,14 @@ Secret-free terminal capture window: `2026-07-16 17:40:09.567`–`17:40:14.377 +
 
 No credential/broker-balance error or CLI failure was recorded. `sync --live`, `--yes`, live order, automatic remediation, and manual DB changes were not executed.
 
-## Rollback disposition and accepted evidence limitation
+## Rollback disposition
 
+- Pre-deploy `ROLLBACK_REVISION`: `7845fbe856e125e712ac481e36ac582c1a2fe54b`.
 - Rollback was **not performed**: no stop condition, startup failure, mutation risk, or smoke failure was recorded.
-- The reconstructed evidence preserves the `main → 6d90f895…` checkout transition but does **not** preserve the exact pre-deploy `ROLLBACK_REVISION` SHA; the named user/approver identity is also intentionally absent from the sanitized handoff.
-- These are historical evidence limitations, not a claim that the omitted values were captured. The lead accepts the limitation for this already-completed, no-migration rollout because immutable deployed target, controlled restart, startup health, read-only smoke results, and rollback disposition are independently evidenced. This acceptance is **not** a precedent for future releases: future release records must contain a redacted approval reference and exact rollback SHA before execution.
 
 ## `confirm-release` decision
 
-**Released.** The committed runbook’s completion criteria are satisfied by the immutable target identity, restart evidence, startup acceptance, both read-only smoke results, and a recorded no-rollback disposition. The production live-sync gate remains separate and was not opened by REL-011.
+**Released.** The committed runbook’s completion criteria are satisfied by the explicit approval reference, immutable target identity, captured rollback revision, controlled restart, startup health, both read-only smoke results, and a recorded no-rollback disposition. The production live-sync gate remains separate and was not opened by REL-011.
 
 ## Source records