feat(k1): wire canonical control session to UI
This commit is contained in:
@@ -39,14 +39,13 @@ capture verifies the `ModelingRequest` topic, action values, field layout,
|
||||
literal `{device_id}:ModelingRequest` session relation, retained start settings
|
||||
and numeric success code. Retained client/wire evidence identifies OpenAPI as
|
||||
one private application-level value rather than a per-scanner profile. A fixed
|
||||
read-only macOS Keychain loader, bounded in-memory lease and dormant facade
|
||||
orchestrator now exist. The installed runtime has no request-emission method or
|
||||
live MQTT sink. A separate uninstalled acceptance transport implements the
|
||||
retained MQTT session, exact response subscriptions and poison-on-unknown
|
||||
one-shot behavior. Operator-owned Keychain item provisioning, physical
|
||||
acceptance, durable save completion and rollback evidence remain unresolved.
|
||||
Acquisition therefore stays `operator-manual` through the verified physical
|
||||
double-click.
|
||||
read-only macOS Keychain loader, bounded shadow lease and dormant facade
|
||||
orchestrator remain. Plugin v0.5.0 separately installs an interactive acceptance
|
||||
transport implementing the retained MQTT session, exact response subscriptions
|
||||
and poison-on-unknown one-shot behavior. The descriptive profile still cannot
|
||||
enable writes by itself: active control exists only while the operator-opened
|
||||
canonical session owns the socket. Physical acceptance, durable native save
|
||||
completion and rollback evidence remain unresolved.
|
||||
The standalone encoder models the recovered wire schema, including enum values
|
||||
outside the retained request. It is not an authorization policy: any future
|
||||
publisher must enforce the exact profile mapping (`2/1/0`, omitted
|
||||
|
||||
Reference in New Issue
Block a user