rapp-playwright/workplans/RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md
tegwick ccf46d8c59 Implement bounded browser service, consumer evidence and managed package
Assistant: codex
Assistant-Model: gpt-6-astra
Assistant-Session: 01a13590-a16f-7f60-be60-fd71627bc99d
2026-10-13 19:23:29 +02:00

4.8 KiB

id type title domain repo topic_slug status flavor owner depends_on created updated reuse_check state_hub_workstream_id
RAPP-PLAYWRIGHT-WP-0004 workplan Activate the service, prove agent consumption and update discovery infotech rapp-playwright stack blocked implementation codex
RAPP-PLAYWRIGHT-WP-0003
2026-10-13 2026-10-13 Publish provider evidence through existing capability.infotech.headless-browser; do not fork discovery. f9280c40-201e-59b5-a6f0-1aace8e0e2e2

Live service and consumer proof

Entry: WP-0003 passed and deployment/access prerequisites are available through their owners. Exit: a fresh independent agent can execute the documented trial, content-explorer has a usable evidence path, and discovery accurately describes the verified contract and its limits.

Admit and activate the managed workload

id: RAPP-PLAYWRIGHT-WP-0004-T01
status: wait
priority: high
state_hub_task_id: "09f87694-8832-5ae8-9d0b-b66834ffcfcc"

Confirm capacity, network/target reachability, access and credential lanes with the responsible platform owners. Deploy the reviewed digest; verify health, browser launch, result retrieval and failure diagnosis from the consumer network. Exercise restart/recovery, cancellation and rollback against the deployed runtime.

Acceptance: retained commands, release digest, endpoint/access documentation, timestamps and live results demonstrate the contract. Record unavailable owner dependencies as explicit waits rather than inferring admission from repo setup.

Run the independent trial and content-explorer pilot

id: RAPP-PLAYWRIGHT-WP-0004-T02
status: done
priority: high
state_hub_task_id: "08fb80b5-d36b-5b31-8b67-20be5ead70b2"

Have a fresh coding-agent environment use the public-to-consumers instructions without installing a local browser or copying sibling fixtures. Retrieve desktop and narrow screenshots, keyboard interaction outcomes and a machine-readable receipt. Repeat a failing UI assertion and unreachable-target case for diagnosis. Then support content-explorer's pinned baseline target and its own T04 evidence requirements. Keep source/data authorization and consumer task closure with that repo. Record any remaining consumer gap explicitly.

Acceptance: independent fixture receipt and consumer pilot evidence identify commands, client/browser versions, target, assertions and retrievable artifacts; content-explorer assesses its own completion. A health response alone cannot pass.

Publish verified availability and maintain reuse guidance

id: RAPP-PLAYWRIGHT-WP-0004-T03
status: wait
priority: high
state_hub_task_id: "c8642437-27c5-5e58-b0f8-847c285fb4e6"

Publish the supported contract, setup/trial command, endpoint/access route, limitations, versions, artifacts and operational evidence. Notify reuse-surface to update the existing capability record and availability assessment. Supply the exact usable next step for discovery responses and identify source-only fallbacks explicitly. Leave registry ranking fixes with reuse-surface.

Acceptance: inspect the maintained capability and published discovery response to confirm the provider references and claimed availability match the receipts. Retain the notification and readback evidence, synchronize work records, and track any remaining delivery or consumer gap in a live follow-up work record.

Execution evidence — 2026-10-13

T02 passed for provider acceptance: independent initial/final local-container trials and a pinned OnCo home-page pilot retained receipts, screenshots, keyboard outcomes and negative cases. See independent report and pilot. Content-explorer was notified via 621635c9-0a72-4a88-9fd6-2ee1fbddc68f; it decides its own T04 acceptance and further route coverage. Local proof does not imply managed endpoint proof.

T01 remains wait on WP-0003 image publication and railiance-platform admission (c82d75f3-3191-410d-a8c8-fd647bf7f3ef, follow-up e77247e5-ce25-4711-a64f-af81a9f7cbb1). Founder selected that lifecycle owner. The namespace is absent; no workload was deployed. Current capacity and reviewed package exist. Resume with owner admission/access, bootstrap/server dry-run/diff, immutable rollout, independent managed trial and live cancellation/restart/rollback.

T03 remains wait on reuse-surface's maintained and published update. Notification 30503ee1-77f9-4e9e-a63a-2f70ac097823 provides contract and local evidence. Readback still showed planned/source-only provider availability. Delivery of a message is not registry publication. Resume by inspecting the owner update and published discovery response; preserve the local/managed distinction.

Implementation evidence and scope preserve these live waits. This workplan is not finished.