tpk_cli 0.2.0

TesterPayKit command-line client. Designed for agentic use — every command supports --json output and --token for non-interactive flows.

Changelog

All notable changes to the TesterPayKit CLI (tpk_cli) are documented here.

The format is based on Keep a Changelog, and this package adheres to Semantic Versioning.

0.2.0 - 2026-07-07

Added

• Terminal dogfood loop — become a tester and file bugs from the CLI:
  • tpk tester login --project <id|bundle> [--code NAME] mints an anonymous per-project tester (idempotent on {project, code}; default code CLI-<HOSTNAME>) and stores it in a parallel tester slot in ~/.tpk, alongside any coordinator login.
  • tpk bug report --title … --severity … files a bug as that tester, auto-starting a session. Options: --description, --type, --category, --screen, --step (repeatable), --session.
  • tpk tester logout clears just the tester session; tpk logout now leaves the tester session intact (parallel identities).
• Admin-provisioned named testers — tpk tester create --email … [--name …] [--status …] (admin login required) creates a managed tester up-front so a known person can sign in via magic-link without the self-signup → pending → approve flow.

0.1.0 - 2026-06-03

Added

• tpk executable — agentic command-line client for the TesterPayKit service. Every command supports --json output and --token for non-interactive / CI / agent flows (envs, sessions, bugs, bug context with navigation flow).
• tpk_mcp executable — read-only MCP (Model Context Protocol) server over stdio JSON-RPC, exposing the same coordinator data (envs, sessions, timelines, bugs, bug context) to MCP-capable agents.
• Talks to the API over HTTP only; no Flutter or TesterPayKit SDK dependency.