feat(managed): add explicit experimental Googlevideo suffix policy

Keep operator-owned native circular extrapolation distinct from cold/adaptive qualification and playback readiness. Preserve qualified frontend/assets, use guarded journal transactions and rollback, and apply private startup requests before the owned monitor begins. Retain legacy rendering and qualification gates.

Co-authored-by: GPT-6 <gpt-6@openai.com>
This commit is contained in:
ZeusinaandGPT-6 Bot committed 2026-10-12 07:04:12 +03:00
1 parent 0398e6fe28
commit 371382c2c4
10 files changed
+386 -9

No files matched your search

+30
View File
@@ -388,3 +388,33 @@ do not attribute all of them to the clean run. No media playback, real 90-minute
watchdog expiry or real two-hour absence expiry wait is claimed. Production rollout
and backup-restore acceptance remain operator gates on a new isolated target;
local unit/static checks and isolated PASS do not establish blanket production readiness.
### Explicit experimental Googlevideo suffix
Normal `--googlevideo-scope suffix` still requires representative qualification,
media proof, and both qualified image profiles. An operator may explicitly own
the audited native circular A/E composite without claiming those results:
```sh
zapret-autotune managed apply --googlevideo-experiment native-circular --googlevideo-scope experimental_googlevideo_suffix
```
This command requires the monitor singleton to be free, a matching native Lua
hash, a fresh Player-discovered exact GGC identity, and existing qualified
frontend/assets. It preserves their candidate IDs and uses the normal guarded
transaction/reload/Player-health/rollback hooks. The new candidate definition
has no cold/adaptive evidence and is not a qualified candidate. Both pending
and committed journal policy record `experimental_googlevideo_suffix`; legacy
rendered bytes and qualification gates are unchanged. Unknown policies fail closed.
For PID-1-controlled application, while this dedicated target is stopped and
after taking a complete private state backup, create a private empty file named
`.autotune-experimental-suffix-request` in its owned state directory. Startup
reconciles/starts the known deployment, performs the command before launching
the monitor, and consumes the request only on success. Failure exits closed;
retain artifacts and use the matched whole-state/image rollback procedure above.
Resource probes still run. This policy remains `DEGRADED`/GGC-unresolved even
when a bounded media check succeeds: neither playback READY nor family
qualification is inferred. Automatic frontend/image repairs preserve the
operator suffix; automatic GGC recovery does not replace or qualify it.