Seed development licences for development workspaces
What It Does
Development seeding supplies missing licensed-application grants through the normal override path. It preserves earlier human decisions and withdrawals. The per-workspace entry enforces development selection; the bulk function relies on caller selection rather than an internal environment guard.
The Flow
When Something Fails
Seed functions propagate database and history failures, so they do not establish universal deploy or provisioning success. Earlier grants can remain committed when a later application fails. Sequential rerun consults that history, which can also prevent repair of follow-up work skipped after a committed grant. The per-workspace path requests one refresh when it writes grants.