@credibledata/cred-cli 0.0.105 → 0.0.106

package/dist/client/api.js

@@ -25,10 +25,10 @@ var __importDefault = (this && this.__importDefault) || function (mod) {
     return (mod && mod.__esModule) ? mod : { "default": mod };
 };
 Object.defineProperty(exports, "__esModule", { value: true });
-exports.PackagePermissionInheritedPermissionEnum = exports.PackagePermissionPermissionEnum = exports.OrganizationPermissionPermissionEnum = exports.MaterializationFreshnessFallbackEnum = exports.MaterializationScopeEnum = exports.MaterializationStatusEnum = exports.MaterializationOriginEnum = exports.LiveWorkItemStatusEnum = exports.IntegrationTemplateAuthEnum = exports.IntegrationSecretFieldShapeEnum = exports.IndexStatus = exports.IndexFreshnessFallbackEnum = exports.IndexScopeEnum = exports.IndexStatusEnum = exports.GroupMemberStatusEnum = exports.GetOrganizationResponseUserPermissionEnum = exports.EnvironmentPermissionPermissionEnum = exports.EnvironmentUserPermissionEnum = exports.DraftTreeEntryTypeEnum = exports.DraftPullRequestStateEnum = exports.DraftFileDiffStatusEnum = exports.DraftDocumentChangeStatusEnum = exports.DraftDocumentChangeSincePublicationEnum = exports.DraftDocumentStatusEnum = exports.DraftDocumentKindEnum = exports.DraftDocumentTypeEnum = exports.DraftCompileVerdictStatusEnum = exports.DraftCheckpointStatusEnum = exports.DraftBackingEnum = exports.DocumentTypeEnum = exports.DatabaseTableUploadMethodEnum = exports.DatabaseTableSourceKindEnum = exports.DatabaseTableFileFormatEnum = exports.DatabaseTableStatusEnum = exports.DatabaseTableSchemaEnum = exports.DatabaseIndexingStatusEnum = exports.DatabaseStatusEnum = exports.CredentialCheckOutcome = exports.ConnectionS3ConnectionProviderEnum = exports.ConnectionPostgresConnectionSslmodeEnum = exports.ConnectionAllOfProxyTypeEnum = exports.ConnectionAllOfDucklakeConnectionStorageS3ConnectionProviderEnum = exports.ConnectionAllOfDuckdbConnectionPostgresConnectionSslmodeEnum = exports.ConnectionAllOfDuckdbConnectionAzureConnectionAuthTypeEnum = exports.ConnectionAllOfDuckdbConnectionAttachedDatabasesTypeEnum = exports.ConnectionIndexingStatusEnum = exports.ConnectionTemplateEnum = exports.ConnectionTypeEnum = exports.BookmarkType = exports.AttributeValueEntryScopeEnum = void 0;
-exports.DraftsApiAxiosParamCreator = exports.UpdateDocumentUpdateMaskEnum = exports.DocumentsApi = exports.DocumentsApiFactory = exports.DocumentsApiFp = exports.DocumentsApiAxiosParamCreator = exports.DemoApi = exports.DemoApiFactory = exports.DemoApiFp = exports.DemoApiAxiosParamCreator = exports.DatabasesApi = exports.DatabasesApiFactory = exports.DatabasesApiFp = exports.DatabasesApiAxiosParamCreator = exports.CredentialsApi = exports.CredentialsApiFactory = exports.CredentialsApiFp = exports.CredentialsApiAxiosParamCreator = exports.ConnectionsApi = exports.ConnectionsApiFactory = exports.ConnectionsApiFp = exports.ConnectionsApiAxiosParamCreator = exports.BookmarksApi = exports.BookmarksApiFactory = exports.BookmarksApiFp = exports.BookmarksApiAxiosParamCreator = exports.AttributesApi = exports.AttributesApiFactory = exports.AttributesApiFp = exports.AttributesApiAxiosParamCreator = exports.WorkspacePermissionPermissionEnum = exports.WorkspaceWorkspaceTypeEnum = exports.VersionScopeEnum = exports.VersionBuildStatusEnum = exports.VersionArchiveStatusEnum = exports.UpdateGroupMemberStatusRequestStatusEnum = exports.UpdateDatabaseTableRequestUploadStatusEnum = exports.SystemPermissionPermissionEnum = exports.StalenessReason = exports.SourceEntityFieldTypeEnum = exports.SharedItemTypeEnum = exports.RunBuildPlanNodeArtifactEnum = exports.RunBuildPlanNodeStatusEnum = exports.RunBuildPlanNodeNodeTypeEnum = exports.RunStatusEnum = exports.RunTriggerEnum = exports.PreaggregateFreshnessFallbackEnum = exports.PreaggregateScopeEnum = exports.PreaggregateStatusEnum = exports.PackageWarningSeverityEnum = void 0;
-exports.PackagePermissionsApiFp = exports.PackagePermissionsApiAxiosParamCreator = exports.ListOrganizationsUserPermissionEnum = exports.OrganizationsApi = exports.OrganizationsApiFactory = exports.OrganizationsApiFp = exports.OrganizationsApiAxiosParamCreator = exports.OrganizationPermissionsApi = exports.OrganizationPermissionsApiFactory = exports.OrganizationPermissionsApiFp = exports.OrganizationPermissionsApiAxiosParamCreator = exports.MaterializationsApi = exports.MaterializationsApiFactory = exports.MaterializationsApiFp = exports.MaterializationsApiAxiosParamCreator = exports.InvitesApi = exports.InvitesApiFactory = exports.InvitesApiFp = exports.InvitesApiAxiosParamCreator = exports.IntegrationTemplatesApi = exports.IntegrationTemplatesApiFactory = exports.IntegrationTemplatesApiFp = exports.IntegrationTemplatesApiAxiosParamCreator = exports.IndexesApi = exports.IndexesApiFactory = exports.IndexesApiFp = exports.IndexesApiAxiosParamCreator = exports.GroupsApi = exports.GroupsApiFactory = exports.GroupsApiFp = exports.GroupsApiAxiosParamCreator = exports.GitRepositoryRegistrationsApi = exports.GitRepositoryRegistrationsApiFactory = exports.GitRepositoryRegistrationsApiFp = exports.GitRepositoryRegistrationsApiAxiosParamCreator = exports.EnvironmentsApi = exports.EnvironmentsApiFactory = exports.EnvironmentsApiFp = exports.EnvironmentsApiAxiosParamCreator = exports.EnvironmentPermissionsApi = exports.EnvironmentPermissionsApiFactory = exports.EnvironmentPermissionsApiFp = exports.EnvironmentPermissionsApiAxiosParamCreator = exports.EntitiesApi = exports.EntitiesApiFactory = exports.EntitiesApiFp = exports.EntitiesApiAxiosParamCreator = exports.DraftsApi = exports.DraftsApiFactory = exports.DraftsApiFp = void 0;
-exports.WorkspacesApi = exports.WorkspacesApiFactory = exports.WorkspacesApiFp = exports.WorkspacesApiAxiosParamCreator = exports.WorkspacePermissionsApi = exports.WorkspacePermissionsApiFactory = exports.WorkspacePermissionsApiFp = exports.WorkspacePermissionsApiAxiosParamCreator = exports.WebhooksApi = exports.WebhooksApiFactory = exports.WebhooksApiFp = exports.WebhooksApiAxiosParamCreator = exports.VersionsApi = exports.VersionsApiFactory = exports.VersionsApiFp = exports.VersionsApiAxiosParamCreator = exports.UsersApi = exports.UsersApiFactory = exports.UsersApiFp = exports.UsersApiAxiosParamCreator = exports.RunActionActionEnum = exports.RunsApi = exports.RunsApiFactory = exports.RunsApiFp = exports.RunsApiAxiosParamCreator = exports.PreaggregatesApi = exports.PreaggregatesApiFactory = exports.PreaggregatesApiFp = exports.PreaggregatesApiAxiosParamCreator = exports.PermissionsApi = exports.PermissionsApiFactory = exports.PermissionsApiFp = exports.PermissionsApiAxiosParamCreator = exports.PackagesApi = exports.PackagesApiFactory = exports.PackagesApiFp = exports.PackagesApiAxiosParamCreator = exports.PackagePermissionsApi = exports.PackagePermissionsApiFactory = void 0;
+exports.OrganizationPermissionPermissionEnum = exports.MaterializationFreshnessFallbackEnum = exports.MaterializationScopeEnum = exports.MaterializationStatusEnum = exports.MaterializationOriginEnum = exports.LiveWorkItemStatusEnum = exports.IntegrationTemplateAuthEnum = exports.IntegrationSecretFieldShapeEnum = exports.IndexStatus = exports.IndexFreshnessFallbackEnum = exports.IndexScopeEnum = exports.IndexStatusEnum = exports.GroupMemberStatusEnum = exports.GetOrganizationResponseUserPermissionEnum = exports.EnvironmentPermissionPermissionEnum = exports.EnvironmentUserPermissionEnum = exports.DraftTreeEntryTypeEnum = exports.DraftPullRequestStateEnum = exports.DraftFileDiffStatusEnum = exports.DraftDocumentChangeStatusEnum = exports.DraftDocumentChangeSincePublicationEnum = exports.DraftDocumentStatusEnum = exports.DraftDocumentKindEnum = exports.DraftDocumentTypeEnum = exports.DraftCompileVerdictStatusEnum = exports.DraftCheckpointStatusEnum = exports.DraftCapabilitiesPublishModesEnum = exports.DraftCapabilitiesWriteTimingEnum = exports.DraftBackingEnum = exports.DocumentTypeEnum = exports.DatabaseTableUploadMethodEnum = exports.DatabaseTableSourceKindEnum = exports.DatabaseTableFileFormatEnum = exports.DatabaseTableStatusEnum = exports.DatabaseTableSchemaEnum = exports.DatabaseIndexingStatusEnum = exports.DatabaseStatusEnum = exports.CredentialCheckOutcome = exports.ConnectionS3ConnectionProviderEnum = exports.ConnectionPostgresConnectionSslmodeEnum = exports.ConnectionAllOfProxyTypeEnum = exports.ConnectionAllOfDucklakeConnectionStorageS3ConnectionProviderEnum = exports.ConnectionAllOfDuckdbConnectionPostgresConnectionSslmodeEnum = exports.ConnectionAllOfDuckdbConnectionAzureConnectionAuthTypeEnum = exports.ConnectionAllOfDuckdbConnectionAttachedDatabasesTypeEnum = exports.ConnectionIndexingStatusEnum = exports.ConnectionTemplateEnum = exports.ConnectionTypeEnum = exports.BookmarkType = exports.AttributeValueEntryScopeEnum = void 0;
+exports.DemoApi = exports.DemoApiFactory = exports.DemoApiFp = exports.DemoApiAxiosParamCreator = exports.DatabasesApi = exports.DatabasesApiFactory = exports.DatabasesApiFp = exports.DatabasesApiAxiosParamCreator = exports.CredentialsApi = exports.CredentialsApiFactory = exports.CredentialsApiFp = exports.CredentialsApiAxiosParamCreator = exports.ConnectionsApi = exports.ConnectionsApiFactory = exports.ConnectionsApiFp = exports.ConnectionsApiAxiosParamCreator = exports.BookmarksApi = exports.BookmarksApiFactory = exports.BookmarksApiFp = exports.BookmarksApiAxiosParamCreator = exports.AttributesApi = exports.AttributesApiFactory = exports.AttributesApiFp = exports.AttributesApiAxiosParamCreator = exports.AgentSchedulesApi = exports.AgentSchedulesApiFactory = exports.AgentSchedulesApiFp = exports.AgentSchedulesApiAxiosParamCreator = exports.WorkspacePermissionPermissionEnum = exports.WorkspaceWorkspaceTypeEnum = exports.VersionScopeEnum = exports.VersionBuildStatusEnum = exports.VersionArchiveStatusEnum = exports.UpdateGroupMemberStatusRequestStatusEnum = exports.UpdateDatabaseTableRequestUploadStatusEnum = exports.SystemPermissionPermissionEnum = exports.StalenessReason = exports.SourceEntityFieldTypeEnum = exports.SharedItemTypeEnum = exports.RunBuildPlanNodeArtifactEnum = exports.RunBuildPlanNodeStatusEnum = exports.RunBuildPlanNodeNodeTypeEnum = exports.RunStatusEnum = exports.RunTriggerEnum = exports.PreaggregateFreshnessFallbackEnum = exports.PreaggregateScopeEnum = exports.PreaggregateStatusEnum = exports.PackageWarningSeverityEnum = exports.PackagePermissionInheritedPermissionEnum = exports.PackagePermissionPermissionEnum = void 0;
+exports.OrganizationsApiAxiosParamCreator = exports.OrganizationPermissionsApi = exports.OrganizationPermissionsApiFactory = exports.OrganizationPermissionsApiFp = exports.OrganizationPermissionsApiAxiosParamCreator = exports.MaterializationsApi = exports.MaterializationsApiFactory = exports.MaterializationsApiFp = exports.MaterializationsApiAxiosParamCreator = exports.InvitesApi = exports.InvitesApiFactory = exports.InvitesApiFp = exports.InvitesApiAxiosParamCreator = exports.IntegrationTemplatesApi = exports.IntegrationTemplatesApiFactory = exports.IntegrationTemplatesApiFp = exports.IntegrationTemplatesApiAxiosParamCreator = exports.IndexesApi = exports.IndexesApiFactory = exports.IndexesApiFp = exports.IndexesApiAxiosParamCreator = exports.GroupsApi = exports.GroupsApiFactory = exports.GroupsApiFp = exports.GroupsApiAxiosParamCreator = exports.GitRepositoryRegistrationsApi = exports.GitRepositoryRegistrationsApiFactory = exports.GitRepositoryRegistrationsApiFp = exports.GitRepositoryRegistrationsApiAxiosParamCreator = exports.EnvironmentsApi = exports.EnvironmentsApiFactory = exports.EnvironmentsApiFp = exports.EnvironmentsApiAxiosParamCreator = exports.EnvironmentPermissionsApi = exports.EnvironmentPermissionsApiFactory = exports.EnvironmentPermissionsApiFp = exports.EnvironmentPermissionsApiAxiosParamCreator = exports.EntitiesApi = exports.EntitiesApiFactory = exports.EntitiesApiFp = exports.EntitiesApiAxiosParamCreator = exports.DraftsApi = exports.DraftsApiFactory = exports.DraftsApiFp = exports.DraftsApiAxiosParamCreator = exports.UpdateDocumentUpdateMaskEnum = exports.DocumentsApi = exports.DocumentsApiFactory = exports.DocumentsApiFp = exports.DocumentsApiAxiosParamCreator = void 0;
+exports.WorkspacesApi = exports.WorkspacesApiFactory = exports.WorkspacesApiFp = exports.WorkspacesApiAxiosParamCreator = exports.WorkspacePermissionsApi = exports.WorkspacePermissionsApiFactory = exports.WorkspacePermissionsApiFp = exports.WorkspacePermissionsApiAxiosParamCreator = exports.WebhooksApi = exports.WebhooksApiFactory = exports.WebhooksApiFp = exports.WebhooksApiAxiosParamCreator = exports.VersionsApi = exports.VersionsApiFactory = exports.VersionsApiFp = exports.VersionsApiAxiosParamCreator = exports.UsersApi = exports.UsersApiFactory = exports.UsersApiFp = exports.UsersApiAxiosParamCreator = exports.RunActionActionEnum = exports.RunsApi = exports.RunsApiFactory = exports.RunsApiFp = exports.RunsApiAxiosParamCreator = exports.PreaggregatesApi = exports.PreaggregatesApiFactory = exports.PreaggregatesApiFp = exports.PreaggregatesApiAxiosParamCreator = exports.PermissionsApi = exports.PermissionsApiFactory = exports.PermissionsApiFp = exports.PermissionsApiAxiosParamCreator = exports.PackagesApi = exports.PackagesApiFactory = exports.PackagesApiFp = exports.PackagesApiAxiosParamCreator = exports.PackagePermissionsApi = exports.PackagePermissionsApiFactory = exports.PackagePermissionsApiFp = exports.PackagePermissionsApiAxiosParamCreator = exports.ListOrganizationsUserPermissionEnum = exports.OrganizationsApi = exports.OrganizationsApiFactory = exports.OrganizationsApiFp = void 0;
 const axios_1 = __importDefault(require("axios"));
 // Some imports not used depending on template conditions
 // @ts-ignore
@@ -179,6 +179,14 @@ exports.DraftBackingEnum = {
     Git: 'git',
     Provisioning: 'provisioning'
 };
