appmgr-api-generator

Adding a new AppMgr API requires synchronized edits across client, proxy, stub, service, and service-inner layers. Missing one layer breaks the call chain and leaves the IPC functionality incomplete or disconnected.

Parameter marshaling and unmarshaling in AppMgr IPC requires writing interface code enum entries and handling parameter serialization across the proxy and stub to ensure synchronized client and service communication.

To ensure AppMgrService layer implementation is included, generate the complete client-to-service-inner call chain at once rather than editing files manually to prevent dropping required service orchestration logic.

Yes, this code generation approach works for OpenHarmony app_manager service interfaces by producing consistent multi-file edits spanning the full synchronized client implementation and AppMgrService business logic.

Manually editing AppMgr IPC files risks missing interdependent layers like the stub or service-inner, which breaks the call chain, whereas generating the complete chain ensures pattern-aligned edits and service-layer completeness across all required files.