fix: load telegram command config from contract surfaces

extensions/telegram/contract-surfaces.ts

@@ -3,6 +3,12 @@ export {
   collectRuntimeConfigAssignments,
   secretTargetRegistryEntries,
 } from "./src/secret-contract.js";
+export {
+  TELEGRAM_COMMAND_NAME_PATTERN,
+  normalizeTelegramCommandDescription,
+  normalizeTelegramCommandName,
+  resolveTelegramCustomCommands,
+} from "./src/command-config.js";
 export { singleAccountKeysToMove } from "./src/setup-contract.js";
 
 export function hasConfiguredState(params: { env?: NodeJS.ProcessEnv }): boolean {

src/config/telegram-command-config.ts

@@ -29,7 +29,7 @@ type TelegramCommandConfigContract = {
 function loadTelegramCommandConfigContract(): TelegramCommandConfigContract {
   const contract = getBundledChannelContractSurfaceModule<TelegramCommandConfigContract>({
     pluginId: "telegram",
-    preferredBasename: "contract-api.ts",
+    preferredBasename: "contract-surfaces.ts",
   });
   if (!contract) {
     throw new Error("telegram command config contract surface is unavailable");