docs: record remote acceptance upload blocker

This commit is contained in:
Zeusina committed 2026-10-10 10:12:42 +03:00
1 parent 2fbb247a1e
commit c19c4ffbd9
1 file changed
+2 -1
+2 -1
View File
@@ -4,7 +4,8 @@
## Готово
- Добавлены `managed monitor` и supervision только dedicated target entrypoint: guarded target-owned DB/identity до singleton, policy 5m/3/30m с bounded CLI/env validation, owned-loopback Player API probe/discovery без direct fallback, fixed blockcheck/zapret argv с context cancellation/join. Startup bootstrap только без qualified active frontend, saved-first recovery; GGC unresolved продолжает мониторинг, DB/safety errors fatal. SIGTERM ждёт monitor restoration до zapret/SS stop. Добавлены local fake CLI/entrypoint tests. Tests/build/network не запускались; verification deferred orchestrator. Docker/remote/existing target/Xray не менялись. Нижние пункты описывают предшествующие increments, не отменяют эту интеграцию.
- **2026-10-10 update:** switched the new target password to Compose environment input (`SS_PASSWORD`), removed `DAC_OVERRIDE` and secret-file mount, and clear the variable before launching child processes. Commit: `558b215`; local `go test ./...`, build, Compose config, static deploy guard and entrypoint syntax passed. Remote read-only checks found Docker 29.8.2, the old target still running untouched, and host SOCKS port 11080 free. No target/state was created. Remote deployment is currently blocked because SSH MCP `sftp-upload-file` has no configured `defaults.transferRoot`; direct SCP is unavailable. Configure its transfer root as `/tmp/opencode` (or provide another upload path) to continue the full fresh-target acceptance.
- Added `managed monitor` and supervision only in the dedicated target entrypoint: guarded target-owned DB/identity before singleton, policy 5m/3/30m with bounded CLI/env validation, owned-loopback Player API probe/discovery without direct fallback, fixed blockcheck/zapret argv with context cancellation/join. Startup bootstraps only without a qualified active frontend, tries saved scenarios first, then scans; unresolved GGC keeps monitoring; safety/DB errors stop it. SIGTERM waits for monitor restoration before stopping target-local zapret/SS. Local fake CLI/entrypoint tests are present. Live remote behavior remains unverified; the existing target and Xray are unchanged.
- Hardened managed recovery artifacts: общий `revalidateCandidate` удаляет старый combined JSON перед каждым check, remove errors/missing/malformed report fail closed; scan shortlist проверяется на regular file и mtime не раньше whole-second scan start (production использует unique temp path). Добавлены fake-only regression tests stale/missing shortlist, stale combined, remove failure и infrastructure classification/restoration. Tests/build/network не запускались; verification deferred orchestrator, CLI/entrypoint не добавлены.