Export agent evidence as portable Playwright checks

.prettierignore

@@ -0,0 +1 @@
+site/.vercel/

README.md

@@ -12,6 +12,8 @@ The Build Week reference flow records a browser bug, captures the expected outco
 
 The agent-operated reference flow is limited to local HTTP and HTTPS development servers. TaskTape creates a headed isolated Chrome session and exposes 12 bounded MCP tools for observation, interaction, evidence capture, check creation, and explicit execution. Finishing a capture never runs or schedules the check.
 
+Agent-created checks keep their evidence attached. Users can inspect screenshot, console, network, and trace counts, copy a ticket-ready Markdown report, reveal the local files, or export the observed steps as an ordinary Playwright TypeScript test. Exported tests use no LLM at run time and remain reviewable before they enter source control or CI.
+
 Checks have editable instructions and can run now or on hourly, daily, weekday, or weekly timing. Manual and scheduled results appear in Run history, so a team can see when a previously fixed behavior regresses.
 
 A spoken schedule such as "every Monday at 9 AM" prefills the save controls. It never becomes active until the user confirms unattended execution and saves the task. The Scheduled view shows the next run, last result, pause or resume, and Run now controls.
@@ -56,6 +58,7 @@ Ask the connected agent to reproduce a bug on a local development URL and turn i
 - [Architecture](docs/architecture.md)
 - [Agent-operated replay milestone](docs/agent-mcp-milestone.md)
 - [Voice and scheduling research](docs/voice-and-scheduling-research.md)
+- [Reddit competitor research](docs/reddit-market-research.md)
 - [Market validation](docs/market-validation.md)
 - [Milestone roadmap](docs/roadmap.md)
 - [Verification log](docs/verification.md)

docs/architecture.md

