Remove restart infrastructure, generalize WASM channel setup

[henrypark133]

Summary

• Remove the gateway restart mechanism — hot-activation works, restart won't fix activation failures. restartGateway() was already dead code (defined but never called).
• Generalize Telegram-specific hardcoded checks so all WASM channels (Slack, Discord, WhatsApp) get equal treatment: pairing status, 3-step stepper, owner_id injection.
• Remove ~700 lines of dead setup_telegram() code — Telegram's capabilities.json declares required_secrets, so the generic setup_wasm_channel() path handles it.

Test plan

• cargo clippy --all --benches --tests --examples --all-features — zero warnings
• cargo test — all pass
• cargo fmt --check — clean
• grep -rn 'channel_name == "telegram"\|ext\.name == "telegram"\|isTelegram\|telegram_owner_id' src/ — zero hits
• Manual: install Telegram channel via web UI, verify 3-step stepper, pairing flow works
• Manual: verify TELEGRAM_OWNER_ID env var still works (backwards compat)

🤖 Generated with Claude Code

[gemini-code-assist]

Summary of Changes

Hello, I'm Gemini Code Assist¹! I'm currently reviewing this pull request and will post my feedback shortly. In the meantime, here's a summary to help you and other reviewers quickly get up to speed!

This pull request significantly refactors the channel management system by eliminating the defunct gateway restart functionality and generalizing the setup process for WASM channels. The changes streamline the codebase, remove dead code, and ensure that all WASM-based channels benefit from a consistent and robust activation and configuration flow, moving away from Telegram-specific special casing.

Highlights

• Removed Gateway Restart Infrastructure: The unused gateway restart mechanism, including its API route, state flags, and associated UI elements, has been completely removed, as hot-activation is the preferred and functional method.
• Generalized WASM Channel Setup: Telegram-specific hardcoded checks and setup logic for pairing status, the 3-step stepper, and owner ID injection have been generalized to apply to all WASM channels (e.g., Slack, Discord, WhatsApp), promoting a unified approach.
• Refactored Telegram Setup Code: Approximately 700 lines of Telegram-specific setup code have been removed, as the generic setup_wasm_channel() path now handles its configuration requirements, leveraging capabilities.json for required_secrets.

Changelog

• src/channels/web/handlers/extensions.rs
  • Removed Telegram-specific condition for checking active extension status, generalizing it for all active extensions.
• src/channels/web/mod.rs
  • Removed the restart_requested field from the GatewayChannel struct.
• src/channels/web/server.rs
  • Removed the restart_requested field from GatewayState struct.
  • Removed the /api/gateway/restart API route and its associated handler.
  • Generalized the logic for determining an active channel's status, removing Telegram-specific checks.
  • Removed the needs_restart flag from the extensions_setup_submit_handler response.
• src/channels/web/static/app.js
  • Removed the 'coming soon' note previously displayed for non-Telegram WASM channels.
  • Removed client-side logic related to gateway restart, including restartGateway() and showRestartOverlay() functions.
  • Updated submitConfigureModal to remove needs_restart handling.
  • Generalized the WASM channel stepper to consistently use a 3-step process for all channels, removing Telegram-specific conditions.
• src/channels/web/static/style.css
  • Removed CSS styles associated with the gateway restart overlay.
• src/channels/web/types.rs
  • Removed the needs_restart field from the ActionResponse struct.
• src/channels/web/ws.rs
  • Removed the restart_requested field from GatewayState initialization in test utilities.
• src/config/channels.rs
  • Replaced the telegram_owner_id field with a generic wasm_channel_owner_ids HashMap to store owner IDs for multiple WASM channels.
  • Updated the from_env implementation to populate wasm_channel_owner_ids, maintaining backward compatibility for the TELEGRAM_OWNER_ID environment variable.
• src/extensions/manager.rs
  • Replaced telegram_owner_id with wasm_channel_owner_ids in ChannelRuntimeState and its initialization.
  • Updated the owner ID injection logic to use the generic wasm_channel_owner_ids map instead of a Telegram-specific field.
  • Removed the suggestion to 'restart IronClaw to activate' from activation failure messages.
