Role Composition

Non-admin runnable APIs and panels select the existing role they need independently from each part. Declare that selection with a symbolic link named after the part inside the process directory: panels link to the part’s panel/<selectedRole> directory, and APIs link to its api/api/<selectedRole> directory. For example, a managerPanel can link accounts to accounts/panel/admin, while managerApi links accounts to accounts/api/api/admin. Reuse shared core infrastructure and the selected part code through composition; do not copy it or create a part role directory merely to match the runnable process name. The selected implementation role does not change the authenticated user’s roles or bypass API authorization.

Fix

Replace duplicated process-specific part roles with symbolic links to existing part roles, and resolve those selections in core composition infrastructure.