Testlane 0.7.0-beta.1 — agent-authored browser verification

Testlane 0.7.0-beta.1 packages the opt-in testlane-verify skill and authenticated verification harness with the local credential broker. Your coding agent reads the feature brief and app code, writes app-specific Playwright tests, and uses Testlane sessions to run them. The package contains no embedded model or hosted test service.

New in this preview:

• verify init creates a draft suite and copies the fixture/helper without replacing existing tests or changing accounts, profiles or stored credentials.
• verify run binds the plan, spec and helper hashes to actual case outcomes and cleanup. Missing, skipped, duplicated, retried, expected-failure or caught failed assertions cannot produce passing acceptance. Passing cases need an observed Playwright expect; counts cannot prove the quality of the business oracle.
• verify report renders a private local HTML summary. Failed mapped cases can identify a line and column in the hashed spec without retaining raw error messages or values.
• Screenshots require explicit local opt-in. Traces, videos and automatic screenshots remain off.

The attached tarball was prepared by the tagged release workflow. macOS release validation and the Linux Secret Service consumer's nine checks passed. The exact hosted bytes also match the Windows installed-package candidate: its preserved independently authored suite failed on a generated 4199-cent defect, then passed at 4200 with the same plan/spec/config/helper. Both runs verified owned-record cleanup; the installed CLI's alias, init, draft refusal and overwrite protection checks passed. See the attached source/run binding and Windows summary for exact hashes and limits. The merged-main CI run also passed.

Use the installed preview quickstart, existing-app setup and changelog. Install the reviewed tarball into the app project with its pinned Playwright dependency. npm publication is separate; stable latest remains 0.6.0, and any npm preview is intended for next.

This is a pre-1.0 beta. Use approved sandbox/test accounts and existing client permissions. App-authored test code is trusted local code, not a security sandbox. Assertions determine business correctness. Session files are live credentials; deleting a file does not revoke the app session. Local reports/screenshots can contain app data and should stay private unless reviewed. One generated-app proof does not establish complete workflow coverage, all-client compatibility or independent security assurance.