• src/main.rs
  • Removed the gateway_state variable and the associated restart logic at agent shutdown.
  • Updated the ExtensionManager initialization to pass the new wasm_channel_owner_ids map.
  • Generalized the owner ID injection logic for WASM channels during initial setup.
• src/settings.rs
  • Replaced telegram_owner_id with wasm_channel_owner_ids (a HashMap) in ChannelSettings.
  • Updated to_db_map and from_db_map methods to correctly handle the new wasm_channel_owner_ids structure.
  • Removed Telegram-specific owner ID tests and replaced them with generalized WASM channel owner ID tests.
• src/setup/channels.rs
  • Removed all Telegram-specific setup functions, including setup_telegram, bind_telegram_owner, setup_telegram_webhook_secret, and validate_telegram_token.
  • Removed Telegram-specific structs and imports related to its API.
  • Updated file comments to reflect the generalized nature of channel setup flows.
• src/setup/mod.rs
  • Removed setup_telegram and validate_telegram_token from public exports.
• src/setup/wizard.rs
  • Removed the special handling and call to setup_telegram within the WASM channel setup flow, relying entirely on the generic setup_wasm_channel.
• tests/openai_compat_integration.rs
  • Removed the restart_requested field from GatewayState initialization in test helper functions.
• tests/ws_gateway_integration.rs
  • Removed the restart_requested field from GatewayState initialization in test helper functions.

Activity

• The pull request was created by henrypark133.
• The pull request includes a comprehensive test plan covering code quality checks, unit tests, and manual verification for the generalized WASM channel setup and owner ID functionality.

Using Gemini Code Assist

The full guide for Gemini Code Assist can be found on our documentation page, here are some quick tips.

Invoking Gemini

You can request assistance from Gemini at any point by creating a comment using either /gemini <command> or @gemini-code-assist <command>. Below is a summary of the supported commands on the current page.

Feature	Command	Description
Code Review	/gemini review	Performs a code review for the current pull request in its current state.
Pull Request Summary	/gemini summary	Provides a summary of the current pull request in its current state.
Comment	@gemini-code-assist	Responds in comments when explicitly tagged, both in pull request comments and review comments.
Help	/gemini help	Displays a list of available commands.

Customization

To customize Gemini Code Assist for GitHub experience, repository maintainers can create a configuration file and/or provide a custom code review style guide (such as PEP-8 for Python) by creating and adding files to a .gemini/ folder in the base of the repository. Detailed instructions can be found here.

Limitations & Feedback

Gemini Code Assist may make mistakes. Please leave feedback on any instances where its feedback is incorrect or counter productive. You can react with 👍 and 👎 on @gemini-code-assist comments. If you're interested in giving your feedback about your experience with Gemini Code Assist for Github and other Google products, sign up here.

You can also get AI-powered code generation, chat, as well as code reviews directly in the IDE at no cost with the Gemini Code Assist IDE Extension.

Footnotes

1. Review the Privacy Notices, Generative AI Prohibited Use Policy, Terms of Service, and learn how to configure Gemini Code Assist in GitHub here. Gemini can make mistakes, so double check it and use code with caution. ↩

[gemini-code-assist]

Code Review

This pull request effectively removes the gateway restart infrastructure and generalizes the WASM channel setup, removing Telegram-specific logic. The changes are consistent across the backend, frontend, and tests. I've identified one area for improvement regarding test coverage for the new configuration setting.

_{Note: Security Review did not run due to the size of the PR.}

[gemini-code-assist]

The test test_telegram_owner_id_via_set was removed. While the telegram_owner_id field is gone, this test was covering the Settings::set functionality. With the new wasm_channel_owner_ids being a HashMap, it would be beneficial to add a new test to ensure that setting values in this map via the set method works as expected. This would prevent potential regressions in configuration management.

    #[test]
    fn test_wasm_channel_owner_ids_via_set() {
        let mut settings = Settings::default();
        settings
            .set("channels.wasm_channel_owner_ids.telegram", "987654321")
            .unwrap();
        assert_eq!(
            settings.channels.wasm_channel_owner_ids.get("telegram"),
            Some(&987654321)
        );
    }

[henrypark133]

Good catch — added the test in 20e6f65. The Settings::set() dotted-path API handles this correctly: "987654321" is parsed as a JSON number by the fallback path (line 837) and deserializes into HashMap<String, i64> without issues.