# Lead Gen Manage Access Package Baseline

## Why this note exists

This train adds `sales.lead-gen.manage` as the OM-aligned runtime permission for operating Lead Gen list-builder mutations. The implementation ships through `@elevasis/core` and `@elevasis/ui`; template projects need the package baseline update so derived apps receive the new access key and shared Lead Gen UI guards.

## Applies to

- Template UI package baseline: `external/_template/ui/package.json`
- Template core package baseline: `external/_template/core/package.json`
- Template operations package baseline: `external/_template/operations/package.json`
- Derived projects that expose the shared Lead Gen list-builder UI

## Required actions

1. Publish the prepared `@elevasis/core` release containing `sales.lead-gen.manage` and `AccessKeys.leadGenManage`.
2. Publish the prepared `@elevasis/ui` release containing the shared Lead Gen mutation affordance guards.
3. Run the prepared external sync manifest so derived projects receive the updated package baselines.
4. For client launches, verify Operator users receive `sales.lead-gen.manage` through platform role grants before list-builder smoke.

## Verification

- `pnpm -C packages/core build:publish`
- `pnpm -C packages/ui build:publish`
- `pnpm -C external/_template/ui check-types`
- `pnpm -C external/_template/ui build`
- `pnpm sync:verify` after the manifest-scoped external sync stage

## Not handled by /git-sync

Database permission rows and system role grants are environment state, not template files. Apply the SQL migration or equivalent environment change separately before inviting Operator users.
