Both binary SHA-256 hashes match the installed executables on 192.168.0.223. The frontend was deployed and its service readiness and served JavaScript verified on 2026-09-08. The backend is the existing installed binary.
Both binaries were deployed together to 192.168.0.223. Installed hashes matched SHA256SUMS. Readiness returned 7/7 completed stages, ready=true, and elapsed_ms=1593 during an API service restart. CAPTCHA PNG issuance and the updated login script were verified. This was not a cold-boot timing test.
The frontend adds persistent firmware upload progress, validation/apply/reboot status, automatic status polling after reconnection, and duplicate submission prevention. Completion is displayed only after the device reports success. Alt-clicking a tab close button keeps only the dashboard. Existing CAPTCHA behavior is retained.
Login is enabled only after required configuration and service checks succeed. Errors are actually retried with a three-second pause; after 25 seconds an unfinished stage is shown as delayed. Calls never overlap if a device operation stops responding. Delayed stages still block login and automatically recover on success. Detailed errors remain in API logs. The progress bar represents completed stages, not estimated remaining time.
Validation: 4 firmware progress tests and 9 workspace tab tests passed; Linux ARM64 build passed. A full firmware flash was not performed for this UI release. The device's last inspected firmware journal still recorded the earlier minimum-version validation failure; this web deployment does not resolve firmware package compatibility.
The CAPTCHA area explains the wait while startup is pending. The actual challenge is issued only after readiness and enabled-policy confirmation, avoiding expiry during startup. Existing firmware progress and login security remain included. Serial capture configuration is batched below the control socket request-size limit.
Verify file integrity from this directory with `sha256sum -c SHA256SUMS`. Install executable files with mode `0755`.
IMPORTANT: During validation the device clock was 1970-01-01, causing TLS certificate validity errors and repeated initialization attempts. The device system clock was synchronized to the host's current UTC time before successful validation. Persistence of time across power loss/RTC/NTP remains unverified. Retry does not fix an incorrect clock or the previously observed WCH kernel RCU/IRQ fault.
This bundle contains only the web and API executables, not a complete firmware image. It requires the compatible device services and configuration already installed on the target. Runtime data, credentials, and private keys are not included. Source changes are not included in this binary-only commit.
Install both files together with mode 0755; an older API lacks the readiness endpoint required by this frontend. Verify with `sha256sum -c SHA256SUMS`.
Validation: backend startup/API tests, frontend login/readiness tests, 9 JavaScript login tests, and Linux ARM64 builds passed. The broader frontend handler suite has previously observed unrelated asset-version expectation failures. No full firmware flash or complete 48-channel traffic test was performed.
Device rollback backup: `/userdata/tera-backups/login-ready-20260909-101038` (api and web).
This is a binary-only release; source changes, runtime data, credentials and private keys are not included. It requires the existing compatible device services and configuration.
gudae
2 months ago