teraWeb/final-build

Final device builds

Release: 20260909-config-read-static-progress-1 Target: Linux ARM64 (RK3568) UI: http://192.168.0.223/ — HTTP port 80.

Replacement device install mapping

Release file	Installed path	Existing init service
frontend/tera-clone-demo-web	/usr/bin/tera-clone-demo-web	S61teraweb
backend/tera-clone-demo-api	/usr/bin/tera-api	S50tera-api
backend/tera-timed	/usr/bin/tera-timed	S45tera-timed
backend/tera-clone-demo-alarmd	/usr/bin/tera-alarmd	S47tera-alarmd
backend/tera-seriald	/usr/bin/tera-seriald	S40tera-seriald
backend/tera-logd	/usr/bin/tera-logd	S44tera-logd
backend/tera-sessiond	/usr/bin/tera-sessiond	S55tera-sessiond
backend/tera-netd	/usr/bin/tera-netd	S43tera-netd

The API/alarm release filenames retain the clone-demo naming; this replacement device uses the standard API/alarm install paths above. Install all eight compatible binaries together with mode 0755. Verify sha256sum -c SHA256SUMS before installation. Back up installed binaries and stop services before replacement.

Preserve /etc/tera/teraweb.env: PORT=80, API upstream http://127.0.0.1:8082, session upstream http://127.0.0.1:8081. Keep the existing S61teraweb service. Do not install the previous device's port-8083 web environment or duplicate API services. Device configuration, accounts, private keys and serial mapping are not included in this release.

Readiness

Login remains blocked until all 12 startup stages finish: settings restore, TLS, SNMP, management access, serial configuration, service health, time/NTP settings, network settings, notification/authentication policies, log retention, fresh port observations, and port services. The UI uses neutral “설정 중…” wording and the normal progress color throughout initialization, including retries. Progress and elapsed time remain visible; delayed stages cannot be counted as complete. Detailed startup errors remain in device logs.

The login page synchronizes an uninitialized device clock from the PC before login. Factory certificates created before year 2000 are reissued after clock recovery, retaining their key and subject. User certificates and normally dated expired certificates are not automatically replaced.

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

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.

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.

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.