What problem does it solve? Migration runs to Wix produce no structured feedback about what went wrong, where time was spent, or which skills need improvement. This Skill captures halts, errors, fidelity losses, API gaps, coverage gaps, user decisions, and pipeline defects as validated, privacy-scrubbed telemetry events, plus a finalized run rollup with stage timings, volumes, and verification results. ## Core Features & Use Cases - Validated event recording: A recorder CLI enforces a strict event taxonomy (halt_needs_user, error, fidelity_loss, api_gap, skill_coverage_gap, user_decision, pipeline_defect), folds repeated occurrences per problem class, and rejects unknown fields or invalid enums. - Run lifecycle tracking: Commands for start, dims, stage boundaries, wait intervals, metering (model/API/script latency and token counts), and finalize produce a complete run document with active vs waiting time and derived cost. - Privacy and BI push: A mechanical scrub removes secrets, URLs, and emails from free text, and finalized runs are pushed to a Wix BI sink with GUID validation and batching. - Use Case: During a WordPress-to-Wix migration, the orchestrator starts telemetry at run begin, records an api_gap event when a Wix API cannot express an operation, meters import-stage API latency from the audit log, and finalizes with per-entity volumes and operator acceptance. ## Quick Start Ask the agent to start telemetry for the current migration project by running the recorder's start command with the source platform dimensions, then record events and finalize the run when it reaches a terminal state.
