# DISPATCH — Worker 1 (QA Automation & Departmental Reporting Lead)

You are worker_1.
Working directory: c:\Projects\FreeExile\.agents\teamwork\worker_1
Original request path: c:\Projects\FreeExile\.agents\teamwork\ORIGINAL_REQUEST.md (read header ## 2026-10-02T16:35:53Z).
Project scope: c:\Projects\FreeExile\.agents\teamwork\orchestrator_19\PROJECT.md
Explorer reports to read:
- `c:\Projects\FreeExile\.agents\teamwork\explorer_survey_1\survey_report.md` (Client WebApp, render loop, combat, i-frame, Playwright setup)
- `c:\Projects\FreeExile\.agents\teamwork\explorer_survey_2\survey_report.md` (Viewports, mobile orientation, safe area, 9-locale i18n, empirical UI bugs)
- `c:\Projects\FreeExile\.agents\teamwork\explorer_survey_3\survey_report.md` (Stress scenarios, telemetry metrics, 5-department taxonomy, standard bug report schemas)

MANDATORY INTEGRITY WARNING:
DO NOT CHEAT. All implementations must be genuine. DO NOT hardcode test results, create dummy/facade implementations, or circumvent the intended task. A teamwork_preview_auditor will independently verify your work. Integrity violations WILL be detected and your work WILL be rejected.

Core Objectives:
1. Implement the automated browser test harness `tools/qa/run_browser_qa_suite.py` using Python Playwright (or CDP).
   - Ensure it starts the local web server (`tools/serve_webapp.py` on port 8088) or connects to it if running.
   - Run R1 scenarios: Render performance (measure 60fps/120fps, frame times array, avg/min/max FPS, p95/p99 frame times, jank count), combat input buffering (test button presses during wind-up/cooldown), 0.25s i-frame evasion timing (`player.iFrameTimer`), state sync / console & network logs.
   - Run R2 scenarios: Desktop widescreen (1920x1080), Mobile portrait (393x852) and landscape (852x393), Notch Safe Area compensation, 9-language in-place reactive switching (`FreeExileI18n.setLanguage`) measuring latency (target < 10ms, zero page reload) and checking translation parity, virtual controls / joystick / hotswap.
   - Run R3 scenarios: Continuous biome traversal (loading multiple styles from the 30 biome catalog, tracking 8-slot chunk cache), dense combat particle / VFX overload, Target Dummy high-frequency attacks (DPS/combo telemetry), memory footprint tracking (JS Heap before/after, DOM node count, Canvas VRAM context count).
   - Save screenshots and telemetry JSON into `docs/qa/reports/telemetry/`.

2. Execute the test suite and verify that all test runs complete with 0 browser crashes.

3. Author the standardized cross-department issue reports in `docs/qa/reports/` classified by department:
   - Client (`CLI`):
     - `docs/qa/reports/QA-BUG-CLI-20261002-01.md`: Canvas resolution & aspect ratio distortion on viewport switch
     - `docs/qa/reports/QA-BUG-CLI-20261002-02.md`: Portrait orientation critical layout breakage & header overflow
     - `docs/qa/reports/QA-BUG-CLI-20261002-03.md`: Zero combat input buffering causing dropped actions during skill wind-up/cooldown
   - Server (`SRV`):
     - `docs/qa/reports/QA-BUG-SRV-20261002-01.md`: Client-authoritative standalone simulation with mockup HUD ping and missing WebSocket state sync protocol
   - Game Design (`GDS`):
     - `docs/qa/reports/QA-BUG-GDS-20261002-01.md`: Target Dummy DPS meter synchronous layout thrashing & unbuffered skill queuing
   - Art / VFX (`ART`):
     - `docs/qa/reports/QA-BUG-ART-20261002-01.md`: Particle allocation bypass in VFX renderer causing GC pressure and Biome chunk re-bake stutter
   - Security (`SEC`):
     - `docs/qa/reports/QA-BUG-SEC-20261002-01.md`: Missing server-authoritative combat validation, client-side damage calculation & unencrypted local state exposure

   Each report MUST follow the standardized 9-part schema:
   - 1. Header (Bug ID, Severity, Department, Status, Date, Reporter)
   - 2. Title & Executive Summary
   - 3. Severity & Impact Justification
   - 4. Environment & Test Configuration
   - 5. Step-by-Step Reproduction Procedure
   - 6. Empirical Telemetry, Logs & Evidence (Real numbers from browser test runs!)
   - 7. Root Cause Technical Analysis (Specific files, functions, lines)
   - 8. Actionable Fix Proposal & Architecture Alignment (Specific code patches / designs)
   - 9. Verification & Regression Criteria

4. Author the master `docs/qa/reports/QA_EXECUTIVE_SUMMARY.md`:
   - Executive Overview & Test Execution Context
   - Global Quality Metrics Table (FPS avg/p95/p99, i-Frame latency, i18n switch time, Memory Delta, DOM count)
   - Cross-Department Risk Matrix (Prioritized bugs by severity and department)
   - Departmental Action Item Roadmap (Client, Server, Game Design, Art/VFX, Security)
   - Sign-off & Production Readiness Verdict

5. Run any project hygiene checks (`python tools/lint/check_code_and_doc_hygiene.py`, `python tools/lint/check_i18n_hygiene.py --strict`) and ensure all new files comply with project standards.

Deliverable:
All test scripts, telemetry logs, bug reports in `docs/qa/reports/`, `docs/qa/reports/QA_EXECUTIVE_SUMMARY.md`, and your complete handoff report at `c:\Projects\FreeExile\.agents\teamwork\worker_1\handoff.md`.

## 2026-10-02T16:52:45Z
[Message] timestamp=2026-10-02T16:52:45Z sender=c5d663cf-5362-4a81-9212-5f449cfcc314 priority=MESSAGE_PRIORITY_HIGH content=You are worker_1.
Your working directory is: c:\Projects\FreeExile\.agents\teamwork\worker_1
Your original request path is: c:\Projects\FreeExile\.agents\teamwork\ORIGINAL_REQUEST.md (header ## 2026-10-02T16:35:53Z).
Read DISPATCH.md in your working directory for full objectives, inputs, and constraints.
MANDATORY INTEGRITY WARNING: DO NOT CHEAT. All implementations must be genuine. DO NOT hardcode test results, create dummy/facade implementations, or circumvent the intended task. A auditor will independently verify your work.

Implement the automated real-browser test suite `tools/qa/run_browser_qa_suite.py` with Playwright, execute all scenarios (R1, R2, R3), collect empirical metrics, author the departmental bug reports in `docs/qa/reports/` (CLI, SRV, GDS, ART, SEC), and author the master `docs/qa/reports/QA_EXECUTIVE_SUMMARY.md`. Verify hygiene.
When done, write your handoff report to `c:\Projects\FreeExile\.agents\teamwork\worker_1\handoff.md` and message the parent.