+exports.DraftCapabilitiesWriteTimingEnum = {
+    PerEdit: 'perEdit',
+    PerTurn: 'perTurn'
+};
+exports.DraftCapabilitiesPublishModesEnum = {
+    Direct: 'direct',
+    PullRequest: 'pullRequest'
+};
 exports.DraftCheckpointStatusEnum = {
     None: 'none',
     Pending: 'pending',
@@ -428,6 +436,292 @@ exports.WorkspacePermissionPermissionEnum = {
     Manager: 'manager',
     Viewer: 'viewer'
 };
+/**
+ * AgentSchedulesApi - axios parameter creator
+ * @export
+ */
+const AgentSchedulesApiAxiosParamCreator = function (configuration) {
+    return {
+        /**
+         * Runs one task of a package agent on a cron schedule, at the package\'s latest version. Each fire is the turn the app\'s Run button sends, run as the person who created the schedule: the same access, budget and chat as if they had pressed it.  **Authorization**: Requires membership of the organization, managing the workspace (`can_update_workspace`) and the caller\'s own read access to the package (`can_read_package`).  **Cron**: exactly five whitespace-separated fields, evaluated in UTC, no `@nicknames`. The cron must have a future fire. There is no minimum interval and no limit per workspace; a run\'s cost is bounded by the organization\'s LLM budget and the agent\'s run caps.  **Refused** with `400`: an invalid `cron` (`invalid-cron`), an `agentName` that is not a lowercase hyphenated name of at most 64 characters (`VALIDATION_ERROR`), a `taskPath` or `taskTitle` that is empty or over 255 characters (`VALIDATION_ERROR`), a `taskPath` that is not `/`-separated segments of letters, digits, `.`, `_` and `-`, or that has a `.` or `..` segment (`VALIDATION_ERROR`), a `taskTitle` that is blank or holds a control character (`invalid-task-title`), and an environment draft package (`draft-package`). `403` from a caller that is not a person.
+         * @summary Schedule a package agent\'s task in a workspace
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {CreateAgentScheduleRequest} createAgentScheduleRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        createAgentSchedule: (organizationName_1, workspaceName_1, createAgentScheduleRequest_1, ...args_1) => __awaiter(this, [organizationName_1, workspaceName_1, createAgentScheduleRequest_1, ...args_1], void 0, function* (organizationName, workspaceName, createAgentScheduleRequest, options = {}) {
+            // verify required parameter 'organizationName' is not null or undefined
+            (0, common_1.assertParamExists)('createAgentSchedule', 'organizationName', organizationName);
+            // verify required parameter 'workspaceName' is not null or undefined
+            (0, common_1.assertParamExists)('createAgentSchedule', 'workspaceName', workspaceName);
+            // verify required parameter 'createAgentScheduleRequest' is not null or undefined
+            (0, common_1.assertParamExists)('createAgentSchedule', 'createAgentScheduleRequest', createAgentScheduleRequest);
+            const localVarPath = `/organizations/{organizationName}/workspaces/{workspaceName}/agent-schedules`
+                .replace(`{${"organizationName"}}`, encodeURIComponent(String(organizationName)))
+                .replace(`{${"workspaceName"}}`, encodeURIComponent(String(workspaceName)));
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, common_1.DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'POST' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            localVarHeaderParameter['Content-Type'] = 'application/json';
+            (0, common_1.setSearchParams)(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            localVarRequestOptions.data = (0, common_1.serializeDataIfNeeded)(createAgentScheduleRequest, localVarRequestOptions, configuration);
+            return {
+                url: (0, common_1.toPathString)(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
+        /**
+         * Deletes the schedule: it never fires again. A run already started is its creator\'s chat and carries on, and the chats it produced are kept.  **Authorization**: Requires reading the workspace, and either being the schedule\'s creator, managing the workspace (`can_update_workspace`) or administering the organization (`can_update_organization`).
+         * @summary Delete an agent schedule
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {string} scheduleId The unique identifier of the schedule
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deleteAgentSchedule: (organizationName_1, workspaceName_1, scheduleId_1, ...args_1) => __awaiter(this, [organizationName_1, workspaceName_1, scheduleId_1, ...args_1], void 0, function* (organizationName, workspaceName, scheduleId, options = {}) {
+            // verify required parameter 'organizationName' is not null or undefined
+            (0, common_1.assertParamExists)('deleteAgentSchedule', 'organizationName', organizationName);
+            // verify required parameter 'workspaceName' is not null or undefined
+            (0, common_1.assertParamExists)('deleteAgentSchedule', 'workspaceName', workspaceName);
+            // verify required parameter 'scheduleId' is not null or undefined
+            (0, common_1.assertParamExists)('deleteAgentSchedule', 'scheduleId', scheduleId);
+            const localVarPath = `/organizations/{organizationName}/workspaces/{workspaceName}/agent-schedules/{scheduleId}`
+                .replace(`{${"organizationName"}}`, encodeURIComponent(String(organizationName)))
+                .replace(`{${"workspaceName"}}`, encodeURIComponent(String(workspaceName)))
+                .replace(`{${"scheduleId"}}`, encodeURIComponent(String(scheduleId)));
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, common_1.DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'DELETE' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            (0, common_1.setSearchParams)(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            return {
+                url: (0, common_1.toPathString)(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
+        /**
+         * Lists the workspace\'s schedules, oldest first, each with its last fire\'s session id as `lastSessionId`.  **Authorization**: Requires read access to the workspace.  **Pagination**: `limit` / `offset` with `Total-Count` and `Link`.
+         * @summary List a workspace\'s agent schedules
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {number} [limit] Maximum number of items to return. Use -1 or omit to return all results. Valid values: -1 (all results) or 1–500.
+         * @param {number} [offset] Number of items to skip before starting to return results
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        listAgentSchedules: (organizationName_1, workspaceName_1, limit_1, offset_1, ...args_1) => __awaiter(this, [organizationName_1, workspaceName_1, limit_1, offset_1, ...args_1], void 0, function* (organizationName, workspaceName, limit, offset, options = {}) {
+            // verify required parameter 'organizationName' is not null or undefined
+            (0, common_1.assertParamExists)('listAgentSchedules', 'organizationName', organizationName);
+            // verify required parameter 'workspaceName' is not null or undefined
+            (0, common_1.assertParamExists)('listAgentSchedules', 'workspaceName', workspaceName);
+            const localVarPath = `/organizations/{organizationName}/workspaces/{workspaceName}/agent-schedules`
+                .replace(`{${"organizationName"}}`, encodeURIComponent(String(organizationName)))
+                .replace(`{${"workspaceName"}}`, encodeURIComponent(String(workspaceName)));
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, common_1.DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'GET' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            if (limit !== undefined) {
+                localVarQueryParameter['limit'] = limit;
+            }
+            if (offset !== undefined) {
+                localVarQueryParameter['offset'] = offset;
+            }
+            (0, common_1.setSearchParams)(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            return {
+                url: (0, common_1.toPathString)(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
+    };
+};
+exports.AgentSchedulesApiAxiosParamCreator = AgentSchedulesApiAxiosParamCreator;
+/**
+ * AgentSchedulesApi - functional programming interface
+ * @export
+ */
+const AgentSchedulesApiFp = function (configuration) {
+    const localVarAxiosParamCreator = (0, exports.AgentSchedulesApiAxiosParamCreator)(configuration);
+    return {
+        /**
+         * Runs one task of a package agent on a cron schedule, at the package\'s latest version. Each fire is the turn the app\'s Run button sends, run as the person who created the schedule: the same access, budget and chat as if they had pressed it.  **Authorization**: Requires membership of the organization, managing the workspace (`can_update_workspace`) and the caller\'s own read access to the package (`can_read_package`).  **Cron**: exactly five whitespace-separated fields, evaluated in UTC, no `@nicknames`. The cron must have a future fire. There is no minimum interval and no limit per workspace; a run\'s cost is bounded by the organization\'s LLM budget and the agent\'s run caps.  **Refused** with `400`: an invalid `cron` (`invalid-cron`), an `agentName` that is not a lowercase hyphenated name of at most 64 characters (`VALIDATION_ERROR`), a `taskPath` or `taskTitle` that is empty or over 255 characters (`VALIDATION_ERROR`), a `taskPath` that is not `/`-separated segments of letters, digits, `.`, `_` and `-`, or that has a `.` or `..` segment (`VALIDATION_ERROR`), a `taskTitle` that is blank or holds a control character (`invalid-task-title`), and an environment draft package (`draft-package`). `403` from a caller that is not a person.
+         * @summary Schedule a package agent\'s task in a workspace
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {CreateAgentScheduleRequest} createAgentScheduleRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        createAgentSchedule(organizationName, workspaceName, createAgentScheduleRequest, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b, _c;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.createAgentSchedule(organizationName, workspaceName, createAgentScheduleRequest, options);
+                const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
+                const localVarOperationServerBasePath = (_c = (_b = base_1.operationServerMap['AgentSchedulesApi.createAgentSchedule']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
+                return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
+        /**
+         * Deletes the schedule: it never fires again. A run already started is its creator\'s chat and carries on, and the chats it produced are kept.  **Authorization**: Requires reading the workspace, and either being the schedule\'s creator, managing the workspace (`can_update_workspace`) or administering the organization (`can_update_organization`).
+         * @summary Delete an agent schedule
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {string} scheduleId The unique identifier of the schedule
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deleteAgentSchedule(organizationName, workspaceName, scheduleId, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b, _c;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.deleteAgentSchedule(organizationName, workspaceName, scheduleId, options);
+                const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
+                const localVarOperationServerBasePath = (_c = (_b = base_1.operationServerMap['AgentSchedulesApi.deleteAgentSchedule']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
+                return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
+        /**
+         * Lists the workspace\'s schedules, oldest first, each with its last fire\'s session id as `lastSessionId`.  **Authorization**: Requires read access to the workspace.  **Pagination**: `limit` / `offset` with `Total-Count` and `Link`.
+         * @summary List a workspace\'s agent schedules
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {number} [limit] Maximum number of items to return. Use -1 or omit to return all results. Valid values: -1 (all results) or 1–500.
+         * @param {number} [offset] Number of items to skip before starting to return results
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        listAgentSchedules(organizationName, workspaceName, limit, offset, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b, _c;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.listAgentSchedules(organizationName, workspaceName, limit, offset, options);
+                const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
+                const localVarOperationServerBasePath = (_c = (_b = base_1.operationServerMap['AgentSchedulesApi.listAgentSchedules']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
+                return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
+    };
+};
+exports.AgentSchedulesApiFp = AgentSchedulesApiFp;
+/**
+ * AgentSchedulesApi - factory interface
+ * @export
+ */
+const AgentSchedulesApiFactory = function (configuration, basePath, axios) {
+    const localVarFp = (0, exports.AgentSchedulesApiFp)(configuration);
+    return {
+        /**
+         * Runs one task of a package agent on a cron schedule, at the package\'s latest version. Each fire is the turn the app\'s Run button sends, run as the person who created the schedule: the same access, budget and chat as if they had pressed it.  **Authorization**: Requires membership of the organization, managing the workspace (`can_update_workspace`) and the caller\'s own read access to the package (`can_read_package`).  **Cron**: exactly five whitespace-separated fields, evaluated in UTC, no `@nicknames`. The cron must have a future fire. There is no minimum interval and no limit per workspace; a run\'s cost is bounded by the organization\'s LLM budget and the agent\'s run caps.  **Refused** with `400`: an invalid `cron` (`invalid-cron`), an `agentName` that is not a lowercase hyphenated name of at most 64 characters (`VALIDATION_ERROR`), a `taskPath` or `taskTitle` that is empty or over 255 characters (`VALIDATION_ERROR`), a `taskPath` that is not `/`-separated segments of letters, digits, `.`, `_` and `-`, or that has a `.` or `..` segment (`VALIDATION_ERROR`), a `taskTitle` that is blank or holds a control character (`invalid-task-title`), and an environment draft package (`draft-package`). `403` from a caller that is not a person.
+         * @summary Schedule a package agent\'s task in a workspace
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {CreateAgentScheduleRequest} createAgentScheduleRequest
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        createAgentSchedule(organizationName, workspaceName, createAgentScheduleRequest, options) {
+            return localVarFp.createAgentSchedule(organizationName, workspaceName, createAgentScheduleRequest, options).then((request) => request(axios, basePath));
+        },
+        /**
+         * Deletes the schedule: it never fires again. A run already started is its creator\'s chat and carries on, and the chats it produced are kept.  **Authorization**: Requires reading the workspace, and either being the schedule\'s creator, managing the workspace (`can_update_workspace`) or administering the organization (`can_update_organization`).
+         * @summary Delete an agent schedule
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {string} scheduleId The unique identifier of the schedule
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        deleteAgentSchedule(organizationName, workspaceName, scheduleId, options) {
+            return localVarFp.deleteAgentSchedule(organizationName, workspaceName, scheduleId, options).then((request) => request(axios, basePath));
+        },
+        /**
+         * Lists the workspace\'s schedules, oldest first, each with its last fire\'s session id as `lastSessionId`.  **Authorization**: Requires read access to the workspace.  **Pagination**: `limit` / `offset` with `Total-Count` and `Link`.
+         * @summary List a workspace\'s agent schedules
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {number} [limit] Maximum number of items to return. Use -1 or omit to return all results. Valid values: -1 (all results) or 1–500.
+         * @param {number} [offset] Number of items to skip before starting to return results
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        listAgentSchedules(organizationName, workspaceName, limit, offset, options) {
+            return localVarFp.listAgentSchedules(organizationName, workspaceName, limit, offset, options).then((request) => request(axios, basePath));
+        },
+    };
+};
+exports.AgentSchedulesApiFactory = AgentSchedulesApiFactory;
+/**
+ * AgentSchedulesApi - object-oriented interface
+ * @export
+ * @class AgentSchedulesApi
+ * @extends {BaseAPI}
+ */
+class AgentSchedulesApi extends base_1.BaseAPI {
+    /**
+     * Runs one task of a package agent on a cron schedule, at the package\'s latest version. Each fire is the turn the app\'s Run button sends, run as the person who created the schedule: the same access, budget and chat as if they had pressed it.  **Authorization**: Requires membership of the organization, managing the workspace (`can_update_workspace`) and the caller\'s own read access to the package (`can_read_package`).  **Cron**: exactly five whitespace-separated fields, evaluated in UTC, no `@nicknames`. The cron must have a future fire. There is no minimum interval and no limit per workspace; a run\'s cost is bounded by the organization\'s LLM budget and the agent\'s run caps.  **Refused** with `400`: an invalid `cron` (`invalid-cron`), an `agentName` that is not a lowercase hyphenated name of at most 64 characters (`VALIDATION_ERROR`), a `taskPath` or `taskTitle` that is empty or over 255 characters (`VALIDATION_ERROR`), a `taskPath` that is not `/`-separated segments of letters, digits, `.`, `_` and `-`, or that has a `.` or `..` segment (`VALIDATION_ERROR`), a `taskTitle` that is blank or holds a control character (`invalid-task-title`), and an environment draft package (`draft-package`). `403` from a caller that is not a person.
+     * @summary Schedule a package agent\'s task in a workspace
+     * @param {string} organizationName The unique identifier of the organization
+     * @param {string} workspaceName The unique identifier of the workspace
+     * @param {CreateAgentScheduleRequest} createAgentScheduleRequest
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AgentSchedulesApi
+     */
+    createAgentSchedule(organizationName, workspaceName, createAgentScheduleRequest, options) {
+        return (0, exports.AgentSchedulesApiFp)(this.configuration).createAgentSchedule(organizationName, workspaceName, createAgentScheduleRequest, options).then((request) => request(this.axios, this.basePath));
+    }
+    /**
+     * Deletes the schedule: it never fires again. A run already started is its creator\'s chat and carries on, and the chats it produced are kept.  **Authorization**: Requires reading the workspace, and either being the schedule\'s creator, managing the workspace (`can_update_workspace`) or administering the organization (`can_update_organization`).
+     * @summary Delete an agent schedule
+     * @param {string} organizationName The unique identifier of the organization
+     * @param {string} workspaceName The unique identifier of the workspace
+     * @param {string} scheduleId The unique identifier of the schedule
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AgentSchedulesApi
+     */
+    deleteAgentSchedule(organizationName, workspaceName, scheduleId, options) {
+        return (0, exports.AgentSchedulesApiFp)(this.configuration).deleteAgentSchedule(organizationName, workspaceName, scheduleId, options).then((request) => request(this.axios, this.basePath));
+    }
+    /**
+     * Lists the workspace\'s schedules, oldest first, each with its last fire\'s session id as `lastSessionId`.  **Authorization**: Requires read access to the workspace.  **Pagination**: `limit` / `offset` with `Total-Count` and `Link`.
+     * @summary List a workspace\'s agent schedules
+     * @param {string} organizationName The unique identifier of the organization
+     * @param {string} workspaceName The unique identifier of the workspace
+     * @param {number} [limit] Maximum number of items to return. Use -1 or omit to return all results. Valid values: -1 (all results) or 1–500.
+     * @param {number} [offset] Number of items to skip before starting to return results
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof AgentSchedulesApi
+     */
+    listAgentSchedules(organizationName, workspaceName, limit, offset, options) {
+        return (0, exports.AgentSchedulesApiFp)(this.configuration).listAgentSchedules(organizationName, workspaceName, limit, offset, options).then((request) => request(this.axios, this.basePath));
+    }
+}
+exports.AgentSchedulesApi = AgentSchedulesApi;
 /**
  * AttributesApi - axios parameter creator
  * @export
@@ -3617,10 +3911,11 @@ const DocumentsApiAxiosParamCreator = function (configuration) {
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {boolean} [retrieveContent] If true, include the document content in the response. Defaults to false.
+         * @param {string} [pathPrefix] List only the documents whose path starts with this string, matched literally (`%` and `_` are not wildcards). A draft\'s files are `drafts/{draftId}/`, so a caller that wants one draft\'s files reads those rather than the whole workspace. Omitted, every document is listed.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listDocuments: (organizationName_1, workspaceName_1, retrieveContent_1, ...args_1) => __awaiter(this, [organizationName_1, workspaceName_1, retrieveContent_1, ...args_1], void 0, function* (organizationName, workspaceName, retrieveContent, options = {}) {
+        listDocuments: (organizationName_1, workspaceName_1, retrieveContent_1, pathPrefix_1, ...args_1) => __awaiter(this, [organizationName_1, workspaceName_1, retrieveContent_1, pathPrefix_1, ...args_1], void 0, function* (organizationName, workspaceName, retrieveContent, pathPrefix, options = {}) {
             // verify required parameter 'organizationName' is not null or undefined
             (0, common_1.assertParamExists)('listDocuments', 'organizationName', organizationName);
             // verify required parameter 'workspaceName' is not null or undefined
@@ -3640,6 +3935,9 @@ const DocumentsApiAxiosParamCreator = function (configuration) {
             if (retrieveContent !== undefined) {
                 localVarQueryParameter['retrieveContent'] = retrieveContent;
             }
+            if (pathPrefix !== undefined) {
+                localVarQueryParameter['pathPrefix'] = pathPrefix;
+            }
             (0, common_1.setSearchParams)(localVarUrlObj, localVarQueryParameter);
             let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
             localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
@@ -3772,13 +4070,14 @@ const DocumentsApiFp = function (configuration) {
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {boolean} [retrieveContent] If true, include the document content in the response. Defaults to false.
+         * @param {string} [pathPrefix] List only the documents whose path starts with this string, matched literally (`%` and `_` are not wildcards). A draft\'s files are `drafts/{draftId}/`, so a caller that wants one draft\'s files reads those rather than the whole workspace. Omitted, every document is listed.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listDocuments(organizationName, workspaceName, retrieveContent, options) {
+        listDocuments(organizationName, workspaceName, retrieveContent, pathPrefix, options) {
             return __awaiter(this, void 0, void 0, function* () {
                 var _a, _b, _c;
-                const localVarAxiosArgs = yield localVarAxiosParamCreator.listDocuments(organizationName, workspaceName, retrieveContent, options);
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.listDocuments(organizationName, workspaceName, retrieveContent, pathPrefix, options);
                 const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
                 const localVarOperationServerBasePath = (_c = (_b = base_1.operationServerMap['DocumentsApi.listDocuments']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
                 return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
@@ -3861,11 +4160,12 @@ const DocumentsApiFactory = function (configuration, basePath, axios) {
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {boolean} [retrieveContent] If true, include the document content in the response. Defaults to false.
+         * @param {string} [pathPrefix] List only the documents whose path starts with this string, matched literally (`%` and `_` are not wildcards). A draft\'s files are `drafts/{draftId}/`, so a caller that wants one draft\'s files reads those rather than the whole workspace. Omitted, every document is listed.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listDocuments(organizationName, workspaceName, retrieveContent, options) {
-            return localVarFp.listDocuments(organizationName, workspaceName, retrieveContent, options).then((request) => request(axios, basePath));
+        listDocuments(organizationName, workspaceName, retrieveContent, pathPrefix, options) {
+            return localVarFp.listDocuments(organizationName, workspaceName, retrieveContent, pathPrefix, options).then((request) => request(axios, basePath));
         },
         /**
          * Updates the content and metadata of an existing document within the workspace.  **Authorization**: `can_create_document` in the workspace (its managers, and its members who belong to the organization). Anything in a draft (`drafts/{draftId}` and every path under it) additionally takes `can_create_package` on the environment its manifest names, so a member who is not a modeler there cannot change a colleague\'s draft. When the REQUEST BODY\'s `type` is `draft_package`, the environment named by its `metadata.target_env` must additionally grant the caller `can_create_package` — the same bar `createDocument` applies, checked here on the incoming type because this operation ASSIGNS the type from the body: without it, converting any writable document into a `draft_package` would reach the modeling surface. A missing or blank `metadata.target_env` is refused. This narrows the existing 403; it is not a new status. **Content**: Supports updating document content, type, and other properties.  Refuses with `400` (`draft-notebook-read-only`) when the path is a `.malloynb` file inside a draft (`drafts/{draftId}/...`) and the write would change it or add a new one to a draft that already has files, whatever the request\'s `type`. See `writeDraftDocument`.  **Precondition**: `expectedUpdatedAt` is the `updatedAt` the writer read the document at. When sent, the write applies only if the document still carries that `updatedAt` (compared to the millisecond), else `409` `stale-document` and nothing is written; the check and the write hold the row lock together, so of two writers holding the same value exactly one wins. Absent, the write is last-writer-wins as it has always been.  **Partial update**: `updateMask=metadata` writes only the body\'s `metadata`. The stored `type` and `content` are kept whatever the body carries, so a caller changing metadata need not read or resend the content, and the response omits `content`. Every check above applies, against the stored type. Absent, the body replaces type, content and metadata.  **A public-link visitor** changes a document of theirs only while the package it is about (metadata `visitor_package`) is still public to them; otherwise 403. `visitor_package` is controlplane\'s: an update cannot change or remove it.
@@ -3941,12 +4241,13 @@ class DocumentsApi extends base_1.BaseAPI {
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
      * @param {boolean} [retrieveContent] If true, include the document content in the response. Defaults to false.
+     * @param {string} [pathPrefix] List only the documents whose path starts with this string, matched literally (`%` and `_` are not wildcards). A draft\'s files are `drafts/{draftId}/`, so a caller that wants one draft\'s files reads those rather than the whole workspace. Omitted, every document is listed.
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
      * @memberof DocumentsApi
      */
-    listDocuments(organizationName, workspaceName, retrieveContent, options) {
-        return (0, exports.DocumentsApiFp)(this.configuration).listDocuments(organizationName, workspaceName, retrieveContent, options).then((request) => request(this.axios, this.basePath));
+    listDocuments(organizationName, workspaceName, retrieveContent, pathPrefix, options) {
+        return (0, exports.DocumentsApiFp)(this.configuration).listDocuments(organizationName, workspaceName, retrieveContent, pathPrefix, options).then((request) => request(this.axios, this.basePath));
     }
     /**
      * Updates the content and metadata of an existing document within the workspace.  **Authorization**: `can_create_document` in the workspace (its managers, and its members who belong to the organization). Anything in a draft (`drafts/{draftId}` and every path under it) additionally takes `can_create_package` on the environment its manifest names, so a member who is not a modeler there cannot change a colleague\'s draft. When the REQUEST BODY\'s `type` is `draft_package`, the environment named by its `metadata.target_env` must additionally grant the caller `can_create_package` — the same bar `createDocument` applies, checked here on the incoming type because this operation ASSIGNS the type from the body: without it, converting any writable document into a `draft_package` would reach the modeling surface. A missing or blank `metadata.target_env` is refused. This narrows the existing 403; it is not a new status. **Content**: Supports updating document content, type, and other properties.  Refuses with `400` (`draft-notebook-read-only`) when the path is a `.malloynb` file inside a draft (`drafts/{draftId}/...`) and the write would change it or add a new one to a draft that already has files, whatever the request\'s `type`. See `writeDraftDocument`.  **Precondition**: `expectedUpdatedAt` is the `updatedAt` the writer read the document at. When sent, the write applies only if the document still carries that `updatedAt` (compared to the millisecond), else `409` `stale-document` and nothing is written; the check and the write hold the row lock together, so of two writers holding the same value exactly one wins. Absent, the write is last-writer-wins as it has always been.  **Partial update**: `updateMask=metadata` writes only the body\'s `metadata`. The stored `type` and `content` are kept whatever the body carries, so a caller changing metadata need not read or resend the content, and the response omits `content`. Every check above applies, against the stored type. Absent, the body replaces type, content and metadata.  **A public-link visitor** changes a document of theirs only while the package it is about (metadata `visitor_package`) is still public to them; otherwise 403. `visitor_package` is controlplane\'s: an update cannot change or remove it.
@@ -4017,7 +4318,7 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Deletes the draft: its manifest and, for a document-store draft, its files. Its environment draft package is marked for the checkpoint reaper, so what was serving the draft is removed on the next tick.  **The branch lives on.** Deleting a draft does not delete its git branch (docs/git-synced-modeling.md §7.2). Branch removal was inherited from the document model — documents are deletable, so a draft\'s branch looked like it had to go too — and every failure mode of that obligation had to be handled. Git\'s model is the opposite: branches accumulate and tidying is a convenience. Once a draft has had a pull request, GitHub retains `refs/pull/N/head` permanently, so deleting the branch would not remove the content anyway. Removing a branch is `DELETE .../drafts/{draftId}/branch`, and the one case worth tidying — a branch nothing was ever committed to — is the caller\'s to decide. The other case is server-side: a successful publish closes the draft and deletes its branch with it (see `writeDraftPublication` and `createOrUpdatePackage`\'s `draftId`).  **A second delete, or a read after this one, answers 404** to a caller who can use the workspace (403 to one who cannot): the gate is the workspace\'s, and the row is gone.  **Authorization**: requires `can_delete_document` on the draft document, and `can_create_package` on the environment it targets.
+         * Deletes the draft: its manifest and, for a document-store draft, its files. Its environment draft package is marked for the checkpoint reaper, so what was serving the draft is removed on the next tick.  **The branch usually lives on.** Deleting a draft does not delete its git branch (docs/git-synced-modeling.md §7.2), with one server-side exception: a draft that was never published and still sits at its seed commit has its branch deleted first, best-effort, so a draft minted from a misread intent leaves nothing behind. The delete is pinned to the seed commit, so a commit that landed since keeps the branch; the pin is not a compare-and-swap, so a commit landing in the instant between the gateway\'s tip re-read and its delete is lost. A failed branch delete never blocks the draft\'s delete, and retrying after a partial failure finds the branch already gone. Every other branch is removed by `DELETE .../drafts/{draftId}/branch`, or by the close after a successful publish (see `writeDraftPublication` and `createOrUpdatePackage`\'s `draftId`).  **A second delete, or a read after this one, answers 404** to a caller who can use the workspace (403 to one who cannot): the gate is the workspace\'s, and the row is gone.  **Authorization**: requires `can_delete_document` on the draft document, and `can_create_package` on the environment it targets.
          * @summary Delete a draft package
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -4054,7 +4355,7 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Thin proxy to the code-assist git-gateway\'s `deleteDraft` — deletes the draft\'s branch in the managed monorepo. See `listDraftCommits` for the auth-forwarding notes.  **This is branch removal only — it does not delete the draft.** Deleting the draft is `DELETE` on the draft itself.  One product path calls this, and only one: since the 2026-08-15 \"branches live on\" decision (docs/git-synced-modeling.md §7.2) deleting a draft deletes the manifest and leaves the branch, so the agent\'s `delete_file` cascade makes no branch call at all, and the app\'s delete tidies the branch only for a draft nothing was ever committed to (the §7.2 amendment of 2026-08-24). Otherwise it is the primitive operator tooling needs — see docs/tenant-offboarding-playbook.md, which prefers it over a raw GitHub call precisely because it carries the FGA check below. The close after a successful publish also deletes a draft\'s branch, but through the gateway directly rather than through this endpoint.  **Authorization**: Requires write access to the draft\'s workspace (`can_create_document`) and `can_create_package` on the environment the draft targets, as deleting the draft does. The gateway re-checks the workspace relation.  Idempotent, and deliberately not gated on the draft being git-backed, so a provisioning draft\'s half-cut branch can still be cleaned up.
+         * Thin proxy to the code-assist git-gateway\'s `deleteDraft` — deletes the draft\'s branch in the managed monorepo. See `listDraftCommits` for the auth-forwarding notes.  **This is branch removal only — it does not delete the draft.** Deleting the draft is `DELETE` on the draft itself.  Stays as the primitive operator tooling needs: `deleteDraft` deletes an untouched draft\'s branch at its seed commit on the server (docs/git-synced-modeling.md §7.2), so neither the app nor the agent needs to call this. See docs/tenant-offboarding-playbook.md, which prefers it over a raw GitHub call precisely because it carries the FGA check below. The close after a successful publish also deletes a draft\'s branch, but through the gateway directly rather than through this endpoint.  **Authorization**: Requires write access to the draft\'s workspace (`can_create_document`) and `can_create_package` on the environment the draft targets, as deleting the draft does. The gateway re-checks the workspace relation.  Idempotent, and deliberately not gated on the draft being git-backed, so a provisioning draft\'s half-cut branch can still be cleaned up.
          * @summary Delete a git-backed draft\'s branch
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -4097,8 +4398,8 @@ const DraftsApiAxiosParamCreator = function (configuration) {
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {string} draftId The draft package identifier
          * @param {string} documentPath The document\'s path relative to the draft root
-         * @param {string} [expectedRef] The branch head the caller read at. For a text document on a git-backed draft it is required; for a data file there it is ignored, since a data file\'s delete is not a commit. Refused for a document-store draft, data file or not — there is no commit to compare it against. See `writeDraftDocument` for why it is the branch head rather than the document\'s own sha.
-         * @param {string} [expectedSha] The `sha` the caller read the document at. Document-store drafts only, refused for a git-backed one: the delete applies only if the document still holds that version, else `409` `draft-document-stale`.
+         * @param {string} [expectedRef] Deprecated, git-only: use `expectedSha`. The branch head the caller read at; for a data file it is ignored, since a data file\'s delete is not a commit. Refused with `expectedSha`, and refused for a document-store draft, data file or not — there is no commit to compare it against.
+         * @param {string} [expectedSha] The `sha` the caller read the document at, on either backing: the delete applies only if the document still holds that version, else `409` `draft-document-stale`; a file already gone counts as deleted when this is the whole request, so a lost response can be resent.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
@@ -4140,13 +4441,13 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Discards the draft\'s change to one file, so the draft carries what its publication has at this path again. This is Restore, for any kind of file; after it the path has no `changeSincePublication` marker. `DELETE` on the document itself deletes the file instead — a different change, which this would undo.  What it does follows the file\'s change marker, never whether a published copy can be read:  - A data file: the draft\'s own upload or deletion is dropped. Where the draft\'s last   publish shipped its own upload, the path returns to that upload; otherwise the   published copy is inherited again, and a small UTF-8 file, which a draft holds as a   document rather than inheriting, is written back as one. `expectedRef` is optional   here, as it is absent on a data file\'s delete: when given on a git-backed draft, the   commit that writes a small published copy back builds on it (`409   draft-file-stale-head` if the branch has moved since), and on the branch\'s current   head when it is not given. - A text file the draft added: deleted. - A text file the draft edited or deleted: the published copy written back. Answers   as `getDraftDocument` with `ref=publication` does when that copy cannot be read   (`404` `draft-file-not-in-publication`, `409`, `413`, `503`), changing nothing.  `404` `draft-document-unchanged` when the draft has no change at this path — a data file the draft\'s last publish shipped and has not touched since included; `503` `draft-changes-unavailable` when its changes could not be compared with its publication.  **Authorization** — the same pair `writeDraftDocument` takes.
+         * Discards the draft\'s change to one file, so the draft carries what its publication has at this path again. This is Restore, for any kind of file; after it the path has no `changeSincePublication` marker. `DELETE` on the document itself deletes the file instead — a different change, which this would undo.  What it does follows the file\'s change marker, never whether a published copy can be read:  - A data file: the draft\'s own upload or deletion is dropped. Where the draft\'s last   publish shipped its own upload, the path returns to that upload; otherwise the   published copy is inherited again, and a small UTF-8 file, which a draft holds as a   document rather than inheriting, is written back as one. The deprecated `expectedRef`   is optional here, as it is absent on a data file\'s delete: when given on a git-backed   draft, the commit that writes a small published copy back builds on it (`409   draft-file-stale-head` if the branch has moved since), and on the branch\'s current   head when it is not given. - A text file the draft added: deleted. - A text file the draft edited or deleted: the published copy written back. Answers   as `getDraftDocument` with `ref=publication` does when that copy cannot be read   (`404` `draft-file-not-in-publication`, `409`, `413`, `503`), changing nothing.  `404` `draft-document-unchanged` when the draft has no change at this path — a data file the draft\'s last publish shipped and has not touched since included. Before any change is found, the comparison itself can be refused, with the answers a read of the baseline gives: `403` when the caller cannot read the package the draft is measured against, `409` `draft-publication-baseline-missing` when that baseline cannot be measured (past a git-backed draft\'s seed bounds, or a corrupt archive), and `503` `draft-changes-unavailable` when it could not be read.  **Authorization** — the same pair `writeDraftDocument` takes.
          * @summary Restore one of a draft\'s files to its published copy
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {string} draftId The draft package identifier
          * @param {string} documentPath The file\'s path relative to the draft root
-         * @param {string} [expectedRef] The branch head the caller read at, for a git-backed draft where the restore is a commit: required for a text file, optional for a data file (used as the compare-and-swap base when a small published copy is written back as a document); refused for a document-store draft.
+         * @param {string} [expectedRef] Deprecated: the restore builds on the branch\'s current head without it. The branch head the caller read at, for a git-backed draft where the restore is a commit (used as the compare-and-swap base); refused for a document-store draft.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
@@ -4258,6 +4559,43 @@ const DraftsApiAxiosParamCreator = function (configuration) {
                 options: localVarRequestOptions,
             };
         }),
+        /**
+         * The draft\'s capabilities, derived by the server from where its files live and what its package has published, so a client asks this rather than branching on `backing`. The same value `getDraft` carries as `capabilities`, for a caller that does not need the rest of the draft: it reads the draft\'s location and one published-version lookup, not the checkpoint, the files or the git gateway.  A draft whose branch is still being cut answers `200` with `ready: false` and nothing else, never a refusal: the answer is \"not yet\", and it changes by itself.  **Authorization**: requires read access to the draft document.
+         * @summary What the draft\'s storage can do
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {string} draftId The draft package identifier
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        getDraftCapabilities: (organizationName_1, workspaceName_1, draftId_1, ...args_1) => __awaiter(this, [organizationName_1, workspaceName_1, draftId_1, ...args_1], void 0, function* (organizationName, workspaceName, draftId, options = {}) {
+            // verify required parameter 'organizationName' is not null or undefined
+            (0, common_1.assertParamExists)('getDraftCapabilities', 'organizationName', organizationName);
+            // verify required parameter 'workspaceName' is not null or undefined
+            (0, common_1.assertParamExists)('getDraftCapabilities', 'workspaceName', workspaceName);
+            // verify required parameter 'draftId' is not null or undefined
+            (0, common_1.assertParamExists)('getDraftCapabilities', 'draftId', draftId);
+            const localVarPath = `/organizations/{organizationName}/workspaces/{workspaceName}/drafts/{draftId}/capabilities`
+                .replace(`{${"organizationName"}}`, encodeURIComponent(String(organizationName)))
+                .replace(`{${"workspaceName"}}`, encodeURIComponent(String(workspaceName)))
+                .replace(`{${"draftId"}}`, encodeURIComponent(String(draftId)));
+            // use dummy base URL string because the URL constructor only accepts absolute URLs.
+            const localVarUrlObj = new URL(localVarPath, common_1.DUMMY_BASE_URL);
+            let baseOptions;
+            if (configuration) {
+                baseOptions = configuration.baseOptions;
+            }
+            const localVarRequestOptions = Object.assign(Object.assign({ method: 'GET' }, baseOptions), options);
+            const localVarHeaderParameter = {};
+            const localVarQueryParameter = {};
+            (0, common_1.setSearchParams)(localVarUrlObj, localVarQueryParameter);
+            let headersFromBaseOptions = baseOptions && baseOptions.headers ? baseOptions.headers : {};
+            localVarRequestOptions.headers = Object.assign(Object.assign(Object.assign({}, localVarHeaderParameter), headersFromBaseOptions), options.headers);
+            return {
+                url: (0, common_1.toPathString)(localVarUrlObj),
+                options: localVarRequestOptions,
+            };
+        }),
         /**
          * Reports where the draft\'s environment package stands. Always answers `200`; `status` is `none` before the first checkpoint is requested, so a polling client does not treat absence as an error.  **A pure read**, and the cheap one: this is what a client polls while a checkpoint is unsettled. It performs no write and starts no publish.  This is a pure read. Resurrecting an idle-reaped draft package is a `POST` to `../checkpoints`, so that a publish into a live environment follows from an explicit request rather than from whichever tab last refreshed. `resurrectable` on the response says whether such a request would rebuild anything.  **Authorization**: requires read access to the draft document, the same bar as the other draft reads.
          * @summary The draft\'s checkpoint status
@@ -4390,7 +4728,7 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * One document\'s content, whichever storage backs the draft. See `listDraftDocuments` for why the backing is not the caller\'s concern.  Refuses with `413` (`draft-file-unreadable`) when the document is not readable as UTF-8 text under 1MB. That is a permanent refusal about the file\'s shape, not a transient failure: the same refusal stops a publish, so retrying achieves nothing until the file is removed or replaced.  **`ref=publication`** reads the document as it is in the version the draft\'s `changeSincePublication` markers compare against. The baseline is resolved server-side, never taken from the caller: for a git-backed draft, the draft-branch commit its last publish shipped (`publishedAs.commitSha`); for a document-store draft, the stored archive of its last published version, or — for one never published — of the version it was opened on. The answers, each distinct:  - `200`: the file\'s content in that baseline. - `403`: on a document-store draft, the caller can read the draft but not the   package whose archive the baseline is. The archive is the package\'s, and   workspace access does not imply environment access, so this read also takes   `can_read_package` on it. A git-backed baseline is the draft\'s own branch. - `404` `draft-file-not-in-publication`: the baseline exists and does not hold   this file. There is nothing to restore from it. - `409` `draft-publication-baseline-missing`: there is no baseline to read — a   draft never published and opened on nothing, a publication recorded before   baselines were, a published version with no stored archive, one whose archive is   corrupt, or one that no longer holds what its publish recorded, or a published   commit no longer on the draft\'s branch. Permanent until the draft publishes again. - `413` `draft-file-unreadable`: the baseline\'s copy is not UTF-8 text under 1MB. - `503` `draft-publication-unreadable`: the baseline exists but could not be read   right now. Retryable.  On a document-store draft the content is the published archive\'s bytes decoded as UTF-8, so its SHA-256 is the hash the markers were computed from. A published file a draft cannot hold (binary, or 1 MiB and over) is inherited by the draft rather than held, so it is not in the baseline and answers `404`. `ref` is null on a document-store answer; on a git answer it names the published commit, which is NOT a head a compare-and-swap write can build on — read the head separately before writing.  **Authorization**: requires read access to the draft document.
+         * One document\'s content, whichever storage backs the draft. See `listDraftDocuments` for why the backing is not the caller\'s concern.  Refuses with `413` (`draft-file-unreadable`) when the document is not readable as UTF-8 text under 1MB. That is a permanent refusal about the file\'s shape, not a transient failure: the same refusal stops a publish, so retrying achieves nothing until the file is removed or replaced.  **`ref=publication`** reads the document as it is in the version the draft\'s `changeSincePublication` markers compare against. The baseline is resolved server-side, never taken from the caller: for a git-backed draft, the draft-branch commit its last publish shipped (`publishedAs.commitSha`); for a document-store draft, the stored archive of its last published version, or — for one never published — of the version it was opened on. The answers, each distinct:  - `200`: the file\'s content in that baseline. - `403`: the baseline is the package\'s stored archive (a document-store draft\'s, or a   git-backed draft\'s never published) and the caller can read the draft but not the   package. Workspace access does not imply environment access, so this read also   takes `can_read_package` on it. A published git-backed draft\'s baseline is its own   branch at `publishedAs.commitSha`, readable by that sha at the draft\'s bar, so it   takes no package bar. - `404` `draft-file-not-in-publication`: the baseline exists and does not hold   this file. There is nothing to restore from it. - `409` `draft-publication-baseline-missing`: there is no baseline to read — a   draft never published and opened on nothing, a publication recorded before   baselines were, a published version with no stored archive, one whose archive is   corrupt, or one that no longer holds what its publish recorded, or a published   commit no longer on the draft\'s branch. Permanent until the draft publishes again. - `413` `draft-file-unreadable`: the baseline\'s copy is not UTF-8 text under 1MB. - `503` `draft-publication-unreadable`: the baseline exists but could not be read   right now. Retryable.  On a document-store draft the content is the published archive\'s bytes decoded as UTF-8, so its SHA-256 is the hash the markers were computed from. A published file a draft cannot hold (binary, or 1 MiB and over) is inherited by the draft rather than held, so it is not in the baseline and answers `404`. `ref` is null on a document-store answer; on a git answer it names the published commit, which is NOT a head a compare-and-swap write can build on — read the head separately before writing.  **Authorization**: requires read access to the draft document.
          * @summary Read one of a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -4558,7 +4896,7 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * The draft\'s files, **whichever storage backs them**. A git-backed draft\'s files live on its branch and a document-store draft\'s live as workspace documents; this answers for both, so a client never branches on the backing to read a draft\'s contents. That branch is the reason a draft\'s backing had to be known before its files could be fetched, which put an unrelated read on the critical path of every draft page.  Two shapes, both listings: the documents under `path` to `depth`, or — with `ref` — that same listing as of a commit. Git-backed drafts only for `ref`; a document-store draft has no history to address and ignores it.  **Listed against the draft\'s last publication.** A draft is a package in draft mode, so a listing of the draft as it stands (no `ref`) reports each document\'s `changeSincePublication` — added, modified, or unchanged — and includes the files the publication shipped that the draft has since deleted, as `removed` entries. A deletion is an edit like any other, and a page rendering the draft\'s files needs all of them from one read. A document-store draft never published is measured against the published version it was opened on, and only for a caller with read access to that package: the markers would otherwise name the package\'s published files, and their absence say which of them the draft leaves unchanged, to a reader who cannot read it. For such a caller the draft\'s own files are listed without markers, with `Changes-Unavailable`. Any other never-published draft, or a listing at a `ref`, carries no markers and no removed entries. When the comparison cannot be made (a git compare over the gateway\'s size limit, a transient failure, or a publication recorded before its baseline existed), the listing is still returned, without markers, and says so with the `Changes-Unavailable` header rather than failing.  What changed between two COMMITS is a different question — the History tab\'s — and has its own endpoint: `GET ../comparison`.  Content is omitted from the listing; read a document to get it.  **Authorization**: requires read access to the draft document.
+         * The draft\'s files, **whichever storage backs them**. A git-backed draft\'s files live on its branch and a document-store draft\'s live as workspace documents; this answers for both, so a client never branches on the backing to read a draft\'s contents. That branch is the reason a draft\'s backing had to be known before its files could be fetched, which put an unrelated read on the critical path of every draft page.  Two shapes, both listings: the documents under `path` to `depth`, or — with `ref` — that same listing as of a commit. Git-backed drafts only for `ref`; a document-store draft has no history to address and ignores it.  **Listed against the draft\'s last publication.** A draft is a package in draft mode, so a listing of the draft as it stands (no `ref`) reports each document\'s `changeSincePublication` — added, modified, or unchanged — and includes the files the publication shipped that the draft has since deleted, as `removed` entries. A deletion is an edit like any other, and a page rendering the draft\'s files needs all of them from one read. A draft never published, on either backing, is measured against the published version it was opened on (the package\'s latest version when none was recorded), and only for a caller with read access to that package: the markers would otherwise name the package\'s published files, and their absence say which of them the draft leaves unchanged, to a reader who cannot read it. For such a caller the draft\'s own files are listed without markers, with `Changes-Unavailable`. A baseline that exists but cannot be measured or read (a git-backed draft\'s version past the seed\'s bounds, or an archive that failed to download) is `Changes-Unavailable` too, never \"nothing to compare against\". A never-published draft of a package with no published version, or a listing at a `ref`, carries no markers and no removed entries. When the comparison cannot be made (a git compare over the gateway\'s size limit, a transient failure, or a publication recorded before its baseline existed), the listing is still returned, without markers, and says so with the `Changes-Unavailable` header rather than failing.  What changed between two COMMITS is a different question — the History tab\'s — and has its own endpoint: `GET ../comparison`.  Content is omitted from the listing unless `withContent=true`; otherwise read a document to get it.  **Authorization**: requires read access to the draft document.
          * @summary List a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -4566,12 +4904,13 @@ const DraftsApiAxiosParamCreator = function (configuration) {
          * @param {string} [path] Restrict the listing to this subtree, relative to the draft root.
          * @param {number} [depth] `1` lists only the immediate children of `path`, as a file browser would. Omitted returns the whole subtree, which is what a section listing wants. The two are answered by different reads, so they differ in two ways a caller can see. A bounded depth returns directory entries as well as files; the whole subtree returns files only, since a directory is not a document and every caller of the depth-less listing filters to files anyway. And the whole subtree is refused with `413` for a draft holding a symlink or submodule, where a bounded depth lists around it.
          * @param {string} [ref] Read the listing at this commit rather than at the branch tip. Accepts only a full 40-character sha reachable from the draft\'s branch. Ignored by a document-store draft, which has no commits.
+         * @param {boolean} [withContent] Carry each document\'s content on its entry, so a caller that wants the whole draft makes one request rather than one per file. A document\'s text comes as `content`; a file that is not UTF-8 text comes as `contentBase64`. A data file the draft holds beside its documents (`kind` `data`) carries neither, as in any listing. The listing is whole-draft or refused: past the same file-count and byte limits a checkpoint collects under, it answers `413` `draft-listing-too-large` rather than a partial one, and `limit` and `offset` do not lower what is read, only what is returned. Read the files one at a time instead.
          * @param {number} [limit] Maximum number of items to return. Use -1 or omit to return all results.
          * @param {number} [offset] Number of items to skip before starting to return results
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listDraftDocuments: (organizationName_1, workspaceName_1, draftId_1, path_1, depth_1, ref_1, limit_1, offset_1, ...args_1) => __awaiter(this, [organizationName_1, workspaceName_1, draftId_1, path_1, depth_1, ref_1, limit_1, offset_1, ...args_1], void 0, function* (organizationName, workspaceName, draftId, path, depth, ref, limit, offset, options = {}) {
+        listDraftDocuments: (organizationName_1, workspaceName_1, draftId_1, path_1, depth_1, ref_1, withContent_1, limit_1, offset_1, ...args_1) => __awaiter(this, [organizationName_1, workspaceName_1, draftId_1, path_1, depth_1, ref_1, withContent_1, limit_1, offset_1, ...args_1], void 0, function* (organizationName, workspaceName, draftId, path, depth, ref, withContent, limit, offset, options = {}) {
             // verify required parameter 'organizationName' is not null or undefined
             (0, common_1.assertParamExists)('listDraftDocuments', 'organizationName', organizationName);
             // verify required parameter 'workspaceName' is not null or undefined
@@ -4600,6 +4939,9 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             if (ref !== undefined) {
                 localVarQueryParameter['ref'] = ref;
             }
+            if (withContent !== undefined) {
+                localVarQueryParameter['withContent'] = withContent;
+            }
             if (limit !== undefined) {
                 localVarQueryParameter['limit'] = limit;
             }
@@ -4781,7 +5123,7 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Asks for a checkpoint of the draft\'s current content. A `POST` to the collection rather than a `PUT` on a singleton: this starts a job and answers `202`, and the checkpoints it appends to are a series (`1.0.N`), not one value being set. Sending it twice is still safe — see the coalescing note below — but that is a property of the nudge, not a claim that the request is idempotent in the `PUT` sense.  The current checkpoint\'s status is a separate read: `GET` on `../checkpoint`.  Records that the draft\'s current content should be published as the next checkpoint (`1.0.N`) of its environment draft package — an ordinary published package named `draft-{draftKey}` in the draft\'s target environment, served by the Publisher exactly like any other package there (docs/workspace-architecture-design.md §4). Always answers `202` with the current status: this call is a nudge, not the publish. The reconciler resolves the draft\'s current content itself when it collects the work — the git branch head for a git-backed draft, the doc-store tree otherwise — which is why the request carries no ref and no content: a caller-supplied ref would be both spoofable and racy against the agent\'s own commits, and a nudge that arrives late still publishes what the draft says NOW.  Nudges coalesce: any number recorded between publishes produce one checkpoint of the newest content, and a nudge whose content is identical to the latest published checkpoint publishes nothing. That is this operation\'s own contract, not something the verb supplies — a `POST` to a collection is not idempotent, so a retry after a lost response would otherwise mint a second checkpoint of content that has not changed.  A failed publish (the draft does not compile, most commonly) records `failed` with the compiler\'s message and leaves the previous checkpoint serving; the next nudge retries with the then-current content.  **This is also how a reaped draft package comes back.** A draft whose package has been idle-reaped (24 hours without a checkpoint request) keeps its row as a witness, and a nudge clears the reap marker and re-queues the publish — the same row update that publishes anything else, so no separate verb is needed. `GET` on this path reports `resurrectable` so a client knows to send one. A merge reap comes back the same way, but a client with the draft page open asks automatically: the app\'s own `POST` rebuilds the package unless the reap\'s own tick wins the race first — at `1.0.0` after the reap, or cancelling the reap and republishing into it. A package a resurrect brought back is a live draft again from there, so the ordinary idle sweep (24 hours since the *last checkpoint request*, not tied to a viewer leaving) reclaims it if nobody keeps asking. Either way a draft that outlives its merge (its close was skipped or its publish failed) can be nudged again, and any later nudge rebuilds it the same way: at `1.0.0` once the reap is deleting the package, or as the next `1.0.N` when the nudge lands before the reap starts and keeps it. Only a deleted draft\'s reap is terminal — its content has no home left — and a nudge for one is refused rather than honoured.  **Authorization**: requires `can_update_document` on the draft document AND the target environment\'s `can_create_package` — the same two bars every content-writing draft operation already takes, so anyone modeling in the draft holds both.
+         * Asks for a checkpoint of the draft\'s current content. A `POST` to the collection rather than a `PUT` on a singleton: this starts a job and answers `202`, and the checkpoints it appends to are a series (`1.0.N`), not one value being set. Sending it twice is still safe — see the coalescing note below — but that is a property of the nudge, not a claim that the request is idempotent in the `PUT` sense.  The current checkpoint\'s status is a separate read: `GET` on `../checkpoint`.  Records that the draft\'s current content should be published as the next checkpoint (`1.0.N`) of its environment draft package — an ordinary published package named `draft-{draftKey}` in the draft\'s target environment, served by the Publisher exactly like any other package there (docs/workspace-architecture-design.md §4). Answers `202` with the current status: this call is a nudge, not the publish. A draft whose branch is still being cut answers `409` `draft-provisioning` and records nothing; retry after a moment. The reconciler resolves the draft\'s current content itself when it collects the work — the git branch head for a git-backed draft, the doc-store tree otherwise — which is why the request carries no ref and no content: a caller-supplied ref would be both spoofable and racy against the agent\'s own commits, and a nudge that arrives late still publishes what the draft says NOW.  Nudges coalesce: any number recorded between publishes produce one checkpoint of the newest content, and a nudge whose content is identical to the latest published checkpoint publishes nothing. That is this operation\'s own contract, not something the verb supplies — a `POST` to a collection is not idempotent, so a retry after a lost response would otherwise mint a second checkpoint of content that has not changed.  A failed publish (the draft does not compile, most commonly) records `failed` with the compiler\'s message and leaves the previous checkpoint serving; the next nudge retries with the then-current content.  **This is also how a reaped draft package comes back.** A draft whose package has been idle-reaped (24 hours without a checkpoint request) keeps its row as a witness, and a nudge clears the reap marker and re-queues the publish — the same row update that publishes anything else, so no separate verb is needed. `GET` on this path reports `resurrectable` so a client knows to send one. A merge reap comes back the same way, but a client with the draft page open asks automatically: the app\'s own `POST` rebuilds the package unless the reap\'s own tick wins the race first — at `1.0.0` after the reap, or cancelling the reap and republishing into it. A package a resurrect brought back is a live draft again from there, so the ordinary idle sweep (24 hours since the *last checkpoint request*, not tied to a viewer leaving) reclaims it if nobody keeps asking. Either way a draft that outlives its merge (its close was skipped or its publish failed) can be nudged again, and any later nudge rebuilds it the same way: at `1.0.0` once the reap is deleting the package, or as the next `1.0.N` when the nudge lands before the reap starts and keeps it. Only a deleted draft\'s reap is terminal — its content has no home left — and a nudge for one is refused rather than honoured.  **Authorization**: requires `can_update_document` on the draft document AND the target environment\'s `can_create_package` — the same two bars every content-writing draft operation already takes, so anyone modeling in the draft holds both.
          * @summary Set the draft\'s checkpoint to its current content
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -4818,7 +5160,7 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Creates or replaces a document, whichever storage backs the draft. `PUT` rather than `POST` because the path is the identifier and the caller chooses it — there is no server-assigned id for a file, so a collection `POST` would have nothing to assign.  **The precondition depends on the storage, and each is refused on the other.** On a git-backed draft `expectedRef` is required and is the BRANCH HEAD the writer read at, not the document\'s own blob sha: the gateway refuses to build on anything but the branch\'s current tip, so a stale value means the draft moved under the writer. Take it from `getDraftDocument`\'s `ref`, and read the document at the head you intend to write against — reading the document first and the head second pairs content from one commit with a precondition naming a later one, which passes the swap and silently overwrites whatever moved in between.  On a document-store draft the precondition is per file: `expectedSha` (the `sha` the writer read) replaces the document only if it still holds that version, and `createOnly` creates it only if no document is there. Either is checked in the same statement that writes, so of two writers holding the same `sha` exactly one wins and the other gets `409` `draft-document-stale`. They are mutually exclusive (`400` when both are sent). With neither, the write is last-writer-wins, as a write through the documents API has always been. `expectedRef` is refused on a document-store draft, and `expectedSha` and `createOnly` are refused on a git-backed one, rather than ignored: a caller that sends a precondition believes it holds a guarantee.  On a document-store draft the server requests the draft\'s checkpoint after the write commits, so a client does not request one itself.  **Authorization** — `can_update_document` on the draft document, **and** `can_create_package` on the draft\'s target environment, on either backing. The second is not redundant: `can_update_document` on a draft is satisfied by bare workspace membership, while a file written here reaches the environment on the draft author\'s next checkpoint, carrying the checkpointer\'s bar rather than the writer\'s. A git-backed write also commits into that environment\'s repository. The environment comes from the draft\'s own manifest and is never a request field; a draft that names none is refused, since it could not be published either.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
+         * Creates or replaces a document, whichever storage backs the draft. `PUT` rather than `POST` because the path is the identifier and the caller chooses it — there is no server-assigned id for a file, so a collection `POST` would have nothing to assign.  **The precondition is per file, on either backing.** `expectedSha` (the `sha` the writer read) replaces the document only if it still holds that version, and `createOnly` creates it only if no document is there. Of two writers holding the same `sha` exactly one wins and the other gets `409` `draft-document-stale`, except that a resent write that already landed is answered as applied (below). They are mutually exclusive (`400` when both are sent). With neither, the write is last-writer-wins, as a write through the documents API has always been.  On either backing a retry whose change is already in place (the content is current, or the file to delete is gone) is answered as applied, not as a conflict, so a lost response can be resent. A deletion of a gone file with an `expectedSha` counts as applied only when no write in the same set is still to land: a move whose old path was deleted or moved by someone else is stale (`\"\"`), not a second copy.  On a git-backed draft the check is made against the branch\'s current files, so a commit that touched only OTHER files does not fail the write: the server re-sends it once on the new tip, and answers `409` `draft-write-contended` if the tip kept moving.  `expectedRef` is deprecated and git-only: the BRANCH HEAD the writer read at, which any commit to any file makes stale (`409` `draft-file-stale-head`). It is refused together with `expectedSha` or `createOnly`, and refused on a document-store draft rather than ignored: a caller that sends a precondition believes it holds a guarantee.  On a document-store draft the server requests the draft\'s checkpoint after the write commits, so a client does not request one itself.  **Authorization** — `can_update_document` on the draft document, **and** `can_create_package` on the draft\'s target environment, on either backing. The second is not redundant: `can_update_document` on a draft is satisfied by bare workspace membership, while a file written here reaches the environment on the draft author\'s next checkpoint, carrying the checkpointer\'s bar rather than the writer\'s. A git-backed write also commits into that environment\'s repository. The environment comes from the draft\'s own manifest and is never a request field; a draft that names none is refused, since it could not be published either.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
          * @summary Write one of a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -4910,7 +5252,7 @@ const DraftsApiAxiosParamCreator = function (configuration) {
             };
         }),
         /**
-         * Writes a set of documents together. On a git-backed draft they land as **one commit**, which is the reason this exists beside the per-document `PUT`: seeding a draft from a package is a single logical change, and writing its files one at a time would put N commits in the History tab for one action — and leave a reader of any intermediate commit looking at half a package.  Ordinary editing uses the per-document `PUT`. This is for the cases that are atomic by nature: the seed, and a multi-file edit that should be reviewable as one diff.  `expectedRef` applies to the whole set, and a client-minted `intentTimestamp` resent byte-identical makes a retried write a replay rather than a second commit — which matters more here than for one document, since a lost response after an N-file commit is otherwise indistinguishable from a write that never landed.  On a document-store draft each member may carry its own `expectedSha` or `createOnly` (see `writeDraftDocument`), so a move is one set: `createOnly` on the new path and a deletion with `expectedSha` on the old one. The set stays all-or-nothing: if any member\'s precondition fails, none is written and the `409` `draft-document-stale` names every conflicting path.  **Authorization**: as `writeDraftDocument`.  **Fenced by a work item.** A caller executing a work item (one claimed through the controlplane\'s private work-item API) sends its claim in `Work-Item-Claim` (`{id}@{generation}`). The claim is checked first thing in the transaction that writes the document rows, and refused with `409` `draft-write-fenced` -- writing nothing -- when it is no longer the live one: released, cancelled, or swept after its holder stopped heartbeating. On a branch-backed draft the commit is made by the gateway, so the claim is checked just before it: a cancel that lands during that one commit can let it through, and the commit\'s `Turn-Work-Item` trailer records which item wrote it. A malformed header is a `400`. Without the header the write is unfenced, as before. Only this operation honors the header.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
+         * Writes a set of documents together. On a git-backed draft they land as **one commit**, which is the reason this exists beside the per-document `PUT`: seeding a draft from a package is a single logical change, and writing its files one at a time would put N commits in the History tab for one action — and leave a reader of any intermediate commit looking at half a package.  Ordinary editing uses the per-document `PUT`. This is for the cases that are atomic by nature: the seed, and a multi-file edit that should be reviewable as one diff.  Each member may carry its own `expectedSha` or `createOnly` on either backing (see `writeDraftDocument`), so a move is one set: `createOnly` on the new path and a deletion with `expectedSha` on the old one. If any member\'s precondition fails, none is written and the `409` `draft-document-stale` names every conflicting path; a set already partly in place (a resent one) commits only what remains.  `expectedRef` is deprecated: it applies to the whole set, is git-only, and is refused together with a member\'s `expectedSha` or `createOnly`. A client-minted `intentTimestamp` resent byte-identical makes a retried write a replay rather than a second commit — which matters more here than for one document, since a lost response after an N-file commit is otherwise indistinguishable from a write that never landed.  **Authorization**: as `writeDraftDocument`.  **Fenced by a work item.** A caller executing a work item (one claimed through the controlplane\'s private work-item API) sends its claim in `Work-Item-Claim` (`{id}@{generation}`). The claim is checked first thing in the transaction that writes the document rows, and refused with `409` `draft-write-fenced` -- writing nothing -- when it is no longer the live one: released, cancelled, or swept after its holder stopped heartbeating. On a branch-backed draft the commit is made by the gateway, so the claim is checked just before it: a cancel that lands during that one commit can let it through, and the commit\'s `Turn-Work-Item` trailer records which item wrote it. A malformed header is a `400`. Without the header the write is unfenced, as before. Only this operation honors the header.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
          * @summary Write several of a draft\'s documents as one change
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5058,7 +5400,7 @@ const DraftsApiFp = function (configuration) {
             });
         },
         /**
-         * Deletes the draft: its manifest and, for a document-store draft, its files. Its environment draft package is marked for the checkpoint reaper, so what was serving the draft is removed on the next tick.  **The branch lives on.** Deleting a draft does not delete its git branch (docs/git-synced-modeling.md §7.2). Branch removal was inherited from the document model — documents are deletable, so a draft\'s branch looked like it had to go too — and every failure mode of that obligation had to be handled. Git\'s model is the opposite: branches accumulate and tidying is a convenience. Once a draft has had a pull request, GitHub retains `refs/pull/N/head` permanently, so deleting the branch would not remove the content anyway. Removing a branch is `DELETE .../drafts/{draftId}/branch`, and the one case worth tidying — a branch nothing was ever committed to — is the caller\'s to decide. The other case is server-side: a successful publish closes the draft and deletes its branch with it (see `writeDraftPublication` and `createOrUpdatePackage`\'s `draftId`).  **A second delete, or a read after this one, answers 404** to a caller who can use the workspace (403 to one who cannot): the gate is the workspace\'s, and the row is gone.  **Authorization**: requires `can_delete_document` on the draft document, and `can_create_package` on the environment it targets.
+         * Deletes the draft: its manifest and, for a document-store draft, its files. Its environment draft package is marked for the checkpoint reaper, so what was serving the draft is removed on the next tick.  **The branch usually lives on.** Deleting a draft does not delete its git branch (docs/git-synced-modeling.md §7.2), with one server-side exception: a draft that was never published and still sits at its seed commit has its branch deleted first, best-effort, so a draft minted from a misread intent leaves nothing behind. The delete is pinned to the seed commit, so a commit that landed since keeps the branch; the pin is not a compare-and-swap, so a commit landing in the instant between the gateway\'s tip re-read and its delete is lost. A failed branch delete never blocks the draft\'s delete, and retrying after a partial failure finds the branch already gone. Every other branch is removed by `DELETE .../drafts/{draftId}/branch`, or by the close after a successful publish (see `writeDraftPublication` and `createOrUpdatePackage`\'s `draftId`).  **A second delete, or a read after this one, answers 404** to a caller who can use the workspace (403 to one who cannot): the gate is the workspace\'s, and the row is gone.  **Authorization**: requires `can_delete_document` on the draft document, and `can_create_package` on the environment it targets.
          * @summary Delete a draft package
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5076,7 +5418,7 @@ const DraftsApiFp = function (configuration) {
             });
         },
         /**
-         * Thin proxy to the code-assist git-gateway\'s `deleteDraft` — deletes the draft\'s branch in the managed monorepo. See `listDraftCommits` for the auth-forwarding notes.  **This is branch removal only — it does not delete the draft.** Deleting the draft is `DELETE` on the draft itself.  One product path calls this, and only one: since the 2026-08-15 \"branches live on\" decision (docs/git-synced-modeling.md §7.2) deleting a draft deletes the manifest and leaves the branch, so the agent\'s `delete_file` cascade makes no branch call at all, and the app\'s delete tidies the branch only for a draft nothing was ever committed to (the §7.2 amendment of 2026-08-24). Otherwise it is the primitive operator tooling needs — see docs/tenant-offboarding-playbook.md, which prefers it over a raw GitHub call precisely because it carries the FGA check below. The close after a successful publish also deletes a draft\'s branch, but through the gateway directly rather than through this endpoint.  **Authorization**: Requires write access to the draft\'s workspace (`can_create_document`) and `can_create_package` on the environment the draft targets, as deleting the draft does. The gateway re-checks the workspace relation.  Idempotent, and deliberately not gated on the draft being git-backed, so a provisioning draft\'s half-cut branch can still be cleaned up.
+         * Thin proxy to the code-assist git-gateway\'s `deleteDraft` — deletes the draft\'s branch in the managed monorepo. See `listDraftCommits` for the auth-forwarding notes.  **This is branch removal only — it does not delete the draft.** Deleting the draft is `DELETE` on the draft itself.  Stays as the primitive operator tooling needs: `deleteDraft` deletes an untouched draft\'s branch at its seed commit on the server (docs/git-synced-modeling.md §7.2), so neither the app nor the agent needs to call this. See docs/tenant-offboarding-playbook.md, which prefers it over a raw GitHub call precisely because it carries the FGA check below. The close after a successful publish also deletes a draft\'s branch, but through the gateway directly rather than through this endpoint.  **Authorization**: Requires write access to the draft\'s workspace (`can_create_document`) and `can_create_package` on the environment the draft targets, as deleting the draft does. The gateway re-checks the workspace relation.  Idempotent, and deliberately not gated on the draft being git-backed, so a provisioning draft\'s half-cut branch can still be cleaned up.
          * @summary Delete a git-backed draft\'s branch
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5100,8 +5442,8 @@ const DraftsApiFp = function (configuration) {
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {string} draftId The draft package identifier
          * @param {string} documentPath The document\'s path relative to the draft root
-         * @param {string} [expectedRef] The branch head the caller read at. For a text document on a git-backed draft it is required; for a data file there it is ignored, since a data file\'s delete is not a commit. Refused for a document-store draft, data file or not — there is no commit to compare it against. See `writeDraftDocument` for why it is the branch head rather than the document\'s own sha.
-         * @param {string} [expectedSha] The `sha` the caller read the document at. Document-store drafts only, refused for a git-backed one: the delete applies only if the document still holds that version, else `409` `draft-document-stale`.
+         * @param {string} [expectedRef] Deprecated, git-only: use `expectedSha`. The branch head the caller read at; for a data file it is ignored, since a data file\'s delete is not a commit. Refused with `expectedSha`, and refused for a document-store draft, data file or not — there is no commit to compare it against.
+         * @param {string} [expectedSha] The `sha` the caller read the document at, on either backing: the delete applies only if the document still holds that version, else `409` `draft-document-stale`; a file already gone counts as deleted when this is the whole request, so a lost response can be resent.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
@@ -5115,13 +5457,13 @@ const DraftsApiFp = function (configuration) {
             });
         },
         /**
-         * Discards the draft\'s change to one file, so the draft carries what its publication has at this path again. This is Restore, for any kind of file; after it the path has no `changeSincePublication` marker. `DELETE` on the document itself deletes the file instead — a different change, which this would undo.  What it does follows the file\'s change marker, never whether a published copy can be read:  - A data file: the draft\'s own upload or deletion is dropped. Where the draft\'s last   publish shipped its own upload, the path returns to that upload; otherwise the   published copy is inherited again, and a small UTF-8 file, which a draft holds as a   document rather than inheriting, is written back as one. `expectedRef` is optional   here, as it is absent on a data file\'s delete: when given on a git-backed draft, the   commit that writes a small published copy back builds on it (`409   draft-file-stale-head` if the branch has moved since), and on the branch\'s current   head when it is not given. - A text file the draft added: deleted. - A text file the draft edited or deleted: the published copy written back. Answers   as `getDraftDocument` with `ref=publication` does when that copy cannot be read   (`404` `draft-file-not-in-publication`, `409`, `413`, `503`), changing nothing.  `404` `draft-document-unchanged` when the draft has no change at this path — a data file the draft\'s last publish shipped and has not touched since included; `503` `draft-changes-unavailable` when its changes could not be compared with its publication.  **Authorization** — the same pair `writeDraftDocument` takes.
+         * Discards the draft\'s change to one file, so the draft carries what its publication has at this path again. This is Restore, for any kind of file; after it the path has no `changeSincePublication` marker. `DELETE` on the document itself deletes the file instead — a different change, which this would undo.  What it does follows the file\'s change marker, never whether a published copy can be read:  - A data file: the draft\'s own upload or deletion is dropped. Where the draft\'s last   publish shipped its own upload, the path returns to that upload; otherwise the   published copy is inherited again, and a small UTF-8 file, which a draft holds as a   document rather than inheriting, is written back as one. The deprecated `expectedRef`   is optional here, as it is absent on a data file\'s delete: when given on a git-backed   draft, the commit that writes a small published copy back builds on it (`409   draft-file-stale-head` if the branch has moved since), and on the branch\'s current   head when it is not given. - A text file the draft added: deleted. - A text file the draft edited or deleted: the published copy written back. Answers   as `getDraftDocument` with `ref=publication` does when that copy cannot be read   (`404` `draft-file-not-in-publication`, `409`, `413`, `503`), changing nothing.  `404` `draft-document-unchanged` when the draft has no change at this path — a data file the draft\'s last publish shipped and has not touched since included. Before any change is found, the comparison itself can be refused, with the answers a read of the baseline gives: `403` when the caller cannot read the package the draft is measured against, `409` `draft-publication-baseline-missing` when that baseline cannot be measured (past a git-backed draft\'s seed bounds, or a corrupt archive), and `503` `draft-changes-unavailable` when it could not be read.  **Authorization** — the same pair `writeDraftDocument` takes.
          * @summary Restore one of a draft\'s files to its published copy
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {string} draftId The draft package identifier
          * @param {string} documentPath The file\'s path relative to the draft root
-         * @param {string} [expectedRef] The branch head the caller read at, for a git-backed draft where the restore is a commit: required for a text file, optional for a data file (used as the compare-and-swap base when a small published copy is written back as a document); refused for a document-store draft.
+         * @param {string} [expectedRef] Deprecated: the restore builds on the branch\'s current head without it. The branch head the caller read at, for a git-backed draft where the restore is a commit (used as the compare-and-swap base); refused for a document-store draft.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
@@ -5170,6 +5512,24 @@ const DraftsApiFp = function (configuration) {
                 return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
             });
         },
+        /**
+         * The draft\'s capabilities, derived by the server from where its files live and what its package has published, so a client asks this rather than branching on `backing`. The same value `getDraft` carries as `capabilities`, for a caller that does not need the rest of the draft: it reads the draft\'s location and one published-version lookup, not the checkpoint, the files or the git gateway.  A draft whose branch is still being cut answers `200` with `ready: false` and nothing else, never a refusal: the answer is \"not yet\", and it changes by itself.  **Authorization**: requires read access to the draft document.
+         * @summary What the draft\'s storage can do
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {string} draftId The draft package identifier
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        getDraftCapabilities(organizationName, workspaceName, draftId, options) {
+            return __awaiter(this, void 0, void 0, function* () {
+                var _a, _b, _c;
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.getDraftCapabilities(organizationName, workspaceName, draftId, options);
+                const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
+                const localVarOperationServerBasePath = (_c = (_b = base_1.operationServerMap['DraftsApi.getDraftCapabilities']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
+                return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
+            });
+        },
         /**
          * Reports where the draft\'s environment package stands. Always answers `200`; `status` is `none` before the first checkpoint is requested, so a polling client does not treat absence as an error.  **A pure read**, and the cheap one: this is what a client polls while a checkpoint is unsettled. It performs no write and starts no publish.  This is a pure read. Resurrecting an idle-reaped draft package is a `POST` to `../checkpoints`, so that a publish into a live environment follows from an explicit request rather than from whichever tab last refreshed. `resurrectable` on the response says whether such a request would rebuild anything.  **Authorization**: requires read access to the draft document, the same bar as the other draft reads.
          * @summary The draft\'s checkpoint status
@@ -5229,7 +5589,7 @@ const DraftsApiFp = function (configuration) {
             });
         },
         /**
-         * One document\'s content, whichever storage backs the draft. See `listDraftDocuments` for why the backing is not the caller\'s concern.  Refuses with `413` (`draft-file-unreadable`) when the document is not readable as UTF-8 text under 1MB. That is a permanent refusal about the file\'s shape, not a transient failure: the same refusal stops a publish, so retrying achieves nothing until the file is removed or replaced.  **`ref=publication`** reads the document as it is in the version the draft\'s `changeSincePublication` markers compare against. The baseline is resolved server-side, never taken from the caller: for a git-backed draft, the draft-branch commit its last publish shipped (`publishedAs.commitSha`); for a document-store draft, the stored archive of its last published version, or — for one never published — of the version it was opened on. The answers, each distinct:  - `200`: the file\'s content in that baseline. - `403`: on a document-store draft, the caller can read the draft but not the   package whose archive the baseline is. The archive is the package\'s, and   workspace access does not imply environment access, so this read also takes   `can_read_package` on it. A git-backed baseline is the draft\'s own branch. - `404` `draft-file-not-in-publication`: the baseline exists and does not hold   this file. There is nothing to restore from it. - `409` `draft-publication-baseline-missing`: there is no baseline to read — a   draft never published and opened on nothing, a publication recorded before   baselines were, a published version with no stored archive, one whose archive is   corrupt, or one that no longer holds what its publish recorded, or a published   commit no longer on the draft\'s branch. Permanent until the draft publishes again. - `413` `draft-file-unreadable`: the baseline\'s copy is not UTF-8 text under 1MB. - `503` `draft-publication-unreadable`: the baseline exists but could not be read   right now. Retryable.  On a document-store draft the content is the published archive\'s bytes decoded as UTF-8, so its SHA-256 is the hash the markers were computed from. A published file a draft cannot hold (binary, or 1 MiB and over) is inherited by the draft rather than held, so it is not in the baseline and answers `404`. `ref` is null on a document-store answer; on a git answer it names the published commit, which is NOT a head a compare-and-swap write can build on — read the head separately before writing.  **Authorization**: requires read access to the draft document.
+         * One document\'s content, whichever storage backs the draft. See `listDraftDocuments` for why the backing is not the caller\'s concern.  Refuses with `413` (`draft-file-unreadable`) when the document is not readable as UTF-8 text under 1MB. That is a permanent refusal about the file\'s shape, not a transient failure: the same refusal stops a publish, so retrying achieves nothing until the file is removed or replaced.  **`ref=publication`** reads the document as it is in the version the draft\'s `changeSincePublication` markers compare against. The baseline is resolved server-side, never taken from the caller: for a git-backed draft, the draft-branch commit its last publish shipped (`publishedAs.commitSha`); for a document-store draft, the stored archive of its last published version, or — for one never published — of the version it was opened on. The answers, each distinct:  - `200`: the file\'s content in that baseline. - `403`: the baseline is the package\'s stored archive (a document-store draft\'s, or a   git-backed draft\'s never published) and the caller can read the draft but not the   package. Workspace access does not imply environment access, so this read also   takes `can_read_package` on it. A published git-backed draft\'s baseline is its own   branch at `publishedAs.commitSha`, readable by that sha at the draft\'s bar, so it   takes no package bar. - `404` `draft-file-not-in-publication`: the baseline exists and does not hold   this file. There is nothing to restore from it. - `409` `draft-publication-baseline-missing`: there is no baseline to read — a   draft never published and opened on nothing, a publication recorded before   baselines were, a published version with no stored archive, one whose archive is   corrupt, or one that no longer holds what its publish recorded, or a published   commit no longer on the draft\'s branch. Permanent until the draft publishes again. - `413` `draft-file-unreadable`: the baseline\'s copy is not UTF-8 text under 1MB. - `503` `draft-publication-unreadable`: the baseline exists but could not be read   right now. Retryable.  On a document-store draft the content is the published archive\'s bytes decoded as UTF-8, so its SHA-256 is the hash the markers were computed from. A published file a draft cannot hold (binary, or 1 MiB and over) is inherited by the draft rather than held, so it is not in the baseline and answers `404`. `ref` is null on a document-store answer; on a git answer it names the published commit, which is NOT a head a compare-and-swap write can build on — read the head separately before writing.  **Authorization**: requires read access to the draft document.
          * @summary Read one of a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5306,7 +5666,7 @@ const DraftsApiFp = function (configuration) {
             });
         },
         /**
-         * The draft\'s files, **whichever storage backs them**. A git-backed draft\'s files live on its branch and a document-store draft\'s live as workspace documents; this answers for both, so a client never branches on the backing to read a draft\'s contents. That branch is the reason a draft\'s backing had to be known before its files could be fetched, which put an unrelated read on the critical path of every draft page.  Two shapes, both listings: the documents under `path` to `depth`, or — with `ref` — that same listing as of a commit. Git-backed drafts only for `ref`; a document-store draft has no history to address and ignores it.  **Listed against the draft\'s last publication.** A draft is a package in draft mode, so a listing of the draft as it stands (no `ref`) reports each document\'s `changeSincePublication` — added, modified, or unchanged — and includes the files the publication shipped that the draft has since deleted, as `removed` entries. A deletion is an edit like any other, and a page rendering the draft\'s files needs all of them from one read. A document-store draft never published is measured against the published version it was opened on, and only for a caller with read access to that package: the markers would otherwise name the package\'s published files, and their absence say which of them the draft leaves unchanged, to a reader who cannot read it. For such a caller the draft\'s own files are listed without markers, with `Changes-Unavailable`. Any other never-published draft, or a listing at a `ref`, carries no markers and no removed entries. When the comparison cannot be made (a git compare over the gateway\'s size limit, a transient failure, or a publication recorded before its baseline existed), the listing is still returned, without markers, and says so with the `Changes-Unavailable` header rather than failing.  What changed between two COMMITS is a different question — the History tab\'s — and has its own endpoint: `GET ../comparison`.  Content is omitted from the listing; read a document to get it.  **Authorization**: requires read access to the draft document.
+         * The draft\'s files, **whichever storage backs them**. A git-backed draft\'s files live on its branch and a document-store draft\'s live as workspace documents; this answers for both, so a client never branches on the backing to read a draft\'s contents. That branch is the reason a draft\'s backing had to be known before its files could be fetched, which put an unrelated read on the critical path of every draft page.  Two shapes, both listings: the documents under `path` to `depth`, or — with `ref` — that same listing as of a commit. Git-backed drafts only for `ref`; a document-store draft has no history to address and ignores it.  **Listed against the draft\'s last publication.** A draft is a package in draft mode, so a listing of the draft as it stands (no `ref`) reports each document\'s `changeSincePublication` — added, modified, or unchanged — and includes the files the publication shipped that the draft has since deleted, as `removed` entries. A deletion is an edit like any other, and a page rendering the draft\'s files needs all of them from one read. A draft never published, on either backing, is measured against the published version it was opened on (the package\'s latest version when none was recorded), and only for a caller with read access to that package: the markers would otherwise name the package\'s published files, and their absence say which of them the draft leaves unchanged, to a reader who cannot read it. For such a caller the draft\'s own files are listed without markers, with `Changes-Unavailable`. A baseline that exists but cannot be measured or read (a git-backed draft\'s version past the seed\'s bounds, or an archive that failed to download) is `Changes-Unavailable` too, never \"nothing to compare against\". A never-published draft of a package with no published version, or a listing at a `ref`, carries no markers and no removed entries. When the comparison cannot be made (a git compare over the gateway\'s size limit, a transient failure, or a publication recorded before its baseline existed), the listing is still returned, without markers, and says so with the `Changes-Unavailable` header rather than failing.  What changed between two COMMITS is a different question — the History tab\'s — and has its own endpoint: `GET ../comparison`.  Content is omitted from the listing unless `withContent=true`; otherwise read a document to get it.  **Authorization**: requires read access to the draft document.
          * @summary List a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5314,15 +5674,16 @@ const DraftsApiFp = function (configuration) {
          * @param {string} [path] Restrict the listing to this subtree, relative to the draft root.
          * @param {number} [depth] `1` lists only the immediate children of `path`, as a file browser would. Omitted returns the whole subtree, which is what a section listing wants. The two are answered by different reads, so they differ in two ways a caller can see. A bounded depth returns directory entries as well as files; the whole subtree returns files only, since a directory is not a document and every caller of the depth-less listing filters to files anyway. And the whole subtree is refused with `413` for a draft holding a symlink or submodule, where a bounded depth lists around it.
          * @param {string} [ref] Read the listing at this commit rather than at the branch tip. Accepts only a full 40-character sha reachable from the draft\'s branch. Ignored by a document-store draft, which has no commits.
+         * @param {boolean} [withContent] Carry each document\'s content on its entry, so a caller that wants the whole draft makes one request rather than one per file. A document\'s text comes as `content`; a file that is not UTF-8 text comes as `contentBase64`. A data file the draft holds beside its documents (`kind` `data`) carries neither, as in any listing. The listing is whole-draft or refused: past the same file-count and byte limits a checkpoint collects under, it answers `413` `draft-listing-too-large` rather than a partial one, and `limit` and `offset` do not lower what is read, only what is returned. Read the files one at a time instead.
          * @param {number} [limit] Maximum number of items to return. Use -1 or omit to return all results.
          * @param {number} [offset] Number of items to skip before starting to return results
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, limit, offset, options) {
+        listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, withContent, limit, offset, options) {
             return __awaiter(this, void 0, void 0, function* () {
                 var _a, _b, _c;
-                const localVarAxiosArgs = yield localVarAxiosParamCreator.listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, limit, offset, options);
+                const localVarAxiosArgs = yield localVarAxiosParamCreator.listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, withContent, limit, offset, options);
                 const localVarOperationServerIndex = (_a = configuration === null || configuration === void 0 ? void 0 : configuration.serverIndex) !== null && _a !== void 0 ? _a : 0;
                 const localVarOperationServerBasePath = (_c = (_b = base_1.operationServerMap['DraftsApi.listDraftDocuments']) === null || _b === void 0 ? void 0 : _b[localVarOperationServerIndex]) === null || _c === void 0 ? void 0 : _c.url;
                 return (axios, basePath) => (0, common_1.createRequestFunction)(localVarAxiosArgs, axios_1.default, base_1.BASE_PATH, configuration)(axios, localVarOperationServerBasePath || basePath);
@@ -5405,7 +5766,7 @@ const DraftsApiFp = function (configuration) {
             });
         },
         /**
-         * Asks for a checkpoint of the draft\'s current content. A `POST` to the collection rather than a `PUT` on a singleton: this starts a job and answers `202`, and the checkpoints it appends to are a series (`1.0.N`), not one value being set. Sending it twice is still safe — see the coalescing note below — but that is a property of the nudge, not a claim that the request is idempotent in the `PUT` sense.  The current checkpoint\'s status is a separate read: `GET` on `../checkpoint`.  Records that the draft\'s current content should be published as the next checkpoint (`1.0.N`) of its environment draft package — an ordinary published package named `draft-{draftKey}` in the draft\'s target environment, served by the Publisher exactly like any other package there (docs/workspace-architecture-design.md §4). Always answers `202` with the current status: this call is a nudge, not the publish. The reconciler resolves the draft\'s current content itself when it collects the work — the git branch head for a git-backed draft, the doc-store tree otherwise — which is why the request carries no ref and no content: a caller-supplied ref would be both spoofable and racy against the agent\'s own commits, and a nudge that arrives late still publishes what the draft says NOW.  Nudges coalesce: any number recorded between publishes produce one checkpoint of the newest content, and a nudge whose content is identical to the latest published checkpoint publishes nothing. That is this operation\'s own contract, not something the verb supplies — a `POST` to a collection is not idempotent, so a retry after a lost response would otherwise mint a second checkpoint of content that has not changed.  A failed publish (the draft does not compile, most commonly) records `failed` with the compiler\'s message and leaves the previous checkpoint serving; the next nudge retries with the then-current content.  **This is also how a reaped draft package comes back.** A draft whose package has been idle-reaped (24 hours without a checkpoint request) keeps its row as a witness, and a nudge clears the reap marker and re-queues the publish — the same row update that publishes anything else, so no separate verb is needed. `GET` on this path reports `resurrectable` so a client knows to send one. A merge reap comes back the same way, but a client with the draft page open asks automatically: the app\'s own `POST` rebuilds the package unless the reap\'s own tick wins the race first — at `1.0.0` after the reap, or cancelling the reap and republishing into it. A package a resurrect brought back is a live draft again from there, so the ordinary idle sweep (24 hours since the *last checkpoint request*, not tied to a viewer leaving) reclaims it if nobody keeps asking. Either way a draft that outlives its merge (its close was skipped or its publish failed) can be nudged again, and any later nudge rebuilds it the same way: at `1.0.0` once the reap is deleting the package, or as the next `1.0.N` when the nudge lands before the reap starts and keeps it. Only a deleted draft\'s reap is terminal — its content has no home left — and a nudge for one is refused rather than honoured.  **Authorization**: requires `can_update_document` on the draft document AND the target environment\'s `can_create_package` — the same two bars every content-writing draft operation already takes, so anyone modeling in the draft holds both.
+         * Asks for a checkpoint of the draft\'s current content. A `POST` to the collection rather than a `PUT` on a singleton: this starts a job and answers `202`, and the checkpoints it appends to are a series (`1.0.N`), not one value being set. Sending it twice is still safe — see the coalescing note below — but that is a property of the nudge, not a claim that the request is idempotent in the `PUT` sense.  The current checkpoint\'s status is a separate read: `GET` on `../checkpoint`.  Records that the draft\'s current content should be published as the next checkpoint (`1.0.N`) of its environment draft package — an ordinary published package named `draft-{draftKey}` in the draft\'s target environment, served by the Publisher exactly like any other package there (docs/workspace-architecture-design.md §4). Answers `202` with the current status: this call is a nudge, not the publish. A draft whose branch is still being cut answers `409` `draft-provisioning` and records nothing; retry after a moment. The reconciler resolves the draft\'s current content itself when it collects the work — the git branch head for a git-backed draft, the doc-store tree otherwise — which is why the request carries no ref and no content: a caller-supplied ref would be both spoofable and racy against the agent\'s own commits, and a nudge that arrives late still publishes what the draft says NOW.  Nudges coalesce: any number recorded between publishes produce one checkpoint of the newest content, and a nudge whose content is identical to the latest published checkpoint publishes nothing. That is this operation\'s own contract, not something the verb supplies — a `POST` to a collection is not idempotent, so a retry after a lost response would otherwise mint a second checkpoint of content that has not changed.  A failed publish (the draft does not compile, most commonly) records `failed` with the compiler\'s message and leaves the previous checkpoint serving; the next nudge retries with the then-current content.  **This is also how a reaped draft package comes back.** A draft whose package has been idle-reaped (24 hours without a checkpoint request) keeps its row as a witness, and a nudge clears the reap marker and re-queues the publish — the same row update that publishes anything else, so no separate verb is needed. `GET` on this path reports `resurrectable` so a client knows to send one. A merge reap comes back the same way, but a client with the draft page open asks automatically: the app\'s own `POST` rebuilds the package unless the reap\'s own tick wins the race first — at `1.0.0` after the reap, or cancelling the reap and republishing into it. A package a resurrect brought back is a live draft again from there, so the ordinary idle sweep (24 hours since the *last checkpoint request*, not tied to a viewer leaving) reclaims it if nobody keeps asking. Either way a draft that outlives its merge (its close was skipped or its publish failed) can be nudged again, and any later nudge rebuilds it the same way: at `1.0.0` once the reap is deleting the package, or as the next `1.0.N` when the nudge lands before the reap starts and keeps it. Only a deleted draft\'s reap is terminal — its content has no home left — and a nudge for one is refused rather than honoured.  **Authorization**: requires `can_update_document` on the draft document AND the target environment\'s `can_create_package` — the same two bars every content-writing draft operation already takes, so anyone modeling in the draft holds both.
          * @summary Set the draft\'s checkpoint to its current content
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5423,7 +5784,7 @@ const DraftsApiFp = function (configuration) {
             });
         },
         /**
-         * Creates or replaces a document, whichever storage backs the draft. `PUT` rather than `POST` because the path is the identifier and the caller chooses it — there is no server-assigned id for a file, so a collection `POST` would have nothing to assign.  **The precondition depends on the storage, and each is refused on the other.** On a git-backed draft `expectedRef` is required and is the BRANCH HEAD the writer read at, not the document\'s own blob sha: the gateway refuses to build on anything but the branch\'s current tip, so a stale value means the draft moved under the writer. Take it from `getDraftDocument`\'s `ref`, and read the document at the head you intend to write against — reading the document first and the head second pairs content from one commit with a precondition naming a later one, which passes the swap and silently overwrites whatever moved in between.  On a document-store draft the precondition is per file: `expectedSha` (the `sha` the writer read) replaces the document only if it still holds that version, and `createOnly` creates it only if no document is there. Either is checked in the same statement that writes, so of two writers holding the same `sha` exactly one wins and the other gets `409` `draft-document-stale`. They are mutually exclusive (`400` when both are sent). With neither, the write is last-writer-wins, as a write through the documents API has always been. `expectedRef` is refused on a document-store draft, and `expectedSha` and `createOnly` are refused on a git-backed one, rather than ignored: a caller that sends a precondition believes it holds a guarantee.  On a document-store draft the server requests the draft\'s checkpoint after the write commits, so a client does not request one itself.  **Authorization** — `can_update_document` on the draft document, **and** `can_create_package` on the draft\'s target environment, on either backing. The second is not redundant: `can_update_document` on a draft is satisfied by bare workspace membership, while a file written here reaches the environment on the draft author\'s next checkpoint, carrying the checkpointer\'s bar rather than the writer\'s. A git-backed write also commits into that environment\'s repository. The environment comes from the draft\'s own manifest and is never a request field; a draft that names none is refused, since it could not be published either.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
+         * Creates or replaces a document, whichever storage backs the draft. `PUT` rather than `POST` because the path is the identifier and the caller chooses it — there is no server-assigned id for a file, so a collection `POST` would have nothing to assign.  **The precondition is per file, on either backing.** `expectedSha` (the `sha` the writer read) replaces the document only if it still holds that version, and `createOnly` creates it only if no document is there. Of two writers holding the same `sha` exactly one wins and the other gets `409` `draft-document-stale`, except that a resent write that already landed is answered as applied (below). They are mutually exclusive (`400` when both are sent). With neither, the write is last-writer-wins, as a write through the documents API has always been.  On either backing a retry whose change is already in place (the content is current, or the file to delete is gone) is answered as applied, not as a conflict, so a lost response can be resent. A deletion of a gone file with an `expectedSha` counts as applied only when no write in the same set is still to land: a move whose old path was deleted or moved by someone else is stale (`\"\"`), not a second copy.  On a git-backed draft the check is made against the branch\'s current files, so a commit that touched only OTHER files does not fail the write: the server re-sends it once on the new tip, and answers `409` `draft-write-contended` if the tip kept moving.  `expectedRef` is deprecated and git-only: the BRANCH HEAD the writer read at, which any commit to any file makes stale (`409` `draft-file-stale-head`). It is refused together with `expectedSha` or `createOnly`, and refused on a document-store draft rather than ignored: a caller that sends a precondition believes it holds a guarantee.  On a document-store draft the server requests the draft\'s checkpoint after the write commits, so a client does not request one itself.  **Authorization** — `can_update_document` on the draft document, **and** `can_create_package` on the draft\'s target environment, on either backing. The second is not redundant: `can_update_document` on a draft is satisfied by bare workspace membership, while a file written here reaches the environment on the draft author\'s next checkpoint, carrying the checkpointer\'s bar rather than the writer\'s. A git-backed write also commits into that environment\'s repository. The environment comes from the draft\'s own manifest and is never a request field; a draft that names none is refused, since it could not be published either.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
          * @summary Write one of a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5463,7 +5824,7 @@ const DraftsApiFp = function (configuration) {
             });
         },
         /**
-         * Writes a set of documents together. On a git-backed draft they land as **one commit**, which is the reason this exists beside the per-document `PUT`: seeding a draft from a package is a single logical change, and writing its files one at a time would put N commits in the History tab for one action — and leave a reader of any intermediate commit looking at half a package.  Ordinary editing uses the per-document `PUT`. This is for the cases that are atomic by nature: the seed, and a multi-file edit that should be reviewable as one diff.  `expectedRef` applies to the whole set, and a client-minted `intentTimestamp` resent byte-identical makes a retried write a replay rather than a second commit — which matters more here than for one document, since a lost response after an N-file commit is otherwise indistinguishable from a write that never landed.  On a document-store draft each member may carry its own `expectedSha` or `createOnly` (see `writeDraftDocument`), so a move is one set: `createOnly` on the new path and a deletion with `expectedSha` on the old one. The set stays all-or-nothing: if any member\'s precondition fails, none is written and the `409` `draft-document-stale` names every conflicting path.  **Authorization**: as `writeDraftDocument`.  **Fenced by a work item.** A caller executing a work item (one claimed through the controlplane\'s private work-item API) sends its claim in `Work-Item-Claim` (`{id}@{generation}`). The claim is checked first thing in the transaction that writes the document rows, and refused with `409` `draft-write-fenced` -- writing nothing -- when it is no longer the live one: released, cancelled, or swept after its holder stopped heartbeating. On a branch-backed draft the commit is made by the gateway, so the claim is checked just before it: a cancel that lands during that one commit can let it through, and the commit\'s `Turn-Work-Item` trailer records which item wrote it. A malformed header is a `400`. Without the header the write is unfenced, as before. Only this operation honors the header.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
+         * Writes a set of documents together. On a git-backed draft they land as **one commit**, which is the reason this exists beside the per-document `PUT`: seeding a draft from a package is a single logical change, and writing its files one at a time would put N commits in the History tab for one action — and leave a reader of any intermediate commit looking at half a package.  Ordinary editing uses the per-document `PUT`. This is for the cases that are atomic by nature: the seed, and a multi-file edit that should be reviewable as one diff.  Each member may carry its own `expectedSha` or `createOnly` on either backing (see `writeDraftDocument`), so a move is one set: `createOnly` on the new path and a deletion with `expectedSha` on the old one. If any member\'s precondition fails, none is written and the `409` `draft-document-stale` names every conflicting path; a set already partly in place (a resent one) commits only what remains.  `expectedRef` is deprecated: it applies to the whole set, is git-only, and is refused together with a member\'s `expectedSha` or `createOnly`. A client-minted `intentTimestamp` resent byte-identical makes a retried write a replay rather than a second commit — which matters more here than for one document, since a lost response after an N-file commit is otherwise indistinguishable from a write that never landed.  **Authorization**: as `writeDraftDocument`.  **Fenced by a work item.** A caller executing a work item (one claimed through the controlplane\'s private work-item API) sends its claim in `Work-Item-Claim` (`{id}@{generation}`). The claim is checked first thing in the transaction that writes the document rows, and refused with `409` `draft-write-fenced` -- writing nothing -- when it is no longer the live one: released, cancelled, or swept after its holder stopped heartbeating. On a branch-backed draft the commit is made by the gateway, so the claim is checked just before it: a cancel that lands during that one commit can let it through, and the commit\'s `Turn-Work-Item` trailer records which item wrote it. A malformed header is a `400`. Without the header the write is unfenced, as before. Only this operation honors the header.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
          * @summary Write several of a draft\'s documents as one change
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5541,7 +5902,7 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
             return localVarFp.createDraft(organizationName, workspaceName, draftCreateRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Deletes the draft: its manifest and, for a document-store draft, its files. Its environment draft package is marked for the checkpoint reaper, so what was serving the draft is removed on the next tick.  **The branch lives on.** Deleting a draft does not delete its git branch (docs/git-synced-modeling.md §7.2). Branch removal was inherited from the document model — documents are deletable, so a draft\'s branch looked like it had to go too — and every failure mode of that obligation had to be handled. Git\'s model is the opposite: branches accumulate and tidying is a convenience. Once a draft has had a pull request, GitHub retains `refs/pull/N/head` permanently, so deleting the branch would not remove the content anyway. Removing a branch is `DELETE .../drafts/{draftId}/branch`, and the one case worth tidying — a branch nothing was ever committed to — is the caller\'s to decide. The other case is server-side: a successful publish closes the draft and deletes its branch with it (see `writeDraftPublication` and `createOrUpdatePackage`\'s `draftId`).  **A second delete, or a read after this one, answers 404** to a caller who can use the workspace (403 to one who cannot): the gate is the workspace\'s, and the row is gone.  **Authorization**: requires `can_delete_document` on the draft document, and `can_create_package` on the environment it targets.
+         * Deletes the draft: its manifest and, for a document-store draft, its files. Its environment draft package is marked for the checkpoint reaper, so what was serving the draft is removed on the next tick.  **The branch usually lives on.** Deleting a draft does not delete its git branch (docs/git-synced-modeling.md §7.2), with one server-side exception: a draft that was never published and still sits at its seed commit has its branch deleted first, best-effort, so a draft minted from a misread intent leaves nothing behind. The delete is pinned to the seed commit, so a commit that landed since keeps the branch; the pin is not a compare-and-swap, so a commit landing in the instant between the gateway\'s tip re-read and its delete is lost. A failed branch delete never blocks the draft\'s delete, and retrying after a partial failure finds the branch already gone. Every other branch is removed by `DELETE .../drafts/{draftId}/branch`, or by the close after a successful publish (see `writeDraftPublication` and `createOrUpdatePackage`\'s `draftId`).  **A second delete, or a read after this one, answers 404** to a caller who can use the workspace (403 to one who cannot): the gate is the workspace\'s, and the row is gone.  **Authorization**: requires `can_delete_document` on the draft document, and `can_create_package` on the environment it targets.
          * @summary Delete a draft package
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5553,7 +5914,7 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
             return localVarFp.deleteDraft(organizationName, workspaceName, draftId, options).then((request) => request(axios, basePath));
         },
         /**
-         * Thin proxy to the code-assist git-gateway\'s `deleteDraft` — deletes the draft\'s branch in the managed monorepo. See `listDraftCommits` for the auth-forwarding notes.  **This is branch removal only — it does not delete the draft.** Deleting the draft is `DELETE` on the draft itself.  One product path calls this, and only one: since the 2026-08-15 \"branches live on\" decision (docs/git-synced-modeling.md §7.2) deleting a draft deletes the manifest and leaves the branch, so the agent\'s `delete_file` cascade makes no branch call at all, and the app\'s delete tidies the branch only for a draft nothing was ever committed to (the §7.2 amendment of 2026-08-24). Otherwise it is the primitive operator tooling needs — see docs/tenant-offboarding-playbook.md, which prefers it over a raw GitHub call precisely because it carries the FGA check below. The close after a successful publish also deletes a draft\'s branch, but through the gateway directly rather than through this endpoint.  **Authorization**: Requires write access to the draft\'s workspace (`can_create_document`) and `can_create_package` on the environment the draft targets, as deleting the draft does. The gateway re-checks the workspace relation.  Idempotent, and deliberately not gated on the draft being git-backed, so a provisioning draft\'s half-cut branch can still be cleaned up.
+         * Thin proxy to the code-assist git-gateway\'s `deleteDraft` — deletes the draft\'s branch in the managed monorepo. See `listDraftCommits` for the auth-forwarding notes.  **This is branch removal only — it does not delete the draft.** Deleting the draft is `DELETE` on the draft itself.  Stays as the primitive operator tooling needs: `deleteDraft` deletes an untouched draft\'s branch at its seed commit on the server (docs/git-synced-modeling.md §7.2), so neither the app nor the agent needs to call this. See docs/tenant-offboarding-playbook.md, which prefers it over a raw GitHub call precisely because it carries the FGA check below. The close after a successful publish also deletes a draft\'s branch, but through the gateway directly rather than through this endpoint.  **Authorization**: Requires write access to the draft\'s workspace (`can_create_document`) and `can_create_package` on the environment the draft targets, as deleting the draft does. The gateway re-checks the workspace relation.  Idempotent, and deliberately not gated on the draft being git-backed, so a provisioning draft\'s half-cut branch can still be cleaned up.
          * @summary Delete a git-backed draft\'s branch
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5571,8 +5932,8 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {string} draftId The draft package identifier
          * @param {string} documentPath The document\'s path relative to the draft root
-         * @param {string} [expectedRef] The branch head the caller read at. For a text document on a git-backed draft it is required; for a data file there it is ignored, since a data file\'s delete is not a commit. Refused for a document-store draft, data file or not — there is no commit to compare it against. See `writeDraftDocument` for why it is the branch head rather than the document\'s own sha.
-         * @param {string} [expectedSha] The `sha` the caller read the document at. Document-store drafts only, refused for a git-backed one: the delete applies only if the document still holds that version, else `409` `draft-document-stale`.
+         * @param {string} [expectedRef] Deprecated, git-only: use `expectedSha`. The branch head the caller read at; for a data file it is ignored, since a data file\'s delete is not a commit. Refused with `expectedSha`, and refused for a document-store draft, data file or not — there is no commit to compare it against.
+         * @param {string} [expectedSha] The `sha` the caller read the document at, on either backing: the delete applies only if the document still holds that version, else `409` `draft-document-stale`; a file already gone counts as deleted when this is the whole request, so a lost response can be resent.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
@@ -5580,13 +5941,13 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
             return localVarFp.deleteDraftDocument(organizationName, workspaceName, draftId, documentPath, expectedRef, expectedSha, options).then((request) => request(axios, basePath));
         },
         /**
-         * Discards the draft\'s change to one file, so the draft carries what its publication has at this path again. This is Restore, for any kind of file; after it the path has no `changeSincePublication` marker. `DELETE` on the document itself deletes the file instead — a different change, which this would undo.  What it does follows the file\'s change marker, never whether a published copy can be read:  - A data file: the draft\'s own upload or deletion is dropped. Where the draft\'s last   publish shipped its own upload, the path returns to that upload; otherwise the   published copy is inherited again, and a small UTF-8 file, which a draft holds as a   document rather than inheriting, is written back as one. `expectedRef` is optional   here, as it is absent on a data file\'s delete: when given on a git-backed draft, the   commit that writes a small published copy back builds on it (`409   draft-file-stale-head` if the branch has moved since), and on the branch\'s current   head when it is not given. - A text file the draft added: deleted. - A text file the draft edited or deleted: the published copy written back. Answers   as `getDraftDocument` with `ref=publication` does when that copy cannot be read   (`404` `draft-file-not-in-publication`, `409`, `413`, `503`), changing nothing.  `404` `draft-document-unchanged` when the draft has no change at this path — a data file the draft\'s last publish shipped and has not touched since included; `503` `draft-changes-unavailable` when its changes could not be compared with its publication.  **Authorization** — the same pair `writeDraftDocument` takes.
+         * Discards the draft\'s change to one file, so the draft carries what its publication has at this path again. This is Restore, for any kind of file; after it the path has no `changeSincePublication` marker. `DELETE` on the document itself deletes the file instead — a different change, which this would undo.  What it does follows the file\'s change marker, never whether a published copy can be read:  - A data file: the draft\'s own upload or deletion is dropped. Where the draft\'s last   publish shipped its own upload, the path returns to that upload; otherwise the   published copy is inherited again, and a small UTF-8 file, which a draft holds as a   document rather than inheriting, is written back as one. The deprecated `expectedRef`   is optional here, as it is absent on a data file\'s delete: when given on a git-backed   draft, the commit that writes a small published copy back builds on it (`409   draft-file-stale-head` if the branch has moved since), and on the branch\'s current   head when it is not given. - A text file the draft added: deleted. - A text file the draft edited or deleted: the published copy written back. Answers   as `getDraftDocument` with `ref=publication` does when that copy cannot be read   (`404` `draft-file-not-in-publication`, `409`, `413`, `503`), changing nothing.  `404` `draft-document-unchanged` when the draft has no change at this path — a data file the draft\'s last publish shipped and has not touched since included. Before any change is found, the comparison itself can be refused, with the answers a read of the baseline gives: `403` when the caller cannot read the package the draft is measured against, `409` `draft-publication-baseline-missing` when that baseline cannot be measured (past a git-backed draft\'s seed bounds, or a corrupt archive), and `503` `draft-changes-unavailable` when it could not be read.  **Authorization** — the same pair `writeDraftDocument` takes.
          * @summary Restore one of a draft\'s files to its published copy
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
          * @param {string} draftId The draft package identifier
          * @param {string} documentPath The file\'s path relative to the draft root
-         * @param {string} [expectedRef] The branch head the caller read at, for a git-backed draft where the restore is a commit: required for a text file, optional for a data file (used as the compare-and-swap base when a small published copy is written back as a document); refused for a document-store draft.
+         * @param {string} [expectedRef] Deprecated: the restore builds on the branch\'s current head without it. The branch head the caller read at, for a git-backed draft where the restore is a commit (used as the compare-and-swap base); refused for a document-store draft.
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
@@ -5617,6 +5978,18 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
         getDraftBranch(organizationName, workspaceName, draftId, options) {
             return localVarFp.getDraftBranch(organizationName, workspaceName, draftId, options).then((request) => request(axios, basePath));
         },
+        /**
+         * The draft\'s capabilities, derived by the server from where its files live and what its package has published, so a client asks this rather than branching on `backing`. The same value `getDraft` carries as `capabilities`, for a caller that does not need the rest of the draft: it reads the draft\'s location and one published-version lookup, not the checkpoint, the files or the git gateway.  A draft whose branch is still being cut answers `200` with `ready: false` and nothing else, never a refusal: the answer is \"not yet\", and it changes by itself.  **Authorization**: requires read access to the draft document.
+         * @summary What the draft\'s storage can do
+         * @param {string} organizationName The unique identifier of the organization
+         * @param {string} workspaceName The unique identifier of the workspace
+         * @param {string} draftId The draft package identifier
+         * @param {*} [options] Override http request option.
+         * @throws {RequiredError}
+         */
+        getDraftCapabilities(organizationName, workspaceName, draftId, options) {
+            return localVarFp.getDraftCapabilities(organizationName, workspaceName, draftId, options).then((request) => request(axios, basePath));
+        },
         /**
          * Reports where the draft\'s environment package stands. Always answers `200`; `status` is `none` before the first checkpoint is requested, so a polling client does not treat absence as an error.  **A pure read**, and the cheap one: this is what a client polls while a checkpoint is unsettled. It performs no write and starts no publish.  This is a pure read. Resurrecting an idle-reaped draft package is a `POST` to `../checkpoints`, so that a publish into a live environment follows from an explicit request rather than from whichever tab last refreshed. `resurrectable` on the response says whether such a request would rebuild anything.  **Authorization**: requires read access to the draft document, the same bar as the other draft reads.
          * @summary The draft\'s checkpoint status
@@ -5658,7 +6031,7 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
             return localVarFp.getDraftContent(organizationName, workspaceName, draftId, options).then((request) => request(axios, basePath));
         },
         /**
-         * One document\'s content, whichever storage backs the draft. See `listDraftDocuments` for why the backing is not the caller\'s concern.  Refuses with `413` (`draft-file-unreadable`) when the document is not readable as UTF-8 text under 1MB. That is a permanent refusal about the file\'s shape, not a transient failure: the same refusal stops a publish, so retrying achieves nothing until the file is removed or replaced.  **`ref=publication`** reads the document as it is in the version the draft\'s `changeSincePublication` markers compare against. The baseline is resolved server-side, never taken from the caller: for a git-backed draft, the draft-branch commit its last publish shipped (`publishedAs.commitSha`); for a document-store draft, the stored archive of its last published version, or — for one never published — of the version it was opened on. The answers, each distinct:  - `200`: the file\'s content in that baseline. - `403`: on a document-store draft, the caller can read the draft but not the   package whose archive the baseline is. The archive is the package\'s, and   workspace access does not imply environment access, so this read also takes   `can_read_package` on it. A git-backed baseline is the draft\'s own branch. - `404` `draft-file-not-in-publication`: the baseline exists and does not hold   this file. There is nothing to restore from it. - `409` `draft-publication-baseline-missing`: there is no baseline to read — a   draft never published and opened on nothing, a publication recorded before   baselines were, a published version with no stored archive, one whose archive is   corrupt, or one that no longer holds what its publish recorded, or a published   commit no longer on the draft\'s branch. Permanent until the draft publishes again. - `413` `draft-file-unreadable`: the baseline\'s copy is not UTF-8 text under 1MB. - `503` `draft-publication-unreadable`: the baseline exists but could not be read   right now. Retryable.  On a document-store draft the content is the published archive\'s bytes decoded as UTF-8, so its SHA-256 is the hash the markers were computed from. A published file a draft cannot hold (binary, or 1 MiB and over) is inherited by the draft rather than held, so it is not in the baseline and answers `404`. `ref` is null on a document-store answer; on a git answer it names the published commit, which is NOT a head a compare-and-swap write can build on — read the head separately before writing.  **Authorization**: requires read access to the draft document.
+         * One document\'s content, whichever storage backs the draft. See `listDraftDocuments` for why the backing is not the caller\'s concern.  Refuses with `413` (`draft-file-unreadable`) when the document is not readable as UTF-8 text under 1MB. That is a permanent refusal about the file\'s shape, not a transient failure: the same refusal stops a publish, so retrying achieves nothing until the file is removed or replaced.  **`ref=publication`** reads the document as it is in the version the draft\'s `changeSincePublication` markers compare against. The baseline is resolved server-side, never taken from the caller: for a git-backed draft, the draft-branch commit its last publish shipped (`publishedAs.commitSha`); for a document-store draft, the stored archive of its last published version, or — for one never published — of the version it was opened on. The answers, each distinct:  - `200`: the file\'s content in that baseline. - `403`: the baseline is the package\'s stored archive (a document-store draft\'s, or a   git-backed draft\'s never published) and the caller can read the draft but not the   package. Workspace access does not imply environment access, so this read also   takes `can_read_package` on it. A published git-backed draft\'s baseline is its own   branch at `publishedAs.commitSha`, readable by that sha at the draft\'s bar, so it   takes no package bar. - `404` `draft-file-not-in-publication`: the baseline exists and does not hold   this file. There is nothing to restore from it. - `409` `draft-publication-baseline-missing`: there is no baseline to read — a   draft never published and opened on nothing, a publication recorded before   baselines were, a published version with no stored archive, one whose archive is   corrupt, or one that no longer holds what its publish recorded, or a published   commit no longer on the draft\'s branch. Permanent until the draft publishes again. - `413` `draft-file-unreadable`: the baseline\'s copy is not UTF-8 text under 1MB. - `503` `draft-publication-unreadable`: the baseline exists but could not be read   right now. Retryable.  On a document-store draft the content is the published archive\'s bytes decoded as UTF-8, so its SHA-256 is the hash the markers were computed from. A published file a draft cannot hold (binary, or 1 MiB and over) is inherited by the draft rather than held, so it is not in the baseline and answers `404`. `ref` is null on a document-store answer; on a git answer it names the published commit, which is NOT a head a compare-and-swap write can build on — read the head separately before writing.  **Authorization**: requires read access to the draft document.
          * @summary Read one of a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5711,7 +6084,7 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
             return localVarFp.listDraftCommits(organizationName, workspaceName, draftId, limit, offset, options).then((request) => request(axios, basePath));
         },
         /**
-         * The draft\'s files, **whichever storage backs them**. A git-backed draft\'s files live on its branch and a document-store draft\'s live as workspace documents; this answers for both, so a client never branches on the backing to read a draft\'s contents. That branch is the reason a draft\'s backing had to be known before its files could be fetched, which put an unrelated read on the critical path of every draft page.  Two shapes, both listings: the documents under `path` to `depth`, or — with `ref` — that same listing as of a commit. Git-backed drafts only for `ref`; a document-store draft has no history to address and ignores it.  **Listed against the draft\'s last publication.** A draft is a package in draft mode, so a listing of the draft as it stands (no `ref`) reports each document\'s `changeSincePublication` — added, modified, or unchanged — and includes the files the publication shipped that the draft has since deleted, as `removed` entries. A deletion is an edit like any other, and a page rendering the draft\'s files needs all of them from one read. A document-store draft never published is measured against the published version it was opened on, and only for a caller with read access to that package: the markers would otherwise name the package\'s published files, and their absence say which of them the draft leaves unchanged, to a reader who cannot read it. For such a caller the draft\'s own files are listed without markers, with `Changes-Unavailable`. Any other never-published draft, or a listing at a `ref`, carries no markers and no removed entries. When the comparison cannot be made (a git compare over the gateway\'s size limit, a transient failure, or a publication recorded before its baseline existed), the listing is still returned, without markers, and says so with the `Changes-Unavailable` header rather than failing.  What changed between two COMMITS is a different question — the History tab\'s — and has its own endpoint: `GET ../comparison`.  Content is omitted from the listing; read a document to get it.  **Authorization**: requires read access to the draft document.
+         * The draft\'s files, **whichever storage backs them**. A git-backed draft\'s files live on its branch and a document-store draft\'s live as workspace documents; this answers for both, so a client never branches on the backing to read a draft\'s contents. That branch is the reason a draft\'s backing had to be known before its files could be fetched, which put an unrelated read on the critical path of every draft page.  Two shapes, both listings: the documents under `path` to `depth`, or — with `ref` — that same listing as of a commit. Git-backed drafts only for `ref`; a document-store draft has no history to address and ignores it.  **Listed against the draft\'s last publication.** A draft is a package in draft mode, so a listing of the draft as it stands (no `ref`) reports each document\'s `changeSincePublication` — added, modified, or unchanged — and includes the files the publication shipped that the draft has since deleted, as `removed` entries. A deletion is an edit like any other, and a page rendering the draft\'s files needs all of them from one read. A draft never published, on either backing, is measured against the published version it was opened on (the package\'s latest version when none was recorded), and only for a caller with read access to that package: the markers would otherwise name the package\'s published files, and their absence say which of them the draft leaves unchanged, to a reader who cannot read it. For such a caller the draft\'s own files are listed without markers, with `Changes-Unavailable`. A baseline that exists but cannot be measured or read (a git-backed draft\'s version past the seed\'s bounds, or an archive that failed to download) is `Changes-Unavailable` too, never \"nothing to compare against\". A never-published draft of a package with no published version, or a listing at a `ref`, carries no markers and no removed entries. When the comparison cannot be made (a git compare over the gateway\'s size limit, a transient failure, or a publication recorded before its baseline existed), the listing is still returned, without markers, and says so with the `Changes-Unavailable` header rather than failing.  What changed between two COMMITS is a different question — the History tab\'s — and has its own endpoint: `GET ../comparison`.  Content is omitted from the listing unless `withContent=true`; otherwise read a document to get it.  **Authorization**: requires read access to the draft document.
          * @summary List a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5719,13 +6092,14 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
          * @param {string} [path] Restrict the listing to this subtree, relative to the draft root.
          * @param {number} [depth] `1` lists only the immediate children of `path`, as a file browser would. Omitted returns the whole subtree, which is what a section listing wants. The two are answered by different reads, so they differ in two ways a caller can see. A bounded depth returns directory entries as well as files; the whole subtree returns files only, since a directory is not a document and every caller of the depth-less listing filters to files anyway. And the whole subtree is refused with `413` for a draft holding a symlink or submodule, where a bounded depth lists around it.
          * @param {string} [ref] Read the listing at this commit rather than at the branch tip. Accepts only a full 40-character sha reachable from the draft\'s branch. Ignored by a document-store draft, which has no commits.
+         * @param {boolean} [withContent] Carry each document\'s content on its entry, so a caller that wants the whole draft makes one request rather than one per file. A document\'s text comes as `content`; a file that is not UTF-8 text comes as `contentBase64`. A data file the draft holds beside its documents (`kind` `data`) carries neither, as in any listing. The listing is whole-draft or refused: past the same file-count and byte limits a checkpoint collects under, it answers `413` `draft-listing-too-large` rather than a partial one, and `limit` and `offset` do not lower what is read, only what is returned. Read the files one at a time instead.
          * @param {number} [limit] Maximum number of items to return. Use -1 or omit to return all results.
          * @param {number} [offset] Number of items to skip before starting to return results
          * @param {*} [options] Override http request option.
          * @throws {RequiredError}
          */
-        listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, limit, offset, options) {
-            return localVarFp.listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, limit, offset, options).then((request) => request(axios, basePath));
+        listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, withContent, limit, offset, options) {
+            return localVarFp.listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, withContent, limit, offset, options).then((request) => request(axios, basePath));
         },
         /**
          * The workspace\'s drafts, each as the same `Draft` the item endpoint returns.  **This is how a surface finds drafts.** Before it existed the only way was to list every document in the workspace and filter on type and path prefix, which meant the sidebar, the scope chips and the edit-package flow each pulled every file of every draft in the workspace to render a handful of rows. Composed server-side, one query against the checkpoint rows rather than one request per draft.  **Authorization**: requires read access to the workspace, and each draft is filtered to those the caller can read — the same two-stage bar `listDocuments` applies, since a draft\'s authorization object is still its manifest document.
@@ -5780,7 +6154,7 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
             return localVarFp.updateDraftPullRequest(organizationName, workspaceName, draftId, mergeDraftPullRequest, options).then((request) => request(axios, basePath));
         },
         /**
-         * Asks for a checkpoint of the draft\'s current content. A `POST` to the collection rather than a `PUT` on a singleton: this starts a job and answers `202`, and the checkpoints it appends to are a series (`1.0.N`), not one value being set. Sending it twice is still safe — see the coalescing note below — but that is a property of the nudge, not a claim that the request is idempotent in the `PUT` sense.  The current checkpoint\'s status is a separate read: `GET` on `../checkpoint`.  Records that the draft\'s current content should be published as the next checkpoint (`1.0.N`) of its environment draft package — an ordinary published package named `draft-{draftKey}` in the draft\'s target environment, served by the Publisher exactly like any other package there (docs/workspace-architecture-design.md §4). Always answers `202` with the current status: this call is a nudge, not the publish. The reconciler resolves the draft\'s current content itself when it collects the work — the git branch head for a git-backed draft, the doc-store tree otherwise — which is why the request carries no ref and no content: a caller-supplied ref would be both spoofable and racy against the agent\'s own commits, and a nudge that arrives late still publishes what the draft says NOW.  Nudges coalesce: any number recorded between publishes produce one checkpoint of the newest content, and a nudge whose content is identical to the latest published checkpoint publishes nothing. That is this operation\'s own contract, not something the verb supplies — a `POST` to a collection is not idempotent, so a retry after a lost response would otherwise mint a second checkpoint of content that has not changed.  A failed publish (the draft does not compile, most commonly) records `failed` with the compiler\'s message and leaves the previous checkpoint serving; the next nudge retries with the then-current content.  **This is also how a reaped draft package comes back.** A draft whose package has been idle-reaped (24 hours without a checkpoint request) keeps its row as a witness, and a nudge clears the reap marker and re-queues the publish — the same row update that publishes anything else, so no separate verb is needed. `GET` on this path reports `resurrectable` so a client knows to send one. A merge reap comes back the same way, but a client with the draft page open asks automatically: the app\'s own `POST` rebuilds the package unless the reap\'s own tick wins the race first — at `1.0.0` after the reap, or cancelling the reap and republishing into it. A package a resurrect brought back is a live draft again from there, so the ordinary idle sweep (24 hours since the *last checkpoint request*, not tied to a viewer leaving) reclaims it if nobody keeps asking. Either way a draft that outlives its merge (its close was skipped or its publish failed) can be nudged again, and any later nudge rebuilds it the same way: at `1.0.0` once the reap is deleting the package, or as the next `1.0.N` when the nudge lands before the reap starts and keeps it. Only a deleted draft\'s reap is terminal — its content has no home left — and a nudge for one is refused rather than honoured.  **Authorization**: requires `can_update_document` on the draft document AND the target environment\'s `can_create_package` — the same two bars every content-writing draft operation already takes, so anyone modeling in the draft holds both.
+         * Asks for a checkpoint of the draft\'s current content. A `POST` to the collection rather than a `PUT` on a singleton: this starts a job and answers `202`, and the checkpoints it appends to are a series (`1.0.N`), not one value being set. Sending it twice is still safe — see the coalescing note below — but that is a property of the nudge, not a claim that the request is idempotent in the `PUT` sense.  The current checkpoint\'s status is a separate read: `GET` on `../checkpoint`.  Records that the draft\'s current content should be published as the next checkpoint (`1.0.N`) of its environment draft package — an ordinary published package named `draft-{draftKey}` in the draft\'s target environment, served by the Publisher exactly like any other package there (docs/workspace-architecture-design.md §4). Answers `202` with the current status: this call is a nudge, not the publish. A draft whose branch is still being cut answers `409` `draft-provisioning` and records nothing; retry after a moment. The reconciler resolves the draft\'s current content itself when it collects the work — the git branch head for a git-backed draft, the doc-store tree otherwise — which is why the request carries no ref and no content: a caller-supplied ref would be both spoofable and racy against the agent\'s own commits, and a nudge that arrives late still publishes what the draft says NOW.  Nudges coalesce: any number recorded between publishes produce one checkpoint of the newest content, and a nudge whose content is identical to the latest published checkpoint publishes nothing. That is this operation\'s own contract, not something the verb supplies — a `POST` to a collection is not idempotent, so a retry after a lost response would otherwise mint a second checkpoint of content that has not changed.  A failed publish (the draft does not compile, most commonly) records `failed` with the compiler\'s message and leaves the previous checkpoint serving; the next nudge retries with the then-current content.  **This is also how a reaped draft package comes back.** A draft whose package has been idle-reaped (24 hours without a checkpoint request) keeps its row as a witness, and a nudge clears the reap marker and re-queues the publish — the same row update that publishes anything else, so no separate verb is needed. `GET` on this path reports `resurrectable` so a client knows to send one. A merge reap comes back the same way, but a client with the draft page open asks automatically: the app\'s own `POST` rebuilds the package unless the reap\'s own tick wins the race first — at `1.0.0` after the reap, or cancelling the reap and republishing into it. A package a resurrect brought back is a live draft again from there, so the ordinary idle sweep (24 hours since the *last checkpoint request*, not tied to a viewer leaving) reclaims it if nobody keeps asking. Either way a draft that outlives its merge (its close was skipped or its publish failed) can be nudged again, and any later nudge rebuilds it the same way: at `1.0.0` once the reap is deleting the package, or as the next `1.0.N` when the nudge lands before the reap starts and keeps it. Only a deleted draft\'s reap is terminal — its content has no home left — and a nudge for one is refused rather than honoured.  **Authorization**: requires `can_update_document` on the draft document AND the target environment\'s `can_create_package` — the same two bars every content-writing draft operation already takes, so anyone modeling in the draft holds both.
          * @summary Set the draft\'s checkpoint to its current content
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5792,7 +6166,7 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
             return localVarFp.writeDraftCheckpoint(organizationName, workspaceName, draftId, options).then((request) => request(axios, basePath));
         },
         /**
-         * Creates or replaces a document, whichever storage backs the draft. `PUT` rather than `POST` because the path is the identifier and the caller chooses it — there is no server-assigned id for a file, so a collection `POST` would have nothing to assign.  **The precondition depends on the storage, and each is refused on the other.** On a git-backed draft `expectedRef` is required and is the BRANCH HEAD the writer read at, not the document\'s own blob sha: the gateway refuses to build on anything but the branch\'s current tip, so a stale value means the draft moved under the writer. Take it from `getDraftDocument`\'s `ref`, and read the document at the head you intend to write against — reading the document first and the head second pairs content from one commit with a precondition naming a later one, which passes the swap and silently overwrites whatever moved in between.  On a document-store draft the precondition is per file: `expectedSha` (the `sha` the writer read) replaces the document only if it still holds that version, and `createOnly` creates it only if no document is there. Either is checked in the same statement that writes, so of two writers holding the same `sha` exactly one wins and the other gets `409` `draft-document-stale`. They are mutually exclusive (`400` when both are sent). With neither, the write is last-writer-wins, as a write through the documents API has always been. `expectedRef` is refused on a document-store draft, and `expectedSha` and `createOnly` are refused on a git-backed one, rather than ignored: a caller that sends a precondition believes it holds a guarantee.  On a document-store draft the server requests the draft\'s checkpoint after the write commits, so a client does not request one itself.  **Authorization** — `can_update_document` on the draft document, **and** `can_create_package` on the draft\'s target environment, on either backing. The second is not redundant: `can_update_document` on a draft is satisfied by bare workspace membership, while a file written here reaches the environment on the draft author\'s next checkpoint, carrying the checkpointer\'s bar rather than the writer\'s. A git-backed write also commits into that environment\'s repository. The environment comes from the draft\'s own manifest and is never a request field; a draft that names none is refused, since it could not be published either.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
+         * Creates or replaces a document, whichever storage backs the draft. `PUT` rather than `POST` because the path is the identifier and the caller chooses it — there is no server-assigned id for a file, so a collection `POST` would have nothing to assign.  **The precondition is per file, on either backing.** `expectedSha` (the `sha` the writer read) replaces the document only if it still holds that version, and `createOnly` creates it only if no document is there. Of two writers holding the same `sha` exactly one wins and the other gets `409` `draft-document-stale`, except that a resent write that already landed is answered as applied (below). They are mutually exclusive (`400` when both are sent). With neither, the write is last-writer-wins, as a write through the documents API has always been.  On either backing a retry whose change is already in place (the content is current, or the file to delete is gone) is answered as applied, not as a conflict, so a lost response can be resent. A deletion of a gone file with an `expectedSha` counts as applied only when no write in the same set is still to land: a move whose old path was deleted or moved by someone else is stale (`\"\"`), not a second copy.  On a git-backed draft the check is made against the branch\'s current files, so a commit that touched only OTHER files does not fail the write: the server re-sends it once on the new tip, and answers `409` `draft-write-contended` if the tip kept moving.  `expectedRef` is deprecated and git-only: the BRANCH HEAD the writer read at, which any commit to any file makes stale (`409` `draft-file-stale-head`). It is refused together with `expectedSha` or `createOnly`, and refused on a document-store draft rather than ignored: a caller that sends a precondition believes it holds a guarantee.  On a document-store draft the server requests the draft\'s checkpoint after the write commits, so a client does not request one itself.  **Authorization** — `can_update_document` on the draft document, **and** `can_create_package` on the draft\'s target environment, on either backing. The second is not redundant: `can_update_document` on a draft is satisfied by bare workspace membership, while a file written here reaches the environment on the draft author\'s next checkpoint, carrying the checkpointer\'s bar rather than the writer\'s. A git-backed write also commits into that environment\'s repository. The environment comes from the draft\'s own manifest and is never a request field; a draft that names none is refused, since it could not be published either.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
          * @summary Write one of a draft\'s documents
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5820,7 +6194,7 @@ const DraftsApiFactory = function (configuration, basePath, axios) {
             return localVarFp.writeDraftDocumentContent(organizationName, workspaceName, draftId, documentPath, body, options).then((request) => request(axios, basePath));
         },
         /**
-         * Writes a set of documents together. On a git-backed draft they land as **one commit**, which is the reason this exists beside the per-document `PUT`: seeding a draft from a package is a single logical change, and writing its files one at a time would put N commits in the History tab for one action — and leave a reader of any intermediate commit looking at half a package.  Ordinary editing uses the per-document `PUT`. This is for the cases that are atomic by nature: the seed, and a multi-file edit that should be reviewable as one diff.  `expectedRef` applies to the whole set, and a client-minted `intentTimestamp` resent byte-identical makes a retried write a replay rather than a second commit — which matters more here than for one document, since a lost response after an N-file commit is otherwise indistinguishable from a write that never landed.  On a document-store draft each member may carry its own `expectedSha` or `createOnly` (see `writeDraftDocument`), so a move is one set: `createOnly` on the new path and a deletion with `expectedSha` on the old one. The set stays all-or-nothing: if any member\'s precondition fails, none is written and the `409` `draft-document-stale` names every conflicting path.  **Authorization**: as `writeDraftDocument`.  **Fenced by a work item.** A caller executing a work item (one claimed through the controlplane\'s private work-item API) sends its claim in `Work-Item-Claim` (`{id}@{generation}`). The claim is checked first thing in the transaction that writes the document rows, and refused with `409` `draft-write-fenced` -- writing nothing -- when it is no longer the live one: released, cancelled, or swept after its holder stopped heartbeating. On a branch-backed draft the commit is made by the gateway, so the claim is checked just before it: a cancel that lands during that one commit can let it through, and the commit\'s `Turn-Work-Item` trailer records which item wrote it. A malformed header is a `400`. Without the header the write is unfenced, as before. Only this operation honors the header.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
+         * Writes a set of documents together. On a git-backed draft they land as **one commit**, which is the reason this exists beside the per-document `PUT`: seeding a draft from a package is a single logical change, and writing its files one at a time would put N commits in the History tab for one action — and leave a reader of any intermediate commit looking at half a package.  Ordinary editing uses the per-document `PUT`. This is for the cases that are atomic by nature: the seed, and a multi-file edit that should be reviewable as one diff.  Each member may carry its own `expectedSha` or `createOnly` on either backing (see `writeDraftDocument`), so a move is one set: `createOnly` on the new path and a deletion with `expectedSha` on the old one. If any member\'s precondition fails, none is written and the `409` `draft-document-stale` names every conflicting path; a set already partly in place (a resent one) commits only what remains.  `expectedRef` is deprecated: it applies to the whole set, is git-only, and is refused together with a member\'s `expectedSha` or `createOnly`. A client-minted `intentTimestamp` resent byte-identical makes a retried write a replay rather than a second commit — which matters more here than for one document, since a lost response after an N-file commit is otherwise indistinguishable from a write that never landed.  **Authorization**: as `writeDraftDocument`.  **Fenced by a work item.** A caller executing a work item (one claimed through the controlplane\'s private work-item API) sends its claim in `Work-Item-Claim` (`{id}@{generation}`). The claim is checked first thing in the transaction that writes the document rows, and refused with `409` `draft-write-fenced` -- writing nothing -- when it is no longer the live one: released, cancelled, or swept after its holder stopped heartbeating. On a branch-backed draft the commit is made by the gateway, so the claim is checked just before it: a cancel that lands during that one commit can let it through, and the commit\'s `Turn-Work-Item` trailer records which item wrote it. A malformed header is a `400`. Without the header the write is unfenced, as before. Only this operation honors the header.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
          * @summary Write several of a draft\'s documents as one change
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} workspaceName The unique identifier of the workspace
@@ -5881,7 +6255,7 @@ class DraftsApi extends base_1.BaseAPI {
         return (0, exports.DraftsApiFp)(this.configuration).createDraft(organizationName, workspaceName, draftCreateRequest, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Deletes the draft: its manifest and, for a document-store draft, its files. Its environment draft package is marked for the checkpoint reaper, so what was serving the draft is removed on the next tick.  **The branch lives on.** Deleting a draft does not delete its git branch (docs/git-synced-modeling.md §7.2). Branch removal was inherited from the document model — documents are deletable, so a draft\'s branch looked like it had to go too — and every failure mode of that obligation had to be handled. Git\'s model is the opposite: branches accumulate and tidying is a convenience. Once a draft has had a pull request, GitHub retains `refs/pull/N/head` permanently, so deleting the branch would not remove the content anyway. Removing a branch is `DELETE .../drafts/{draftId}/branch`, and the one case worth tidying — a branch nothing was ever committed to — is the caller\'s to decide. The other case is server-side: a successful publish closes the draft and deletes its branch with it (see `writeDraftPublication` and `createOrUpdatePackage`\'s `draftId`).  **A second delete, or a read after this one, answers 404** to a caller who can use the workspace (403 to one who cannot): the gate is the workspace\'s, and the row is gone.  **Authorization**: requires `can_delete_document` on the draft document, and `can_create_package` on the environment it targets.
+     * Deletes the draft: its manifest and, for a document-store draft, its files. Its environment draft package is marked for the checkpoint reaper, so what was serving the draft is removed on the next tick.  **The branch usually lives on.** Deleting a draft does not delete its git branch (docs/git-synced-modeling.md §7.2), with one server-side exception: a draft that was never published and still sits at its seed commit has its branch deleted first, best-effort, so a draft minted from a misread intent leaves nothing behind. The delete is pinned to the seed commit, so a commit that landed since keeps the branch; the pin is not a compare-and-swap, so a commit landing in the instant between the gateway\'s tip re-read and its delete is lost. A failed branch delete never blocks the draft\'s delete, and retrying after a partial failure finds the branch already gone. Every other branch is removed by `DELETE .../drafts/{draftId}/branch`, or by the close after a successful publish (see `writeDraftPublication` and `createOrUpdatePackage`\'s `draftId`).  **A second delete, or a read after this one, answers 404** to a caller who can use the workspace (403 to one who cannot): the gate is the workspace\'s, and the row is gone.  **Authorization**: requires `can_delete_document` on the draft document, and `can_create_package` on the environment it targets.
      * @summary Delete a draft package
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
@@ -5894,7 +6268,7 @@ class DraftsApi extends base_1.BaseAPI {
         return (0, exports.DraftsApiFp)(this.configuration).deleteDraft(organizationName, workspaceName, draftId, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Thin proxy to the code-assist git-gateway\'s `deleteDraft` — deletes the draft\'s branch in the managed monorepo. See `listDraftCommits` for the auth-forwarding notes.  **This is branch removal only — it does not delete the draft.** Deleting the draft is `DELETE` on the draft itself.  One product path calls this, and only one: since the 2026-08-15 \"branches live on\" decision (docs/git-synced-modeling.md §7.2) deleting a draft deletes the manifest and leaves the branch, so the agent\'s `delete_file` cascade makes no branch call at all, and the app\'s delete tidies the branch only for a draft nothing was ever committed to (the §7.2 amendment of 2026-08-24). Otherwise it is the primitive operator tooling needs — see docs/tenant-offboarding-playbook.md, which prefers it over a raw GitHub call precisely because it carries the FGA check below. The close after a successful publish also deletes a draft\'s branch, but through the gateway directly rather than through this endpoint.  **Authorization**: Requires write access to the draft\'s workspace (`can_create_document`) and `can_create_package` on the environment the draft targets, as deleting the draft does. The gateway re-checks the workspace relation.  Idempotent, and deliberately not gated on the draft being git-backed, so a provisioning draft\'s half-cut branch can still be cleaned up.
+     * Thin proxy to the code-assist git-gateway\'s `deleteDraft` — deletes the draft\'s branch in the managed monorepo. See `listDraftCommits` for the auth-forwarding notes.  **This is branch removal only — it does not delete the draft.** Deleting the draft is `DELETE` on the draft itself.  Stays as the primitive operator tooling needs: `deleteDraft` deletes an untouched draft\'s branch at its seed commit on the server (docs/git-synced-modeling.md §7.2), so neither the app nor the agent needs to call this. See docs/tenant-offboarding-playbook.md, which prefers it over a raw GitHub call precisely because it carries the FGA check below. The close after a successful publish also deletes a draft\'s branch, but through the gateway directly rather than through this endpoint.  **Authorization**: Requires write access to the draft\'s workspace (`can_create_document`) and `can_create_package` on the environment the draft targets, as deleting the draft does. The gateway re-checks the workspace relation.  Idempotent, and deliberately not gated on the draft being git-backed, so a provisioning draft\'s half-cut branch can still be cleaned up.
      * @summary Delete a git-backed draft\'s branch
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
@@ -5913,8 +6287,8 @@ class DraftsApi extends base_1.BaseAPI {
      * @param {string} workspaceName The unique identifier of the workspace
      * @param {string} draftId The draft package identifier
      * @param {string} documentPath The document\'s path relative to the draft root
-     * @param {string} [expectedRef] The branch head the caller read at. For a text document on a git-backed draft it is required; for a data file there it is ignored, since a data file\'s delete is not a commit. Refused for a document-store draft, data file or not — there is no commit to compare it against. See `writeDraftDocument` for why it is the branch head rather than the document\'s own sha.
-     * @param {string} [expectedSha] The `sha` the caller read the document at. Document-store drafts only, refused for a git-backed one: the delete applies only if the document still holds that version, else `409` `draft-document-stale`.
+     * @param {string} [expectedRef] Deprecated, git-only: use `expectedSha`. The branch head the caller read at; for a data file it is ignored, since a data file\'s delete is not a commit. Refused with `expectedSha`, and refused for a document-store draft, data file or not — there is no commit to compare it against.
+     * @param {string} [expectedSha] The `sha` the caller read the document at, on either backing: the delete applies only if the document still holds that version, else `409` `draft-document-stale`; a file already gone counts as deleted when this is the whole request, so a lost response can be resent.
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
      * @memberof DraftsApi
@@ -5923,13 +6297,13 @@ class DraftsApi extends base_1.BaseAPI {
         return (0, exports.DraftsApiFp)(this.configuration).deleteDraftDocument(organizationName, workspaceName, draftId, documentPath, expectedRef, expectedSha, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Discards the draft\'s change to one file, so the draft carries what its publication has at this path again. This is Restore, for any kind of file; after it the path has no `changeSincePublication` marker. `DELETE` on the document itself deletes the file instead — a different change, which this would undo.  What it does follows the file\'s change marker, never whether a published copy can be read:  - A data file: the draft\'s own upload or deletion is dropped. Where the draft\'s last   publish shipped its own upload, the path returns to that upload; otherwise the   published copy is inherited again, and a small UTF-8 file, which a draft holds as a   document rather than inheriting, is written back as one. `expectedRef` is optional   here, as it is absent on a data file\'s delete: when given on a git-backed draft, the   commit that writes a small published copy back builds on it (`409   draft-file-stale-head` if the branch has moved since), and on the branch\'s current   head when it is not given. - A text file the draft added: deleted. - A text file the draft edited or deleted: the published copy written back. Answers   as `getDraftDocument` with `ref=publication` does when that copy cannot be read   (`404` `draft-file-not-in-publication`, `409`, `413`, `503`), changing nothing.  `404` `draft-document-unchanged` when the draft has no change at this path — a data file the draft\'s last publish shipped and has not touched since included; `503` `draft-changes-unavailable` when its changes could not be compared with its publication.  **Authorization** — the same pair `writeDraftDocument` takes.
+     * Discards the draft\'s change to one file, so the draft carries what its publication has at this path again. This is Restore, for any kind of file; after it the path has no `changeSincePublication` marker. `DELETE` on the document itself deletes the file instead — a different change, which this would undo.  What it does follows the file\'s change marker, never whether a published copy can be read:  - A data file: the draft\'s own upload or deletion is dropped. Where the draft\'s last   publish shipped its own upload, the path returns to that upload; otherwise the   published copy is inherited again, and a small UTF-8 file, which a draft holds as a   document rather than inheriting, is written back as one. The deprecated `expectedRef`   is optional here, as it is absent on a data file\'s delete: when given on a git-backed   draft, the commit that writes a small published copy back builds on it (`409   draft-file-stale-head` if the branch has moved since), and on the branch\'s current   head when it is not given. - A text file the draft added: deleted. - A text file the draft edited or deleted: the published copy written back. Answers   as `getDraftDocument` with `ref=publication` does when that copy cannot be read   (`404` `draft-file-not-in-publication`, `409`, `413`, `503`), changing nothing.  `404` `draft-document-unchanged` when the draft has no change at this path — a data file the draft\'s last publish shipped and has not touched since included. Before any change is found, the comparison itself can be refused, with the answers a read of the baseline gives: `403` when the caller cannot read the package the draft is measured against, `409` `draft-publication-baseline-missing` when that baseline cannot be measured (past a git-backed draft\'s seed bounds, or a corrupt archive), and `503` `draft-changes-unavailable` when it could not be read.  **Authorization** — the same pair `writeDraftDocument` takes.
      * @summary Restore one of a draft\'s files to its published copy
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
      * @param {string} draftId The draft package identifier
      * @param {string} documentPath The file\'s path relative to the draft root
-     * @param {string} [expectedRef] The branch head the caller read at, for a git-backed draft where the restore is a commit: required for a text file, optional for a data file (used as the compare-and-swap base when a small published copy is written back as a document); refused for a document-store draft.
+     * @param {string} [expectedRef] Deprecated: the restore builds on the branch\'s current head without it. The branch head the caller read at, for a git-backed draft where the restore is a commit (used as the compare-and-swap base); refused for a document-store draft.
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
      * @memberof DraftsApi
@@ -5963,6 +6337,19 @@ class DraftsApi extends base_1.BaseAPI {
     getDraftBranch(organizationName, workspaceName, draftId, options) {
         return (0, exports.DraftsApiFp)(this.configuration).getDraftBranch(organizationName, workspaceName, draftId, options).then((request) => request(this.axios, this.basePath));
     }
+    /**
+     * The draft\'s capabilities, derived by the server from where its files live and what its package has published, so a client asks this rather than branching on `backing`. The same value `getDraft` carries as `capabilities`, for a caller that does not need the rest of the draft: it reads the draft\'s location and one published-version lookup, not the checkpoint, the files or the git gateway.  A draft whose branch is still being cut answers `200` with `ready: false` and nothing else, never a refusal: the answer is \"not yet\", and it changes by itself.  **Authorization**: requires read access to the draft document.
+     * @summary What the draft\'s storage can do
+     * @param {string} organizationName The unique identifier of the organization
+     * @param {string} workspaceName The unique identifier of the workspace
+     * @param {string} draftId The draft package identifier
+     * @param {*} [options] Override http request option.
+     * @throws {RequiredError}
+     * @memberof DraftsApi
+     */
+    getDraftCapabilities(organizationName, workspaceName, draftId, options) {
+        return (0, exports.DraftsApiFp)(this.configuration).getDraftCapabilities(organizationName, workspaceName, draftId, options).then((request) => request(this.axios, this.basePath));
+    }
     /**
      * Reports where the draft\'s environment package stands. Always answers `200`; `status` is `none` before the first checkpoint is requested, so a polling client does not treat absence as an error.  **A pure read**, and the cheap one: this is what a client polls while a checkpoint is unsettled. It performs no write and starts no publish.  This is a pure read. Resurrecting an idle-reaped draft package is a `POST` to `../checkpoints`, so that a publish into a live environment follows from an explicit request rather than from whichever tab last refreshed. `resurrectable` on the response says whether such a request would rebuild anything.  **Authorization**: requires read access to the draft document, the same bar as the other draft reads.
      * @summary The draft\'s checkpoint status
@@ -6007,7 +6394,7 @@ class DraftsApi extends base_1.BaseAPI {
         return (0, exports.DraftsApiFp)(this.configuration).getDraftContent(organizationName, workspaceName, draftId, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * One document\'s content, whichever storage backs the draft. See `listDraftDocuments` for why the backing is not the caller\'s concern.  Refuses with `413` (`draft-file-unreadable`) when the document is not readable as UTF-8 text under 1MB. That is a permanent refusal about the file\'s shape, not a transient failure: the same refusal stops a publish, so retrying achieves nothing until the file is removed or replaced.  **`ref=publication`** reads the document as it is in the version the draft\'s `changeSincePublication` markers compare against. The baseline is resolved server-side, never taken from the caller: for a git-backed draft, the draft-branch commit its last publish shipped (`publishedAs.commitSha`); for a document-store draft, the stored archive of its last published version, or — for one never published — of the version it was opened on. The answers, each distinct:  - `200`: the file\'s content in that baseline. - `403`: on a document-store draft, the caller can read the draft but not the   package whose archive the baseline is. The archive is the package\'s, and   workspace access does not imply environment access, so this read also takes   `can_read_package` on it. A git-backed baseline is the draft\'s own branch. - `404` `draft-file-not-in-publication`: the baseline exists and does not hold   this file. There is nothing to restore from it. - `409` `draft-publication-baseline-missing`: there is no baseline to read — a   draft never published and opened on nothing, a publication recorded before   baselines were, a published version with no stored archive, one whose archive is   corrupt, or one that no longer holds what its publish recorded, or a published   commit no longer on the draft\'s branch. Permanent until the draft publishes again. - `413` `draft-file-unreadable`: the baseline\'s copy is not UTF-8 text under 1MB. - `503` `draft-publication-unreadable`: the baseline exists but could not be read   right now. Retryable.  On a document-store draft the content is the published archive\'s bytes decoded as UTF-8, so its SHA-256 is the hash the markers were computed from. A published file a draft cannot hold (binary, or 1 MiB and over) is inherited by the draft rather than held, so it is not in the baseline and answers `404`. `ref` is null on a document-store answer; on a git answer it names the published commit, which is NOT a head a compare-and-swap write can build on — read the head separately before writing.  **Authorization**: requires read access to the draft document.
+     * One document\'s content, whichever storage backs the draft. See `listDraftDocuments` for why the backing is not the caller\'s concern.  Refuses with `413` (`draft-file-unreadable`) when the document is not readable as UTF-8 text under 1MB. That is a permanent refusal about the file\'s shape, not a transient failure: the same refusal stops a publish, so retrying achieves nothing until the file is removed or replaced.  **`ref=publication`** reads the document as it is in the version the draft\'s `changeSincePublication` markers compare against. The baseline is resolved server-side, never taken from the caller: for a git-backed draft, the draft-branch commit its last publish shipped (`publishedAs.commitSha`); for a document-store draft, the stored archive of its last published version, or — for one never published — of the version it was opened on. The answers, each distinct:  - `200`: the file\'s content in that baseline. - `403`: the baseline is the package\'s stored archive (a document-store draft\'s, or a   git-backed draft\'s never published) and the caller can read the draft but not the   package. Workspace access does not imply environment access, so this read also   takes `can_read_package` on it. A published git-backed draft\'s baseline is its own   branch at `publishedAs.commitSha`, readable by that sha at the draft\'s bar, so it   takes no package bar. - `404` `draft-file-not-in-publication`: the baseline exists and does not hold   this file. There is nothing to restore from it. - `409` `draft-publication-baseline-missing`: there is no baseline to read — a   draft never published and opened on nothing, a publication recorded before   baselines were, a published version with no stored archive, one whose archive is   corrupt, or one that no longer holds what its publish recorded, or a published   commit no longer on the draft\'s branch. Permanent until the draft publishes again. - `413` `draft-file-unreadable`: the baseline\'s copy is not UTF-8 text under 1MB. - `503` `draft-publication-unreadable`: the baseline exists but could not be read   right now. Retryable.  On a document-store draft the content is the published archive\'s bytes decoded as UTF-8, so its SHA-256 is the hash the markers were computed from. A published file a draft cannot hold (binary, or 1 MiB and over) is inherited by the draft rather than held, so it is not in the baseline and answers `404`. `ref` is null on a document-store answer; on a git answer it names the published commit, which is NOT a head a compare-and-swap write can build on — read the head separately before writing.  **Authorization**: requires read access to the draft document.
      * @summary Read one of a draft\'s documents
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
@@ -6064,7 +6451,7 @@ class DraftsApi extends base_1.BaseAPI {
         return (0, exports.DraftsApiFp)(this.configuration).listDraftCommits(organizationName, workspaceName, draftId, limit, offset, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * The draft\'s files, **whichever storage backs them**. A git-backed draft\'s files live on its branch and a document-store draft\'s live as workspace documents; this answers for both, so a client never branches on the backing to read a draft\'s contents. That branch is the reason a draft\'s backing had to be known before its files could be fetched, which put an unrelated read on the critical path of every draft page.  Two shapes, both listings: the documents under `path` to `depth`, or — with `ref` — that same listing as of a commit. Git-backed drafts only for `ref`; a document-store draft has no history to address and ignores it.  **Listed against the draft\'s last publication.** A draft is a package in draft mode, so a listing of the draft as it stands (no `ref`) reports each document\'s `changeSincePublication` — added, modified, or unchanged — and includes the files the publication shipped that the draft has since deleted, as `removed` entries. A deletion is an edit like any other, and a page rendering the draft\'s files needs all of them from one read. A document-store draft never published is measured against the published version it was opened on, and only for a caller with read access to that package: the markers would otherwise name the package\'s published files, and their absence say which of them the draft leaves unchanged, to a reader who cannot read it. For such a caller the draft\'s own files are listed without markers, with `Changes-Unavailable`. Any other never-published draft, or a listing at a `ref`, carries no markers and no removed entries. When the comparison cannot be made (a git compare over the gateway\'s size limit, a transient failure, or a publication recorded before its baseline existed), the listing is still returned, without markers, and says so with the `Changes-Unavailable` header rather than failing.  What changed between two COMMITS is a different question — the History tab\'s — and has its own endpoint: `GET ../comparison`.  Content is omitted from the listing; read a document to get it.  **Authorization**: requires read access to the draft document.
+     * The draft\'s files, **whichever storage backs them**. A git-backed draft\'s files live on its branch and a document-store draft\'s live as workspace documents; this answers for both, so a client never branches on the backing to read a draft\'s contents. That branch is the reason a draft\'s backing had to be known before its files could be fetched, which put an unrelated read on the critical path of every draft page.  Two shapes, both listings: the documents under `path` to `depth`, or — with `ref` — that same listing as of a commit. Git-backed drafts only for `ref`; a document-store draft has no history to address and ignores it.  **Listed against the draft\'s last publication.** A draft is a package in draft mode, so a listing of the draft as it stands (no `ref`) reports each document\'s `changeSincePublication` — added, modified, or unchanged — and includes the files the publication shipped that the draft has since deleted, as `removed` entries. A deletion is an edit like any other, and a page rendering the draft\'s files needs all of them from one read. A draft never published, on either backing, is measured against the published version it was opened on (the package\'s latest version when none was recorded), and only for a caller with read access to that package: the markers would otherwise name the package\'s published files, and their absence say which of them the draft leaves unchanged, to a reader who cannot read it. For such a caller the draft\'s own files are listed without markers, with `Changes-Unavailable`. A baseline that exists but cannot be measured or read (a git-backed draft\'s version past the seed\'s bounds, or an archive that failed to download) is `Changes-Unavailable` too, never \"nothing to compare against\". A never-published draft of a package with no published version, or a listing at a `ref`, carries no markers and no removed entries. When the comparison cannot be made (a git compare over the gateway\'s size limit, a transient failure, or a publication recorded before its baseline existed), the listing is still returned, without markers, and says so with the `Changes-Unavailable` header rather than failing.  What changed between two COMMITS is a different question — the History tab\'s — and has its own endpoint: `GET ../comparison`.  Content is omitted from the listing unless `withContent=true`; otherwise read a document to get it.  **Authorization**: requires read access to the draft document.
      * @summary List a draft\'s documents
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
@@ -6072,14 +6459,15 @@ class DraftsApi extends base_1.BaseAPI {
      * @param {string} [path] Restrict the listing to this subtree, relative to the draft root.
      * @param {number} [depth] `1` lists only the immediate children of `path`, as a file browser would. Omitted returns the whole subtree, which is what a section listing wants. The two are answered by different reads, so they differ in two ways a caller can see. A bounded depth returns directory entries as well as files; the whole subtree returns files only, since a directory is not a document and every caller of the depth-less listing filters to files anyway. And the whole subtree is refused with `413` for a draft holding a symlink or submodule, where a bounded depth lists around it.
      * @param {string} [ref] Read the listing at this commit rather than at the branch tip. Accepts only a full 40-character sha reachable from the draft\'s branch. Ignored by a document-store draft, which has no commits.
+     * @param {boolean} [withContent] Carry each document\'s content on its entry, so a caller that wants the whole draft makes one request rather than one per file. A document\'s text comes as `content`; a file that is not UTF-8 text comes as `contentBase64`. A data file the draft holds beside its documents (`kind` `data`) carries neither, as in any listing. The listing is whole-draft or refused: past the same file-count and byte limits a checkpoint collects under, it answers `413` `draft-listing-too-large` rather than a partial one, and `limit` and `offset` do not lower what is read, only what is returned. Read the files one at a time instead.
      * @param {number} [limit] Maximum number of items to return. Use -1 or omit to return all results.
      * @param {number} [offset] Number of items to skip before starting to return results
      * @param {*} [options] Override http request option.
      * @throws {RequiredError}
      * @memberof DraftsApi
      */
-    listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, limit, offset, options) {
-        return (0, exports.DraftsApiFp)(this.configuration).listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, limit, offset, options).then((request) => request(this.axios, this.basePath));
+    listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, withContent, limit, offset, options) {
+        return (0, exports.DraftsApiFp)(this.configuration).listDraftDocuments(organizationName, workspaceName, draftId, path, depth, ref, withContent, limit, offset, options).then((request) => request(this.axios, this.basePath));
     }
     /**
      * The workspace\'s drafts, each as the same `Draft` the item endpoint returns.  **This is how a surface finds drafts.** Before it existed the only way was to list every document in the workspace and filter on type and path prefix, which meant the sidebar, the scope chips and the edit-package flow each pulled every file of every draft in the workspace to render a handful of rows. Composed server-side, one query against the checkpoint rows rather than one request per draft.  **Authorization**: requires read access to the workspace, and each draft is filtered to those the caller can read — the same two-stage bar `listDocuments` applies, since a draft\'s authorization object is still its manifest document.
@@ -6138,7 +6526,7 @@ class DraftsApi extends base_1.BaseAPI {
         return (0, exports.DraftsApiFp)(this.configuration).updateDraftPullRequest(organizationName, workspaceName, draftId, mergeDraftPullRequest, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Asks for a checkpoint of the draft\'s current content. A `POST` to the collection rather than a `PUT` on a singleton: this starts a job and answers `202`, and the checkpoints it appends to are a series (`1.0.N`), not one value being set. Sending it twice is still safe — see the coalescing note below — but that is a property of the nudge, not a claim that the request is idempotent in the `PUT` sense.  The current checkpoint\'s status is a separate read: `GET` on `../checkpoint`.  Records that the draft\'s current content should be published as the next checkpoint (`1.0.N`) of its environment draft package — an ordinary published package named `draft-{draftKey}` in the draft\'s target environment, served by the Publisher exactly like any other package there (docs/workspace-architecture-design.md §4). Always answers `202` with the current status: this call is a nudge, not the publish. The reconciler resolves the draft\'s current content itself when it collects the work — the git branch head for a git-backed draft, the doc-store tree otherwise — which is why the request carries no ref and no content: a caller-supplied ref would be both spoofable and racy against the agent\'s own commits, and a nudge that arrives late still publishes what the draft says NOW.  Nudges coalesce: any number recorded between publishes produce one checkpoint of the newest content, and a nudge whose content is identical to the latest published checkpoint publishes nothing. That is this operation\'s own contract, not something the verb supplies — a `POST` to a collection is not idempotent, so a retry after a lost response would otherwise mint a second checkpoint of content that has not changed.  A failed publish (the draft does not compile, most commonly) records `failed` with the compiler\'s message and leaves the previous checkpoint serving; the next nudge retries with the then-current content.  **This is also how a reaped draft package comes back.** A draft whose package has been idle-reaped (24 hours without a checkpoint request) keeps its row as a witness, and a nudge clears the reap marker and re-queues the publish — the same row update that publishes anything else, so no separate verb is needed. `GET` on this path reports `resurrectable` so a client knows to send one. A merge reap comes back the same way, but a client with the draft page open asks automatically: the app\'s own `POST` rebuilds the package unless the reap\'s own tick wins the race first — at `1.0.0` after the reap, or cancelling the reap and republishing into it. A package a resurrect brought back is a live draft again from there, so the ordinary idle sweep (24 hours since the *last checkpoint request*, not tied to a viewer leaving) reclaims it if nobody keeps asking. Either way a draft that outlives its merge (its close was skipped or its publish failed) can be nudged again, and any later nudge rebuilds it the same way: at `1.0.0` once the reap is deleting the package, or as the next `1.0.N` when the nudge lands before the reap starts and keeps it. Only a deleted draft\'s reap is terminal — its content has no home left — and a nudge for one is refused rather than honoured.  **Authorization**: requires `can_update_document` on the draft document AND the target environment\'s `can_create_package` — the same two bars every content-writing draft operation already takes, so anyone modeling in the draft holds both.
+     * Asks for a checkpoint of the draft\'s current content. A `POST` to the collection rather than a `PUT` on a singleton: this starts a job and answers `202`, and the checkpoints it appends to are a series (`1.0.N`), not one value being set. Sending it twice is still safe — see the coalescing note below — but that is a property of the nudge, not a claim that the request is idempotent in the `PUT` sense.  The current checkpoint\'s status is a separate read: `GET` on `../checkpoint`.  Records that the draft\'s current content should be published as the next checkpoint (`1.0.N`) of its environment draft package — an ordinary published package named `draft-{draftKey}` in the draft\'s target environment, served by the Publisher exactly like any other package there (docs/workspace-architecture-design.md §4). Answers `202` with the current status: this call is a nudge, not the publish. A draft whose branch is still being cut answers `409` `draft-provisioning` and records nothing; retry after a moment. The reconciler resolves the draft\'s current content itself when it collects the work — the git branch head for a git-backed draft, the doc-store tree otherwise — which is why the request carries no ref and no content: a caller-supplied ref would be both spoofable and racy against the agent\'s own commits, and a nudge that arrives late still publishes what the draft says NOW.  Nudges coalesce: any number recorded between publishes produce one checkpoint of the newest content, and a nudge whose content is identical to the latest published checkpoint publishes nothing. That is this operation\'s own contract, not something the verb supplies — a `POST` to a collection is not idempotent, so a retry after a lost response would otherwise mint a second checkpoint of content that has not changed.  A failed publish (the draft does not compile, most commonly) records `failed` with the compiler\'s message and leaves the previous checkpoint serving; the next nudge retries with the then-current content.  **This is also how a reaped draft package comes back.** A draft whose package has been idle-reaped (24 hours without a checkpoint request) keeps its row as a witness, and a nudge clears the reap marker and re-queues the publish — the same row update that publishes anything else, so no separate verb is needed. `GET` on this path reports `resurrectable` so a client knows to send one. A merge reap comes back the same way, but a client with the draft page open asks automatically: the app\'s own `POST` rebuilds the package unless the reap\'s own tick wins the race first — at `1.0.0` after the reap, or cancelling the reap and republishing into it. A package a resurrect brought back is a live draft again from there, so the ordinary idle sweep (24 hours since the *last checkpoint request*, not tied to a viewer leaving) reclaims it if nobody keeps asking. Either way a draft that outlives its merge (its close was skipped or its publish failed) can be nudged again, and any later nudge rebuilds it the same way: at `1.0.0` once the reap is deleting the package, or as the next `1.0.N` when the nudge lands before the reap starts and keeps it. Only a deleted draft\'s reap is terminal — its content has no home left — and a nudge for one is refused rather than honoured.  **Authorization**: requires `can_update_document` on the draft document AND the target environment\'s `can_create_package` — the same two bars every content-writing draft operation already takes, so anyone modeling in the draft holds both.
      * @summary Set the draft\'s checkpoint to its current content
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
@@ -6151,7 +6539,7 @@ class DraftsApi extends base_1.BaseAPI {
         return (0, exports.DraftsApiFp)(this.configuration).writeDraftCheckpoint(organizationName, workspaceName, draftId, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Creates or replaces a document, whichever storage backs the draft. `PUT` rather than `POST` because the path is the identifier and the caller chooses it — there is no server-assigned id for a file, so a collection `POST` would have nothing to assign.  **The precondition depends on the storage, and each is refused on the other.** On a git-backed draft `expectedRef` is required and is the BRANCH HEAD the writer read at, not the document\'s own blob sha: the gateway refuses to build on anything but the branch\'s current tip, so a stale value means the draft moved under the writer. Take it from `getDraftDocument`\'s `ref`, and read the document at the head you intend to write against — reading the document first and the head second pairs content from one commit with a precondition naming a later one, which passes the swap and silently overwrites whatever moved in between.  On a document-store draft the precondition is per file: `expectedSha` (the `sha` the writer read) replaces the document only if it still holds that version, and `createOnly` creates it only if no document is there. Either is checked in the same statement that writes, so of two writers holding the same `sha` exactly one wins and the other gets `409` `draft-document-stale`. They are mutually exclusive (`400` when both are sent). With neither, the write is last-writer-wins, as a write through the documents API has always been. `expectedRef` is refused on a document-store draft, and `expectedSha` and `createOnly` are refused on a git-backed one, rather than ignored: a caller that sends a precondition believes it holds a guarantee.  On a document-store draft the server requests the draft\'s checkpoint after the write commits, so a client does not request one itself.  **Authorization** — `can_update_document` on the draft document, **and** `can_create_package` on the draft\'s target environment, on either backing. The second is not redundant: `can_update_document` on a draft is satisfied by bare workspace membership, while a file written here reaches the environment on the draft author\'s next checkpoint, carrying the checkpointer\'s bar rather than the writer\'s. A git-backed write also commits into that environment\'s repository. The environment comes from the draft\'s own manifest and is never a request field; a draft that names none is refused, since it could not be published either.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
+     * Creates or replaces a document, whichever storage backs the draft. `PUT` rather than `POST` because the path is the identifier and the caller chooses it — there is no server-assigned id for a file, so a collection `POST` would have nothing to assign.  **The precondition is per file, on either backing.** `expectedSha` (the `sha` the writer read) replaces the document only if it still holds that version, and `createOnly` creates it only if no document is there. Of two writers holding the same `sha` exactly one wins and the other gets `409` `draft-document-stale`, except that a resent write that already landed is answered as applied (below). They are mutually exclusive (`400` when both are sent). With neither, the write is last-writer-wins, as a write through the documents API has always been.  On either backing a retry whose change is already in place (the content is current, or the file to delete is gone) is answered as applied, not as a conflict, so a lost response can be resent. A deletion of a gone file with an `expectedSha` counts as applied only when no write in the same set is still to land: a move whose old path was deleted or moved by someone else is stale (`\"\"`), not a second copy.  On a git-backed draft the check is made against the branch\'s current files, so a commit that touched only OTHER files does not fail the write: the server re-sends it once on the new tip, and answers `409` `draft-write-contended` if the tip kept moving.  `expectedRef` is deprecated and git-only: the BRANCH HEAD the writer read at, which any commit to any file makes stale (`409` `draft-file-stale-head`). It is refused together with `expectedSha` or `createOnly`, and refused on a document-store draft rather than ignored: a caller that sends a precondition believes it holds a guarantee.  On a document-store draft the server requests the draft\'s checkpoint after the write commits, so a client does not request one itself.  **Authorization** — `can_update_document` on the draft document, **and** `can_create_package` on the draft\'s target environment, on either backing. The second is not redundant: `can_update_document` on a draft is satisfied by bare workspace membership, while a file written here reaches the environment on the draft author\'s next checkpoint, carrying the checkpointer\'s bar rather than the writer\'s. A git-backed write also commits into that environment\'s repository. The environment comes from the draft\'s own manifest and is never a request field; a draft that names none is refused, since it could not be published either.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
      * @summary Write one of a draft\'s documents
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
@@ -6181,7 +6569,7 @@ class DraftsApi extends base_1.BaseAPI {
         return (0, exports.DraftsApiFp)(this.configuration).writeDraftDocumentContent(organizationName, workspaceName, draftId, documentPath, body, options).then((request) => request(this.axios, this.basePath));
     }
     /**
-     * Writes a set of documents together. On a git-backed draft they land as **one commit**, which is the reason this exists beside the per-document `PUT`: seeding a draft from a package is a single logical change, and writing its files one at a time would put N commits in the History tab for one action — and leave a reader of any intermediate commit looking at half a package.  Ordinary editing uses the per-document `PUT`. This is for the cases that are atomic by nature: the seed, and a multi-file edit that should be reviewable as one diff.  `expectedRef` applies to the whole set, and a client-minted `intentTimestamp` resent byte-identical makes a retried write a replay rather than a second commit — which matters more here than for one document, since a lost response after an N-file commit is otherwise indistinguishable from a write that never landed.  On a document-store draft each member may carry its own `expectedSha` or `createOnly` (see `writeDraftDocument`), so a move is one set: `createOnly` on the new path and a deletion with `expectedSha` on the old one. The set stays all-or-nothing: if any member\'s precondition fails, none is written and the `409` `draft-document-stale` names every conflicting path.  **Authorization**: as `writeDraftDocument`.  **Fenced by a work item.** A caller executing a work item (one claimed through the controlplane\'s private work-item API) sends its claim in `Work-Item-Claim` (`{id}@{generation}`). The claim is checked first thing in the transaction that writes the document rows, and refused with `409` `draft-write-fenced` -- writing nothing -- when it is no longer the live one: released, cancelled, or swept after its holder stopped heartbeating. On a branch-backed draft the commit is made by the gateway, so the claim is checked just before it: a cancel that lands during that one commit can let it through, and the commit\'s `Turn-Work-Item` trailer records which item wrote it. A malformed header is a `400`. Without the header the write is unfenced, as before. Only this operation honors the header.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
+     * Writes a set of documents together. On a git-backed draft they land as **one commit**, which is the reason this exists beside the per-document `PUT`: seeding a draft from a package is a single logical change, and writing its files one at a time would put N commits in the History tab for one action — and leave a reader of any intermediate commit looking at half a package.  Ordinary editing uses the per-document `PUT`. This is for the cases that are atomic by nature: the seed, and a multi-file edit that should be reviewable as one diff.  Each member may carry its own `expectedSha` or `createOnly` on either backing (see `writeDraftDocument`), so a move is one set: `createOnly` on the new path and a deletion with `expectedSha` on the old one. If any member\'s precondition fails, none is written and the `409` `draft-document-stale` names every conflicting path; a set already partly in place (a resent one) commits only what remains.  `expectedRef` is deprecated: it applies to the whole set, is git-only, and is refused together with a member\'s `expectedSha` or `createOnly`. A client-minted `intentTimestamp` resent byte-identical makes a retried write a replay rather than a second commit — which matters more here than for one document, since a lost response after an N-file commit is otherwise indistinguishable from a write that never landed.  **Authorization**: as `writeDraftDocument`.  **Fenced by a work item.** A caller executing a work item (one claimed through the controlplane\'s private work-item API) sends its claim in `Work-Item-Claim` (`{id}@{generation}`). The claim is checked first thing in the transaction that writes the document rows, and refused with `409` `draft-write-fenced` -- writing nothing -- when it is no longer the live one: released, cancelled, or swept after its holder stopped heartbeating. On a branch-backed draft the commit is made by the gateway, so the claim is checked just before it: a cancel that lands during that one commit can let it through, and the commit\'s `Turn-Work-Item` trailer records which item wrote it. A malformed header is a `400`. Without the header the write is unfenced, as before. Only this operation honors the header.  Refuses with `400` (`draft-notebook-read-only`) when a document path ends `.malloynb` and the write would change it or add a new one to a draft that already has files. A `.malloynb` notebook in a draft is read-only: convert it to a `.malloy` notebook (the same name with `.malloy`, beside it) and edit that, or delete it. Writing identical content, or seeding an empty draft, is allowed, and so is a deletion.  Refuses with `400` and a distinct code when a git-backed checkpoint\'s own content is refused: `checkpoint-over-size-cap` (the draft\'s total content is over the cap; split the change across commits; this code was `draft-file-too-large` before) or `checkpoint-content-not-base64` (a file\'s content is not valid base64).
      * @summary Write several of a draft\'s documents as one change
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} workspaceName The unique identifier of the workspace
@@ -6230,7 +6618,7 @@ exports.DraftsApi = DraftsApi;
 const EntitiesApiAxiosParamCreator = function (configuration) {
     return {
         /**
-         * Lists the field-level entities (dimensions, measures, views, joins) of one model in this version, each carrying the Malloy `code` that defines it. This is a read of the version\'s entities artifact — extracted from the raw model text at publish time by malloy-code-server — never a recompilation, so it is available the moment the version exists.  `versionId` accepts the literal `latest`, resolved to the package\'s pinned latest version. Filters: `modelPath` (required) selects one model file; `source` optionally narrows to one source\'s entities.  Entities of sources outside the package\'s declared query surface (publisher #833 — not manifest-declared, or not in the model\'s `export {}` closure) are never returned: the serving plane hides those sources, so this endpoint must not leak their definitions. A version published before entities artifacts existed returns an empty list.  **Authorization**: Requires read access to the package (`can_read_package`). Deliberately weaker than `getPackageSource`\'s `can_update_package`: per-field definitions of *queryable* sources are viewer-facing documentation (the retrieval `/get_context` API already serves the same `code` under read access), unlike a raw source dump, which stays edit-gated.
+         * Lists the field-level entities (dimensions, measures, views, joins) of one model in this version, each carrying the Malloy `code` that defines it. This is a read of the version\'s entities artifact — reported by the Publisher when the version is published — never a recompilation, so it is available the moment the version exists.  `versionId` accepts the literal `latest`, resolved to the package\'s pinned latest version. Filters: `modelPath` (required) selects one model file; `source` optionally narrows to one source\'s entities.  Entities of sources outside the package\'s declared query surface (publisher #833 — not manifest-declared, or not in the model\'s `export {}` closure) are never returned: the serving plane hides those sources, so this endpoint must not leak their definitions. A version published before entities artifacts existed returns an empty list.  **Authorization**: Requires read access to the package (`can_read_package`). Deliberately weaker than `getPackageSource`\'s `can_update_package`: per-field definitions of *queryable* sources are viewer-facing documentation (the retrieval `/get_context` API already serves the same `code` under read access), unlike a raw source dump, which stays edit-gated.
          * @summary List a version\'s field entities with their Malloy definitions
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} environmentName The unique identifier of the environment
@@ -6299,7 +6687,7 @@ const EntitiesApiFp = function (configuration) {
     const localVarAxiosParamCreator = (0, exports.EntitiesApiAxiosParamCreator)(configuration);
     return {
         /**
-         * Lists the field-level entities (dimensions, measures, views, joins) of one model in this version, each carrying the Malloy `code` that defines it. This is a read of the version\'s entities artifact — extracted from the raw model text at publish time by malloy-code-server — never a recompilation, so it is available the moment the version exists.  `versionId` accepts the literal `latest`, resolved to the package\'s pinned latest version. Filters: `modelPath` (required) selects one model file; `source` optionally narrows to one source\'s entities.  Entities of sources outside the package\'s declared query surface (publisher #833 — not manifest-declared, or not in the model\'s `export {}` closure) are never returned: the serving plane hides those sources, so this endpoint must not leak their definitions. A version published before entities artifacts existed returns an empty list.  **Authorization**: Requires read access to the package (`can_read_package`). Deliberately weaker than `getPackageSource`\'s `can_update_package`: per-field definitions of *queryable* sources are viewer-facing documentation (the retrieval `/get_context` API already serves the same `code` under read access), unlike a raw source dump, which stays edit-gated.
+         * Lists the field-level entities (dimensions, measures, views, joins) of one model in this version, each carrying the Malloy `code` that defines it. This is a read of the version\'s entities artifact — reported by the Publisher when the version is published — never a recompilation, so it is available the moment the version exists.  `versionId` accepts the literal `latest`, resolved to the package\'s pinned latest version. Filters: `modelPath` (required) selects one model file; `source` optionally narrows to one source\'s entities.  Entities of sources outside the package\'s declared query surface (publisher #833 — not manifest-declared, or not in the model\'s `export {}` closure) are never returned: the serving plane hides those sources, so this endpoint must not leak their definitions. A version published before entities artifacts existed returns an empty list.  **Authorization**: Requires read access to the package (`can_read_package`). Deliberately weaker than `getPackageSource`\'s `can_update_package`: per-field definitions of *queryable* sources are viewer-facing documentation (the retrieval `/get_context` API already serves the same `code` under read access), unlike a raw source dump, which stays edit-gated.
          * @summary List a version\'s field entities with their Malloy definitions
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} environmentName The unique identifier of the environment
@@ -6332,7 +6720,7 @@ const EntitiesApiFactory = function (configuration, basePath, axios) {
     const localVarFp = (0, exports.EntitiesApiFp)(configuration);
     return {
         /**
-         * Lists the field-level entities (dimensions, measures, views, joins) of one model in this version, each carrying the Malloy `code` that defines it. This is a read of the version\'s entities artifact — extracted from the raw model text at publish time by malloy-code-server — never a recompilation, so it is available the moment the version exists.  `versionId` accepts the literal `latest`, resolved to the package\'s pinned latest version. Filters: `modelPath` (required) selects one model file; `source` optionally narrows to one source\'s entities.  Entities of sources outside the package\'s declared query surface (publisher #833 — not manifest-declared, or not in the model\'s `export {}` closure) are never returned: the serving plane hides those sources, so this endpoint must not leak their definitions. A version published before entities artifacts existed returns an empty list.  **Authorization**: Requires read access to the package (`can_read_package`). Deliberately weaker than `getPackageSource`\'s `can_update_package`: per-field definitions of *queryable* sources are viewer-facing documentation (the retrieval `/get_context` API already serves the same `code` under read access), unlike a raw source dump, which stays edit-gated.
+         * Lists the field-level entities (dimensions, measures, views, joins) of one model in this version, each carrying the Malloy `code` that defines it. This is a read of the version\'s entities artifact — reported by the Publisher when the version is published — never a recompilation, so it is available the moment the version exists.  `versionId` accepts the literal `latest`, resolved to the package\'s pinned latest version. Filters: `modelPath` (required) selects one model file; `source` optionally narrows to one source\'s entities.  Entities of sources outside the package\'s declared query surface (publisher #833 — not manifest-declared, or not in the model\'s `export {}` closure) are never returned: the serving plane hides those sources, so this endpoint must not leak their definitions. A version published before entities artifacts existed returns an empty list.  **Authorization**: Requires read access to the package (`can_read_package`). Deliberately weaker than `getPackageSource`\'s `can_update_package`: per-field definitions of *queryable* sources are viewer-facing documentation (the retrieval `/get_context` API already serves the same `code` under read access), unlike a raw source dump, which stays edit-gated.
          * @summary List a version\'s field entities with their Malloy definitions
          * @param {string} organizationName The unique identifier of the organization
          * @param {string} environmentName The unique identifier of the environment
@@ -6359,7 +6747,7 @@ exports.EntitiesApiFactory = EntitiesApiFactory;
  */
 class EntitiesApi extends base_1.BaseAPI {
     /**
-     * Lists the field-level entities (dimensions, measures, views, joins) of one model in this version, each carrying the Malloy `code` that defines it. This is a read of the version\'s entities artifact — extracted from the raw model text at publish time by malloy-code-server — never a recompilation, so it is available the moment the version exists.  `versionId` accepts the literal `latest`, resolved to the package\'s pinned latest version. Filters: `modelPath` (required) selects one model file; `source` optionally narrows to one source\'s entities.  Entities of sources outside the package\'s declared query surface (publisher #833 — not manifest-declared, or not in the model\'s `export {}` closure) are never returned: the serving plane hides those sources, so this endpoint must not leak their definitions. A version published before entities artifacts existed returns an empty list.  **Authorization**: Requires read access to the package (`can_read_package`). Deliberately weaker than `getPackageSource`\'s `can_update_package`: per-field definitions of *queryable* sources are viewer-facing documentation (the retrieval `/get_context` API already serves the same `code` under read access), unlike a raw source dump, which stays edit-gated.
+     * Lists the field-level entities (dimensions, measures, views, joins) of one model in this version, each carrying the Malloy `code` that defines it. This is a read of the version\'s entities artifact — reported by the Publisher when the version is published — never a recompilation, so it is available the moment the version exists.  `versionId` accepts the literal `latest`, resolved to the package\'s pinned latest version. Filters: `modelPath` (required) selects one model file; `source` optionally narrows to one source\'s entities.  Entities of sources outside the package\'s declared query surface (publisher #833 — not manifest-declared, or not in the model\'s `export {}` closure) are never returned: the serving plane hides those sources, so this endpoint must not leak their definitions. A version published before entities artifacts existed returns an empty list.  **Authorization**: Requires read access to the package (`can_read_package`). Deliberately weaker than `getPackageSource`\'s `can_update_package`: per-field definitions of *queryable* sources are viewer-facing documentation (the retrieval `/get_context` API already serves the same `code` under read access), unlike a raw source dump, which stays edit-gated.
      * @summary List a version\'s field entities with their Malloy definitions
      * @param {string} organizationName The unique identifier of the organization
      * @param {string} environmentName The unique identifier of the environment