v0.2.0 — Reproducible isolated demo and release hardening

This release makes the project easier to evaluate and safer to publish without
changing the core trust boundary: intelligence stays outside the MCP server,
while the server provides deterministic Telegram operations and explicit
delivery outcomes.

Highlights

• Added an isolated, reproducible demonstration flow that cannot accidentally
  reuse another running MCP server or external process.
• Added the generated demo artifacts and the commands needed to reproduce them
  from the repository.
• Hardened the release path so a version is built from one exact Git commit,
  verified before publication, and accepted only after the corresponding
  release workflow succeeds.
• Updated clap and bumpalo while retaining the existing compatibility-pinned
  Ferogram and related dependency surface.

Release integrity

The release adapter derives the tag from Cargo.toml, binds its manifest to the
source commit and release notes, and verifies that the remote main branch is
the same commit before creating the tag. Publication is complete only after the
matching GitHub Actions run succeeds and the release is visible under that tag.

Verification scope

The test and demonstration paths are deterministic and isolated from real
Telegram accounts. As in v0.1.0, live provider behaviour is not implied by the
local verification suite; uncertain delivery outcomes remain explicit rather
than being reported as success.

v0.1.0 — First public prerelease

First public prerelease of a deterministic stdio MCP server for one Telegram
personal-account session. Intelligence and human approval stay in the MCP host;
this server provides a typed Telegram boundary.

Highlights

• 14 typed MCP tools for dialog/message discovery, bounded context reads,
  attachment transfer, prepared text sends, and hash-bound file replies.
• Zero-credential --demo mode and a real child-process stdio test covering
  search → context → PDF download → modified copy → SHA-256-bound reply.
• Crash-recoverable prepared text sends with persisted random_id, payload
  hash, terminal receipts, and account revalidation.
• Account-scoped immutable downloads and private upload snapshots that reject
  outside/cross-account paths and file-hash drift.
• Fail-closed single-session selection, canonical peer references, TTY-only
  interactive login, and environment-only secrets.

Install

Install from the exact Git tag:

cargo install --locked \
  --git https://github.com/Stranmor/telegram-personal-mcp.git \
  --tag v0.1.0

This prerelease is not published to crates.io.

Release archives are built on clean GitHub-hosted runners for their native Rust
host triples. Verify downloaded assets against SHA256SUMS before use.

Verification boundary

Release validation is deterministic and credential-free. It exercises the real
binary and MCP transport against the fake/demo backend, but it does not
authenticate to a live Telegram account or send a real Telegram message. Real
Telegram login and MTProto behavior remain prerelease surfaces that require
operator testing.

Known limitations

• Global Telegram search is first-page-only.
• No durable update feed, deletion tool, signup flow, or automatic tdata
  import.
• Prepared/idempotent delivery covers text only.
• Direct send_message and send_file must not be retried after
  DELIVERY_UNCERTAIN.
• Local cache and state are not encrypted or automatically purged.

See README.md for setup/demo instructions, CHANGELOG.md for the full
change set, and SECURITY.md for trust boundaries and private reporting.