wip(k1): checkpoint connection recovery rewrite

Capture the current unreleased K1 connection, recovery, lifecycle, viewer, and test work as a single known-bad baseline for subsequent fixes.
This commit is contained in:
DCCONSTRUCTIONS
2026-08-14 14:57:50 +03:00
parent aff331082f
commit 0ca7316a24
157 changed files with 152962 additions and 4036 deletions
+10 -4
View File
@@ -6,17 +6,23 @@ generic application source tree.
The contribution contains:
- `K1ProvisioningPipeline` for power confirmation, BLE discovery and the three
explicit local connection directions: Bridge, Quick Connect and Direct
Connect;
- `K1ProvisioningPipeline` for explicit BLE discovery and the three local
connection directions: Bridge, Quick Connect and Direct Connect;
- `K1AcquisitionPipeline` for explicit canonical connection/workspace/project/
START checkpoints, local receiver preparation and compatibility file replay;
- `K1SpatialControls` for an explicit no-retry STOP followed by the separate
READY plus steady-green completion gate;
- plugin-local diagnostics, metrics, API state, lifecycle mapping,
observation-source mapping and scoped styles;
- typed v0.6.0 local-network and interactive application-control state plus legacy shadow
- typed v0.7.0 supervised connection lifecycle and interactive application-control state plus legacy shadow
inspection contracts;
- a click-correlated, non-secret provisioning presentation latch: after Apply,
Steps 01–02 keep their selected-device/form anatomy with disabled controls
until the exact connection attempt becomes reachable or reaches bounded
recovery; the Wi-Fi password is cleared before asynchronous dispatch;
- policy-gated retirement of an unavailable historical K1 as an explicit
local ledger action; it never emits a device command and never bypasses the
public `retire-unavailable-physical-target` decision;
- `plugin.ts`, which binds the manifest `device.connection` component key to
the runtime provider and connection view.