refactor: reuse embedded startup phase boundaries (#3640)

This commit is contained in:
安正超
2026-06-20 06:58:48 +08:00
committed by GitHub
parent f8117eb46b
commit 131e9dc804
5 changed files with 188 additions and 126 deletions
+8
View File
@@ -81,6 +81,14 @@ outbound TLS publication, generation recording, and TLS metrics initialization.
`startup_runtime` still owns BOOT-006 ordering and must preserve the fatal
boundary when configured TLS material fails to load.
## Embedded Startup Phase Reuse
Embedded startup should use the same startup server and storage phase owners for
listen context, endpoint/local disk setup, storage runtime setup, readiness
publication, and replication startup. Embedded-specific behavior still owns its
stable-port requirement, one-shot global initialization guard placement, S3-only
HTTP listener, and non-fatal KMS/audit/notification policy.
## AppContext Foundation
Early AppContext work should split resolver files and add compatibility tests before