tpk_cli 0.4.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.4.0 - 2026-10-28

Added

• tpk autotest --project <id> — start an AI test run that the next app of the project with aiRemoteTrigger on picks up; waits for the result and prints findings (--persona, --max-actions, --no-wait, --timeout). Exit code 1 when the run found bugs or failed.
• --task <id> — the AI works through that test assignment step by step; the result shows a verdict per step and the exit code follows the assignment's verdict (passed / failed / incomplete).

0.3.0 - 2026-10-21

Added

• tpk --version (and tpk version / tpk --json version) — print the installed CLI version.
• tpk update (alias upgrade) — self-update from pub.dev via dart pub global activate tpk_cli.

Both were listed under 0.2.0 before, but landed one day after that release was published — the 0.2.0 on pub.dev does not contain them.

Removed

• tpk register and tpk login --email … --password …. Both called endpoints the API dropped with the move to passwordless magic-link sign-in, so they only ever returned 404. tpk login is the device-auth flow (approve in the web console); agents and CI pass a token with the global --token flag.

Changed

• Dependencies: args ^2.7.0, http ^1.6.0, lints ^6.1.0, test ^1.33.0.
• README: install from pub.dev (dart pub global activate tpk_cli), note that an invite-only TesterPayKit account is required, document tpk_mcp. New example/example.md.
• Doc comments no longer contain raw <…> (dartdoc read them as HTML); the package now has its own analysis_options.yaml on package:lints/recommended.yaml, the baseline pub.dev scores against.
• pubspec.yaml no longer points repository at a GitHub repo that doesn't contain the source.

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.