Add prebuilt release automation (cargo-dist) and Homebrew installation

[dlackty]

First off, this project is awesome. Thank you for building something that is genuinely helpful for Taiwan users. It solves a very real problem, and it is great to see a tool that treats zh-TW quality as a first-class concern.

Summary

I’d like to suggest adding a prebuilt release pipeline for zhtw-mcp, so people can install it without having to build from source locally.

That would ideally include:

• GitHub Releases with prebuilt binaries
• a shell installer
• Homebrew installation
• release automation via cargo-dist

Motivation

Right now the install path is mostly source-first:

• users need a recent Rust toolchain
• the first build also needs to generate src/engine/s2t_data.rs
• that makes the initial setup a bit harder for people who just want to try the tool

Since this is a CLI / MCP server, having an easy install path would make it much easier for more people to use and recommend.

Proposed approach

Use cargo-dist to handle release packaging and GitHub Actions.

Suggested scope:

• publish archives for:
  • aarch64-apple-darwin
  • x86_64-apple-darwin
  • x86_64-unknown-linux-gnu
• generate:
  • GitHub Release assets
  • shell installer
  • Homebrew formula
• keep make install as the developer-oriented / local workflow

One repo-specific detail: release builds need to run python3 scripts/gen-s2t-tables.py before Rust compilation, since src/engine/s2t_data.rs is generated.

[jserv]

I completely agree with shipping a prebuilt MCP server to benefit end users. However, my experience with Rust-based projects is still limited. One of my motivations for developing this project is to strengthen my skills in Rust and its ecosystem.

At this stage, I am not able to commit to specific technical details and would really value your guidance. Please feel free to submit pull requests to move this forward.