rapp-playwright/workplans/RAPP-PLAYWRIGHT-WP-0002-consumer-contract.md

id	type	title	domain	repo	topic_slug	status	flavor	owner	depends_on	created	updated	reuse_check
RAPP-PLAYWRIGHT-WP-0002	workplan	Define the agent consumption contract and first browser trial	infotech	rapp-playwright	stack	proposed	planning	codex	RAPP-PLAYWRIGHT-WP-0001	2026-10-13	2026-10-13	Extend capability.infotech.headless-browser; inspect its existing Playwright examples before implementing a wrapper.

Agent consumption contract

Entry: bootstrap and demand review exist. Exit: a reviewed contract and executable trial specification cover the complete agent path without claiming availability.

Choose execution and target connectivity

id: RAPP-PLAYWRIGHT-WP-0002-T01
status: todo
priority: high

Inspect the registered JS and Python examples and current upstream Playwright contracts. Decide native remote sessions versus submitted jobs, documenting client compatibility, artifact retrieval, per-run isolation and operational cost. Define how workstation development servers and deployed URLs become reachable from the browser. Record supported target/access boundaries and actionable failure behavior. Avoid assuming remote localhost reaches the consumer.

Acceptance: a decision record with a complete fresh-agent sequence, required client setup, version negotiation/pinning, connectivity path and deployment owner. No speculative endpoint is presented as live.

Specify availability, run lifecycle and evidence

id: RAPP-PLAYWRIGHT-WP-0002-T02
status: todo
priority: high

Define preflight, run/session creation, progress, terminal result, cancellation, timeouts and cleanup. Specify request inputs (target, viewports, actions/assertions, time budget) and result fields (run ID, execution location, versions, target, timestamps, per-assertion outcome, error category and artifact references). Define artifact retention and authorized retrieval, and exclusion of credentials and storage state from ordinary evidence. Distinguish unavailable service, unreachable target, browser launch failure and failed UI assertion.

Acceptance: documented request/result examples for success, UI failure and setup failure; defined limits and lifecycle semantics; planned availability is explicit.

Design the minimal trial and content-explorer pilot

id: RAPP-PLAYWRIGHT-WP-0002-T03
status: todo
priority: high

Specify a tiny JS-enabled fixture with deterministic interaction, desktop and narrow viewports, a keyboard focus/action sequence and an observable assertion. Write the proposed one-command trial flow including artifact retrieval. Map it to CONTENT-WP-0000-T04 and identify the consumer-owned pinned OnCo target and acceptance responsibilities. Agree on useful evidence without importing OnCo or treating the fixture trial as the consumer's completed task.

Acceptance: trial specification and consumer checklist are traceable to every demand row; integration and failure cases are ready for WP-0003 implementation.