Add comprehensive GitHub Copilot instructions for telegram-ssh repository

[Copilot]

This PR adds a comprehensive .github/copilot-instructions.md file that provides GitHub Copilot coding agents with detailed instructions on how to work effectively in the telegram-ssh codebase.

Key Features

Exhaustive Command Validation: Every command in the instructions has been tested and verified to work correctly:

• npm install - measured at 3-4 seconds with proper timeout guidance
• node test.js - validates parsing logic immediately
• node bot.js --help - shows CLI interface
• Bot startup testing with dummy parameters (fails at network calls as expected)

Comprehensive Coverage: The instructions address all critical aspects:

• Bootstrap and Setup: Exact dependency installation procedures
• Security Management: npm audit guidance for 8 existing vulnerabilities
• Validation Procedures: Steps to test changes without external dependencies
• Error Handling: Common failure patterns and troubleshooting
• File Structure: Complete repository layout and key file descriptions

Production-Ready Guidance: Includes important operational notes:

• Network limitations in isolated environments
• Required external services (Telegram bot tokens, SSH servers)
• File format validation (JSON array format requirements)
• Timeout recommendations with measured data

Imperative Format: All instructions use the required imperative tone ("Run this command", "Do not do this") with explicit "NEVER CANCEL" warnings for appropriate operations.

The instructions enable any GitHub Copilot agent to quickly understand and work with this Node.js Telegram bot application without needing to explore or experiment with commands that might fail.

Fixes #4.

Warning

Firewall rules blocked me from connecting to one or more addresses (expand for details)

I tried to connect to the following addresses, but was blocked by firewall rules:

• api.telegram.org
  • Triggering command: node bot.js --bot_token dummy_token --chat_id dummy_chat --owner_ids 123456 --path_privatekey /tmp/test_key --servers_file /tmp/test_servers.json (dns block)
  • Triggering command: node bot.js --bot_token test_token_123 --chat_id 12345 --owner_ids 12345,67890 --path_privatekey /tmp/ssh_test/key --servers_file /tmp/test_servers_valid.json (dns block)
  • Triggering command: node bot.js --bot_token test --chat_id 123 --owner_ids 123 --path_privatekey /tmp/test_key --servers_file /tmp/test_servers.json (dns block)

If you need me to access, download, or install something from one of these locations, you can either:

• Configure Actions setup steps to set up my environment, which run before the firewall is enabled
• Add the appropriate URLs or hosts to the custom allowlist in this repository's Copilot coding agent settings (admins only)

---

💡 You can make Copilot smarter by setting up custom instructions, customizing its development environment and configuring Model Context Protocol (MCP) servers. Learn more Copilot coding agent tips in the docs.