@helyx/bot 0.1.2 → 0.2.0

package/CHANGELOG.md

@@ -1,5 +1,28 @@
 # Changelog
 
+## 0.2.0
+
+### Minor Changes
+
+- 7b25ea0: Add the opt-in Helyx Cloud Connect configuration, local persistence, connector runtime, support-redaction contract and generated self-host environment guidance. Cloud Connect remains disabled until a deployment owner explicitly configures and enrols it.
+
+### Patch Changes
+
+- Updated dependencies [7b25ea0]
+  - @helyx/config@0.2.0
+  - @helyx/database@0.2.0
+  - @helyx/module-manifest@0.2.0
+  - @helyx/platform@0.1.3
+  - @helyx/core@0.1.3
+  - @helyx/sdk@0.2.3
+  - @helyx/framework@0.1.3
+
+## 0.1.3 - 2026-07-23
+
+- Acknowledge slow interactions safely, edit deferred responses, support
+  module-owned public message updates and log bounded interaction identifiers
+  when handling fails.
+
 ## 0.1.2 - 2026-07-23
 
 - Identify the included Helyx Source Available Licence as `HSAL 1.0` and align public core dependencies.

package/README.md

@@ -16,4 +16,6 @@ Gateway intents are derived from installed event contributions. The bot always r
 
 When `HELYX_BOT_CONTROL_SECRET` is configured, the bot also starts a private authenticated HTTP control server on `HELYX_BOT_CONTROL_PORT`. The dashboard API uses this service to obtain real Discord roles and channels and to apply validated module, configuration and permission changes. Only `/health` is unauthenticated; all `/v1` routes require the shared bearer secret. Keep this endpoint on a private service network and do not assign it a public domain.
 
+Optional Helyx Cloud Connect is a separate outbound management path for self-hosted deployments. It is disabled unless `HELYX_CLOUD_CONNECT_ENABLED=true` and requires a separate local `HELYX_DATA_ENCRYPTION_KEY`. The owner-only `/helyx-cloud` command supports connection-code enrolment, status, credential rotation, disconnection and bounded support consent. The bot never sends its Discord token, database URL or connector private key to Helyx Cloud, and local Discord operation continues when Cloud is unavailable.
+
 For packaged operation use `helyx start`. `helyx migrate` applies core database migrations without Discord, and read-only `helyx doctor` verifies environment, PostgreSQL migration history, and configured package metadata.

package/dist/cloud-connector.d.ts

@@ -0,0 +1,43 @@
+import type { BotEnvironment } from "@helyx/config";
+import { type CloudConnectorConsentRecord, type DatabasePool } from "@helyx/database";
+import type { Client } from "discord.js";
+import type { Logger } from "pino";
+import type { ConfiguredModulePackage } from "./modules.js";
+import type { BotControlHandler } from "./control-server.js";
+type ConnectorState = "disabled" | "unpaired" | "connecting" | "online" | "offline" | "revoked" | "stopped";
+export interface CloudConnectorStatus {
+    state: ConnectorState;
+    installationId?: string;
+    lastConnectedAt?: Date;
+    lastErrorCode?: string;
+}
+export declare class CloudConnectorController {
+    #private;
+    private readonly input;
+    constructor(input: {
+        environment: BotEnvironment;
+        database: DatabasePool;
+        client: Client;
+        modules: readonly ConfiguredModulePackage[];
+        coreVersion: string;
+        logger: Logger;
+    });
+    setControlHandler(handler: BotControlHandler): void;
+    start(): Promise<void>;
+    status(): CloudConnectorStatus;
+    getSupportConsent(): Promise<CloudConnectorConsentRecord>;
+    updateSupportConsent(input: {
+        supportInspectionEnabled: boolean;
+        supportDataClasses: string[];
+        diagnosticsEnabled: boolean;
+    }): Promise<CloudConnectorConsentRecord>;
+    enrol(rawToken: string, source: "startup" | "discord" | "file"): Promise<CloudConnectorStatus>;
+    disconnect(): Promise<void>;
+    rotate(): Promise<CloudConnectorStatus>;
+    stop(): Promise<void>;
+}
+export declare class CloudConnectorUserError extends Error {
+    constructor(message: string);
+}
+export {};
+//# sourceMappingURL=cloud-connector.d.ts.map