feat(monitor): wire isolated target recovery

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-10 09:45:34 +03:00
1 parent 2d4e4878ae
commit 5f3a6953ee
16 files changed
+1919 -73

No files matched your search

+11 -8
View File
@@ -1,7 +1,7 @@
# Isolated managed-test definition — deployment deferred
This definition is **not autonomous acceptance-ready**: no `managed monitor`
or integrated recovery loop exists. Do not build/pull/start it as part of this
This definition is **not autonomous acceptance-ready**: `managed monitor` and
entrypoint recovery integration exist in code but are not live verified. Do not build/pull/start it as part of this
change. Existing containers, production and Xray configuration are out of scope.
For a later approved deployment, from this directory:
@@ -61,10 +61,11 @@ or host filesystem restrictions.
Go builder matches `Dockerfile`; runtime digest is pinned and image-owned
Lua/fakes retained. Startup: ss-server/ss-local → internal listener 1080
(30-second bound) → guarded managed init on fresh state (status on recreation)
→ zapret2 start using target config. Drift/pending state refuses startup;
no automatic adoption/reconciliation. SIGTERM/SIGINT stop only target-local
zapret firewall and the entrypoint's own Shadowsocks children. Process
supervision is **not** health/recovery; no restart policy hides fail-closed exits.
→ zapret2 start using target config → one installed managed monitor child. Drift/pending state refuses startup;
no automatic adoption of unknown state. SIGTERM/SIGINT cancels and waits the monitor
before stopping target-local zapret and the entrypoint's Shadowsocks children.
Monitor fatal exits stop the entrypoint; no restart policy hides fail-closed exits.
Monitor probes Player API via owned loopback SOCKS; unresolved GGC is not playback health.
Inside target, `zapret-autotune health youtube` uses
`socks5://127.0.0.1:1080`, never the host port. It is one-shot Player API health,
@@ -79,5 +80,7 @@ the `tpws` user drop). Prove target-local routing,
NFQUEUE activation/rollback, signal cleanup and persistent recreation on the
new target only. Compose syntax, build and runtime integration are unverified
by this producer. Do not widen capabilities or reuse existing config/network
as a workaround. Autonomous acceptance also needs monitor/recovery integration
and crash reconciliation.
as a workaround. Autonomous acceptance also needs tests/build and live verification
of monitor/recovery and crash reconciliation, including shutdown grace sufficient
for bounded restoration (which may exceed the defined 45s). Docker configuration
has not been changed by this code integration increment.