@@ -31,6 +31,10 @@ The first MCP capability intentionally targets local web applications. `start_bu
 
 Every operation stores an ordered action plus a screenshot. The session also records console messages, page errors, failed requests, HTTP error responses, initial and final screenshots, and a Playwright trace containing DOM snapshots and action timing. Finishing compiles the recorded actions into a review-required computer workflow and closes the temporary browser. Running or scheduling remains a separate explicit action.
 
+Agent actions also persist their schema-validated replay command. TaskTape can compile those commands into a small Playwright TypeScript test using the exact observed selectors and inputs, without calling a model during later test runs. The export carries the expected outcome as review context and uses a visual assertion that requires the developer to approve a baseline. Older sessions remain readable but cannot be exported from their natural-language summaries.
+
+The same session can produce a Markdown bug report with reproduction steps and diagnostic context. Reports are copied through the main process, exports use a native save dialog and `0600` file mode, and revealing evidence opens the existing local session directory. The renderer receives only evidence counts and availability flags.
+
 ## Capture source selection
 
 TaskTape lists full displays and open application windows through Electron `desktopCapturer`, then renders a grouped thumbnail gallery in the sandboxed UI. A source ID selected by the user is validated against a freshly enumerated main-process source list. The display-media handler consumes that one pending selection and rejects requests without one; the renderer cannot nominate an arbitrary capture target.

docs/hackathon-strategy.md

@@ -347,15 +347,15 @@ The README must then show: what changed during Build Week, exact GPT-5.6 integra
 9. **Can it test any application?** No. The hackathon proves one complete browser workflow and a bounded macOS execution path.
 10. **What happens when the UI changes?** GPT-5.6 reasons over the current screen instead of replaying fixed coordinates, but major changes can still fail and are reported.
 11. **Does it capture passwords?** Agent sessions reject password-field fills, accept only local development URLs, and remain local. API keys use operating-system encryption. Human recordings still require the user to avoid exposing secrets.
-12. **Why not generate Playwright?** TaskTape already uses Playwright for rich capture, but GPT-5.6 replay adapts to the current visual interface and can later extend beyond DOM-only targets. Exportable Playwright tests are future work.
+12. **Does TaskTape generate Playwright?** Agent-recorded browser sessions can export their observed steps as ordinary Playwright TypeScript with a reviewed visual baseline. TaskTape also keeps GPT-5.6 replay for adaptive checks and targets beyond DOM-only browser flows.
 13. **Does scheduling run while the Mac sleeps?** No. The app must be open and the Mac awake.
 14. **What happens on a model safety check?** The run stops before the flagged action executes.
 15. **What did Codex build?** The repo documents the iterative native recorder, schemas, execution adapters, scheduler, tests, and design revisions in dated commits.
 16. **What existed before Build Week?** Nothing in this repository. The first planning commit is dated July 14, inside the submission period.
 17. **What is mocked?** Automated Electron tests mock model responses. The separate live tests use the real OpenAI API and are labeled.
 18. **How reliable is it?** All 61 unit and integration tests and 10 Electron journeys pass. The visual evaluator classified five consecutive broken and fixed pairs correctly, and the paired live replay produced the expected fail and pass results.
 19. **What is the business wedge?** Product and support teams that collect bug videos but lack time to convert every issue into regression coverage.
-20. **What comes next?** Exportable test artifacts, CI triggers, richer event traces, signed builds, and an open evaluation format for computer-use agents.
+20. **What comes next?** Repository-aware exports, CI triggers, reviewed repair suggestions, signed builds, and an open evaluation format for computer-use agents.
 
 ## Red-team conclusion
 

docs/reddit-market-research.md

@@ -0,0 +1,74 @@
+# Reddit market research
+
+Research date: 2026-07-20
+
+## Question
+
+Which competitor features are useful in real QA work, and which gaps should TaskTape close without becoming another generic recorder or opaque AI testing service?
+
+This is qualitative research, not market sizing. Reddit comments are anecdotal and can include vendor promotion. Claims were checked against current product documentation where possible.
+
+## What practitioners keep saying
+
+- Ground automation in a browser flow that a person or agent actually observed. Several practitioners report better results when AI converts a verified Playwright recording into code instead of inventing tests from source code alone.
+- Keep a human in the loop. Reviewable code, explicit expected outcomes, and key-step screenshots matter more than an agent claiming success.
+- Capture debugging context with the report. Console messages, failed requests, screenshots, and exact reproduction steps reduce the developer's work after a bug is filed.
+- Do not require an LLM every time a regression runs. Teams call out cost, latency, noisy MCP sessions, weak selectors, and confidently incorrect assertions.
+- Let the team own the artifact. Ordinary Playwright files fit source control, code review, CI, and existing test conventions better than a closed test format.
+
+## Competitor comparison
+
+| Product or approach                  | What appears to work                                                                                           | Repeated weakness or risk                                                                                                    | TaskTape before this milestone                                                              |
+| ------------------------------------ | -------------------------------------------------------------------------------------------------------------- | ---------------------------------------------------------------------------------------------------------------------------- | ------------------------------------------------------------------------------------------- |
+| Jam                                  | One capture includes video, reproduction context, console and network evidence, then moves into issue trackers | Strong at reporting, but it is not the same as a durable regression test owned in the repository                             | TaskTape stored richer local evidence but did not turn it into a ticket-ready report        |
+| Playwright recorder and MCP          | Real browser execution, familiar code, screenshots, traces, and CI compatibility                               | Generated tests still need review; users report weak locators, missing assertions, token use, and very large generated files | TaskTape captured observed actions but kept them inside its session format                  |
+| BugBug and record-and-replay tools   | Fast recording, screenshots for each step, reports, and low-code editing                                       | Recorder output can be brittle, and a recording without a meaningful assertion is not a regression check                     | TaskTape had an expected result and replay verdict, but no portable test export             |
+| Momentic and Autify-style AI testing | Natural-language authoring, self-healing, run diagnostics, and managed execution                               | Closed or platform-specific formats can reduce control; AI healing still needs governance                                    | TaskTape favored local evidence and explicit approval, but lacked a developer-owned handoff |
+| QA Wolf                              | Playwright ownership, managed parallel runs, CI, and human-reviewed failures                                   | Managed service cost and external ownership are a poor fit for every small team                                              | TaskTape runs locally but did not offer standard code that could graduate into CI           |
+
+## Features selected
+
+### 1. Portable Playwright export
+
+TaskTape now stores structured commands while an agent reproduces a bug and compiles them into a small TypeScript Playwright test. The export uses role, label, text, or CSS locators captured during the observed run, supports a `TASKTAPE_BASE_URL` override, records the expected result, and ends with an explicit visual assertion.
+
+The generated test does not call an LLM. A developer reviews it once, creates the visual baseline, and can then run it in normal Playwright CI. Sessions recorded before structured command capture clearly ask the user to record again instead of guessing from prose.
+
+### 2. Ticket-ready bug report
+
+Each agent-created check can copy a Markdown report containing what happened, the expected result, exact reproduction steps, observations, console and network events, and local evidence filenames. This borrows the useful handoff shape from Jam without uploading private evidence or requiring an issue-tracker account.
+
+### 3. Visible evidence inventory
+
+Saved checks now expose action, screenshot, console, network, and trace counts. Users can reveal the local evidence folder before deciding whether to run, export, or share anything.
+
+## Not selected yet
+
+- **Automatic self-healing:** useful when a locator changes, but dangerous without showing the proposed repair and comparing it with the original intent. This needs a separate review workflow and flake classification.
+- **Direct Jira, Linear, or GitHub issue creation:** valuable, but local Markdown copy provides the handoff without adding OAuth, cloud storage, or a vendor-specific integration during this milestone.
+- **Managed cloud execution:** competitors already serve this category. TaskTape's current differentiation is local evidence, agent operation, explicit review, and portable output.
+- **Automatic codebase edits:** Reddit contains concrete reports of coding agents changing application behavior so generated tests pass. TaskTape exports a reviewable test and does not modify the target application.
+
+## Decision
+
+TaskTape should not compete as another no-code recorder. Its strongest position is the bridge from a human or coding agent reproducing a real bug to two owned artifacts: a developer-ready report and a normal regression test. The product still needs repository-aware export, direct issue handoff, CI setup, and reviewed repair suggestions before it can replace a mature team workflow.
+
+## Sources
+
+### Reddit discussions
+
+- [Are you actually using AI in test automation?](https://www.reddit.com/r/QualityAssurance/comments/1sxdmmo/are_you_actually_using_ai_in_test_automation/)
+- [Anyone actually using AI for test automation? What works?](https://www.reddit.com/r/QualityAssurance/comments/1mna861/anyone_actually_using_ai_for_test_automation_what/)
+- [Has anyone used Playwright MCP yet?](https://www.reddit.com/r/QualityAssurance/comments/1jzkqgs/has_anyone_used_playwright_mcp_yet_im_wondering/)
+- [What real-world QA use cases do you have with AI agents?](https://www.reddit.com/r/QualityAssurance/comments/1tp15zu/what_realworld_qa_use_cases_do_you_have_with_aiai/)
+- [Bug reporting tool discussion about Jam](https://www.reddit.com/r/QualityAssurance/comments/152t1kx/)
+- [Do software testers use any tools or AI for testing?](https://www.reddit.com/r/QualityAssurance/comments/1rq6d23/do_software_testers_here_use_any_tools_or_ai_for/)
+- [What is missing from this AI-driven E2E testing workflow?](https://www.reddit.com/r/Playwright/comments/1umqvix/whats_missing_from_this_aidriven_e2e_testing/)
+- [Claude wrote Playwright tests that secretly patched the app](https://www.reddit.com/r/ClaudeCode/comments/1rug14a/claude_wrote_playwright_tests_that_secretly/)
+
+### Product checks
+
+- [Jam for Linear](https://jam.dev/linear)
+- [BugBug features](https://bugbug.io/features/)
+- [Momentic documentation](https://momentic.ai/docs)
+- [QA Wolf documentation](https://docs.qawolf.com/qawolf/Welcome-to-QA-Wolf)

docs/roadmap.md

@@ -187,6 +187,24 @@ Verified result:
 - The production landing page and stable GitHub download passed desktop, mobile, redirect, full-download, SHA-256, and disk-image checks.
 - The release remains clearly labeled as an unsigned Apple Silicon beta until Apple Developer ID and notarization credentials are available.
 
+## Milestone 6: Portable evidence handoff - Complete July 20
+
+Deliverables:
+
+- Reddit competitor and practitioner research with explicit product boundaries.
+- Evidence inventory on every agent-created check.
+- Ticket-ready Markdown report copied without uploading local evidence.
+- Ordinary Playwright TypeScript export built from observed structured commands.
+- Updated desktop and mobile release site using a verified product screenshot.
+
+Exit gate:
+
+- Unit tests verify deterministic compilation and legacy-session refusal. The Electron MCP journey reads the report from the system clipboard and validates the exported test. That journey passes against the development build, unpacked production app, and read-only mounted DMG.
+
+Verified result:
+
+- The complete gate passed with 66 unit and integration tests, 10 Electron journeys, two release-site browser viewports, package integrity checks, and two packaged-app MCP runs. Exported tests use no model at run time and remain review-required. Automatic repair, direct issue-tracker OAuth, and managed cloud execution remain out of scope.
+
 ## Buffer: July 21
 
 Only submission fixes, reliability fixes, and final upload verification. No new product scope.