experience-ui-bundle-deploy

Authenticate the org, build the UI bundle to produce dist/, deploy metadata using manifest/package.xml if present, then assign permission sets, optionally import data, and finally fetch the GraphQL schema and run codegen. Order matters because the schema reflects deployed org state.

The schema was likely fetched before metadata deployment or before permission sets were assigned. Custom objects and fields appear only after deployment, and users need field-level security via permission sets for introspection to return them.

Re-run schema fetch and codegen after every metadata deployment that changes objects, fields, or permissions, or when schema.graphql is missing. Codegen reads the schema locally, so it must be refreshed first.

No. Data import only runs if data/data-plan.json exists, and the skill always asks the user before importing or cleaning data. Deletes run in reverse plan order and imports use Anonymous Apex with duplicate rule saves enabled.

Users will lack access to custom objects and fields, and GraphQL introspection will return an incomplete schema. The skill discovers permission sets in force-app/main/default/permissionsets/ and assigns them or asks the user.