Repository navigation
Lockbot v2.15.2
Lockbot v2.15.2
A maintenance release for reliable Agent notifications and stricter private-task access.
- Flush Agent operations collected during the notification throttle window in trailing batches instead of silently dropping them. Keep notification failures separate from the resource operation result; uncertain notification delivery does not replay a lock or release.
- Limit private task purposes, Agent labels, authorization notes and credential identifiers to the same verified actor or the current super administrator. Ordinary bot administrators and bot-scoped OP keys retain public categories, resource state and safe operational summaries.
- Apply server-side filtering to management state, activity, authorization audit and legacy log downloads; audit elevated reads without copying private task bodies. Refresh Agent/OP Skills and context privacy metadata.
Delivery remains best effort: trailing batches use a bounded in-process queue and do not survive a process restart.
Compatibility: no new database migration or key rebind is required. The ordinary OP/admin visibility restriction is intentional; an OP key generated by a super administrator remains an ordinary bot maintenance credential. Hardware metrics authorization and approved container/host-user metadata remain separate. App RBAC is not encrypted isolation from OS/root or platform signing-credential holders; private notes must not contain secrets.
Scope: includes the fixes from #42 and #40 on release/2.x. The scoped monitoring/history work (#22), OP historical reports (#44) and Feishu work are not included. Existing deployments must upgrade explicitly; keys do not need to be rebound. Rolling back old code may restore the earlier disclosure behavior, so retain the privacy fix during incident recovery.