@seliseblocks/client 0.1.3 → 0.1.5

package/README.md

@@ -1,216 +1,222 @@
-# Blocks Client
-
-Framework-neutral TypeScript SDK for SELISE Blocks frontend and app-runtime code.
-
-`@seliseblocks/client` gives consumer apps a small, typed wrapper around the Blocks APIs they normally call at runtime: Auth/IAM, Data, Localization, and shared HTTP configuration. Detailed `what / why / how` descriptions are kept on the SDK functions themselves so editors and generated typings show the guidance where developers use the API.
-
-Admin/control-plane work belongs in `@seliseblocks/cli-os`: project setup, schema/rules deploy, release deploy, and AI/admin terminal workflows.
-
-For AI agents and automation, see [AI_USAGE_GUIDE.md](AI_USAGE_GUIDE.md).
-
-## Install
-
-```bash
-npm install @seliseblocks/client
-```
-
-Requires Node.js 20+ or a browser/runtime with `fetch`.
-
-## Create A Client
-
-```ts
-import { createBlocksClient } from "@seliseblocks/client";
-
-const blocks = createBlocksClient({
-  apiUrl: "https://api.seliseblocks.com",
-  xBlocksKey: "<blocks-key>",
-  accessToken: () => currentUserSession?.accessToken,
-  oidc: {
-    url: "https://iam.seliseblocks.com",
-    clientId: "<public-browser-client-id>",
-    redirectUri: configuredRedirectUri ?? `${window.location.origin}/login/callback`
-  }
-});
-```
-
-`xBlocksKey` is always sent as the `x-blocks-key` header. Do not send `ProjectKey` or `projectKey` in request query/body payloads.
-
-The SDK does not store tokens. Your app owns login state, refresh scheduling, storage, and logout cleanup.
-
-Use a configured OIDC redirect URI when your app has one. The current-origin `/login/callback` URL is only a browser fallback.
-
-## Auth
-
-Auth has two login flows.
-
-OIDC/hosted IAM login uses `auth.idp`. The SDK relies on Blocks IAM `IdpController`, sends the configured public `clientId`, and does not manually build `oidc/authorize` URLs. Refresh OIDC sessions with `auth.oidc.refreshToken()`, which calls `/iam/v4/oidc/token` and sends `client_id`.
-
-```ts
-await blocks.auth.idp.redirectToProvider();
-
-const result = await blocks.auth.idp.callback(window.location.href);
-
-const refreshed = await blocks.auth.oidc.refreshToken({
-  refreshToken: result.refresh_token,
-  clientId: "<public-browser-client-id>"
-});
-```
-
-Embedded/app-owned login UI uses AuthController methods directly on `auth`: `auth.login()`, `auth.socialInitiate(clientId, redirectUri)` (two positional strings, not an object), `auth.socialCallback(request)`, and `auth.refresh()`.
-
-```ts
-const login = await blocks.auth.login({
-  username: "user@example.com",
-  password: "password"
-});
-
-const refreshed = await blocks.auth.refresh({
-  refreshToken: login.refresh_token
-});
-```
-
-Other auth APIs, such as user info, organization switch, logout, signup, recovery, activation, auth config, user codes, client credentials, and identity providers, can be used by either flow when the app has the required token/permission.
-
-`auth.oidc.clientCredentials()` is for trusted non-browser runtimes only because it requires a client secret.
-
-`auth.accessToken()` resolves the caller-owned bearer token configured on `createBlocksClient` (string or callback). `auth.isAuthenticated()` checks the current session against IAM through `GET /iam/v4/auth/me` and returns a boolean based on the raw response status - use it instead of `userInfo()` when you need a true/false signal, since IAM's hosted IdP flow may set the session as a cookie with no local `accessToken` to inspect.
-
-```ts
-const config = await blocks.mfa.config();
-await blocks.mfa.totp.setup();
-await blocks.mfa.totp.verifySetup({ code: "123456" });
-await blocks.mfa.setMethod({ mfaType: 1 });
-const backupCodes = await blocks.mfa.backupCodes.generate();
-```
-
-## Mail And Notifications
-
-```ts
-await blocks.mail.send({
-  to: ["user@example.com"],
-  purpose: "welcome",
-  language: "en",
-  subjectDataContext: { firstName: "Ada" }
-});
-
-await blocks.mail.sendToAny({
-  to: ["qa@example.com"],
-  purpose: "welcome",
-  language: "en",
-  isTestMail: true
-});
-
-await blocks.notifier.notify({
-  userIds: ["user-id"],
-  denormalizedPayload: JSON.stringify({ orderId: "123" }),
-  saveDenormalizedPayloadAsAnObject: true
-});
-
-const inbox = await blocks.notifier.getNotifications({ isUnreadOnly: true, page: 1, pageSize: 20 });
-await blocks.notifier.markNotificationAsRead({ id: inbox.notifications[0].id });
-await blocks.notifier.markAllNotificationAsRead();
-```
-
-`mail.send`/`mail.sendToAny` call `/logic/v4/Mail/Send`/`SendToAny`. `notifier.*` calls `/logic/v4/Notifier/*`
-for sending/reading notifications; tenant notification *channel configuration* (`/os/v4/Notification/*`)
-is an admin concern handled by `@seliseblocks/cli-os`'s `notification *` commands, not this SDK.
-
-## Common Runtime Calls
-
-```ts
-const me = await blocks.iam.me();
-const orgs = await blocks.iam.organizations.my();
-const features = await blocks.iam.resources.features();
-```
-
-```ts
-const schemas = await blocks.data.schemas.list();
-const schemaInfo = await blocks.data.schemas.infoByName("Student");
-const schemaRules = await blocks.data.validations.bySchemaId("schema-id");
-
-const students = blocks.data.collection("Students");
-const rows = await students.list({ pageNo: 1, pageSize: 20 });
-await students.create({ firstName: "Test" });
-
-const graph = await blocks.data.graphql({
-  query: "{ students { items { itemId firstName } } }"
-});
-```
-
-```ts
-const upload = await blocks.data.files.presignedUploadUrl({
-  name: "avatar.png",
-  configurationName: "default",
-  parentDirectoryId: "root",
-  accessModifier: "Private"
-});
-
-await blocks.data.files.uploadToUrl({
-  url: upload.uploadUrl,
-  body: file,
-  contentType: file.type
-});
-
-const items = await blocks.data.dms.list({
-  configurationName: "default",
-  parentId: "root",
-  skip: 0,
-  take: 20
-});
-```
-
-```ts
-await blocks.localization.load("en-US", ["common", "dashboard"]);
-const label = blocks.localization.t("dashboard.title", "Dashboard");
-
-const tenantLanguages = await blocks.localization.languagesForCurrentTenant();
-const selectedKeys = await blocks.localization.keysByNames({
-  keyNames: ["dashboard.title"]
-});
-```
-
-## API Surface
-
-- `blocks.auth`: AuthController login, social login, refresh, org switch, logout, signup, recovery, activation, auth config, user codes, client credentials, identity providers.
-- `blocks.auth.idp`: hosted IdP initiate, browser redirect, callback, UI config.
-- `blocks.auth.oidc`: refresh-token and client-credentials token endpoint helpers.
-- `blocks.iam`: current user, users, roles, permissions, resources, organizations, signup settings (`blocks.iam.signupSettings`).
-- `blocks.data`: schema reads, validation reads, GraphQL gateway execution, file/storage helpers, DMS file/folder helpers, runtime collection CRUD.
-- `blocks.localization`: tenant language/module discovery, UILM dictionary loading, selected key lookup, simple `t()` lookup.
-- `blocks.mfa`: tenant MFA policy read/save, TOTP enrollment, OTP generate/resend/verify, method switch, disable, and backup codes.
-- `blocks.mail`: `send`/`sendToAny` transactional email through the tenant's configured mail provider.
-- `blocks.notifier`: `notify`, `getNotifications`, `getUnreadNotificationsBySubscriptionFilter`, `markNotificationAsRead`, `markAllNotificationAsRead`.
-
-Professional class names are exported for advanced typing and adapters: `BlocksAuthenticationClient`, `BlocksIAMClient`, `BlocksDataClient`, `BlocksLocalizationClient`, `BlocksMfaClient`, `BlocksMailClient`, and `BlocksNotifierClient`. `BlocksApiError` is exported for typed error handling - every non-2xx response from `http.request`/`http.external` throws it, exposing `status`, `statusText`, and the parsed `body`:
-
-```ts
-try {
-  await blocks.iam.me();
-} catch (error) {
-  if (error instanceof BlocksApiError) {
-    console.error(error.status, error.body);
-  }
-}
-```
-
-## Boundaries
-
-This package must not contain:
-
-- CLI client secrets
-- impersonation APIs
-- project create/list/use
-- schema/rules deploy
-- release deploy
-- token/session/PKCE storage
-- Node filesystem or OS credential storage
-- framework UI components
-- Localization authoring/admin endpoints
-- Data schema/rules mutation endpoints
-
-## Package Checks
-
-```bash
-npm test
-npm pack --dry-run
-```
+# Blocks Client
+
+Framework-neutral TypeScript SDK for SELISE Blocks frontend and app-runtime code.
+
+`@seliseblocks/client` gives consumer apps a small, typed wrapper around the Blocks APIs they normally call at runtime: Auth/IAM, Data, Localization, and shared HTTP configuration. Detailed `what / why / how` descriptions are kept on the SDK functions themselves so editors and generated typings show the guidance where developers use the API.
+
+Admin/control-plane work belongs in `@seliseblocks/cli-os`: project setup, schema/rules deploy, release deploy, and AI/admin terminal workflows.
+
+For AI agents and automation, see [AI_USAGE_GUIDE.md](AI_USAGE_GUIDE.md).
+
+## Install
+
+```bash
+npm install @seliseblocks/client@latest
+```
+
+Requires Node.js 20+ or a browser/runtime with `fetch`.
+
+## Create A Client
+
+```ts
+import { createBlocksClient } from "@seliseblocks/client";
+
+const blocks = createBlocksClient({
+  apiUrl: "https://api.seliseblocks.com",
+  xBlocksKey: "<blocks-key>",
+  accessToken: () => currentUserSession?.accessToken,
+  oidc: {
+    url: "https://iam.seliseblocks.com",
+    clientId: "<public-browser-client-id>",
+    redirectUri: configuredRedirectUri ?? `${window.location.origin}/login/callback`
+  }
+});
+```
+
+`xBlocksKey` is always sent as the `x-blocks-key` header. Do not send `ProjectKey` or `projectKey` in request query/body payloads.
+
+The SDK does not store tokens. Your app owns login state, refresh scheduling, storage, and logout cleanup.
+
+Use a configured OIDC redirect URI when your app has one. The current-origin `/login/callback` URL is only a browser fallback.
+
+## Auth
+
+Auth has two login flows.
+
+OIDC/hosted IAM login uses `auth.idp`. The SDK relies on Blocks IAM `IdpController`, sends the configured public `clientId`, and does not manually build `oidc/authorize` URLs. Refresh OIDC sessions with `auth.oidc.refreshToken()`, which calls `/iam/v4/oidc/token` and sends `client_id`.
+
+```ts
+await blocks.auth.idp.redirectToProvider();
+
+const result = await blocks.auth.idp.callback(window.location.href);
+
+const refreshed = await blocks.auth.oidc.refreshToken({
+  refreshToken: result.refresh_token,
+  clientId: "<public-browser-client-id>"
+});
+```
+
+Embedded/app-owned login UI uses AuthController methods directly on `auth`: `auth.login()`, `auth.socialInitiate(clientId, redirectUri)` (two positional strings, not an object), `auth.socialCallback(request)`, and `auth.refresh()`.
+
+```ts
+const login = await blocks.auth.login({
+  username: "user@example.com",
+  password: "password"
+});
+
+const refreshed = await blocks.auth.refresh({
+  refreshToken: login.refresh_token
+});
+```
+
+Other auth APIs, such as user info, organization switch, logout, signup, recovery, activation, auth config, user codes, client credentials, and identity providers, can be used by either flow when the app has the required token/permission.
+
+`auth.oidc.clientCredentials()` is for trusted non-browser runtimes only because it requires a client secret.
+
+`auth.accessToken()` resolves the caller-owned bearer token configured on `createBlocksClient` (string or callback). `auth.isAuthenticated()` checks the current session against IAM through `GET /iam/v4/auth/me` and returns a boolean based on the raw response status - use it instead of `userInfo()` when you need a true/false signal, since IAM's hosted IdP flow may set the session as a cookie with no local `accessToken` to inspect.
+
+```ts
+const config = await blocks.mfa.config();
+await blocks.mfa.totp.setup();
+await blocks.mfa.totp.verifySetup({ code: "123456" });
+await blocks.mfa.setMethod({ mfaType: 1 });
+const backupCodes = await blocks.mfa.backupCodes.generate();
+```
+
+## Mail And Notifications
+
+```ts
+await blocks.mail.send({
+  to: ["user@example.com"],
+  purpose: "welcome",
+  language: "en",
+  subjectDataContext: { firstName: "Ada" }
+});
+
+await blocks.mail.sendToAny({
+  to: ["qa@example.com"],
+  purpose: "welcome",
+  language: "en",
+  isTestMail: true
+});
+
+await blocks.notifier.notify({
+  userIds: ["user-id"],
+  denormalizedPayload: JSON.stringify({ orderId: "123" }),
+  saveDenormalizedPayloadAsAnObject: true
+});
+
+const inbox = await blocks.notifier.getNotifications({ isUnreadOnly: true, page: 1, pageSize: 20 });
+await blocks.notifier.markNotificationAsRead({ id: inbox.notifications[0].id });
+await blocks.notifier.markAllNotificationAsRead();
+```
+
+`mail.send`/`mail.sendToAny` call `/logic/v4/Mail/Send`/`SendToAny`. `notifier.*` calls `/logic/v4/Notifier/*`
+for sending/reading notifications; tenant notification *channel configuration* (`/os/v4/Notification/*`)
+is an admin concern handled by `@seliseblocks/cli-os`'s `notification *` commands, not this SDK.
+
+## Common Runtime Calls
+
+```ts
+const me = await blocks.iam.me();
+const orgs = await blocks.iam.organizations.my();
+const features = await blocks.iam.resources.features();
+```
+
+`iam.organizations.my()` returns the IAM envelope with `organizations`, not `data`.
+
+```ts
+const schemas = await blocks.data.schemas.list();
+const schemaInfo = await blocks.data.schemas.infoByName("Student");
+const schemaRules = await blocks.data.validations.bySchemaId("schema-id");
+
+const students = blocks.data.collection("Students");
+const rows = await students.list({ pageNo: 1, pageSize: 20 });
+await students.create({ firstName: "Test" });
+
+const graph = await blocks.data.graphql({
+  query: "{ students { items { itemId firstName } } }"
+});
+```
+
+```ts
+const upload = await blocks.data.files.presignedUploadUrl({
+  name: "avatar.png",
+  configurationName: "default",
+  parentDirectoryId: "root",
+  accessModifier: "Private"
+});
+
+await blocks.data.files.uploadToUrl({
+  url: upload.uploadUrl,
+  body: file,
+  contentType: file.type
+});
+
+const items = await blocks.data.objects.list({
+  parentDirectoryId: "root",
+  limit: 20
+});
+
+const directory = await blocks.data.directories.create({
+  name: "Contracts",
+  parentDirectoryId: "root",
+  allowedFileExtensions: ["pdf", "docx"]
+});
+```
+
+```ts
+await blocks.localization.load("en-US", ["common", "dashboard"]);
+const label = blocks.localization.t("dashboard.title", "Dashboard");
+
+const tenantLanguages = await blocks.localization.languagesForCurrentTenant();
+const selectedKeys = await blocks.localization.keysByNames({
+  keyNames: ["dashboard.title"]
+});
+```
+
+## API Surface
+
+- `blocks.auth`: AuthController login, social login, refresh, org switch, logout, signup, recovery, activation, auth config, user codes, client credentials, identity providers.
+- `blocks.auth.idp`: hosted IdP initiate, browser redirect, callback, UI config.
+- `blocks.auth.oidc`: refresh-token and client-credentials token endpoint helpers.
+- `blocks.iam`: current user, users, roles, permissions, resources, organizations, signup settings (`blocks.iam.signupSettings`).
+- `blocks.data`: schema reads, validation reads, GraphQL gateway execution, file/directory/object-tree storage helpers, and runtime collection CRUD.
+- `blocks.localization`: tenant language/module discovery, UILM dictionary loading, selected key lookup, simple `t()` lookup.
+- `blocks.mfa`: tenant MFA policy read/save, TOTP enrollment, OTP generate/resend/verify, method switch, disable, and backup codes.
+- `blocks.mail`: `send`/`sendToAny` transactional email through the tenant's configured mail provider.
+- `blocks.notifier`: `notify`, `getNotifications`, `getUnreadNotificationsBySubscriptionFilter`, `markNotificationAsRead`, `markAllNotificationAsRead`.
+
+Professional class names are exported for advanced typing and adapters: `BlocksAuthenticationClient`, `BlocksIAMClient`, `BlocksDataClient`, `BlocksLocalizationClient`, `BlocksMfaClient`, `BlocksMailClient`, and `BlocksNotifierClient`. `BlocksApiError` is exported for typed error handling - every non-2xx response from `http.request`/`http.external` throws it, exposing `status`, `statusText`, and the parsed `body`:
+
+```ts
+try {
+  await blocks.iam.me();
+} catch (error) {
+  if (error instanceof BlocksApiError) {
+    console.error(error.status, error.body);
+  }
+}
+```
+
+## Boundaries
+
+This package must not contain:
+
+- CLI client secrets
+- impersonation APIs
+- project create/list/use
+- schema/rules deploy
+- release deploy
+- token/session/PKCE storage
+- Node filesystem or OS credential storage
+- framework UI components
+- Localization authoring/admin endpoints
+- Data schema/rules mutation endpoints
+
+## Package Checks
+
+```bash
+npm test
+npm pack --dry-run
+```

