- Shipped
- August 27, 2026 at 9:13 AM UTC
- Author
- Kamo
- Commit
- c94f8cc
The provider advertised extensionManagement, userManagement and deviceManagement as true while implementing none of them, so the UI would have shown buttons that throw 501. Capabilities now match behaviour. An extension in KamoPBX is three documents — a user, a device owned by that user, and a callflow mapping the number to the user. Creating only some of them yields either a number that rings nothing or a handset nothing routes to, so all three are created together and a partial failure rolls back what was made. Deleting an extension removes only the callflow. A member may own several devices, and deleting someone's registered handset because a number was removed would be a far worse surprise than an orphaned document. 253 tests pass, 5 new covering create, rollback, validation, delete scope and capability honesty.