Tapp 0.17.4

Field-report fixes: every finding filed from the first real adoption sessions is closed.

• Release-plan refreshes reground decided proposals across id drift and vanished scopes instead of duplicating them; committed items always carry, and migrations are recorded, never silent.
• A single-iOS-target repository keeps its build-confirmed scheme across init --refresh even when the build and the model resolved different Xcode containers.
• Flow replay resolves credentials from a configured actor's environment-variable bindings (tapp flow run FILE --actor NAME, MCP actor); a bound but unset variable refuses the run instead of replaying with placeholders.
• Coordinate taps fall back to labelled controls that report non-hittable at their own center; sessions expose a full raw tree (tree with full: true); auto-recorded waits exclude date ranges such as week headers; managed web ports accept a CORS-exact web.port pin in .tapp/project.json.
• The cold-launch session contract, raw-stdio stderr guidance, and actor set --replace are documented on the agent-facing surfaces.

The core engine remains MIT licensed and runs in infrastructure you control.

Tapp 0.17.3

Public proof and a safer first contact.

• Replaces abstract product claims with inspectable evidence from real Tapp runs: a source-aware focused iOS route, an autonomous simulator recording, and a sanitized full web report.
• Fixes the website copy control and placeholder home link; adds accessible focus states, demand-loaded media, a professional mark, and a social card.
• Adds privacy-conscious structured intake for reproducible bugs and a small paid founding pilot.
• VS Code 0.3.7 adds the Marketplace icon and pins the extension engine to Tapp 0.17.3.

The core engine remains MIT licensed and runs in infrastructure you control.

Tapp 0.17.2

Source-aware focused navigation is now one command across web, iOS, and Android.

• tapp focus reuses the target reviewed during init, prepares it from source, and follows only previously observed UI Map routes.
• Managed web focus owns and cleans up its runtime across CLI and MCP sessions.
• Android source focus builds and installs the modeled module while discovering standard JDK 17 and Android SDK installations automatically.
• Ambiguous repositories stop with exact --target choices instead of guessing.

Qualified from the exact public commit on Node 18/20/22, managed web, a real iOS simulator, Android API 35, the VS Code extension, a staged clean install, and clean registry installs on all three supported platforms.

Tapp 0.17.1

Tapp 0.17.1 makes agent-driven verification faster and more coherent across CLI, Agent Skill, MCP, VS Code, and GitHub Actions.

Highlights:

• Source-connected tapp focus routes agents directly to named screens and controls on web, iOS, and Android.
• Exploration videos and VS Code previews begin only after the app is visibly settled.
• Native record/replay shares field-finding logic and writes honest failure evidence.
• Invalid CLI verbs fail cleanly without first-run side effects.
• Product guidance now consistently separates observation (explore) from deterministic release judgment (ci).

Install: npx -y @aarwitz/tapp@latest --help

Tapp 0.17.0

Stable repository-connected agent testing for iOS simulators, Android emulators/devices, and web (beta). Tapp explores real app surfaces, saves visual evidence, replays reviewed Flows and contracts, and gives deterministic CI gate outcomes with explicit checked/not-checked scope.\n\nInstall the Agent Skill: npx -y skills add aarwitz/tapp --skill tapp\n\nDirect CLI: npx -y @aarwitz/tapp@latest init . --explore\n\nThis release was qualified from the packed npm artifact and the public commit across Node 18/20/22, managed web, iOS Simulator, Android API 35, the GitHub Action, and VS Code packaging.

Tapp 0.17.0-rc.15

Tapp gives coding agents hands and eyes on real iOS, Android, and web apps. This release aligns the Agent Skill, npm CLI/MCP server, GitHub Action, website, and VS Code extension around one honest product contract.

Install the Agent Skill:

npx -y skills add aarwitz/tapp --skill tapp

Or start directly from a repository:

npx -y @aarwitz/tapp@latest init . --explore

Exploration returns findings, coverage, evidence, and limits. Only tapp ci or the GitHub Action returns pass, fail, or inconclusive. See CHANGELOG.md for the complete rc.15 changes.

The attached tapp-0.3.3.vsix is the matching VS Code extension; it is also published in the VS Code Marketplace.

Tapp 0.16.5

Exploratory web QA now reports deterministic verdict findings, advisory sampled probes, and coverage without a misleading 0–100 scalar. Clean web runs say AUTOMATED CHECKS COMPLETE rather than SHIP-READY.

This release also adds a hosted repeat-run determinism invariant and documents the honest contract boundary for claim-versus-API guarantees: use an app-owned verifier or explicit CI preflight until response-body assertions exist in the DSL.

Validation: 242 local tests, all six public CI jobs, package tarball execution, and zero production dependency vulnerabilities.

Tapp v0.16.4

Web QA now reports visible placeholder links, stabilizes dead-control findings against unrelated DOM churn, ignores navigation-aborted resource noise, and avoids terse/media-only blank-page false positives. Clean web results are labeled AUTOMATED CHECKS PASSED rather than SHIP-READY, with content/claim accuracy, API privacy, brand/SEO consistency, and visual credibility explicitly disclosed as unchecked. Verified with two identical 60-action live web runs and a fresh registry install.

Tapp v0.16.3

Package-only web evidence is now more trustworthy: focused open/tree waits for settled content and supports --tap/--wait-for, web QA avoids help-copy and covered-click false positives, repeated missing assets deduplicate across routes, and CLI reports give CLI-native next steps.

Tapp 0.16.2

Package-first onboarding correction.

tapp doctor now sends a ready user directly to the no-MCP CLI workflow:

• npx -y @aarwitz/tapp open [target]
• npx -y @aarwitz/tapp qa [target]

It no longer presents MCP setup as the default next step. The change has a CLI regression test and was verified from both the packed candidate and a clean npm registry install.