Webcmd Adapter Authoring

You are an agent writing an adapter for a site. The goal of this skill is a 30-minute loop from zero context to a passing webcmd browser verify.

Use the existing tools throughout: webcmd browser *, webcmd doctor, webcmd browser init, and webcmd browser verify. This skill does not introduce new commands.

When debugging browser-backed adapters, start with --trace on --keep-tab true --window foreground. --trace on writes a trace artifact every round, and summary.md is the entry point for reviewing both failures and successes. --keep-tab true --window foreground keeps the tab lease alive and puts the browser window in front so you can inspect the final page state.

Precheck: Know Your Lane

Use coverage-matrix.md for a quick self-test before implementation. Ask three questions:

1. Can the data be seen in the browser? If no, solve authentication first.
2. Is the data HTTP, JSON, or HTML? If no, this skill is out of scope.
3. Does the command require real-time push? If yes, look for an HTTP endpoint with the same data; if none exists, stop.

Continue only when all three answers are yes.