Isolate official account RPC capabilities from API key device driver
This commit is contained in:
@@ -58,3 +58,13 @@ reset, firmware, payment or subscription mutation was executed during research.
|
||||
- Unconfigured access returns `AUTH_REQUIRED` and an explicitly dated snapshot.
|
||||
- Widget selection and the other RPC writes above are not implemented. Account
|
||||
login capability discovery is not permission to exercise those writes.
|
||||
|
||||
## Module extraction
|
||||
|
||||
Official capabilities now live in `pigway_frame_flow/integrations/kokonna_official/`.
|
||||
The account RPC client, login/session handling, operation inventory and widget
|
||||
normalization/catalog are isolated there. API Key drivers no longer own a widget
|
||||
reader. DeviceRegistry composes the optional integration separately per device;
|
||||
the existing public widget route and old Python import remain compatible.
|
||||
Only login and the three verified reads are enabled. The module has no generic
|
||||
public RPC execution endpoint, and unenabled methods cannot reach the network.
|
||||
|
||||
Reference in New Issue
Block a user