63 lines
3.6 KiB
Markdown
63 lines
3.6 KiB
Markdown
# K1 LAB acceptance and onboard continuation
|
|
|
|
## Accepted local baseline
|
|
|
|
The owner confirmed a successful local LAB connection after correcting the
|
|
network name. Core independently recorded `network_applied` and DeviceInfo /
|
|
control ready in 8.298 seconds. In the next operator-run session the owner
|
|
reported the usual approximately 20-second calibration, prompt point-cloud
|
|
appearance, visible signal loss after disabling Wi-Fi and successful recovery
|
|
after enabling it again (approximately 20 seconds of waiting). These recovery
|
|
timings are operator observations, not newly instrumented latency measurements.
|
|
They qualify that local run, not every outage duration, a Node reboot or Ubuntu.
|
|
|
|
The owner requested committing and pushing the working implementation and
|
|
resuming K1 Bridge on the paired onboard computer. The backend connection
|
|
read-model extraction, plugin-owned sensor UI, BLE discovery fixes, station
|
|
error messages, camera evidence-root handling, Node enrollment and separate
|
|
viewer-profile discriminators are included in this checkpoint. Earlier audit
|
|
documents retain their original time-scoped validation and limitations.
|
|
|
|
## Spatial scene placement
|
|
|
|
The owner explicitly moved the local test-device live scene from Control to
|
|
LAB. Its operator job is inspection of the current local test stream; source
|
|
selection, acquisition and live settings retain their existing ownership.
|
|
Keeping it under Control would imply the future operational board view; a new
|
|
root or duplicate viewer would add an unnecessary product surface. The existing
|
|
workspace is therefore registered under LAB with its stable `spatial-scene` ID,
|
|
renderer, settings and links intact. Existing sidebar, workspace shell and
|
|
`globe` icon are reused; no new Design Guideline primitive is introduced.
|
|
|
|
Only obsolete Control quick links to that scene are retired on settings read.
|
|
Custom page copy, media and unrelated links remain intact. Default Control
|
|
shortcuts become cameras and map. Home and LAB links can still open the same
|
|
scene. This is an owner-approved relocation, with no Rerun parameter change.
|
|
|
|
## Validation and onboard candidate
|
|
|
|
- Environment migration, Node bridge, connection read-model and Fleet
|
|
enrollment tests passed: 36 cases. Ruff passed for the environment changes.
|
|
- Go package tests passed with the built Node UI embedded and an isolated
|
|
build cache. No system toolchain or package installation was needed.
|
|
- Core architecture/type checks passed. Full frontend run: 784/786 passed;
|
|
the two failures were old LAB workspace-list expectations. Those expectations
|
|
were updated and both affected suites passed; no production change followed.
|
|
- Node 0.7.1 is the next package version so the earlier 0.7.0 candidate is not
|
|
silently replaced. Build provenance now covers the moved K1 frontend sources.
|
|
The 51 K1 and 29 RealSense wheel hashes were verified before reuse.
|
|
|
|
The current paired board was resolved from authenticated Core Fleet data and
|
|
its SSH host key matched the previously trusted Mini key. It runs Node 0.6.11.
|
|
Administrative installation requires the owner's normal Ubuntu authentication;
|
|
non-interactive sudo is unavailable. No password is requested in chat.
|
|
|
|
The exact package, installation result, source commit and final Core UI
|
|
delivery are recorded in a subsequent release addendum after the build.
|
|
Device preparation and real Bridge acquisition must still be accepted through
|
|
both interfaces on that board. Operator and board WLANs remain independent;
|
|
the board owns Bluetooth, network observation, K1 commands and raw data.
|
|
|
|
Ops direct tools are absent in this session. This local report is prepared for
|
|
the K1 and Node cards; no Ops publication is claimed.
|