docs(release): capture REL-011 feedback

This commit is contained in:
Hermes Agent
2026-07-17 17:30:19 +09:00
parent 0929f9300b
commit 8f33a83bf6
@@ -84,3 +84,9 @@ Rollback target is the **actual pre-deploy revision captured in the operational
**Released.** The release-specific evidence records the immutable target revision, controlled restart, startup health, both required read-only smoke checks, no-write boundary, and no-rollback disposition. The retained limitations (exact historical rollback SHA and named approval identity absent from sanitized evidence) are explicitly recorded in the [execution evidence](evidence/rel-011_20260717_execution-evidence.md) and accepted only for this reconstructed historical rollout. **Released.** The release-specific evidence records the immutable target revision, controlled restart, startup health, both required read-only smoke checks, no-write boundary, and no-rollback disposition. The retained limitations (exact historical rollback SHA and named approval identity absent from sanitized evidence) are explicitly recorded in the [execution evidence](evidence/rel-011_20260717_execution-evidence.md) and accepted only for this reconstructed historical rollout.
This decision does not authorize live sync, configuration activation, remediation, DB changes, or deployment of other M5 services. This decision does not authorize live sync, configuration activation, remediation, DB changes, or deployment of other M5 services.
## Release feedback
- **Operational outcome:** the reconstructed record shows a clean controlled restart, no startup fatal log, and successful read-only smoke for both approved instances; no release-scope rollback or incident was recorded.
- **Process debt:** the historical record lacked an exact pre-deploy rollback SHA and named approval identity in its sanitized form. The limitation was accepted only for this completed historical rollout.
- **Next Discovery input:** establish a release-evidence capture standard that records a redacted approval reference, exact rollback revision, instance identity, per-command timestamp/exit/result/no-write classification, and rollback disposition before a future release gate is closed.