Takopi Telegram Coding Bridge

The README discloses the main Telegram, external-agent CLI, progress-streaming, file-transfer, and worktree channels, while release workflows use scoped GitHub permissions and PyPI trusted publishing; authorship and license attribution are clear. Deductions apply because repository, branch, and file operations are powerful yet no runtime least-privilege model, hazardous-action confirmation policy, token storage/redaction policy, retention policy, or complete recovery procedure is shown. Most dependencies have lower bounds rather than exact pins, and no vulnerability scanning or dependency-update policy is evidenced. Unknown publisher identity was not treated as suspicious.

The README, package metadata, entry points, CI, and release workflow agree on the product purpose, supported engines, Python requirement, and versioning, justifying full self-consistency credit. Dependencies and external engine prerequisites are identified, frozen synchronization is used in CI, and releases run tests. Credit is reduced because Python 3.14+ and separately installed PATH engines narrow availability, with no documented fallback. No runtime implementation or user-facing error examples are supplied, so failure_messages receives zero.

The assistant, workspace, and handoff workflows are concrete, and the repository describes multi-project, worktree, group-topic, and terminal-handoff scenarios thoroughly. Engine prefixes, project commands, branch mentions, and plugin entry points provide reasonably precise selection and extension mechanisms. Deductions reflect missing evidence for ambiguous or conflicting triggers, invalid targets, group authorization boundaries, and platform-specific behavior; environment coverage is largely limited to uv, Python 3.14+, PATH engines, and an OS-independent classifier.

The README has clear feature, requirement, installation, setup, usage, plugin, and development sections with pointers to deeper documentation; package, CLI, version, and entry-point naming are consistent. Installation guidance and the complete MIT license justify full marks for those criteria. Deductions apply because the supplied material contains no FAQ, consolidated limitations, support policy, or standalone changelog. Generated release notes and tag/version validation provide only partial version-history evidence. The named author, issue tracker, and release workflow establish an update path, but no maintainer roster, response commitment, or governance policy is shown.

The product offers a clear convenience layer over several agent CLIs through Telegram, with progress streaming, resume support, queues, cancellation, worktrees, and file exchange. These features plausibly create useful mobile-oriented output and marginal value. Scores are reduced because the evidence consists mainly of feature descriptions and test helpers: it provides no representative rendered outputs, evidence of readability for complex results, performance information, or systematic accounting of subscription, Telegram trust-boundary, Python, and engine-installation costs.

Identity, version, dependencies, entry points, license, CI, and publishing claims are traceable to specific supplied files. Engine claims are corroborated between the README and package entry points, while CI and pytest configuration independently show quality gates. Deductions apply because most runtime feature claims lack accompanying implementation files or focused tests in the supplied evidence; the tests shown are only fixtures and event factories. Feature prose also rarely distinguishes supported conditions, exceptions, and intended behavior explicitly.