package/dist/data/data-client.d.ts

@@ -1,5 +1,5 @@
 import { BlocksHttpClient } from "../http/http-client.js";
-import { BlocksDataCollection, BlocksDataCollectionOptions, BlocksDmsCreateFolderRequest, BlocksDmsListRequest, BlocksDmsUploadRequest, BlocksFileDeleteRequest, BlocksFileGetOptions, BlocksFileInfoListRequest, BlocksDataSchema, BlocksFileListRequest, BlocksFileUpdateAdditionalInfoRequest, BlocksFileUploadRequest, BlocksFolderDeleteRequest, BlocksGraphqlRequest, BlocksLocalStorageUploadRequest, BlocksPagedResult, BlocksRegexGenerateRequest, BlocksSchemaFieldValidationOptions, BlocksSchemaListOptions, BlocksSchemaValidationListOptions, BlocksUploadToUrlRequest } from "./types.js";
+import { BlocksDataCollection, BlocksDataCollectionOptions, BlocksDirectoryCreateRequest, BlocksDirectoryDeleteRequest, BlocksDirectoryMoveRequest, BlocksDirectoryUpdateRequest, BlocksFileCopyRequest, BlocksFileCreateVersionRequest, BlocksFileDeleteRequest, BlocksFileGetOptions, BlocksFileInfoListRequest, BlocksFileMoveRequest, BlocksFileRenameRequest, BlocksFileVersionsRequest, BlocksDataSchema, BlocksFileListRequest, BlocksFileUpdateAdditionalInfoRequest, BlocksFileUploadRequest, BlocksGraphqlRequest, BlocksLocalStorageUploadRequest, BlocksPagedResult, BlocksRegexGenerateRequest, BlocksSchemaFieldValidationOptions, BlocksSchemaListOptions, BlocksSchemaValidationListOptions, BlocksStorageAccessPolicyRequest, BlocksStorageObjectListRequest, BlocksStorageObjectPageRequest, BlocksStorageObjectSearchRequest, BlocksStorageObjectsResponse, BlocksStorageResourceRequest, BlocksStorageRevokeAccessRequest, BlocksStorageShareRequest, BlocksStorageToggleInheritanceRequest, BlocksUploadToUrlRequest } from "./types.js";
 export declare class BlocksDataClient {
     private readonly http;
     constructor(http: BlocksHttpClient);
@@ -43,27 +43,27 @@ export declare class BlocksDataClient {
     };
     files: {
         /**
-         * What: reads one file record through `GET /data/v4/Files/GetFile`.
+         * What: reads one file record through the current file download operation.
          * Why: frontend views need file metadata or a downloadable reference by file id.
          * How: pass `fileId` and optional Data file configuration/version fields.
          */
         get: (fileId: string, options?: BlocksFileGetOptions) => Promise<unknown>;
         /**
-         * What: batch-reads files through `POST /data/v4/Files/GetFiles`.
+         * What: batch-reads file metadata and download URLs.
          * Why: pages with many attachments should avoid one request per file.
          * How: pass the file-list payload exactly as Data expects; the SDK does not inject project fields.
          */
         getMany: (request: BlocksFileListRequest) => Promise<unknown>;
         /**
-         * What: lists file records and metadata through `POST /data/v4/Files/GetFilesInfo`.
+         * What: lists file records and metadata.
          * Why: storage browsers and attachment managers need paged file metadata before downloading content.
          * How: pass paging, sort, and filter fields; the SDK sends your request without any `projectKey`.
          */
         info: (request: BlocksFileInfoListRequest) => Promise<unknown>;
         /**
-         * What: requests an upload URL through `POST /data/v4/Files/GetPreSignedUrlForUpload`.
+         * What: creates file/version metadata and requests a pre-signed upload URL.
          * Why: browser apps should upload binary content through the URL issued by Blocks Data.
-         * How: pass file metadata such as `name`, `contentType`, `configurationName`, and optional DMS fields.
+         * How: pass file metadata plus a parent directory id or module default.
          */
         presignedUploadUrl: (request: BlocksFileUploadRequest) => Promise<unknown>;
         /**
@@ -73,55 +73,50 @@ export declare class BlocksDataClient {
          */
         uploadToUrl: (request: BlocksUploadToUrlRequest) => Promise<unknown>;
         /**
-         * What: uploads a file through `POST /data/v4/Files/UploadFileToLocalStorage`.
+         * What: creates a file/version and uploads its bytes to local storage.
          * Why: local-storage deployments need multipart upload through Blocks Data instead of a pre-signed cloud URL.
          * How: pass a `Blob`/`File` and metadata; the SDK builds `FormData` and does not add `projectKey`.
          */
         uploadToLocalStorage: (request: BlocksLocalStorageUploadRequest) => Promise<unknown>;
         /**
-         * What: deletes a file through `POST /data/v4/Files/DeleteFile`.
+         * What: moves a file to trash or permanently deletes it.
          * Why: storage UIs need to remove files when permissions and Data rules allow it.
-         * How: pass `fileId` and optional `configurationName`; the SDK sends no project key.
+         * How: pass `fileId` and an explicit `permanent` choice; false moves to trash.
          */
         delete: (request: BlocksFileDeleteRequest) => Promise<unknown>;
         /**
-         * What: updates file additional properties through `POST /data/v4/Files/UpdateFileAdditionalInfo`.
+         * What: updates file additional properties.
          * Why: apps often need to attach searchable metadata such as agent status or business references to a file.
          * How: pass `itemId` and `additionalProperties`; the SDK forwards the request as-is except for not adding project fields.
          */
         updateAdditionalInfo: (request: BlocksFileUpdateAdditionalInfoRequest) => Promise<unknown>;
-        /**
-         * What: reads DMS file/folder entries through `POST /data/v4/Files/GetDmsFileAndFolder`.
-         * Why: document-management views need combined folder and file listings.
-         * How: pass Data's DMS listing payload exactly as your app builds it.
-         */
-        listFolder: (request: BlocksFileListRequest) => Promise<unknown>;
+        versions: (request: BlocksFileVersionsRequest) => Promise<unknown>;
+        createVersion: (request: BlocksFileCreateVersionRequest) => Promise<unknown>;
+        copy: (request: BlocksFileCopyRequest) => Promise<unknown>;
+        move: (request: BlocksFileMoveRequest) => Promise<unknown>;
+        rename: (request: BlocksFileRenameRequest) => Promise<unknown>;
     };
-    dms: {
-        /**
-         * What: lists DMS files and folders through `POST /data/v4/Files/GetDmsFileAndFolder`.
-         * Why: document-management screens need folder contents, search, skip/take paging, and file entries together.
-         * How: pass DMS listing fields such as `parentId`, `configurationName`, `searchKey`, `skip`, and `take`.
-         */
-        list: (request: BlocksDmsListRequest) => Promise<unknown>;
-        /**
-         * What: registers uploaded files in DMS through `POST /data/v4/Files/UploadFile`.
-         * Why: after binary upload, DMS needs artifact metadata so files appear in document folders.
-         * How: pass the `upload` array with file storage ids and metadata returned from the upload flow.
-         */
-        uploadFiles: (request: BlocksDmsUploadRequest) => Promise<unknown>;
-        /**
-         * What: creates a DMS folder through `POST /data/v4/Files/CreateFolder`.
-         * Why: document-management UIs need to create folder hierarchy for uploaded files.
-         * How: pass folder metadata such as `artifactName`, `parentId`, and optional `configurationName`.
-         */
-        createFolder: (request: BlocksDmsCreateFolderRequest) => Promise<unknown>;
-        /**
-         * What: deletes a DMS folder through `POST /data/v4/Files/DeleteFolder`.
-         * Why: document-management UIs need to remove empty or allowed folders.
-         * How: pass `folderId` and optional `configurationName`; the SDK sends no project key.
-         */
-        deleteFolder: (request: BlocksFolderDeleteRequest) => Promise<unknown>;
+    directories: {
+        create: (request: BlocksDirectoryCreateRequest) => Promise<unknown>;
+        get: (directoryId: string) => Promise<unknown>;
+        update: (request: BlocksDirectoryUpdateRequest) => Promise<unknown>;
+        delete: (request: BlocksDirectoryDeleteRequest) => Promise<unknown>;
+        move: (request: BlocksDirectoryMoveRequest) => Promise<unknown>;
+    };
+    objects: {
+        list: (request?: BlocksStorageObjectListRequest) => Promise<BlocksStorageObjectsResponse>;
+        search: (request: BlocksStorageObjectSearchRequest) => Promise<BlocksStorageObjectsResponse>;
+        trash: (request?: BlocksStorageObjectPageRequest) => Promise<BlocksStorageObjectsResponse>;
+        shared: (request?: BlocksStorageObjectPageRequest) => Promise<BlocksStorageObjectsResponse>;
+        restore: (request: BlocksStorageResourceRequest) => Promise<unknown>;
+        deleteFromTrash: (request: BlocksStorageResourceRequest) => Promise<unknown>;
+        accessPolicies: (resourceId: string) => Promise<unknown>;
+        grantAccess: (request: BlocksStorageAccessPolicyRequest) => Promise<unknown>;
+        updateAccess: (request: BlocksStorageAccessPolicyRequest) => Promise<unknown>;
+        revokeAccess: (request: BlocksStorageRevokeAccessRequest) => Promise<unknown>;
+        resolveAccess: (resourceId: string) => Promise<unknown>;
+        toggleInheritance: (request: BlocksStorageToggleInheritanceRequest) => Promise<unknown>;
+        share: (request: BlocksStorageShareRequest) => Promise<unknown>;
     };
     validations: {
         /**