rapp-playwright/workplans/RAPP-PLAYWRIGHT-WP-0004-consumer-verification.md

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
blocked_on: message-from:railiance-platform
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
blocked_on: message-from:railiance-platform
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 railiance-platform admission (c82d75f3-3191-410d-a8c8-fd647bf7f3ef, follow-up e77247e5-ce25-4711-a64f-af81a9f7cbb1). Founder selected that lifecycle owner. WP-0003 publication is now complete: exact immutable digest readback and railiance01 pull passed; see publication evidence. The namespace is absent; no browser 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.

Resumed audit after publication

Fresh readback confirmed local provider preflight, absent managed namespace and unchanged planned-provider discovery. See readback. Platform follow-up a282c300-eaef-4cd6-99b0-f4fb255203b3 resolves the earlier registry blocker and requests the remaining admission, consumer binding and initial target decisions. The admission review prepares that decision without inferring approval. Reuse follow-up fbab576e-7737-4b44-ab45-d7215b7ecca4 supplies published release/source evidence. T01 and T03 remain wait until their owner outcomes can be verified. Actual cross-version rollback remains unproven with only one release; same-image recovery must be labeled accurately.

Owner progress accepted — 2026-10-13 21:42 Europe/Berlin

Platform reply 8d1de2a9-5209-4f82-a2cd-80d8c2e07001 and RPF-WP-0056 resolve package admission, deployment and the consumer group binding. Fresh readback confirms 1/1 Ready on the published digest and a Bound 2Gi PVC. Platform operator-driven evidence passes 14 fixture steps, six negative/health checks, and same-image restart with all four artifact hashes retained. Evidence: readback and reviewed receipts. This supersedes the earlier absent-namespace observations.

T01 remains wait specifically for real human/agent authentication, per-caller API transport and native consumer receipts under RPF-WP-0056-T03, plus remaining abrupt-interruption/recovery evidence. Initial eligibility is already decided; no further membership approval is needed. RPF-WP-0056-T06 tracks Custodian coordination. Administrator impersonation does not satisfy consumer acceptance.

REUSE-WP-0024 is finished and live federation now has D3/A5/C2/R2, pinned client instructions, local container guidance and explicit conditional managed access. The local-provider publication requirement is satisfied. T03's remaining wait now follows platform consumer acceptance and the final managed-availability update, rather than an unanswered local-provider registry handoff. The current published admission-pending wording lags the deployed pilot and should distinguish pilot runtime from consumer readiness in that update. T03 stays open as requested by platform until the native consumer receipts are accepted.