@rivus/gateway 0.16.6 → 0.17.0

package/README.md

@@ -4,3 +4,28 @@ Message Gateway and deployment control package for Rivus. It owns normalized mes
 Feishu adapters, management, project initialization, and the Gateway CLI resources.
 
 The package has no npm bin. Applications choose the public entrypoint or an explicit template resource.
+
+The root exposes `createRivusPluginCatalog`, `resolveRivusAgentDefinition`, `RIVUS_PLUGIN_API_VERSION` and
+`runRivusNodeEntrypoint`, plus nine plugin contracts. Catalog construction and resolution are implemented in Bootstrap.
+Host, Deployment, Automation, Human, Inbox, Recovery, Delegation and presentation helpers remain internal; use the
+published Bootstrap and MCP entrypoints for complete process graphs.
+
+`@rivus/gateway/bootstrap/pi-feishu` provides `createRivusDeploymentAdapters` for manifest deployments and
+`createRivusDaemonProcess` for standalone Pi/Feishu daemons. The Pi templates re-export these constructors; Gateway
+assembles canonical Runtime execution through public package APIs. Standalone HTTP status is optional through
+`RIVUS_STATUS_PORT`; Home/manifest deployments use their own status path.
+
+Gateway is the sole owner of deployment templates, the starter Plugin and runtime-management Skill. Resolve
+`@rivus/gateway/plugin/starter` and `@rivus/gateway/skills/runtime-management/SKILL.md` directly. Background-session
+MCP uses `@rivus/gateway/mcp`; old Agent bootstrap, Plugin, Skill and MCP aliases are not available.
+
+Pi deployment Bootstrap opens the Runtime JSONL Memory Repository and injects one canonical Effect Memory service.
+The former Gateway Memory service factories are removed; use Runtime's public Repository and service constructors.
+
+Gateway adapts real plugin tools to Runtime's canonical Effect Broker. Pi deployment Bootstrap and offline Recovery
+open the canonical Runtime Ledger directly, and Human approval ports compose Effect. The former Gateway Promise
+Broker and JSONL Ledger factories are removed; operation files retain their existing path and v1 format.
+
+Bootstrap composes canonical Effect Host/Endpoint/Runtime factories, control and replay directly. WebSocket, SDK,
+plugin and CLI boundaries retain their actual asynchronous calling conventions. Removing Compatibility adapters
+does not change the JSON/JSONL historical readers or the durable delivery retry budget.

package/dist/bootstrap/herdr-feishu.d.ts

@@ -0,0 +1,37 @@
+import { Effect } from "effect";
+//#region src/adapters/herdr/session/herdr-socket-client.d.ts
+interface HerdrSessionConfig {
+  readonly name: string;
+  readonly socketPath: string;
+}
+//#endregion
+//#region src/bootstrap/herdr-feishu.d.ts
+export interface HerdrFeishuBridgeOptions {
+  readonly appId: string;
+  readonly appSecret: string;
+  readonly sessions?: readonly HerdrSessionConfig[];
+  readonly discoverSessionsIn?: string;
+  readonly allowedActors: readonly string[];
+  readonly allowedChats: readonly string[];
+  readonly menuChats?: Readonly<Record<string, string>>;
+  readonly stateDirectory: string;
+  readonly writable?: boolean;
+  readonly fontFiles?: readonly string[];
+  readonly onObservation?: (event: {
+    readonly type: string;
+    readonly messageId?: string;
+  }) => void;
+}
+export declare function checkHerdrFeishuBridge(options: HerdrFeishuBridgeOptions): Promise<{
+  panels: number;
+  sessionsWithPanels: number;
+  unavailableSessions: string[];
+  writable: boolean;
+  feishuVerified: false;
+}>;
+export declare function startHerdrFeishuBridge(options: HerdrFeishuBridgeOptions): Promise<{
+  stop: () => Promise<void>;
+}>;
+//#endregion
+export type { HerdrSessionConfig };
+export {};