@ -29,12 +29,22 @@ The login page synchronizes an uninitialized device clock from the PC before log
External NTP/SMTP/authentication availability is separate from local settings application. No-response serial ports may complete observation; every port is not required to be connected. Kernel drivers are unchanged.
External NTP/SMTP/authentication availability is separate from local settings application. No-response serial ports may complete observation; every port is not required to be connected. Kernel drivers are unchanged.
## Latest changes
The API supports configuration-only port reads (`runtime=false`) so loading port configuration does not wait for runtime telemetry. Default port reads retain live telemetry. The frontend queues the most recent navigation while a page initializer is running and loads runtime observations separately from port configuration.
The login progress bar no longer runs an infinite CSS animation. Actual progress, elapsed time, readiness checks and CAPTCHA remain active. This reduces unnecessary rendering load in the device's internal browser.
## Validation
## Validation
Backend startup/API, matched session-service protocol, TLS bootstrap recovery, time service, serial, network, log service/storage and policy tests passed. Frontend login/readiness tests and 10 JavaScript login tests passed. Linux ARM64 builds completed. This release does not claim a cold-boot timing test or full 48-channel traffic validation.
Backend startup/API, matched session-service protocol, TLS bootstrap recovery, time service, serial, network, log service/storage and policy tests passed. Frontend login/readiness tests and 10 JavaScript login tests passed. Linux ARM64 builds completed. This release does not claim a cold-boot timing test or full 48-channel traffic validation.
Replacement-device deployment verified at http://192.168.0.223/ on 2026-09-09: `ready=true`, `completed=12`, `total=12`, `elapsed_ms=34470`. All eight installed SHA256 values matched this manifest. The default-port page served the neutral progress wording and updated cache version. CAPTCHA remains disabled according to this device's existing policy. Login-before-ready and clock bootstrap were validated; no account login credentials were changed.
The latest API and frontend binaries in this directory match the SHA256 values recorded during successful replacement-device deployments on 2026-09-09. The other six binaries are unchanged from the preceding compatible release. This publication updates the repository artifacts; it does not perform another device deployment.
Latest recorded deployment checks: HTTP80, readiness 12/12, CAPTCHA enabled. Configuration-only API tests, frontend handler tests and JavaScript regression checks were completed during the associated changes. The release artifacts were checked for ELF64 AArch64 headers and SHA256 manifest consistency before publication.
The short internal-browser CPU sample after the animation change was 11–14%, compared with 41–44% before it. This is not a long-term or cold-boot guarantee. RCU stall and WCH IRQ95 disablement remain separate unresolved kernel issues. Full 48-channel communication and all external integrations have not been certified by this release.
Rollback backup: `/userdata/tera-backups/replacement-default-port-20260909-112729`. The measured 34.47 seconds includes serial-service restart and its initial observation delay; it is not a full power-cycle measurement.
Deployment evidence is retained locally in `runtime/config-read-transfer.log` and `runtime/static-progress-transfer.log`. Device serial baud 9600 and CAPTCHA enablement are existing device settings, not configuration files included in this binary release.
Binary-only release. Unrelated workspace source changes and runtime files are excluded.
Binary-only release. Unrelated workspace source changes and runtime files are excluded.
gudae
2 months ago