docs: record generic monitor fault acceptance
Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
1 parent
5c85f3f0b9
commit
2242643000
3 files changed
+29
-6
No files matched your search
+7
-1
@@ -16,7 +16,11 @@ retry after its cooldown. There is **no strategy selection, recovery or apply**,
|
||||
and no no-strategy two-hour pause. HEALTHY means configured checks passed,
|
||||
not playback health, generic recovery or whole-production READY: HEALTHY is
|
||||
**CHECKS_ONLY**, never READY. The scheduling, status, persistence and lifecycle
|
||||
base is unit/fixture-verified; isolated remote fault acceptance remains pending.
|
||||
base passed native full/race checks, independent security review and isolated
|
||||
remote fault acceptance for `4efc066` plus ownership-status fix `5c85f3f`.
|
||||
See [PROGRESS.md](PROGRESS.md) for supplied evidence and its narrow scope.
|
||||
Version1 is bounded to 16 services / 64 resources with stable configured IDs;
|
||||
valid configuration/state does not imply an automatic strategy assignment.
|
||||
|
||||
Invalid resource JSON initially or after reload is BLOCKED, with no DNS or
|
||||
transfers until repaired. Bad static target role, proxy or DNS settings still
|
||||
@@ -63,4 +67,6 @@ BLOCKED pending operator repair/restart; no unsafe daemon sourcing is allowed.
|
||||
Generic cleanup shares an 80-second budget, including watchdog setup and
|
||||
command kill escalation, with bounded final reaping; it is designed to fit
|
||||
within a 90-second Docker stop limit (the supplied Compose grants 240 seconds).
|
||||
Bounded final reaps/worst-case cleanup were verified offline; measured remote
|
||||
normal stops were 1.45s, 0.59s and 0.57s, not an 80-second runtime worst-case test.
|
||||
These changes do not claim to fix legacy YouTube exit 78.
|
||||
Reference in new issue
Block a user