@letitbexai_root/lexxit-automation-framework 1.0.7 → 1.0.8

package/package.json

@@ -1,6 +1,6 @@
 {
   "name": "@letitbexai_root/lexxit-automation-framework",
-  "version": "1.0.7",
+  "version": "1.0.8",
   "description": "Playwright test execution framework with Express API for test execution and reporting.",
   "publishConfig": {
     "access": "public"

package/scripts/deploy/windows/install-lexxit-agent.ps1

@@ -117,6 +117,7 @@ Copy-Item -Path (Join-Path $PSScriptRoot "*.ps1") -Destination $permanentScripts
 # -- 1. The lexxit-runner account --------------------------------------------
 $securePwd = ConvertTo-SecureString $RunnerPassword -AsPlainText -Force
 $existingUser = Get-LocalUser -Name $RunnerUsername -ErrorAction SilentlyContinue
+$isNewRunnerAccount = -not $existingUser
 if (-not $existingUser) {
     Write-Host "[lexxit] Creating local user $RunnerUsername..."
     # New-LocalUser's -Description has a hard 48-char cap (a SAM user-account
@@ -473,3 +474,31 @@ Write-Host "  Agent port:        $AgentPort"
 Write-Host "  VNC port:          5900 (TightVNC, service mode)"
 Write-Host "  Scheduled task:    $taskName (At log on of $RunnerUsername)"
 Write-Host "  NOT validated against a real Windows EC2 AMI yet - test every step above before relying on it in production."
+
+# -- 11. Reboot once, automatically, if this is a brand-new runner account --
+# AutoAdminLogon (both the registry fallback above and Sysinternals'
+# autologon.exe) only takes effect at Windows's own boot-time logon prompt -
+# neither can retroactively log an already-running Windows session into a
+# different user. So on a first-time install, lexxit-runner has never
+# actually had an interactive desktop session, which is why Live View (VNC)
+# shows the Windows lock/login screen instead of a usable desktop, even
+# though the agent task itself already reports healthy (confirmed on a real
+# VM: Start-ScheduledTask against an "At log on" trigger for a user who has
+# never logged on still manages to run something that answers /api/health,
+# just not inside a real lexxit-runner desktop session - so the health
+# check above is not a reliable signal that VNC will show anything useful).
+# One automatic reboot here closes that gap completely: the VM comes back
+# up with lexxit-runner already logged in for real, VNC shows its actual
+# desktop, and this never needs a human to remember "oh, it needs a
+# reboot" again. Skipped when lexxit-runner already existed (e.g. a
+# version/password-only re-run on an already-live agent) - no reason to
+# bounce a VM that's already working.
+if ($isNewRunnerAccount) {
+    Write-Host ""
+    Write-Host "[lexxit] $RunnerUsername was just created, so this VM needs one reboot for its auto-logon to"
+    Write-Host "         actually take effect - that's expected, not a failure. Rebooting now; give it a"
+    Write-Host "         couple of minutes, then check Lexxit -> Administration -> VM Agents - Live View"
+    Write-Host "         should show a real desktop instead of the lock screen once it's back."
+    Start-Sleep -Seconds 5
+    Restart-Computer -Force
+}