From 6a36febfebe3597b1649f8a8cce3d0c061b00123 Mon Sep 17 00:00:00 2001 From: igor04091968 Date: Fri, 8 May 2026 08:15:53 +0300 Subject: [PATCH] docs: capture todo - deploy standalone agent on SHARKON2025 --- ...t-on-sharkon2025-and-validate-live-flow.md | 20 +++++++++++++++++++ 1 file changed, 20 insertions(+) create mode 100644 .planning/todos/pending/2026-05-08-deploy-standalone-agent-on-sharkon2025-and-validate-live-flow.md diff --git a/.planning/todos/pending/2026-05-08-deploy-standalone-agent-on-sharkon2025-and-validate-live-flow.md b/.planning/todos/pending/2026-05-08-deploy-standalone-agent-on-sharkon2025-and-validate-live-flow.md new file mode 100644 index 0000000..8cb3a8c --- /dev/null +++ b/.planning/todos/pending/2026-05-08-deploy-standalone-agent-on-sharkon2025-and-validate-live-flow.md @@ -0,0 +1,20 @@ +--- +created: 2026-05-07T21:46:00Z +title: Deploy standalone agent on SHARKON2025 and validate live flow +area: tooling +files: + - windows/installkit/innosetup/AWatch-rus-InnoSetup.iss + - windows/install-standalone-service.ps1 + - windows/aw-standalone-service.ps1 + - windows/installkit/innosetup/BUILD.md + - docs/windows/deployment.md + - docs/windows/troubleshooting.md +--- + +## Problem + +Standalone InnoSetup mode and service wrapper are implemented and pushed, and AW API write path was verified by manual heartbeat posts. But production value still depends on real endpoint rollout: installer must be deployed on SHARKON2025 (192.168.100.21), service must be running persistently, and UI/API must show continuously fresh events without manual seeding. + +## Solution + +Deploy the newly built installer `AWatch-rus-InstallKit.exe` to SHARKON2025, run installation with target `10.10.10.13:5600`, verify `AWatchRusStandaloneAgent` state, inspect `standalone-agent-service.log`, and confirm fresh `metadata.end` progression for `aw-dlp-endpoint-signals_SHARKON2025`, `aw-file-operations_SHARKON2025`, and `aw-worktime-sessions_SHARKON2025` over time.