docs: add Iran transit connection/build guide and validation workflow

[ehsanking]

Motivation

• Provide a clear, bilingual build/install section so operators can install, test and optionally package the tool locally.
• Explain how to connect an Iran-hosted server to the public internet via a transit provider and an encrypted tunnel so the project can be used for IP-transit based resilience testing.
• Add end-to-end validation steps (including IP-transit checks) and a simple diagram so non-expert users can follow the workflow.

Description

• Added a bilingual Build | ساخت section with dependency install and packaging commands (npm install, npm test, npm pack, npm install -g ...) in README.md.
• Added a new bilingual section Connecting Iran Server to Internet Transit (Step-by-step) that documents server preparation, listener probes, transit-path analysis, recommended tunnel attachment (WireGuard → OpenVPN/SSH fallback), and final IP transit validation commands (traceroute, mtr, node cli.js analyze).
• Included a simple ASCII network diagram showing User → Transit VPS/CDN Edge → Encrypted Tunnel → Iran Server to aid general audience comprehension.
• Change is documentation-only (single-file README.md addition) and does not modify runtime code or tests.

Testing

• Ran the automated test suite with npm test, and all tests passed (6 tests, 0 failures).

---

Codex Task

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: c2709f99b7

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Open probe port before listener validation

The workflow opens 443/tcp and 51820/udp, but the very next step starts listener on port 9000 and asks users to probe that port. On systems where UFW has a default deny policy, those probe commands will fail even if the tool is working, which breaks the documented validation path. Add firewall rules for 9000 (TCP/UDP) or change the listener/probe examples to an already-open port.

Useful? React with 👍 / 👎.